That would probably work for output, but if they're used to job progress messages on VM from JES via NJE msgs, that would break message routing, I think. Worth a try, though.
Rob's idea is intriguing; the approach of letting a service machine mung the JCL into IEBGENR and submitting it via the internal rdr is clever (and gets the text processing work out of assembler and into REXX and Pipes, which would be double-plus good in terms of easy maintainability as well as getting rid of a JES exit or mod). If the //*MAIN ORG idea works, that'd be the way to implement it. Whatever they do, though, I think those custom commands are probably toast. ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Friday, September 26, 2008 1:33 PM To: [email protected] Subject: Re: VM RSCS as RJP to JES3, replace current process and last 3745. I'm not sure what the 'JL' command is but it sounds like you want your job sysout, jesmsg, etc. to stay over on the JES3 side. You might try editing the jcl on the VM side to include a //*MAIN ORG statement to override the origin similar to //*MAIN ORG=jes3node.LOCAL where jes3node is your zOS BDT node name. You can use OUTPUT or FORMAT statements as well but //*MAIN ORG might be best. I don't know what 'JL' is but we send jobs and data from zVM to zOS sendimng output to various vendor softcopy and output storage products. Some need special output classes. But if your current jcl works from VM with RJE then NJE may work fine if you try options with //*MAIN ORG. Always glad to see someone else using JES3.
