I need help with the START command. What happened is: program A checks if PF1 is pressed, it starts transid(B)...
at same terminal. User pressed PF1 and right after that PF2 was pressed. Therefore, the user was kicked off from CICS region. How can I make the second PF key pressed by user stay at buffle until the started task finishes?
Although it is difficult to understand your question, it looks like you have hit the dreaded EB trap.
When you do an XC START TRAN(Y) TERM(x) , the 3270 terminal is open for keyboard-related activity. Thus, if the user gets in quickly, they can initiate transaction Z before Y gets going. This is because, in VTAM terms, an End Bracket has flowed from CICS so permitting keyboard input.
In your case, it looks like the transaction initated by PF2 has got going before the one previously started by PF1 so causing the failure.
You get around this by not doing an XC START but an XC RETURN TRANSID(B) IMMEDIATE. This will start the B transaction at the terminal without ending the Bracket. The terminal will not be unlocked, and so the use of PF2 will not start its transaction as there is not an opportunity for the user to interrupt processing.
Transaction B had better check for PF2 after its first interaction with the user to reject usage.
Related Q&A from Robert Crawford
I want to replicate DB2 from the mainframe to an AIX box since it's cheaper and the copy can be used for testing. Is this possible?continue reading
What's the impact on I/O when you run in a CPU-constrained mainframe environment?continue reading
I need to transfer one PS file's data from a mainframe to a Linux server. Are there any JCL scripts that can do this for me?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.