Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

Just wanted to thank everyone on the list for their insight to my issues with a 
new JES2MAS, especaiilly Lizzette, 
followed the doc to the letter, removed the old member first with a warm start 
MEMBER(2),NAME= 
once I responded to the JES2 WTOR are you sure, JES2 Initialized, I shutdown 
JES2 and updated the member name 
MEMBER(2)NAME=SYSC 
started JES2 and viola ! job submission via sysaff works as designed 
only issue I'm having now is an NJE connection to a test lpar, once SYSC joined 
SYSA, node names were redefined for some reason, so for now I'm stuck with node 
name N1 on SYSA as OWNNODE, the connections to the test system fail 

IAZ0543I NETSRV1 TCP/IP connection with IP Addr: TCPIPT1.abcbs.net 
Port: 1041 Successful 
IAZ0520I NETSRV1 NJETCP Signon error: OHOST value 'LITJES2A' not 
valid in OPEN from IP addr: TCPIPT1.abcbs.net 
well that's true the node(LITJES2A) has become N1 
looks like a cold start to correct OWNNODE, I'm reviewing the doc, I'm sure I 
messed up somehow not defining the nodes on SYSC the same as SYSA - but this is 
an NJE connection to a test LPAR so not so critical. 
again thanks everyone for their help 
Carmen 
- Original Message -

From: "Lizette Koehler" <stars...@mindspring.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, December 6, 2016 9:44:56 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

And just to make sure I remember correctly. 

The way a warm start works is no work is running in JES2. So nothing up using 
SYSOUT. Then abend JES2 and restart with WARM,NOREQ 

If any work is running with SYSOUT, then I think JES2 changes to a HOT START. 

So, when I have done a warm start, I am at a Master Console (not SDSF) and the 
only tasks running is what comes up in NIP and JES2. No TSO, no VTAM, etc... 

Then I can $PJES2,ABEND 
S JES2,PARM='WARM,NOREQ' 


Just checking 

Lizette 


> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Carmen Vitullo 
> Sent: Tuesday, December 06, 2016 8:17 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> I spent the morning reviewing and re-reading the link Lizz provided, this was 
> a great help, I was thinking I could just rename the member to what I wanted 
> and warm start JES2, according to the good doc not so fast 
> 
> 
> 
> Figure 1. Reassigning Member Identifiers to Different Processors 
> MEMBER(1) NAME=SYSA /* ORIGINAL CONFIGURATION */ 
> MEMBER(2) NAME=SYSB 
> 
> . 
> . 
> . 
> 
> 
> Step 1: 
> MEMBER(1) NAME=SYSA /* DEFINE TEMPORARY */ 
> MEMBER(2) NAME=SYSY /* MEMBER IDENTIFIERS */ 
> /* AND THEN WARM START */ 
> . 
> . 
> . 
> 
> 
> Step 2: 
> $PJES2 on all members in MAS. 
> 
> 
> Step 3: 
> Perform an all-member warm start with the above configuration. 
> 
> 
> Step 4: 
> When JES2 starts redefine with the following statements: 
> 
> 
> MEMBER(1) NAME=SYSA /* NEW CONFIGURATION */ 
> MEMBER(2) NAME=SYSC 
> 
> this will be my plan for my next downtime schedule, again thanks ALL for your 
> great insight , thanks Lizz for the push to re read the doc Carmen . 
> . 

-- 
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

got ya, I will review thanks Tom 
Carmen 





- Original Message -

From: "Tom Marchant" <000a2a8c2020-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, December 6, 2016 10:14:45 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

On Tue, 6 Dec 2016 10:54:23 -0500, Carmen Vitullo wrote: 

>S JES2,PARM='WARM,NOREQ' 
>this will be my plan for the next downtime; 

Make sure that all of the parameters that you are changing from 
the way it is running now are parameters that can be changed on 
a warm start. Many (most?) JES2 parameters cannot. 

-- 
Tom Marchant 

-- 
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: new JES2 MAS jobs will not run on member 2

[Tom Marchant]

On Tue, 6 Dec 2016 10:54:23 -0500, Carmen Vitullo wrote:

>S JES2,PARM='WARM,NOREQ'
>this will be my plan for the next downtime;

Make sure that all of the parameters that you are changing from 
the way it is running now are parameters that can be changed on 
a warm start. Many (most?) JES2 parameters cannot.

-- 
Tom Marchant

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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

First thanks for the previous link to z/OS2.2 JES enhancements 
I have access to the master console so, I let automation shutdown everything, a 
$PJES2 is issued via OPS, no need today to issue a $PJES2,TERM or $PJES2,ABEND, 
I really don't like to ABEND JES unless required. 
so starting JES2 prior to an IPL, I start JES2 as you suggested 


S JES2,PARM='WARM,NOREQ' 
this will be my plan for the next downtime; 
once JES2 is down on MEMBER(1) - singe system MAS, I'll reconfigure using my 
process I have outlined, 
once the members are reassigned correctly it is easier for me to IPL member(1) 
'SYSA' with the new PARMS 
then bring member(2) into the MAS 
one other issue I found with my parms on member(2) was I defined both member(1) 
and member(2), according to the good book, there's no need to code member(1) on 
member(2)'s jesparms 
again thanks Lizz! 
Carmen 


- Original Message -

From: "Lizette Koehler" <stars...@mindspring.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, December 6, 2016 9:44:56 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

And just to make sure I remember correctly. 

The way a warm start works is no work is running in JES2. So nothing up using 
SYSOUT. Then abend JES2 and restart with WARM,NOREQ 

If any work is running with SYSOUT, then I think JES2 changes to a HOT START. 

So, when I have done a warm start, I am at a Master Console (not SDSF) and the 
only tasks running is what comes up in NIP and JES2. No TSO, no VTAM, etc... 

Then I can $PJES2,ABEND 
S JES2,PARM='WARM,NOREQ' 


Just checking 

Lizette 


> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Carmen Vitullo 
> Sent: Tuesday, December 06, 2016 8:17 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> I spent the morning reviewing and re-reading the link Lizz provided, this was 
> a great help, I was thinking I could just rename the member to what I wanted 
> and warm start JES2, according to the good doc not so fast 
> 
> 
> 
> Figure 1. Reassigning Member Identifiers to Different Processors 
> MEMBER(1) NAME=SYSA /* ORIGINAL CONFIGURATION */ 
> MEMBER(2) NAME=SYSB 
> 
> . 
> . 
> . 
> 
> 
> Step 1: 
> MEMBER(1) NAME=SYSA /* DEFINE TEMPORARY */ 
> MEMBER(2) NAME=SYSY /* MEMBER IDENTIFIERS */ 
> /* AND THEN WARM START */ 
> . 
> . 
> . 
> 
> 
> Step 2: 
> $PJES2 on all members in MAS. 
> 
> 
> Step 3: 
> Perform an all-member warm start with the above configuration. 
> 
> 
> Step 4: 
> When JES2 starts redefine with the following statements: 
> 
> 
> MEMBER(1) NAME=SYSA /* NEW CONFIGURATION */ 
> MEMBER(2) NAME=SYSC 
> 
> this will be my plan for my next downtime schedule, again thanks ALL for your 
> great insight , thanks Lizz for the push to re read the doc Carmen . 
> . 

-- 
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: new JES2 MAS jobs will not run on member 2

[Lizette Koehler]

And just to make sure I remember correctly.

The way a warm start works is no work is running in JES2.  So nothing up using 
SYSOUT.  Then abend JES2 and restart with WARM,NOREQ

If any work is running with SYSOUT, then I think JES2 changes to a HOT START.  

So, when I have done a warm start, I am at a Master Console (not SDSF) and the 
only tasks running is what comes up in NIP and JES2.  No TSO, no VTAM, etc...

Then I can $PJES2,ABEND
 S JES2,PARM='WARM,NOREQ'


Just checking

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Carmen Vitullo
> Sent: Tuesday, December 06, 2016 8:17 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> I spent the morning reviewing and re-reading the link Lizz provided, this was
> a great help, I was thinking I could just rename the member to what I wanted
> and warm start JES2, according to the good doc not so fast
> 
> 
> 
> Figure 1. Reassigning Member Identifiers to Different Processors
> MEMBER(1) NAME=SYSA /* ORIGINAL CONFIGURATION */
> MEMBER(2) NAME=SYSB
> 
> .
> .
> .
> 
> 
> Step 1:
> MEMBER(1) NAME=SYSA /* DEFINE TEMPORARY */
> MEMBER(2) NAME=SYSY /* MEMBER IDENTIFIERS */
> /* AND THEN WARM START */
> .
> .
> .
> 
> 
> Step 2:
> $PJES2 on all members in MAS.
> 
> 
> Step 3:
> Perform an all-member warm start with the above configuration.
> 
> 
> Step 4:
> When JES2 starts redefine with the following statements:
> 
> 
> MEMBER(1) NAME=SYSA /* NEW CONFIGURATION */
> MEMBER(2) NAME=SYSC
> 
> this will be my plan for my next downtime schedule, again thanks ALL for your
> great insight , thanks Lizz for the push to re read the doc Carmen .
> .

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

