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.
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 .VO7aaqqaAFk.0@/search390>discussion forums.
Dig deeper on Mainframe operating systems and management
Related Q&A from Robert Crawford
With 3270 bridge, you can't stack input messages into one structure. The bridge can't process them all at once. It takes a little more work.continue reading
CICS expert Robert Crawford offers advice on determining the connection between CICS transactions and MQ Queue name.continue reading
CICS expert Robert Crawford discusses if a program can use IXLLIST macros in CICS when IXLLIST are APF.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.