We do this sort of thing all the time, using XCOM, a CA product that does
FTP-like things. Here's the sequence of events:
1. JOB-A on LPAR-A runs and does:
a. iefbr14 to delete a dataset-a that will receive output from LPAR-B.
b. sends JOB-B to LPAR-B.
2. JOB-B runs on LPAR-B and does:
a. whatever you wish it to do, writing its output to dataset-b.
b. sends dataset-b back to LPAR-A, calling it dataset-a.
Good for all sorts of things, cross-LPARs.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Chase, John
Sent: Monday, December 05, 2005 11:38 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Kick off a job on a different LPAR.
> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of McKown, John
>
> > -----Original Message-----
> >
> > I would like to be able to allow usesr on the Production LPAR to
> > submit a job containing SFTP commands and some how have it run on
> > the Test LPAR and return the results of the SFTP run (which ran on
> > the Test LPAR) to the user on the Production LPAR.
>
> plain, old ftp?
Another way, assuming the two LPARs are "connected" via NJE and are running
JES2:
//JOBNAME JOB ....
/*XEQ TEST <-- routes job to specified system (node)
// <rest of job >
-jc-
----------------------------------------------------------------------
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
