z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

BPXBATCH
BPXBATCH — Run shell commands, shell scripts, or executable files
Format
Description
BPXBATCH SH|PGM shell_command|program_name
BPXBATCH makes it easy for you to run, from your TSO/E session, shell scripts or
z/OS C executable files that reside in z/OS UNIX files.
Note: For additional information on using BPXBATCH in order to run shell scripts
and executable files that reside in z/OS UNIX files through the MVS job
control language (JCL), see Appendix D, “Running shell scripts or executable
files under MVS environments.”
With BPXBATCH, you can allocate the MVS standard file stdin only as z/OS UNIX
files for passing input. You can allocate the MVS standard files stdout, stderr or
stdenv as MVS data sets or z/OS UNIX text files. The stdenv file for containing
environment variables or the stderr and stdout files for saving job output can be
allocated as SYSOUT, PDSE, PDS or sequential data sets. If you do not allocate
them, stdin, stdout, stderr, and stdenv default to /dev/null. Allocate the standard
files using the data definition PATH keyword options, or standard data definition
options for MVS data sets, for stdenv, stdout and stderr. For more information
about BPXBATCH, see Appendix D, “Running shell scripts or executable files under
MVS environments.”
In addition to using BPXBATCH, a user who wants to perform a local spawn without
being concerned about environment setup (that is, without having to set specific
environment variables which could be overwritten if they are also set in the user’s
profile) can use BPXBATSL. BPXBATSL provides users with an alternate entry point
into BPXBATCH, and forces a program to run using a local spawn instead of
fork/exec as BPXBATCH does. This ultimately allows a program to run faster.
The following example contains DD statements that are accessible to a program
that was given control from BPXBATSL:
//jobname JOB ...
//stepname EXEC PGM=BPXBATSL,PARM=’PGM program_name’
/* The following 2 DDs are still available in the program which gets
/* control from BPXBATSL.
//DD1 DD DSN=MVSDSN.FOR.APPL1,DISP=SHR
//DD2 DD DSN=MVSDSN.FOR.APPL2,DISP=SHR
/* The following DDs are processed by BPXBATSL to create file descriptors
/* for stdin, stdout, stderr
//STDIN DD PATH=’/stdin-file-pathname’,PATHOPTS=(ORDONLY)
//STDOUT DD PATH=’/stdout-file-pathname’,PATHOPTS=(OWRONLY,OCREAT,OTRUNC
// PATHMODE=SIRWXU
//STDERR DD PATH=’/stderr-file-pathname’,PATHOPTS=(OWRONLY,OCREAT,OTRUNC
// PATHMODE=SIRWXU
BPXBATSL is also useful when the user wants to perform a local spawn of their
program, but also needs subsequent child processes to be fork/exec’ed. Formerly,
with BPXBATCH, this could not be done since BPXBATCH and the requested
program shared the same environment variables.
BPXBATSL is an alias of BPXBATCH.
826 z/OS V1R9.0 UNIX System Services Command Reference