Re: SPAM: Re: Transfer reports from lpar to lpar
-snip I haven't been following this but has anyone suggested setting up a CTC between the LPAR's. The connection is setup over Escon channels. ---unsnip That will make a very reasonable physical connection; the next step is to configure software to actually use it. :-) I vote for a NJE connection, with routing JECL where appropriate. It's a LOT less prone to error than trying to do spool OFFLOAD and LOAD. Shared spool may be out for valid reasons. -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
Rick Fochtman wrote: That will make a very reasonable physical connection; the next step is to configure software to actually use it. :-) I vote for a NJE connection, with routing JECL where appropriate. It's a LOT less prone to error than trying to do spool OFFLOAD and LOAD. The OP indicates that he already has TCP/IP connectivity between all LPARs and FTP servers running on each. Therefore, the JES FTP interface should be available without any additional configuration. (Though I would highly recommend specifying JESINTERFACELEVEL 2 for the FTP server configurations.) -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
In a message dated 3/8/2008 11:03:41 A.M. Central Standard Time, r [EMAIL PROTECTED] writes: vote for a NJE connection, with routing JECL where appropriate. It's a LOT less prone to error than trying to do spool OFFLOAD and LOAD. Shared spool may be out for valid reasons. Guess if all you got is PFCSKs DEST='IP:ipaddr' might suffice w/o NJE quote JCL Reference DEST=destination The destination subparameter for JES2 is one of the following: LOCAL|ANYLOCAL 'IP:ipaddr' name | Nn | NnRm NnnR NnnnRmmm NRmm | NnRm | (node,remote) nodename.userid 'nodename.IP:ipaddr' end quote **It's Tax Time! Get tips, forms, and advice on AOL Money Finance. (http://money.aol.com/tax?NCID=aolprf000301) -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
On Sat, 8 Mar 2008 09:21:53 -0800, Edward Jaffe The OP indicates that he already has TCP/IP connectivity between all LPARs and FTP servers running on each. Therefore, the JES FTP interface should be available without any additional configuration. (Though I would highly recommend specifying JESINTERFACELEVEL 2 for the FTP server configurations.) -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ Thank you all for all the great ideas. Sounds like I am restricted to using FTP to transfer the report files. I looked up info on the JESINTERFACELEVEL 2 option and it appears this will allow me to pull reports/sysouts that do not match my userid or owner among other things. Does this parameter have to be coded in the TCPIP parameter library or can it be specified as a parameter in a batch jcl? Also can you ftp a report directly from one jes spool to another jes spool or do I have to put the report in an intermediary dataset and then ftp that file to the desired jes spool output? Regards, Gil. -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
On Sat, 8 Mar 2008 12:45:28 EST, Ed Finnell [EMAIL PROTECTED] wrote: Guess if all you got is PFCSKs DEST='IP:ipaddr' might suffice w/o NJE quote JCL Reference DEST=destination The destination subparameter for JES2 is one of the following: LOCAL|ANYLOCAL 'IP:ipaddr' name | Nn | NnRm NnnR NnnnRmmm NRmm | NnRm | (node,remote) nodename.userid 'nodename.IP:ipaddr' end quote I would like to use this option however, if I use the 'IP:ipaddr' the jcl reference states that a functional subsystem that can process IP-distributed data sets sends the data to the specified host system. Could you please translate what that means. I see the report in the output queue sitting with a dest of IP but how does the report get transmitted across? Regards, Gil. -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
Gilbert Cardenas wrote: On Sat, 8 Mar 2008 12:45:28 EST, Ed Finnell [EMAIL PROTECTED] wrote: Guess if all you got is PFCSKs DEST='IP:ipaddr' might suffice w/o NJE quote JCL Reference DEST=destination The destination subparameter for JES2 is one of the following: LOCAL|ANYLOCAL 'IP:ipaddr' name | Nn | NnRm NnnR NnnnRmmm NRmm | NnRm | (node,remote) nodename.userid 'nodename.IP:ipaddr' end quote I would like to use this option however, if I use the 'IP:ipaddr' the jcl reference states that a functional subsystem that can process IP-distributed data sets sends the data to the specified host system. Could you please translate what that means. I see the report in the output queue sitting with a dest of IP but how does the report get transmitted across? Regards, Gil. The remote still must be either a NJE node or a RJE node/workstation. -- 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
Re: SPAM: Re: Transfer reports from lpar to lpar
Setting up NJE really isn't that difficult. I can send you a short set of directions for how to set it up if you want. If your systems are both on the same physical processor (2 LPARs), and if it's a z-series box with an OSA/e or similar, it's even easier. I would bet that your systems people probably already have all of the pieces there, they just need to put them in place. Let me know. Brian -- 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
