I'm talking about the TSO SH command not a shell script!
On 2020-05-15 9:13 PM, Joel C. Ewing wrote:
Nope. In Unix, semicolons are command separators, not a continuation
indicator. The actual command continuation character is "\", but that
is only needed just prior to an EOL character.
It would appear that in this environment no end-of-line characters are
seen, so unix just sees "SH su <whitespace> SH ...". Without the
semicolon the shell sees the command "su SH", which is an attempt to
switch to the context of user "SH". In the absence of a recognized
EOL/ENTER to indicate end of command, the semicolon must be used between
commands -- although putting an extra one at the end doesn't hurt -- it
just sees a null command at the end.
This requirement may not be documented. They may just assume that
everyone familiar with Unix will of course "know" this if they describe
the STDPARM file as being treated as a single string or a single line
with no EOL forced at the end of each record.
Joel C Ewing
On 5/15/20 7:47 AM, David Crayford wrote:
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
Hi Jon,
Every line except for the last line needs a semicolon.
Regards,
David
On 2020-05-15 08:10, Jon Bathmaker wrote:
Hi Ed,
Thanks for this! How *did* you find out about the semicolons, I
didn't see them anywhere in the doc.
Best regards,
*Jon Bathmaker,*
SYS1 Consulting Inc.
519-577-9661
On 5/15/2020 12:19 AM, Ed Jaffe wrote:
On 5/14/2020 5:23 PM, Jon Bathmaker wrote:
//STDPARM DD *
SH su
SH echo $PATH
SH unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
The above looks wrong to me. I always do it this way:
//STDPARM DD *
SH su;
echo $PATH;
unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
..
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
