You can use /*ROUTE to route execution and/or SYSOUT to the local system, as well as remote systems. See Chapter 27 of the JCL Reference.
I believe this meets your stated requirement of no extra setup, a simple JCL change to test, and so on. Cheers,,,Steve Steven F. Conway, CISSP Hosting Services Division, Cloud Technology and Hosting Office, AO-DTS-CTHO-HSD z/OS Systems Support Phone: 703-295-1926 Mobile: 703-402-2650 [email protected] From: Paul Gilmartin <[email protected]> To: [email protected] Date: 03/24/2014 08:11 AM Subject: Re: Reflexivity (was: NJE Clarifications) Sent by: IBM Mainframe Discussion List <[email protected]> On Sun, 23 Mar 2014 20:12:49 -0400, Shmuel Metz (Seymour J.) wrote: > >I''m not asking a question; I'm pointing out a false analogy. "TCP/IP, >in contrast, is blessedly tolerant." makes no sense. >... >I'm asking in what sense TCP/IP is more tolerant than SNA. It's >certainly not in the ability to run multiple applications on the same >host, since SNA does that as well as TCP/IP does. > I can use FTP (a TCP/IP protocol) to submit jobs to localhost. I do not need multiple TCP/IP stacks to do this; only a conventional TCP/IP configuration. Generally, TCP/IP-based protocols such as FTP, HTTP, SSH, ... can communicate with localhost with no special configuration. The discussion here indicates that to use NJE to submit jobs or otherwise communicate with the local host requires some unusual configuration such as multiple instances of JES or multiple instances of NJE. So, I perceive TCP/IP as more tolerant; it has no bias against the local host. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
