I understand why they parse pgm and sh differently. What I don't understand is why instream data should be treated differently from other datasets.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Joel C. Ewing <jcew...@acm.org> Sent: Friday, May 15, 2020 10:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: USS: su: User ID "SH" does not exist I think that maybe they are trying to imply that if "PGM" is used, the whole rest of the multi-line string is parsed as MVS-style program parameters, with record boundaries always being a parameter boundary, and passed to the program. if "SH" is used, the entire string is passed as the "command" argument to the unix shell, which then parses it as unix commands plus parameters according to unix command syntax rules; so that with only a blank at end-of-record, an in-stream end-of-line might not be the end of a command or even the end of a parameter. Either way, highly confusing as would appear to be a collision of two paradigms. Multiple examples of what they really meant would have been useful. Joel C Ewing On 5/15/20 8:35 AM, Seymour J Metz wrote: > "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 >> >> > ... -- Joel C. Ewing ---------------------------------------------------------------------- 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
