Explanation
This message is issued when an LU 6.2 application
program requests that a session be established, but a session level
LU-LU verification violation or error occurred.
profilename is
the name of the security manager profile defined for the LU pair.
The format of
profilename is
local_netid.local_name.partner_name where:
- local_netid is the local network ID
- local_name is the ACB name of the local application program
- partner_name is the LU name of the session partner.
code is the type of security violation
that occurred.
- 03
- The security manager locked the profile.
- 04
- The profile contains an invalid session key.
- 05
- partner_name rejected the session due to a
security related error.
- 06
- local_name was defined with REQUIRED session
level LU-LU verification, but one of the following occurred:
- local_name is the PLU, but no password was
defined for profilename.
- partner_name is the PLU requesting a session
without using session level LU-LU verification.
- 07
- Session level LU-LU verification data for the session between local_name and partner_name matched
the data for an outstanding session activation request.
- 08
- local_name was defined with optional verification,
and a password was defined for profilename, indicating
that session level LU-LU verification is necessary. partner_name requested
a session without verification.
- 09
- local_name was defined with optional verification,
and no password was defined for profilename, indicating
that session level LU-LU verification should not be used. partner_name requested
a session with verification.
- 0B
- The profile was changed during session activation.
- 0C
- The password for the profile has expired.
- 0D
- local_name was defined to use only the enhanced
protocol (SECLVL=LEVEL2 is specified on the APPL definition statement). partner_name does
not support the enhanced protocol.
- 20
- The security manager component is either not available or overloaded
(received a large number of requests in a short period of time).
- 3C
- The security manager component failed.
System action
Session activation failed.
Operator response
For codes 03, 04, 0B, and 0C,
enter the MODIFY PROFILES command for the local LU. If VTAM® issues this message repeatedly, notify
the security administrator of code and profilename.
For
code 05, consult message IST970I issued to the partner LU for
specific actions.
For codes 06, 08, and 09, enter
the MODIFY PROFILES command for the local LU. If VTAM issues this message repeatedly, save the
system log for problem determination.
For codes 07 and 0D,
notify the security administrator of code and profilename.
For
codes 20 and 3C, save the system log for problem determination.
System programmer response
For code 05, consult
message IST970I issued to the partner LU for specific actions.
For
codes 06, 08, and 09, check the VERIFY operand
specified on the APPL statements to identify the correct level for
the two LUs.
For code 20, verify that the security manager
is installed and resource class APPCLU is active.
If the security
manager is installed and resource class APPCLU is active, the problem
may be that the security manager is overloaded. Lowering the value
of AUTOSES on the LU definition statements may solve the problem.
For
code 3C, verify that the security manager is installed and
resource class APPCLU is active.
Routing code
Descriptor code