Messages ECAB00 through ECABxx

This group includes messages for the IOA (infrastructure) product.

ECAB01I CHANNEL(channelId) ECAPARM PORT SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUE

Explanation: This information message indicates that the PORT value specified in the EXEC PARM parameters successfully replaced the ECAPARM PORT value of the indicated channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If a TCP/IP port number was specified in EXEC PARM, then IOAGATE replaces the PORT value specified in the ECAPARM configuration file for the indicated channel with the value from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel with the PORT value that was replaced.

Corrective Action: No action is required.

ECAB02I CHANNEL(channelId) ECAPARM APPLIDS SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUE

Explanation: This information message indicates that the APPLIDS values specified in the EXEC PARM parameters successfully replaced the ECAPARM APPLIDS values of the specified channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If VTAM LU 6.2 (APPC) APPLIDS was specified in EXEC PARM, IOAGATE tries to replace the APPLIDS values specified in the ECAPARM configuration file for the indicated channel with values from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel with the APPLIDS values that were replaced.

Corrective Action: No action is required.

ECAB03W PORT AND APPLID CANNOT BE SPECIFIED FOR THE SAME CHANNEL SIMULTANEOUSLY

Explanation: A PORT value and an APPLID value were specified in the EXEC PARM parameters simultaneously.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. A TCP/IP port number and a VTAM LU 6.2 (APPC) APPLID were specified in the EXEC PARM parameters simultaneously. These values cannot be specified together.

Both the PORT and APPLID values are ignored. Normal processing continues.

Corrective Action: Correct the indicated parameters and restart IOAGATE.

ECAB04I CHANNEL(channelId) ECAPARM APPLID SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUE

Explanation: This information message indicates that the APPLID value specified in the EXEC PARM parameters successfully replaced the ECAPARM APPLID value of the specified channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If VTAM LU 6.2 (APPC) APPLID was specified in EXEC PARM, IOAGATE tries to replace the APPLID value specified in the ECAPARM configuration file for the indicated channel, with the value from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel for which the APPLID value was replaced.

Corrective Action: No action is required.

ECAB05W PORT(port) SPECIFIED BY THE EXEC PARM WAS NOT APPLIED

Explanation: The PORT value in the EXEC PARM parameters was not used, and the ECAPARM PORT value is still valid.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. When a TCP/IP port number is specified in EXEC PARM, the IOAGATE tries to replace the PORT value specified in the ECAPARM configuration file for the intended channel with the value from EXEC PARM.

The current attempt failed and the ECAPARM PORT value is still valid. The channel for which the specified PORT value was intended may have been disabled during initialization.

In this message, port is the TCP/IP communication port value specified in EXEC PARM.

Corrective Action: Do the following:

1. Look for more information in
   • IOAGATE JES log
   • the DAIGLOG log
   • the DATRACE log
2. Try to correct the problem.
3. If you cannot correct the problem, contact BMC Customer Support.

ECAB06W APPLIDS(applId1, applId2) SPECIFIED BY THE EXEC PARM WERE NOT APPLIED

Explanation: The APPLIDS values specified in the EXEC PARM parameters were not used, and the ECAPARM APPLIDS values are still valid.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. When VTAM APPLIDS application IDs are specified in EXEC PARM, the IOAGATE tries to replace the APPLIDS values specified in the ECAPARM configuration file for the intended channel with the values from EXEC PARM.

The current attempt failed and the ECAPARM APPLIDS values are still valid. The channel for which the specified APPLIDS values were intended may have been disabled during the initialization.

In this message, applId1 and applId2 are VTAM LU 6.2 (APPC) application IDs specified by the APPLIDS parameter in EXEC PARM for a dual connection (DC) SNA channel.

Corrective Action: Do the following:

1. Look for more information in
   • the IOAGATE JES log
   • the DAIGLOG log
   • the DATRACE log
2. Try to correct the problem.
3. If you cannot correct the problem, contact BMC Customer Support.

