Well, I thought about that, but I don't think that works either. JESA would have to know about both JES2's of the same name, and that still doesn't work(at least that is my understanding).
Someone correct me if I am wrong.....please. I think it would take JES2 -> JESA -> JESB -> JES2 _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Services [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of McKown, John Sent: Wednesday, December 01, 2010 9:45 AM To: [email protected] Subject: Re: spool to spool output transfer I don't think this is what you will want, but I'll just throw it out there anyway. Have you considered running two JES2 systems on system #1? The second JES2 would be, say, JESA. You could then NJE from JES2 to JESA on system #1, then NJE from JESA on system #1 to the JES2 on system #2. I'm not sure, but I think you'd need to turn off the "network path manager" in JESA. That's PATHMGR=NO on the NODE for JESA as defined in the other JES2 systems. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Jousma, David > Sent: Wednesday, December 01, 2010 8:21 AM > To: [email protected] > Subject: Re: spool to spool output transfer > > Thanks Gilbert. > > I have to be able to do the action to all output in a certain output > class via a interval driven process. > > I am still leaning toward the spool offload process. > > _________________________________________________________________ > Dave Jousma > Assistant Vice President, Mainframe Services > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G > p 616.653.8429 > f 616.653.8497 > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Gilbert Cardenas > Sent: Wednesday, December 01, 2010 9:13 AM > To: [email protected] > Subject: Re: spool to spool output transfer > > I had a similar requirement a few months back because for some reason, > they > have NJE locked up real tight around here. > > I created a rexx routine that basically ftps the spool file to the > intended lpar > by ip address. > > I initiate the process by performing an SE on the spool entry and then > typing > the Edit Macro/REXX at the command line. For lack of creativity, I > called my > script LPR and follow it by the destination name of the lpar such as > PROD, > DEV, QA etc. The esoteric name then gets converted by the > rexx to the ip > > address of the lpar and I can ftp to the same lpar where the > command was > > initiated if needed. > > I place a jcl skeleton (iebgener) and spool data into an mvs file > (RECFM=VBA,LRECL=300,BLKSIZE=27900) > and then FTP the file to the desired lpar to create the new > spool entry. > > QUOTE SITE FILETYP=JES > MODE B > TYPE E > QUOTE SITE JESLRECL=254 > PUT '||"'"FIL2FTP"'" > > Although it is not fully automated and the original characteristics of > the spool > entry are not kept, it has worked fine for all intents and purposes. > I'm positive there is much room for improvement but my only > requirement > was > to be able to print a report/sysout for programmers from lpars that do > not > have printers set up so it works just fine for me. Offloading to a > spool offload > dataset and then reloading was too cumbersome so this was much easier. > > > > On Tue, 30 Nov 2010 13:09:03 -0500, Jousma, David > <[email protected]> wrote: > > >All, > > > >Looking for ideas for doing spool to spool transfer of > output NOT using > >NJE. Issue is transferring output between two different > MAS-plex of > >the same node-name. NJE would work if multi-hopped, NODE-A connected > to > >NODE-B, NODE-B connected to NODE-C, and finally NODE-C > connects to the > >other NODE-A, but that is too many hops in my opinion. > > > >Looking for other creative, supportable methods to solve this. > Already > >thinking about: > > > >- Automated spool offload to dataset, FTP to remote site, spool > >reload > >- ?? > > > >Assumptions: > > > >- Maintain print characteristics > >- both spools have the same node name, that's why is not the first > >option > >- cannot change node name due to external customer connections > >- existing external connections are using Enterprise Extender, and > >the IP's of the separate hosts ARE different, so no conflict > externally. > > > > > > > > > > > >_________________________________________________________________ > >Dave Jousma > >Assistant Vice President, Mainframe Services > >[email protected] > >1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G > >p 616.653.8429 > >f 616.653.8497 > > > > > >This e-mail transmission contains information that is > confidential and > may be > privileged. > >It is intended only for the addressee(s) named above. If you receive > this e- > mail in error, > >please do not read, copy or disseminate it in any manner. If you are > not the > intended > >recipient, any disclosure, copying, distribution or use of > the contents > of this > information > >is prohibited. Please reply to the message immediately by > informing the > > sender that the > >message was misdirected. After replying, please erase it from your > computer > system. Your > >assistance in correcting this error is appreciated. > > > > > > > > > >------------------------------------------------------------- > --------- > >For IBM-MAIN subscribe / signoff / archive access instructions, > >send email to [email protected] with the message: GET > IBM-MAIN INFO > >Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > This e-mail transmission contains information that is > confidential and may be privileged. It is intended only for > the addressee(s) named above. If you receive this e-mail in > error, please do not read, copy or disseminate it in any > manner. If you are not the intended recipient, any > disclosure, copying, distribution or use of the contents of > this information is prohibited. Please reply to the message > immediately by informing the sender that the message was > misdirected. After replying, please erase it from your > computer system. Your assistance in correcting this error is > appreciated. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
