> Doesn't JES3 speak TCP/IP these days? If so, use the TCP/IP NJE driver to > connect RSCS to > JES3.
I think it does (or it's trivial to use our NJE Bridge to provide an impedance matcher), but it sounds like the original setup has some kind of modified RJE exit on the JES3 side that sets the default for output to the JES system, not the originator of the job. In that case, you'd have to apply those mods to the NJE driver in JES3, which is not trivial. I think they are going to have to make some changes in the job stream to tell JES to dump the output locally, or make the mod to the NJE driver if they want the same functionality. It's not clear to me whether the specialized commands he's talking about are on the JES side or on the RSCS side, but in either case, they're looking at some refit.
