On Wed, 26 Aug 2026 16:21:28 +0200, Radoslaw Skorupk wrote:

>
>Now I have another issue with the BPXBATCH.
>I used the following:
>
>    ...
>//STDPARM  DD *
>SH echo "mkdir -p /some/very/long/dir &&&& chmod -R 750 
>/some/very/long/dir" | su
>
>Actually I used &VARiable for directory name, however after the
>substitution the line length exceed 80 characters and yields abend 001-04.
>Can I split the line? What are the continuation rules? Note the ""
>
<https://www.ibm.com/docs/en/zos/3.2.0?topic=bpxbatch-guidelines-defining-stdparm>
    Guidelines for defining STDPARM
    The record format can be fixed or variable (unspanned).
    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 blanks within a line.
    The file or data set should not have sequence numbers in it.

o Separate commands with semicolons.
o Or with a symbol SET to newline.
o Use otiose command substitution for comments.

Escape the 80 column tyranny:
    //READER  DD  SYSOUT=(,INTRDR),RECFM=VB,
    //    LRECL=[ISPF Symbol]
which I have used in  a macro alternative to SUBMIT.

-- 
gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
  • ... Radoslaw Skorupka
    • ... Philippe Leite
      • ... Styles, Andy (CIO Enabling Services - Core Infrastructure Platform)
    • ... Farley, Peter
    • ... Sri Hari Kolusu
    • ... Radoslaw Skorupka
    • ... Paul Gilmartin
    • ... Paul Gilmartin
      • ... Radoslaw Skorupka
    • ... Paul Gilmartin
    • ... Dana Mitchell
      • ... Kirk Wolf
        • ... Tony Harminc
        • ... Radoslaw Skorupka
          • ... Kirk Wolf
        • ... Rob Schramm
    • ... Paul Gilmartin

Reply via email to