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 www.shorkend.com Tel: +972524208743 Fax: +97239772196 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
