Chapter 68 OMF (Object Monitoring Facility) Messages

The messages in this chapter are sent by the Object Monitoring Facility (OMF) subsystem. The subsystem ID displayed by these messages includes OMF as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

100

timestamp pid OMF: CPU CPU-number, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`CPU-number`	is the CPU number that is the subject of the event.
`cur‑state`	is the current state of the processor.
`prev-state`	is the previous state of the processor.
`sampling-int`	is the sampling interval of the CPU object type.

Cause A monitored processor reached the up state after being over threshold, full, or down.

Effect The processor is functioning normally again.

Recovery This is an informational message only; no corrective action is necessary.

101

timestamp pid OMF: CPU CPU-number, Current State = cur‑state, Previous State = prev-state, Current Usage = current-usage, Configured Threshold = threshold, Sampling Interval = sampling‑int minutes

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`CPU-number`	is the CPU number that is the subject of the event.
`cur‑state`	is the current state of the processor.
`prev-state`	is the previous state of the processor.
`current-usage`	is the current usage of the processor.
`threshold`	is the configured threshold of the processor.
`sampling-int`	is the sampling interval of the CPU object type.

Cause A monitored processor is operating over its configured threshold, and its previous state was either up, full, or down.

Effect This monitored processor may be the cause of performance degradation on the system if it continues to operate over its configured threshold for an extended period of time.

Recovery Follow your normal procedures to continue or to correct the problem.

102

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`CPU-number`	is the CPU number that is the subject of the event.
`cur‑state`	is the current state of the processor.
`prev-state`	is the previous state of the processor.
`current-usage`	is the current usage of the processor.
`threshold`	is the configured threshold of the processor.
`sampling-int`	is the sampling interval of the CPU object type.

Cause A monitored processor is being used at 100 percent of its capacity, and its previous state was either up, over threshold, or down.

Effect The monitored processor is currently at its maximum usage capability; the system may be experiencing performance problems.

Recovery Follow your normal procedures to continue or to correct the problem.

103

timestamp pid OMF: CPU CPU-number, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`CPU-number`	is the CPU number that is the subject of the event.
`cur‑state`	is the current state of the processor.
`prev-state`	is the previous state of the processor.
`sampling-int`	is the sampling interval of the CPU object type.

Cause A monitored processor has gone down, and its previous state was either up, over threshold, or full.

Effect The processor is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

104

timestamp pid OMF: Action complete event for CPU CPU-number, Current State = cur-state, Sampling Interval = sampling-int minutes

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`CPU-number`	is the CPU number that is the subject of the event.
`cur‑state`	is the current state of the processor, which is set to the value of the corresponding action attention event that preceded it.
`sampling-int`	is the sampling interval of the CPU object type.

Cause A monitored processor left a state that generated an action attention event.

Effect The processor is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

200

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the up state, and its previous state was not the up state.

Effect The device is available for use.

Recovery This is an informational message only; no corrective action is necessary.

201

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the down state, and its previous state was not the down state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

202

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the special state, and its previous state was not the special state.

Effect The device is no longer accessible for normal processing.

Recovery Follow your normal procedures to continue or to correct the problem.

203

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the mount state, and its previous state was not the mount state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

204

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the revive state, and its previous state was not the revive state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

205

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the reserved state, and its previous state was not the reserved state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

206

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the exercise state, and its previous state was not the exercise state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

207

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the exclusive state, and its previous state was not the exclusive state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

208

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the harddown state, and its previous state was not the harddown state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

209

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the format state, and its previous state was not the format state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

210

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the config error state, and its previous state was not the config error state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

211

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the lacks resource state, and its previous state was not the lacks resource state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

212

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached the premature takeover state, and its previous state was not the premature takeover state.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

216

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device reached an unknown state, and its previous state was a known state. (Known states are up, down, special, mount, revive, reserved, exercise, exclusive, harddown, format, config error, lacks resource, and premature takeover.)

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

217

timestamp pid OMF: DEVICE $device-name, Primary CPU Inaccessible[ while communicating with the IOP, Error = error], Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`error`	is the file system error that occurred while monitoring this device; if there is no error, this field is blank.
`sampling-int`	is the sampling interval of the device object type.

Cause The primary processor of a monitored device has gone down or is inaccessible, and previously the primary processor was running.

Effect The device is still accessible through the backup processor.

Recovery Follow your normal procedures to continue or to correct the problem.

218

timestamp pid OMF: DEVICE $device-name, Primary CPU Accessible, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The primary processor of a monitored device has gone back to normal and previously the primary processor was down.

Effect The device is now accessible through the primary processor.

Recovery This is an informational message only; no corrective action is necessary.

219

timestamp pid OMF: DEVICE $device-name, Backup CPU Inaccessible[ while communicating with the IOP, Error = error], Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`error`	is the file system error that occurred while monitoring this device; if there is no error, this field is blank.
`sampling-int`	is the sampling interval of the device object type.

Cause The backup processor of a monitored device has gone down or is inaccessible and previously the backup processor was running.

Effect The device is still accessible through the primary processor.

Recovery Follow your normal procedures to continue or to correct the problem.

220

timestamp pid OMF: DEVICE $device-name, Backup CPU Accessible, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The backup processor of a monitored device has gone back to normal and previously the backup processor was down.

Effect The device is now accessible through the backup processor.

Recovery This is an informational message only; no corrective action is necessary.

221

timestamp pid OMF: DEVICE $device-name, Primary and Backup CPU Inaccessible, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The primary and backup processors of a monitored device have gone down and previously one or both of the processors were up.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

223

timestamp pid OMF: DEVICE $device-name, CPU Switch, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The primary and backup processors of a monitored device switched, and previously they were normal.

Effect The device is still accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

224

timestamp pid OMF: DEVICE $device-name, CPU Back to Normal, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The primary and backup processors of a monitored device switched back to normal and previously they were not normal.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

225

timestamp pid OMF: DEVICE $device-name, PATH Switch, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The path of a monitored device switched and previously it was normal.

Effect The device is still accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

226

timestamp pid OMF: DEVICE $device-name, PATH Back to Normal, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The path of a monitored device switched back to normal and previously it was not normal.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

227

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device, defined as audited in the PUP LISTDEV file, has been audited and previously it was not.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

228

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device, defined as audited in the PUP LISTDEV file, has not been audited and previously it was audited.

Effect The device is still accessible, but it is not audited anymore.

Recovery Follow your normal procedures to continue or to correct the problem.

229

timestamp pid OMF: DEVICE $device-name, The current configuration is not the same as the ideal one, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The configuration of a monitored device is not the same as the ideal configuration.

Effect The device is still accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

230

timestamp pid OMF: DEVICE $device-name, The current configuration is the same as the ideal one, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause The configuration of a monitored device is now the same as the ideal configuration.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

231

timestamp pid OMF: DEVICE $device-name, Sampling Error, File System Error = file-syst-error, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`file-syst-error`	is the file system error.
`sampling-int`	is the sampling interval of the device object type.

Cause A file-system error occurred while monitoring a device, and previously there was a different error or no error at all.

Effect The device is no longer accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

232

timestamp pid OMF: DEVICE $device-name, No more Sampling Error, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`sampling-int`	is the sampling interval of the device object type.

Cause No more errors are encountered while monitoring a device and previously there was an error.

Effect The device is now accessible.

Recovery This is an informational message only; no corrective action is necessary.

233

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`sampling-int`	is the sampling interval of the device object type.

