A quick way to determine the error is to submit the JCL as a batch
job. If the job fails during syntax checking, it will not matter
whether the data sets are cataloged or whether JES2 is already
running.
//JES2 PROC M=JES2PARM
//IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15)
//HASPLIST DD DDNAME=IEFRDER
//HASPPARM DD DSN=SYS1.CPAC.PARMLIB(&M),DISP=SHR
//PROC00 DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB
// DD DISP=SHR,DSN=SYS1.PROCLIB
//HASPLIST DD DDNAME=IEFRDER
//STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE
// PEND
//DOIT EXEC PROC=JES2
The resulting messages are:
STMT NO. MESSAGE
3 IEFC001I PROCEDURE JES2 WAS EXPANDED USING INSTREAM PROCEDURE
DEFINITION
10 IEF631I NUMBER OF DDNAMES EXCEEDS MAXIMUM IN THE DDNAME FIELD
11 IEF686I DDNAME REFERRED TO ON DDNAME KEYWORD IN PRIOR STEP
WAS NOT RESOLVED
The second message, IEF631I, is the error. This message is not fully
described in the System Messages manual:
"Explanation: The system found the DDNAME parameter within a job step
unresolved in six or more DD statements at one time. There may be no
more than 5 outstanding, unresolved DDNAME parameters in a step at one
time."
The JCL rule that is being violated is documented under the DDNAME
parameter in the MVS JCL Reference, SA22-7597-13, in topic 12.17.2
Subparameter Definition:
"A job step or procedure step can contain up to five outstanding,
unresolved DD parameters in a step at one time. Each DDNAME parameter
must refer to a different DD statement."
The text of message IEF631I, and the description in the System
Messages manual, refer to the first sentence, but the rule that
is being violated in this example is the second sentence.
Larry Stout
On Mon, 29 Mar 2010 10:36:03 -0500, Ramiro
Camposagrado <[email protected]>
wrote:
> Why not start your new JES2 proc on a system that has JES2 already started?
> It should go ro regular conversion and then issue the $HASP426 message.
On Mon, 29 Mar 2010 09:40:01 -0500, Mark
Zelden <[email protected]> wrote (in part):
> But why do you have 2 HASPLIST DDs?
> Lose the second one.
On Mon, 29 Mar 2010 13:15:33 +0000, Rob Scott <[email protected]> wrote:
>Why do you have *two* HASPLIST DD specifications ?
>
>
>Rob Scott
>Developer
>Rocket Software
>275 Grove Street * Newton, MA 02466-2272 * USA
>Tel: +1.617.614.2305
>Email: [email protected]
>Web: www.rocketsoftware.com
>
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Ron Wells
>Sent: 29 March 2010 14:01
>To: [email protected]
>Subject: Re: The hardest JCL ERROR I have met
>
>(2) HASPLIST ??
>STEPLIB s/b after EXEC
>
>
>
>
>From:
>Hu Lei <[email protected]>
>To:
>[email protected]
>Date:
>03/29/2010 07:45 AM
>Subject:
>The hardest JCL ERROR I have met
>Sent by:
>IBM Mainframe Discussion List <[email protected]>
>
>
>
>Hello world!
>
>
>
>I am trying to setup a mini system, and during IPL, I have met JES2 start
error. I am suffer from this error for days, I have do all I can image to
correct the error, but still no result.
>
>It would be great appreciated if any comments!! Thanks in advance.
>
>
>
>The joblog during IPL looks:
>
>IEF403I IEESYSAS - STARTED - TIME=03.47.40
>
>IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED
>
>IEF452I JES2 - JOB NOT RUN - JCL ERROR
>
>And the JES2 proc:
>
>//JES2 PROC M=JES2PARM
>
>//IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15)
>
>//HASPLIST DD DDNAME=IEFRDER
>
>//HASPPARM DD DSN=SYS1.CPAC.PARMLIB(&M),DISP=SHR
>
>//PROC00 DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB
>
>// DD DISP=SHR,DSN=SYS1.PROCLIB
>
>//HASPLIST DD DDNAME=IEFRDER
>
>//STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE
>
>IEFSSNxx
>
> SUBSYS SUBNAME(JES2)
>
> PRIMARY(YES) START(NO)
>
>COMMDxx:
>
>COM='S JES2,PARM='COLD,NOREQ''
>
>
>
>Here is what I have checked:
>
>All the datasets referred in Jes2 proc are cataloged in Master catalog by
using IDCAMS listcat.
>
>SYS1.SHASLNKE has listed in PROGxx, and APFed.
>
>Storage volume has been specified in VATLSTxx.
>
>Both null SMS configuration and none SMS environment have tried.
>
>Both VLF, LLA, DLF, RACF has started.
>
>
>
>From IEF677I, it seems system found some error and used a system default.
>But where is it? Can we got some additional message from other ways?
>
>Thanks for your time.
----------------------------------------------------------------------
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
