Nope, the comma is not the problem. I got it out of there with a quick change 
that works so long as the object file name is short. Still sat for a minute 
elapsed doing nothing on a nearly-idle z13s:

IEF236I ALLOC. FOR useridCC BPXARCH                                          
IEF237I DMY  ALLOCATED TO STDIN                                              
IEF237I JES2 ALLOCATED TO STDOUT                                             
IEF237I JES2 ALLOCATED TO STDERR                                             
IEF142I useridCC BPXARCH - STEP WAS EXECUTED - COND CODE 0000                
IEF285I   userid.useridCC.JOB04942.D0000105.?          SYSOUT                
IEF285I   userid.useridCC.JOB04942.D0000106.?          SYSOUT                
IEF373I STEP/BPXARCH /START 2018032.1836                                     
IEF032I STEP/BPXARCH /STOP  2018032.1837                                     
        CPU:     0 HR  00 MIN  00.02 SEC    SRB:     0 HR  00 MIN  00.00 SEC 
        VIRT:   164K  SYS:   348K  EXT:       16K  SYS:    12084K            
        ATB- REAL:                     0K  SLOTS:                     0K     
             VIRT- ALLOC:      14M SHRD:       0M                            
IEF375I  JOB/useridCC/START 2018032.1836                                     
IEF033I  JOB/useridCC/STOP  2018032.1837                                     
        CPU:     0 HR  00 MIN  06.53 SEC    SRB:     0 HR  00 MIN  00.16 SEC

Charles


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Thursday, February 1, 2018 3:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 
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

Reply via email to