Cause The device $0 is defined in the PUP LISTDEV file with the console state ON, but the current console state is OFF.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

234

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`sampling-int`	is the sampling interval of the device object type.

Cause The device $0 console state is ON, and previously it was OFF.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

237

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored optical disk device is unlocked and previously it was locked.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

238

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored optical disk device is locked, and previously it was unlocked.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

239

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored optical disk device is not opened, and previously it was opened, either in read or write mode.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

240

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored optical disk device is opened in read mode, and previously it was not opened or it was opened in write mode.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

241

timestamp pid OMF: DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Ideal State = ideal-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the current state of the device.
`prev-state`	is the previous state of the device.
`ideal-state`	is the ideal state of the device as defined in the PUP-LISTDEV-FILE.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored optical disk device has been opened in write mode, and previously it was not opened or it was opened in read mode.

Effect The device is still accessible.

Recovery This is an informational message only; no corrective action is necessary.

242

timestamp pid OMF: Action complete event for DEVICE $device-name, Current State = cur‑state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the device name that is the subject of the event.
`cur‑state`	is the value of the corresponding action attention event that preceded it.
`sampling-int`	is the sampling interval of the device object type.

Cause A monitored device left a state that generated an action attention event.

Effect This event means the DEVICE is no longer in a state operator action.

Recovery This is an informational message only; no corrective action is necessary.

300

timestamp pid OMF: DISK $disk-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk reached the up state, and its previous state was either over threshold, over extent, full, down, or an illegal device.

Effect The disk is functioning normally.

Recovery This is an informational message only; no corrective action is necessary.

301

timestamp pid OMF: DISK $disk-name, Current State = cur‑state, Previous State = prev-state, Current Usage = current-usage, Configured Threshold = threshold, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`current‑usage`	is the current percentage of disk space used.
`threshold`	is the configured threshold of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk exceeded its configured threshold, and its previous state was either up, over extent, full, down, or an illegal device.

Effect The monitored disk may become full in the near future.

Recovery This is an informational message only; no corrective action is necessary.

302

timestamp pid OMF: DISK $disk-name, Current State = cur‑state, Previous State = prev-state, Largest Free Extent = = free-extent, Extent Size = extent-size, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`free-extent`	is the current largest free extent of the disk.
`extent-size`	is the configured extent size required of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause The largest free extent of a monitored disk is smaller than the required one, and its previous state was either up, over threshold, full, down, or an illegal device.

Effect The monitored disk is lacking the extent size free space required.

Recovery Follow your normal procedures to continue or to correct the problem.

303

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`current‑usage`	is the current percentage of disk space used.
`threshold`	is the configured threshold of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk is being used at 100 percent of its capacity. There is no more available space on that disk, and its previous state was either up, over threshold, over extent, down, or an illegal device.

Effect No more space is available on that monitored disk.

Recovery Follow your normal procedures to continue or to correct the problem.

304

timestamp pid OMF: DISK $disk-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk has gone down, and its previous state was either up, over threshold, over extent, full, or an illegal device.

Effect The disk is not accessible.

Recovery Follow your normal procedures to continue or to correct the problem.

305

timestamp pid OMF: DISK $disk-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`prev-state`	is the previous state of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk is not a disk volume; that is, the disk does not exist, and its previous state was either up, over threshold, over extent, full, or down.

Effect The disk is not available.

Recovery This is an informational message only; no corrective action is necessary.

306

timestamp pid OMF: Action complete event for DISK $disk-name, Current State = cur‑state, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`disk-name`	is the disk name that is the subject of the event.
`cur‑state`	is the current state of the disk.
`sampling-int`	is the sampling interval of the disk object type.

Cause A monitored disk left a state that generated an action attention event.

Effect The disk is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

307

timestamp pid OMF: DISK $disk-name, Unable to get disk information, File System Error = file-syst-error, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the name of the OMF process that generated the event.
`disk-name`	is the name of the disk that is the subject of the event.
`file-syst-error`	is the file system error.
`sampling-int`	is the sampling interval of the process object type.

Cause OMF cannot get information about a disk.

Effect The state of the disk remains unchanged until OMF is able to obtain information about it.

Recovery Review the file system error information to determine why OMF is unable to obtain information about the disk.

400

timestamp pid OMF: FILE $file-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file is an existing one, and its previous state was either over threshold, full, broken, corrupt, or absent.

Effect The file is back to normal.

Recovery This is an informational message only; no corrective action is necessary.

401

timestamp pid OMF: FILE $file-name, Current State = cur‑state, Previous State = prev-state, Current Usage = current-usage, Configured Threshold = threshold, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`current‑usage`	is the current percentage of file space used.
`threshold`	is the configured threshold of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file exceeded its configured threshold, and its previous state was either present, full, broken, corrupt, or absent.

Effect The monitored file may become full in the near future.

Recovery This is an informational message only; no corrective action is necessary.

402

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`current‑usage`	is the current percentage of file space used.
`threshold`	is the configured threshold of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file is being used at 100 percent of its capacity. There is no more available space in that file, and its previous state was either present, over threshold, broken, corrupt, or absent.

Effect No more space is available in that file.

Recovery Follow your normal procedures to continue or to correct the problem.

403

timestamp pid OMF: FILE $file-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file reached the broken state, and its previous state was either present, over threshold, full, corrupt, or absent.

Effect This file is broken.

Recovery Follow your normal procedures to continue or to correct the problem.

404

timestamp pid OMF: FILE $file-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file reached the corrupt state, and its previous state was either present, over threshold, full, broken, or absent.

Effect This file is corrupted.

Recovery Follow your normal procedures to continue or to correct the problem.

405

timestamp pid OMF: FILE $file-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`prev-state`	is the previous state of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file does not exist, and its previous state was either present, over threshold, full, broken, or corrupt.

Effect A monitored file is not available.

Recovery This is an informational message only; no corrective action is necessary.

406

timestamp pid OMF: Action complete event for FILE $file-name, Current State = cur‑state, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name that is the subject of the event.
`cur‑state`	is the current state of the file.
`sampling-int`	is the sampling interval of the file object type.

Cause A monitored file left a state that generated an action attention event.

Effect A monitored file is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

500

timestamp pid OMF: PRINT PROCESS $print-proc-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`prev-state`	is the previous state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process reached the active state, and its previous state was either drain, procerror, or not found.

Effect The print process is currently in use.

Recovery This is an informational message only; no corrective action is necessary.

501

timestamp pid OMF: PRINT PROCESS $print-proc-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`prev-state`	is the previous state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process reached the drain state, and its previous state was either active, procerror, dormant, or not found.

Effect When the print process finishes printing the current job, it will stop.

Recovery Follow your normal procedures to continue or to correct the problem.

502

timestamp pid OMF: PRINT PROCESS $print-proc-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`prev-state`	is the previous state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process reached the procerror state, and its previous state was either active, drain, dormant, or not found.

Effect The supervisor determined that the print process was not responding correctly, and placed it into the procerror state.

Recovery Follow your normal procedures to continue or to correct the problem.

503

timestamp pid OMF: PRINT PROCESS $print-proc-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`prev-state`	is the previous state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process reached the dormant state, and its previous state was either drain, procerror, or not found.

Effect The print process was in an abnormal state and is now normal, but is not currently printing any job.

Recovery This is an informational message only; no corrective action is necessary.

504

