RSE user logging

userlog/$LOGNAME/
There are several log files created by the components related to RSE. All 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.
- .dstoreMemLogging - DataStore memory usage logging
- .dstoreTrace - DataStore action logging
- .dstoreHashmap.* - snapshot of the active DataStore hashmap
- .dstoreStackTrace.* - snapshot of the active DataStore threads and where they were invoked
- ffs.log - The log of the Foreign File System (FFS) server, which executes native MVS™ functions
- ffsget.log - The log of the file reader, that reads a sequential data set or a PDS member
- ffsput.log - The log of the file writer, that writes a sequential data set or a PDS member
- ffslock.log - The log of the lock manager, that locks or unlocks a sequential data set or a PDS member
- rsecomm.log - The log of the RSE server, that handles commands from the client and the communication logging of all services relying on RSE (may contain Java™ exception stack trace)

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 z/OS Explorer client, select the Window > Preferences… > Remote Systems > Files preference page and enable “Show hidden files”.
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).
The .dstore* log files are created in UTF8. Use z/OS UNIX command iconv -f UTF8 -t IBM-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.
There are operator commands available to control the amount of data written to some of the mentioned log files. Refer to "Operator commands" in the Host Configuration Guide (SC27-8437) for more information.
The ffs*.log and rsecomm.log files can also exist with a “.last” extension instead of a “.log” extension if keep.last.log=true is specified in rse.env. By default, the “.last” log files are not created.
The ffs*.log and rsecomm.log files will have an extended name if keep.all.logs=true is specified in rse.env. By default the extended name is used. The following is a sample extended name, where RSEDx represents the address space name of the thread pool in which the user is active and yyyymmddhhmmss is a date and time stamp (year, month, day, hour, minute, second): ffs.RSEDx#yyyymmddhhmmss.log