z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


MNPS session recovery error

z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
GC27-3667-00

Problem statement
One or more MNPS sessions were terminated unexpectedly and were not recovered. This can be due to any of several possible causes.
Probable cause 1
Pathswitcher time set by HPRPST expired on other end of HPR pipe.
User response 1
Restart the application using automatic restart manager (ARM). Set HPRPST to allow more time (if possible) or recover more quickly the next time.
Probable cause 2
HPR connectivity is not consistent throughout the sysplex.
User response 2
Update network definitions to make sure that connectivity is consistent among all the MNPS nodes.
Probable cause 3
The VTAM® is not in a sysplex, or the VTAM nodes are not in the same subplex, if subplexing is being used. Subplexing is being used if the XCFGRPID start option has been used to specify an XCF group ID suffix.
User response 3
Implement the recovery in a sysplex environment. If subplexing is being used, ensure that all nodes involved in MNPS sessions and session recovery are in the same subplex. VTAM nodes are in the same subplex if each node specifies the same 2-digit value on the XCFGRPID start option.
Probable cause 4
VTAM is not connected to the MNPS structure.
User response 4
Check the value of the STRMNPS start option. To determine the status of VTAMs connection, issue the command:
D NET,STATS,type=CFS,ID=MNPSstructurename
Probable cause 5
Pathswitcher time set by PSTIMER has expired.
User response 5
Restart the application using automatic restart manager (ARM). You can set the timer to allow more time using the application start definitions or else recover more quickly the next time.
Probable cause 6
The PERSIST=MULTI operand is not defined for the application. This sets the application for MNPS; if it is not defined, MNPS is not allowed.
User response 6
Terminate the application. Define PERSIST=MULTI on the APPL definition statement. Restart the application.
Probable cause 7
Session traverses a subarea path not on an RTP connection.
User response 7
Change the network configuration to ensure that the session is established over valid network routes. Ensure that SORDER is set to search APPN first.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014