timestamp pid OMF: PRINT PROCESS $print-proc-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`prev-state`	is the previous state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process does not exist under its configured supervisor, and its previous state was either active, drain, procerror, or dormant.

Effect A monitored print process is not available.

Recovery Follow your normal procedures to continue or to correct the problem.

505

timestamp pid OMF: Action complete event for PRINT PROCESS $print-proc-name, Current State = cur-state, Supervisor Name = $superv‑name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`print-proc-name`	is the print process name that is the subject of the event.
`cur‑state`	is the current state of the print process.
`superv-name`	is the supervisor name under which the print process is configured within OMF.
`sampling-int`	is the sampling interval of the print process object type.

Cause A monitored print process left a state that generated an action attention event.

Effect A monitored print process is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

600

timestamp pid OMF: PROCESS $process-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`cur‑state`	is the current state of the process.
`prev-state`	is the previous state of the process.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process is running normally, and its previous state was either wrong processor, wrong priority, wrong processor and wrong priority, suspended, debug, inspect, saveabend, or stopped.

Effect The process is running normally.

Recovery This is an informational message only; no corrective action is necessary.

601

timestamp pid OMF: PROCESS $process-name, Current State = cur‑state, Previous State = prev-state, Current CPU = cur-CPU, Default CPU = def-CPU, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`cur‑state`	is the current state of the process.
`prev-state`	is the previous state of the process.
`cur-CPU`	is the CPU that the process is currently running in.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process is running in the wrong processor, and its previous state was either running, wrong priority, suspended, debug, inspect, saveabend, or stopped.

Effect The process is running in the wrong processor according to its configured default one.

Recovery Follow your normal procedures to continue or to correct the problem.

602

timestamp pid OMF: PROCESS $process-name, Current State = cur‑state, Previous State = prev-state, Current Priority = cur‑priority, Default Priority = def-priority, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`cur‑state`	is the current state of the process.
`prev-state`	is the previous state of the process.
`cur-priority`	is the priority that the process is currently running under.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process is running under the wrong priority, and its previous state was either running, wrong processor, suspended, debug, inspect, saveabend, or stopped.

Effect The process is running under the wrong priority according to its configured default one.

Recovery Follow your normal procedures to continue or to correct the problem.

604

timestamp pid OMF: PROCESS $process-name, Current State = SUSPENDED, Previous State = prev-state, Default CPU = def-CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`prev-state`	is the previous state of the process.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process reached the suspended state, and its previous state was either running, wrong processor, wrong priority, wrong processor and wrong priority, debug, inspect, saveabend, or stopped.

Effect The process is not available for normal processing, which is an abnormal condition.

Recovery Follow your normal procedures to continue or to correct the problem.

605

timestamp pid OMF: PROCESS $process-name, Current State = DEBUG, Previous State = prev-state, Default CPU = def-CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`prev-state`	is the previous state of the process.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process reached the debug state, and its previous state was either running, wrong processor, wrong priority, wrong processor and wrong priority, suspend, inspect, saveabend, or stopped.

Effect The process is not available for normal processing, which is an abnormal condition.

Recovery Follow your normal procedures to continue or to correct the problem.

606

timestamp pid OMF: PROCESS $process-name, Current State = INSPECT, Previous State = prev-state, Default CPU = def-CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`prev-state`	is the previous state of the process.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process reached the inspect state, and its previous state was either running, wrong processor, wrong priority, wrong processor and wrong priority, suspend, debug, saveabend, or stopped.

Effect The process is not available for normal processing, which is an abnormal condition.

Recovery Follow your normal procedures to continue or to correct the problem.

607

timestamp pid OMF: PROCESS $process-name, Current State = SAVEABEND, Previous State = prev-state, Default CPU = def-CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`prev-state`	is the previous state of the process.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process reached the saveabend state, and its previous state was either running, wrong processor, wrong priority, wrong processor and wrong priority, suspend, debug, inspect, or stopped.

Effect The process has encountered a problem and is currently saving the value of all its variables and registers into a file. The process is not available for normal processing, which is an abnormal condition.

Recovery Follow your normal procedures to continue or to correct the problem.

608

timestamp pid OMF: PROCESS $process-name, Current State = STOPPED, Previous State = prev-state, Default CPU = def‑CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`prev-state`	is the previous state of the process.
`def-CPU`	is the CPU that the process is supposed to be running in according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process stopped, and its previous state was either running, wrong processor, wrong priority, wrong processor and wrong priority, suspend, debug, inspect, or saveabend.

Effect The process is not running anymore.

Recovery Follow your normal procedures to continue or to correct the problem.

609

timestamp pid OMF: Action complete event for PROCESS $process-name, Current State = cur-state, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the process name that is the subject of the event.
`cur-state`	is the current state of the process.
`sampling-int`	is the sampling interval of the process object type.

Cause A monitored process left a state that generated an action attention event.

Effect The process is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

610

timestamp pid OMF: PROCESS $process-name, Current State = NOT MONITORED, Previous State = prev-state, Default CPU = def‑CPU, Default Priority = def-priority, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the name of the process that is the subject of the event.
`prev-state`	is the previous state of the process.
`def‑CPU`	is the the CPU that the process is supposed to be running in, according to its configuration within OMF.
`def-priority`	is the priority that the process is supposed to be running under, according to its configuration within OMF.
`sampling-int`	is the sampling interval of the process object type.

Cause A PROCESS is in the OMF configuration file, but is not monitored by OMF.

Effect The process is not monitored, but is still in the UP state.

Recovery Follow your normal procedures.

700

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur-state, Previous State = prev-state, Supervisor Name = $superv‑name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector reached the active state, and its previous state was either over threshold, drain, full, dormant, error, or not found.

Effect The spooler collector is working normally.

Recovery This is an informational message only; no corrective action is necessary.

701

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Current Usage = current-usage, Configured Threshold = threshold, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`current‑usage`	is the current percentage of spooler collector file space used.
`threshold`	is the configured threshold of the spooler collector.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector exceeded its configured threshold, and its previous state was either active, drain, full, dormant, error, or not found.

Effect The spooler collector data file may become full in the near future.

Recovery This is an informational message only; no corrective action is necessary.

702

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector reached the drain state, and its previous state was either active, over threshold, full, dormant, error, or not found.

Effect The spooler collector does not accept new jobs for spooling, but jobs currently being spooled continue until completion. When all open jobs complete, the spooler collector enters the dormant state.

Recovery This is an informational message only; no corrective action is necessary.

703

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`current‑usage`	is the current percentage of spooler collector file space used.
`threshold`	is the configured threshold of the spooler collector.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector is being used at 100 percent of its capacity, and its previous state was either active, over threshold, drain, dormant, error, or not found.

Effect No more space is available in the spooler collector data file, and the spooler collector will not accept new jobs for spooling.

Recovery This is an informational message only; no corrective action is necessary.

704

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector reached the dormant state, and its previous state was either active, over threshold, drain, full, error or not found.

Effect The spooler collector cannot accept new jobs for spooling, and no jobs are currently being spooled.

Recovery This is an informational message only; no corrective action is necessary.

705

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector reached the error state, and its previous state was either active, over threshold, drain, full, dormant, or not found.

Effect The spooler collector cannot function anymore because of a NonStop Kernel file-system error or a new process error.

Recovery Follow your normal procedures to continue or to correct the problem.

706

