Re: JES2 can't find customised start-up parameters

2016-08-03 Thread Tom Marchant 
On Wed, 3 Aug 2016 08:10:25 -0700, Lizette Koehler wrote:

>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.  

OTOH, that means that you do not use the system PARMLIB concatenation for your 
JES2 parameters. 

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-03 Thread John McKown 
On Wed, Aug 3, 2016 at 10:10 AM, Lizette Koehler 
wrote:

> My preference is to always code a HASPPARM dd statement.  That way you do
> not get a misleading
> IEC130I HASPPARM DD STATEMENT MISSING
>
> ​m​
> essage 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.
>

I was going to comment on the truth of this. But I got so sarcastic that
even I got offended.


> Lizette
>
>
>
-- 
Klein bottle for rent -- inquire within.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-03 Thread Lizette Koehler 
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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vince Getgood
> Sent: Wednesday, August 03, 2016 6:22 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-03 Thread Vince Getgood 
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-03 Thread Lucas Rosalen 
I think Andy nailed it.  Wrong parenthesis in start command.

Lucas

On Aug 2, 2016 21:01, "Lizette Koehler"  wrote:

> The sample JES2 Start up proc contains a HASPPARM DD Statement.
>
> I do not see one in your expanded JCL.
>
> //JES2 PROC N=SYS1,L=SHASLNKE,
> //  M=JES2PARM,PN=SYS1,PL=PARMLIB,U=
> //  PROC00='SYS1.PROCLIB',PROC01='SYS1.PROCLIB'
> //IEFPROC  EXEC PGM=HASJES20,TIME=1440,PARM=(WARM,NOREQ)
> //HASPLIST  *  DD DDNAME=IEFRDER
> //*
> //HASPPARM DD UNIT=,DSN=(),DISP=SHR
> //*
>
>
> Lizette
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-02 Thread Lizette Koehler 
The sample JES2 Start up proc contains a HASPPARM DD Statement.

I do not see one in your expanded JCL.

//JES2 PROC N=SYS1,L=SHASLNKE,
//  M=JES2PARM,PN=SYS1,PL=PARMLIB,U=
//  PROC00='SYS1.PROCLIB',PROC01='SYS1.PROCLIB'
//IEFPROC  EXEC PGM=HASJES20,TIME=1440,PARM=(WARM,NOREQ)
//HASPLIST  *  DD DDNAME=IEFRDER
//*
//HASPPARM DD UNIT=,DSN=(),DISP=SHR
//*


Lizette

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-02 Thread Andy Higgins 
On Tue, 2 Aug 2016 09:46:19 -0500, Vince Getgood  wrote:

[snip]

>
>In the SYSLOG, for my failed start of JES, I can see the following: -
>
>S JES2,SUB=MSTR,M=JES2PRSP,START=(COLD,FORMAT,NOREQ) 
>IEF196I 1 //JES2 JOB MSGLEVEL=1  
>IEF196I 2 //STARTING EXEC JES2,M=JES2PRSP,START=(COLD,FORMAT,
>IEF196I NOREQ)   
>IEF196I  STMT NO. MESSAGE
>IEF196I 2 IEFC001I PROCEDURE JES2 WAS EXPANDED USING SYSTEM  
>IEF196I LIBRARY SYS1.PROCLIB 
>IEF196I 3 XXJES2PROC M=JES2PARM, 
>IEF196I   XX START='WARM,NOREQ'  
>IEF196I 4 XXIEFPROC  EXEC PGM=HASJES20,
>IEF196I   XXPARM=',MEMBER=',   
>IEF196I   XXDPRTY=(15,15),TIME=1440,PERFORM=9  
>IEF196I   IEFC653I SUBSTITUTION JCL - PGM=HASJES20,PARM='(COLD,
>IEF196I FORMAT,NOREQ),MEMBER=JES2PRSP',DPRTY=(15,15),TIME=1440,

[snip]

I think the problem is the parentheses in 
PARM='(COLD,FORMAT,NOREQ),MEMBER=JES2PRSP'.  
Try  JES2,SUB=MSTR,M=JES2PRSP,START='COLD,FORMAT,NOREQ'

