Re: SYSAFF and SCHENV
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" 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] > > How do you add a SCHENV to a job? Does the user/submittor do > this or is it done automatically? > > 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 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 >
Re: SYSAFF and SCHENV
Looks like that got added in 2.1, we've been using SCHENV much longer than that, but good to know, thank you. On Thu, Jan 31, 2019 at 9:42 AM ITURIEL DO NASCIMENTO NETO < ituriel.nascime...@bradesco.com.br> wrote: > Not necessarily. > If your JOBDEF is defined with CNVT_SCHENV=HONOR, convertion phase will be > done at desired Lpar. > > Can be changed by $TJOBDEF, CNVT_SCHENV=HONOR or CNVT_SCHENV=IGNORE > > Atenciosamente / Regards / Saludos > > Ituriel do Nascimento Neto > BANCO BRADESCO S.A. > 4250 / DITI Engenharia de Software > Sistemas Operacionais Mainframes > Tel: +55 11 3684-9602 R: 49602 3-1404 > Fax: +55 11 3684-4427 > > > > -Mensagem original- > De: IBM Mainframe Discussion List Em nome de > Anthony Hirst > Enviada em: domingo, 27 de janeiro de 2019 22:12 > Para: IBM-MAIN@LISTSERV.UA.EDU > Assunto: 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 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 > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > AVISO LEGAL ...Esta mensagem é destinada exclusivamente para a(s) > pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou > legalmente privilegiada. Se você não for destinatário desta mensagem, desde > já fica notificado de abster-se a divulgar, copiar, distribuir, examinar > ou, de qualquer forma, utilizar a informação contida nesta mensagem, por > ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que > nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu > conteúdo em sua base de dados, registros ou sistema de controle. Fica > desprovida de eficácia e validade a mensagem que contiver vínculos > obrigacionais, expedida por quem não detenha poderes de representação. > LEGAL ADVICE...This message is exclusively destined for the people to > whom it is directed, and it can bear private and/or legally exceptional > information. If you are not addressee of this message, since now you are > advised to not release, copy, distribute, check or, otherwise, use the > information contained in this message, because it is illegal. If you > received this message by mistake, we ask you to return this email, making > possible, as soon as possible, the elimination of its contents of your > database, registrations or controls system. The message that bears any > mandatory links, issued by someone who has no representation powers, shall > be null or void. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
RES: SYSAFF and SCHENV
Not necessarily. If your JOBDEF is defined with CNVT_SCHENV=HONOR, convertion phase will be done at desired Lpar. Can be changed by $TJOBDEF, CNVT_SCHENV=HONOR or CNVT_SCHENV=IGNORE Atenciosamente / Regards / Saludos Ituriel do Nascimento Neto BANCO BRADESCO S.A. 4250 / DITI Engenharia de Software Sistemas Operacionais Mainframes Tel: +55 11 3684-9602 R: 49602 3-1404 Fax: +55 11 3684-4427 -Mensagem original- De: IBM Mainframe Discussion List Em nome de Anthony Hirst Enviada em: domingo, 27 de janeiro de 2019 22:12 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: 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 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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN AVISO LEGAL ...Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou legalmente privilegiada. Se você não for destinatário desta mensagem, desde já fica notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu conteúdo em sua base de dados, registros ou sistema de controle. Fica desprovida de eficácia e validade a mensagem que contiver vínculos obrigacionais, expedida por quem não detenha poderes de representação. LEGAL ADVICE...This message is exclusively destined for the people to whom it is directed, and it can bear private and/or legally exceptional information. If you are not addressee of this message, since now you are advised to not release, copy, distribute, check or, otherwise, use the information contained in this message, because it is illegal. If you received this message by mistake, we ask you to return this email, making possible, as soon as possible, the elimination of its contents of your database, registrations or controls system. The message that bears any mandatory links, issued by someone who has no representation powers, shall be null or void. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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" 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] > > How do you add a SCHENV to a job? Does the user/submittor do this > or is it done automatically? > > 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 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 > > > > 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. > > > > > >
Re: SYSAFF and SCHENV [EXTERNAL]
Kees, yes we do run into from time to time someone who wants to run a job that might have conflicting resources. An example might be MQ and SAS. If there is not an MQ task running on the same lpar as SAS then the user needs to rethink how they have the job set up. They may have to break the job up. For things like DB2 we do data sharing so there is an image of DB2 on each lpar. It all comes down to how you have your environment set up. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOP NM) - KLM Sent: Tuesday, January 29, 2019 7:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSAFF and SCHENV [EXTERNAL] 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:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Feller, Paul > Sent: 29 January, 2019 13:50 > To: IBM-MAIN@LISTSERV.UA.EDU > 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: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 > > > > 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
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] > > How do you add a SCHENV to a job? Does the user/submittor do this > or is it done automatically? > > 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 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 > > > > 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 P
Re: SYSAFF and SCHENV [EXTERNAL]
There are so many options with WLM and SCHDENV and WLM resources, you can get real sophisticated. at a very low level at the outsources we used SCHDENV to ensure the correct client ran on the correct LPAR in the PLEX, in one place I worked, SCHDENV and WLM resources were used to AID in moving workloads, or ensuring onlines were up or down depending on the need before some batch processing. So, COSMOS ot your favorite automation product can shutdown DB2 for instance, change the DB2 (subsystem) WLM resource to down so image copies or reorgs can be done with DB2 down. same as required resources, if a batch process needs CICS (exci) we used SCHENV + the WLM resource to ensure the batch ran where it needed to. works well for weekend processing also when you just need to reset a WLM resource so you can perform needed maint. a very simple explanation for a very cool way, other than jobclass(es) only to manage workloads. example: on a jobcard where your batch needs to run where, for example CHANGMAN is up SCHENV='CHANGEMAN_JOBS' if it's not up the jobs wait until automation brings it up and changes the WLM resource to up Carmen Vitullo - Original Message - From: "Kees Vernooij (ITOP NM) - KLM" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, January 29, 2019 6:59:30 AM Subject: Re: SYSAFF and SCHENV [EXTERNAL] 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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Feller, Paul > Sent: 29 January, 2019 13:50 > To: IBM-MAIN@LISTSERV.UA.EDU > 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: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
Re: SYSAFF and SCHENV [EXTERNAL]
How do you add a SCHENV to a job? Does the user/submittor do this or is it done automatically? 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 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 > > 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 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 ? > > > > > >
Re: SYSAFF and SCHENV [EXTERNAL]
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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Feller, Paul > Sent: 29 January, 2019 13:50 > To: IBM-MAIN@LISTSERV.UA.EDU > 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: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 > > > > 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-
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: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 > > 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 wrote: > > > > > Hi > &g
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 > 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 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. > &
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 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 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
Re: SYSAFF and SCHENV
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 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 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
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 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 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 > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- 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
Re: SYSAFF and SCHENV
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 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSAFF and SCHENV
Similar purpose, but different mechanisms. SYSTEM, SYSAFF, and SCHENV all control the system that a job is allowed to run on, but they filter based on different mechanisms. SYSTEM and SYSAFF are based off of the JES2/JES3 member name. SCHENV is based off of your WLM setup; in WLM, you can define scheduling environments, which are essentially arbitrary resources that can be associated with a system image via SDSF or system commands. So with SYSTEM/SYSAFF, you're saying "this job can only run on a system called X." With SCHENV, you're saying that "this job can only run if the system has resources A, B, and C," when A, B, and C are all things that the installation can control whether or not they're defined at any given time. So with scheduling environments, you can have some very basic job scheduling, if you want to. As an example, we typically run our sysplexes with a mix of z/OS release levels (say, V2R1, V2R2, and V2R3). Some of our jobs will only run on a system with release level V2R2 or above. So I can create a scheduling environment called SCHV2R2, and only enable it on systems that are running V2R2 or V2R3. And jobs with SCHENV=SCHV2R2 will be limited to running on those systems. Or you could control it based on the presence of a subsystem, or whether or not the system is DEVTEST, or whatever arbitrary reasons you want to schedule based on. --- Kevin McKenzie External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test Services - Test Architect, Provisioning IBM Mainframe Discussion List wrote on 01/26/2019 10:52:49 PM: > From: Peter > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 01/26/2019 10:53 PM > Subject: SYSAFF and SCHENV > Sent by: IBM Mainframe Discussion List > > 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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSAFF and SCHENV
SYSAFF looks for a match on JES2 system name only. Nothing else. If there's a match by name, a job will execute there. Otherwise the job will wait (forever) until a matching system joins the MAS. SCHENV is much more complex. If you've been in the mainframe biz a while, think of SCHENV as an official incarnation of the venerable 'abstract resource' manager (aka Mellon mods). The resources are abstract in that they don’t represent any particular JES2 entity. They are entirely user defined. The bits in the 16-byte SCHENV carry whatever meaning the installation assigns. If the string in JCL is non-zero, WLM will hold a job until at least one system matches. Resources that may be mapped might include time of day, presence of required support software, or a particular Db2 subsystem. The possibilities are limitless. We created an SCHENV schema in early Y2K. It supports JECL keywords that users can code for a variety of reasons to format the SCHENV string. This is all done in JES2 exits. Unlike SYSAFF, JES2 proper knows nothing about the SCHENV resources being managed. WLM commands turn resource availability on or off. . . 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 Peter Sent: Saturday, January 26, 2019 7:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):SYSAFF and SCHENV 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SYSAFF and SCHENV
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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
