Re: [External] Re: Comments in IDCAMS statements
Hi Steve, What I find interesting is that apparently the comment close string "*/" is optional. If you don't include it, it defaults to "this is a comment until the end of the logical line". Thus if you have a hyphen at the end of the line even though it is after a "/* IDCAMS recognizes it as a continuation character even though it is officially inside the comment, but if there's a hyphen with other characters following it, the hyphen is counted as part of the comment. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Wednesday, May 30, 2018 12:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: Comments in IDCAMS statements Ah... continuation character... that's what I forgot. I'm not sure this scheme is entirely sensible, nor is it documented correctly, but at least the mystery is resolved. sas On Wed, May 30, 2018 at 12:27 PM, Pommier, Rex wrote: > You are correct. > > Simple job: > > //STEP1 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > /* THIS IS A COMMENT */ > /* SO IS THIS */ > /* > //STEP2 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > /* THIS IS A COMMENT - > SO IS THIS */ > /* > > Output: > > IDCAMS SYSTEM SERVICES > > /* THIS IS A COMMENT */ > /* SO IS THIS */ > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 > IDCAMS SYSTEM SERVICES > > /* THIS IS A COMMENT - > SO IS THIS */ > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 > > No complaints about a multi-line comment. > > Rex > > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mike Wawiorko > Sent: Wednesday, May 30, 2018 9:56 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] Re: Comments in IDCAMS statements > > Isn't this more lack of the IDCAMS continuation character ' - ' or does my > memory fail me? > > Mike Wawiorko > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Comments in IDCAMS statements
Ah... continuation character... that's what I forgot. I'm not sure this scheme is entirely sensible, nor is it documented correctly, but at least the mystery is resolved. sas On Wed, May 30, 2018 at 12:27 PM, Pommier, Rex wrote: > You are correct. > > Simple job: > > //STEP1 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > /* THIS IS A COMMENT */ > /* SO IS THIS */ > /* > //STEP2 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > /* THIS IS A COMMENT - > SO IS THIS */ > /* > > Output: > > IDCAMS SYSTEM SERVICES > > /* THIS IS A COMMENT */ > /* SO IS THIS */ > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 > IDCAMS SYSTEM SERVICES > > /* THIS IS A COMMENT - > SO IS THIS */ > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 > > No complaints about a multi-line comment. > > Rex > > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mike Wawiorko > Sent: Wednesday, May 30, 2018 9:56 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] Re: Comments in IDCAMS statements > > Isn't this more lack of the IDCAMS continuation character ' - ' or does my > memory fail me? > > Mike Wawiorko > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Comments in IDCAMS statements
Steve Smith wrote: >I thoguht I understood how to run AMS. Either I don't, or something strange >is going on: [ ... snipped ... ] Please post the full IDCANS statements as well the JCL you used. Then the IBM-MAIN members can then see what you're trying to use. 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: Comments in IDCAMS statements
You are correct. Simple job: //STEP1 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * /* THIS IS A COMMENT */ /* SO IS THIS */ /* //STEP2 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * /* THIS IS A COMMENT - SO IS THIS */ /* Output: IDCAMS SYSTEM SERVICES /* THIS IS A COMMENT */ /* SO IS THIS */ IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 IDCAMS SYSTEM SERVICES /* THIS IS A COMMENT - SO IS THIS */ IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 No complaints about a multi-line comment. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Wawiorko Sent: Wednesday, May 30, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: Comments in IDCAMS statements Isn't this more lack of the IDCAMS continuation character ' - ' or does my memory fail me? Mike Wawiorko -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: 30 May 2018 15:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Comments in IDCAMS statements This mail originated from outside our organisation - 01a0403c5dc1-dmarc-requ...@listserv.ua.edu From the book: Commands can begin at, or to the right of, the left margin. For batch processing jobs, the default margins are 2 and 72. Commands are separated from their parameters by one or more separators (blanks,commas, or comments). For some parameters, parentheses are used as separators. Comments are strings of characters surrounded by /* and */. Comments can contain any characters except */. I haven’t tested, but it looks like multi-line comments are not supported with only 1 opening and closing /* */? _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Wednesday, May 30, 2018 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Comments in IDCAMS statements **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I thoguht I understood how to run AMS. Either I don't, or something strange is going on: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 BELOW TO ALLOCATE THERE. 11090078 IDC3219I VERB NAME 'BELOW' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 ALTERNATIVE IS TO DELETE THE VOL(EAVNS0) LINES . 11100078 IDC3219I VERB NAME 'ALTERNATIVE' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 */ 0078 IDC3219I VERB NAME '*/' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 Even more baffling, this worked: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 /*BELOW TO ALLOCATE THERE. 11090079 11100079 /*OTHERWISE DELETE THE VOL(EAVNS0) LINES. 0079 11120079 Did they start using the TSO CLIST parser? -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Comments in IDCAMS statements
Isn't this more lack of the IDCAMS continuation character ' - ' or does my memory fail me? Mike Wawiorko -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: 30 May 2018 15:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Comments in IDCAMS statements This mail originated from outside our organisation - 01a0403c5dc1-dmarc-requ...@listserv.ua.edu From the book: Commands can begin at, or to the right of, the left margin. For batch processing jobs, the default margins are 2 and 72. Commands are separated from their parameters by one or more separators (blanks,commas, or comments). For some parameters, parentheses are used as separators. Comments are strings of characters surrounded by /* and */. Comments can contain any characters except */. I haven’t tested, but it looks like multi-line comments are not supported with only 1 opening and closing /* */? _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Wednesday, May 30, 2018 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Comments in IDCAMS statements **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I thoguht I understood how to run AMS. Either I don't, or something strange is going on: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 BELOW TO ALLOCATE THERE. 11090078 IDC3219I VERB NAME 'BELOW' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 ALTERNATIVE IS TO DELETE THE VOL(EAVNS0) LINES . 11100078 IDC3219I VERB NAME 'ALTERNATIVE' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 */ 0078 IDC3219I VERB NAME '*/' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 Even more baffling, this worked: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 /*BELOW TO ALLOCATE THERE. 11090079 11100079 /*OTHERWISE DELETE THE VOL(EAVNS0) LINES. 0079 11120079 Did they start using the TSO CLIST parser? -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Services Limited provides support and administrative services across Barclays group. Barclays Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation
Re: Comments in IDCAMS statements
You are thinking REXX comments, which allow multi-line comments. IDCAMS only supports single line comments. Tony Thigpen Steve Smith wrote on 05/30/2018 10:24 AM: I thoguht I understood how to run AMS. Either I don't, or something strange is going on: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 BELOW TO ALLOCATE THERE. 11090078 IDC3219I VERB NAME 'BELOW' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 ALTERNATIVE IS TO DELETE THE VOL(EAVNS0) LINES . 11100078 IDC3219I VERB NAME 'ALTERNATIVE' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 */ 0078 IDC3219I VERB NAME '*/' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 Even more baffling, this worked: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 /*BELOW TO ALLOCATE THERE. 11090079 11100079 /*OTHERWISE DELETE THE VOL(EAVNS0) LINES. 0079 11120079 Did they start using the TSO CLIST parser? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Comments in IDCAMS statements
From the book: Commands can begin at, or to the right of, the left margin. For batch processing jobs, the default margins are 2 and 72. Commands are separated from their parameters by one or more separators (blanks,commas, or comments). For some parameters, parentheses are used as separators. Comments are strings of characters surrounded by /* and */. Comments can contain any characters except */. I haven’t tested, but it looks like multi-line comments are not supported with only 1 opening and closing /* */? _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Wednesday, May 30, 2018 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Comments in IDCAMS statements **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I thoguht I understood how to run AMS. Either I don't, or something strange is going on: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 BELOW TO ALLOCATE THERE. 11090078 IDC3219I VERB NAME 'BELOW' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 ALTERNATIVE IS TO DELETE THE VOL(EAVNS0) LINES . 11100078 IDC3219I VERB NAME 'ALTERNATIVE' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 */ 0078 IDC3219I VERB NAME '*/' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 Even more baffling, this worked: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 /*BELOW TO ALLOCATE THERE. 11090079 11100079 /*OTHERWISE DELETE THE VOL(EAVNS0) LINES. 0079 11120079 Did they start using the TSO CLIST parser? -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Comments in IDCAMS statements
I thoguht I understood how to run AMS. Either I don't, or something strange is going on: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 BELOW TO ALLOCATE THERE. 11090078 IDC3219I VERB NAME 'BELOW' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 ALTERNATIVE IS TO DELETE THE VOL(EAVNS0) LINES . 11100078 IDC3219I VERB NAME 'ALTERNATIVE' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 */ 0078 IDC3219I VERB NAME '*/' UNKNOWN IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12 Even more baffling, this worked: /* N.B.: EAVNS0 IS NON-VSAM, SO DELETE DATACLAS AND ACCOUNT 11080078 /*BELOW TO ALLOCATE THERE. 11090079 11100079 /*OTHERWISE DELETE THE VOL(EAVNS0) LINES. 0079 11120079 Did they start using the TSO CLIST parser? -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