hth
Andy


>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 can't find customised start-up parameters

2016-08-02 Thread Lizette Koehler 
Do you have a HASPPARM coded in your currently JES2 Startup JCL?

IEC130I HASPPARM DD STATEMENT MISSING  

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Burrell, C. Todd (CDC/OCOO/OCIO/ITSO) (CTR)
> Sent: Tuesday, August 02, 2016 8:13 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2 can't find customised start-up parameters
> 
> It is acting like it is not using the MEMBER parm - and falling down to
> through the default list?   Here's the order:
> 
> MEMBER= if specified
> HASPPARM= if specified
> default HASPPARM=HASPPARM if DD can be opened
> default MEMBER=HASjesx member of the default PARMLIB concatenation
> 
> So it looks like this is falling down to the last option and it is looking for
> HASJES2.   Strange issue - but it probably is some sort of weird typo
> somewhere, although I don't see anything wrong anywhere in what you sent?  And
> your output seems to indicate that it is honoring the MEMBER parameter you
> sent?
> 
> Keep us posted - I want to know what the resolution is to this head-scratcher.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vince Getgood
> Sent: Tuesday, August 02, 2016 10:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2 can't find customised start-up parameters
> 
> Hi all,
> I've hit an issue with our one-pack rescue system that has me really puzzled.
> 
> I should say in advance that we've re-built and re-ipl'd this system many
> times this year, all without issue, and apologise for any layout issues.
> 
> I re-built the one-pack today.  We use the same JCL to build our one-pack
> system - this hasn't changed in months.
> 
> I have the following JES2 procedure in my SYS1.PROCLIB: -
> 
> //JES2PROC M=JES2PARM,
> // START='WARM,NOREQ'
> //IEFPROC  EXEC PGM=HASJES20,
> //PARM=',MEMBER=',
> //DPRTY=(15,15),TIME=1440,PERFORM=9
> //HASPLIST DD DDNAME=IEFRDER
> 
> This hasn't changed in years, and is used on our "production" systems.
> 
> When I start JES2, I issue this command: -
> 
> S JES2,M=JES2PRSP,START=(COLD,FORMAT,NOREQ)
> 
> This hasn't changed in all the time I've been here.  Member JES2PRSP is in
> SYS1.PARMLIB.
> 
> So having set the scene, onto the problem.
> 
> On Start-up, JES issues the following messages: -
> 
>  IEC130I HASPPARM DD STATEMENT MISSING
>  IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED - MEMBER
>  HASJES2 NOT FOUND.
>  IEF196I IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED -
>  IEF196I MEMBER HASJES2 NOT FOUND.
> *£HASP450 OPEN FAILED FOR JES2 PARAMETER LIBRARY - MEMBER HASJES2
> *0001 £HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR 'N' TO TERMINATE
> 
> We do NOT have a HASJES2 member in the parmlib concatenation, but why is it
> even looking for it?
> Why is it looking for HASPPARM?
> 
> According to what I have read, because we've coded the initialisation
> parameter "MEMBER=xx", JES should look for it's start up parameters (in
> this case JES2PRSP) in the logical parmlib.
> 
> Our MSTJCLxx for the one-pack system looks like this: -
> 
> //MSTJCL00 JOB MSGLEVEL=(1,1),TIME=NOLIMIT
> // EXEC PGM=IEEMB860,DPRTY=(15,15)
> //STCINRDR DD SYSOUT=(A,INTRDR)
> //TSOINRDR DD SYSOUT=(A,INTRDR)
> //IEFPDSI  DD DSN=SYS1.PROCLIB,DISP=SHR
> // DD DSN=SYS1.CPAC.PROCLIB,DISP=SHR
> // DD DSN=SYS1.IBM.PROCLIB,DISP=SHR
> //SYSUADS  DD DSN=SYS1.UADS,DISP=SHR
> //SYSLBC   DD DSN=SYS1.BRODCAST,DISP=SHR
> 
> This hasn't changed in a year.
> 
> If I do a D PARMLIB on the one-pack system, I get: -
> 
> PARMLIB DATA SETS SPECIFIED
> AT IPL
> ENTRY  FLAGS  VOLUME  DATA SET
>   1  DZD1PAK  SYS1.PARMLIB
>   2  SZD1PAK  SYS1.IBM.PARMLIB
> 
> All SYS1.xxx datasets are catalogued in the master catalog on the one-pack
> system.
> 
> As I have access to the one-pack DASD from other systems, I added a HASPPARM
> statement to the JES2 procedure (taking a back-up first).  The HASPPARM points
> to SYS1.PARMLIB(JES2PRSP).  With this added, JES2 starts normally.
> 
> In the SYSLOG, for my failed start of JES, I can see the following: -
> 
> S JES2,SUB=MSTR,M=JES2PRSP,START=(COLD,FORMAT,NOREQ)
> IEF196I 1 //JES2 JOB MSGLEVEL=1
> IEF196I 2 //STARTING EXEC JES2,M=JES2PRSP,START=(COLD,FORMAT,
> IEF196I NOREQ)
> IEF196I  STMT NO. MESSAGE
> IEF196I 2 IEFC001I PROCEDURE JES2 WAS EXPANDED USING SYSTEM
> IEF196I LIBRARY SYS1.PROCLIB
> IEF196I 3 XXJES2PROC M=JES2PARM,
> IEF196I

