ATB80008I Address space cannot use the system base LU.
Explanation
A TP called the LU 6.2 Allocate or CPI-C Initialize_Conversation service. The request did not specify a local LU name, so APPC/MVS selected a local LU to be the source of the conversation. The program is running in an address space that is associated with an alternate transaction scheduler. No base LU is defined for the alternate scheduler. The system base LU is owned by the APPC scheduler (ASCH), so the address space in which the TP is running cannot use the system base LU.
System action
The system returns a product_specific_error (decimal 20) return code to the caller of the Allocate or Initialize_Conversation service.
Operator response
At the request of the application programmer, enter a DISPLAY APPC,LU command to determine if other LUs are available to the scheduler.
At the request of the system programmer, enter a SET APPC=xx command to activate a newly defined LU in the APPC/MVS configuration.
System programmer response
At the request of the application programmer, enter an LUADD statement in an APPCPMxx parmlib member to define a base LU for the alternate transaction scheduler or a NOSCHED LU. Then ask the operator to enter a SET APPC=xx command to activate the newly defined LU in the APPC/MVS configuration.
Programmer response
- Contact the system programmer to determine if a base LU can be defined for the alternate transaction scheduler.
- Contact the system programmer to determine if a NOSCHED base LU can be defined.
- Contact the operator to determine if other LUs are available to the scheduler. These may be LUs associated with that scheduler, or LUs not associated with any scheduler (NOSCHED LUs). Change the TP to use the ATBALC2 version of Allocate, and specify the name of an LU available to the scheduler on the Local_LU parameter.
- Ensure that the TP tries to allocate or initialize the conversation from an address space that is able to use the system base LU.
Source
APPC/MVS
| Detecting Module: |
| ATBVSAL, ATBVSIN |