Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Restarting APPC/MVS z/OS MVS Planning: APPC/MVS Management SA23-1388-00 |
|
If APPC/MVS encounters an unrecoverable error when starting either
of its two address spaces, APPC or ASCH, it attempts to restart the
address space automatically. If your installation is using different
names for the APPC or ASCH started procedure, APPC/MVS cannot use
that name in its restart attempt; it uses "APPC" or "ASCH",
which means that:
If you code a time on the PSTIMER parameter of the LUADD statement, VTAM® keeps LU-to-LU sessions active during interruptions in APPC/MVS service. Even though APPC/MVS has been deactivated, the VTAM persistent sessions remain active for the length of time that you specify on the PSTIMER parameter. For an APPC/MVS LU that handles protected conversations, however, sessions on which syncpoint operations were in progress do not persist. All other sessions still have the persistent attribute. In this case, the session is unbound so that outstanding resynchronization work can proceed when the LU is reactivated. If APPC/MVS could not restart the APPC address space automatically
(indicated by message ATB006I), or if the address space was stopped
by a CANCEL or FORCE command (message ATB010I or ATB012I, respectively),
do the following to restart the APPC address space:
If APPC/MVS could not restart the APPC/MVS transaction scheduler
(ASCH) address space automatically (indicated by message ASB051I),
or if the address space was stopped by a CANCEL or FORCE command (message
ASB059I), do the following to restart the ASCH address space:
Note that each time you cancel APPC and ASCH, the system marks the address spaces in which they were running as non-reusable until the next IPL. Therefore, do not cancel and then restart them unnecessarily. See Recovering from APPC problems for more information on recovery from APPC problems. |
Copyright IBM Corporation 1990, 2014
|