As part of a POC we have exposed a CICS "Cobol DB2 code" as a webservice. The code is getting invoked on request through the transaction CPIH. The code is calling another module where it fails on first DB2 hit with -922.
To resolve the same I have provided the approach to create the WSDL file and WSBIND file with new transaction name that will be defined in CICS with new RCT entry and PCT same as that of CPIH.
This I have done seeing that after -922 we may again hit -805 problem. Thinking this we have gone ahead with user defined transaction then both problem may be resolved. We are yet to test the approach.
Can anyone say that we are on right track or there is another way round with CIPH transaction itself.
We created the wsdl and wsbind file for the COMMAREA of the code and used the wsdl in a Java code. The Java code calls the the CICS code through SOAP using the wsdl. The input to the COMMAREA is built by java before invoking the cics code.
Using the new transaction instead of CIPH transaction, for which i created the PCT and RCT entry and provided public access to the plan, has worked for me and no more -922 problem is coming. But sill I would like to know if it was possible through CPIH transaction itself and I may have missed on some settings.