Yes, it does just toss it out as an error and keeps going. And I've considered this and I may have to resort to it. It is just that the SYSIN for my process already is darned huge and this would enlarge it tenfold if I did up to 10 SEQ for each... but... I may just have to. Thanks, good suggestion.
-----Original Message----- From: Robert A. Rosenberg [mailto:[email protected]] Sent: Tuesday, October 23, 2012 2:34 PM To: IBM Mainframe Discussion List Cc: George, William@FTB Subject: Re: SARBCH - PRINT all SEQ's of a GEN= for jobs At 13:01 -0700 on 10/23/2012, George, William@FTB wrote about SARBCH - PRINT all SEQ's of a GEN= for jobs: >I do know a LIST on the job with GEN=1000 and no SEQ will list each >time it ran within a GEN with their sequence numbers. With this info I >could construct another SARBCH job with 3 individual PRINT commands, >one for each SEQ number. However, due to how the process is setup, is >all done in REXX, it would add a tremendous amount of overhead to LIST >each job first, read in the results, then construct another SARBCH from >the LIST results. There are about 70 jobs I have to extract SAR >reports from and doing a single PRINT (or LOAD) would be FAR more efficient. > > > >Any insights? What happens if you ask for seq=4 when there are only 3 versions? If it just tosses an error message and goes to the next commend, why not just submit 100 commands asking for seq=1 to seq=100. Once it has processed all the existent sequences, it will just ignore the requests for the non-existent ones. ______________________________________________________________________ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