Re: new JES2 MAS jobs will not run on member 2

[Bill Woodger]

Unless Sir Nose d'Voidoffunk his wielding his Snooze Gun, you mean defunct, not 
"defunked". Just sayin'.

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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

I spent the morning reviewing and re-reading the link Lizz provided, this was a 
great help, I was thinking I could just rename the member to what I wanted and 
warm start JES2, according to the good doc not so fast 



Figure 1. Reassigning Member Identifiers to Different Processors 
MEMBER(1) NAME=SYSA /* ORIGINAL CONFIGURATION */ 
MEMBER(2) NAME=SYSB 

. 
. 
. 


Step 1: 
MEMBER(1) NAME=SYSA /* DEFINE TEMPORARY */ 
MEMBER(2) NAME=SYSY /* MEMBER IDENTIFIERS */ 
/* AND THEN WARM START */ 
. 
. 
. 


Step 2: 
$PJES2 on all members in MAS. 


Step 3: 
Perform an all-member warm start with the above configuration. 


Step 4: 
When JES2 starts redefine with the following statements: 


MEMBER(1) NAME=SYSA /* NEW CONFIGURATION */ 
MEMBER(2) NAME=SYSC 

this will be my plan for my next downtime schedule, again thanks ALL for your 
great insight , thanks Lizz for the push to re read the doc 
Carmen . 
. 
. 
- Original Message -

From: "Lizette Koehler" <stars...@mindspring.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 11:57:45 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

So the commands do the following 

$HQ,ALL Hold all JES2 queues 
$S Start JES2 
,ALL Still hold all queues. 



C=c1[...c36] 
The specified job queue(s) (classes A-Z and 0-9) are held. A maximum of 36 
classes may be specified. 

ALL 
All job queues are held. 



Not sure but it looks like they did not want anything running after System 
IPL'd and JES2 was started. 

How is jes2 started? 
S JES2,PARM='NOREQ' is a typical way to bring up JES2 without responding to the 
WTOR that JES2 could produce to see if you wanted JES2 to start immediately. 

As for security issues. Check out the $TDEBUG command for tracing in JES2 for 
any SAF products or issues. NOTE: Do not leave it on for long - it will flood 
syslog. 

Lizette 


> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Carmen Vitullo 
> Sent: Monday, December 05, 2016 9:42 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> we're a TSS show but I think if its security related any tracing I can 
> activate would help, so far the only think I question is at the end of the 
> JES2 PARM DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if 
> this 
> stopped my test job from hitting the converter also, we don't have any WLM 
> resources defined, but I question why the RES display in SDSF shows, I know 
> we 
> don't use these resources but could the state of the resource (SYSNAME) in 
> RESET cause jobs not to run? 
> 
> 
> RESPONSE=SYSC 
> IWM038I 10.33.50 WLM DISPLAY 027 
> RESOURCE: SYSA 
> DESCRIPTION: SYSA resource 
> SYSTEM STATE SYSTEM STATE SYSTEM STATE 
> SYSA RESET SYSC RESET SYST RESET 
> 
> 
> thanks for your help Paul 
> Carmen - Original Message - 
> 
> From: "Paul Feller" <paul.fel...@transamerica.com> 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Sent: Monday, December 5, 2016 10:27:57 AM 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> Carmen, sometimes it just helps to see others definitions. This is the 
> definitions we use for a three member MAS. All three members are running z/OS 
> 2.2. All three members share the same startup parms. I would put in the 
> SECURITY=YES just in case there might be a RACF (security) related to the 
> job(s). I'm sure everyone has a little different take on how some the parms 
> should look. 
> 
> 
> MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM 
> HOLD TIME  OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/ 
> OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ SHARED=CHECK, /* CHECK 
> FOR SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.)  
> OC*/ 
> XCFGRPNM=TS00 /* XCF comm group name OC*/ 
> MEMBER(3) NAME=TS01 /* TS01 member */ 
> MEMBER(4) NAME=TS02 /* TS02 MEMBER */ 
> MEMBER(5) NAME=TS03 /* TS03 member */ 
> /* */ 
> SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), 
> TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED, 
> DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP 
> /* */ 
> CKPTDEF CKPT1=(STR=TS00_JES2CKPT), 
> NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007), 
> CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES), 
> NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005), 
> MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE 
> /* */ 
> /*--*/ 
> /* SECURITY=YES: Provides additional RACF security info related */ 
> /* to the $HASP186 message */ 
> /* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */ 
> /* record is written */ 
> /*--*/ 
&

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

Thanks Jesse, I wondered about the late yesterday before I left, on my test 
LPAR there was another defunked system there, I tested the process of removing 
the system, I think I should have followed the same process in the prod mas I 
was defining 
from the MAS display currently, since I did back this out: 

SDSF MAS DISPLAY SYSA LITJES2 26% SPOOL LINE 1-2 (2) 
COMMAND INPUT ===> SCROLL ===> PAGE 
PREFIX=OPERC* DEST=(ALL) OWNER=* SYSNAME= 
NP NAME Status SID PrevCkpt Hold ActHold Dormancy ActDorm Sync 
SYSA ACTIVE 1 0.27 40 40 (100,500) 229 
SYSB DRAINED,P 2 0.00 0 0 (0,0) 0 

SYSB was the old system I wanted to replace shifting left on the MAS display 
shows 
NAME ol Ind RSID SysName 
SYSA 00 NO SYSA 
SYSB 0 NO SYSC <- this is the system I want to add to the MAS, so I think I 
need to follow the doc more carefully, remove the system bu adding 
MEMBER(2),NAME= 
WARM start JES2, respond to the initialization message, then shut down JES2 
update JES2PARMS with MEMBER(2),NAME=SYSC 
WARM start JES2, respond to the initialization message 
Can't see any other reason for jobs submit but will not run, it has to be a 
mismatch in the PARMS, or I'm not following the process correctly to 
add/replace a system into a MAS. 
Thanks again Jesse 


Carmen 
- Original Message -

From: "Jesse 1 Robinson" <jesse1.robin...@sce.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 4:17:52 PM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Following this line of inquiry, get into SDSF and type MAS. There could be a 
discrepancy between the definition for the new member and its old 
gone-but-not-necessarily-forgotten ancestor. Replacing a member IIRC is a 
multistep process that involves first deleting the old guy, then defining the 
new guy. There could be conflicting attributes hanging around. 

. 
. 
J.O.Skip Robinson 
Southern California Edison Company 
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager 
323-715-0595 Mobile 
626-302-7535 Office 
robin...@sce.com 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant 
Sent: Monday, December 05, 2016 10:10 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: (External):Re: new JES2 MAS jobs will not run on member 2 

On Mon, 5 Dec 2016 08:24:12 -0500, Carmen Vitullo wrote: 

>mermber definition in both systems jes2parms are; 

(snipped) 

You may be focusing unnecessarily on your JES2PARMS. 
Many parameters, including MASDEF cannot be changed with a warm start. 
The only way tho change them is with a cold start, or via command, e.g. 
$TMASDEF. 

-- 
Tom Marchant 


-- 
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: new JES2 MAS jobs will not run on member 2

[Jesse 1 Robinson]

Following this line of inquiry, get into SDSF and type MAS. There could be a 
discrepancy between the definition for the new member and its old 
gone-but-not-necessarily-forgotten ancestor. Replacing a member IIRC is a 
multistep process that involves first deleting the old guy, then defining the 
new guy. There could be conflicting attributes hanging around.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Monday, December 05, 2016 10:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: new JES2 MAS jobs will not run on member 2

On Mon, 5 Dec 2016 08:24:12 -0500, Carmen Vitullo wrote:

>mermber definition in both systems jes2parms are;

(snipped)

You may be focusing unnecessarily on your JES2PARMS.
Many parameters, including MASDEF cannot be changed with a warm start.
The only way tho change them is with a cold start, or via command, e.g. 
$TMASDEF.

--
Tom Marchant


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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

OK, thanks Tom, I understand, I know a cold start is using the big hammer and 
would add time, and another point of failure to a process that should be 
straight forward. 
I'll take your good advice and display current JES2 environment and use the 
reset ($T) command where needed. 
my next downtime request will be to TEST JES2MAS configuration - if all works I 
just leave it in :) 


Thanks again 
Carmen 


I found in my test LPAR the $T command works well for things I wanted to test 
From: "Tom Marchant" <000a2a8c2020-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 2:18:05 PM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

