This MVS 3.8j tidbit hints the OP started coding something on his S JOB, command incorrectly. Perhaps using a new symbolic his JOB proc did not have. As in the earlier post, onmy 1.7 system I can still get it to work without adding this DDNAME=IEFRDER type of statement.
>>>>>>>>>>>>>>>>>> startup procedure contains a line //HASPRDR DD DDNAME=IEFRDER and the warning that is issued just tells you that the DDNAME IEFRDER was not resolved in the JES2 procedure. No need to do anything. Actually, you migth be tempted to fix it by removing the line altogether. But that might not be a very good idea. There is a feature in JCL processing, long since forgotten, which allows to place nearly any JCL onto the IEFRDER statement when needed. How? Very simple. If you enter the command s jes2,,,dsn=SYS1.HASPLIST,DISP=(,CATLG),UNIT=3350,SPACE=(CYL,(1,1)) then the DDNAME IEFRDER will be creted in step IEFPROC of procedure JES2, and the supplied JCL parameters will be associated with the IEFRDER DDNAME. And what do you find in HASPLIST? HASPLIST is useful if JES2 doesn't start because of some error in the JES2 startup deck. In this case HASPLIST contains the listing of the startup parameters, and all the error messages that were issued. This is controlled via the LIST intialization control statement found in SYS1.JES2PARM(JES2PARM) <<<<<<<<<<<<<<<<<<<<<<<<<<<<< ---------------------------------------------------------------------- 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
