ATB70017I TP security violation. Partner LU plu_name rejected the allocate request because authorization checks failed.
Explanation
APPC/MVS received an inbound allocate request
(FMH-5). A TP security violation occurred. The TP encountered one
of the following security violations, depending on the security_type
value specified on the allocate request:
- The user ID, password, or optional group profile name is not valid
- The MVS LU does not accept security_none requests
- The user is not authorized to access the partner LU from this local LU.
In the message text:
- plu_name
- The name of the LU where the allocate request arrived.
System action
The system rejects the request with a sense code of security_violation (X'080F6051').
System programmer response
Depending on the security_type value
specified on the allocate request, do one of the following:
- For a security_type of security_none, verify that the LU accepts security_none allocate requests by checking the security product class profiles that control user access to the LU, or checking the SECACPT parameter value on the VTAM APPL definition of the LU.
- For a security_type of security_pgm or security_same, verify that the user has authority to access the partner LU from this local LU by checking the security product class profiles that control user access to and from the LU, or by checking the SECACPT parameter value on the VTAM APPL definition of the LU.
See z/OS MVS Planning: APPC/MVS Management for more information about controlling access to or from LUs.
Programmer response
If a security_type of security_pgm was specified on the allocate request, verify the user ID, password, and group profile name (if any) that are specified on the allocate request. If these values are correct, or if a different security_type was specified on the allocate request, ask the security administrator to help you determine what caused the security violation.
Source
APPC/MVS
|