Paul, Thanks. That is similar to we do with our 'Dependencies'. The difference is that our jobs can have several 'dependencies'. Jobs can have only 1 SCHENV and 1 WITH. This gives less flexibility, e.g. for jobs that need IMS or DB2 or IMS+DB2.
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Feller, Paul > Sent: 29 January, 2019 13:50 > To: [email protected] > Subject: Re: SYSAFF and SCHENV [EXTERNAL] > > Kees, we do this several ways. Users can add the SCHENV to their jobs > if they know what resource they will need. As an example if they know > they are using MQ in their job they will add the needed SCHENV to their > job. We also add SCHENV during processing in JES2 exit 60. An example > we will look at the user ID the job was submitted under and assign a > default SCHENV to the job if none was set in the JCL. Now this default > SCHENV might get overwritten if we find the job also has SAS in it. > > Thanks.. > > Paul Feller > AGT Mainframe Technical Support > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Vernooij, Kees (ITOP NM) - KLM > Sent: Tuesday, January 29, 2019 1:22 AM > To: [email protected] > Subject: Re: SYSAFF and SCHENV [EXTERNAL] > > We have a home written utility that does this. > > We are looking at replacing this by standard features and besides > SCHENVs, the SCHEDULE parameter WITH is a good new candidate. > > How do you add a SCHENV to a job? Does the user/submittor do this or is > it done automatically? > > Kees. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Feller, Paul > > Sent: 29 January, 2019 5:04 > > To: [email protected] > > Subject: Re: SYSAFF and SCHENV [EXTERNAL] > > > > We use SCHENV to direct jobs to different lpars related to MQ, DB2, > > IMS, SAS, Connect Direct and other miscellaneous resources. > > > > Thanks.. > > > > Paul Feller > > AGT Mainframe Technical Support > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Jesse 1 Robinson > > Sent: Monday, January 28, 2019 4:13 PM > > To: [email protected] > > Subject: Re: SYSAFF and SCHENV [EXTERNAL] > > > > SCHENV is 20 years old. I'm curious how many other shops have taken > > the plunge. > > > > . > > . > > 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 Mike Shorkend > > Sent: Sunday, January 27, 2019 10:45 PM > > To: [email protected] > > Subject: (External):Re: SYSAFF and SCHENV > > > > I used SCHENV several years ago to direct workload to a CEC that had > > a ZIIP installed. Another use is for EXCI - switch the SCHENV on and > > off according to the availability of the CICS region. > > > > On Mon, 28 Jan 2019 at 06:26, Jesse 1 Robinson > > <[email protected]> > > wrote: > > > > > Before we implemented SCHENV control, we depended on SYSAFF to > > > direct a job toward the member running a suitable Db2 subsystem. > > > Then we had a couple of instances where the target Db2 abended and > > > would not restart on the 'normal' LPAR, but would run a different > > > LPAR. The task of directing a slew of batch jobs containing SYSAFF > > > to another LPAR was laborious and time consuming. Or else IPL. > > > > > > With SCHENV, we could issue a few WLM commands to disable resources > > > on the broken LPAR and enable them on the other one. No change to > > > automation, no change to JCL. And most all, no unscheduled IPL. > > > > > > However, SCHENV would not (early 2000s) override SYSAFF. If SYSAFF > > > and SCHENV conflicted, a job would just hang. So part of the > > > supporting SCHENV code was to nullify any SYSAFF if SCHENV was also > > > specified. If that has changed, we never revisited the issue. > > > > > > . > > > . > > > 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 Anthony Hirst > > > Sent: Sunday, January 27, 2019 4:12 PM > > > To: [email protected] > > > Subject: (External):Re: SYSAFF and SCHENV > > > > > > One difference that I haven't seen be mentioned is that SYSAFF > > > controls all stages of JES2 processing, while the SCHED only > > > controls execution phase, we've run into issues where subsystems > > > aren't active on some LPARs and a job with a SCHED setting gets > > > interpreted on that system you get a JCL error, only way to avoid > > > that we've found is to code SYSAFF. We keep the SCHED to because it > > > points to the actual resource requirement adding documentation. > > > > > > On Sat, Jan 26, 2019 at 8:53 PM Peter <[email protected]> wrote: > > > > > > > Hi > > > > > > > > It is just general question > > > > > > > > I was going through the manual. > > > > > > > > Does SCHENV perform the same function as SYSAFF ? Or it does more > > > > than that ? > > > > > > > > Peter > > -- > > Mike Shorkend > > [email protected] > > www.shorkend.com > > Tel: +972524208743 > > Fax: +97239772196 > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > Please note: This message originated outside your organization. > > Please use caution when opening links or attachments. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > ******************************************************** > For information, services and offers, please visit our web site: > https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.klm.com&d=DwIGaQ&c=9g4MJkl2VjLjS6R4ei18BA&r=eUhu3PeeWy6RTndlJVKe > mbFjFsvwCa8eeU_gm45NyOc&m=6Q2yXO-yRkQ-3mqLL4W3YIbD-gsF1ZI- > mo8GFUoU3HI&s=ryNRoaVJjCnO2k4Ngq93mbCtuxTOfx6rPD60ogUr-Mw&e=. This e- > mail and any attachment may contain confidential and privileged material > intended for the addressee only. If you are not the addressee, you are > notified that no part of the e-mail or any attachment may be disclosed, > copied or distributed, and that any other action related to this e-mail > or attachment is strictly prohibited, and may be unlawful. If you have > received this e-mail by error, please notify the sender immediately by > return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or > its employees shall not be liable for the incorrect or incomplete > transmission of this e-mail or any attachments, nor responsible for any > delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** > > > ---------------------------------------------------------------------- > 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 ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