Re: JES2 can't find customised start-up parameters

2016-08-02 Thread Burrell, C. Todd (CDC/OCOO/OCIO/ITSO) (CTR) 
It is acting like it is not using the MEMBER parm - and falling down to through 
the default list?   Here's the order:

MEMBER= if specified
HASPPARM= if specified
default HASPPARM=HASPPARM if DD can be opened
default MEMBER=HASjesx member of the default PARMLIB concatenation

So it looks like this is falling down to the last option and it is looking for 
HASJES2.   Strange issue - but it probably is some sort of weird typo 
somewhere, although I don't see anything wrong anywhere in what you sent?  And 
your output seems to indicate that it is honoring the MEMBER parameter you 
sent? 

Keep us posted - I want to know what the resolution is to this head-scratcher.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vince Getgood
Sent: Tuesday, August 02, 2016 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2 can't find customised start-up parameters

Hi all,
I've hit an issue with our one-pack rescue system that has me really puzzled.  

I should say in advance that we've re-built and re-ipl'd this system many times 
this year, all without issue, and apologise for any layout issues.

I re-built the one-pack today.  We use the same JCL to build our one-pack 
system - this hasn't changed in months.

I have the following JES2 procedure in my SYS1.PROCLIB: -

//JES2PROC M=JES2PARM, 
// START='WARM,NOREQ'  
//IEFPROC  EXEC PGM=HASJES20,  
//PARM=',MEMBER=', 
//DPRTY=(15,15),TIME=1440,PERFORM=9
//HASPLIST DD DDNAME=IEFRDER   

This hasn't changed in years, and is used on our "production" systems.   

When I start JES2, I issue this command: -

S JES2,M=JES2PRSP,START=(COLD,FORMAT,NOREQ)

This hasn't changed in all the time I've been here.  Member JES2PRSP is in 
SYS1.PARMLIB.

So having set the scene, onto the problem.

On Start-up, JES issues the following messages: -

 IEC130I HASPPARM DD STATEMENT MISSING
 IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED - MEMBER 
 HASJES2 NOT FOUND.
 IEF196I IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED -
 IEF196I MEMBER HASJES2 NOT FOUND. 
*£HASP450 OPEN FAILED FOR JES2 PARAMETER LIBRARY - MEMBER HASJES2  
*0001 £HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR 'N' TO TERMINATE

We do NOT have a HASJES2 member in the parmlib concatenation, but why is it 
even looking for it?  
Why is it looking for HASPPARM?

According to what I have read, because we've coded the initialisation parameter 
"MEMBER=xx", JES should look for it's start up parameters (in this case 
JES2PRSP) in the logical parmlib.

Our MSTJCLxx for the one-pack system looks like this: -