timestamp pid OMF: SPOOLER-COLLECTOR $collector-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`prev-state`	is the previous state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector does not exist under its configured supervisor, and its previous state was either active, over threshold, drain, full, dormant, or error.

Effect A monitored spooler collector is not available.

Recovery This is an informational message only; no corrective action is necessary.

707

timestamp pid OMF: Action complete event for SPOOLER-COLLECTOR $collector-name, Current State = cur-state, Supervisor Name = $superv‑name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`collector-name`	is the spooler collector name that is the subject of the event.
`cur‑state`	is the current state of the spooler collector.
`superv-name`	is the supervisor name under which the spooler collector is configured within OMF.
`sampling-int`	is the sampling interval of the spooler collector object type.

Cause A monitored spooler collector leaves a state that generated an action attention event.

Effect A monitored spooler collector is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

800

timestamp pid OMF: SPOOLER-DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the busy state, and its previous state was either suspended, offline, procerror, deverror, or not found.

Effect The spooler device is again functioning normally and is currently printing a job.

Recovery This is an informational message only; no corrective action is necessary.

801

timestamp pid OMF: SPOOLER-DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the waiting state, and its previous state was either suspended, offline, procerror, deverror, or not found.

Effect The spooler device is again functioning normally and is not currently printing a job.

Recovery This is an informational message only; no corrective action is necessary.

802

timestamp pid OMF: SPOOLER-DEVICE $device-name, Current State = cur‑state,[ Error = error-number,] Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`error‑number`	is the last error number that occurred on the spooler device if any.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the suspended state, and its previous state was either busy, waiting, offline, procerror, deverror, or not found.

Effect A job was printing on the device, but printing has stopped as a result of a DEV, SUSPEND command within the SPOOLCOM program.

Recovery Follow your normal procedures to continue or to correct the problem.

803

timestamp pid OMF: SPOOLER-DEVICE $device-name, Current State = cur‑state,[ Error = error-number,] Previous State = prev‑state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`error‑number`	is the last error number that occurred on the spooler device if any.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the offline state, and its previous state was either busy, waiting, suspended, procerror, deverror, or not found.

Effect The spooler device is not available for printing jobs.

Recovery Follow your normal procedures to continue or to correct the problem.

804

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`error‑number`	is the last error number that occurred on the spooler device if any.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the procerror state, and its previous state was either busy, waiting, suspended, offline, deverror, or not found.

Effect The supervisor has determined that the spooler device is not working correctly. The spooler device is unusable until the print process is restarted.

Recovery Follow your normal procedures to continue or to correct the problem.

805

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`error‑number`	is the last error number that occurred on the spooler device if any.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device reached the deverror state, and its previous state was either busy, waiting, suspended, offline, procerror, or not found.

Effect A NonStop Kernel file-system error occurred on the device while a job was printing.

Recovery Follow your normal procedures to continue or to correct the problem.

806

timestamp pid OMF: SPOOLER-DEVICE $device-name, Current State = cur‑state, Previous State = prev-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`prev-state`	is the previous state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device does not exist under its configured supervisor, and its previous state was either busy, waiting, suspended, offline, procerror, or deverror.

Effect A monitored spooler device is not available.

Recovery Follow your normal procedures to continue or to correct the problem.

807

timestamp pid OMF: Action complete event for SPOOLER-DEVICE $device-name, Current State = cur-state, Supervisor Name = $superv-name, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`device-name`	is the spooler device name that is the subject of the event.
`cur‑state`	is the current state of the spooler device.
`superv-name`	is the supervisor name under which the spooler device is configured within OMF.
`sampling-int`	is the sampling interval of the spooler device object type.

Cause A monitored spooler device left a state that generated an action attention event.

Effect A monitored spooler device is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

900

timestamp pid OMF:SUPERVISOR $supervisor-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`prev-state`	is the previous state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor reached the active state, and its previous state was either cold, drain, warm or dormant.

Effect The spooler supervisor is again fully operational.

Recovery This is an informational message only; no corrective action is necessary.

901

timestamp pid OMF:SUPERVISOR $supervisor-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`prev-state`	is the previous state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor reached the cold state, and its previous state was either active, drain, warm, or dormant.

Effect The spooler supervisor is ready for declaration and initialization of collectors and print processes, but is not yet operational.

Recovery Follow your normal procedures to continue or to correct the problem.

902

timestamp pid OMF:SUPERVISOR $supervisor-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`prev-state`	is the previous state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor reached the drain state, and its previous state was either active, cold, warm, or dormant.

Effect The spooler supervisor is currently stopping.

Recovery Follow your normal procedures to continue or to correct the problem.

903

timestamp pid OMF:SUPERVISOR $supervisor-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`prev-state`	is the previous state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor reached the warm state, and its previous state was either active, cold, drain, or dormant.

Effect The spooler supervisor is ready for declaration and initialization of collectors and print processes, but is not yet operational.

Recovery Follow your normal procedures to continue or to correct the problem.

904

timestamp pid OMF:SUPERVISOR $supervisor-name, Current State = cur‑state, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`prev-state`	is the previous state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor reached the dormant state, and its previous state was either active, cold, drain or warm.

Effect The spooler supervisor is running, but you cannot enter the SPOOLCOM program to obtain information because there is no supervisor with which the SPOOLCOM program can communicate.

Recovery Follow your normal procedures to continue or to correct the problem.

905

timestamp pid OMF: Action complete event for SUPERVISOR $supervisor-name, Current State = cur-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`supervisor-name`	is the spooler supervisor name that is the subject of the event.
`cur‑state`	is the current state of the spooler supervisor.
`sampling-int`	is the sampling interval of the spooler supervisor object type.

Cause A monitored spooler supervisor left a state that generated an action attention event.

Effect The monitored spooler supervisor is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1000

timestamp pid OMF: Tape Mount Request tape-mount-id, has been proceeded Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`tape-mount-id`	is the tape mount request identification number that is the subject of the event.
`sampling-int`	is the sampling interval of the tape mount object type.

Cause An outstanding tape mount request has been processed, if it was not the first time this tape mount request was encountered, meaning that it was in the odd or down state before being processed.

Effect An outstanding tape mount request has been processed.

Recovery This is an informational message only; no corrective action is necessary.

1001

timestamp pid OMF: Tape Mount Request tape-mount-id, has been pending for time-elapsed minutes, [Tape Device $tape-name,] Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`tape-mount-id`	is the tape mount request identification number that is the subject of the event.
`time-elapsed`	is the time, in minutes, that the tape mount request has been waiting.
`tape-name`	is the Tape Device Name, if available.
`sampling-int`	is the sampling interval of the tape mount object type.

Cause An outstanding tape mount request has been encountered for the second time.

Effect This outstanding tape mount request is now in the odd state, and still has not been responded to.

Recovery Follow your normal procedures to continue or to correct the problem.

1002

timestamp pid OMF: Tape Mount Request tape-mount-id, has been pending for time-elapsed minutes, [Tape Device $tape-name,] Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`tape-mount-id`	is the tape mount request identification number that is the subject of the event.
`time-elapsed`	is the time, in minutes, that the tape mount request has been waiting.
`tape-name`	is the Tape Device Name, if available.
`sampling-int`	is the sampling interval of the tape mount object type.

Cause An outstanding tape mount request has been encountered for the third time.

Effect This outstanding tape mount request is now in the down state, and still has not been responded to.

Recovery Follow your normal procedures to continue or to correct the problem.

1003