ECAB08E PORT SPECIFIED BY THE EXEC PARM FOR SNA CHANNEL(channelId) CANNOT BE USED

Explanation: A PORT value that was specified in the EXEC PARM parameters was not applied.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup, and tries to modify the channel that is explicitly specified in the EXEC PARM parameters. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

The TCP/IP port number was specified in the EXEC PARM parameters. However, IOAGATE could not apply the PORT value.

In this message, channelId is the identity of the SNA channel.

Possible causes are:

• A specific CHAN parameter was specified in EXEC PARM parameters, but this is an SNA channel.
• IOAGATE tried to apply the PORT value to the first ECAPARM channel, but this channel is an SNA channel.

The PORT parameter in EXEC PARM is ignored. Normal processing continues.

Corrective Action: Correct the EXEC PARM parameters and restart IOAGATE.

ECAB09E applIdParm SPECIFIED BY THE EXEC PARM FOR CHANNEL(channelId.TCP) CANNOT BE USED

Explanation: The APPLID or APPLIDS values set in the EXEC PARM parameters cannot be used. During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup, and tries to modify the channel that is explicitly specified in the EXEC PARM parameters. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

APPLID or APPLIDS values were specified in the EXEC PARM parameters. However, IOAGATE could not apply the specified values.

Possible causes are:

• An explicit CHAN parameter was specified in the EXEC PARM parameters, but this is a TCP channel.
• IOAGATE tried to apply the specified value to the first ECAPARM channel, but this channel is a TCP channel.

The variables in this message are:

• applIdParm - the APPLID or APPLIDS parameter specified by the user in the EXEC PARM parameters
• channelId - the identity of the TCP channel

The APPLID or APPLIDS EXEC PARM parameter is ignored. Normal processing continues.

Corrective Action: Correct the EXEC PARM parameter applIdParm and restart IOAGATE.

ECAB0AE IMPROPER CHANNEL(channel. chEntryId) SPECIFIED TO SUPPORT MAP(mapId), APSERVER(applName. apEntryId) DISABLED

Explanation: IOAGATE detected an invalid channel reference from an APSERVER definition in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The specified channel cannot serve IOAGATE-to-IOAGATE communication over a multiple connection (MC) channel with the network map specified.

The variables in this message are:

• channel - the channel identity assigned by the user in the ECAPARM configuration file
• chEntryId - the sequential number of the channel definition entry in the ECAPARM configuration file
• mapId - the name of a member in the IOA PARM library that describes a map of network connections between IOAGATEs allowing one IOAGATE to communicate with another over a multiple connection (MC) channel
• applName - the full name of the application declared by an APSERVER definition
• apEntryId - the sequential number of an APSERVER definition entry in the ECAPARM configuration file

The specified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAB0BE CHANNEL(channel. chEntryId) MAP MUST BE SPECIFIED, APSERVER(applName. apEntryId) DISABLED

Explanation: IOAGATE detected an improper channel specification for the application.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. It detected that the specified channel does not have a network map specification that is required for the indicated application server.

The variables in this message are:

• channel - the channel identity assigned by the user in an APSERVER definition
• chEntryId - the sequential number of the channel definition entry in the ECAPARM configuration file
• applName - the full name of the application declared by an APSERVER definition
• apEntryId - the sequential number of an APSERVER definition entry in the ECAPARM configuration file

The specified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the APSERVER and CHANNEL definitions and restart IOAGATE.

ECAB0DI processor PROCESSOR CREATED(timeStamp) CCID(changeLevel)

Explanation: This information message indicates the program level of the specified processor of IOAGATE.

The variables in this message are:

• processor - the name of the parameter member. Valid values are:
  • ECAAPPL
  • ECAPARM
  • NWORKMAP
• timeStamp - the date and time when the specified processor was compiled
• changeLevel - the level of the change that was last applied to the specified processor

Corrective Action: No action is required.

