The MVS™ System Management Facility (SMF) collects and records a variety of system and job-related information. ISPF uses SMF to format information for a type 32 record. This type 32 record contains the names of the program functions and TSO commands being executed and the number of times each is used during the session. SMF also allows the installation to specify that the record is to include resources such as the total processor time under TCBs and SRBs and the total number of TGETs, TPUTs, and transactions associated with each name. The record is written when a TSO user logs off or when an SMF recording interval expires.

ISPF issues an SVC 109 (the extended service router, code X'19') to start and stop this functional accounting before and after the link to a program function, and before and after attaching a command. When processing command (CLIST) functions, the SVC 109 is issued before and after attaching the EXEC command processor. Therefore, the command name EXEC will be recorded, rather than the actual CLIST name.

The calls to SVC 109 can be nested depending on the nature of the program function or CLIST. The commands (and service units attributed to each command, if recorded) are accounted to the appropriate logical screen and are recorded as such. The command name ISPFSWAP is passed to SMF to indicate the user has swapped screens.

You must specify in module IEEMB846 the name of each module that is invoked for ISPF subfunctions or subcommands. You should also specify the command used to invoke ISPF. z/OS MVS System Management Facilities (SMF) provides details on including additional names. Without these additions to IEEMB846, ISPF will cause extensive counts of ***OTHER to be recorded in the SMF type 32 records.

Table 1 lists the ISPF options and their related module names plus any additional commands that can be implicitly or explicitly invoked by a particular option.

Table 2 lists the ISPF commands with the related modules: