My preference is to always code a HASPPARM dd statement. That way you do not get a misleading IEC130I HASPPARM DD STATEMENT MISSING
message which could distract from the true issue. Also provides better documentation in JES2 where the member is coming from. Defaults are fine, unless you do not know the rules. Sysprogs of the future may not understand how JES2 gets its init deck. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Vince Getgood > Sent: Wednesday, August 03, 2016 6:22 AM > To: [email protected] > Subject: Re: JES2 can't find customised start-up parameters > > Thanks for your help everyone. > > It was indeed the parenthesis. Once I replied using quotes instead of > brackets, JES2 started fine. > > Lizette, no need for a HASPPARM DD statement in the JES2 PROC. There's a > SHARE presentation around that has a JES2 procedure even more minimalistic > than mine! > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
