I've found the REXX function sysvar("symdef", "jobname") words well in more
than one site.


OREXXMan
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)?  Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.


On Thu, Dec 30, 2021 at 7:21 AM Peter Relson <[email protected]> wrote:

> &SYSJOBNM and &SYSJOBID are not system symbols in the proper usage of the
> term.
> They are symbols that begin with "SYS". They are provided, I presume, by
> JES.
>
> System symbols are well-defined as the set of system-defined static
> symbols (&SYSNAME, &SYSCLONE, &SYSPLEX, &SYSR1, &SYSALVL, &SYSOSLVL) plus
> the set of system-defined dynamic symbols (of which &JOBNAME is one) plus
> the symbols defined by the customer.
>
> &JOBNAME is defined as being the jobname of the running job, so that using
> it within JCL is not going to give you the name of the job that is going
> to be run, as should be pretty clear from its definition.
>
> System symbols are displayed by DISPLAY SYMBOLS. System symbols are
> processed by the ASASYMBM module. System symbols are initially defined in
> parmlib member IEASYMxx.
>
> Peter Relson
> z/OS Core Technology Design
>
>
> ----------------------------------------------------------------------
> 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

Reply via email to