ECAB10W EXEC PARM PARAMETER CHAN= MUST BE 2 CHARACTERS EXACTLY, PARAMETER IGNORED

Explanation: The value of the CHAN parameter that was specified at startup of the IOAGATE is invalid.

The channel ID specified by the CHAN parameter must have two characters exactly.

Corrective Action: Correct the value of the CHAN parameter and restart IOAGATE.

ECAB11S INSUFFICIENT MEMORY(area_size) GETMAIN FOR (area_id) FAILED

Explanation: The GETMAIN request issued by IOAGATE or the application server address space failed.

IOAGATE issued a GETMAIN request during initialization to obtain main storage for the specified area. However the call failed because there was not enough main storage.

The variables in this message are:

• area_size - the size of the area GETMAIN requested
• area_id - the internal identity of the area for which main storage resources were requested.

The IOAGATE or application server address space shuts down with a return code of 56 or 08, respectively.

Corrective Action: Increase the region size and restart the IOAGATE. If you cannot resolve the problem, contact BMC Customer Support.

ECAB17W EXEC PARM PARAMETER PORT= MUST BE A NUMERIC VALUE IN THE RANGE FROM 1024 TO 65534

Explanation: The value set for the PORT parameter in the EXEC PARM parameters is invalid.

The PORT parameter value must be in the range from 1024 through 65534.

The PORT parameter value specified in the ECAPARM configuration file remains valid.

Corrective Action: Specify a valid value for the PORT parameter in the EXEC PARM parameters, and restart IOAGATE.

ECAB18W EXEC PARM PARAMETER APPLID= MUST BE UP TO 8 ALPHANUMERIC CHARACTERS

Explanation: The APPLID parameter value specified in the EXEC PARM parameters is invalid.

The APPLID parameter must comply with VTAM naming conventions.

The value of the APPLID parameter specified in the ECAPARM configuration file is still valid.

Corrective Action: Specify a valid value for the APPLID parameter in the EXEC PARM parameters and restart IOAGATE.

ECAB22I EXEC PARM PARAMETERS: parms

Explanation: This information message displays the EXEC PARM parameters that were specified in the PARM field of the EXEC JCL statement.

Corrective Action: No action is required.

ECAB27I START FOR SERVER TASK(type. taskId. addrSpaceId) INITIATED

Explanation: This information message indicates that the operator issued the F IOAGATE,STARTTID=taskId command. IOAGATE submitted a STARTTID command for the specified task.

The variables in this message are:

• type - the CS (application server) task type
• taskId - the internal identity of a server task
• addrSpaceId - the internal identity of the application server address space to which this task belongs

Corrective Action: No action is required.

ECAB30E AN ATTEMPT TO LAUNCH SERVER TASK(taskId) FAILED

Explanation: An attempt to launch an application server task failed.

During initialization or automatic recovery, IOAGATE launches the server tasks for all application servers defined in the ECAPARM configuration file. However, an attempt to launch a server task failed.

In this message, taskId identifies the server task that failed.

Corrective Action: Examine the IOAGATE JES log, DAIGLOG, DATRACE logs for more information about the problem. Try to find the cause and correct the problem.

ECAB32S ECAGTW INTERNAL ERROR, ADDRESS/VALUE(value_id) LOST

Explanation: IOAGATE encountered a severe internal error.

IOAGATE may shut down or continue, depending on the severity of the error.

Corrective Action: Contact BMC Customer Support.

ECAB36E SERVER TASK(type. taskId. addrSpaceId) CANNOT BE STOPPED BY OPERATOR

Explanation: IOAGATE rejected an F IOAGATE,STOPTID=taskId command, because an operator is not allowed to stop this task. A STOPTID command was issued for a CM, CD or CU server task. The specified server task can be stopped only if an entire application server address space is stopped.

The variables in this message are:

• type - the server task type Possible values are:
  • CM - the manager of the address space of an application server
  • CD - a detector server
  • CU - an updater server
• taskId - the internal identity of a server task
• addrSpaceId - the internal identity of the application server address space to which this task is assigned

