On Wed, Jan 28, 2009 at 10:35 AM, John Kelly <[email protected]> wrote: > <snip> > I cannot think of a way to do this. The JCL is expanded by the > "converter". > When you use a /*XEQ or /*XMIT, JES simply copies your in-stream JCL to > the > next z/OS system along the route to the destination z/OS system. > <unsnip> > > I'm not sure if I understand the issue but from my reading of it, I think > the JES2 SYSAFF parm might address the issue. With SYSAFF the conversion > and execute are done on the specified system.
Hi Jack, I think that's the problem... I want the conversion (expansion of the JCL proc) to be done on one system and THEN submit the expanded result to another system for actual execution. An example is... - A VM user runs an exec to process data from a magnetic tape. - The exec on VM knows on which MVS system to run the job based on tape vol ser. (Tapes with prefix A go to MVS A, tapes with prefix B go to MVS B, etc.) - The JCL PROC is maintained on MVS A - Send the JCL to MVS A with "something" that says, after expanding the PROC, execute the resulting job stream on MVS x This should include any DD */DD DATA inline data as well, and the same JOB card should be sent. As far as I can tell, that's (almost) exactly what /*XMIT does... thek iccker being that /*XMIT sends the JCL to the other system BEFORE expanding any JCL procs. DOH! :-) We do use SYSAFF in some cases... MVSA for exa,ple is actually two systems with (almost) shared "everything". Some jobs require the sysaffinity. But If I submit a JOB to MVSA (which could actually run on MVSA or MVSA1 if no SYSAFF is coded) and I specify SYSAFF=MVSB, which is in a different city.... will that accomplish what I want? I can try it easily enough. But I didn't think that would do it either. ---------------------------------------------------------------------- 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