On Mon, 5 Dec 2016 13:30:47 -0500, Carmen Vitullo wrote: 

>the more I review and diagnose the more I tend to think a warm 
>start is not good enough, I agree Tom, a cold start may be needed 
>to do this correctly. 

It isn't that you need a cold start, but you can't do it by changing 
your JES2PARM and doing a warm start. A cold start can be pretty 
traumatic, and I wouldn't recommend it. 

For that matter, your JES2PARM is not a reliable method to determine 
what you have. The reason is that you can change most of what 
you have specified with commands, and those changes are kept in 
checkpoint and used upon a warm start. 

I would start by issuing JES2 display commands to document where 
you are, and figure out the $T commands that you need to set it the 
way you want it. Then you will probably want to update your 
JES2PARM so that it will be ready in case you ever need a cold start. 

-- 
Tom Marchant 

-- 
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: new JES2 MAS jobs will not run on member 2

[Tom Marchant]

On Mon, 5 Dec 2016 13:30:47 -0500, Carmen Vitullo wrote:

>the more I review and diagnose the more I tend to think a warm 
>start is not good enough, I agree Tom, a cold start may be needed 
>to do this correctly.

It isn't that you need a cold start, but you can't do it by changing 
your JES2PARM and doing a warm start. A cold start can be pretty 
traumatic, and I wouldn't recommend it.

For that matter, your JES2PARM is not a reliable method to determine 
what you have. The reason is that you can change most of what 
you have specified with commands, and those changes are kept in 
checkpoint and used upon a warm start.

I would start by issuing JES2 display commands to document where 
you are, and figure out the $T commands that you need to set it the 
way you want it. Then you will probably want to update your 
JES2PARM so that it will be ready in case you ever need a cold start.

-- 
Tom Marchant

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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

the more I review and diagnose the more I tend to think a warm start is not 
good enough, I agree Tom, a cold start may be needed to do this correctly. 
one thing I did fail to mention was there WAS another system in a MAS with 
SYSA, that is now defunked, SYSB, still defined in the old JES2PARMS, and once 
SYSA's JES2 is up, I get a message about changing the member, I'll have to 
check the log for the exact message, but it does rename member(2) to SYSC, I 
should just add the MEMBER(2)= statement to nullify the member name but every 
time I back out its an afterthought 
thanks again for your thoughts and assistance. 
Carmen 

- Original Message -

From: "Tom Marchant" <000a2a8c2020-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 12:09:57 PM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

On Mon, 5 Dec 2016 08:24:12 -0500, Carmen Vitullo wrote: 

>mermber definition in both systems jes2parms are; 

(snipped) 

You may be focusing unnecessarily on your JES2PARMS. 
Many parameters, including MASDEF cannot be changed 
with a warm start. 
The only way tho change them is with a cold start, or via 
command, e.g. $TMASDEF. 

-- 
Tom Marchant 

-- 
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

yep, these command were prolly a throw back from prior to automation, I'm not 
100% sure, the operators issue the same command ($HQ,ALL) prior to system 
maintenance downtime 
JES2 is started via OPS 'S JES2,PARM='NOREQ'' 
I'll make sure the debug for security is no on for long, thanks for that !~ 


next is to schedule some time to debug any issues using all the great idea's I 
received here. 
thanks 
Carmen 

- Original Message -

From: "Lizette Koehler" <stars...@mindspring.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 11:57:45 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

So the commands do the following 

$HQ,ALL Hold all JES2 queues 
$S Start JES2 
,ALL Still hold all queues. 



C=c1[...c36] 
The specified job queue(s) (classes A-Z and 0-9) are held. A maximum of 36 
classes may be specified. 

ALL 
All job queues are held. 



Not sure but it looks like they did not want anything running after System 
IPL'd and JES2 was started. 

How is jes2 started? 
S JES2,PARM='NOREQ' is a typical way to bring up JES2 without responding to the 
WTOR that JES2 could produce to see if you wanted JES2 to start immediately. 

As for security issues. Check out the $TDEBUG command for tracing in JES2 for 
any SAF products or issues. NOTE: Do not leave it on for long - it will flood 
syslog. 

Lizette 


> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Carmen Vitullo 
> Sent: Monday, December 05, 2016 9:42 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> we're a TSS show but I think if its security related any tracing I can 
> activate would help, so far the only think I question is at the end of the 
> JES2 PARM DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if 
> this 
> stopped my test job from hitting the converter also, we don't have any WLM 
> resources defined, but I question why the RES display in SDSF shows, I know 
> we 
> don't use these resources but could the state of the resource (SYSNAME) in 
> RESET cause jobs not to run? 
> 
> 
> RESPONSE=SYSC 
> IWM038I 10.33.50 WLM DISPLAY 027 
> RESOURCE: SYSA 
> DESCRIPTION: SYSA resource 
> SYSTEM STATE SYSTEM STATE SYSTEM STATE 
> SYSA RESET SYSC RESET SYST RESET 
> 
> 
> thanks for your help Paul 
> Carmen - Original Message - 
> 
> From: "Paul Feller" <paul.fel...@transamerica.com> 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Sent: Monday, December 5, 2016 10:27:57 AM 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> Carmen, sometimes it just helps to see others definitions. This is the 
> definitions we use for a three member MAS. All three members are running z/OS 
> 2.2. All three members share the same startup parms. I would put in the 
> SECURITY=YES just in case there might be a RACF (security) related to the 
> job(s). I'm sure everyone has a little different take on how some the parms 
> should look. 
> 
> 
> MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM 
> HOLD TIME  OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/ 
> OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ SHARED=CHECK, /* CHECK 
> FOR SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.)  
> OC*/ 
> XCFGRPNM=TS00 /* XCF comm group name OC*/ 
> MEMBER(3) NAME=TS01 /* TS01 member */ 
> MEMBER(4) NAME=TS02 /* TS02 MEMBER */ 
> MEMBER(5) NAME=TS03 /* TS03 member */ 
> /* */ 
> SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), 
> TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED, 
> DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP 
> /* */ 
> CKPTDEF CKPT1=(STR=TS00_JES2CKPT), 
> NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007), 
> CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES), 
> NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005), 
> MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE 
> /* */ 
> /*--*/ 
> /* SECURITY=YES: Provides additional RACF security info related */ 
> /* to the $HASP186 message */ 
> /* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */ 
> /* record is written */ 
> /*--*/ 
> DEBUG SECURITY=YES,SYMREC=YES 
> 
> 
> 
> Thanks.. 
> 
> Paul Feller 
> AGT Mainframe Technical Support 
> 
> 
> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Carmen Vitullo 
> Sent: Monday, December 05, 2016 08:13 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: new JES2 MAS jobs will not run on member 2 
> 
> Thanks Gerhard - 
> Carmen 
> 
> - Original Message -

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

the same status is what i found, scroll over to the right 
AWAIT CONV - 
my test job had /*JOBPARM S=SYSC, no real reason for the SYSAFF, just a test 
scenario I wanted to run, the other scenario was to submit from SYSC to SYSC, 
same results, job sitting in the input queue , but now shows the correct input 
class, 


- Original Message -

From: "Jesse 1 Robinson" <jesse1.robin...@sce.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 11:49:09 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

There are some fields in SDSF (by default way to the right) that attempt to 
explain why a job is not running. Some of these are 

Scheduling-Env Dly Mode Spin PhaseName Phase Type DelayRsn 

I would expect to see something non-blank in one or more of these columns. We 
happen to have several jobs in the input queue. All but one show a status of 
HOLD. The other one shows 

PhaseName Phase 
AWAIT CONV 129 

I looked into the job and found this--no idea how it happened: 

/*JOBPARM SYSAFF=(ANY,IND) 

. 
. 
J.O.Skip Robinson 
Southern California Edison Company 
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager 
323-715-0595 Mobile 
626-302-7535 Office 
robin...@sce.com 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 05, 2016 8:42 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: (External):Re: new JES2 MAS jobs will not run on member 2 

we're a TSS show but I think if its security related any tracing I can activate 
would help, so far the only think I question is at the end of the JES2 PARM 
DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if this stopped my 
test job from hitting the converter also, we don't have any WLM resources 
defined, but I question why the RES display in SDSF shows, I know we don't use 
these resources but could the state of the resource (SYSNAME) in RESET cause 
jobs not to run? 


RESPONSE=SYSC 
IWM038I 10.33.50 WLM DISPLAY 027 
RESOURCE: SYSA 
DESCRIPTION: SYSA resource 
SYSTEM STATE SYSTEM STATE SYSTEM STATE 
SYSA RESET SYSC RESET SYST RESET 


thanks for your help Paul 
Carmen - Original Message - 

From: "Paul Feller" <paul.fel...@transamerica.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 10:27:57 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Carmen, sometimes it just helps to see others definitions. This is the 
definitions we use for a three member MAS. All three members are running z/OS 
2.2. All three members share the same startup parms. I would put in the 
SECURITY=YES just in case there might be a RACF (security) related to the 
job(s). I'm sure everyone has a little different take on how some the parms 
should look. 


MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM 
HOLD TIME  OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/ 
OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ SHARED=CHECK, /* CHECK FOR 
SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.)  OC*/ 
XCFGRPNM=TS00 /* XCF comm group name OC*/ 
MEMBER(3) NAME=TS01 /* TS01 member */ 
MEMBER(4) NAME=TS02 /* TS02 MEMBER */ 
MEMBER(5) NAME=TS03 /* TS03 member */ 
/* */ 
SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), 
TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED, 
DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP 
/* */ 
CKPTDEF CKPT1=(STR=TS00_JES2CKPT), 
NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007), 
CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES), 
NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005), 
MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE 
/* */ 
/*--*/ 
/* SECURITY=YES: Provides additional RACF security info related */ 
/* to the $HASP186 message */ 
/* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */ 
/* record is written */ 
/*--*/ 
DEBUG SECURITY=YES,SYMREC=YES 



Thanks.. 

Paul Feller 
AGT Mainframe Technical Support 


-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 05, 2016 08:13 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Thanks Gerhard - 
Carmen 

- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 8:00:17 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Correct. Those define NJE APPL's ... 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 5, 2016 5:53 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE

Re: new JES2 MAS jobs will not run on member 2

[Tom Marchant]

On Mon, 5 Dec 2016 08:24:12 -0500, Carmen Vitullo wrote:

>mermber definition in both systems jes2parms are;

(snipped)

You may be focusing unnecessarily on your JES2PARMS.
Many parameters, including MASDEF cannot be changed 
with a warm start.
The only way tho change them is with a cold start, or via 
command, e.g. $TMASDEF.

-- 
Tom Marchant

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

Re: new JES2 MAS jobs will not run on member 2

[Lizette Koehler]

So the commands do the following

  $HQ,ALL   Hold all JES2 queues
  $SStart JES2
  ,ALL   Still hold all queues.



C=c1[...c36]
The specified job queue(s) (classes A-Z and 0-9) are held. A maximum of 36 
classes may be specified.

ALL
All job queues are held.



Not sure but it looks like they did not want anything running after System 
IPL'd and JES2 was started.

How is jes2 started?
  S JES2,PARM='NOREQ'  is  a typical way to bring up JES2 without responding to 
the WTOR that JES2 could produce to see if you wanted JES2 to start immediately.

As for security issues.  Check out the $TDEBUG command for tracing in JES2 for 
any SAF products or issues.  NOTE:  Do not leave it on for long - it will flood 
syslog.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Carmen Vitullo
> Sent: Monday, December 05, 2016 9:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> we're a TSS show but I think if its security related any tracing I can
> activate would help, so far the only think I question is at the end of the
> JES2 PARM DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if this
> stopped my test job from hitting the converter also, we don't have any WLM
> resources defined, but I question why the RES display in SDSF shows, I know we
> don't use these resources but could the state of the resource (SYSNAME) in
> RESET cause jobs not to run?
> 
> 
> RESPONSE=SYSC
> IWM038I 10.33.50 WLM DISPLAY 027
> RESOURCE: SYSA
> DESCRIPTION: SYSA resource
> SYSTEM STATE SYSTEM STATE SYSTEM STATE
> SYSA RESET SYSC RESET SYST RESET
> 
> 
> thanks for your help Paul
> Carmen - Original Message -
> 
> From: "Paul Feller" <paul.fel...@transamerica.com>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Monday, December 5, 2016 10:27:57 AM
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> Carmen, sometimes it just helps to see others definitions. This is the
> definitions we use for a three member MAS. All three members are running z/OS
> 2.2. All three members share the same startup parms. I would put in the
> SECURITY=YES just in case there might be a RACF (security) related to the
> job(s). I'm sure everyone has a little different take on how some the parms
> should look.
> 
> 
> MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM
> HOLD TIME  OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/
> OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ SHARED=CHECK, /* CHECK
> FOR SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.) 
> OC*/
> XCFGRPNM=TS00 /* XCF comm group name OC*/
> MEMBER(3) NAME=TS01 /* TS01 member */
> MEMBER(4) NAME=TS02 /* TS02 MEMBER */
> MEMBER(5) NAME=TS03 /* TS03 member */
> /* */
> SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80),
> TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED,
> DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP
> /* */
> CKPTDEF CKPT1=(STR=TS00_JES2CKPT),
> NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007),
> CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES),
> NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005),
> MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE
> /* */
> /*--*/
> /* SECURITY=YES: Provides additional RACF security info related */
> /* to the $HASP186 message */
> /* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */
> /* record is written */
> /*--*/
> DEBUG SECURITY=YES,SYMREC=YES
> 
> 
> 
> Thanks..
> 
> Paul Feller
> AGT Mainframe Technical Support
> 
> 
> -----Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Carmen Vitullo
> Sent: Monday, December 05, 2016 08:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> Thanks Gerhard -
> Carmen
> 
> - Original Message -
> 
> From: "Gerhard Adam" <gada...@charter.net>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Monday, December 5, 2016 8:00:17 AM
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> Correct. Those define NJE APPL's ...
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Carmen Vitullo
> Sent: Monday, December 5, 2016 5:53 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: new JES2 MAS jobs will not run on member 2
> 
> and along those lines I think my other issue is I don't need
> 
> APPL(LITJES2A) NODE=1 <-- this is member( 1)
> APPL(

Re: new JES2 MAS jobs will not run on member 2

[Jesse 1 Robinson]

There are some fields in SDSF (by default way to the right) that attempt to 
explain why a job is not running. Some of these are 

Scheduling-Env   Dly Mode Spin PhaseNamePhase Type DelayRsn

I would expect to see something non-blank in one or more of these columns. We 
happen to have several jobs in the input queue. All but one show a status of 
HOLD. The other one shows 

PhaseNamePhase
AWAIT CONV 129

I looked into the job and found this--no idea how it happened:

/*JOBPARM SYSAFF=(ANY,IND)

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Monday, December 05, 2016 8:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: new JES2 MAS jobs will not run on member 2

we're a TSS show but I think if its security related any tracing I can activate 
would help, so far the only think I question is at the end of the JES2 PARM 
DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if this stopped my 
test job from hitting the converter also, we don't have any WLM resources 
defined, but I question why the RES display in SDSF shows, I know we don't use 
these resources but could the state of the resource (SYSNAME) in RESET cause 
jobs not to run? 


RESPONSE=SYSC
IWM038I 10.33.50 WLM DISPLAY 027
RESOURCE: SYSA
DESCRIPTION: SYSA resource
SYSTEM STATE SYSTEM STATE SYSTEM STATE
SYSA RESET SYSC RESET SYST RESET 


thanks for your help Paul
Carmen - Original Message -

From: "Paul Feller" <paul.fel...@transamerica.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, December 5, 2016 10:27:57 AM
Subject: Re: new JES2 MAS jobs will not run on member 2 

Carmen, sometimes it just helps to see others definitions. This is the 
definitions we use for a three member MAS. All three members are running z/OS 
2.2. All three members share the same startup parms. I would put in the 
SECURITY=YES just in case there might be a RACF (security) related to the 
job(s). I'm sure everyone has a little different take on how some the parms 
should look. 


MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM 
HOLD TIME  OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/ 
OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ SHARED=CHECK, /* CHECK FOR 
SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.)  OC*/
XCFGRPNM=TS00 /* XCF comm group name OC*/
MEMBER(3) NAME=TS01 /* TS01 member */
MEMBER(4) NAME=TS02 /* TS02 MEMBER */
MEMBER(5) NAME=TS03 /* TS03 member */
/* */
SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80),
TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED,
DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP
/* */
CKPTDEF CKPT1=(STR=TS00_JES2CKPT),
NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007),
CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES),
NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005),
MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE
/* */
/*--*/
/* SECURITY=YES: Provides additional RACF security info related */
/* to the $HASP186 message */
/* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */
/* record is written */
/*--*/
DEBUG SECURITY=YES,SYMREC=YES 



Thanks.. 

Paul Feller
AGT Mainframe Technical Support 


-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 05, 2016 08:13 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Thanks Gerhard - 
Carmen 

- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 8:00:17 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Correct. Those define NJE APPL's ... 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 5, 2016 5:53 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1) 
APPL(LITJES2C) NODE=1 <--- this is member(2) 
APPL(LITJES2T) NODE=2 
APPL(A6504JEA) NODE=4 


- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters point 
to the same data set. That's it.

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

we're a TSS show but I think if its security related any tracing I can activate 
would help, so far the only think I question is 
at the end of the JES2 PARM DECK my predecessor added a 
$HQ,ALL 
$S 
$HQ,ALL 
I'm wondering if this stopped my test job from hitting the converter 
also, we don't have any WLM resources defined, but I question why the RES 
display in SDSF shows, I know we don't use these resources but could the state 
of the resource (SYSNAME) in RESET cause jobs not to run? 


RESPONSE=SYSC 
IWM038I 10.33.50 WLM DISPLAY 027 
RESOURCE: SYSA 
DESCRIPTION: SYSA resource 
SYSTEM STATE SYSTEM STATE SYSTEM STATE 
SYSA RESET SYSC RESET SYST RESET 


thanks for your help Paul 
Carmen - Original Message -

From: "Paul Feller" <paul.fel...@transamerica.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 10:27:57 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Carmen, sometimes it just helps to see others definitions. This is the 
definitions we use for a three member MAS. All three members are running z/OS 
2.2. All three members share the same startup parms. I would put in the 
SECURITY=YES just in case there might be a RACF (security) related to the 
job(s). I'm sure everyone has a little different take on how some the parms 
should look. 


MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ 
HOLD=40, /* MINIMUM HOLD TIME  OC*/ 
LOCKOUT=1000, /* LOCK-OUT WARNING TIME  OC*/ 
OWNMEMB=, /* SMF ID OF THIS SYSTEM  WS*/ 
SHARED=CHECK, /* CHECK FOR SHARED DASD ---(NEW) OC*/ 
SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.)  OC*/ 
XCFGRPNM=TS00 /* XCF comm group name OC*/ 
MEMBER(3) NAME=TS01 /* TS01 member */ 
MEMBER(4) NAME=TS02 /* TS02 MEMBER */ 
MEMBER(5) NAME=TS03 /* TS03 member */ 
/* */ 
SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), 
TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED, 
DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP 
/* */ 
CKPTDEF CKPT1=(STR=TS00_JES2CKPT), 
NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007), 
CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES), 
NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005), 
MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE 
/* */ 
/*--*/ 
/* SECURITY=YES: Provides additional RACF security info related */ 
/* to the $HASP186 message */ 
/* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */ 
/* record is written */ 
/*--*/ 
DEBUG SECURITY=YES,SYMREC=YES 



Thanks.. 

Paul Feller 
AGT Mainframe Technical Support 


-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 05, 2016 08:13 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Thanks Gerhard - 
Carmen 

- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 8:00:17 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Correct. Those define NJE APPL's ... 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 5, 2016 5:53 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1) 
APPL(LITJES2C) NODE=1 <--- this is member(2) 
APPL(LITJES2T) NODE=2 
APPL(A6504JEA) NODE=4 


- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters point 
to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's the 
latter you want, then you need a network connection and you need to ensure it 
is started before the systems will recognize each other. 

Adam 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, but 
now that you mention this, I really didn't need it since member 2 has only one 
specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 7

Re: new JES2 MAS jobs will not run on member 2

[Feller, Paul]

Carmen, sometimes it just helps to see others definitions.  This is the 
definitions we use for a three member MAS.  All three members are running z/OS 
2.2.  All three members share the same startup parms.  I would put in the 
SECURITY=YES just in case there might be a RACF (security) related to the 
job(s).  I'm sure everyone has a little different take on how some the parms 
should look.  


MASDEF   DORMANCY=(80,500),  /* MIN/MAX DORMANCY TIME  OC*/
 HOLD=40,/* MINIMUM HOLD TIME  OC*/
 LOCKOUT=1000,   /* LOCK-OUT WARNING TIME  OC*/
 OWNMEMB=,   /* SMF ID OF THIS SYSTEM  WS*/
 SHARED=CHECK,   /* CHECK FOR SHARED DASD   ---(NEW)   OC*/
 SYNCTOL=120,/* SYNCH.TOLERANCE (SEC.) OC*/
 XCFGRPNM=TS00   /* XCF comm group nameOC*/
MEMBER(3) NAME=TS01  /* TS01 member  */
MEMBER(4) NAME=TS02  /* TS02 MEMBER  */
MEMBER(5) NAME=TS03  /* TS03 member  */
  /**/ 
SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), 
 TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED,
 DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP  
  /**/ 
CKPTDEF  CKPT1=(STR=TS00_JES2CKPT),
 NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007),  
 CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES),   
 NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005),  
 MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE 
  /**/
/*--*/
/* SECURITY=YES: Provides additional RACF security info related */
/*   to the $HASP186 message*/
/* SYMREC=YES:   Message $HASP805 is written when a LOGREC symptom  */
/*   record is written  */
/*--*/
DEBUGSECURITY=YES,SYMREC=YES  



Thanks..

Paul Feller
AGT Mainframe Technical Support


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Monday, December 05, 2016 08:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Thanks Gerhard - 
Carmen 

- Original Message -

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 8:00:17 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Correct. Those define NJE APPL's ... 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 5, 2016 5:53 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1) 
APPL(LITJES2C) NODE=1 <--- this is member(2) 
APPL(LITJES2T) NODE=2 
APPL(A6504JEA) NODE=4 


- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters point 
to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's the 
latter you want, then you need a network connection and you need to ensure it 
is started before the systems will recognize each other. 

Adam 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, but 
now that you mention this, I really didn't need it since member 2 has only one 
specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114 
Office: 501.210.4705 
Cell: 501.514.4266 
cpvitu...@arkbluecross.com 
arkansasbluecross.com 





-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

Thanks Gerhard - 
Carmen 

- Original Message -

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 8:00:17 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Correct. Those define NJE APPL's ... 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Monday, December 5, 2016 5:53 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1) 
APPL(LITJES2C) NODE=1 <--- this is member(2) 
APPL(LITJES2T) NODE=2 
APPL(A6504JEA) NODE=4 


- Original Message - 

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters point 
to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's the 
latter you want, then you need a network connection and you need to ensure it 
is started before the systems will recognize each other. 

Adam 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, but 
now that you mention this, I really didn't need it since member 2 has only one 
specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114 
Office: 501.210.4705 
Cell: 501.514.4266 
cpvitu...@arkbluecross.com 
arkansasbluecross.com 





-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gerhard Adam 
Sent: Sunday, December 04, 2016 3:51 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor does 
it use the /*JOBPARM statement. If there is an initiator available, it will 
pick up the job. 

Sent from my iPhone 

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P 
> <cpvitu...@arkbluecross.com> 
wrote: 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has 
anyone seen this type of issue? my first time bringing 2 systems into a MAS, 
What am I missing ? 
> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 
> Arkansas Blue Cross and Blue Shield 
> IT Infrastructure Services 
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114 
> Office: 501.210.4705 
> Cell: 501.514.4266 
> cpvitu...@arkbluecross.com 
> arkansasbluecross.com 
> 
> 
> 
> IBM-MAIN 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> 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 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) or 
800-524-2621. 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) or 
800-524-2621. 

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

Re: new JES2 MAS jobs will not run on member 2

[Gerhard Adam]

Correct.  Those define NJE APPL's ...

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Monday, December 5, 2016 5:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1)
APPL(LITJES2C) NODE=1 <--- this is member(2)
APPL(LITJES2T) NODE=2
APPL(A6504JEA) NODE=4 


- Original Message -

From: "Gerhard Adam" <gada...@charter.net>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, December 5, 2016 7:40:12 AM
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters point 
to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's the 
latter you want, then you need a network connection and you need to ensure it 
is started before the systems will recognize each other. 

Adam 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vitullo, Carmen P
Sent: Sunday, December 4, 2016 2:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, but 
now that you mention this, I really didn't need it since member 2 has only one 
specific class 


Carmen Vitullo
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield
IT Infrastructure Services
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114
Office: 501.210.4705
Cell: 501.514.4266
cpvitu...@arkbluecross.com
arkansasbluecross.com 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gerhard Adam
Sent: Sunday, December 04, 2016 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2 

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor does 
it use the /*JOBPARM statement. If there is an initiator available, it will 
pick up the job. 

Sent from my iPhone 

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P 
> <cpvitu...@arkbluecross.com>
wrote: 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has
anyone seen this type of issue? my first time bringing 2 systems into a MAS, 
What am I missing ? 
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114
> Office: 501.210.4705
> Cell: 501.514.4266
> cpvitu...@arkbluecross.com
> arkansasbluecross.com
> 
> 
> 
> IBM-MAIN
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621. 
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621. 
> 
> --
> 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 

--
Privacy Information: http://privacynotice.net (data rate charges may apply) or 
800-524-2621. 

--
Privacy Information: http://privacynotice.net (data rate charges may apply) or 
800-524-2621. 

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


--
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

yep got ya ! from member(1)'s jes2parms 



MASDEF AUTOEMEM=ON, 
CKPTLOCK=ACTION, 
DORMANCY=(200,500), 
HOLD=50, 
LOCKOUT=1000, 
OWNMEMB=, 
RESTART=YES, 
SHARED=CHECK, 
SYNCTOL=120, 
XCFGRPNM=LITJES2 


MEMBER(1) NAME=SYSA 
MEMBER(2) NAME=SYSC 


from member(2)'s jes2parms 

MASDEF AUTOEMEM=ON, 
CKPTLOCK=ACTION, 
DORMANCY=(200,500), 
HOLD=50, 
LOCKOUT=1000, 
OWNMEMB=, 
RESTART=YES, 
SHARED=CHECK, 
SYNCTOL=120, 
XCFGRPNM=LITJES2 
/* */ 
/ MULTI-ACCESS SPOOL / 
/* */ 
MEMBER(1) NAME=SYSA 
MEMBER(2) NAME=SYSC 
thanks 




