The RSED start task supports the MODIFY LOGS operator command to collect z/OS Explorer host logs and setup information. The collected data is placed in a z/OS® UNIX file, $TMPDIR/feklogs.%sysname.%jobname, where $TMPDIR is the value of the TMPDIR directive in rse.env (default /tmp), %sysname is your z/OS system name and %jobname is the name of the RSED started task.
By default, only the server logs are collected. Command options allow you to collect different logs:
| USER | Collect log files for the specified user ID’s |
| AUDIT | Collect audit logs |
| NOSERVER | Do not collect server logs |
By default, all available log files are collected.
The RANGE command option allows you to limit this
selection to those log files that were updated in the last given number
of hours. 
z/OS Explorer will query your security product for access permits to FEK.CMD.LOGS.** profiles to determine if the requestor is allowed to collect the specified logs. By default, the requestor is the RSED started task user ID, unless the OWNER option is specified. Only the requestor has access to the file holding the collected data.
To collect data before the RSED started task can start, z/OS Explorer provides a sample job, FEKLOGS, which gathers all z/OS UNIX log files as well as z/OS Explorer installation and configuration information.
Sample job FEKLOGS is located in FEK.#CUST.JCL, unless you specified a different location when you customized and submitted job FEK.SFEKSAMP(FEKSETUP). See "Customization setup" in the Host Configuration Guide (SC27-8437) for more details.
The customization of FEKLOGS is described within the JCL. The customization encompasses the provision of a few key variables.