EZD1246I

Explanation
 The application could not initialize because it
detected an error. 
 In the message text: applname
The name of the application. The application name can be one of
the following: ADNR for the automated domain name registration (ADNR) application 
LBADV for the z/OS® Load
Balancing Advisor (Advisor) 
LBAGENT for the z/OS Load
Balancing Agent (Agent) 
The job name of the Advisor or Agent, if it is configured for
subplexing 

reason
The reason code for the error.  Possible values are: 1
Another copy of the application is already active. If subplexing is being used: Only one copy of the Advisor can be active in the subplex.  
On each MVS™ system, only
one copy of the Agent can be active for each subplex on that system.

If subplexing is not being used: Only one copy of the Advisor can be active in the sysplex.  
Only one copy of the Agent can be active on each MVS system in the sysplex.

This reason code does not apply to ADNR.
2
The Agent, Advisor, or ADNR application cannot open the configuration
file, or found an  error in the configuration file.  Message EZD1235I
should precede this  message.  See the information about Load Balancing Advisor in z/OS Communications Server: IP Configuration
Reference for information about configuring the Advisor,
and for information about the Agent. See the information about automated domain name registration in z/OS Communications Server: IP Configuration
Reference for information about configuring the ADNR
application.
3
Indicates an internal error in the application. 
4
The Agent, Advisor, or ADNR application found an error in a start
option parameter in the  start procedure. 
5
The user ID associated with the started task is not authorized,
or the  application was not started as a started procedure.  See  z/OS Communications Server: IP Configuration
Guide for information about setting up the authorization
 profiles for the security product.  
6
A required resource is not available.  For example, the TCP/IP
stack  is not started, or a configured IP address is not defined or
available on the  TCP/IP stack, or the Advisor or Agent was configured
for subplexing and a TCP/IP stack or VTAM® node
corresponding to the specified TCP/IP sysplex group name could not
be found.

System action
 The application ends.

Operator response
  If the reason value is 1,
then verify that the copy of the application that is active is the
one that is wanted.  If a previous copy of the application was stopped
but  never ended, issue a CANCEL command to cancel the previous copy
before starting  the new copy.  
If the reason value is 6,
then start the TCP/IP stack, if it is not already started.  
If the stack is already started, and for all other reason values,
save the syslogd file and contact the system programmer.

System programmer response
 Take action appropriate for the reason
as follows:  1
If subplexing is being used, ensure that the correct TCP/IP sysplex
group name is coded in the configuration file for the Agent and Advisor
in each subplex.
2
Examine the application syslogd file for errors.  Correct the
 configuration file as needed.
3
Contact IBM® software support
center.  The application syslogd file is the minimum  diagnostic data
that should be provided.  See  z/OS Communications Server: IP Diagnosis Guide for information about collecting diagnostic
data.
4
Examine the application syslogd file for errors.  Correct the
start  procedure as needed.
5
Examine the security product profiles that have been established
for  the Advisor, Agent, and ADNR.  Ensure that the application was
started from a started  procedure and that the user ID in the start
procedure is permitted to the  appropriate profiles if they are defined.
6
Examine the application syslogd file for errors.  Verify that
the  correct IP addresses are configured in the configuration file.
 Correct the  configuration file as needed. See the information about
the  Load Balancing Advisor in z/OS Communications Server: IP Configuration
Reference for more information about configuring the
Advisor, and for information about the Agent. See the information
about automated domain name registration in z/OS Communications Server: IP Configuration
Reference for information about configuring the ADNR
application.

User response
  If the reason value is 1,
then verify that the copy of the application that is active is the
copy that is wanted.  If a previous copy of the application was stopped
but never ended, issue a CANCEL command to cancel the previous copy
before starting  the new copy.  
If the reason value is 6,
then start the TCP/IP stack, if it is not already started.  
If the stack is already started, and for all other reason values,
save the syslogd file and contact the system programmer.

Problem determination
 To ensure that there is sufficient information
to debug this problem, configure the application to use a debug level
of 127 and restart the application. See z/OS Communications Server: IP Configuration
Reference for information about how to configure the
debug level for the specified application.
 Contact IBM software support center. The
application syslogd file is the minimum diagnostic data that should
be provided. See  z/OS Communications Server: IP Diagnosis Guide for information about collecting diagnostic
data.

Problem determination
 Not applicable.

Source
 z/OS Communication
Server TCP/IP other application

Module
 lamain.c, lmmain.c, ldmain.c

Routing code
 10

Descriptor code
 12

Example
  None.