ATB80067I The Local LU unregistered as a resource manager causing the allocate request to fail.

Explanation

A TP called the LU 6.2 Allocate service or the CPI-C Allocate service to allocate a conversation with a synchronization level of syncpt, but the request could not be processed because the local LU became unregistered as a resource manager, which resulted in the allocate request failing. The local LU may have unregistered as a resource manager for one of the following reasons:
  • An LUDEL was issued to quiesce work for the local LU and delete the LU from the APPC configuration.
  • The transaction scheduler for the local lu unidentified itself from APPC/MVS.
  • The syncpoint manager (RRS) became unavailable.
  • A VTAM VARY command was issued to stop work for the local LU immediately.
  • VTAM became unavailable.
  • An internal APPC error caused the local LU to become unregistered as a resource manager.

System action

The system returns a product_specific_error (decimal 20) return code to the caller. No further conversation services will be successful for the conversation.

Operator response

At the request of the application programmer:
  • Enter a DISPLAY APPC,LU command to display the LUs that are currently defined to the APPC/MVS configuration. Verify that the Local LU is defined to the APPC/MVS configuration, is registered as a resource manager and is capable of processing conversations with a synchronization level of syncpt.
  • Verify that RRS is available.
  • Verify that VTAM is available and the local LU is active in the VTAM configuration.

System programmer response

If the operator determines that VTAM and RRS are available and the local LU is defined and active in the APPC/MVS configuration, but the local LU is still not capable of processing conversations with a synchronization level of syncpt, search the problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the logrec data set error records and any SVC dumps taken by APPC/MVS.

Programmer response

Contact the operator to determine why the local LU may have unregistered as a resource manager and have the Operator verify that the Local LU is currently registered as a resource manager before attempting to the allocate another syncpt conversation.

Source

APPC/MVS