RSE tracing

There are several log files created by the components related to RSE. Most are located in userlog/$LOGNAME/, where userlog is the combined value of the user.log and DSTORE_LOG_DIRECTORY directives in rse.env, and $LOGNAME is the logon user ID (uppercase). If the user.log directive is a null string, the home path of the user is used. The home path is defined in the OMVS security segment of the user ID.

The amount of data written to ffs*.log and rsecomm.log is controlled by the modify rsecommlog operator command, or by setting debug_level in rsecomm.properties. See "Operator commands" in the Host Configuration Guide (SC27-8437) and "(Optional) RSE tracing" in the Host Configuration Guide (SC27-8437) for more details.

The creation of the .dstore* log files is controlled by the –DDSTORE_* Java™ startup options, as described in "Defining extra Java startup parameters with _RSE_JAVAOPTS" in the Host Configuration Guide (SC27-8437).

Note:
  • The .dstore* log files start with a dot (.), which makes them hidden. Use z/OS® UNIX command ls –lA to list hidden files and directories. When using the client, select the Window > Preferences… > Remote Systems > Files preference page and enable “Show hidden files”.
  • The .dstore* log files are created in UTF8. Use z/OS UNIX command iconv -f UTF8IBM®-1047 .dstore* to display them in EBCDIC (when using code page IBM-1047).
  • Unlike all *.log files, the .dstore* log files are not removed automatically upon client reconnect. Removing these files is a manual action.

The RSE daemon and RSE thread pool specific log files are located in daemon-home, where daemon-home is the value of the daemon.log directive in rse.env.

The amount of data written to rsedaemon.log and rseserver.log is controlled by the modify rsedaemonlog and modify rseserverlog operator commands or by setting debug_level in rsecomm.properties . See "Operator commands" in the Host Configuration Guide (SC27-8437) and "(Optional) RSE tracing" in the Host Configuration Guide (SC27-8437) for more details.

serverlogs.count, stderr.*.log, and stdout.*.log are only created if the enable.standard.log directive in rse.env is active, or if the function is dynamically activated with the modify rsestandardlog on operator command..