Re: JCL to include data
> I don't think SUBMIT * works in REXX as it would in CLIST No; a CLIST operates from the stack and can do things that REXX can't support. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of John McKown Sent: Tuesday, July 9, 2019 7:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL to include data On Mon, Jul 8, 2019 at 2:33 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 8 Jul 2019 14:02:20 -0500, Elardus Engelbrecht wrote: > >... > >??? Please explain that. Do you mean, you want to add the members as an > input into that JCL? Why not just concatenate them using some DD statements? > > ... > >Why not use a [concatenated] DD refering to the source of that data in > that flat file / PDs / members of that PDS? > > > Me, too. But this thread inspired me to RTFM, where I see: > > > https://secure-web.cisco.com/1bX2diunCOX0oboKQRuXDIqwfibyBLGLujz9ZLvUhn_vYzHZ-q2u1ukOba-TGpiivH5b1xQ6Jox92I8a0zCX_8CD_YzhJCiwuKdnU5OAwMv2QLEgunimUgN3eD5vjVqjN7D1p_6zCqTxdAWS2q7FIFKiBBMRdR_SFesVQmHJDDBaRXFA7lBn2hBNiKJ810CO6Gya0Gw31S44yw4ktKg8w8ZAbzeFiVXhgD4l96GwsABRvQdCdDTPeepLo-MG0rrksF_43b436Sgn7RH_qY3vPJOg9sQiFEKoGH17O3NsfBNMvaFeb3DGGvvpig9lMcWwb1sxIBubId-d79YSKOaIsGlYl3puehPm01kR3dS4X9PQR1t42klwHWhi7EENRdRkgeaXG5iZoqUO8vpmnHAjQ1NOkRyDtod5YykaHCxaBXGPLAod21-9ExoQDKdVSwKXN/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.ikjc500%2Fikj2l2_SUBMIT_command_operands.htm > Note [brightly highlighed] > All characters in the job stream are converted to uppercase > before being processed. > > WTF!? Does that mean that if I SUBMIT a job containing: > //SYSUT1 DD * > This is Mixed Case text. > The effect is the same as: > //SYSUT1 DD * > THIS IS MIXED CASE TEXT. > As I read it, the translation to upper case only occurs when you do SUBMIT * to read the JCL from the terminal or when it is embedded in the CLIST (I don't think SUBMIT * works in REXX as it would in CLIST). > > I don't remember it that way, but I confess I can't remember having > tried it. Lately I've submitted only via FTP or copy to INTRDR. But > is a clarification RCF in order? > > I'd advocate RFEs for a > oSUBMIT FROMDDNAME(...) option > oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 > and for JESZ3 far earlier, but lingering in TSO/ISPF submit. > That would be nice, but the likelihood of IBM doing any enhancements to TSO is about as likely as them releasing MVS/XA to the hobbists to use with Hercules. There are two chances: FAT and SLIM. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. -- Larry Wall Maranatha! <>< John McKown -- 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: JCL to include data
On Mon, Jul 8, 2019 at 2:33 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 8 Jul 2019 14:02:20 -0500, Elardus Engelbrecht wrote: > >... > >??? Please explain that. Do you mean, you want to add the members as an > input into that JCL? Why not just concatenate them using some DD statements? > > ... > >Why not use a [concatenated] DD refering to the source of that data in > that flat file / PDs / members of that PDS? > > > Me, too. But this thread inspired me to RTFM, where I see: > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/ikj2l2_SUBMIT_command_operands.htm > Note [brightly highlighed] > All characters in the job stream are converted to uppercase > before being processed. > > WTF!? Does that mean that if I SUBMIT a job containing: > //SYSUT1 DD * > This is Mixed Case text. > The effect is the same as: > //SYSUT1 DD * > THIS IS MIXED CASE TEXT. > As I read it, the translation to upper case only occurs when you do SUBMIT * to read the JCL from the terminal or when it is embedded in the CLIST (I don't think SUBMIT * works in REXX as it would in CLIST). > > I don't remember it that way, but I confess I can't remember having > tried it. Lately I've submitted only via FTP or copy to INTRDR. But > is a clarification RCF in order? > > I'd advocate RFEs for a > oSUBMIT FROMDDNAME(...) option > oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 > and for JESZ3 far earlier, but lingering in TSO/ISPF submit. > That would be nice, but the likelihood of IBM doing any enhancements to TSO is about as likely as them releasing MVS/XA to the hobbists to use with Hercules. There are two chances: FAT and SLIM. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. -- Larry Wall Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
Oh how I got led down a path today. Guy told me a lot of stuff, but not everything. I didn't ask him the right questions, ASSuMEing, he knew what he was doing. He was trying to insert VB records in the JCL, and he was out of space in the PDS. But I think I did learn something from you guys concerning the question I asked as opposed to what the problem actually was. On Mon, Jul 8, 2019 at 3:33 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 8 Jul 2019 14:02:20 -0500, Elardus Engelbrecht wrote: > >... > >??? Please explain that. Do you mean, you want to add the members as an > input into that JCL? Why not just concatenate them using some DD statements? > > ... > >Why not use a [concatenated] DD refering to the source of that data in > that flat file / PDs / members of that PDS? > > > Me, too. But this thread inspired me to RTFM, where I see: > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/ikj2l2_SUBMIT_command_operands.htm > Note [brightly highlighed] > All characters in the job stream are converted to uppercase > before being processed. > > WTF!? Does that mean that if I SUBMIT a job containing: > //SYSUT1 DD * > This is Mixed Case text. > The effect is the same as: > //SYSUT1 DD * > THIS IS MIXED CASE TEXT. > > I don't remember it that way, but I confess I can't remember having > tried it. Lately I've submitted only via FTP or copy to INTRDR. But > is a clarification RCF in order? > > I'd advocate RFEs for a > oSUBMIT FROMDDNAME(...) option > oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 > and for JESZ3 far earlier, but lingering in TSO/ISPF submit. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
On Mon, 8 Jul 2019 14:33:14 -0500, Paul Gilmartin wrote: > ... >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/ikj2l2_SUBMIT_command_operands.htm >Note [brightly highlighed] >All characters in the job stream are converted to uppercase >before being processed. > >WTF!? Does that mean that if I SUBMIT a job containing: >//SYSUT1 DD * >This is Mixed Case text. >The effect is the same as: >//SYSUT1 DD * >THIS IS MIXED CASE TEXT. > I've received an off-list clarification (thanks) that that applies only to "SUBMIT *", as opposed to "SUBMIT dsn". The behavior is yet increasingly oppressively archaic in that "SUBMIT *" precludes reference to, for example UNIX files with mixed case names. Where's ASIS when you need it? >I'd advocate RFEs for a >oSUBMIT FROMDDNAME(...) option >oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 > and for JESZ3 far earlier, but lingering in TSO/ISPF submit. o ASIS in many more places; even global to the TSO session. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
On Mon, 8 Jul 2019 19:42:58 +, Seymour J Metz wrote: >Does the OP need to do SUBMIT? > This feels like a case where the user is throwing his influence around and invoking middle management's support against an "unresponsive" support staff's refusal to accommodate the user's way. >Do you have a business case for removing the brain-dead FB80 restriction in >SUBMIT? > Not specifically, but there must have been one for the much harder task of removing that restriction from JES2. It's a pity that "brain-dead" isn't per se a business case. Putrefaction? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
Does the OP need to do SUBMIT? Do you have a business case for removing the brain-dead FB80 restriction in SUBMIT? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Monday, July 8, 2019 3:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL to include data On Mon, 8 Jul 2019 14:02:20 -0500, Elardus Engelbrecht wrote: >... >??? Please explain that. Do you mean, you want to add the members as an input >into that JCL? Why not just concatenate them using some DD statements? > ... >Why not use a [concatenated] DD refering to the source of that data in that >flat file / PDs / members of that PDS? > Me, too. But this thread inspired me to RTFM, where I see: https://secure-web.cisco.com/1GlMdtzvEKP3x9RqXA8s_aHoLb9YfYKrWBmjvTHgf5RzAfVFTkz1Z-ed3kk0u3oc93-HJYBc0K9WpdRW16K4JQUWKaZq9XGUQGbbz5wRMR-O-uW0ZdvdLnKeFRToho8EBEQZVpQGhWRr35wBOtCciDnwvrbGf4S_yhMV7GD19EwgA43ktd7MzLCvkLLtxU0-xhfptTaA0B-jH-p4ProHXmVTlWmIyrMpz6VJaih3830obRNcAuO0VfJetpvumiXVj_f8O9YCpnvFMBtfYNjAtYeqvHgNWmJjlwcUcZKi5AoISe4WgrKlprQPCsSajzZyLHNdT6euHZisQFZntYdch6HvmK8kspS6O1fpGaNBEkJ0htZQRZofg_zo92ctneFZd/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.ikjc500%2Fikj2l2_SUBMIT_command_operands.htm Note [brightly highlighed] All characters in the job stream are converted to uppercase before being processed. WTF!? Does that mean that if I SUBMIT a job containing: //SYSUT1 DD * This is Mixed Case text. The effect is the same as: //SYSUT1 DD * THIS IS MIXED CASE TEXT. I don't remember it that way, but I confess I can't remember having tried it. Lately I've submitted only via FTP or copy to INTRDR. But is a clarification RCF in order? I'd advocate RFEs for a oSUBMIT FROMDDNAME(...) option oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 and for JESZ3 far earlier, but lingering in TSO/ISPF submit. -- 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: JCL to include data
Separate the JCL into a prefix member and a suffix member, then write a job to copy a concatenation of the pieces to the Internal Reader. But if you don't need to do symbol substitution then you can just change your job to use DSN= instead of * or DATA. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Mark Pace Sent: Monday, July 8, 2019 2:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JCL to include data Working with a user that needs include a bunch of data in a JCL. The data is too large to copy into the JCL. During the copy he gets several E37s and then ends with a B37. It appears to me that he runs out of space in that PDS. The data that needs to be included is a flat file and not a PDS, which seems to rule out the // INCULDE statement. Any suggestions would be appreciated. -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- 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: JCL to include data
On Mon, 8 Jul 2019 14:02:20 -0500, Elardus Engelbrecht wrote: >... >??? Please explain that. Do you mean, you want to add the members as an input >into that JCL? Why not just concatenate them using some DD statements? > ... >Why not use a [concatenated] DD refering to the source of that data in that >flat file / PDs / members of that PDS? > Me, too. But this thread inspired me to RTFM, where I see: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/ikj2l2_SUBMIT_command_operands.htm Note [brightly highlighed] All characters in the job stream are converted to uppercase before being processed. WTF!? Does that mean that if I SUBMIT a job containing: //SYSUT1 DD * This is Mixed Case text. The effect is the same as: //SYSUT1 DD * THIS IS MIXED CASE TEXT. I don't remember it that way, but I confess I can't remember having tried it. Lately I've submitted only via FTP or copy to INTRDR. But is a clarification RCF in order? I'd advocate RFEs for a oSUBMIT FROMDDNAME(...) option oRemoving the Fixed-80 restriction, relaxed for JES2 circa z/OS 1.5 and for JESZ3 far earlier, but lingering in TSO/ISPF submit. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
Mark Pace wrote: >Working with a user that needs include a bunch of data in a JCL. The data is >too large to copy into the JCL. During the copy he gets several E37s and then >ends with a B37. How is the JCL generated in the first place? Do you build up a large, extra large, extreme large dataset where you throw in the JCL and that "bunch of data" into it before giving it to JES2 internal reader? Do you get the x37 abends before you or them are able to submit it in the first place? Please post an example of that JCL and some sample of that "bunch of data". Also, please post all the x37 abend messages. > It appears to me that he runs out of space in that PDS. ??? Please explain that. Do you mean, you want to add the members as an input into that JCL? Why not just concatenate them using some DD statements? >The data that needs to be included is a flat file and not a PDS, which seems >to rule out the // INCULDE statement. Why not use a [concatenated] DD refering to the source of that data in that flat file / PDs / members of that PDS? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL to include data
On Mon, 8 Jul 2019 14:49:00 -0400, Mark Pace wrote: >Working with a user that needs include a bunch of data in a JCL. The data >is too large to copy into the JCL. During the copy he gets several E37s and >then ends with a B37. It appears to me that he runs out of space in that >PDS. > >The data that needs to be included is a flat file and not a PDS, which >seems to rule out the // INCULDE statement. > >Any suggestions would be appreciated. > "data" but not JCL statements? I'm mystified. Is this something that can't be referenced in a //SYSUT1 DD DSN=... statement? How large is it? How many lines? What facility is he using to "copy"? Can he allocate a larger target PDS? Can he copy directly to INTRDR? Other relevant facts? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
JCL to include data
Working with a user that needs include a bunch of data in a JCL. The data is too large to copy into the JCL. During the copy he gets several E37s and then ends with a B37. It appears to me that he runs out of space in that PDS. The data that needs to be included is a flat file and not a PDS, which seems to rule out the // INCULDE statement. Any suggestions would be appreciated. -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
