Chapter 20 DCT (Remote Destination Control Table Monitor process) Messages

The messages in this chapter are generated by the DCTMON subsystem, the Remote Destination Control Table Monitor process. Each event includes the DCTMON process name ($ZDMnn).

The minimum RVUs required by DCTMON are:

H-Series: H06.24; the applicable DCTMON SPR is T1000H01^AAA
J-Series: J06.13; the applicable DCTMON SPR is T1000H01^AAA
L-Series: L15.08; the applicable DCTMON SPR is T1000L02

5001

The DCT Access Monitor Process, process-name, has started in processor cpunum.

Program file: programfile

Priority: priority

Autorestart count: restart-count

`process-name`	is the name of the DCT Access Monitor Process.
`cpunum`	is the processor number where DCTMON is running.
`programfile`	is the DCTMON program file.
`priority`	is the priority at which the DCTMON process is running.
`restart-count`	is the autorestart count configured for the process.

Cause The DCTMON process was started by the operator or $ZPM. In the event of a subsequent failure of the DCTMON process, the Persistence Manager ($ZPM) automatically restarts DCTMON. DCTMON cannot distinguish between these three cases — a manual start by the operator, a start by $ZPM, or a restart by $ZPM).

Effect The DCT Access Monitor Process ($ZDMnn) is running.

Recovery Informational message only; no corrective action is needed.

5002

The DCT Access Monitor Process, process-name, has been terminated, Reason: reason.

`process-name`	is the name of the DCT Access Monitor Process.
`reason`	is an enumeration of the cause of the termination.

Cause The DCT Access Monitor Process terminated voluntarily. The termination was either by an operator command, or an environmental problem, or an internal error caused DCTMON to self-terminate. If this event is due to an environmental problem, there will have been a dctmon-info (5004) or version-mismatch (5005) event reporting the environmental problem found by DCTMON.

Effect The DCT Access Monitor Process is no longer running.

Recovery If this event is due to an environmental problem, follow recovery instructions for the dctmon-info (5004) or version-mismatch (5005) event. After correcting any environmental problems found by DCTMON, restart the process with an operator command. If the event is due to an internal error, collect any ZZSA* saveabend files that may have been generated by the system, and inform your service provider of the problem. Also, confirm in this case that the affected DCTMON process was restarted by $ZPM.

5003

DCTMON Access Monitor Process internal trace entry trace-entry.

trace-entry

is a structured token containing the trace record. Only the ASCII header is displayed in the message text. The contents of the trace record are:

The header; a 10 character ASCII string
Four integer fields
The trace type
The trace timestamp

Cause These records are generated when an internal trace is enabled.

Effect The DCT Access Monitor Process state is unchanged.

Recovery Informational message only; no corrective action is needed.

5004

DCT Access Monitor Process, process-name, reports dctmon-info.

`process-name`	is the name of the DCT Access Monitor Process.
`dctmon-info`	is an enumeration containing the cause of the environmental problem.

Cause DCTMON found an environmental problem, or the process name is wrong (not $ZDMnn). This event is usually followed by a DCTMON termination event.

Effect This is an informational message, but for certain environmental problems the DCT Access Monitor Process terminates.

Recovery Corrective action may be required to fix one or more environmental problems:

wrong-processor-name - alter DCTMON's startup parameters (generic process configuration under SCF.)

5005

Process process-name is not compatible with the current version of the Kernel message system.

process-name

is the name of the DCT Access Monitor Process.

Cause The process (DCTMON) made a comparison of its own version and that of the Kernel message system. The versions were incompatible and this event was followed by a process termination event.

Effect The process (DCTMON) terminates.

Recovery Check SPR requisites for NSK (T9050) and DCTMON (T1000). Ensure that the versions of T1000 and T9050 are compatible.

5006

DSM Trace error error, error-detail, Operation trace-action.

`error`	is the error code returned from the DSM trace routine.
`error-detail`	is the error detail code returned from the DSM trace routine.
`trace-action`	is the action that was performed when the error occurred.

Cause DCTMON encountered an error using the DSM trace routines.

Effect Any pending trace is terminated.

Recovery Investigate the cause of the error. Reissue the SCF TRACE command.

5007 (not applicable on L-series)

The DCT Access Monitor Process process-name, has delayed remote DCTMON discovery. Reason: cause.

`process-name`	is the name of the DCT Access Monitor Process.
`cause`	is the reason that DCTMON has delayed remote DCTMON discovery.

Cause The ServerNet node number is not valid in the local node.

Effect The DCTMON process is not able to discover remote DCTMON processes running in other nodes. Remote DCT access operations can not be done directly via the ServerNet cluster with assistance from DCTMON processes.

Recovery Ensure that the local node is properly configured for connectivity to the ServerNet cluster. Confirm that the local node has been connected to the ServerNet cluster. If necessary, start the ServerNet cluster subsystem and Expand-over-ServerNet line handlers in the local node.

5008 (not applicable on L-series)

The DCT Access Monitor Process process-name, has resumed remote DCTMON discovery. Reason: cause.

`process-name`	is the name of the DCT Access Monitor Process.
`cause`	is the reason that DCTMON has resumed remote DCTMON discovery.

Cause The ServerNet node number is now valid in the local node.

Effect The DCTMON process will resume discovery of remote DCTMON processes. Once discovery completes, remote DCT access operations are performed directly via the ServerNet cluster with assistance from the DCTMON processes.

Recovery Informational message only; no corrective action is needed.