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 <IBM-MAIN@LISTSERV.UA.EDU> 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 <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 > > > > ---------------------------------------------------------------------- > > 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 <br>...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<br>...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
