I have the following case,

PROG-A, PROG-B and PROG-C are EGL generated to COBOL/CICS.

PROG-X is a non-EGL and COBOL/CICS.

I know the EGL rule does not allow a program CALLED make a TRANSFER (XCTL) to a MAIN program.

But nothing prevents a cobol CALLED make a XCTL for EGL program.

I know the consequences, but what I'm doing is allowed? or have anything in EGL that prevents this external action ?

Why I got abend ELAB in the PROG-C ?

Thanks !

Hsieh,

From what I can see in your picture, the XCTL will start up Prog C in the same transaction.  Therefore, Prog C is sharing the same EGL rununit as Prog A and B and it essentially is detecting you are trying to transfer to a Main program from a called program (not allowed).

If all you want to do is start a "new" main program, then doing a CICS START from the non-EGL may work as it starts a new Rununit.    You could also look at doing a VGLib.startTransaction from Prog B.  This will not shut down the Prog A and Prog B rununit, but will start an asynchronous transaction (independent). 

If I were you, I would see how you can shut down Prog A and Prog b and do the transfer from Prog A (or use our Return Immediate support before it terminates.  That is what you are effectively doing when you issue an XCTL....as it is "ending" prog A and prog B.

take care.

Mark

Hi Mark,

I undestood. I will make your instruction.

Thanks a lot !