Lucas, I think this is a mis-interpretation of your observations:
With /*JOBPARM SYSAFF: the job has affinity to the mentioned system: for convertor, interpretor and execution, so here you can be sure of the substituted values. Without /*JOBPARM SYSAFF: the job can be handled by any system in the MAS for all 3 phases, so it can be submitted on system1, converted on system 2 and executed on system 3. You will not know in advance which system will do what. Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lucas Rosalen > Sent: 21 June, 2018 8:57 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Using JCL Symbld and TYPRUN=SCAN > > On the side topic... > > Based on our latest "experience": > - without /*JOBPARM SYSAFF: symbols got resolved in the submitting LPAR, > which caused some problems as they were different from the executing > LPAR > (and used as a dataset qualifier); > - with /*JOBPARM SYSAFF: symbols are resolved in the executing LPAR > (even > with SYSAFF=*); > > I also don't know about the documentation, just learned from a colleague > that had worked on our issue. > > > ------------------------------------------------------------------------ > ------------------------------------------------------- > *Lucas Rosalen* > rosalen.lu...@gmail.com / lucas.rosal...@ibm.com > http://br.linkedin.com/in/lrosalen > > > 2018-06-21 8:16 GMT+02:00 Elardus Engelbrecht < > elardus.engelbre...@sita.co.za>: > > > Andrew Rowley wrote: > > > > >> to this one (clear out the SYSIN - at least for IDCAMS SYSIN and > place > > it in a JCL comment): > > >> //* DELETE KVPO.MOST.DB2DATA.&LVL4..&PART..TRS > > >> //SYSIN DD *,SYMBOLS=(JCLONLY,X) > > >> SET MAXCC = 0 > > > > >Unfortunately that may not work because the symbols in SYSIN are not > > substituted the same way as in the regular JCL. I have been playing > around > > with them and my conclusion is that the whole feature seems to have > been > > badly thought out. > > > > Thanks for this reminder. I remember that I also discovered that > > substition is not always correct, but I was too busy to follow it up. > > > > > > >If IBM had omitted some features, e.g. system symbols on the > execution > > system and instead substituted the symbols at the same time as the > symbols > > in the rest of the JCL, they would have lost maybe 10% of the > usefulness > > but decreased the astonishment by 90%. > > > > Which brings another question - I am just curious - Where are the > Symbols > > resolved? At the submitting LPAR or at the Executing LPAR? Or is the > > '/*JOBPARM SYSAFF=<LPAR>' used to determine the LPAR where the Symbols > are > > to be resolved/substituted? > > > > I am asking, because there are Symbols unique for a LPAR, like this: > > > > D SYMBOLS > > IEA007I STATIC SYSTEM SYMBOL VALUES > > &SYSALVL. = "2" > > &SYSCLONE. = "C4" <--- Unique per LPAR > > &SYSNAME. = "????" <--- Unique per LPAR > > > > If that is documented, I must missed it somewhere ... > > > > Sorry for this topic drift, but ... ;-) > > > > Groete / Greetings > > Elardus Engelbrecht > > > > ---------------------------------------------------------------------- > > 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 ******************************************************** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