timestamp pid OMF: Action complete event for OUTSTANDING Tape Mount Request tape-mount-id, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`tape-mount-id`	is the tape mount request identification number that is the subject of the event.
`sampling-int`	is the sampling interval of the tape mount object type.

Cause An outstanding tape mount request left a state that generated an action attention event.

Effect This outstanding tape mount request is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1100

timestamp pid OMF: TMF Audit Dump Process $process-name, Current Status = cur-status, Previous Status = prev-status, Current State = cur‑state, Previous State = prev-state, [Current Audit File = $cur-file, ] Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the audit dump process name that is the subject of the event.
`cur‑status`	is the current status of the audit dump process.
`prev-status`	is the previous status of the audit dump process.
`cur‑state`	is the current state of the audit dump process.
`prev-state`	is the previous state of the audit dump process.
`cur‑file`	is the name of the file currently being dumped if the current status of the audit dump process is Active.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process reached the enabled state, and its previous state was deferred.

Effect The audit dump process is now available for dumping audit trail files.

Recovery This is an informational message only; no corrective action is necessary.

1101

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the audit dump process name that is the subject of the event.
`cur‑status`	is the current status of the audit dump process.
`prev-status`	is the previous status of the audit dump process.
`cur‑state`	is the current state of the audit dump process.
`prev-state`	is the previous state of the audit dump process.
`cur‑file`	is the name of the file currently being dumped if the current status of the audit dump process is Active.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process reached the deferred state, and its previous state was enabled.

Effect The audit dump process is now unavailable for dumping audit trail files.

Recovery Follow your normal procedures to continue or to correct the problem.

1102

timestamp pid OMF: TMF Audit Dump cur‑state for audittrailid Audit Trail File. Previous State = prev-state, [Current Audit File = $audit-filename, Audit Dump Process = $audit‑processname, ] Current Status = cur-status, [Previous Status = prev‑status, ]Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`cur‑state`	is the current state of the audit dump process.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`prev-state`	is the previous state of the audit dump process.
`audit-filename`	is the name of the file currently being dumped if the current status of the audit dump process is Active.
`audit‑processname`	is the name of the audit dump process if a file is currently being dumped.
`cur‑status`	is the current status of the audit dump process.
`prev-status`	is the previous status of the audit dump process.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process reached the enabled state, and its previous state was disabled or not configured.

Effect The audit dump process is now available for dumping audit trail files.

Recovery This is an informational message only; no corrective action is necessary.

1103

timestamp pid OMF: TMF Audit Dump cur‑state for audittrailid Audit Trail File. Previous State = prev-state, [Current Audit File = $audit-filename, Audit Dump Process = $audit‑processname, ]Current Status = cur-status, [Previous Status = prev-status, ]Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`cur‑state`	is the current state of the audit dump process.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`prev-state`	is the previous state of the audit dump process.
`audit-filename`	is the name of the file currently being dumped if the current status of the audit dump process is Active.
`audit‑processname`	is the name of the audit dump process if a file is currently being dumped.
`cur‑status`	is the current status of the audit dump process.
`prev-status`	is the previous status of the audit dump process.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process reached the disabled state, and its previous state was enabled or not configured.

Effect The audit dump process is now unavailable for dumping audit trail files.

Recovery It is not recommended that the audit dump process be left in the disabled state for too long. Follow your normal procedures to continue or to correct the problem.

1104

timestamp pid OMF: TMF Audit Dump cur‑state for audittrailid Audit Trail File. Previous State = prev-state, Previous Status = prev-status, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`cur‑state`	is the current state of the audit dump process.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`prev-state`	is the previous state of the audit dump process.
`prev-status`	is the previous status of the audit dump process.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process reached the “not configured” state.

Effect The audit trail type does not have the audit dump attribute set to ON in the TMF subsystem. None of the audit trail files related to the audit trail type will be dumped. This audit trail can get full.

Recovery Change the audit dump attribute to ON, or follow your normal procedures to continue or to correct the problem.

1105

timestamp pid OMF: Action complete event for TMF Audit Dump Process, Current State = cur-state Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`cur‑state`	is the current state of the audit dump process.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process on a D20 system left a state that generated an action attention event.

Effect The TMF audit dump process is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1106

timestamp pid OMF: Action complete event for TMF Audit Dump for Audit Trail File. Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`sampling-int`	is the sampling interval of the audit dump process object type.

Cause A TMF audit dump process on a D30 or later system left a state that generated an action attention event.

Effect The TMF audit dump process is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1200

timestamp pid OMF: TMF Current Audit Trail file $file-name, Current Sequence = cur-seq, Oldest Sequence = old-seq, Configured Maxfiles = max-files, Available Audit Trail File = files-avail, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the current audit trail file that is the subject of the event.
`cur-seq`	is the sequence number of the current audit trail file.
`old-seq`	is the sequence number of the oldest audit trail file, which has not been dumped yet.
`max-files`	is the configured maxfiles parameter within TMF.
`files-avail`	is the number of available audit trail files.
`sampling-int`	is the sampling interval of the audit trail process object type.

Cause The difference between the TMF maxfiles parameter and the current number of available audit trail files is at least 3 after being less than 3.

Effect The number of TMF audit trail files available on the audit trail subvolume is at least 3.

Recovery This is an informational message only; no corrective action is necessary.

1201

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the current audit trail file that is the subject of the event.
`cur-seq`	is the sequence number of the current audit trail file.
`old-seq`	is the sequence number of the oldest audit trail file, which has not been dumped yet.
`max-files`	is the configured maxfiles parameter within TMF.
`files-avail`	is the number of available audit trail files.
`sampling-int`	is the sampling interval of the audit trail process object type.

Cause The difference between the TMF maxfiles parameter and the current number of available audit trail files is 2, after being less or more than 2.

Effect The number of TMF audit trail files available on the audit trail subvolume is 2. The TMF audit trail is in the odd state.

Recovery Follow your normal procedures to continue or to correct the problem.

1202

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the current audit trail file that is the subject of the event.
`cur-seq`	is the sequence number of the current audit trail file.
`old-seq`	is the sequence number of the oldest audit trail file, which has not been dumped yet.
`max-files`	is the configured maxfiles parameter within TMF.
`files-avail`	is the number of available audit trail files.
`sampling-int`	is the sampling interval of the audit trail process object type.

Cause The difference between the TMF maxfiles parameter and the current number of available audit trail files is 1 or 0 after being 2 or more.

Effect The number of TMF audit trail files available on the audit trail subvolume is 1 or none. The TMF audit trail is in the down state.

Recovery Follow your normal procedures to continue or to correct the problem.

1203

timestamp pid OMF: TMF Audit Trail File audittrailid, Current State = cur‑state, First Pinned File = $first-pinned-file, Reason = pinned-reason, Current Usage = current-usage, Configured Threshold = threshold, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`cur‑state`	is the current state of the audit trail.
`first-pinned-file`	is the name of the oldest audit trail file that cannot yet be reused or purged from the active or overflow audit volume by the TMF subsystem.
`pinned-reason`	is the code corresponding to the reason the first pinned file is pinned.
`current‑usage`	is the current capacity in use of the audit trail.
`threshold`	is the overflow threshold of the audit trail.
`prev‑state`	is the previous state of the audit trail.
`sampling-int`	is the sampling interval of the audit trail object type.

Cause A TMF audit trail reached the normal state.

Effect There is still space in the audit trail.

Recovery This is an informational message only; no corrective action is necessary.

