Re: report splitting
Put the output to a dataset and process with Sort and icetools. Rob On Sat, Aug 29, 2020, 08:21 Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Fri, 28 Aug 2020 18:14:47 -0700, Ed Jaffe wrote: > > > >Haha! Thanks Dave for pointing out (E)JES' API can be called from HLASM, > >COBOL, C/C++ and similar machine-speed languages (as well as REXX and > >Java). SDSF's is REXX and Java only. > > > And OS/390 2.10? > > And how is the Rexx compatibility? Does ADDRESS SDSF work with (E)JES, > or must it be ADDRESS EJES because of trademark restrictions? > > Some aver that Java's JIT translation competes with "machine-speed > languages". > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
On Fri, 28 Aug 2020 18:14:47 -0700, Ed Jaffe wrote: > >Haha! Thanks Dave for pointing out (E)JES' API can be called from HLASM, >COBOL, C/C++ and similar machine-speed languages (as well as REXX and >Java). SDSF's is REXX and Java only. > And OS/390 2.10? And how is the Rexx compatibility? Does ADDRESS SDSF work with (E)JES, or must it be ADDRESS EJES because of trademark restrictions? Some aver that Java's JIT translation competes with "machine-speed languages". -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
Isn't this an OS390 O/S?, if so, I'm not sure what SDSF REXX interfaces are supported. I have developed some SDSF REXX code (sorry Ed Jaffe ). It does exactly what Tony is looking for. We have some Windows apps that talk back to Tivoli Workload Scheduler and all the output ends up in a Tivoli bucket started task with the output in a JES2 writer. The problem we had was linking some Windows task with the originating z/OS batch job. This is how we dealt with it: We read the Tivoli STC output and parse the writer output. This contains the original z/OS job name and any return code and failure information. We scrape this output and create a new job name that matches the originating job. The new output is printed using IEBGENER. We purge the writer output from the STC, so it won't be seen again. The job is picked up by our output manager (OMCS) and archived. It's clunky but it gives the end user the ability to look at the job with its original name. On Sat, Aug 29, 2020 at 11:29 AM Steve Smith wrote: > I suggest the original output be directed to a regular file, which would > make reading it for the split much simpler. If that's not an allowed > change, oh well (or ow, hell?). > > I think I might suggest to the client that I could replace the existing > vendor product for say, 50% of the cost. That should give you the > motivation to find the time to write it. > > sas > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
I suggest the original output be directed to a regular file, which would make reading it for the split much simpler. If that's not an allowed change, oh well (or ow, hell?). I think I might suggest to the client that I could replace the existing vendor product for say, 50% of the cost. That should give you the motivation to find the time to write it. sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
On 8/28/2020 4:37 PM, Gibney, Dave wrote: How about with APIs available with E(JES) :) ? Haha! Thanks Dave for pointing out (E)JES' API can be called from HLASM, COBOL, C/C++ and similar machine-speed languages (as well as REXX and Java). SDSF's is REXX and Java only. In this case, I might suggest using any of SSI 80, SDSF, (E)JES, perhaps even IOF or others, to dynamically allocate the sysout needing to be split to an input DD of your choice (e.g., for SPOOL BROWSE). Then dynamically allocate an output DD to sysout using TSO/E ALLOC or whatever. Then, in a real, machine-speed program (not a REXX)... 1. OPEN both DDs, loop and copy records input -> output until the split separator is reached. 2. Once reached, CLOSE, re-allocate, and re-OPEN the output DD. Loop back to #1 above and continue as before until the next separator or EOF is reached. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
How about with APIs available with E(JES) :) ? > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Ed Jaffe > Sent: Friday, August 28, 2020 4:30 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: report splitting > > On 8/28/2020 3:40 PM, Gibney, Dave wrote: > > I think I've recently seen SDSFand Rexx examples here sufficient to make a > start at this. > > > Okay, if they are short reports. > > I would *NOT* process millions or even hundreds of thousands of lines of > SPOOL data using REXX. > > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://urldefense.com/v3/__https://www.phoenixsoftware.com/__;!!JmP > EgBY0HMszNaDT!8RW9pqhvk9C2XPbzNFyzvD38ee1iTMzRRmQaChJ3RI- > tv0pwnQ-MUUg6QOgJbA$ > > > > This e-mail message, including any attachments, appended messages and > the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to > be > free of any virus or other defect that might affect any computer system into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
On 8/28/2020 3:40 PM, Gibney, Dave wrote: I think I've recently seen SDSFand Rexx examples here sufficient to make a start at this. Okay, if they are short reports. I would *NOT* process millions or even hundreds of thousands of lines of SPOOL data using REXX. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
I think I've recently seen SDSFand Rexx examples here sufficient to make a start at this. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Tony Thigpen > Sent: Friday, August 28, 2020 3:03 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: report splitting > > I need to clarify that we can't touch the programs. All the original > programmers are gone and with them their knowledge. The one contract > programmer they have is only allowed to make regulatory changes. > > This has to be done with a process that gets the reports out of the JES2 > queue and puts them back in as separate reports. It just need simple "if > I see this on a header line, break up the report" logic. > > I have written this for z/VSE before, I guess I just need to allocate > the time to convert the z/VSE code to z/OS. > > Tony Thigpen > > Mike Schwab wrote on 8/28/20 5:17 PM: > > https://urldefense.com/v3/__http://www.mabu.org/jcl- > reference.pdf__;!!JmPEgBY0HMszNaDT!5liv5KBe8CS6- > gtdU2bN0DxEO_hZAwtFGMCiJaPoAjGSf9-VlAHW08m6V1d6ww$ OS/390 > 2.10 from 2000 reference. > > Same example is on > > > https://urldefense.com/v3/__https://www.ibm.com/support/knowledgece > nter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieab600/outst.htm__;!!JmPEgBY0H > MszNaDT!5liv5KBe8CS6-gtdU2bN0DxEO_hZAwtFGMCiJaPoAjGSf9- > VlAHW08n1GeuG9Q$ > > > > //OUT1 OUTPUT DEST=STLNODE.WMSMITH > > //OUT2 OUTPUT CONTROL=DOUBLE > > //DSDD SYSOUT=C,OUTPUT=(*.OUT1,*.OUT2) > > > > So set one to print, and one to hold, then reference both. > > > > On Fri, Aug 28, 2020 at 8:21 AM Tony Thigpen wrote: > >> > >> All, > >> > >> I have an old OS/390 2.10 system that I need to support for a few more > >> years until the customer finishes their off-platform migration. > >> > >> The current project involves removing costly third-party software that > >> is providing minimal returns for a large cost. One of those products is > >> a report archive system, but the only part still being used is the > >> function of 'report splitting' which just sticks the reports back into > >> the JES2 queue as separate reports. > >> > >> While writing something is fun, I don't really have time to write this > >> one as there are other things I need to write first. > >> > >> I don't see anything on the CBT that addresses this, but there may be a > >> small item in a larger bundle that I can't identify from the contents of > >> FILE001. Or, someone may have some basic code they can share so that I > >> don't have to re-invent the wheel on this one. > >> > >> > >> Tony Thigpen > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > > -- > > Mike A Schwab, Springfield IL USA > > Where do Forest Rangers go to get away from it all? > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
I need to clarify that we can't touch the programs. All the original programmers are gone and with them their knowledge. The one contract programmer they have is only allowed to make regulatory changes. This has to be done with a process that gets the reports out of the JES2 queue and puts them back in as separate reports. It just need simple "if I see this on a header line, break up the report" logic. I have written this for z/VSE before, I guess I just need to allocate the time to convert the z/VSE code to z/OS. Tony Thigpen Mike Schwab wrote on 8/28/20 5:17 PM: http://www.mabu.org/jcl-reference.pdf OS/390 2.10 from 2000 reference. Same example is on https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieab600/outst.htm //OUT1 OUTPUT DEST=STLNODE.WMSMITH //OUT2 OUTPUT CONTROL=DOUBLE //DSDD SYSOUT=C,OUTPUT=(*.OUT1,*.OUT2) So set one to print, and one to hold, then reference both. On Fri, Aug 28, 2020 at 8:21 AM Tony Thigpen wrote: All, I have an old OS/390 2.10 system that I need to support for a few more years until the customer finishes their off-platform migration. The current project involves removing costly third-party software that is providing minimal returns for a large cost. One of those products is a report archive system, but the only part still being used is the function of 'report splitting' which just sticks the reports back into the JES2 queue as separate reports. While writing something is fun, I don't really have time to write this one as there are other things I need to write first. I don't see anything on the CBT that addresses this, but there may be a small item in a larger bundle that I can't identify from the contents of FILE001. Or, someone may have some basic code they can share so that I don't have to re-invent the wheel on this one. Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
http://www.mabu.org/jcl-reference.pdf OS/390 2.10 from 2000 reference. Same example is on https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieab600/outst.htm //OUT1 OUTPUT DEST=STLNODE.WMSMITH //OUT2 OUTPUT CONTROL=DOUBLE //DSDD SYSOUT=C,OUTPUT=(*.OUT1,*.OUT2) So set one to print, and one to hold, then reference both. On Fri, Aug 28, 2020 at 8:21 AM Tony Thigpen wrote: > > All, > > I have an old OS/390 2.10 system that I need to support for a few more > years until the customer finishes their off-platform migration. > > The current project involves removing costly third-party software that > is providing minimal returns for a large cost. One of those products is > a report archive system, but the only part still being used is the > function of 'report splitting' which just sticks the reports back into > the JES2 queue as separate reports. > > While writing something is fun, I don't really have time to write this > one as there are other things I need to write first. > > I don't see anything on the CBT that addresses this, but there may be a > small item in a larger bundle that I can't identify from the contents of > FILE001. Or, someone may have some basic code they can share so that I > don't have to re-invent the wheel on this one. > > > Tony Thigpen > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
Look into file 527 on the CBT tape. There is a callable sub-program that allows a COBOL (or any other language) program to change a f SYSOUT file characteristics. Close the report file in the program, change what you want changed, then open the report file. This creates a separate SYSOUT each time. There may be example programs in file 529 to use this sub-progarm. Matthew On Fri, 28 Aug 2020 10:46:47 -0700, Ed Jaffe wrote: >On 8/28/2020 6:20 AM, Tony Thigpen wrote: >> >> The current project involves removing costly third-party software that >> is providing minimal returns for a large cost. One of those products >> is a report archive system, but the only part still being used is the >> function of 'report splitting' which just sticks the reports back into >> the JES2 queue as separate reports. > > >Unless you need to split on a "special" boundary, I would just use >SEGMENT= on the SYSOUT DD statement. > > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
On 8/28/2020 6:20 AM, Tony Thigpen wrote: The current project involves removing costly third-party software that is providing minimal returns for a large cost. One of those products is a report archive system, but the only part still being used is the function of 'report splitting' which just sticks the reports back into the JES2 queue as separate reports. Unless you need to split on a "special" boundary, I would just use SEGMENT= on the SYSOUT DD statement. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
Run the report files through their sort product. Depending on how complicated the split criteria is, it might be quite simple to split. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Tony Thigpen > Sent: Friday, August 28, 2020 6:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: report splitting > > All, > > I have an old OS/390 2.10 system that I need to support for a few more > years until the customer finishes their off-platform migration. > > The current project involves removing costly third-party software that > is providing minimal returns for a large cost. One of those products is > a report archive system, but the only part still being used is the > function of 'report splitting' which just sticks the reports back into > the JES2 queue as separate reports. > > While writing something is fun, I don't really have time to write this > one as there are other things I need to write first. > > I don't see anything on the CBT that addresses this, but there may be a > small item in a larger bundle that I can't identify from the contents of > FILE001. Or, someone may have some basic code they can share so that I > don't have to re-invent the wheel on this one. > > > Tony Thigpen > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: report splitting
the only thing I can think of is RMDS, if its still available, you don't need to use the RMDS repository and can be used to split out reports to different recipients -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
report splitting
All, I have an old OS/390 2.10 system that I need to support for a few more years until the customer finishes their off-platform migration. The current project involves removing costly third-party software that is providing minimal returns for a large cost. One of those products is a report archive system, but the only part still being used is the function of 'report splitting' which just sticks the reports back into the JES2 queue as separate reports. While writing something is fun, I don't really have time to write this one as there are other things I need to write first. I don't see anything on the CBT that addresses this, but there may be a small item in a larger bundle that I can't identify from the contents of FILE001. Or, someone may have some basic code they can share so that I don't have to re-invent the wheel on this one. Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
