As I mentioned previously, we devised a set of JES2 exit routines that process JECL cards (/*SCHENV ...) to create the required 16 byte SCHENV card. The user can code that directly if desired; otherwise we build it from JECL.
The only value we insert directly on the user's behalf is 'TAPE'. 20 years ago our VTS system required fairly frequent and lengthy upgrade windows. During those windows, we didn’t want 'tape jobs' to execute. We *already* had JES2 exit code to scan for tape-resident data sets, so it was easy to add an SCHENV indicator. With SCHENV/TAPE turned off in WLM, such jobs would simply wait until tape was back in operation. This simplified life for Operations. Other SCHENV values are up to the users. We don’t try to guess what they need. . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Tuesday, January 29, 2019 6:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSAFF and SCHENV [EXTERNAL] Sorry Kees, I got a bit off track, the outsourcer I worked at used a number of JES2 exits to add SCHENV dependant on the specific client, it was pretty cool because all batch, unless your ID was entered into a table, ran via the scheduler, the schedulers resources + SCHENV and WLM resources managed all batch controls. at the transportation company I worked at the users with the direction of operations/production control added the required SCHENV Carmen Vitullo ----- Original Message ----- From: "Kees Vernooij (ITOP NM) - KLM" <kees.verno...@klm.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, January 29, 2019 8:09:44 AM Subject: Re: SYSAFF and SCHENV [EXTERNAL] Allen, Carmen, I know how SCHENVs work, we used them for limited purposes. My question to Paul was, how does he get the right SCHENV added to a job. With our 'dependencies' we moved almost all handling to Exit60, require users to use standard PROCs and put the info for the 'dependencies' in the PROCs. Exit60 will then see all job requirements and compose the dependencies-set, like Paul does to determine the SCHENV. The purpose of my question was to find out which other smart techniques were available. Apparently none since the last 30 years. Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Allan Staller > Sent: 29 January, 2019 14:44 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SYSAFF and SCHENV [EXTERNAL] > > <quote>How do you add a SCHENV to a job? Does the user/submittor do > this or is it done automatically?</quote> > > 1) JES can assign a default SCHENV on the JOBDEF/JOBCLASS(n) init > parms > 2) Modern schedulers (CA7, CTL-M) allow this to be added to the job as > part of their processing. > 3) SCHENV= on Job Card. > > There are probably others, but they don't come readily to mind. > > HTH, > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Vernooij, Kees (ITOP NM) - KLM > Sent: Tuesday, January 29, 2019 1:22 AM > To: IBM-MAIN@LISTSERV.UA.EDU > 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Feller, Paul > > Sent: 29 January, 2019 5:04 > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson > > Sent: Monday, January 28, 2019 4:13 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 > > robin...@sce.com > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Shorkend > > Sent: Sunday, January 27, 2019 10:45 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 > > <jesse1.robin...@sce.com> > > 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 > > > robin...@sce.com > > > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Anthony Hirst > > > Sent: Sunday, January 27, 2019 4:12 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > 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 <dbajava...@gmail.com> 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 > > m...@shorkend.com > > https://apac01.safelinks.protection.outlook.com/?url=www.shorkend.co ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
