On Mon, 6 Sep 2010 15:45:33 +0300, G+D+J+ B+N% #B+J+ wrote: > >The user has the job displayed in the editor. >He Submits the job. >The user enters a command on the command line, moves the cursor to the job >name and presses enter >The command performs the following functions: >1. get the job name from the cursor position
Can the just submitted job ID be read from the screen by an EXEC or macro, or has the message line already been cleared from the screen before the macro begins execution? Wouldn't it be great if ISPF kept the name and number of the last job submitted in variables? (Or does it already?) If a macro issues the submit command, is the job ID available in a reply? >2. starts SDSF >3. enters the prefix command with the job name >4. enters the ST command. > >The user can then look at the job, monitor its execution, and do all the other >wonderful things you can do in SDSF. > I have mixed feelings about this. You appear to want "SDSF for Dummies", sparing the user any real knowledge of what he's doing. Any programmer with the skill to be editing and submitting JCL ought to be well capable of mastering SDSF. But it sounds so convenient that I'd use it if it were there. But I'd make little effort to obtain it or create it. Usually I just keep SDSF ST display with OWNER <userid()>; PREFIX *; sorted by submission time descending in another split. On submitting a job I need only to SWAP to that other split and the job just submitted appears on the top line. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
