ISPF daemon configuration file (ispfdmn.conf)

Customize the ISPF daemon by specifying settings in the ispfdmn.conf file.
The ISPF daemon uses the definitions in ispfdmn.conf. This file is in /etc/jazz700/ccm, unless you specified a different location when you customized and submitted job hlq.SBLZSAMP(BLZCPBTK) as part of the installation and configuration of the Build System Toolkit. If you have not previously run BLZCPBTK, run it now. For more information, see Installing and configuring the Build System Toolkit on z/OS systems.
You can edit the ispfdmn.conf file with ISPF option 3.17. The ispfdmn.conf file must be customized to match your system environment. When you are using a US code page, comment lines start with a pound sign (#). Data lines can have a directive and its assigned value only, and comments are not allowed on the same line. Line continuations are not supported, and spaces around the equal sign (=) are not supported.
Note: The BLZISPFD started task must be restarted to pick up any changes you make.
The following definitions are required:
_ISPF_CLEANUP_INTERVAL
This environment variable is used with the _ISPF_CLEANUP_THRESHHOLD environment variable. The cleanup interval logs out any sessions that are inactive for the specified time within the specified threshold time. For example, with _ISPF_CLEANUP_INTERVAL set to 900000 and _ISPF_CLEANUP_THRESHHOLD set to 86400000, the daemon scans every 15 minutes and discards any sessions inactive for the last 24 hours.

Set this value to -1 to disable this cleanup.

_ISPF_CLEANUP_THRESHHOLD
See the _ISPF_CLEANUP_INTERVAL definition for an explanation of how this environment variable is used. The default is 86400000, which equals 24 hours.

Set this value to -1 to disable this cleanup.

_ISPF_DAEMON_APPLID=BLZAPPL
The application ID that the ISPF daemon uses for PassTicket security support. The application ID specified here must match what you define in the APPL class definition and the PTKTDATA class definition as shown in job BLZRACFT in hlq.SBLZSAMP.
_ISPF_DAEMONCONFIG_DIR
Specifies the absolute path to the ISPF daemon configuration directory, for example, /u/username/work/configuration/daemonconfig.
_ISPF_REGISTRY_DIR
Specifies the path to the daemon registry directory. This path is in a hierarchical file system (HFS) location where the daemon writes its location information. For example, you could set this path to /u/work/ccm.
JAVA_HOME
Specifies the path to the Java™ home directory. The default is /usr/lpp/java/J8.0_64. Change to match your Java installation.
PATH_TO_IRRRACF
Specifies the path to the location of the Java interface to your security product, IRRRacf.jar. The default is /usr/include/java_classes/. Change to match your security software setup.
RTC_HOME
Specifies the path to the IBM® Engineering Workflow Management (EWM) home directory. The default is /usr/lpp/jazz/v7.0.0/. Change to match your EWM installation.
SCM_WORK
The path to the directory where the metadata are stored for PDSEs. The metadata are stored under ${SCM_WORK}/SCM. Set this path to your work directory, which is /u/jazz700/ccm by default. Developers running the EWM ISPF client require write access to the directory pointed to by SCM_WORK (and at least read and execute access to its parent directories).
The following definitions are optional:
_BPXK_SETIBMOPT_TRANSPORT
Specifies the TCP/IP stack name if the site is using multiple TCP/IP stacks and the default TCPIP stack is not being used.
_CEE_DMPTARG
Specifies the absolute path to the directory where CEEDUMPs are written, for example, /u/username/work/ccm.
_ISPF_CLEAN
When you start the daemon, if you want to force Eclipse to reinitialize the cached data, set this definition to –clean.
_ISPF_CLIENT_LOG_MAX
Specifies the initial maximum number of client trace log files for a user. The default number of trace log files is 3.

To disable client trace logging, set this value to zero.

_ISPF_CLIENT_LOG_OVER
Specifies whether individual users can override the default values for _ISPF_CLIENT_LOG_MAX and _ISPF_CLIENT_LOG_SIZE set in the ISPF daemon configuration file. Valid values are YES and NO. The default setting is YES. Setting this value to NO disables individual users from changing the logging settings in the ISPF client preferences.
_ISPF_CLIENT_LOG_SIZE
Specifies the initial maximum client trace log file size for a user, in bytes. The default is 100000 bytes.

When the first log file reaches the size that is specified or allowed to default, subsequent log entries are logged in a new log file.

_ISPF_DAEMON_LOG_CONF
Specifies the absolute path to where the ISPF daemon trace log files are stored, for example, /u/username/conf/ccm/commons-logging.properties.
The log files are stored in a path that is relative to the value of _ISPF_REGISTRY_DIR, for example, daemon registry directory/logs/userid. To view the log files, open Help (F1) and select 1. Display logs.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki