Explanation
VTAM® issues
this message in response to a DISPLAY ID command when a multinode
persistent application is specified and the application is not defined
to the VTAM on which the command
is issued, but is found in the multinode persistent session coupling
facility structure.
owning_VTAM is the VTAM where the multinode persistent
application last opened its ACB.
The application can be in
one of the following states:
- CLEANUP
- The data related to this application is being cleaned up in the
multinode persistent coupling facility structure.
- DISABLED
- The application OPENed its ACB and specified PERSIST=YES, but
has not yet issued SETLOGON OPTCD=PERSIST. Data for the application
is stored in the coupling facility structure in case the application
chooses to enable persistence. However, sessions are not restored
in the event of a failure.
- ENABLED
- The application issued SETLOGON OPTCD=PERSIST. Multinode persistent
sessions will be restored in the event of a failure.
- RECOVERY PENDING
- A failure of the VTAM owning
the application was detected. Wait for the application to recover.
- SNPS RECOVERY PENDING
- The application failed, or issued CLOSE, while it was enabled
for persistence. The application is now waiting for recovery on its
owning VTAM or some other VTAM. In the event of subsequent
failure of the owning VTAM,
the sessions will be maintained and thus can be restored.
- SUSPECT
- The data associated with this application might be invalid; in
the event of failure, the application's sessions will not be recovered.
This might be caused by the following:
- The multinode persistent coupling facility structure containing
the application's data is currently being rebuilt.
- The owning_VTAM lost connectivity to the multinode
persistent session structure containing the application's data.
- TAKEOVER ACKNOWLEDGED
- The application received a forced takeover request, asking the
application to move from its current owning node to a different node
in the sysplex. The application is in the process of completing its
persistent CLOSE ACB processing prior to moving to the new owning
node. The owning VTAM is the
CP where the application is undergoing persistent CLOSE processing,
and not the VTAM to which the
application is expected to eventually move.
- TAKEOVER IN PROGRESS
- The application is moving from one VTAM to
another VTAM. The owning VTAM is the CP where the application
is expected to end up. If the owning CP were to fail, sessions in
this state would be maintained and could be recovered.
- TERMINATE
- The application CLOSEd its ACB, in a non-persistent manner, on
its owning VTAM, but not all
the multinode persistent sessions or RTP connections have been terminated
yet.
- UNKNOWN STATE
- The application is MNPS capable, but there is currently no local
application status block (ASB) available for this VTAM to use to determine the MNPS state of the
application. This will most probably occur when the application is
attempting to move from one VTAM to
this VTAM, but the ownership
of the application has not yet been transferred between the VTAMs.
Operators
can display the current application state from other VTAMs in the
sysplex that are connected to the MNPS structure.
System action
Operator response
System programmer response
Routing code
Descriptor code