You could have stepa run on systemA and have a step a1 submit a job via the internal reader which has a /*route exq to systemB, then have that job on systemB submit the rest of the job that needs to run on systemA (also via internal reader).
We had a product which we were in beta test back in 2005 which we were going to market that did this all internally, and it worked perfectly fine, but there wasn't much interest. There were very few things that really needed this capability. We provided several options, (wait and take up the initiator while the other job runs, end the job and requeue in the follow-on step when the second step finished, bounce the entire job back and forth, and a couple others I can't recall right now), but they were all for nothing because no one wanted to license it. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
