16.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Parameters<br />

BPXBATA2 and BPXBATA8 are provided as APF - authorized alternatives to<br />

BPXBATSL. BPXBATA2 and BPXBATA8 provide the capability for a target APF -<br />

authorized z/<strong>OS</strong> <strong>UNIX</strong> Program to run in the same address space as the originating<br />

job, allowing it to share the same allocations and joblog. BPXBATA2 is specifically<br />

intended to provide the capability for a PSW Key 2 APF - authorized z/<strong>OS</strong> <strong>UNIX</strong><br />

program to be started. To insure the target program receives control PSW Key 2, a<br />

PPT entry for BPXBATA2 must be set up that specifies that BPXBATA2 starts up<br />

PSW Key 2. The same restrictions that apply to BPXBATSL apply to BPXBATA2<br />

and BPXBATA8, in addition to the following:<br />

v The PGM keyword is the only invocation type that is supported. The SH keyword<br />

is not supported.<br />

v The interfaces can only be used from Started Task address spaces.<br />

v The z/<strong>OS</strong> <strong>UNIX</strong> program that is the target of the BPXBATA2 and BPXBATA8 job<br />

must be marked as an APF - authorized executable file.<br />

Restriction: Any other usage of the BPXBATA8 and BPXBATA2 interfaces than<br />

what is described is not supported and will cause the invoking job to fail.<br />

SH|PGM<br />

Specifies whether BPXBATCH is to run a shell script or command, or a z/<strong>OS</strong> C<br />

executable file located in a z/<strong>OS</strong> <strong>UNIX</strong> file.<br />

If neither SH nor PGM is specified, BPXBATCH assumes that the shell is to be<br />

started in order to run the shell script allocated by stdin.<br />

SH<br />

Specifies that the shell designated in your TSO/E user ID’s security product<br />

profile is to be started and is to run shell commands or scripts provided<br />

from stdin or the specified program_name.<br />

If SH is specified with no program_name information, BPXBATCH attempts<br />

to run anything read in from stdin.<br />

SH is the default.<br />

BPXBATCH<br />

PGM<br />

Specifies that the program identified by the program_name parameter is<br />

invoked directly from BPXBATCH. This is done either via a spawn or a fork<br />

and exec. BPXBATCH creates a process for the program to run in and then<br />

calls the program. If you specify PGM, you must also specify<br />

program_name.<br />

All environment variables read from the stdenv file are set when the<br />

program is run, if stdenv was allocated. If the HOME and LOGNAME<br />

environment variables are not specified in the stdenv file, or stdenv was not<br />

allocated, then HOME and LOGNAME, if possible, are set when the<br />

program is run.<br />

Note: When using PGM, the program_name cannot contain any shell<br />

specific functions because they will not be resolved. If shell specific<br />

functions must be specified, then SH should be used to avoid<br />

possible errors or unpredictable results.<br />

program_name<br />

Specifies the shell command name or pathname for the shell script or z/<strong>OS</strong> C<br />

executable file that you want to run. program_name can also contain option<br />

information. program_name is in uppercase and lowercase letters.<br />

Chapter 3. TSO/E commands 827

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!