On Thu, 14 May 2020 20:23:20 -0400, Jon Bathmaker wrote:
>
>
>//STDERR�� DD SYSOUT=*
>
>//STDOUT� �DD SYSOUT=*
>
>//STDPARM� DD *
>
>SH su
>
>SH echo $PATH
>
>SH unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
>
>Here is the contents of STDERR when the job runs.
>
>FSUM5023 su: User ID "SH" does not exist, or the RACF profile does not
>contain an OMVS segment.
>
Why do your auditors prohibit UID 0 from TSO but allow
it otherwise?
I'll recommend BPXWUNIX as a superior alternative. And
SYSIN for bpxwunix can then be an instream data set.
I haven't the stamina to compose all the RCFs the description of STDPARM
in the Command Ref. deserves. A couple examples:
If a MVS data set is specified:
• Specify one argument per line.
What's an "argument"
Should PGM or SH be specified on only the first line,
or on every line? If the latter, is a mixture of PGM
and SH supported?
• Trailing blanks are truncated for SYSIN and variable block data sets,
but not for fixed block data sets. For a fixed block data set,
trailing blanks will be included in the parameter text for a given
argument up to the end of the record.
WTF!? It makes sense to truncate for fixed, where the
programmer can't control trailing blanks. For variable,
the programmer has control and trailing blanks should be
preserved.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