- Original Message -

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:53:22 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

One correction to my previous comment ... you also need a MASDEF parameter. 



-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, 
but now that you mention this, I really didn't need it since member 2 has 
only one specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114 
Office: 501.210.4705 
Cell: 501.514.4266 
cpvitu...@arkbluecross.com 
arkansasbluecross.com 





-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Gerhard Adam 
Sent: Sunday, December 04, 2016 3:51 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor 
does it use the /*JOBPARM statement. If there is an initiator available, it 
will pick up the job. 

Sent from my iPhone 

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com> 
wrote: 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has 
anyone seen this type of issue? my first time bringing 2 systems into a MAS, 
What am I missing ? 
> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 
> Arkansas Blue Cross and Blue Shield 
> IT Infrastructure Services 
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114 
> Office: 501.210.4705 
> Cell: 501.514.4266 
> cpvitu...@arkbluecross.com 
> arkansasbluecross.com 
> 
> 
> 
> IBM-MAIN 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> 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 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

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


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

Re: new JES2 MAS jobs will not run on member 2

[Gerhard Adam]

One correction to my previous comment ... you also need a MASDEF parameter.



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Vitullo, Carmen P
Sent: Sunday, December 4, 2016 2:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Easier for this situation to do an IPL, since both systems jes2parms were
needing change I  used a jobparm to direct the job to the correct system,
but now that you mention this, I really didn't need it since member 2 has
only one specific class


Carmen Vitullo
Lead Systems Programmer

Arkansas Blue Cross and Blue Shield
IT Infrastructure Services
515 West Pershing Blvd.
North Little Rock, Arkansas 72114
Office: 501.210.4705
Cell: 501.514.4266
cpvitu...@arkbluecross.com
arkansasbluecross.com 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Gerhard Adam
Sent: Sunday, December 04, 2016 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor
does it use the /*JOBPARM statement.  If there is an initiator available, it
will pick up the job.

Sent from my iPhone

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com>
wrote:
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has
anyone seen this type of issue? my first time bringing 2 systems into a MAS,
What am I missing ?
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd.
> North Little Rock, Arkansas 72114
> Office: 501.210.4705  
> Cell: 501.514.4266
> cpvitu...@arkbluecross.com
> arkansasbluecross.com
> 
> 
> 
> IBM-MAIN
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621.
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621.
> 
> --
> 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

--
Privacy Information: http://privacynotice.net (data rate charges may apply)
or 800-524-2621.

--
Privacy Information: http://privacynotice.net (data rate charges may apply)
or 800-524-2621.

--
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

and along those lines I think my other issue is I don't need 

APPL(LITJES2A) NODE=1 <-- this is member( 1) 
APPL(LITJES2C) NODE=1 <--- this is member(2) 
APPL(LITJES2T) NODE=2 
APPL(A6504JEA) NODE=4 


- Original Message -

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters 
point to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's 
the latter you want, then you need a network connection and you need to 
ensure it is started before the systems will recognize each other. 

Adam 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, 
but now that you mention this, I really didn't need it since member 2 has 
only one specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114 
Office: 501.210.4705 
Cell: 501.514.4266 
cpvitu...@arkbluecross.com 
arkansasbluecross.com 





-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Gerhard Adam 
Sent: Sunday, December 04, 2016 3:51 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor 
does it use the /*JOBPARM statement. If there is an initiator available, it 
will pick up the job. 

Sent from my iPhone 

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com> 
wrote: 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has 
anyone seen this type of issue? my first time bringing 2 systems into a MAS, 
What am I missing ? 
> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 
> Arkansas Blue Cross and Blue Shield 
> IT Infrastructure Services 
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114 
> Office: 501.210.4705 
> Cell: 501.514.4266 
> cpvitu...@arkbluecross.com 
> arkansasbluecross.com 
> 
> 
> 
> IBM-MAIN 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> 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 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

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


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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

you are absolutely right, I was not sure if these definitions were still 
needed. 
I'm not sure that would cause the jobs to get submitted but not run but I'm 
going to remove these defintions 
thank you 


- Original Message -

From: "Gerhard Adam" <gada...@charter.net> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 7:40:12 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

I'm sorry, but it seems that you're trying to set up an NJE node but you're 
calling it a MAS. 

A MAS doesn't require anything, except that the SPOOL and CKPT parameters 
point to the same data set. That's it. There's nothing else required. 

All these references to MEMBER and OWNMEMB are NJE definitions. If it's 
the latter you want, then you need a network connection and you need to 
ensure it is started before the systems will recognize each other. 

Adam 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Vitullo, Carmen P 
Sent: Sunday, December 4, 2016 2:25 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change I used a jobparm to direct the job to the correct system, 
but now that you mention this, I really didn't need it since member 2 has 
only one specific class 


Carmen Vitullo 
Lead Systems Programmer 

Arkansas Blue Cross and Blue Shield 
IT Infrastructure Services 
515 West Pershing Blvd. 
North Little Rock, Arkansas 72114 
Office: 501.210.4705 
Cell: 501.514.4266 
cpvitu...@arkbluecross.com 
arkansasbluecross.com 





-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Gerhard Adam 
Sent: Sunday, December 04, 2016 3:51 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor 
does it use the /*JOBPARM statement. If there is an initiator available, it 
will pick up the job. 

Sent from my iPhone 

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com> 
wrote: 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has 
anyone seen this type of issue? my first time bringing 2 systems into a MAS, 
What am I missing ? 
> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 
> Arkansas Blue Cross and Blue Shield 
> IT Infrastructure Services 
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114 
> Office: 501.210.4705 
> Cell: 501.514.4266 
> cpvitu...@arkbluecross.com 
> arkansasbluecross.com 
> 
> 
> 
> IBM-MAIN 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621. 
> 
> -- 
> 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 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621. 

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


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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

I see the test job i submitted on both systems (SDSF) input queue as I would 
expect, 

MASDEF AUTOEMEM=ON, 
CKPTLOCK=ACTION, 
DORMANCY=(200,500), 
HOLD=50, 
LOCKOUT=1000, 
OWNMEMB=, 
RESTART=YES, 
SHARED=CHECK, 
SYNCTOL=120, 
XCFGRPNM=LITJES2 <- both systems alike 



MEMBER(1) NAME=SYSA 
MEMBER(2) NAME=SYSC 






- Original Message -

From: "Elardus Engelbrecht" <elardus.engelbre...@sita.co.za> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 4:27:45 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Vitullo, Carmen P wrote: 

>Job sits on JES2 queue awaiting conversion - I've tried everything with node 
>and member statements and nothing works 
>If I submit from member 2 the jobs still sits in the input queue, now showing 
>the correct class, 

What input queue? What is your statements in that job: 

/*ROUTE XEQ  
/*JOBPARM SYSAFF= 

>Has anyone seen this type of issue? my first time bringing 2 systems into a 
>MAS, 
>What am I missing ? 

Did you tried out the replies from others? 

Show us your init statements for all the JES2 members, like this sample from 
that IBM KC webpage: 

MEMBER(1) NAME=SY01 
MASDEF OWNMEMB=SY01, 

Groete / Greetings 
Elardus Engelbrecht 

-- 
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: new JES2 MAS jobs will not run on member 2

[Gerhard Adam]

I'm sorry, but it seems that you're trying to set up an NJE node but you're
calling it a MAS.

A MAS doesn't require anything, except that the SPOOL and CKPT parameters
point to the same data set.  That's it.  There's nothing else required.

All these references to MEMBER and OWNMEMB are NJE definitions.   If it's
the latter you want, then you need a network connection and you need to
ensure it is started before the systems will recognize each other.

Adam

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Vitullo, Carmen P
Sent: Sunday, December 4, 2016 2:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Easier for this situation to do an IPL, since both systems jes2parms were
needing change I  used a jobparm to direct the job to the correct system,
but now that you mention this, I really didn't need it since member 2 has
only one specific class


Carmen Vitullo
Lead Systems Programmer

Arkansas Blue Cross and Blue Shield
IT Infrastructure Services
515 West Pershing Blvd.
North Little Rock, Arkansas 72114
Office: 501.210.4705
Cell: 501.514.4266
cpvitu...@arkbluecross.com
arkansasbluecross.com 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Gerhard Adam
Sent: Sunday, December 04, 2016 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor
does it use the /*JOBPARM statement.  If there is an initiator available, it
will pick up the job.

Sent from my iPhone

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com>
wrote:
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has
anyone seen this type of issue? my first time bringing 2 systems into a MAS,
What am I missing ?
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd.
> North Little Rock, Arkansas 72114
> Office: 501.210.4705  
> Cell: 501.514.4266
> cpvitu...@arkbluecross.com
> arkansasbluecross.com
> 
> 
> 
> IBM-MAIN
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621.
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may
> apply) or 800-524-2621.
> 
> --
> 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

--
Privacy Information: http://privacynotice.net (data rate charges may apply)
or 800-524-2621.

--
Privacy Information: http://privacynotice.net (data rate charges may apply)
or 800-524-2621.

--
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

good suggesting, I have to check that out thanks, another weekend for that :( 
Carmen 

- Original Message -

From: "Lucas Rosalen" <rosalen.lu...@gmail.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, December 5, 2016 1:20:38 AM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

Check if JES2 are running in Independent Mode. Can't remember the command 
for that. 

It had been suggested before, but I also think $DJ,LONG is the place to 
start 

On Dec 5, 2016 01:58, "John McKown" <john.archie.mck...@gmail.com> wrote: 

> On Sun, Dec 4, 2016 at 3:13 PM, Vitullo, Carmen P < 
> cpvitu...@arkbluecross.com> wrote: 
> 
> > I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> > finger issues, and an IPL and all OK 
> > Testing the batch submitting I submit job from member 1 to member 2 using 
> > /*JOBPARM S=memb2 
> > Job sits on JES2 queue awaiting conversion - I've tried everything with 
> > node and member statements and nothing works 
> > If I submit from member 2 the jobs still sits in the input queue, now 
> > showing the correct class, 
> > Has anyone seen this type of issue? my first time bringing 2 systems into 
> > a MAS, 
> > What am I missing ? 
> > 
> 
> ​Silly question: Is JES2 on the new system "started". I don't mean started 
> in the S JES2,SUB=MSTR sense. I mean, do you have a PARM=NOREQ in the JES2 
> proc so that it automatically starts processing once it's up? My first 
> thought is to just do a $S command to tell JES2 "wake up, fool!". 
> 
> Do you use scheduling environments. I saw this: 
> http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/ 
> com.ibm.zos.v2r1.hasa200/sjpc.htm 
> [quote] 
> 
> CNVT_SCHENV=HONOR|IGNORE 
> 
> Specifies whether the availability of a scheduling environment that is 
> associated with a job controls which member a job converts on. If 
> CNVT_SCHENV=HONOR is specified, then a job can only convert on a system 
> where the scheduling environment associated with the job is available. 
> 
> [quote/]​ 
> 
> ​Maybe try the command: $TJOBDEF,CNVT_SCHENV=IGNORE​ 
> 
> 
> 
> > Thanks 
> > 
> > 
> > 
> > Carmen Vitullo 
> > Lead Systems Programmer 
> > 
> > Arkansas Blue Cross and Blue Shield 
> > IT Infrastructure Services 
> > 515 West Pershing Blvd. 
> > North Little Rock, Arkansas 72114 
> > Office: 501.210.4705 
> > Cell: 501.514.4266 
> > 
> > 
> 
> -- 
> 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 


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

Re: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

:) I'm not sure how many times I issued the $S command thinking the simplest 
resolution, I even released all job classes issued from both systems, nothing 
nada, a class W (WLM ) job submitted from member 2 ran ok on member 1 
very strange. 
No scheduling environments here, I suggested setting these up initially but 
backed off until the MAS was working OK, so no SE's defined, no resources 
defined, I submitted a BR14 job class=b, the only class on member 2 and it just 
sat in the queue - $AJ did nothing. still scratching my head 
thanks John 
Carmen 


- Original Message -

From: "John McKown" <john.archie.mck...@gmail.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Sunday, December 4, 2016 6:57:37 PM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

On Sun, Dec 4, 2016 at 3:13 PM, Vitullo, Carmen P < 
cpvitu...@arkbluecross.com> wrote: 

> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK 
> Testing the batch submitting I submit job from member 1 to member 2 using 
> /*JOBPARM S=memb2 
> Job sits on JES2 queue awaiting conversion - I've tried everything with 
> node and member statements and nothing works 
> If I submit from member 2 the jobs still sits in the input queue, now 
> showing the correct class, 
> Has anyone seen this type of issue? my first time bringing 2 systems into 
> a MAS, 
> What am I missing ? 
> 

​Silly question: Is JES2 on the new system "started". I don't mean started 
in the S JES2,SUB=MSTR sense. I mean, do you have a PARM=NOREQ in the JES2 
proc so that it automatically starts processing once it's up? My first 
thought is to just do a $S command to tell JES2 "wake up, fool!". 

Do you use scheduling environments. I saw this: 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/sjpc.htm
 
[quote] 

CNVT_SCHENV=HONOR|IGNORE 

Specifies whether the availability of a scheduling environment that is 
associated with a job controls which member a job converts on. If 
CNVT_SCHENV=HONOR is specified, then a job can only convert on a system 
where the scheduling environment associated with the job is available. 

[quote/]​ 

​Maybe try the command: $TJOBDEF,CNVT_SCHENV=IGNORE​ 



> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 
> Arkansas Blue Cross and Blue Shield 
> IT Infrastructure Services 
> 515 West Pershing Blvd. 
> North Little Rock, Arkansas 72114 
> Office: 501.210.4705 
> Cell: 501.514.4266 
> 
> 

-- 
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: new JES2 MAS jobs will not run on member 2

[Carmen Vitullo]

backing away from this for now, I ran out of time and had to back out, some 
good take away's, displaying the job, I knew there was a jes2 command to see 
why a job was held up just in the flurry of issue I did not think of this, next 
time for sure 
to answer your questions: 
we had one one WLM init, new to both systems, no resources defined or tied to 
that INIT. 
no TPM or MODS, only exits are exit5 and exit1, my mermber definition in both 
systems jes2parms are; 

MEMBER(1) NAME=SYSA 
MEMBER(2) NAME=SYSC 



MASDEF AUTOEMEM=ON, 
CKPTLOCK=ACTION, 
DORMANCY=(200,500), 
HOLD=50, 
LOCKOUT=1000, 
OWNMEMB=, 
RESTART=YES, 
SHARED=CHECK, 
SYNCTOL=120, 
XCFGRPNM=LITJES2 
JES2 comes up no issues, jobclasses not held, queues not held, like i said jobs 
submitted from member 1 sit in the input queue class(*) awaiting conversion, I 
was thinking I had some INTRDR issues? but that didn't seem to jive. 
gone back to the operlogs and see if I can see any other issues. 
thanks Lizz 
Carmen 


- Original Message -

From: "Lizette Koehler" <stars...@mindspring.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Sunday, December 4, 2016 6:37:39 PM 
Subject: Re: new JES2 MAS jobs will not run on member 2 

First thing to do is $DJ#,LONG 

It should show you want Resource JES2 is waiting to show up. 

Next, do you have Thruput Manager by MVS Solutions, or zOSEM by Trident 
Software 

Or do you have any JES2 Mods that need resources? 

If you have SDSF issue the I against the Job in the Command Column 

Everything depends on what you have JES2 setup to do. 

Do you use WLM Inits? If so, are they started? 

Do you have MAS set up for both LPAR names? 

Try this link 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa300/masmem.htm
 


Lizette 


> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Vitullo, Carmen P 
> Sent: Sunday, December 04, 2016 2:13 PM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: new JES2 MAS jobs will not run on member 2 
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat finger 
> issues, and an IPL and all OK Testing the batch submitting I submit job from 
> member 1 to member 2 using /*JOBPARM S=memb2 Job sits on JES2 queue awaiting 
> conversion - I've tried everything with node and member statements and 
> nothing 
> works If I submit from member 2 the jobs still sits in the input queue, now 
> showing the correct class, Has anyone seen this type of issue? my first time 
> bringing 2 systems into a MAS, What am I missing ? 
> Thanks 
> 
> 
> 
> Carmen Vitullo 
> Lead Systems Programmer 
> 

-- 
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: new JES2 MAS jobs will not run on member 2

[Elardus Engelbrecht]

Vitullo, Carmen P wrote:

>Job sits on JES2 queue awaiting conversion - I've tried everything with node 
>and member statements and nothing works
>If I submit from member 2 the jobs still sits in the input queue, now showing 
>the correct class, 

What input queue? What is your statements in that job:

/*ROUTE XEQ   
/*JOBPARM SYSAFF= 

>Has anyone seen this type of issue? my first time bringing 2 systems into a 
>MAS,
>What am I missing ?

Did you tried out the replies from others?

Show us your init statements for all the JES2 members, like this sample from 
that IBM KC webpage:

MEMBER(1) NAME=SY01
MASDEF OWNMEMB=SY01,

Groete / Greetings
Elardus Engelbrecht

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

Re: new JES2 MAS jobs will not run on member 2

[Lucas Rosalen]

Check if JES2 are running in Independent Mode. Can't remember the command
for that.

It had been suggested before, but I also think $DJ,LONG is the place to
start

On Dec 5, 2016 01:58, "John McKown"  wrote:

> On Sun, Dec 4, 2016 at 3:13 PM, Vitullo, Carmen P <
> cpvitu...@arkbluecross.com> wrote:
>
> > I just brought 2 systems into a JES2MAS everything looked OK, some fat
> > finger issues, and an IPL and all OK
> > Testing the batch submitting I submit job from member 1 to member 2 using
> > /*JOBPARM S=memb2
> > Job sits on JES2 queue awaiting conversion - I've tried everything with
> > node and member statements and nothing works
> > If I submit from member 2 the jobs still sits in the input queue, now
> > showing the correct class,
> > Has anyone seen this type of issue? my first time bringing 2 systems into
> > a MAS,
> > What am I missing ?
> >
>
> ​Silly question: Is JES2 on the new system "started". I don't mean started
> in the S JES2,SUB=MSTR sense. I mean, do you have a PARM=NOREQ in the JES2
> proc so that it automatically starts processing once it's up? My first
> thought is to just do a $S command to tell JES2 "wake up, fool!".
>
> Do you use scheduling environments. I saw this:
> http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/
> com.ibm.zos.v2r1.hasa200/sjpc.htm
> [quote]
>
> CNVT_SCHENV=HONOR|IGNORE
>
> Specifies whether the availability of a scheduling environment that is
> associated with a job controls which member a job converts on. If
> CNVT_SCHENV=HONOR is specified, then a job can only convert on a system
> where the scheduling environment associated with the job is available.
>
> [quote/]​
>
> ​Maybe try the command: $TJOBDEF,CNVT_SCHENV=IGNORE​
>
>
>
> > Thanks
> >
> >
> >
> > Carmen Vitullo
> > Lead Systems Programmer
> >
> > Arkansas Blue Cross and Blue Shield
> > IT Infrastructure Services
> > 515 West Pershing Blvd.
> > North Little Rock, Arkansas 72114
> > Office: 501.210.4705
> > Cell: 501.514.4266
> >
> >
>
> --
> 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: new JES2 MAS jobs will not run on member 2

[John McKown]

On Sun, Dec 4, 2016 at 3:13 PM, Vitullo, Carmen P <
cpvitu...@arkbluecross.com> wrote:

> I just brought 2 systems into a JES2MAS everything looked OK, some fat
> finger issues, and an IPL and all OK
> Testing the batch submitting I submit job from member 1 to member 2 using
> /*JOBPARM S=memb2
> Job sits on JES2 queue awaiting conversion - I've tried everything with
> node and member statements and nothing works
> If I submit from member 2 the jobs still sits in the input queue, now
> showing the correct class,
> Has anyone seen this type of issue? my first time bringing 2 systems into
> a MAS,
> What am I missing ?
>

​Silly question: Is JES2 on the new system "started". I don't mean started
in the S JES2,SUB=MSTR sense. I mean, do you have a PARM=NOREQ in the JES2
proc so that it automatically starts processing once it's up? My first
thought is to just do a $S command to tell JES2 "wake up, fool!".

Do you use scheduling environments. I saw this:
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/sjpc.htm
[quote]

CNVT_SCHENV=HONOR|IGNORE

Specifies whether the availability of a scheduling environment that is
associated with a job controls which member a job converts on. If
CNVT_SCHENV=HONOR is specified, then a job can only convert on a system
where the scheduling environment associated with the job is available.

[quote/]​

​Maybe try the command: $TJOBDEF,CNVT_SCHENV=IGNORE​



> Thanks
>
>
>
> Carmen Vitullo
> Lead Systems Programmer
>
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd.
> North Little Rock, Arkansas 72114
> Office: 501.210.4705
> Cell: 501.514.4266
>
>

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

Re: new JES2 MAS jobs will not run on member 2

[Lizette Koehler]

First thing to do is $DJ#,LONG

It should show you want Resource JES2 is waiting to show up.

Next, do you have Thruput Manager by MVS Solutions, or zOSEM by Trident Software

Or do you have any JES2 Mods that need resources?

If you have SDSF issue the I against the Job in the Command Column

Everything depends on what you have JES2 setup to do.

Do you use WLM Inits?  If so, are they started?

Do you have MAS set up for both LPAR  names?

Try this link
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa300/masmem.htm


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vitullo, Carmen P
> Sent: Sunday, December 04, 2016 2:13 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: new JES2 MAS jobs will not run on member 2
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat finger
> issues, and an IPL and all OK Testing the batch submitting I submit job from
> member 1 to member 2 using /*JOBPARM S=memb2 Job sits on JES2 queue awaiting
> conversion - I've tried everything with node and member statements and nothing
> works If I submit from member 2 the jobs still sits in the input queue, now
> showing the correct class, Has anyone seen this type of issue? my first time
> bringing 2 systems into a MAS, What am I missing ?
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 

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

Re: new JES2 MAS jobs will not run on member 2

[Vitullo, Carmen P]

Easier for this situation to do an IPL, since both systems jes2parms were 
needing change
I  used a jobparm to direct the job to the correct system, but now that you 
mention this, I really didn't need it since member 2 has only one specific class


Carmen Vitullo
Lead Systems Programmer

Arkansas Blue Cross and Blue Shield
IT Infrastructure Services
515 West Pershing Blvd.
North Little Rock, Arkansas 72114
Office: 501.210.4705  
Cell: 501.514.4266
cpvitu...@arkbluecross.com
arkansasbluecross.com 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gerhard Adam
Sent: Sunday, December 04, 2016 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: new JES2 MAS jobs will not run on member 2

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor does 
it use the /*JOBPARM statement.  If there is an initiator available, it will 
pick up the job.

Sent from my iPhone

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P <cpvitu...@arkbluecross.com> 
> wrote:
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat 
> finger issues, and an IPL and all OK Testing the batch submitting I 
> submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits 
> on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works If I submit from member 2 the 
> jobs still sits in the input queue, now showing the correct class, Has anyone 
> seen this type of issue? my first time bringing 2 systems into a MAS, What am 
> I missing ?
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd.
> North Little Rock, Arkansas 72114
> Office: 501.210.4705  
> Cell: 501.514.4266
> cpvitu...@arkbluecross.com
> arkansasbluecross.com
> 
> 
> 
> IBM-MAIN
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621.
> 
> --
> Privacy Information: http://privacynotice.net (data rate charges may 
> apply) or 800-524-2621.
> 
> --
> 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

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621.

-- 
Privacy Information: http://privacynotice.net (data rate charges may apply) 
or 800-524-2621.

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

Re: new JES2 MAS jobs will not run on member 2

[Gerhard Adam]

Not sure what you're doing but a MAS certainly doesn't require an IPL, nor does 
it use the /*JOBPARM statement.  If there is an initiator available, it will 
pick up the job.

Sent from my iPhone

> On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P  
> wrote:
> 
> I just brought 2 systems into a JES2MAS everything looked OK, some fat finger 
> issues, and an IPL and all OK
> Testing the batch submitting I submit job from member 1 to member 2 using 
> /*JOBPARM S=memb2
> Job sits on JES2 queue awaiting conversion - I've tried everything with node 
> and member statements and nothing works
> If I submit from member 2 the jobs still sits in the input queue, now showing 
> the correct class, 
> Has anyone seen this type of issue? my first time bringing 2 systems into a 
> MAS,
> What am I missing ?
> Thanks
> 
> 
> 
> Carmen Vitullo
> Lead Systems Programmer
> 
> Arkansas Blue Cross and Blue Shield
> IT Infrastructure Services
> 515 West Pershing Blvd.
> North Little Rock, Arkansas 72114
> Office: 501.210.4705  
> Cell: 501.514.4266
> cpvitu...@arkbluecross.com
> arkansasbluecross.com 
> 
> 
> 
> IBM-MAIN
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may apply) 
> or 800-524-2621.
> 
> -- 
> Privacy Information: http://privacynotice.net (data rate charges may apply) 
> or 800-524-2621.
> 
> --
> 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