1204

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`cur‑state`	is the current state of the audit trail.
`first-pinned-file`	is the name of the oldest audit trail file that cannot yet be reused or purged from the active or overflow audit volume by the TMF subsystem.
`pinned-reason`	is the code corresponding to the reason the first pinned file is pinned.
`current‑usage`	is the current capacity in use of the audit trail.
`threshold`	is the overflow threshold of the audit trail.
`prev‑state`	is the previous state of the audit trail.
`sampling-int`	is the sampling interval of the audit trail object type.

Cause A TMF audit trail reached the over threshold state.

Effect The audit trail current capacity is used over its overflow threshold, and there is no overflow space configured within the TMF subsystem. The audit trail is getting full.

Recovery According to the pinned reason, take the corresponding action or follow your normal procedures to continue or to correct the problem.

1205

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`cur‑state`	is the current state of the audit trail.
`first-pinned-file`	is the name of the oldest audit trail file that cannot yet be reused or purged from the active or overflow audit volume by the TMF subsystem.
`pinned-reason`	is the code corresponding to the reason the first pinned file is pinned.
`current‑usage`	is the current capacity in use of the audit trail.
`threshold`	is the overflow threshold of the audit trail.
`prev‑state`	is the previous state of the audit trail.
`sampling-int`	is the sampling interval of the audit trail object type.

Cause A TMF audit trail reached the overflow in used state.

Effect The audit trail current capacity is used over its overflow threshold, and there is an overflow space configured within the TMF subsystem. The audit trail is getting full.

Recovery According to the pinned reason, take the corresponding action or follow your normal procedures to continue or to correct the problem.

1206

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`cur‑state`	is the current state of the audit trail.
`first-pinned-file`	is the name of the oldest audit trail file that cannot yet be reused or purged from the active or overflow audit volume by the TMF subsystem.
`pinned-reason`	is the code corresponding to the reason the first pinned file is pinned.
`current‑usage`	is the current capacity in use of the audit trail.
`threshold`	is the overflow threshold of the audit trail.
`prev‑state`	is the previous state of the audit trail.
`sampling-int`	is the sampling interval of the audit trail object type.

Cause A TMF audit trail reached the full state.

Effect The audit trail is being used at 100 percent of its capacity. The TMF subsystem is not able to continue its work.

Recovery According to the pinned reason, take the corresponding action or follow your normal procedures to continue or to correct the problem.

1207

timestamp pid OMF: Action completion event for TMF Current Audit Trail file $file-name, Current Sequence = cur-seq, Oldest Sequence = old-seq, Configured Maxfiles = max-files, Available Audit Trail File = files-avail, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the current audit trail file that is the subject of the event.
`cur-seq`	is the sequence number of the current audit trail file.
`old-seq`	is the sequence number of the oldest audit trail file, which has not been dumped yet.
`max-files`	is the configured maxfiles parameter within TMF.
`files-avail`	is the number of available audit trail files.
`sampling-int`	is the sampling interval of the audit trail process object type.

Cause A TMF audit trail on a D20 system left a state that generated an action attention event.

Effect The audit trail is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1208

timestamp pid OMF: Action completion event for TMF Audit Trail File audittrailid, Current State = cur-state, First Pinned File = $first-pinned-file, Reason = pinned-reason, Current Usage = current-usage, Configured Threshold = threshold, Previous State = prev-state, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`audittrailid`	is the number corresponding to the TMF Audit trail type.
`cur‑state`	is the current state of the audit trail.
`first-pinned-file`	is the name of the oldest audit trail file that cannot yet be reused or purged from the active or overflow audit volume by the TMF subsystem.
`pinned-reason`	is the code corresponding to the reason the first pinned file is pinned.
`current‑usage`	is the current capacity in use of the audit trail.
`threshold`	is the overflow threshold of the audit trail.
`prev‑state`	is the previous state of the audit trail.
`sampling-int`	is the sampling interval of the audit trail object type.

Cause A TMF audit trail on a D30 or later system left a state that generated an action attention event.

Effect The audit trail is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1300

timestamp pid OMF: TMF Transaction trans-id has been proceeded, Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`trans-id`	is the TMF transaction identification number that is the subject of the event.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause A TMF transaction has been proceeded, if it was not the first time this TMF transaction was encountered.

Effect The transaction was in the odd or down state before being proceeded.

Recovery Follow your normal procedures to continue or to correct the problem

1301

timestamp pid OMF: TMF Transaction trans-id has been pending for time-elapsed minutes, [Process = {$process-name | cpu,pin}, ] Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`trans-id`	is the TMF transaction identification number that is the subject of the event.
`time-elapsed`	is the time, in minutes, that the TMF transaction has been pending.
`process-name`	is the name of the TMF process used to get the transaction information.
`cpu`	is the CPU number of the transaction’s process if available; otherwise this token is absent in the event.
`pin`	is the PIN number of the transaction’s process, if available; otherwise this field is absent.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause A TMF transaction has been encountered for the second time.

Effect This TMF transaction is considered to be in the odd state.

Recovery Follow your normal procedures to continue or to correct the problem

1302

timestamp pid OMF: TMF Transaction trans-id has been pending for time-elapsed minutes, [Process = {$process-name | cpu,pin}, ] Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`trans-id`	is the TMF transaction identification number that is the subject of the event.
`time-elapsed`	is the time, in minutes, that the TMF transaction has been pending.
`process-name`	is the name of the TMF process used to get the transaction information.
`cpu`	is the CPU number of the transaction’s process if available; otherwise this token is absent in the event.
`pin`	is the PIN number of the transaction’s process, if available; otherwise this field is absent.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause A TMF transaction has been encountered for the third time.

Effect This TMF transaction is considered to be in the down state.

Recovery Follow your normal procedures to continue or to correct the problem.

1303

timestamp pid OMF: TMF Transaction trans-id has been pending for hh:mm:ss hour(s), [Process = {$process-name | cpu,pin}, ] Current State = transac-state, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`trans-id`	is the TMF transaction identification number that is the subject of the event.
`hh:mm:ss`	is the time, in hours, minutes, and seconds, that the TMF transaction has been pending.
`process-name`	is the name of the TMF process used to get the transaction information.
`cpu`	is the CPU number of the transaction’s process if available; otherwise this token is absent in the event.
`pin`	is the PIN number of the transaction’s process, if available; otherwise this field is absent.
`transac-state`	is the value corresponding to the current TMF transaction state.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause The elapsed time (duration) of a TMF transaction is higher than the value of the TMF transaction object type sampling interval.

Effect This TMF transaction is considered to be in the odd state.

Recovery Follow your normal procedures to continue or to correct the problem.

1304

timestamp pid OMF: TMF Transaction trans-id has been pending for hh:mm:ss hour(s), [Process = {$process-name | cpu,pin}, ] Current State = transac-state, Sampling Interval = sampling‑int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`trans-id`	is the TMF transaction identification number that is the subject of the event.
`hh:mm:ss`	is the time, in hours, minutes, and seconds, that the TMF transaction has been pending.
`process-name`	is the name of the TMF process used to get the transaction information.
`cpu`	is the CPU number of the transaction’s process if available; otherwise this token is absent in the event.
`pin`	is the PIN number of the transaction’s process, if available; otherwise this field is absent.
`transac-state`	is the value corresponding to the current TMF transaction state.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause The elapsed time (duration) of a TMF transaction is higher than twice the value of the TMF transaction object type sampling interval.

