Share Spool
Question on node numbers being defined... understand the NJEDEF.. OWNNODE s/b same on both JES2parms But in the case of the NODE(nn)>> are they not still defined as seperate NODEnumber and NAME being the name of that system ? same question on the TCPip NJE setup ..are the names and node number still used as before ... -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
JES2-Share Spool
Have a question ... Just trying Shared Spool between (2) lpars..(A) and (B) lpars Have a NJE connection from (T) lpar to (A)... I route a output from (T) lpar to (A)lpar... I cannot see the out unless I do a ST command in SDSF ... ? and The output does not retain it's original owner information ...?? Is there some NJEnode definitions or OUTput definition I'm missing or?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
Ron asked: >understand the NJEDEF.. OWNNODE s/b same on both JES2parms >But in the case of the NODE(nn)>> are they not still defined as seperate >NODEnumber and NAME being the name of that system ? I'm not certain what you are asking, but I'll give it a shot. The entire MAS is one JES2 node. NJEDEF specifies the OWNNODE number for the MAS. NODE (nn) specifies the name of the MAS. Each member of the MAS should have the same name and node number for the MAS. Each member of the MAS is defined by a MEMBER(nn) NAME=. So, each member of the MAS has its own member number and name. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
Martin... The MEMBER (nn) is just a number or the node number relationship? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
MASDEF DORMANCY=(070,600), HOLD=60, LOCKOUT=1000, OWNMEMB=SYSA, SHARED=CHECK, XCFGRPNM=SYSX,CF, SYNCTOL=240 MEMBER(1) NAME=SYSA>>> MEMBER(2) NAME=SYSD >>> can this be or should it be the same name as I have in old setup?>> sing SMFid as for node number--kept same NJEDEF OWNNODE=1 >> same on both def's in jes But still have old NODE(nn) defined for old system when not shared spool ..>> guess that can be eliminated ? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
>The MEMBER (nn) is just a number or the node number relationship? Member and node are two separate numbers. A JES2 node can have multiple members - thus shared spool. Each member has a different number. The MEMBER statement specifies which number slot is used by each system sharing the spool. >MASDEF DORMANCY=(070,600), > HOLD=60, > LOCKOUT=1000, > OWNMEMB=SYSA, > SHARED=CHECK, > XCFGRPNM=SYSX,CF, > SYNCTOL=240 >MEMBER(1) NAME=SYSA>>> >MEMBER(2) NAME=SYSD >>> can this be or should it be the same >name as I have in old setup?>> sing SMFid as for node number--kept same > NJEDEF OWNNODE=1 >> same on both def's in jes In your case Both systems should specify OWNNODE=1. On the MASDEF statement for SYSA, you should have OWNMEMB=SYSA, and on the MASDEF for SYSD you should have OWNMEMB=SYSD. Each system in the MAS identifies its own name to the MAS in this way. (If not specified, then OWNMEMB defaults to the SMF ID). The SPOOLDEF and CKPTDEF statements for both systems should also match. Each member of the MAS has to have a different member number. So, both members should have the same pair of MEMBER statements in their parameters. The MEMBER(1) NAME=SYSA and MEMBER(2) NAME=SYSD identify which member number is assigned to each of the member names. JES2 can take a lot of defaults - like using SMF ID for the member name, but I prefer to specify the MAS parameters explicitly, so whenever I have a question about how it works, I'm not doing research about how each parameter might have defaulted. >But still have old NODE(nn) defined for old system when not shared spool >..>> guess that can be eliminated ? That depends on whether or not NODE(nn) still exists, and, if so, whether or not you want to your MAS communicate with it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
Martin Thanks---starting to make sense now... except--lol NODE(nn) since it was originally setup non-shared...and the NAME= not matching anything other than the APPL and LOGON for that system.. would it have any use ?? Since NODE(1)>> OWNNODE is now both the same ?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
>NODE(nn) since it was originally setup non-shared...and the NAME= not >matching anything other than the APPL and LOGON for that system.. >would it have any use ?? >Since NODE(1)>> OWNNODE is now both the same ?? Yes. Node(1) tells JES2 which what symbolic name you want for the MAS. It's been a long time since I dealt with connecting JES2 networks, but as I remember it, the name for your node should be relatively unique if you ever expect to connect multiple networks together - more important when those networks belong to other organizations than when they belong to a single conglomerate. You can avoid a lot of confusion that way. My personal recommendation for node names is to use the company name or stock id along with a numeric or location reference. Your chances of running into duplicate network names are greatly reduced. For example, suppose you choose 'SYSA' as your node name and VTAM APPLID. Then suppose CompanyX wants to connect to your network to allow JES2 to send reports to them directly, but CompanyX also selected 'SYSA' as their node name and APPLID. One of you would have to change. Not so bad with single-node networks. Worse, suppose you already connected to dozens of other JES2 networks owned by other companies, and your node name and applid were 'NEWYORK'. Then you run into CompanyZ, which also has multiple connected JES2 systems with many other companies, one of which also elected to use the node name 'NEWYORK'. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
ok--following is what I intended but guess I'm still missing it... intent is being able to use N9 to still route sysout from opther lpar's besides N1 so do I need or can NODE(9) have same name as NODE(1) ? system SYSA > LOGON(1) APPLID=SYSA MASDEF OWNMEMB=SYSA9 >>> smfid SHARED=CHECK, XCFGRPNM=SYSA MEMBER(1) NAME=SYSA9 MEMBER(2) NAME=SYSD NJEDEF OWNNODE=1 NODE(1) NAME=SYSA NODE(9) NAME=SYSD>> to join in shared spool APPL(SYSD) NODE=9 >> >> -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
>ok--following is what I intended but guess I'm still missing it... >intent is being able to use N9 to still route sysout from opther lpar's >besides N1 so do I need or can NODE(9) have same name as NODE(1) ? >system SYSA > >LOGON(1) APPLID=SYSA >MASDEF > OWNMEMB=SYSA9 >>> smfid >SHARED=CHECK, >XCFGRPNM=SYSA >MEMBER(1) NAME=SYSA9 >MEMBER(2) NAME=SYSD >NJEDEF >OWNNODE=1 >NODE(1) NAME=SYSA >NODE(9) NAME=SYSD>> to join in shared spool >APPL(SYSD) NODE=9 >> First, all the members sharing the same spool and checkpoint are in the same MAS system. That's "shared spool". That collection of JES2 instances sharing the MAS is a single JES2 node. Therefore, if SYSA and SYSD are in the same MAS, then they are the same node. That node has one node number. Only one. It's either node 1 or node 9, but not both. If you have other LPARs not sharing the MAS that want to communicate with the MAS and currently refer to it by the node number, 'N9" in this case, then make the entire MAS node number 9. Both SYSA and SYSD being part of the shared spool, will both be node 9. Using your member statements, SYSA would be member 1 of node 9, and SYSD would be member 2 of node 9. With that setup, when you route output from other nodes to N9, the output is placed into NODE 9's shared spool, and can be accessed by both SYSA and SYSD. Externally, other NJE systems see the MAS as a single node. Whether they connect to SYSA or to SYSD is determined by the APPLID they connect to. For example, if SYSX connects to APPLID SYSA, it is connected to member 1 of NODE 9. If SYSX instead connects to APPLID SYSD, it is still connected to NODE 9, but to member 2 instead. Whether external systems connect via SYSA or SYSD makes no difference when the output arrives at node 9 because it's shared spool - shared between members SYSA and SYSD. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Share Spool
Thanks Martingot it... -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: JES2-Share Spool
Did following in SDSF to see it correctlybut how can I make this a default function>>> not understanding?? >> /$tjnn,sysaff=(*,ind) >>> - Forwarded by Ron Wells/AGFS/AGFin on 05/19/2009 02:54 PM - Ron Wells/AGFS/AGFin 05/19/2009 02:10 PM To IBM Mainframe Discussion List cc Subject JES2-Share Spool Have a question ... Just trying Shared Spool between (2) lpars..(A) and (B) lpars Have a NJE connection from (T) lpar to (A)... I route a output from (T) lpar to (A)lpar... I cannot see the out unless I do a ST command in SDSF ... ? and The output does not retain it's original owner information ...?? Is there some NJEnode definitions or OUTput definition I'm missing or?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: JES2-Share Spool
could it be something in isfparms for sdsf?? - Forwarded by Ron Wells/AGFS/AGFin on 05/19/2009 03:53 PM - Ron Wells/AGFS/AGFin 05/19/2009 02:56 PM To IBM Mainframe Discussion List cc Subject Fw: JES2-Share Spool Did following in SDSF to see it correctlybut how can I make this a default function>>> not understanding?? >> /$tjnn,sysaff=(*,ind) >>> - Forwarded by Ron Wells/AGFS/AGFin on 05/19/2009 02:54 PM - Ron Wells/AGFS/AGFin 05/19/2009 02:10 PM To IBM Mainframe Discussion List cc Subject JES2-Share Spool Have a question ... Just trying Shared Spool between (2) lpars..(A) and (B) lpars Have a NJE connection from (T) lpar to (A)... I route a output from (T) lpar to (A)lpar... I cannot see the out unless I do a ST command in SDSF ... ? and The output does not retain it's original owner information ...?? Is there some NJEnode definitions or OUTput definition I'm missing or?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
Ron Wells pisze: Have a question ... Just trying Shared Spool between (2) lpars..(A) and (B) lpars You mean sysplex? Have a NJE connection from (T) lpar to (A)... I route a output from (T) lpar to (A)lpar... I cannot see the out unless I do a ST command in SDSF ... ? and The output does not retain it's original owner information ...?? It depends on NODES class profiles in RACF. Is there some NJEnode definitions or OUTput definition I'm missing or?? Maybe, you didn't presented us any of them, so it's hard to determine what is missing/incorrect -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: JES2-Share Spool
Below are the njedef's for the lpar's in question...as for racf ?? the isfparm is still in use and those follow.. lpar(a) >> LOGON(1) APPLID=LPARA, LOG=NO, TRACEIO=NO, PASSWORD= LOGON(2) APPLID=JES2, LOG=NO, TRACEIO=NO, PASSWORD= > MASDEF DORMANCY=(070,600), HOLD=60, LOCKOUT=1000, OWNMEMB=SMFA, SHARED=CHECK, XCFGRPNM=LPARA, SYNCTOL=240 MEMBER(1) NAME=SMFA MEMBER(2) NAME=SMFB > NJEDEF DELAY=120, JRNUM=4, JTNUM=4, LINENUM=30, NODENUM=30, OWNNODE=1, MAXHOP=0, PATH=1, RESTMAX=800, RESTNODE=100, RESTTOL=0, SRNUM=4, STNUM=4, TIMETOL=20 > NODE(1) NAME=LPARA, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO NODE(6) NAME=LPART, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO > APPL(LPARB) NODE=1 APPL(LPART) NODE=6 >>>> lpar(b) >> LOGON(1) APPLID=LPARB, LOG=NO, TRACEIO=NO, PASSWORD= LOGON(2) APPLID=JES2, LOG=NO, TRACEIO=NO, PASSWORD= > MASDEF DORMANCY=(070,600) HOLD=60, LOCKOUT=1000, OWNMEMB=SMFB, SHARED=CHECK, XCFGRPNM=LPARA, SYNCTOL=240 MEMBER(1) NAME=SMFA, MEMBER(2) NAME=SMFB > NJEDEF DELAY=120, JRNUM=4, JTNUM=4, LINENUM=30, NODENUM=30, OWNNODE=1, MAXHOP=0, PATH=1, RESTMAX=800, RESTNODE=100, RESTTOL=0, SRNUM=4, STNUM=4, TIMETOL=20 > NODE(1) NAME=LPARA, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO NODE(6) NAME=LPART, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO > APPL(LPARA) NODE=1 APPL(LPART) NODE=6 APPL(LPARB) NODE=1 >>> lpart > LOGON(1) APPLID=LPART, LOG=NO, TRACEIO=NO, PASSWORD= LOGON(2) APPLID=JES2, LOG=NO, TRACEIO=NO, PASSWORD= > MASDEF DORMANCY=(070,600), HOLD=60, LOCKOUT=1000, OWNMEMB=SMFT, SHARED=CHECK, XCFGRPNM=LPART, SYNCTOL=240 MEMBER(1) NAME=SMFT > NJEDEF DELAY=120, JRNUM=4, JTNUM=4, LINENUM=30, NODENUM=30, OWNNODE=6, MAXHOP=0, PATH=1, RESTMAX=800, RESTNODE=100, RESTTOL=0, SRNUM=4, STNUM=4, TIMETOL=20 > NODE(1) NAME=LPARA, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO NODE(6) NAME=LPART, COMPACT=0, AUTH=(DEVICE=YES, JOB=YES, SYSTEM=YES, NET=YES), LOGMODE=, PATHMGR=YES, PRIVATE=NO, REST=0, TRACE=NO, TRANSMIT=BOTH, RECEIVE=BOTH, HOLD=NONE, PENCRYPT=NO > APPL(LPARA) NODE=1 APPL(LPART) NODE=6 APPL(LPARB) NODE=1 - Forwarded by Ron Wells/AGFS/AGFin on 05/20/2009 08:23 AM - "R.S." Sent by: IBM Mainframe Discussion List 05/20/2009 05:32 AM Please respond to IBM Mainframe Discussion List To IBM-MAIN@bama.ua.edu cc Subject Re: JES2-Share Spool Ron Wells pisze: > Have a question ... > > Just trying Shared Spool between (2) lpars..(A) and (B) lpars You mean sysplex? > Have a NJE connection from (T) lpar to (A)... > > I route a output from (T) lpar to (A)lpar... I cannot see the out unless I > do a ST command in SDSF ... ?
Re: JES2-Share Spool
ok---found something going on >>> generated output on lpart .. xmit to N1 > lpara can not see it in O or H ... must use ST issue $TJn,SYSAFF=(*,IND) >> now I can see it and purge or retransmit... if I retransmit to node it came from I run into same problem... so SYSAFF is key to my problem and not understanding what nailed me -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
anyone else have any ideas..? think I'm missing something stupid can attach jes2parm's---offline--if someone else wants to look at setup... -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
On Thu, 21 May 2009 08:32:19 -0500, Ron Wells wrote: >anyone else have any ideas..? >think I'm missing something stupid > >can attach jes2parm's---offline--if someone else wants to look at setup... I haven't been following this thread, but I looked back at one post and saw a reference to "ind". Is one of these systems in independent mode, i.e. $TMEMBER(),IND=YES ? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: JES2-Share Spool
They all(systems) show IND=YES on $DMEMBER .. Was told I had to have this so I do not need to specify SYSAFF in jcl on job submission .. have following in JES2PARMS on all the systems .. $T MEMBER(&SYSNAME),IND=Y $TINTRDR,SYSAFF=(&SYSNAME,IND) - Forwarded by Ron Wells/AGFS/AGFin on 05/21/2009 09:14 AM - Mark Zelden Sent by: IBM Mainframe Discussion List 05/21/2009 09:04 AM Please respond to IBM Mainframe Discussion List To IBM-MAIN@bama.ua.edu cc Subject Re: JES2-Share Spool On Thu, 21 May 2009 08:32:19 -0500, Ron Wells wrote: >anyone else have any ideas..? >think I'm missing something stupid > >can attach jes2parm's---offline--if someone else wants to look at setup... I haven't been following this thread, but I looked back at one post and saw a reference to "ind". Is one of these systems in independent mode, i.e. $TMEMBER(),IND=YES ? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
Ron, you initially said you were trying to set up shared spool b/w A and B, yet you are trying to access the output from T? I think you won't be able to access that output from T, unless it's in the MAS. You can ship it over and back (via NJE), but not look at the output on the spool from a non-mas system. Can you paste the output of $DMEMB(*) Mary Anne On Thu, May 21, 2009 at 9:32 AM, Ron Wells wrote: > anyone else have any ideas..? > think I'm missing something stupid > > can attach jes2parm's---offline--if someone else wants to look at setup... > > -- > Email Disclaimer > This E-mail contains confidential information belonging to the sender, > which may be legally privileged information. This information is intended > only for the use of the individual or entity addressed above. If you are > not the intended recipient, or an employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > disclosure, copying, distribution, or the taking of any action in reliance > on the contents of the E-mail or attached files is strictly prohibited. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: JES2-Share Spool
A time back last year when we initally tested this in the list..>> can not remember who.. Concern was job's being submitted and which system they was to run on.. Did not want to change/add /*jobparm nor wanted an exit to maintain... was told this would do it...and both $T commands was reccomended.. So>>> your saying do not specify IND on the INTRDR...or better yet just setit in jes2parm.. as for $Tmember---leave it out as well? - Forwarded by Ron Wells/AGFS/AGFin on 05/21/2009 09:51 AM - Mark Zelden Sent by: IBM Mainframe Discussion List 05/21/2009 09:49 AM Please respond to IBM Mainframe Discussion List To IBM-MAIN@bama.ua.edu cc Subject Re: Fw: JES2-Share Spool On Thu, 21 May 2009 09:16:49 -0500, Ron Wells wrote: >They all(systems) show IND=YES on $DMEMBER .. >Was told I had to have this so I do not need to specify SYSAFF in jcl on >job submission .. Was told by who? Independent mode is really a testing facility. Typically you set this on only one member of the MAS. Why share spool at all if you want to run that way all the time? I don't know if this has anything to do with your original problem or not since I still haven't gone back and looked at all the details... > >have following in JES2PARMS on all the systems .. > >$T MEMBER(&SYSNAME),IND=Y >$TINTRDR,SYSAFF=(&SYSNAME,IND) I think using $TINTRDR,SYSAFF=(&SYSNAME) without IND will do what you want. Or better than putting the $T, why not code INTRDR that way to start. Again why are you sharing spool if you want all the separation? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
Ann Sharing spool between A and B.. transfering job's/output between T to A which is where problem occured...also transfering back... from what I was just informed---the way I have it is all wet... all systems A/B and T are set with IND=YES on member and intrdr...which is the problem.. did not want to add/change jcl or deal with an exit thought>> was told a time back last year>> the following would do what I wanted.. $T MEMBER(&SYSNAME),IND=Y $TINTRDR,SYSAFF=(&SYSNAME,IND) -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
Ron, so you want all jobs submitted on T to run on A or B, then come back to the T output queue? And you want to be able to see them during execution, but not via ST, via DA? Mary Anne On Thu, May 21, 2009 at 10:59 AM, Ron Wells wrote: > Ann > > Sharing spool between A and B.. > transfering job's/output between T to A which is where problem > occured...also transfering back... > from what I was just informed---the way I have it is all wet... > > all systems A/B and T are set with IND=YES on member and intrdr...which is > the problem.. > > did not want to add/change jcl or deal with an exit thought>> was told > a time back last year>> the following would do what I wanted.. > > $T MEMBER(&SYSNAME),IND=Y > $TINTRDR,SYSAFF=(&SYSNAME,IND) > > -- > Email Disclaimer > This E-mail contains confidential information belonging to the sender, > which may be legally privileged information. This information is intended > only for the use of the individual or entity addressed above. If you are > not the intended recipient, or an employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > disclosure, copying, distribution, or the taking of any action in reliance > on the contents of the E-mail or attached files is strictly prohibited. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
Ann No---want jobs sub'd on A to run on A B to run on B T to run on T Gather only real way to seperate classes or add /*jobparm or exit .. -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2-Share Spool
On Thu, 21 May 2009 10:30:01 -0500, Ron Wells wrote: >Ann > >No---want jobs sub'd on A to run on A >B to run on B >T to run on T > >Gather only real way to seperate classes or add /*jobparm or exit .. > Hi Ron, If you are trying to accomplish the above for jobs that don't have SYSAFF coded on their /*jobparm cards then you can issue or put in your JES2 parms $TINTRDR,SYSAFF=member name on each lpar If you have system symbolic that matches your JES2 member name (for us we match &SYSNAME and JES2 member name) you can issue $TINTRDR,SYSAFF=&SYSNAME If the problem is that you want to override jobs that specify SYSAFF on the JOBPARM the you are correct that you would need an exit. Doug -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
On Thu, 21 May 2009 09:16:49 -0500, Ron Wells wrote: >They all(systems) show IND=YES on $DMEMBER .. >Was told I had to have this so I do not need to specify SYSAFF in jcl on >job submission .. Was told by who? Independent mode is really a testing facility. Typically you set this on only one member of the MAS. Why share spool at all if you want to run that way all the time? I don't know if this has anything to do with your original problem or not since I still haven't gone back and looked at all the details... > >have following in JES2PARMS on all the systems .. > >$T MEMBER(&SYSNAME),IND=Y >$TINTRDR,SYSAFF=(&SYSNAME,IND) I think using $TINTRDR,SYSAFF=(&SYSNAME) without IND will do what you want. Or better than putting the $T, why not code INTRDR that way to start. Again why are you sharing spool if you want all the separation? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
On Thu, 21 May 2009 09:55:34 -0500, Ron Wells wrote: >A time back last year when we initally tested this in the list..>> can not >remember who.. Keyword being "tested". As I said, IND mode is good for testing or when you first implement shared spool and you would typically set that on the new member you just added. The only times I have used it in the last 10 years were for implementing a new LPAR with a shared spool environment and I used it for quite a while in one system of a 2 LPAR sandbox MAS when I was re-writing / testing JES2 exits that were required when we upgraded from z/OS 1.6 to z/OS 1.8 (the changes were required for z/OS 1.7, which we skipped). >Concern was job's being submitted and which system they was to run on.. >Did not want to change/add /*jobparm nor wanted an exit to maintain... >was told this would do it...and both $T commands was reccomended.. > >So>>> your saying do not specify IND on the INTRDR...or better yet just >setit in jes2parm.. >as for $Tmember---leave it out as well? If you set it on INTRDR, then you don't need to change it with $T. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
thsnks---mark -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
--: A time back last year when we initally tested this in the list..>> can not remember who.. Concern was job's being submitted and which system they was to run on.. Did not want to change/add /*jobparm nor wanted an exit to maintain... was told this would do it...and both $T commands was reccomended.. So>>> your saying do not specify IND on the INTRDR...or better yet just setit in jes2parm.. as for $Tmember---leave it out as well? --- Many moons ago, I fought the same battle. Our solution was to use different initiator classes on the various LPARs sharing the spool. Since all the images shared the same DASD, we didn't care which node did the conversion of JCL, etc. Have you considered this, as opposed to IND parms within JES2? -- Rick -- Remember that if you’re not the lead dog, the view never changes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
Rick/Doug/Mark/Ann Thanks for your help...think we got it going now Only one problem remaining maybe it will trigger an answer... When I transfer from one system...Test to Prod I see output---no problembut the owner field is set to ?? Checked with security guy and ID's valid..and tried with mine as well same owner id.. any ideas..? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
On Thu, 21 May 2009 12:52:33 -0500, Ron Wells wrote: >Rick/Doug/Mark/Ann > >Thanks for your help...think we got it going now > >Only one problem remaining maybe it will trigger an answer... > >When I transfer from one system...Test to Prod I see output---no >problembut the owner field is set to ?? >Checked with security guy and ID's valid..and tried with mine as well >same owner id.. > >any ideas..? > Have a look at the RACF Admin Guide. Chapter 17 in the manual I am looking at right now (z/OS 1.9). If you are using a different security package, look at the doc related to JES2 nodes / NJE, etc. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fw: JES2-Share Spool
Thanks Mark Racf guy seen what was missing as you mentioned.corrected now... thanks again -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
