Use of this trace makes sense if execution problems are suspected with requests in HSMS.
The HSMS trace is activated and deactivated with the privileged HSMS statements START-TRACE and STOP-TRACE.
START-TRACE |
DOMAIN = *ALL / list-poss(32): *REPOSITORY / *MESSAGES / *SHARE-PVS / *STATEMENTS ,TSN = *ALL / <alphanum-name 1..4> |
STOP-TRACE |
CLOSE-MODE = *NORMAL-CLOSE / *PSEUDO-CLOSE |
The DOMAIN operand determines whether the trace should cover all or some specific functional areas:
The operand value *ALL initiates trace entries for all functional areas which are subsequently named.
The operand value *REPOSITORY currently generates no trace entries.
The operand value *MESSAGES generates trace entries for all HSMS message outputs (parameter list of MSG7) via the DHSBMSG module.
The operand value *SHARE-PVS generates trace entries for the HSMS requests sent in shared pubset operation (internal HSMS commands) via the DHSBCIH module.
The operand value *STATEMENTS generates trace entries for all HSMS statements entered via the DHSEVAL module.
When the trace is deactivated the diagnostic information is written to a file. The CLOSE-MODE=*PSEUDO-CLOSE operand allows the trace to continue, but the data written up to this point can be read.
Name of the trace file: $SYSHSMS.HSM.Y.TRACE.<yyyymmdd>.<hhmmss>
The status of the trace is output using the HSMS statement SHOW-LOGGING-STATUS.
The content of the trace file can be edited and written to SYSLST using the HSMS statement LIST-LOGGING-FILE.