Common AT-TLS startup errors

The following list describes startup errors, possible causes, and actions to take.

• If message EZZ4248E is written to the console and not released, one of the following might have occurred:
  • Policy Agent has not been started.
  • Policy Agent configuration does not contain a TCPImage statement for this stack, or the stack policy configuration does not contain any local or remote AT-TLS policies.
  • Policy Agent is not permitted to create a socket with this stack. Ensure that the SERVAUTH class is active. Ensure that the EZB.INITSTACK.mvsname.tcpname resource profile is defined and that Policy Agent is permitted to it. If the EZB.STACKACCESS.mvsname.tcpname resource profile is defined, ensure that Policy Agent is permitted to it.
• If message EZD1288I is displayed, the AT-TLS group is configured with FIPS140 on, but ICSF is not active. Start ICSF before starting AT-TLS groups configured with FIPS140 On.
• If applications started after the stack fail to create a socket (errno EAGAIN, errno2 JrTcpNotActive), the stack is probably being configured for AT-TLS, and the application has been started before AT-TLS policy has been installed. If this is a required network infrastructure application, permit it to the EZB.INITSTACK.mvsname.tcpname resource profile in the SERVAUTH class. If it is not a required network infrastructure application, either start it after message EZZ4248E is released or modify the application to wait a short time and try again when the errno is EAGAIN.
• If message EZD1287I TTLS Error RC: 5020 Group Init is displayed, the TCP/IP stack was not able to load the System SSL DLL required for AT-TLS processing.