Collecting the CRASTART log files

CRASTART creates a TSO environment as a child process of RSE, which runs in a separate address space. Non-trivial actions might be needed to keep the CARMA output sent to SYSOUT(*), which complicates the collecting of log files. This difficulty can be resolved by writing the log files to a user-specific data set, as shown in the following sample allocation:

-COMMAND=ALLOC FI(CARMALOG) MOD CATALOG DSORG(PS) RECFM(F,B) LRECL(133)
  BLKSIZE(27930) SPACE(5,5) TRACKS UNIT(SYSALLDA) 
  DA(&CRAUSER..&SYSNAME..CRA.CARMALOG)
Note:
  • Due to page width limitations, some lines in the sample wrapped onto the next line. All lines that start with an indentation should be added to the end of the previous line.
  • To be able to create user-specific log files, this log file must be allocated using the -COMMAND statement.
  • You can also allocate the log data sets in an allocation exec if you need more flexibility; for example, only send the log to a data set for specific users. For more information about allocation execs, see (Optional) Custom allocation exec.
If you are writing log files to SYSOUT, remember that SYSOUT allocated by z/OS® UNIX processes is treated as special output in JES. This is similar to SYSOUT allocated by APPC transactions.
  • While the CARMA server is still active, the output can be seen using the DA command in SDSF. The job will have the user's user ID followed by a random one-digit number as job name and an STC job ID. The user is the job owner.
  • If the output was written to a HOLD output class, when the CARMA server ends, due to inactivity or the user ending the connection, the output can be seen using the APPC ON and H ALL commands in SDSF. The job name, job ID, and job owner remain the same. Each DD shows up as a separate spool file, without any indication which DD it is.
  • JES Job Monitor can also show the output if SEARCHALL=ON is active in FEJJCNFG and the output resides on the spool in a HOLD output class. For more information about the SEARCHALL directive, see the IBM® Explorer for z/OS Host Configuration Guide (SC27-8437)..