Under CICS Transaction Server Version 1, Release 3, we have a number of programs that are executed via XCTL from another program. The called programs on initial execution execute a START command to themselves but not sure why. Entry is always initiates through a menu system.
When original entry is through the terminal owning region (TOR), the START command results in a loss of the EIB information after execution of the START command. When original entry is through the application-owning region (AOR), the EIB information is maintained and is available after the START command.
This is an old problem that dates back about seven years that has been neglected but I would really like to figure out what is going on. Any ideas?
I'm not at all sure I understand the symptoms you are observing but seven years is a long time for it to be a bug! I cannot conceive how an EIB is lost after doing an XC START in the CICS transaction that did the XC commands itself. I suspect that you are actually observing that the EIB fields (of which I guess the TERMID is what you are really noting) are different for a non-terminal attached transaction as against a terminal-attached transaction and you seem to have these two cases so that is consistent. I suspect that as one way of getting running via the XC START SYSID runs non-terminal whilst the other runs Terminal this is what is giving a different content of the EIB.
CICS Technical Strategist -- CICS expert at Search390.com
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our
This was first published in December 2005