https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idau100/u1241.htm
That page documents the standard format of the Utility control statements. On Wed, Dec 21, 2016 at 8:51 AM, Paul Gilmartin < [email protected]> wrote: > On Wed, 21 Dec 2016 08:26:14 -0700, Sri h Kolusu wrote: > > > >Seriously? That COLS line was for demonstration purposes to show that both > >the Control cards and Comments are within the first 72 bytes. It is NOT > >part of the control cards nor is it a comment. > > > I was hoping for a way to code a comment. > > >> And I was looking for a form where SYSIN contains no commands, only > >comments. > > > >What is the purpose of this? When you are invoking a program/utility, you > >can pass parameters to the program/utility via a PARM statement or SYSIN. > >In your case you chose NOT to pass any parameters via SYSIN. That brings > >us to the question "what is the purpose of having comments?" > > > Adding identifying information to SYSPRINT, where I'd expect comments to > be listed along with control statements. I needed none of the latter. > > >What is stopping you from coding a COMMENTS dd and you can have all your > >comments in there? > > > ... and in the next job step modding IEBGENER's sysprint to that. > I'm doing that now. But since IEBGENER already has a SYSIN, > I was hoping I could put the comments there and avoid the extra > job step. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