The modify command is rejected.

Corrective Action: Use the F IOAGATE,STATUS command to specify the task ID, and reissue the command.

ECAB38I AUTOMATIC RECOVERY (recoveryId) FOR APPL.SERVER (applServerName. addrSpaceId) INITIATED

Explanation: This information message indicates that an application server address space abended, and IOAGATE initiated an automatic recovery. IOAGATE initiates an automatic recovery for an abended server address space if a nonzero value is specified for the MAXRECOV parameter in the APSERVER definition for this application server.

The variables in this message are:

• recoveryId - the internal sequence number of this recovery incident
• applServerName - the full name of the application server
• addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB39W APPL.SERVER (applServerName. addrSpaceId) CANNOT BE RECOVERED, THRESHOLD(threshold) REACHED

Explanation: An application server address space abended, and IOAGATE cannot initiate the automatic recovery for the server. IOAGATE does not initiate an automatic recovery for the abended application server, because the maximum number of subsequent recovery retries was already performed. This threshold is specified by the MAXRECOV parameter in the APSERVER definition in the ECAPARM configuration file for this application server.

Note:

Recovery retries are subsequent if the interval between retries is shorter than the time specified by the RECVRSET parameter in the ECAPARM configuration file.

The variables in this message are:

• applServerName - the name of the application server
• addrSpaceId - the internal identity of the application server address space
• threshold - the maximum number of subsequent recovery retries

Corrective Action: Examine the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more messages about the problem. Try to determine why the application server failed and correct the problem. If you cannot correct the problem, call your system programmer for assistance.

ECAB40W SERVER TASK (type.taskId.addrSpaceId) CANNOT BE RECOVERED, THRESHOLD(threshold) REACHED

Explanation: A server task abended, and IOAGATE cannot initiate an automatic recovery for this server task.

IOAGATE does not initiate an automatic recovery for the abended application server task, because the maximum number of subsequent recovery retries was already performed. The MAXRECOV parameter in the APSERVER definition in the ECAPARM configuration file for this application server specifies the maximum number of subsequent retries allowed.

Note:

Recovery retries are subsequent if the interval between retries is shorter than the time specified by the RECVRSET parameter in the ECAPARM configuration file.

The variables in this message are:

• type - the CS (application server) task type
• taskId - the internal identity of a server task
• addrSpaceId - the internal identity of the application server address space to which this task belongs
• threshold - the maximum number of subsequent recovery retries

Corrective Action: Call your system programmer for assistance.

ECAB41I AUTOMATIC RECOVERY (recoveryId) FOR SERVER TASK(type.taskId.addrSpaceId) INITIATED

Explanation: This information message indicates that an application server task abended, and IOAGATE initiated an automatic recovery.

IOAGATE initiates an automatic recovery for the abended application server task, if a nonzero value was specified for the MAXRECOV parameter in the APSERVER definition for this application server.

The variables in this message are:

• recoveryId - the internal sequence number of this recovery incident
• type - the CS application server task type
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB42I ***** text date *****

Explanation: This information message displays the current local date at the system on which the IOAGATE is running. It is first issued when IOAGATE initialization is completed. It is issued again, at the beginning of each day.

The variables in this message are:

• text - Valid values are:
  • LOCAL CURRENT DATE (after initialization)
  • NEW DAY STARTED (beginning of new day)
• date - the local current date. The date format is defined in the IOAPARM member. The format can be redefined for IOAGATE by the DATETYPE parameter in the ECAPARM configuration file. Valid formats are:
  • MMDDYYYY
  • DDMMYYYY (default)
  • YYYYDDD
  • YYYYMMDD

Corrective Action: No action is required.

ECAB43W SERVER TASK(type.taskId.addrSpaceId) BUSY duration units, WARNING interval(repeater) SECs USER(userId) SIID(serviceInstanceId)

Explanation: The status of the application server task stayed BUSY with the same SIID service for longer than the warning interval allowed by the ECAPARM configuration file. This message indicates a possible internal problem in IOAGATE.

The variables in this message are:

• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - an application server
  • CD - a detector server
  • CU - an updater server
• taskId - the internal identity of the problematic server task If this server task is busy handling a request for an alias application, taskId is the short application code of the alias.
• addrSpaceId - the internal identity of the server address space to which this task is assigned
• duration - the number of time units during which the server task handles the same service for the same user
• units - the type of time unit in which the actual duration is expressed Valid values are:
  • secs - The duration is expressed in seconds
  • mins - The duration is expressed in minutes

If the actual duration is less than 5 minutes, duration is expressed in seconds. If the actual duration is 5 minutes or more, duration is expressed in minutes.

• interval - the number of units to wait before issuing this message The first time this message is issued, interval is defined by the SERVDUR parameter in the ECAPARM configuration file.

The value of interval for the second warning, and all subsequent warnings, is defined by the SERVDUR and NWARNING parameters that can be set in the ECAPARM configuration file. If both parameters are set, then interval is the value of SERVDUR multiplied by the value of NWARNING.

Setting SERVDUR to 0 in the ECAPARM configuration file for this server disables the message completely for this server. Setting NWARNING to 0 disables the second and all subsequent warnings. The default for SERVDUR is 60 seconds; the default for NWARNING is 10.

• repeater - the number of interval periods before a second or subsequent warning is issued The value of repeater can be specified in the NWARNING parameter in the ECAPARM configuration file. Valid values are 0 through 99. The default is 0, meaning that this message (ECAB43W) is issued only once.
• userId - the identity of the user whose request is in process
• serviceInstanceId - the service instance identity (SIID) that determines the which service request is handled by the server task

Corrective Action: Examine the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to determine the cause and correct the problem. Consider reassigning the SERVDUR and NWARNING parameters. If the problem persists, contact BMC Customer Support.

ECAB44W APPL.SERVER(addrSpaceId) DOES NOT EXIST

Explanation: An attempt to stop a specified application server using an F IOAGATE,STOPASID=addrSpaceId command failed, because the specified application server address space identity is incorrect. The application server address space identity addrSpaceId must be the correct internal identity of an application server address space.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to identify the correct application server address space identity, and then reissue the command correctly.

ECAB47I SERVER TASK(applServerName .type.taskId.addrSpaceId) RECOVERED SUCCESSFULLY

Explanation: This information message indicates that an application server task recovered successfully.

The variables in this message are:

• applServerName - the name of the application server
• type - the CS server task type
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB48I APPL.SERVER (applServerName.addrSpaceId.stcId) RECOVERED SUCCESSFULLY

Explanation: This information message indicates that the specified application server recovered successfully.

The variables in this message are:

• applServerName - the name of the application server
• addrSpaceId - the internal identity of the application server address space
• stcId - the name of the JCL procedure used to start the application server address space

Corrective Action: No action is required.

ECAB49I SERVER TASK(applServerName.type.taskId.addrSpaceId) STARTED SUCCESSFULLY

Explanation: This information message indicates that IOAGATE launched the specified application server task, and it started successfully.

The variables in this message are:

• applServerName - the full name of the application server
• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - application server
  • CD - a detector server
  • CU - updater server
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB4AW CHANNEL(channelId.protocol) TASK(taskId) TIMEOUT OCCURRED WHILE AWAITING REPLY FROM USER(userId) SIID(serviceInstanceId) SID(serviceId)

Explanation: This warning message indicates that a time-out occurred while awaiting reply from a partner or client because the partner or client did not respond to the message sent by IOAGATE during the time-out interval.

The variables in this message are:

• channelId - the identity of the channel that detected the event
• protocol - the communication protocol used by the channel Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the communication task that detected the event Valid values are:
  • COMTASK
  • RECEIVER
• userId - the identity of the user whose request was in process
• serviceInstanceId - the service instance identity (SIID) that indicates the service request being handled by IOAGATE
• serviceId - the code of a transaction to be performed by IOAGATE

The connection is assumed to be broken and the service is discarded.

Corrective Action: Check status of the partner or client and its communication link to IOAGATE.

ECAB4BW SERVER TASK(type.taskId.addrSpaceId) WILL BE CANCELLED DUE TO BEING BUSY FOR duration MINs, USER(userId) SIID(serviceInstanceId)

Explanation: The application server task is going to be terminated, because it has been in BUSY status with the same SIID service for more than the maximum time allowed by the BUSYDUR parameter in the ECAPARM configuration file. This may indicate a potential internal problem in IOAGATE or in the application server address space.

The variables in this message are:

• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal identifier of the problematic server task
• addrSpaceId - the internal identifier of a server address space of this task
• duration - the time a server task handles the same service for the same user
• userId - the identifier of a user whose request is in process.
• serviceInstanceId - the service instance identifier (SIID) that determines the service request being handled by the server task

The specified application server task is terminated. If it is a critical task, then the whole application server address space is terminated due to this server task failure.

Corrective Action: Do the following:

1. If the problem persists, examine the IOAGATE JES log, DAIGLOG log, and DATRACE log for additional information about the potential problem.
2. Try to find the cause and correct the problem.
3. Consider re-assigning a BUSYDUR parameter.
4. If the problem is not resolved, contact BMC Customer Support.

ECAB50I APPL.SERVER(applServerName.addrSpaceId.proc.stcId.channelId/jobId) STARTED SUCCESSFULLY

Explanation: This information message indicates that the specified application server started successfully.

The variables in this message are:

• applServerName - the name of the application server
• addrSpaceId - the internal identity of the application server address space
• proc - the name of the procedure of the application server address space
• stcId - the name of the JCL procedure used to start the application server address space
• channelId - the channel identity referenced from the APSERVER definition that creates this application server
• jobId - the STC JOBID of the application server assigned by JES to its address space

Corrective Action: No action is required.

ECAB51W APPL.SERVER(applServerName.addrSpaceId.stcId.channelId) HAS NOT BECOME AVAILABLE IN THE LAST interval SECONDS

Explanation: The application server has not started in the specified time interval, either since IOAGATE launched the application server, or since the last occurrence of the same warning. There might be a problem that prevents the application server from starting in time.

The variables in this message are:

• applServerName - the name of the application server
• addrSpaceId - the internal identity of the application server address space
• stcId - the name of the JCL procedure used to start the application server
• channelId - the channel identity referenced from the APSERVER definition that creates this application server
• interval - the number of seconds to wait before issuing this warning messageThe default is 180 seconds.

Corrective Action: Check the application server log, the IOAGATE log, the JES log, the DAIGLOG log, and the DATRACE log for more information. If you cannot correct the problem, contact BMC Customer Support.

ECAB52W TIMER WAS NOT SET FOR THE SERVER TASK (type.taskId.addrSpaceId)

Explanation: An internal timer did not start for the specified server task due to an internal problem.

The variables in this message are:

• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal identity of this server task
• addrSpaceId - the internal identity of the application server address space

Corrective Action: If the problem persists, contact BMC Customer Support.

ECAB54W SERVER TASK (type.taskId.addrSpaceId) IS IN STATUS(status_id) FOR MORE THAN interval SECONDS

Explanation: IOAGATE detected that the specified server task has had the same temporary status for longer than the maximum time interval defined in the ECAPARM configuration file.

This condition might indicate an internal problem in IOAGATE.

The variables in this message are:

• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal identity of the problematic server task
• addrSpaceId - the internal identity of the application server address space to which the indicated task belongs
• status_id - the internal identity of the status in which the server task staysValid values are:
  • WAIT
  • PENDING
• interval - the number of seconds to wait before issuing this warning messageThis value can be assigned by the STATDUR parameter in the ECAPARM configuration file. The default is 60 seconds.

