The use of a JP variable is an interesting possibility. It does not solve the problem but it will provide an interim solution that can be easily maintained. Thank you Regards Jack
On Wed, 20 Mar 2024 at 14:42, Scott Barry <[email protected]> wrote: > One option is to harvest the /D IPLINFO information at IPL-time (maybe > using an automated-SUBMIT batch-job DFSORT / ICETOOL, or SAS, or REXX, > etc.), parse and set a site-specific SYMBOL - then you can use it in one of > various methods in a batch DFSORT job via an expected JCL INCLUDE > MEMBER=<symbols_member>. Do consider challenges with symbol > naming-conventions since the IPL-date/time would be LPAR-specific of course. > > Personally I exploit the DFSORT feature (thanks for listening Frank > Yaeger, back in 2008 !!) where the PARM= can detect external JCL SET > symbols via the JP"&<symbol_name>" and then use the operand JPn within the > DFSORT SYSIN control statements. > > Scott Barry > SBBTech LLC > > IBM.COM DFSORT Doc link: > https://www.ibm.com/docs/en/zos/2.5.0?topic=statements-using-jpn-parameters-in-exec-parm-icetool > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
