I did something like this a few years ago. As I recall: a) I did have the job ID, but I don't remember for sure how I got it. I think the exec did the actual submission, trapped the response with the job ID, captured the ID for itself, then used SAY to repeat the message for the user. But maybe it examined all the jobs having the desired name and picked the latest one, including one that might still be executing or in the input queue.
b) The job was still running when the exec was going, so the exec had to loop around querying SDSF and, if the job hadn't completed yet, waited a half second or so and then asked again. Like yours, this had to be a fast-running job. I'm a lot hazier on the details than I thought I would be when I started this email, but I'm pretty sure of all the above. --- Bob Bridges, [email protected], cell 336 382-7313 /* A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -Lazarus Long */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tony Harminc Sent: Sunday, September 8, 2024 15:20 It certainly displays it (doubtless obtained using the VSAM/JES interface). But whether it makes it available to REXX other than by capturing the message, I don't know. --- On Sun, 8 Sept 2024 at 15:03, Radoslaw Skorupka < [email protected]> wrote: > BTW: does regular ISPF edit SUBMIT get a jobid as a return value? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