Normal processing continues. However, the further consequences of the event are unpredictable.

Corrective Action: If the problem persists, call BMC Customer Support.

ECAB55W SERVER TASK (type.taskId.addrSpaceId) HAS NOT BECOME AVAILABLE IN THE LAST interval SECONDS

Explanation: The server task did not start within the indicated time interval.

There might be a problem that prevents a server task from being started in time.

The variables in this message are:

• type - the server task type Valid values are:
  • CM - the manager of the address space of an application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the application server address space to which the indicated server task belongs
• interval - the time interval in seconds to wait before issuing this warning

Corrective Action: Check the application server log, the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. If you cannot correct the problem, contact BMC Customer Support.

ECAB56W SERVER TASK (type.taskId.addrSpaceId) FAILED TO RECOVER IN THE LAST interval SECONDS

Explanation: The specified server task did not recover successfully during the specified time interval. There might be a problem that prevented the application server task from recovering in time.

The variables in this message are:

• type - the CS server task type
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the server address space
• interval - The actual time in seconds during which the server task did not recover

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to fix the problem. Consider reassigning a SERVDUR parameter. For more assistance, contact BMC Customer Support.

ECAB57W APPL.SERVER (applServerName.addrSpaceId.stcId.channelId) FAILED TO RECOVER IN THE LAST time SECONDS

Explanation: The specified application server did not recover successfully within the specified time interval. There might be a problem that prevented the application server from recovering in time.

The variables in this message are:

• applServerName - the name of the application server
• addrSpaceId - the internal identity of the server address space
• stcId - the JCL procedure used to start the application server address space
• channelId - the channel used by this application server
• time - the actual time in seconds during which the application server did not recover

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. Consider reassigning a SERVDUR parameter. For more assistance, contact BMC Customer Support.

ECAB60I STATISTICS COLLECTION STARTED. INTERVAL IS interval MINUTES

Explanation: This information message indicates that statistics collection for IOAGATE communication started. It is issued during IOAGATE startup when STAT is set to YES in the ECAPARM configuration file, and when the command F IOAGATE,STATON,INTERVAL= interval is issued.

Up to six columns of statistics are collected and saved. After that, existing columns are overwritten. For example, the seventh column of statistics replaces the first.

In this message, interval is the number of minutes during which statistics are collected for each column. After interval minutes, statistics collection for the next column begins.

Corrective Action: No action is required.

ECAB61I STATISTICS COLLECTION STOPPED

Explanation: This information message indicates that statistics collection stopped in response to an F IOAGATE,STATOFF command. Collected data is purged and will not be available.

Corrective Action: No action is required.

ECAB62I STATISTICS DATA WAS RESET

Explanation: This information message indicates that the command F IOAGATE,STATRESET was issued.

Data collected earlier is purged, and collection of new data restarts immediately.

Corrective Action: No action is required.

ECAB63W STATISTICS COLLECTION IS ALREADY ON

Explanation: An F IOAGATE,STATON command was issued, but statistics collection for IOAGATE was already active. To reset the statistics collected data, use the command F IOAGATE,STATRESET instead.

IOAGATE statistics collection is not restarted. The modify command is rejected.

Corrective Action: No action is required.

ECAB64W STATISTICS COLLECTION IS ALREADY OFF

Explanation: An F IOAGATE,STATOFF command was issued, but statistics collection for IOAGATE was not active.

The modify command is rejected. Normal processing continues.

Corrective Action: No action is required.

ECAB65W INVALID STATISTICS INTERVAL WAS SPECIFIED

Explanation: The value of interval in the command F IOAGATE,STATON,INTERVAL=interval is not valid.

The statistics interval sets the time scale for statistics collection and presentation. It must be in the range from 1 through 999 (minutes). For example, if INTERVAL is set to 5, the statistics report will maintain and present the figures at intervals of 5 minutes.

The modify command is rejected. Normal processing continues.

Corrective Action: Correct the value of interval and reissue the command.