Sense code 0890

Search failure.

Bytes 2 and 3 following the sense code contain sense-code-specific information.

0000

No specific code applies.

0010

Routing error during a directed search: A Locate GDS variable for a directed search was received by an intermediate NNCP and could not be successfully routed to the destination control point.

0011

The path used to transport the directed Locate request (a message containing Locate, Find Resource, and Cross-Domain Initiate GDS variables) does not support a sufficiently-large Locate message size to return the Locate response (a message containing Locate, Found Resource, and Cross-Domain Initiate GDS variables). The NNS(OLU) was requested to try the directed search again over a path supporting a sufficient Locate message size.

0020

Resource not found during a directed search: A Locate GDS variable for a directed search was received by the named destination CP and the search argument resource is not a local resource.

0021

Verification reduction could not be satisfied, but was required for the request. This sense code is returned when resource verification reduction cannot be satisfied for the DLU.

VTAM® hint: This sense code is set by the PLU's network node server when resource verification reduction could not be satisfied for a request initiated by the PLU control point to obtain the RSCV from the network node server.

0022

Destination of search not served by this CP.

0028

Resource not found, broadcast required: The resource was not found on a directed LOCATE/CDINIT search, and a restricted broadcast was executed at the destination and failed; a broadcast should be tried.

0030

Resource deleted, no broadcast required: A Locate GDS variable for a directed search was received by the named destination CP and the search argument resource has been deleted.

0036

Duplicate search to a subnetwork. This is an attempt to search a network previously reached by this search procedure. This condition indicates an attempt to loop back into a subnetwork through a different entry point.

0037

Unknown TG vectors to dependent LU requester. A resubmitted Located search for a dependent LU at its dependent LU requester was unsuccessful. This condition arises only after the dependent LU server has verified the existence of the dependent LU.

VTAM hint: VTAM was unable to successfully locate the dependent LU requester (DLUR) node in order to obtain the necessary DLUR endpoint transmission group (TG) vectors. The current session setup will fail. Verify that connectivity exists between the node that issued the sense code and the DLUR node.

0038

Too many directed search subprocedures: A LOCATE exceeded the maximum height of the search tree; too many directed search subprocedures were tried; no retry.

0040

Resource not found during a broadcast search: A Locate GDS variable for a broadcast search was received by a CP that does not provide network services for the search argument resource and neither do any of the CPs searched in its broadcast subtree. This condition is detected by crossing search requests (a CP sends and receives a search request with the same PCID and the same search argument resource) or by a local search failure and all CPs in the broadcast subtree returning this sense data.

0048

Neutral reply received from an end node: A locate reply with no found and no extended sense data (X'35') control vector was received from an APPN end node.

0050

Quiesced CP: A CP in the broadcast search tree is in a quiescent state and, therefore, not receiving Locate GDS variables. This condition is detected when a CP in the search subtree is quiesced and no other CP in the subtree found the requested resource.

0060

Storage not available: A CP in the broadcast search tree does not have sufficient storage to participate in the search and no other CP in the search subtree found the requested resource.

0070

Session outage: A CP in the search tree has lost its CP-CP session with a CP that had been sent a Locate GDS variable and no reply had been received.

0080

Duplicate fully qualified PCID: A CP in the search tree detected a duplicate fully qualified PCID for a different session request from the session request that first used the fully qualified PCID.

0081

PCID modifier too long: A PCID modifier list was received that had a length greater than ten bytes.

0082

PCID modifier space exhausted: A PCID modifier list was received that contained the maximum of ten bytes. As the maximum list size has been reached, another list entry cannot be made that was longer than ten bytes.

VTAM hint:

This sense code is issued when a node determines that it might have to retry, resubmit, or redirect a search, but it cannot allocate a procedure-correlation identifier (PCID) Modifier slot, because all 20 half-byte slots have already been allocated. This indicates that the search has been exhausted (20 nodes have already allocated slots without finding the DLU). There is currently no recovery action architected or implemented to recover from this situation.

The PCID Modifier slots differ from the SSCP visit count in that the SSCP visit count is decremented by every SSCP on the session setup path. The PCID Modifier slots are not allocated by every SSCP, only those that might have to perform retried, resubmitted, or redirected searches.