//MSTJCL00 JOB MSGLEVEL=(1,1),TIME=NOLIMIT  
// EXEC PGM=IEEMB860,DPRTY=(15,15)  
//STCINRDR DD SYSOUT=(A,INTRDR) 
//TSOINRDR DD SYSOUT=(A,INTRDR) 
//IEFPDSI  DD DSN=SYS1.PROCLIB,DISP=SHR 
// DD DSN=SYS1.CPAC.PROCLIB,DISP=SHR
// DD DSN=SYS1.IBM.PROCLIB,DISP=SHR 
//SYSUADS  DD DSN=SYS1.UADS,DISP=SHR
//SYSLBC   DD DSN=SYS1.BRODCAST,DISP=SHR

This hasn't changed in a year.

If I do a D PARMLIB on the one-pack system, I get: -

PARMLIB DATA SETS SPECIFIED   
AT IPL
ENTRY  FLAGS  VOLUME  DATA SET
  1  DZD1PAK  SYS1.PARMLIB
  2  SZD1PAK  SYS1.IBM.PARMLIB

All SYS1.xxx datasets are catalogued in the master catalog on the one-pack 
system.

As I have access to the one-pack DASD from other systems, I added a HASPPARM 
statement to the JES2 procedure (taking a back-up first).  The HASPPARM points 
to SYS1.PARMLIB(JES2PRSP).  With this added, JES2 starts normally.

In the SYSLOG, for my failed start of JES, I can see the following: -

S JES2,SUB=MSTR,M=JES2PRSP,START=(COLD,FORMAT,NOREQ) 
IEF196I 1 //JES2 JOB MSGLEVEL=1  
IEF196I 2 //STARTING EXEC JES2,M=JES2PRSP,START=(COLD,FORMAT,
IEF196I NOREQ)   
IEF196I  STMT NO. MESSAGE
IEF196I 2 IEFC001I PROCEDURE JES2 WAS EXPANDED USING SYSTEM  
IEF196I LIBRARY SYS1.PROCLIB 
IEF196I 3 XXJES2PROC M=JES2PARM, 
IEF196I   XX START='WARM,NOREQ'  
IEF196I 4 XXIEFPROC  EXEC PGM=HASJES20,
IEF196I   XXPARM=',MEMBER=',   
IEF196I   XXDPRTY=(15,15),TIME=1440,PERFORM=9  
IEF196I   IEFC653I SUBSTITUTION JCL - PGM=HASJES20,PARM='(COLD,
IEF196I FORMAT,NOREQ),MEMBER=JES2PRSP',DPRTY=(15,15),TIME=1440,
IEF196I   PERFORM=9
IEF196I

JES2 can't find customised start-up parameters

2016-08-02 Thread Vince Getgood 
Hi all,
I've hit an issue with our one-pack rescue system that has me really puzzled.  

I should say in advance that we've re-built and re-ipl'd this system many times 
this year, all without issue, and apologise for any layout issues.

I re-built the one-pack today.  We use the same JCL to build our one-pack 
system - this hasn't changed in months.

I have the following JES2 procedure in my SYS1.PROCLIB: -

//JES2PROC M=JES2PARM, 
// START='WARM,NOREQ'  
//IEFPROC  EXEC PGM=HASJES20,  
//PARM=',MEMBER=', 
//DPRTY=(15,15),TIME=1440,PERFORM=9
//HASPLIST DD DDNAME=IEFRDER   

This hasn't changed in years, and is used on our "production" systems.   

When I start JES2, I issue this command: -

S JES2,M=JES2PRSP,START=(COLD,FORMAT,NOREQ)

This hasn't changed in all the time I've been here.  Member JES2PRSP is in 
SYS1.PARMLIB.

So having set the scene, onto the problem.

On Start-up, JES issues the following messages: -

 IEC130I HASPPARM DD STATEMENT MISSING
 IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED - MEMBER 
 HASJES2 NOT FOUND.
 IEF196I IEF764I JES2 JES2 LPARMDD SXITLPRMLB PARMLIB READ FAILED -
 IEF196I MEMBER HASJES2 NOT FOUND. 
*£HASP450 OPEN FAILED FOR JES2 PARAMETER LIBRARY - MEMBER HASJES2  
*0001 £HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR 'N' TO TERMINATE

