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.

Return codes<br />

0 Processing successful.<br />

254 Processing unsuccessful. BPXBATCH requires OMVS to be started.<br />

255 Processing unsuccessful. An error message has been issued.<br />

4095 Processing unsuccessful. An error message has been issued.<br />

32000 BPXBATCH invoked the BPX1FRK (fork) callable service. This is usually<br />

invoked only by a TSO/E user. One of the following conditions may have<br />

resulted:<br />

v BPXBATCH failed to open specified files after the program fork. Files are<br />

normally opened and closed prior to a fork. Try running BPXBATCH<br />

again.<br />

v The program_name or the shell exited with an exit status of 125.<br />

32512 One of the following conditions may have resulted:<br />

v The PGM keyword was specified for BPXBATCH and no program_name<br />

could be found.<br />

Message BPXM008I was written to the job log or stderr.<br />

v The SH keyword was specified for BPXBATCH and either /bin/login or<br />

the shell did not exist.<br />

v The SH keyword was specified with a program_name value for<br />

BPXBATCH and no program_name could be found. The shell exited with<br />

an exit status of 127. stdout contains a shell message indicating the<br />

program was not found.<br />

v The program_name or the shell exited with an exit status of 127.<br />

other multiples of 256<br />

A return code greater than 255, unless explicitly documented as a return<br />

code from BPXBATCH (32000 or 32512), is actually an exit status being<br />

returned from the program that was invoked by BPXBATCH. The exit status<br />

can be determined by dividing the value of BPXYWAST by 256.<br />

BPXYWAST<br />

BPXBATCH invoked the BPX1FRK (fork) callable service. This is usually<br />

invoked only by a TSO/E user. Processing was successful with wait() status<br />

containing a nonzero value. The wait status was mapped by BPXYWAST<br />

and returned by BPX1WAT (wait).<br />

No error messages were issued by BPXBATCH.<br />

Using <strong>OS</strong>HELL to run shell commands and scripts from MVS<br />

You can use the <strong>OS</strong>HELL REXX exec to run a shell command or shell script from<br />

the TSO/E READY prompt and display the output to your terminal. This exec uses<br />

BPXBATCH to run the shell command or shell script:<br />

oshell shell_command<br />

For example, to display process information, enter:<br />

oshell ps –ej<br />

BPXBATCH<br />

Note: With this exec, do not use an & to run a shell command in the background.<br />

Appendix D. Running shell scripts or executable files under MVS environments 899

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

Saved successfully!

Ooh no, something went wrong!