Yeah, okay, the comma that MVS in its wisdom REQUIRES in there. Yeah, I could get rid of it but see no need. I was just happy when I got the thing working at all (several years ago).
And yes, sure enough, it does cause an error: ,: FSUM7351 not found But does not seem to hurt anything. Unless perhaps USS is spending two minutes looking for a command named ','. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, February 1, 2018 3:07 PM To: [email protected] Subject: Re: Why does BPXBATCH/ar go to sleep On Thu, 1 Feb 2018 09:52:31 -0800, Charles Mills wrote: > >In answer to your other question, the two semicolons are accepted (required?) >perhaps because MVS in its wisdom adds a comma in there. > Isn't that the comma that *you* typed? On Thu, 1 Feb 2018 08:40:15 -0800, Charles Mills wrote: > >//BPXARCH EXEC PGM=BPXBATCH,COND=(4,LT), // PARM=('SH cd >&CSOURCE/Object;', >// ';ar -rvc MyArchive.a #MEMBER#.o') And doesn't stderr show a syntax error on the comma? Circumventions: o Use symbol substitution to avoid the need for continuation. o Use PARMDD o Use STDPARM o Use a silly command substitution to devour the comma (Ugh!): >//BPXARCH EXEC PGM=BPXBATCH,COND=(4,LT), // PARM=('SH cd >&CSOURCE/Object; $(: ', >// '); ar -rvc MyArchive.a #MEMBER#.o') -- gil ---------------------------------------------------------------------- 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
