Could be. I've been fine with ICOMs among Monoplexes. So I didn't go there with NCF. You can do Batch Terminals via ICOM also.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jerry Whitteridge > Sent: Tuesday, February 14, 2017 11:28 AM > To: [email protected] > Subject: Re: EXTERNAL: Re: INTRDR and NJE > > NCF was a bundled part of CA-7 when we ran it. I'm not aware of additional > costs for running it. > > Jerry Whitteridge > Manager Mainframe Systems & Storage > Albertsons - Safeway Inc. > 623 869 5523 > Corporate Tieline - 85523 > > If you feel in control > you just aren't going fast enough. > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Gibney, Dave > Sent: Tuesday, February 14, 2017 12:27 PM > To: [email protected] > Subject: Re: EXTERNAL: Re: INTRDR and NJE > > But, I think costs more :) > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Jerry Whitteridge > > Sent: Tuesday, February 14, 2017 11:25 AM > > To: [email protected] > > Subject: Re: EXTERNAL: Re: INTRDR and NJE > > > > Also look into the use of CA-7 NCF which allows not sharing the COMMDS. > > > > Jerry Whitteridge > > Manager Mainframe Systems & Storage > > Albertsons - Safeway Inc. > > 623 869 5523 > > Corporate Tieline - 85523 > > > > If you feel in control > > you just aren't going fast enough. > > > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Gibney, Dave > > Sent: Tuesday, February 14, 2017 12:19 PM > > To: [email protected] > > Subject: EXTERNAL: Re: INTRDR and NJE > > > > It takes carefully shared DASD for the COMDS. You can run Additional > > ICOM instances in development. > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] On Behalf Of Jeffrey Holst > > > Sent: Tuesday, February 14, 2017 10:56 AM > > > 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 > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > ________________________________ > > Warning: All e-mail sent to this address will be received by the > > corporate e- mail system, and is subject to archival and review by > > someone other than the recipient. This e-mail may contain proprietary > > information and is intended only for the use of the intended > > recipient(s). If the reader of this message is not the intended > > recipient(s), you are notified that you have received this message in > > error and that any review, dissemination, distribution or copying of > > this message is strictly prohibited. If you have received this message in > error, please notify the sender immediately. > > ________________________________ > > > > ---------------------------------------------------------------------- > > 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 > ________________________________ > Warning: All e-mail sent to this address will be received by the corporate e- > mail system, and is subject to archival and review by someone other than the > recipient. This e-mail may contain proprietary information and is intended > only for the use of the intended recipient(s). If the reader of this message > is > not the intended recipient(s), you are notified that you have received this > message in error and that any review, dissemination, distribution or copying > of this message is strictly prohibited. If you have received this message in > error, please notify the sender immediately. > ________________________________ > > ---------------------------------------------------------------------- > 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
