ADD request errors

These sense codes are returned by OMEGAMON® messages.

X’20000040’

Insufficient private (NCWA)

X’20000041’

Enqueue failure X’20000042’ This sense code is returned for one of the following reasons:

1. Device luname not found in network (no data provided for VERBOSE WTO)
2. LU is a virtual terminal, but no information is available from the MSM.
3. ETE address space is no longer running
4. LU is a switched LU or a 37xx TIC-attached token ring LU that has a status of CONCT

Issue the ETE VERBOSE command to produce a WTO to the system console each time this sense code is returned (except for reason 1 above). The WTO specifies which of the above reasons caused the failure.

X’20000043’

Device not suitable for monitoring X’20000044’ Device does not support SLU-PLU rsps

X’20000045’

User already monitoring this device

X’20000046’

Insufficient CSA–TDBA

X’20000047’

Insufficient CSA–TDBE

X’20000048’

Insufficient CSA–PSQE

X’20000049’

Dequeue failure

X’2000004A’

Control block corruption detected

X’2000004B’

Abend occurred during request

X’2000004C’

Collector abended

X’2000004D’

Unsupported environment

X’2000004E’

Recovery not established

X’2000004F’

Lock obtain timeout

X’20000050’

Partner luname not found in network

X’20000051’

VIT PIU trace is inactive

X’20000052’

TCRB information is unavailable

X’20000053’

ETE address space is inactive

X’20000054’

Device is in connectable status

X’20000055’

Cross memory set up failure

X’20000056’

Add failed for LU type 1 or 3 device. (FAILNL2 was specified on the EXEC statement in the ETE started task JCL (TKANSAM member CANSET).)

X’20000057’

No partner was specified

X’20000058’

Lock obtain timeout

X’20000059’

CID not found during CIHT add processing

X’2000005A’

GETMAIN for additional CIHT failed

X’2000005B’

GETMAIN for ADPB failed

X’2000005C’

ADPB lock obtain failure

X’2000005D’

No terminal for add request