Effect This TMF transaction is considered to be in the down state.

Recovery Follow your normal procedures to continue or to correct the problem.

1305

timestamp pid OMF: Action completion event for TMF Transaction. Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause A TMF transaction on a D20 system left a state that generated an action attention event.

Effect The TMF transaction is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

1306

timestamp pid OMF: Action completion event for TMF Transaction. Sampling Interval = sampling-int minutes.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`sampling-int`	is the sampling interval of the TMF transaction object type.

Cause A TMF transaction on a D30 or later system left a state that generated an action attention event.

Effect The TMF transaction is no longer in a state requiring operator action.

Recovery This is an informational message only; no corrective action is necessary.

5000

timestamp pid OMF: Subsystem Abended. An internal error occurred.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause The Otherwise option of a Case statement has been chosen, meaning that it was an unexpected condition. This is a critical message.

Effect OMF abends.

Recovery For a single-node OMF application, restart the ZOMF-MONITOR server in your Pathway environment or follow your normal procedures to continue or to correct the problem. For a network OMF environment, the NSSOmf process automatically restarts the OMF Monitor process on the same network node. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5001

timestamp pid OMF: Subsystem Abended. A SERVER^ABEND error occurred.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause OMF has encountered an abnormal condition and is trying to generate an event, but some information is missing that makes OMF unable to generate that event. OMF generates this critical message instead.

Effect OMF abends.

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5002

timestamp pid OMF: Subsystem Abended. An internal error occurred. Internal Error: error-code, Procedure Name: procedure-name.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`error-code`	is the code corresponding to the error encountered in OMF.
`procedure-name`	is the procedure name in which the problem was encountered with OMF.

Cause An unexpected condition occurred with memory management. This is a critical message.

Effect OMF abends.

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5003

timestamp pid OMF: Subsystem Abended. Memory initialization failed.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause A problem occurred with the allocation of a memory segment for the creation of all internal lists used for the management of objects within OMF. This is a critical message.

Effect OMF abends.

Recovery See the Guardian Procedure Calls Reference Manual under the system procedure call ALLOCATESEGMENT. The token ZOMF-TKN-ERROR-CODE corresponds to the error returned by ALLOCATESEGMENT. Correct the problem and then, for a single-node OMF application, restart the ZOMF-MONITOR server in your Pathway environment or follow your normal procedures to continue or to correct the problem. For a network OMF environment, the NSSOmf process automatically restarts the OMF Monitor process on the same network node. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5004

timestamp pid OMF: Subsystem Abended. Memory initialization failed.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause A problem occurred when trying to use the allocated memory segment for the creation of all the internal lists for the management of objects within OMF. This is a critical message.

Effect OMF abends.

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5005

timestamp pid OMF: Subsystem Abended. Memory initialization failed.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause A problem occurred when adding a new object type definition to the internal lists. This is a critical message.

Effect OMF abends.

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5006

timestamp pid OMF: Subsystem Abended. An I/O error occurred. File: $file-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.

Cause An error occurred during an I/O operation on a file. The File field indicates on which file the error occurred. The Error field indicates which NonStop Kernel file-system error occurred. This is a critical message.

Effect OMF abends.

Recovery Take corrective actions according to the fields File and Error. For more information on file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. For a single-node OMF application, restart the ZOMF-MONITOR server in your Pathway environment or follow your normal procedures to continue or to correct the problem. For a network OMF environment, the NSSOmf process automatically restarts the OMF Monitor process on the same network node. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5007

timestamp pid OMF: TMF Subsystem Abended. An I/O error occurred. Process: $process-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the name of the TMF process on which the I/O error occurred.
`file-syst-error`	is the file system error.

Cause OMF starts its own TMF process to get all the TMF information it needs for monitoring. An I/O error occurred on that TMF process. The Process field indicates the process name of the TMF process, and the Error field indicates which NonStop Kernel file-system error occurred. This is a critical message.

Effect OMF cannot monitor TMF objects.

Recovery Wait for the next sampling of TMF objects or force the sampling by pressing the F2 function key in any of the TMF Detailed screens, or follow your normal procedures to continue or to correct the problem.

5008

timestamp pid OMF: TMF Subsystem Error. Create Process error occurred.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause OMF starts its own TMF process to collect all TMF information it needs for monitoring. OMF is unable to obtain a process name for the TMF process. This is a critical message.

Effect OMF cannot monitor TMF objects because OMF was not able to start its own TMF process.

5009

timestamp pid OMF: TMF Subsystem Error. New Process error occurred. Process: $process-name, [Program File Name: $file-name,] Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the name of the TMF process on which the I/O error occurred.
`file-name`	is the program file name of TMFSERVE if found on $SYSTEM.SYSTEM or $SYSTEM.SYS`nn`, and is the subject of the event.
`file-syst-error`	is the file system error.

Cause OMF starts its own TMF process to collect all TMF information it needs for monitoring. OMF is unable to create the TMF process. The field Error indicates the NonStop Kernel file-system error that occurred. This is a critical message.

Effect OMF cannot monitor TMF objects because OMF was not able to start its own TMF process.

Recovery Take corrective actions according to the field Error. For more information on file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Wait for the next sampling of TMF objects or force the sampling by pressing the F2 function key in any of the TMF Detailed screens, or follow your normal procedures to continue or to correct the problem.

5010

timestamp pid OMF: Tape Subsystem Error. Lookup Process Name error occurred. Process: $process-name

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the name of the ZSERVER ($ZSVR) process on which the error occurred.

Cause OMF communicates with ZSERVER to obtain tape mount request information. OMF is unable to find the ZSERVER process because ZSERVER is not running on the system or ZSERVER is running on the system using a process name other than $ZSVR. The Process field indicates the ZSERVER ($ZSVR) process name. This is a critical message.

Effect OMF cannot monitor the tape mount object type.

Recovery Start the ZSERVER process according to your normal procedure with $ZSVR as the process name. Then, wait for the next sampling of the tape mount object type or force the sampling by going into the Tape Mounts Detailed screen and pressing the F2 function key.

5011

timestamp pid OMF: Tape Subsystem Error. An I/O error occurred. Process: $process-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`process-name`	is the name of the ZSERVER ($ZSVR) process on which the error occurred.
`file-syst-error`	is the file system error.

Cause OMF communicates with ZSERVER to obtain tape mount request information. An I/O error occurred on the ZSERVER process. The Process field indicates the ZSERVER ($ZSVR) process name, and the Error field indicates the NonStop Kernel file-system error that occurred. This is a critical message.

Effect OMF cannot monitor the tape mount object type.

Recovery Take corrective actions according to the fields Process and Error. For more information on file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Then, wait for the next sampling of the tape mount object type or force the sampling by going into the Tape Mounts Detailed screen and pressing the F2 function key.

5012

timestamp pid OMF: Subsystem has been started.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause OMF has started normally.

Effect The OMF subsystem is available.

Recovery This is an informational message only; no corrective action is necessary.

5013

timestamp pid OMF: Subsystem has been stopped.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause OMF has stopped normally,

Effect The OMF subsystem has stopped processing.

Recovery This is an informational message only; no corrective action is necessary.

5014

timestamp pid OMF: DEVICE Configuration File Error. An I/O error occurred. File: $file-name, Error: file-syst-error [, Line: line-number [ .line-number-2 ] ].

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.
`line-number`	is the edit-file line number where the I/O operation failed, if available.
`line-number-2`	is the decimal part of the edit-file line number where the I/O operation failed (if available and the value of the decimal part is not 0).