We do NOT have a HASJES2 member in the parmlib concatenation, but why is it 
even looking for it?  
Why is it looking for HASPPARM?

According to what I have read, because we've coded the initialisation parameter 
"MEMBER=xx", JES should look for it's start up parameters (in this case 
JES2PRSP) in the logical parmlib.

Our MSTJCLxx for the one-pack system looks like this: -

//MSTJCL00 JOB MSGLEVEL=(1,1),TIME=NOLIMIT  
// EXEC PGM=IEEMB860,DPRTY=(15,15)  
//STCINRDR DD SYSOUT=(A,INTRDR) 
//TSOINRDR DD SYSOUT=(A,INTRDR) 
//IEFPDSI  DD DSN=SYS1.PROCLIB,DISP=SHR 
// DD DSN=SYS1.CPAC.PROCLIB,DISP=SHR
// DD DSN=SYS1.IBM.PROCLIB,DISP=SHR 
//SYSUADS  DD DSN=SYS1.UADS,DISP=SHR
//SYSLBC   DD DSN=SYS1.BRODCAST,DISP=SHR

This hasn't changed in a year.

If I do a D PARMLIB on the one-pack system, I get: -

PARMLIB DATA SETS SPECIFIED   
AT IPL
ENTRY  FLAGS  VOLUME  DATA SET
  1  DZD1PAK  SYS1.PARMLIB
  2  SZD1PAK  SYS1.IBM.PARMLIB

All SYS1.xxx datasets are catalogued in the master catalog on the one-pack 
system.

As I have access to the one-pack DASD from other systems, I added a HASPPARM 
statement to the JES2 procedure (taking a back-up first).  The HASPPARM points 
to SYS1.PARMLIB(JES2PRSP).  With this added, JES2 starts normally.

In the SYSLOG, for my failed start of JES, I can see the following: -

S JES2,SUB=MSTR,M=JES2PRSP,START=(COLD,FORMAT,NOREQ) 
IEF196I 1 //JES2 JOB MSGLEVEL=1  
IEF196I 2 //STARTING EXEC JES2,M=JES2PRSP,START=(COLD,FORMAT,
IEF196I NOREQ)   
IEF196I  STMT NO. MESSAGE
IEF196I 2 IEFC001I PROCEDURE JES2 WAS EXPANDED USING SYSTEM  
IEF196I LIBRARY SYS1.PROCLIB 
IEF196I 3 XXJES2PROC M=JES2PARM, 
IEF196I   XX START='WARM,NOREQ'  
IEF196I 4 XXIEFPROC  EXEC PGM=HASJES20,
IEF196I   XXPARM=',MEMBER=',   
IEF196I   XXDPRTY=(15,15),TIME=1440,PERFORM=9  
IEF196I   IEFC653I SUBSTITUTION JCL - PGM=HASJES20,PARM='(COLD,
IEF196I FORMAT,NOREQ),MEMBER=JES2PRSP',DPRTY=(15,15),TIME=1440,
IEF196I   PERFORM=9
IEF196I 5 XXHASPLIST DD DDNAME=IEFRDER 
IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED 
IEF196I 5 IEF686I DDNAME REFERRED TO ON DDNAME KEYWORD IN PRIOR
IEF196I STEP WAS NOT RESOLVED  
IEF695I START JES2 WITH JOBNAME JES2 IS ASSIGNED TO USER START1
IEF403I JES2 - STARTED - TIME=13.47.42 
IEF196I IEF236I ALLOC. FOR JES2 JES2   
IEF196I IEF237I DMY  ALLOCATED TO HASPLIST 
IEC130I HASPPARM DD STATEMENT MISSING  
IEF196I IEC130I HASPPARM DD STATEMENT MISSING  
IEF196I IEF285I   SYS1.PARMLIB KEPT
IEF196I IEF285I   VOL SER NOS= ZD1PAK. 
IEF196I IEF285I   SYS1.IBM.PARMLIB KEPT
IEF196I IEF285I   VOL SER NOS= ZD1PAK. 

So the