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

Parameters
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
BPXBATCH accepts one parameter string as input, the combination of SH|PGM and
program_name. At least one blank character must separate the parts of the
parameter string. The total length of the parameter string will now support up to
32754 characters.
Tips:
v BPXBATCH was first created for use with JCL, which had a max parm length of
100. Now, BPXBATCH can also be called form CLIST, REXX, and TSO. These
additional environments do not have the 100 character parameter limit. From a
TSO command environment the parameter string itself will now support up to
32754 characters.
v Parameters to BPXBATCH can also be supplied via the STDPARM DD up to a
limit of 65,536 characters. When the STDPARM DD is allocated BPXBATCH will
use the data found in the z/OS UNIX file or MVS data set associated with this
DD rather than what is found on the parameter string or in the STDIN DD. An
informational message BPXM079I will be displayed indicating that this is
occurring, as a warning to the user. The STDPARM DD will allow either a z/OS
UNIX file, or a MVS SYSIN, PDS or PDSE member or a sequential data set.
If neither SH nor PGM is specified as part of the parameter string, BPXBATCH
assumes that the shell is to be started to run the shell script allocated by STDIN.
SH|PGM
Specifies whether BPXBATCH is to run a shell script or command or a z/OS C
executable file located in an z/OS UNIX file.
SH
BPXBATCH
Specifies that the shell designated in your TSO/E user ID’s security product
profile is to be started and is to run shell commands or scripts provided
from stdin or the specified program_name.
If SH is specified with no program_name information, BPXBATCH attempts
to run anything read in from stdin.
PGM
Specifies that the program identified by the program_name parameter is
invoked directly from BPXBATCH. This is done either via a spawn or a fork
Appendix D. Running shell scripts or executable files under MVS environments 893