Cause OMF reads the PUP LISTDEV file to obtain the ideal LISTDEV configuration. An I/O error occurred while using that file. This is a critical message.

Effect OMF does not monitor the LISTDEV object type.

Recovery Take recovery actions according to the fields File, Error, and Line. For more information on file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Then, wait for the next sampling of the LISTDEV object type, or force the sampling by going into the LISTDEV Detailed screen and pressing the F2 function key.

5015

timestamp pid OMF: DEVICE Configuration File Error. A conversion error occurred. Expecting: expect-text. File: $file‑name, Line: line-number [ .line-number-2 ] .

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`expect-text`	is the text OMF was expecting to find in the file.
`file-name`	is the file name on which the conversion error occurred.
`line-number`	is the edit-file line number where the conversion failed.
`line-number-2`	is the decimal part of the edit-file line number where the conversion failed (if available and the value of the decimal part is not 0).

Cause OMF reads the PUP LISTDEV file to obtain the ideal LISTDEV configuration. A conversion error occurred while reading that file. This is a critical message.

Effect OMF does not monitor the LISTDEV object type.

Recovery Take recovery actions according to the fields File, Expecting, and Line. Then, wait for the next sampling of the LISTDEV object type, or force the sampling by going into the LISTDEV Detailed screen and pressing the F2 function key.

5016

timestamp pid OMF: DEVICE Configuration File Reloaded. File: $file-name.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the file name that was reload.

Cause OMF reloaded the PUP LISTDEV file after a previously occurring error was corrected.

Effect OMF monitors the LISTDEV object type at the next sampling of the LISTDEV object type.

Recovery This is an informational message only; no corrective action is necessary.

5017

timestamp pid OMF: Manager Subsystem Abended. An I/O error occurred. File: $file-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.

Effect The OMF Manager Subsystem abends.

5018

timestamp pid OMF: Manager Subsystem Stopped. Missing Assign: OMF-MONITOR-NAME.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause When using single-node OMF, the OMF Manager Subsystem expects an assign, OMF-MONITOR-NAME, and it was not found.

Effect The OMF Manager Subsystem stops.

Recovery Add the assign OMF-MONITOR-NAME to the ZOMF-SUBSYS-MGR server configuration in your Pathway environment and restart the server ZOMF-SUBSYS-MGR, or follow your normal procedures to continue or to correct the problem. The assign OMF-MONITOR-NAME is described in the Tandem Object Monitoring Facility (OMF) Manual.

5019

timestamp pid OMF: Manager Subsystem Stopped. Incorrect Assign: OMF-MONITOR-NAME. Assign Value: assign-value.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`assign-value`	is the value of the assign OMF-MONITOR-NAME.

Cause When using single-node OMF, the OMF Manager Subsystem expects an assign to specify the OMF Monitor name. The assign OMF-MONITOR-NAME was set to an invalid value.

Effect This abnormal condition causes the OMF Manager Subsystem to stop because it is not able to communicate with the OMF server.

Recovery Correct the assign value of OMF-MONITOR-NAME in your Pathway environment and restart the server ZOMF-SUBSYS-MGR, or follow your normal procedures to continue or to correct the problem. The assign OMF-MONITOR-NAME is described in the Tandem Object Monitoring Facility (OMF) Manual.

5020

timestamp pid OMF: Manager Subsystem Stopped. An I/O error occurred. File: $file-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.

Effect The OMF Manager Subsystem stops.

5021

timestamp pid OMF: NSS Configuration File Error. An I/O error occurred. File $file-name, Error: file-syst-error [, Line: line-number[.line-number-2]].

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.
`line-number`	is the edit-file line number where the I/O operation failed, if available.
`line-number-2`	is the decimal part of the edit-file line number where the I/O operation failed (if available and the value of the decimal part is not 0).

Cause The OMF Manager Subsystem reads the NSS Configuration File to obtain the NSS ID and the OMF ID. An I/O error occurred while using that file. This is a critical message.

Effect This abnormal condition prevents the OMF Manager Subsystem from getting network information from NSS Gateway, or prevents communication with any OMF server.

Recovery Take corrective actions according to the fields File, Error, and Line, or use another NSS Configuration file by changing the corresponding field in the network Profile screen. You can also modify the assign corresponding to the NSS Configuration File in your Pathway environment and restart the server ZOMF-SUBSYS-MGR, or follow your normal procedures to continue or to correct the problem. The assign NSS-CONFIG-FILE is described in the Tandem Object Monitoring Facility (OMF) Manual.

5022

timestamp pid OMF: DEVICE Configuration File Created. File: $file-name.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the created file.

Cause OMF created the PUP LISTDEV file at startup time because the file did not exist.

Effect The PUP LISTDEV file is available.

Recovery This is an informational message only; no corrective action is necessary.

5023

timestamp pid OMF: Configuration File Created. File: $file‑name.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the name of the created file.

Cause OMF created the Configuration File (OMFDB) at startup time because the file did not exist.

Effect The Configuration File (OMFDB) is available.

Recovery This is an informational message only; no corrective action is necessary.

5024

timestamp pid OMF: Configuration File Warning. object-type [ object-name][, under Supervisor $superv-name,] was not added because it already exists.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`object-type`	is the code corresponding to the object type that OMF had a problem with.
`object-name`	is the CPU number, if the object type is CPU. Otherwise, it is the object file name if the object type is disk, file, process, print process, spooler collector, spooler device, or spooler supervisor.
`superv-name`	is the spooler supervisor name, if the object type is print process, spooler collector, or spooler device.

Cause OMF tried to add a duplicate record of an existing object while creating the OMF Configuration File (OMFDB).

Effect The object was not added to the OMF Configuration File (OMFDB) because another object with the same name already exists in the Configuration File.

Recovery This is an informational message only; no corrective action is necessary.

5025

timestamp pid OMF: Subsystem Stopped. Invalid OS version: OMF version OMF-version <> OS TOS-version.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`OMF-version`	is the version of OMF.
`TOS-version`	is the NonStop Kernel Version.

Cause The version of the NonStop Kernel is not the same as the OMF version. The OMF version field indicates the NonStop Kernel version that OMF expected. The TOS version field gives the current NonStop Kernel version. This is a critical message.

Effect OMF stops.

Recovery Use the correct version of the OMF Monitor program (OMFMON).

5026

timestamp pid OMF: Subsystem Abended. Memory deallocation failed.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.

Cause A problem occurred while deallocating a memory segment.

Effect OMF abends.

EMS log file
OMFMON saveabend file
OMFDB file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

5027

timestamp pid OMF: Subsystem Stopped. An I/O error occurred. File: $file-name, Error: file-syst-error.

`timestamp`	is the time the event was generated.
`pid`	is the ID of the OMF process that generated the event.
`file-name`	is the file name on which the I/O error occurred.
`file-syst-error`	is the file system error.

Cause An error occurred during an I/O operation on a file. The File field indicates the file on which the error occurred. The Error field indicates which NonStop Kernel file-system error occurred. This is a critical message.

Effect OMF stops.

Recovery Take corrective actions according to the fields File and Error. For more information on file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Then, for a single-node OMF application, restart the ZOMF-MONITOR server in your Pathway environment or follow your normal procedures to continue, or to correct the problem. For a network OMF environment, the NSSOmf process automatically restarts the OMF Monitor process on the same network node.