Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWe had to change to using the supplied examples using "CASTRAND" and "CASFILE" to have files and transactions executed from batch. Do you have those programs?
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWe had to change to using the supplied examples using "CASTRAND" and "CASFILE" to have files and transactions executed from batch. Do you have those programs?
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWe had to change to using the supplied examples using "CASTRAND" and "CASFILE" to have files and transactions executed from batch. Do you have those programs?
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerCASTRAN command is used to CEMT like commands for CICS programs in microfocus. I am talking about executing a CICS program. To take an example of the scenario which i am asking is
1. There is a CICS program PGMA defined in CICS in PCT and PPT entries and the txn to execute it TRN1
TRN1 --> CICS transaction to execute PGMA
2. A batch program ( Only COBOL ) which uses CICS EXCI ( CICS External Interface ) to execute the PGMA
PGMB --> Batch program
JCL1 --> One of the steps is to execute the batch progm PGMB which uses EXCI to execute PGMA
My question is how do i make the step 2 work in microfocus.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerThat's what I am trying to tell you. We couldn't get it to work and converted our stuff to use CASTRN from batch in place of exci. So if some one has it working I'd too would like to know what they did.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerThat's what I am trying to tell you. We couldn't get it to work and converted our stuff to use CASTRN from batch in place of exci. So if some one has it working I'd too would like to know what they did.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerCurrently it's not possible to use EXCI from a batch program (running under the JES subsystem) in Enterprise Server.
There are a few supported ways to invoke a CICS transaction from outside CICS:
- Write a normal (non-mainframe) COBOL program that uses EXCI to invoke the transaction, and deploy it as a Web Service to Enterprise Server. Then generate a proxy for the service, and have your batch program invoke the Web Service using the proxy.
- Use a CICS communications facility such as EZ Sockets or CICS Web Interface to create a CICS server that will invoke your transaction, then write a client program for it. This is basically a less-convenient version of the previous option.
- Use External Call Interface (ECI) to invoke a CICS transaction in the same region or a remote one, using the CICS Transaction Gateway (CTG) protocol. To do this from COBOL, I believe you need Studio/Server 6.0 SP2 WS2. (Earlier products have server-side support for CTG, but didn't supply a client library, so it was mainly for the benefit of Java clients using IBM's CICS Transaction Gateway classes.)
You may also want to talk to your support representative about raising an enhancement request for this functionality.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWanted to reopen this conversation again.
If we go by the 1st option
◦Write a normal (non-mainframe) COBOL program that uses EXCI to invoke the transaction, and deploy it as a Web Service to Enterprise Server. Then generate a proxy for the service, and have your batch program invoke the Web Service using the proxy.
I followed the steps and was able to deploy the batch program as webservice and generated a client.
Would it be possible to invoke the webservice thru a JCL in Microfocus ES ? If so , what are the steps required to accomplish it.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWanted to reopen this conversation again.
If we go by the 1st option
◦Write a normal (non-mainframe) COBOL program that uses EXCI to invoke the transaction, and deploy it as a Web Service to Enterprise Server. Then generate a proxy for the service, and have your batch program invoke the Web Service using the proxy.
I followed the steps and was able to deploy the batch program as webservice and generated a client.
Would it be possible to invoke the webservice thru a JCL in Microfocus ES ? If so , what are the steps required to accomplish it.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerWanted to reopen this conversation again.
If we go by the 1st option
◦Write a normal (non-mainframe) COBOL program that uses EXCI to invoke the transaction, and deploy it as a Web Service to Enterprise Server. Then generate a proxy for the service, and have your batch program invoke the Web Service using the proxy.
I followed the steps and was able to deploy the batch program as webservice and generated a client.
Would it be possible to invoke the webservice thru a JCL in Microfocus ES ? If so , what are the steps required to accomplish it.
Hello,
We have a batch COBOL program which runs during our batch process to execute a CICS transaction via the CICS EXCI Interface.
It uses the CICS LINK command to accomplish the work. I referred to the manuals and was able to compile the program with additional directives CICSEC EXCI YES. When i run the migrated JCL, i am not getting the desired result.
Within manuals it is written that COBOL program needs to be executed as a webservice. Is it not possible without that ?
please let me know.
Thanks
#EnterpriseServerYou can run a program that calls the web service proxy under JCL. As far as I know, nothing special needs to be done here. You write a COBOL program that sets the appropriate parameters and calls the web service proxy you generated, then you run that program from your JCL as you would with any other COBOL program.
