On 30 Nov 2005 22:54:40 -0800, [EMAIL PROTECTED] (Hunkeler Peter , KRDO 4) wrote:
>Be careful. //* may be ambiguous in a JES3 environment. >Most of the JES3 control statements start with //*xyz. > >JCL comment statements should start with //*b (b=blank) >to avoid such ambiguity (this applies to JES3 environments >only, of course). > >There are tools that scan JCL and that have their own use >//* statements. In JCL and in CoBOL, I don't stop with one "*". I started off doing this because my CoBOL pre-compiler put in one '*' when it put in its code, so I wanted to make mine look different. I expanded that to JCL. //OUTFILE DD DSN=&MYFILE..NEW, // UNIT=TAPE, //**** UNIT=DEVEDISK,SPACE=(CYL,(5,5),RLSE), // RECFM=FB,LRECL=430,DSORG=PS, // DISP=(NEW,CATLG,DELETE) The exception is block comments such as: //******************************************************************/ //* THIS VERSION OF TEIF$ IS SPLIT UP. AFTER RUNNING IN UPDATE */ //* RUN $TAUM */ //* */ //******************************************************************/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
