STDOUT and STDERR DD statements

To route log messages to a particular destination, the JCL must contain DD cards STDOUT and STDERR in the DD statements which mean route stdout and stderr to the specified DD location.

DD cards STDOUT and STDERR must be writable destinations. Valid options are: DD cards STDOUT and STDERR are defined as writable HFS files, as shown in the following examples, to be created if they do not already exist (OCREAT), appended if they do exist (OAPPEND), and opened for writing only (OWRONLY). Read-write permissions are given to the batch user ID (SIRUSR,SIWUSR) with read-only to all other users (SIRGRP,SIROTH).
//STDOUT  DD PATH='/u/ctgusr/ctglogs/ctg1_stdout.log',
//   PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
//   PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH)
//STDERR  DD PATH='/u/ctgusr/ctglogs/ctg1_stdoerrlog',
//   PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
//   PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH)

If the STDOUT DD statement is omitted, a JES log with the name 'SYS00001' will be dynamically allocated the first time that data is written to the stdout destination.

If the STDERR DD statement is omitted, a JES log will be dynamically allocated. The name is dependent upon the MSGFILE Language Environment® runtime option. If allowed to default the name will be 'SYSOUT'.

Note: The location specified in the STDERR DD statement will also contain remote mode JNI log messages.

Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/cclaibat.html