z/OS UNIX batch environment

In the z/OS® UNIX batch environment, use one of the following methods to specify the Trace Resolver output location:

If the application resides in a z/OS UNIX file system file, use BPXBATSL to run the program. In this way, DD allocations is passed to the application. If the application does fork, the DD allocations are not passed to the new process, and the Trace Resolver output cannot be collected.
To use the recommended JES SYSOUT, enter the following:
```
//SYSTCPT  DD  SYSOUT=*
```
Because STDOUT cannot be allocated to SYSOUT=* with BPXBATSL, use one of the following STDOUT DD JCL statements:
```
//STDOUT   DD DISP=SHR,DSN=USER3.APPL.RESTRACE

//STDOUT  DD PATH='/tmp/appl.stdout', 
//  PATHOPTS=(OWRONLY,OCREAT),        
//  PATHMODE=SIRWXU
```
Note: In this example, OTRUNC is not specified on the PATHOPTS statement. This means the Trace Resolver output is appended to the z/OS UNIX file system file. To avoid z/OS UNIX file system full conditions, manually delete trace output that is no longer needed to ensure that the file does not fill the specified directory (for example, /tmp/).

You must allocate either SYSTCPT or SYSPRINT DD if the TCPIP.DATA statements, TRACE RESOLVER or OPTIONS DEBUG, are specified. If neither is allocated, then no trace output is written.
To pass the RESOLVER_TRACE environment variable using BPXBATSL or BPXBATCH, enter the following:
```
 //STDENV  DD JCL statement
```
The following shows an example:
```
//STDENV   DD  DISP=SHR,DSN=USER3.APPL.ENVIRON 
```
The STDENV data set can be a fixed or variable (nonspanned) record format type. It can contain multiple environment variables, as shown in the following sample:
```
RESOLVER_TRACE=//'USER3.APPL.RESTRACE'
_BPXK_SETIBMOPT_TRANSPORT=TCPCS 
```
Note:
1. Environment variables must start in column 1, and the data set must not contain any sequence numbers because they would be treated as part of the environment variable.
2. For the RESOLVER_TRACE environment variable, any blanks from a fixed-format STDENV data set is removed. Because this might not be true for all variables, a variable record format data set is recommended.
3. For applications that fork, use of an MVS™ data set is recommended. If you use a z/OS UNIX file system file, a C03 ABEND might occur when the forked process ends.