MVSFORUMS.com

[Novice]

Last week we encountered this problem and will appreciate if any one of you could answer the questions I have.

Our shop is primarily into insurance business and bought a new vendor product, written in CICS and COBOL. One of the online screens developed in our system accesses a COMBO program(Same program can be accessed through both batch and online. While adding it to endevor, we add two link cards one for BATCH with DSNELI call and ONLINE with DSNCLI call. All the CICS calls/statements will be embedded between CICS-BEGIN and CICS-END. Accordingly CICS translator takes care of this during compilation process and two separate LOAD MODULES will be created for BATCH and ONLINE).

The program calls has the following hierarchy

PGM A --> PGM B --> PGMC --> PGMD

PGM A is online program developed and used with in our System. PGM B is a COMBO program newly developed. PGM C and PGM D are vendor supplied programs. PGM D has a file read operation using the START BROWSE and READ NEXT COMMANDS. The STARTBR command has a parameter coded as

[Meera]

A mistake often made by new CICS programmers is the use/abuse of DFHCOMMARE and workingstorage - the former is under CICS control while the latter is specific to the particular instance(TransID+TermID) of A program. The VSAM files and operations performed on it are also under CICS control. When you returned from D to A, and evaluate the EIBRESP it should show the same value it had before you called B. Why should it change - you did not call B with pointer to A's EIBRESP. The original method of calling created, in essence, DFHCOMMAREA local to A and another local to D - thus overriding the very definition of COMMarea!
What was the values of the fields in your ws-dfheiblk after the return?