The first byte represents the resource-status categories:
Value |
Current state |
Desired state |
---|---|---|
00 | Inactive | Inactive |
01 | Pending inactive | Not used |
02 | Connectable | Connectable |
03 | Reactivate | Reactivate |
04 | Pending active | Not used |
05 | Active | Active |
06 | Routable | Routable |
The second byte of RPRCURST and RPRDESST gives the specific resource status. The following table shows the two bytes in combination (for example, value hexadecimal 0001 indicates a category of zero-zero and a specific code of zero-one).
Resource state | Value (hex) | Category | Resource status |
---|---|---|---|
ACTIV | 0505 | Final | The resource is in the active state. |
APEER | 0501 | Final | Attach PU Type 4 or 5 (peer): The node is the backup link station to which a PU Type 4 or 5 in another domain is attached. |
CONCT | 0200 | Final | Connectable: A VARY ACT command
has completed for a switched physical or logical unit, or for an application
program.
|
CTDER | 041D | Susp | Contacted error: A node, such as a link station or physical unit, was being activated and the contacted request was received indicating the contacted error state. For a physical unit, a request to deactivate the resource has been scheduled. For a link station, if the NCP it is trying to contact is being activated, the link station activation will be suspended until the activation is completed; then the link station will be contacted again. A second CTDER causes deactivation of the link station. |
CTD1 | 043D | Susp | Contacted(1): A link station was being activated, and received a contacted request from the appropriate PU services. Because the communication controller contacted is being activated, the activation of the link station is suspended until the communication controller has been activated. Activation processing for the link station is redriven after the communication controller has been activated. |
CTRQI | 043A | Susp | Contacted(2) request IPL: A node, such as a link station or a physical unit, is being activated, and the contacted request indicates that reload is required. For a physical unit, a request to deactivate the resource has been scheduled. For a link station, if the NCP it is trying to contact is being activated, the link station activation will be suspended until the communication controller has been activated. The link station will then be contacted again. A second CTRQI deactivates the link station. |
CT1NS | 040F | Susp | Contact(1) not sent: A link station reached the point in its activation where a contact request should be sent, but the NCP to be contacted is not in a suitable state. The link station activation is suspended and will be redriven when the NCP activation reaches the point where it can be contacted (when its state is PAPU2). |
DALUC | 011E | Susp | DACTLU complete: A DACTLU request was sent and the response was received, but some higher-level node recovery processing has started. This node will remain in this state until the higher-level process redrives it. |
DAPUC | 011F | Int | DACTPU complete: A DACTPU request was sent as the result of a force deactivate or force reactivate command, and either the response was received or, in the case of a communication controller, a route failed and a DACTPU request was received. |
DEFND | 0001 | Short | Defined: A VARY ACT command is being processed for a major node. The major node and its subnodes are known to VTAM®. The activation has been suspended while the processing of the command moves from one internal VTAM PAB to another. |
DLLDD | 05 | Final | Loaded: The physical unit requested a load and that load has been successfully completed. |
DLPAB | 04 | Short | Pending load abort: The physical unit requested load cannot be completed; a request to cancel the load has been sent to the physical unit. |
DLPLD | 03 | Long | Pending load: The physical unit is currently being loaded. |
DLPRP | 02 | Short | Pending ACTPU response: An ACTPU request unit was sent to the physical unit, and VTAM is waiting for the ACTPU response by which the physical unit will indicate whether it needs to be loaded. |
DLRST | 01 | Final | Reset: The physical unit is not being loaded. |
DUMPC | 011B | Susp | Dump complete: A link station was used to dump an NCP and the dump is complete, but the recovery or deactivation of the NCP has not reached the point where link stations connected to that NCP are processed. For recovery, that point is reached when the NCP load or dump procedure status is RESET. For a deactivation, that point is reached when the NCP status is PRSET. |
FDSCC | 0445 | Int | Force Discontact completed: A discontact has been sent as a result of a force deactivate or force reactivate command, and the response to the discontact has been received. |
HLACF | 0409 | Int | Higher-level activate failed: A node was being activated, and activation of its higher-level node failed. For example, a channel-attached physical unit or logical unit was being activated, and PUB allocation failed for its associated channel. A deactivate request was scheduled for the channel-attached physical unit or logical unit. |
HLACT | 042D | Int | Higher-level activate complete: A node is being activated and its higher-level node has completed activation. For example, a channel-attached physical unit or logical unit is being activated, and the activation of the associated channel has been completed. The activation of the resource is about to begin. |
IINOP | 0005 | Final | Inactive (Inoperative): The resource has been deactivated by an INOP request or a forced deactivate request. |
INACS | 0006 | Final | Inactive with sessions: If the resource
is a logical unit, the node is in the inactive state but might have
active sessions. There is no LU-SSCP session, but the logical unit
might have active LU-LU sessions. This state can occur when a cross-domain
resource is made a same-domain resource as part of the takeover of
the resources of an SSCP that failed. If the resource is a CDRM, the node is in an inactive state, but it supports active cross-domain LU-LU sessions. In this state, there is no SSCP-SSCP session, but the CDRM might be supporting active cross-domain LU-LU sessions. This state can occur when (1) the virtual route used by the SSCP-SSCP session is inoperative or has been deactivated by a DACTVR (FORCE), (2) activate CDRM contention has occurred, or (3) an unrecoverable error has been detected for the SSCP-SSCP session. The cross-domain active session, which used the SSCP-SSCP session to set up, remains intact. |
INACT | 0003 | Final | Inactive: The resource has been deactivated. |
INACX | 0007 | Final | Inactive with address transforms: An external CDRM could not be activated. A gateway NCP along the path to the CDRM did not have enough information to support a cross-network session with the CDRM. |
INOP | 0441 | Susp | Inoperative: An INOP request, route failure, or force reactivate command is being processed. Active user sessions have been terminated. The resource is about to be reactivated, but must wait for a higher-level node to activate it. |
INVAP | 0417 | Int | Activate PU response not valid: A node, such as a communication controller or physical unit, is being activated. The ACTPU request was sent, but the response is not valid. Two examples of responses that are not valid are (1) the response unit has a format that is not valid or indicates the physical unit is not in COLD or ERP state and (2) the resource has been loaded and the contents ID is not the expected value. A request to deactivate the resource was scheduled. |
LLQED | 043B | Susp | Lower-level queued: A VARY ACT command is being processed for a communication controller, and the RDT segment has just been built. The network names of both the major node and its subnodes are known to VTAM. At least one of the subnode link stations has been queued on another link station queue, because it is an operand of the RNAME=keyword on the second communication controller VARY ACT command. The activation of the communication controller has been suspended while the processing of the command moves from one internal VTAM PAB to another. |
NACDR | 042F | Int | Negative Activate CDRM response: A CDRM is being activated and the activate CDRM request was sent, but the response was negative (the request failed). A request to deactivate the CDRM has been scheduled. |
NACTL | 0410 | Int | Negative activate LU response: A node, such as an application program or other logical unit was being activated, and the activate LU request was sent, but the response was negative (the request failed). A request to deactivate the resource was scheduled. |
NACTP | 0412 | Int | Negative activate PU response: A node, such as a communication controller or physical unit, was being activated and the activate PU request was sent, but the response was negative, and the request failed. A request to deactivate the resource was scheduled. |
NADLK | 0423 | Int | Negative add link response: A channel link was being activated and an add link request was sent to the appropriate PU services. However, the response was negative and the request failed. A request to deactivate the resource was scheduled. |
NADST | 0420 | Int | Negative add link station response: A channel link station was being activated and an add link station request was sent to the appropriate PU services. However, the response was negative and the request failed. A request to deactivate the resource was scheduled. |
NALNK | 0415 | Int | Negative activate link response: A line was being activated, and the activate link request was sent, but the response was negative (the request failed). A request to deactivate the line has been scheduled. |
NANNA | 0431 | Int | Negative allocate node network address: A node, such as a dynamically added physical unit or logical unit, was being activated, and the request network address assignment request was sent to the appropriate PU services, but the response was negative and the request failed. A request to deactivate the resource was scheduled. |
NASNA | 0426 | Int | Negative allocate subnode network addresses: A node, such as a channel-attached or switched physical unit, is being connected and the request network address assignment request has been sent to the appropriate PU services. However, the response was negative and the request failed. A request to disconnect the resource was scheduled. |
NCONO | 0400 | Int | Negative connect out response: A node, such as a channel-attached or switched physical unit, was being connected and the connect out request was sent to the appropriate physical unit services, but the response was negative and the request failed. A request to disconnect the resource was scheduled. |
NCONT | 041C | Int | Negative contact response: A node, such as a link station or physical unit, was being activated and the contact request was sent, but the response was negative (the request failed). A request to deactivate the resource has been scheduled. |
NEVAC | 0004 | Final | Never activated: The resource has never been activated. |
NFRSV | 0407 | Int | Negative FRS control vector: All the frame relay physical units in a particular frame relay switching equipment set (FRSESET) were being activated, and the FRS control vector request was sent to the appropriate PU services. However, the response was negative, and the request failed. Requests to deactivate all the frame relay physical units in the FRSESET have been scheduled. |
NLOAD | 043C | Int | Negative load response: A communication controller was being activated and a load request was sent to the appropriate physical unit services, but the response was negative and the request failed. A request to deactivate the communication controller was scheduled. |
NNAUV | 0403 | Int | Negative set NAU control vector: A node, such as a switched or dynamically added logical unit, was being connected and the set NAU control vector request was sent to the appropriate physical unit services, but the response was negative and the request failed. A request to disconnect the resource was scheduled. |
NSARV | 041A | Int | Negative set SAR control vector: A node, such as a link station, was being activated and the set SAR control vector request was sent to the appropriate PU services, but the response was negative and the request failed. A request to deactivate the resource was scheduled. |
NSDT | 0428 | Int | Negative SDT response: A communication controller was being activated and the start data traffic request was sent, but the response was negative and the request failed. A request to deactivate the communication controller was scheduled. |
NSNCP | 042E | Int | Negative switch to NCP response: A PEP link was being activated, and the switch to NCP request was sent, but the response was negative and the request failed. A request to deactivate the PEP link was scheduled. |
NSSSV | 0405 | Int | Negative set SSS control vector: A node, such as a DR-added physical unit added by dynamic reconfiguration, or a switched physical unit, was being connected, and the set SSS control vector request was sent to the appropriate PU services, but the response was negative, and the request failed. A request to disconnect the node was scheduled. |
NSTD | 042A | Int | Negative set time and date response: A node, such as a communication controller, was being activated and the set time and date request was sent, but the response was negative and the request failed. A request to deactivate the node was scheduled. |
NVYLM | 0436 | Int | Negative operator query (VFYLM) response: The resource was being activated and the response to the VTAM message IST361A was to terminate the NCP activation. A request to deactivate the resource has been scheduled. |
PABCN | 010B | Short | Pending abandon connection response: A node, such as a channel-attached or switched physical unit, is about to become disconnected. The abandon connection request has been sent to the appropriate PU services, but the response has not been received. |
PABCO | 0116 | Short | Pending abandon connection out response: A node, such as a channel-attached or switched physical unit, is being disconnected and the abandon connect out request has been sent to the appropriate physical unit services, but the response has not been received. |
PACDR | 0430 | Long | Pending activate CDRM response: A CDRM is being activated and the activate CDRM request has been sent, but the response has not been received. |
PACTL | 0411 | Short | Pending activate LU response: A node, such as an application program or other logical unit, is being activated and the activate LU request has been sent, but the response has not been received. |
PADLK | 0421 | Short | Pending add link response: A channel link is being activated and an add link request was sent to the appropriate PU services, but the response has not been received. |
PADST | 0419 | Short | Pending add link station response: A channel-link station is being activated and an add link station request was sent to the appropriate PU services, but the response has not been received. |
PALNK | 0416 | Short | Pending activate link response: A line is being activated, and the activate link request has been sent, but the response has not been received. |
PALUC | 0434 | Short | Pending activate LU cleanup response: An active logical unit is undergoing recovery processing. An ACTLU request has been sent, but the response has not been received. |
PANNA | 0432 | Short | Pending allocate node network address: A node, such as a dynamically added physical unit or logical unit, is being activated and the request network address assignment request has been sent to the appropriate PU services, but the response was not received. |
PAPU1 | 0413 | Short or Long | Pending activate PU(1) response: A communication controller is being activated, and might not need to be loaded. The ACTPU request was sent, but the response was not received. The sending of this request might have to wait for the availability of a virtual route. If one or more explicit routes are operative, this should be a short transient state while route activation proceeds. If no routes are operative, this might be a long transient state while VTAM waits for connectivity to be established along the route. |
PAPU2 | 0425 | Short or Long | Pending activate PU(2) response: A physical unit is being activated, did not need to be loaded or has been loaded, and the activate PU request has been sent, but the response has not been received. For a communication controller, the sending of this request might have to wait for the availability of a virtual route. If one or more explicit routes are operative, this should effectively be a short transient state while route activation proceeds. If no routes are operative, this might be a long transient state while VTAM waits for connectivity to be established along the route. |
PASNA | 0427 | Short | Pending allocate subnode network addresses: A node, such as a channel-attached or switched physical unit, is being connected. The assign network address or request network address assignment request has been sent to the appropriate PU services, but the response was not received. |
PBFSI | 0448 | Short | Pending BFSESSINFO: Takeover processing is in progress for an LU, and active sessions have not been completely reported to the SSCP. |
PCDLA | 0121 | Short | Pending cleanup DACTLINK active: A VARY INACT,TYPE=FORCE command was entered for an NCP-attached line whose status is active, pending active, or pending inactive. The lower level nodes are being deactivated, and a DACTLINK (cleanup) request was sent for the line, but the response has not yet been received. |
PCDLI | 0122 | Short | Pending cleanup DACTLINK inactive: A VARY INACT,TYPE=FORCE command was entered for an NCP-attached line whose status is not active, pending active, or pending inactive. A DACTLINK (cleanup) request was sent for the line, but the response has not yet been received. |
PCONO | 0401 | Short | Pending connect out response: A node, such as a channel-attached or switched physical unit, is being connected and the connect out request has been sent to the appropriate PU services, but the response was not received. |
PCON1 | 041E | Short | Pending contact(1) response: A node, such as a link station, is being activated, and the first contact request was sent to the appropriate PU services, but the response was not received. |
PCON2 | 0422 | Short | Pending contact(2) response: A node, such as a physical unit or link station, is being activated and the contact request (second attempt for link station) has been sent to the appropriate physical unit services, but the response has not been received. |
PCTD1 | 041F | Long | Pending contacted(1) request: A node, such as a link station, is being activated, and the first contact response was received as a positive response, but the contacted request was not received. A communication controller will also be found in this state during activation while waiting for a link station connected to it to be activated. For CTC, if both sides are hung in PCTD1, enter VARY INACT,TYPE=FORCE then VARY ACT on one side only to bypass the problem. |
PCTD2 | 0424 | Long | Pending contacted(2) request: A
node, for example, a link station or a physical unit, is being activated.
The final contact request was sent by VTAM to
the appropriate PU services and the response was received from the
NCP, but the contacted request has not been received from the remote
device. A communication controller will also be found in this state
(it is a suspended state in this case) during activation while waiting
for a link station connected to it to be activated. The difference
between PCTD2 and PCTD1 is that a communication controller in the
PCTD1 state might be loaded if a link station receives a contacted
request indicating the NCP needs to be loaded, whereas in the PCTD2
state, both the link station and the NCP would be deactivated.
Note:
|
PDACL | 010F | Short | Pending DACTLU response: A node, such as an application program or a logical unit, is being disconnected or deactivated. The DACTLU request has been sent, but the response has not been received. |
PDACP | 0110 | Short | Pending DACTPU response: A node, such as a communication controller or physical unit, is being disconnected or deactivated. The DACTPU request has been sent, but the response has not been received. |
PDANC | 0442 | Short | Pending DACTPU ANSC: A DACTPU request was sent to the resource, but the response has not been received. The resource was being activated when the automatic network shutdown complete (ANSC) RU was received from the NCP. This request causes the SSCP to reset the SSCP-PU session and then resume the activation procedure. |
PDANS | 0104 | Short | The abandon connect in request unit has been sent for a node such as a switched link. |
PDELR | 010E | Short | Pending delete network resource response: A node, such as an application program, is being disconnected. The delete network resource request has been sent to the appropriate PU services, but the response has not been received. |
PDGBK | 0123 | Short | Pending DACTLINK giveback: Records were lost when the VTAM subtask VTMTRACE was restarted. A VARY INACT,TYPE=GIVEBACK command was entered for an NCP attached line. A DACTLINK (giveback) request was sent for the line, but the response has not yet been received. |
PDISC | 010D | Short | Pending discontact response: A node, such as a link station or physical unit, is being deactivated or disconnected. The discontact request has been sent to the appropriate PU services, but the response has not been received. |
PDLNK | 0112 | Short | Pending DACTLINK response: A line or channel-attached device is being deactivated, and the DACTLINK request has been sent to the appropriate PU services, but the response has not been received. |
PDLUC | 011D | Short | Pending Deactivate LU cleanup: An active logical unit is undergoing error-recovery processing and the DACTLU request has been sent, but the response has not been received. |
PDMPC | 0439 | Long | Pending dump contention: VTAM is waiting for an indication from the communication controller to resume operation. |
PDPA1 | 0443 | Short | Pending DACTPU (ACT1): A DACTPU request was sent to the resource, but the response has not been received. The communication controller was being activated and was found already loaded. When the DACTPU response is received, this state is exited and processing continues from the beginning. Another attempt to load is allowed. |
PDPA2 | 0444 | Short | Pending DACTPU (ACT2): A DACTPU has been sent to the resource, but the response has not been received. If the resource is a physical unit Type 4, it was being activated and a load was performed. Once the DACTPU response is received, the activation of the communication controller will proceed. If the resource is a BSC 3270 physical unit, a general poll failure occurred and the DACTPU was sent to clean up internal control blocks. When the response is received, an ACTPU will be sent. |
PFDCP | 0440 | Short | Pending force DACTPU response: A DACTPU has been sent as a result of a force-reactivate or force-deactivate command against a node, such as a communication controller. The response has not been received. |
PFDLU | 0120 | Short | Pending force DACTLU response: A DACTLU has been sent as a result of a force-deactivate command for the logical unit, but the response has not yet been received. |
PFDMP | 0119 | Short | Pending dump response: A dump is being performed on a communication controller over a link station, and it has not yet completed processing. |
PFDSC | 042C | Short | Pending force discontact response: A physical unit is being forced to deactivate or forced to reactivate and the discontact request has been sent to the appropriate PU services, but the response has not been received. |
PFNNA | 011C | Short | Pending free node network address: A node, such as a switched or dynamically added physical unit or logical unit, is being deactivated. The free network address request has been sent to the appropriate PU services, but the response has not been received. |
PFRSV | 042F | Susp | Pending FRS control vector response:
A frame relay physical unit is being activated and one of the following
situations has occurred:
|
PFSNA | 010C | Short | Pending free subnode network addresses: A node, such as a channel-attached or switched physical unit, is being disconnected. The free network address request has been sent to the appropriate PU services, but the response has not been received. |
PGAIN | 0449 | Long | Pending Enterprise Extender hostname resolution using the resolver API GetAddrInfo function. This state can vary in duration depending on many factors; for example, how long it takes for the resolver to resolve the hostname, or for the request to fail (either a timeout using resolver configuration definitions or by the IPRESOLV VTAM keyword), or for the TCP/IP stack being used for Enterprise Extender to become active. |
PHLAC | 040A | Susp | Pending higher-level activation: A node is awaiting activation of its higher-level node. For example, a channel-attached physical unit or logical unit is being activated, and the request to activate the associated channel (that is, the associated PUB) has not completed. |
PHLIN | 0102 | Susp | Pending higher-level deactivation: A node is inactive and its higher-level node is being deactivated. For example, a channel-attached physical unit is inactive and the associated channel PUB is being deallocated. |
PINAC | 0100 | Long | Pending inactive: CDRM is being deactivated. |
PLOAD | 040E | Long | Pending load: Either an NCP is being activated and a load operation has begun, or a peripheral physical unit, such as an 8775, is being activated, the physical unit has requested a load, and the SSCP sent the load request to an application program defined in the CNM routing tables. The physical unit has not received a response. |
PLODC | 043E | Long | Pending load contention: VTAM is waiting for an indication from the communication controller to resume operation. |
PLSTC | 043F | Long | Pending load station conditional: Activation processing for a communication controller is waiting for the link station over which the communication controller will be loaded to become available. When the link station is capable of being used for loading, if the link station is a channel link station, VTAM determines if the communication controller is loaded. If it is, a load is not done and activation proceeds. If it is not a channel link station, or if the communication controller is not loaded, a load is performed. |
PLSTU | 040D | Long | Pending load station unconditional: Activation processing for a communication controller will be loaded to become available. When the link station is capable of being used for loading, a load of the NCP will be done. |
PMALD | 0446 | Long | Pending migration ACTPU load or dump procedure: An NCP session recovery loop has been suspended because of an ongoing load or dump operation. |
PMATM | 0447 | Long | Pending migration ACTPU timer: An NCP is waiting for the expiration of a time interval before trying session activation again. |
PNAUV | 0404 | Short | Pending set NAU control vector response: A node, such as a switched or dynamically added logical unit, is being connected, and the set NAU control vector request has been sent to the appropriate PU services, but the response has not been received. |
PNFY1 | 0113 | Long | Pending notify(1): A node, such as a logical unit, is being deactivated or disconnected. The request to terminate user sessions has been scheduled, but the notify request indicating that the user sessions have ended has not yet been received. For example, the application program did not issue CLSDST. |
PNFY2 | 0108 | Long | Pending notify(2): A node, such as a logical unit, is about to become connectable and the request to terminate any queued user sessions has been scheduled. However, the notify request indicating that the user sessions have ended has not yet been received. |
PNFY3 | 0105 | Long | Pending notify(3): A node is about to become inactive and the request to terminate queued user sessions has been scheduled. However, the notify request indicating that the user sessions have ended has not yet been received. |
POAS1 | 0437 | Long | Pending operator query (AUTOSYN1) response: A communication controller is being activated, and message IST183A, which asks if the communication controller should be reloaded or resynchronized, has been entered. The message was sent after the communication controller was contacted but before an SSCP-PU session was established. The reply was not received. |
POAS2 | 0438 | Long | Pending operator query (AUTOSYN2) response: A communication controller is being activated, and message IST183A, which asks if the communication controller should be reloaded or resynchronized, has been issued. The message was sent after an SSCP-PU session was established with the communication controller. The reply was not received. |
PREQC | 0402 | Long | Pending request contact request: A node, such as a channel-attached or switched physical unit, is being connected and the connect out response has been received, but the request contact request has not been received. |
PRMPO | 0103 | Short | Pending RMPO response: A remote power off request has been sent over a link station and the response has not been received. |
PRSET | 0101 | Short | Pending reset: The resource is inactive, but the network name is still known to VTAM. |
PSARV | 041B | Short | Pending set SAR control vector response: A node, such as a link station, is being activated and the set SAR control vector request has been sent to the appropriate PU services, but the response has not been received. |
PSDT | 0429 | Short | Pending start data traffic response: A node, such as a communication controller, was being activated, and the start data traffic request was sent, but the response was not received. |
PSNCP | 0414 | Short | Pending switch to NCP response: A PEP link is being activated, and the switch to NCP request was sent, but the response has not been received. |
PSSSV | 0406 | Short | Pending set SSS control vector response: A switched physical unit is being connected, or a dynamically added physical unit is being activated, and the set SSS control cector request has been sent to the appropriate PU services, but the response has not been received. |
PSTD | 042B | Short | Pending set time and date response: A communication controller was being activated, and the set time and date request was sent, but the response was not received. |
PSUBD | 0502 | Susp | Pending subnode definition: The resource is active but is waiting for dynamic subnodes to be defined. If a switched line is in this state it cannot be used for dial out. |
PSUBR | 0504 | Susp | Pending subnode release: An acquired communication controller that was activated before it was acquired is being released; that is, a request to release the subnodes in the unowned portion of the communication controller is in progress. |
PSUB1 | 0115 | Susp | Pending subnode deactivate(1): A node supporting subnodes, for example, an application program, communication controller, link, or physical unit, is being deactivated or disconnected. Terminate requests for user sessions for application programs or LUs are being performed. |
PSUB2 | 010A | Susp | Pending subnode deactivate(2): A node supporting subnodes, for example, an application program, communication controller, link, or physical unit, is about to become connectable. Terminate requests for queued user sessions for application programs or LUs are being performed. |
PSUB3 | 0107 | Susp | Pending subnode deactivate(3): A node supporting subnodes, for example, an application program, communication controller, link, or physical unit, is about to become inactive. Terminate requests for queued user sessions that apply to application programs or LUs are being performed. |
PSWEP | 0111 | Short | Pending switch to EP mode response: A PEP link has been deactivated. The switch to EP mode request has been sent to the appropriate PU services, but the response has not been received. |
PTRM1 | 0114 | Short | Pending terminate(1) response: A node, such as a logical unit, is being deactivated or disconnected. The request to terminate user sessions has been scheduled, but the response has not yet been received. |
PTRM2 | 0109 | Short | Pending terminate(2): A node, such as a logical unit, is about to become connectable, and the request to terminate queued user sessions has been scheduled. However, the response has not yet been received. |
PTRM3 | 0106 | Short | Pending terminate(3) response: A logical unit is about to become inactive and the request to terminate queued user sessions has been scheduled, but the response has not yet been received. |
PVYLM | 0435 | Long | Pending operator query (VFYLM) response: The resource is being activated and the VTAM operator message IST361A or IST937A has been issued, but the reply has not yet been received. Message IST361A asked the operator if he wanted to load the NCP or terminate the NCP activation. Message IST937A asked the operator if he wanted to reload the NCP, deactivate the NCP, or ignore the correlator mismatch. |
P095A | 0118 | Long | Pending operator query response: An ERP has issued message IST095A asking whether an ERP dump is desired. The reply has not been received. |
P284A | 0408 | Long | Pending operator query response: A communication controller is being recovered and message IST284A, asking whether the communication controller should be reloaded, has been issued. The reply has not been received. |
RACTH | 0301 | Reactivate at higher level: The resource is being deactivated and, once inactive, will wait for its reactivation to be driven by a higher-level node. (This is a desired state only.) | |
RACTN | 0300 | Reactivate at this level: The resource is being deactivated and will then be reactivated at this level. (This is a desired state only.) | |
RADDF | 0433 | Int | RDTADD failed: A node was being activated and the request to add the associated network address to the VTAM RDTADD data base has failed. A request to deactivate the resource has been scheduled. |
RDIAL | 0201 | Redial: A switched physical unit is being disconnected and an attempt to redial the physical unit will be made once disconnection is complete. (This is a desired state only.) | |
RDRSP | 0124 | Long | Pending RTP_deallocation response. |
RELSD | 0002 | Final | Released: A physical unit has been released, or it exists in the unowned portion of an activated-before-acquired communication controller and has not yet been acquired. |
RESET | 0000 | Final | Reset: VTAM built a control block to represent the resource, but the resource has not been added to the symbol table. The resource is not usable by VTAM. You might have a duplicate resource name. For NCP resources, you might need to issue a VTAM VARY ACQ command to acquire the resource before using it. |
RINAC | 0600 | Long | Routable, inactive: A MODIFY LL2 command is being processed for an inactive, dynamically added physical unit. In order to process the command, a network address had to be obtained for the physical unit. When the LL2 test is terminated, the physical unit will be returned to the inactive state. |
RRLSD | 0601 | Long | Routable, released: A MODIFY LL2 command is being processed for a released, dynamically added physical unit. In order to process the command, a network address had to be obtained for the physical unit. When the LL2 test is terminated, the physical unit will be returned to the released state. |
TRACT | 03 | Final | Active: The trace indicated is active. |
TRPAR | 02 | Short | Pending ACT TRACE: The trace is being activated and the ACTTRACE request has been sent to the appropriate PU services, but the response has not been received. |
TRPDR | 01 | Short | Pending DACTTRACE: The trace is being deactivated and the DACTTRACE request has been sent. |
TRRES | 00 | Final | Reset: The trace indicated is not active. |
183AF | 0418 | Int | Operator query (AUTOSYNCH) failed: A request to issue message IST183A was scheduled, but the message could not be issued. Processing continues as if the reply were negative. |
284AF | 0407 | Int | Operator query failed: A request to issue message IST284A has been scheduled, but the message could not be issued. Processing continues as if the reply were negative. |
Note:
|