"For in-stream data sets: with the SH option, trailing blanks are not truncated. Records in in-stream data sets are concatenated with blanks as separator characters, and the string remaining after the SH token is passed as a single argument to a /bin/sh -c command. For the PGM option, the string is divided not only at line boundaries but also at horizontal white space within a line. "
Which doesn't make a lot of sense. If it is not taken as a single parameter for other file types, why not? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon Bathmaker [jon.bathma...@sys1consulting.com] Sent: Friday, May 15, 2020 8:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: USS: su: User ID "SH" does not exist 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
