There are various methods of managing the enterprise, but the fundamental question is whether to share the communication data set. Having worked in a similar environment for a long time, I highly recommend *not* sharing the COMMDS but using one of the supported communication methods such as SNA (if you're inclined) or TCP/IP. Sharing any dataset across sysplex boundaries is highly problematic. Best to have a single COMMDS in the production sysplex and let the product orchestrate job submission.
In any case NJE comes into play for submitting jobs and handling output. These considerations apply equally to CA-7 and TWS. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Barkow, Eileen Sent: Tuesday, February 14, 2017 11:11 AM To: [email protected] Subject: (External):Re: INTRDR and NJE You can ftp to the lpar with SITE FILETYPE=JES SITE FILETYPE=JES PUT 'dataset.with.jobstream' -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jeffrey Holst Sent: Tuesday, February 14, 2017 1:56 PM To: [email protected] Subject: INTRDR and NJE We are planning to split our production sysplex (where we also do development) into a purely production sysplex and a development syslpex. What I am researching is how best to set up jobs that are submitted by our scheduler (CA-7) on the production system to run on the development sysplex. These would be infrastructure type jobs. CA-7 allows us to direct jobs to a particular internal reader DD statement for submission. One alternative is certainly to add the /*ROUTE XEQ statements to the JCL to be submitted via NJE. A second alternative would be to code a CA-7 job submission exit that adds the /*ROUTE XEQ statement when appropriate. What I wonder is whether there is some combination of internal reader DD statements and JES2 JECL to produce this same affect for jobs to be submitted via NJE. That would be the less effort than the alternatives. If I specify something like //INTRDR1 DD SYSOUT=(A,INTRDR),DEST=NODE will that send the job to NODE to be executed? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ________________________________ This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. ---------------------------------------------------------------------- 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
