Re: FILTER cmd not working in batch SDSF?
On Fri, 18 Jul 2008 19:09:30 -0400, Farley, Peter x23353 [EMAIL PROTECTED] wrote: I guess I'll have to wait until Monday and give it to my sysprogs. Thanks for trying to help. Peter I use PGM=SDSF and have two ways to capture job output in batch dating back to early SDSF. 1) Using FILTER and FIND //* //* CAPTURE SPOOL OUTPUT TO SEQUENTIAL DATA SET //* //CAPTURE EXEC PGM=SDSF,PARM='' //ISFINDD * PREFIX MYJBNM* H FILTER JOBID EQ JOB02785 FIND MYJBNMP ++S PRINT FILE OUTDD01 PRINT PRINT CLOSE /* //ISFOUT DD SYSOUT=* //OUTDD01 DD DISP=(NEW,CATLG),DSN=MYJBNM.JOB02785, // UNIT=SYSALLDA,SPACE=(TRK,(20,2)), // DCB=(DSORG=PS,RECFM=VBA,BLKSIZE=0,LRECL=255) //* // 2) Using Select. //* //STEP001 EXEC PGM=SDSF //ISFOUT DD SYSOUT=* //ISFINDD * PRE KTOMIAK* OWNER * H S KTOMIAKK JOB00207 F KTOMIAKK ++? F JESJCL ++S PRINT FILE DDNAME PRINT PRINT CLOSE END /* //DDNAME DD DISP=(NEW,CATLG),DSN=KTOMIAK.JOBOUT.JOB00207, // UNIT=SYSDA,SPACE=(TRK,(45,45),RLSE), // DCB=(DSORG=PS,RECFM=VB,BLKSIZE=0,LRECL=255) //* -- 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
Re: FILTER cmd not working in batch SDSF?
Thank you very much for those excellent examples. The business problem at hand here though is to select just the JESMSGLG output from the jobs to be selected. I did try using SDSF and noted that the FILTER and SELECT operations do work with SDSF, unlike IFSADF. Hmm-m-m-m. I did NOT try selecting the job with ++S and then issuing a FIND for the JESMSGLG component, followed by a PRINT. I will try using SDSF and the PRINT command for this and report back. I still think I'll report the ISFADF failure to my sysprogs, that really ought to either work just like SDSF or be documented not to work. Thanks again for the excellent examples. You made me re-think the problem, and that's a Good Thing(tm). Regards, Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth E Tomiak Sent: Saturday, July 19, 2008 9:40 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: FILTER cmd not working in batch SDSF? Snipped I use PGM=SDSF and have two ways to capture job output in batch dating back to early SDSF. Excellent examples snipped This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
Re: FILTER cmd not working in batch SDSF?
Reporting back as promised. Using PGM=SDSF and Ken's examples as a model, I was able to get the result I wanted. Herewith a sanitized version of what worked for the archives, and a big Thank You to Ken. Note the DISP of MOD for the OUTFILE DD so that multiple job outputs can be captured in the same file and no RLSE parameter on the SPACE so that many jobs could be captured without creating many small extents. //GETSDSF EXEC PGM=SDSF,PARM='++0043,133' //ISFOUT DD SYSOUT=* //OUTFILE DD DISP=(MOD,CATLG,CATLG),DSN=SYSUID..MYJOBS.JESMSGLG, // UNIT=SYSDA,SPACE=(TRK,(15,15)), // DSORG=PS,RECFM=VBA,LRECL=259,BLKSIZE=0 //ISFINDD * SET CURSOR OFF PREFIX TSOUS* H SELECT TSOUSERX JOB61996 FIND TSOUSERX ++? FIND JESMSGLG ++S PRINT FILE OUTFILE PRINT PRINT CLOSE END END H SELECT TSOUSERX JOB60137 FIND TSOUSERX ++? FIND JESMSGLG ++S PRINT FILE OUTFILE PRINT PRINT CLOSE END END // This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
Re: FILTER cmd not working in batch SDSF?
I have REXX code for pre-z/OS 1.8 that accepts a jobname and jobnumber and allocates the output file dynamically that I use so one jobb step can grab several outputs. z/OS 1.8 and above has a wonderful API to SDSF for REXX, too. Glad it helped. On Sat, 19 Jul 2008 10:36:03 -0400, Farley, Peter x23353 [EMAIL PROTECTED] wrote: Reporting back as promised. Using PGM=SDSF and Ken's examples as a model, I was able to get the result I wanted. Herewith a sanitized version of what worked for the archives, and a big Thank You to Ken. -- 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
Re: FILTER cmd not working in batch SDSF?
You proved how being flexible in accepting a solution to a goal beats forcing a pre-chosen method. The other way may just need another command here or there. (I'm not logged on to check but was trying to recall if the PGM=name used is just an alias on the other.) On Sat, 19 Jul 2008 10:10:28 -0400, Farley, Peter x23353 [EMAIL PROTECTED] wrote: Thanks again for the excellent examples. You made me re-think the problem, and that's a Good Thing(tm). Regards, Peter -- 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
Re: FILTER cmd not working in batch SDSF?
ITYM z/OS 1.9, don't you? There are no REXX chapters in the 1.8 SDSF manual, but there is quite a bit of that in the 1.9 version. Unless there's a back-level PTF implementing REXX support for 1.8? Though without access to SMP here (not a sysprog), I wouldn't know if that's installed or not. We haven't gotten to 1.9 yet, though it's coming sometime later this year I am told. If you would be so kind as to send me (or publish here, your choice) the REXX code you mentioned, I would love to give it a try. Or even better you could publish it to the CBT for everyone to use. Regards and thanks again, Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth E Tomiak Sent: Saturday, July 19, 2008 11:57 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: FILTER cmd not working in batch SDSF? I have REXX code for pre-z/OS 1.8 that accepts a jobname and jobnumber and allocates the output file dynamically that I use so one jobb step can grab several outputs. z/OS 1.8 and above has a wonderful API to SDSF for REXX, too. Glad it helped. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
FILTER cmd not working in batch SDSF?
I am running batch SDSF for the first time, using PGM=IFSAFD so I can enter both line commands and also be able to fill in the XD output screen fields. OS level is z/OS 1.8. Here is the input to IFSAFD: //GETSDSF EXEC PGM=ISFAFD,PARM='++0043,133' //ISFOUT DD SYSOUT=* //ISFINDD * SET CURSOR OFF H FILTER JNUM EQ 2197 //* But the FILTER command results in a display on ISFOUT of ALL of the jobs in the Hold screen, NOT just the selected job number. The same command entered on the SDSF screen in TSO results in just the one job being displayed, the one with that job number. FILTER JOBID EQ JOB02197 gives the same results online (works) and in batch (doesn't work). Same results also for SELECT jobnameX JOB02127. Same results using 5-digit number with leading zeroes for JNUM selection. Am I doing something wrong here or should I be asking my sysprogs to check IBMLINK for APAR's? Or did I miss something important in the SDSF manual? This is a problem because I may have many jobs with the same name (format: TSO userid + 1 char) in the Hold queue and I want to select just a specific one, since IFSAFD only operates on the job/dsid at the top line of the screen. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
Re: FILTER cmd not working in batch SDSF?
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Farley, Peter x23353 Sent: Friday, July 18, 2008 5:52 PM To: IBM-MAIN@BAMA.UA.EDU Subject: FILTER cmd not working in batch SDSF? I am running batch SDSF for the first time, using PGM=IFSAFD so I can enter both line commands and also be able to fill in the XD output screen fields. OS level is z/OS 1.8. Here is the input to IFSAFD: //GETSDSF EXEC PGM=ISFAFD,PARM='++0043,133' //ISFOUT DD SYSOUT=* //ISFINDD * SET CURSOR OFF H FILTER JNUM EQ 2197 //* But the FILTER command results in a display on ISFOUT of ALL of the jobs in the Hold screen, NOT just the selected job number. snip Perhaps filters are OFF. Setting a filter condition does not automatically make filters ON. You might try adding another line to ISFIN that says FILTER ON. Bill Bass Senior Applications Developer United Health Care Greenville, SC This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. -- 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
Re: FILTER cmd not working in batch SDSF?
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Bass, Walter W Sent: Friday, July 18, 2008 6:30 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: FILTER cmd not working in batch SDSF? Snipped Perhaps filters are OFF. Setting a filter condition does not automatically make filters ON. You might try adding another line to ISFIN that says FILTER ON. Adding FILTER ON after the filter command didn't make any difference, but thanks for the suggestion. When I use the FILTER command online, they are automatically turned on, giving a display like this one (notice the DISPLAY area shows FILTERS=1): SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 2,545 LINE 1-1 (1) COMMAND INPUT === SCROLL === CSR PREFIX=TSOUS* DEST=(ALL) OWNER=* FILTERS=1 SYSNAME=* NP JOBNAME TYPE JNUM CRDATEC FORM FCB DEST TOT-REC TSOUSERX JOB 2217 07/18/2008 X STD DEFAULT 2,545 This does not happen under ISFAFD. Nothing is ever filtered, although with SET DISPLAY ON the FILTERS=1 shows up. It's just that nothing is actually filtered. I guess I'll have to wait until Monday and give it to my sysprogs. Thanks for trying to help. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
