I'm puzzled by the question. First, what is the point address ISPEXEC ISREDIT? It's an expensive NOP.
Second, wasn't the last thing the user did to call your macro? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of [email protected] <[email protected]> Sent: Sunday, May 3, 2026 2:59 PM To: [email protected] <[email protected]> Subject: Test for command after Rexx ISREDIT External Message: Use Caution I'm not well versed in Rexx -.I do have a simple rexx routine which calls another routine to issue a macro as follows:. address ISREDIT "macro (PDSMEM) NOPROCESS" "CHANGE '@@@class' '"drgclass"'" "CHANGE '@@@packg' '"drgpackg"'" "CHANGE '@@@envt' '"lenvt"'" . address ISPEXEC "ISREDIT SAVE "t.I have no issues with the above code snipet -It works very well as expected -.When the Edit session is returned to the user, I would like to detect the last function the user performed on that screen -The user could have entered SUBMIT, CANCEL, simply depressed the enter key, or decided to end with PF3 -How can i easily and safely determined what the user last performed ?..paul ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
