KGW0001E GWSAA UNABLE TO ACQUIRE SESSION ACCOUNTING AREA

Explanation

Locate or build of a session accounting area could not be attempted due to insufficient storage.

System action

The function is bypassed.

User response

Check the RKLVLOG output for additional messages that may indicate storage-related problems. If problems persist, contact IBM Software Support.

KGW0004E subtask CANNOT COMMUNICATE WITH XMI

Explanation

The system was unable to locate the address of the XMI communication control block using TMS:Engine services.

System action

The subtask identified by the subtask value stops processing.

User response

Confirm that XMI successfully started as a subtask of the Tivoli Enterprise Monitoring Agent address space. Ensure that there is a START command in the Tivoli Enterprise Monitoring Agent CONFIG file that automatically starts XMI. If problems persist, contact IBM Software Support.

KGW0005I AGENT module PTF ptfno @ address ASSEMBLY date time

Explanation

This informational message is written to the RKLVLOG when an agent is first invoked. It lists the agent name, most recently applied PTF, the load point, and date and time of assembly.

System action

None.

User response

None, the message is informational.

KGW0007E XAM INVALID PARAMETERS SPECIFIED

Explanation

The parameter specified on the start command for the exception analysis manager (XAM) subtask is invalid.

System action

The exception analysis manager continues processing.

User response

Specify a valid parameter.

KGW0009E ADDRESS OF GW CVT IS MISSING

Explanation

The Product Communication Vector Table (CVT) could not be located.

System action

Statistics API subtask fails to start.

User response

Try to start the Statistics API component again. If problems persist, contact IBM Software Support.

KGW0017E UNABLE TO ALLOCATE XCB CONTROL BLOCK

Explanation

The cross-memory interface (XMI) subtask was unable to allocate one of its primary communications control blocks from subpool 251 storage.

System action

The cross-memory interface task stops processing.

User response

Consider increasing the region size of the address space in which XMI is started.

KGW0022I XAM EXCEPTION ANALYSIS MANAGER IS TERMINATING

Explanation

The Exception Analysis Manager (XAM) received a request to stop processing.

System action

None.

User response

None.

KGW0023I XAM EXCEPTION ANALYSIS MANAGER IS ACTIVE

Explanation

The Exception Analysis Manager (XAM) completed initialization.

System action

None.

User response

None.

KGW0027E XAM UNABLE TO ACQUIRE TABLE STORAGE: LENGTH=length, ID=table

Explanation

The exception analysis manager (XAM) subtask was unable to allocate length bytes of private storage for table identified by table value.

System action

If the error occurs during initialization, the exception analysis subtask stops processing. Otherwise, XAM continues processing with a decreased ability to compute rates.

User response

Consider increasing the region size of the address space in which XMI is started.

KGW0028E XAM PROGRAM CHECK RECOVERY FOR CICS TG: region

Explanation

The exception analysis manager (XAM) subtask encountered a program. Check in one of its cross-memory mode collection routines while attempting to monitor the CICS® TG denoted by the region value.

System action

The XAM continues processing; no memory dump is produced.

User response

This might be the result of corrupted storage in the CICS TG address space. If problems persist, contact IBM Software Support.

KGW0103I agent UNABLE TO MONITOR CICS TG region: RC=rc

Explanation

OMEGAMON for CICS TG is unable to monitor CICS TG region. The return code rc value indicates the type of error. These are the return codes:

Table 1. Return codes when IBM Z OMEGAMON for CICS TG cannot monitor a CICS region.
Return Code Description
00 CICS TG region is monitored by OMEGAMON for CICS TG.
04 XMI did not register the XCB address.
08 CICS TS or CICS TG region could not be found.
0C Specified region does not belong to CICS TS or CICS TG.
10 CICS TS release is not supported by OMEGAMON for CICS TG.
14 CICS TS or CICS TG job is swapped out.
18 ESTAEX macro failed.
1C Cross memory error occurred during CICS TS or CICS TG validation.
20 CICS TS or CICS TG initialization is not complete.
28 Unable to obtain memory required to build TDA.
2C Session Accounting Area build error occurred.
30 Module load error occurred (see console for message KGW0760E).

System action

No data is collected for all return codes except 00'.

User response

For return code x'04', make sure that XMI (cross memory interface task) is an active subtask of the Tivoli Enterprise Monitoring Agent address space. If problems persist, contact IBM Software Support.

KGW0300I SPI STATISTICS COMPONENT IS ACTIVE

Explanation

The Statistics task is now active.

System action

None.

User response

None.

KGW0301E SPI ANCHOR VALIDATION FAILED

Explanation

The Statistics API subtask has failed to validate component anchor.

System action

The subtask stops processing.

User response

If problem persists, contact IBM Software Support.

KGW0302E SPI STATUS_CLIENT_MANAGER FAILURE. REASON=rc

Explanation

The Statistics API component received a non zero return code when attempting to display component status.

System action

None.

User response

See RKGWSLOG for further messages. If problem persists, contact IBM Software Support.

KGW0303E SPI START_CLIENT_MANAGER FAILURE. REASON=rc

Explanation

The Statistics API component received a non zero return code when attempting to start this component.

System action

The subtask stops processing.

User response

See the RKGWSLOG output for further messages. If attempts to restart the subtask fail, contact IBM Software Support.

KGW0304E SPI MODIFY_CLIENT_MANAGER FAILURE. REASON=rc

Explanation

The Statistics API component received a non zero return code when attempting to process the MODIFY command.

System action

None.

User response

See the RKGWSLOG output for further messages. If problems persist, contact IBM Software Support.

KGW0305E SPI MODIFY ADDICLD INVALID SERVER OR PORT

Explanation

An invalid value was specified for the MODIFY command.

System action

The command is ignored.

User response

Specify a valid value for the ADDICLD keyword and issue the command again.

KGW0306E MODIFY DELICLD INVALID SERVER OR PORT

Explanation

An invalid value was specified for the MODIFY command.

System action

The command is ignored.

User response

Specify a valid value for the DELICLD keyword and issue the command again.

KGW0307E SPI MODIFY CLININV INVALID VALUE

Explanation

An invalid value was specified for the MODIFY command.

System action

The command is ignored.

User response

Specify a valid value for the CLININV keyword and issue the command again.

KGW0308E SPI MODIFY LOOPINV INVALID VALUE

Explanation

An invalid value was specified for the MODIFY command.

System action

The command is ignored.

User response

Specify a valid value for the LOOPINV keyword and issue the command again.

KGW0309E SPI MODIFY CTGTRAC INVALID VALUE

Explanation

An invalid value was specified for the MODIFY command.

System action

The command is ignored.

User response

Specify a valid value for the CTGTRAC keyword and issue the command again.

KGW0310I SPI STOP STATISTICS API CLIENT MANAGER TASK IN PROGRESS

Explanation

The Statistics API component is stopping.

System action

The Statistics API component stops processing.

User response

None.

KGW0311E SPI STOP_CLIENT_MANAGER FAILURE. REASON=rc

Explanation

The Statistics API component received a non zero return code when attempting to stop this component.

System action

The subtask stops processing.

User response

See RKGWSLOG for further messages. If attempting to restart the subtask and restart fails, contact IBM Software Support.

KGW0312I SPI TASK RESOURCE CLEANUP IS COMPLETE

Explanation

All resources owned by the Statistics API component have been successfully released.

System action

None.

User response

None.

KGW0313E SPI INTERFACE TASK HAS ABENDED WITH S0Cx

Explanation

The Statistics API component recovery routine was invoked due to a system abend, where the fourth character x value is a generic substitute for 0-9, A-F.

System action

The component stops processing.

User response

See RKGWSLOG for further messages. If problem persists, contact IBM Software Support.

KGW0601I XTR Transaction Retriever is active.

Explanation

The cross memory CICS TG transaction summarizer subtask is currently active.

System action

The processing continues.

User response

None. Information only message.

KGW0603I XTR Transaction Retriever is terminating.

Explanation

The cross memory CICS TG transaction summarizer subtask is being stopped.

System action

The end of processing continues.

User response

None. Information only message.

KGW0604I XTR Task resource cleanup is complete.

Explanation

Cross memory CICS TG transaction summarizer subtask resource cleanup is complete.

System action

Termination continues.

User response

None. Information only message.

KGW0605E XTR Transaction Retriever is active.

Explanation

The cross memory CICS TG transaction summarizer subtask cannot communicate with XMI.

System action

The transaction summarizer subtask does not start.

User response

Ensure that the OMEGAMON region's Cross memory component or XMI is activated during Agent startup. Verify that the KGW0800I message is issued in the job log for the agent.

KGW0613E XTR ESTAEX macro failure. RC=hhhhhhhh.

Explanation

The recovery environment could not be established during cross memory CICS TG transaction summarizer subtask initialization.

System action

The transaction summarizer subtask does not start.

User response

Contact IBM Software Support.

KGW0623W XTR unable to retrieve data from aaaaaaaa with ASID bbbb.

Explanation

During a retry recovery routine, previously monitored region aaaaaaaa with ASID bbbb was not responding, where:
  • aaaaaaaa is the CICS Transaction Gateway or WebSphere® Application Server jobname.
  • bbbb is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.

System action

The subtask abend continues with percolation.

User response

Contact IBM Software Support with the following information:
  • MCS console log when the incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP, SYSMDUMP)

KGW0760E LOAD OF module FAILED: CODE=abend, REASON=reason

Explanation

The load module module value could not be loaded. The abend value is the abend code, and the reason value indicates the reason code associated with the abend.

System action

The session does not initiate.

User response

Locate the abend code in the IBM System Codes manual, correct the cause of the load failure, and restart the session.

KGW0761W Configuration file processing error: Reason: rrrrrrrr

Explanation

During an OPEN, CLOSE, FIND, or parsing of configuration parameters an error was detected on member KGWSAPIP in the RKANPARU data set.
  • rrrrrrrr is the reason for the error.

System action

Processing continues with default configuration settings. No regions are included for monitoring.

User response

Check the reason code to determine the corrective action.

KGW0762E HOLD COUNT DISPLACEMENT VALIDATION FAILED

Explanation

OMEGAMON was unable to verify the location of the hold count field in the OUCB.

System action

The XMIT stops processing because OMEGAMON components are unable to verify target address spaces if they might be swapped out.

User response

Contact IBM Software Support.

KGW0764E TAI DETECTED AN INCORRECT WORK AREA LENGTH

Explanation

The size of the extended common service area (ECSA) allocated by the TAM module differs from that expected by the TAI module.

System action

The cross memory interface task (XMI) abnormally stops processing with a U0764 ABEND.

User response

Contact IBM Software Support.

KGW0765E TAF DETECTED AN INCORRECT WORK AREA LENGTH

Explanation

The size of the ECSA work area allocated by TAM differs from that expected by module TAF.

System action

The cross memory interface (XMI) abnormally stops processing with a U0765 ABEND.

User response

Contact IBM Software Support.

KGW0766E TAG DETECTED AN INCORRECT WORK AREA LENGTH

Explanation

The size of the ECSA work area allocated by TAM differs from that expected by module TAG.

System action

The cross memory interface task (XMI) abnormally stops processing with a U0766 ABEND.

User response

Contact IBM Software Support.

KGW0800I XMI CROSS MEMORY COMPONENT IS ACTIVE

Explanation

The Cross Memory Interface task is now active.

System action

None.

User response

None.

KGW0808I XMI TASK id ALREADY ACTIVE IN job

Explanation

A second cross memory interface task was started while another one is still active. The XM=nn number is denoted by the id value and the job running the interface task is identified by the job value.

System action

The subtask stops processing.

User response

Either use an XM=nn statement in the configuration file to start another cross memory interface task, or stop the agent address space in which the active task is running.

KGW0810I XMI CROSS MEMORY COMPONENT IS TERMINATING

Explanation

The Cross Memory Interface task is shutting down.

System action

The XMI task stops processing.

User response

None.

KGW0811E XMI CROSS MEMORY COMPONENT HAS ABENDED

Explanation

The cross memory interface task abended.

System action

The XMI task stops processing.

User response

Generate a system memory dump and contact IBM Software Support.

KGW0812I XMI CROSS MEMORY COMPONENT RESOURCE CLEANUP IS COMPLETE

Explanation

The cross memory interface task has completed resource cleanup.

System action

The XMI task stops processing.

User response

None.

KGW0813E subtask ESTAEX MACRO FAILURE. RC=rc

Explanation

The subtask denoted by subtask received a non zero return code from the ESTAEX macro; this is usually caused by a lack of local system queue area (LSQA).

System action

The subtask stops processing.

User response

The return code (rc) for the ESTAEX macro is described in the IBM Macro Reference manual. If the error was caused by a shortage of available storage, decrease the agent address space region size and restart the subtask. If problems persist, contact IBM Software Support.

KGW0818I CLIENT MANAGER TASK TERMINATION COMPLETE

Explanation

The statistics API component stops processing.

System action

None.

User response

None.

KGW0820E SESSION MANAGER TASK ENVIRONMENT SETUP FAILED RESPONSE(EINVAL)

Explanation

The statistics API component failed to establish the session manager task.

System action

The component stops processing.

User response

See RKGWSLOG for further messages. If problems persist, contact IBM Software Support.

KGW0821E SESSION MANAGER TASK ENVIRONMENT SETUP FAILED RESPONSE(EPERM)

Explanation

The statistics API component failed to establish the session manager task.

System action

The component stops processing.

User response

See RKGWSLOG for further messages. If problems persist, contact IBM Software Support.

KGW0828I XMI task with XM=nn already active in UNKNOWN. Reconfigure with different agent XMIT number.

Explanation

The cross memory component for this XM number has already been activated. Concurrent execution of cross memory component with the same XMIT is not permitted.

System action

Only one cross memory component may be active in the agent address space. Therefore, creation of concurrent subtasks is prevented.

User response

None. Information only message.

KGW0946E module(nnn) AND module(nnn) INCOMPATIBLE

Explanation

The versions of the module value and the module it is attempting to load (module) are incompatible.

System action

The loading of the module value and its invoking facility fail.

User response

Verify that the product installation process completed successfully, and that module value is in the Tivoli Enterprise Monitoring Agent library.

KGW0980E SDWA @ address

Explanation

An abend has occurred, and has been trapped by OMEGAMON. The MVS Software Diagnostic Area has been passed to the recovery routine at the location displayed.

System action

The abend activity continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0981E Abend Sxxx Uxxxx has occurred in modname, Section sectname PSW XXXXXXXX XXXXXXXX

Explanation

An abend has occurred, and has been trapped by OMEGAMON. The MVS System and User Completion Codes are displayed along with the name of the Module and control section (CSECT) where the abend occurred and the failing Program Status Word (PSW).

System action

The abend activity continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0982E R0-R7 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

Explanation

An abend occurred, and was trapped by OMEGAMON. The contents of General Purpose Registers 0 through 7 at the time of the abend; this is shown in hexadecimal format.

System action

The abend activity continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0983E R8-R15 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

Explanation

An abend occurred, and was trapped by OMEGAMON. The contents of General Purpose Registers 8 through 15 at the time of the abend; this is shown in hexadecimal format.

System action

The abend activity continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0984E Abend location address - adjacent storage:

Explanation

An abend occurred, and the abend location is shown in the message. The adjacent storage is in the immediate vicinity of the abend location identified in the message.

System action

The abend activity continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0985E aaaaaaaa XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX |cccccccccccccccc|

Explanation

An abend occurred, and was trapped by OMEGAMON. The contents of the 16 bytes at storage location aaaaaaaa are displayed in hexadecimal and character format.

If the storage area for display is not accessible in the agent address space, then this line displays aaaaaaaa Not displayable (Protected) |cccccccccccccccc|.

If the storage area for display is not accessible in the target address space, then this line displays aaaaaaaa Not displayable (TARGET) |cccccccccccccccc|.

System action

The abend recovery continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW0986E Storage addressed by GPR xx

Explanation

An abend occurred, and has been trapped by OMEGAMON. The data at the location addressed by the specified general register are about to be displayed.

System action

The abend recovery continues.

User response

Forward the diagnostic information to IBM Software Support.

KGW9000I ROUTINE rrrrrrrr INITIALIZATION HAS STARTED

Explanation

Routine rrrrrrrr has started initialization of IBM Z OMEGAMON for CICS TG.

System action

None.

User response

None.

KGW9002I IRA REGISTRATION THREAD IS ACTIVE

Explanation

The IBM Z OMEGAMON for CICS TG agent is active.

System action

None.

User response

None.

KGW9003I IRA REGISTRATION THREAD ALREADY ACTIVE

Explanation

An attempt was made to start a another IBM Z OMEGAMON for CICS TG agent.

System action

None.

User response

None.

KGW9004I IRA REGISTRATION THREAD IS NOT ACTIVE

Explanation

An attempt was made to stop the IBM Z OMEGAMON for CICS TG agent thread, but it is not active.

System action

None.

User response

None.

KGW9005I IRA REGISTRATION THREAD IS TERMINATING

Explanation

The IBM Z OMEGAMON for CICS TG agent has received a request to stop processing.

System action

None.

User response

None.

KGW9006E IRA REGISTRATION THREAD IS NOT RESPONDING

Explanation

The IBM Z OMEGAMON for CICS TG agent failed to stop processing within 30 seconds after being notified to stop.

System action

After the IBM Z OMEGAMON for CICS TG agent detects the shutdown request, it stops processing.

User response

None.

KGW9007I MODULE CSECT ADDRESS DATE TIME SYSMOD

Explanation

The message is the header line produced in response to a GW DISPLAY MODULES command.

System action

None.

User response

None.

KGW9008I module csect address date time sysmod

Explanation

This message is generated for each CSECT on the MVS load list in response to a GW DISPLAY MODULES command. The six values displayed in this message include the module, csect, address, date, time, and sysmod associated with each IBM Z OMEGAMON for CICS TG module loaded from STEPLIB.

System action

None.

User response

None.

KGW9009I phase INITIALIZATION HAS ENDED

Explanation

The OMEGAMON for CICS TG initialization phase identified by the phase value has finished.

System action

None.

User response

None.

KGW9010I ATC NO CICS TG MODULES APPEAR ON LOAD LIST

Explanation

The GW DISPLAY MODULES command found no programs on the MVS load list that contained a prefix of KGW.

System action

The command stops processing.

User response

None.

KGW9011E ATC UNABLE TO OBTAIN COMMON WORK AREA STORAGE

Explanation

The OMEGAMON for CICS TG attach controller could not acquire its work area.

System action

None of the OMEGAMON for CICS TG collection routines function.

User response

Increase the amount of memory available to the agent address space. If problems persist, contact IBM Software Support.

KGW9012 pthread_create() error

Explanation

The thread used to monitor active CICS TG regions could not be started.

System action

None of the OMEGAMON for CICS TG reports or situations function.

User response

Inspect the logs for a message that might indicate why the thread failed to start. If problems persist, contact IBM Software Support.

KGW9013E ATC UNABLE TO OBTAIN GWCVT STORAGE

Explanation

The system was unable to allocate the IBM Z OMEGAMON for CICS TG vector table.

System action

None of the OMEGAMON for CICS TG collection routines function.

User response

Increase the amount of memory available to the agent address space. If problems persist, contact IBM Software Support.

KGW9014 pthread_detach() error

Explanation

Unused resources associated with the subnode monitoring thread could not be freed.

System action

Resources remain allocated until IBM Z OMEGAMON for CICS TG stops processing.

User response

None.

KGW9015E ATC entry_point ROUTINE ENTRY POINT NOT FOUND

Explanation

The program used by the attach controller to start subtasks contains an invalid entry point. The entry_point value denotes the entry point that could not be located.

System action

None of the IBM Z OMEGAMON for CICS TG collection routines are functioning.

User response

Contact IBM Software Support.

KGW9016 IRA MANAGER COMMAND UNKNOWN: aaaaaaaa

Explanation

The IRAMAN KGWAGENT modify command directed to the Tivoli Enterprise Monitoring Agent specified an invalid argument as denoted by the aaaaaaaa value.

System action

The command is ignored.

User response

Enter the correct IRAMAN KGWAGENT aaaaaaaa modify command.

KGW9017 IRA MANAGER COMMAND OPERATOR MISSING

Explanation

The IRAMAN KGWAGENT modify command directed to the Tivoli Enterprise Monitoring Agent did not include an argument.

System action

The command is ignored.

User response

Enter the correct IRAMAN KGWAGENT aaaaaaaa modify command.

KGW9018 IRA_Subnode_Register ERROR: RC=aa, Node=bbbbbbbb

Explanation

The function used to register CICS TG bbbbbbbb as online failed with a return code denoted by the aa value.

System action

The CICS TG subnode is not available for situations and reports.

User response

Contact IBM Software Support.

KGW9019I ATC INITIALIZATION RTN DIAGNOSTIC DUMP

Explanation

This message provides a heading for work area displays shown in the RKLVLOG output.

System action

None.

User response

None.

KGW9021 IRA_Subnode_Deregister ERROR: RC=aa, Node=bbbbbbbb

Explanation

The function used to register CICS TG bbbbbbbb as offline failed with a return code denoted by the aa value.

System action

The CICS TG subnode continues to reflect an online status regardless of it actual state.

User response

Contact IBM Software Support.

KGW9022E ATC START COMMAND FAILED. SEE PRIOR MESSAGES

Explanation

The attach controller was unable to start an IBM Z OMEGAMON for CICS TG function.

System action

The function does not initiate.

User response

Consult the RKLVLOG output for additional messages.

KGW9023I ATC COMMAND FORMAT INVALID. SEE PRIOR MESSAGES

Explanation

The attach controller detected a command with invalid syntax.

System action

The command is not processed.

User response

Consult RKLVLOG for additional messages.

KGW9024 IRA_Subnode_SendRequest CALL RETURNED WITH aa

Explanation

The function used to submit CICS TG subnode status has failed with a return code denoted by the aa value.

System action

The CICS TG subnode does not reflect the true state of the region.

User response

Examine the RKLVLOG output for messages that can indicate a problem with the register/deregister functions. If problems persist, contact IBM Software Support.

KGW9025 Agent agent WAS UNABLE TO OBTAIN WORK AREA STORAGE

Explanation

The agent agent value was unable to allocate main memory.

System action

No data is collected.

User response

Consider increasing the agent address space region size.

KGW9026I ATC UNABLE TO DISPLAY CICS TG AGENT DETAIL

Explanation

The GW DISPLAY command was not able to display IBM Z OMEGAMON for CICS TG agent detail information.

System action

None.

User response

None.

KGW9030I ATC PROCESSING THE FOLLOWING COMMAND:

Explanation

This message precedes any command received by the attach controller.

System action

None.

User response

None.

KGW9038E ATC STOP COMMAND FAILED RC=rc

Explanation

A GW STOP command could not be processed.

System action

The task is not stopped.

User response

Contact IBM Software Support.

KGW9039E ATC STOP COMMAND FAILED. INTERNAL ERROR

Explanation

A GW STOP command could not be processed.

System action

The task is not stopped.

User response

Contact IBM Software Support.

KGW9040I ATC STATUS COMMAND BEING PROCESSED

Explanation

A request for status has been received.

System action

None.

User response

None.

KGW9060I ATC THREAD START COMPLETED SUCCESSFULLY

Explanation

An IBM Tivoli Management Services: Engine thread was initiated.

System action

None.

User response

None.

KGW9069E ATC TASK START FAILED ON $DISP ERROR

Explanation

A program could not be initiated due to a dispatch queue problem.

System action

The task does not start.

User response

Contact IBM Software Support.

KGW9070I CICS TG/CICS JOBNAME PARAMETER IS MISSING OR INVALID

Explanation

A GW START, ID=TDA,CICSTG=, or GW START ID=TDA,CICS= command requires a CICS TG or CICS TS job name, but the job name was not specified.

System action

The task does not start.

User response

Ensure that a valid CICS TG or CICS TS name is passed on to the START command.

KGW9198I ATC INITIALIZATION FAILED TO COMPLETE SUCCESSFULLY

Explanation

The IBM Z OMEGAMON for CICS TG attach controller failed to initialize.

System action

None of the IBM Z OMEGAMON for CICS TG collection routines were functioning.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9199I ATC OPERATOR INTERFACE DISABLED, RESTART REQUIRED

Explanation

An error caused the attach controller to fail.

System action

None of the IBM Z OMEGAMON for CICS TG operator commands works under IBM Z OMEGAMON for CICS TG.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9200E ATO OPERATOR INTERFACE NOT INSTALLED

Explanation

The operator interface was not initialized during IBM Tivoli Management Services: Engine initialization.

System action

The command is ignored.

User response

Contact IBM Software Support.

KGW9201E ATO OPERATOR INTERFACE DISPATCH FAILURE

Explanation

The system encountered an internal error when attempting to dispatch the work required to process an operator command.

System action

The command is ignored.

User response

Contact IBM Software Support.

KGW9202E ATO UNABLE TO OBTAIN COMMAND PLIST STORAGE

Explanation

Memory could not be acquired for the operator command parameter list.

System action

The command is ignored.

User response

Increase the amount of storage available to the agent address space.

KGW9300I ATC STATUS – module; entry_point

Explanation

This message displays the entry point of the module module value in response to a GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9311I ATC STATUS – ATC GW$ATCWK: address

Explanation

This message displays the address of the attach parameter list used by the attach controller in response to a GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9312I ATC STATUS – ATC GW$CVT: address

Explanation

This message shows the address of the OMEGAMON for CICS Transaction Gateway CVT when a GW STATUS,DEBUG command is entered.

System action

None.

User response

None.

KGW9313I ATC STATUS – ATC GW$APARM: address

Explanation

This message displays the attach controller anchor control block address in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9314I ATC STATUS – TASK ID: task_id

Explanation

This message displays the task ID of the active task started by the attach controller in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9315I ATC STATUS – TASK: task_id

Explanation

This message displays the task ID for the active task started by the attach controller in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9316I ATC STATUS – APARM; address TYPE: type

Explanation

This message displays the address and type of attach parameter lists created by the attach controller in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9317I ATC STATUS – MODULE: module ENTRY PT: entry_point

Explanation

This message displays the name and entry point of each module loaded by the attach controller in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9318I ATC STATUS – TCB: address EOT ECB: address

Explanation

This message displays the address of each TCB (address value) and its corresponding end of task ECB (address value) created by the attach controller in response to the GW STATUS,DEBUG command.

System action

None.

User response

None.

KGW9398I ATC STATUS – NO TASKS CURRENTLY ACTIVE

Explanation

The attach controller could not find any active tasks in response to a status request.

System action

None.

User response

None.

KGW9399I ATC STATUS – NO TASKS STARTED YET

Explanation

The attach controller has not processed a START command in response to a status request.

System action

None.

User response

None.

KGW9400I ATC req_type – SPI SUBTASK NOT STARTED YET

Explanation

A GW MODIFY ID=SPI or GW STATUS ID=SPI command was issued, but the SPI subtask has not been started.

System action

None.

User response

None.

KGW9401I ATC MODIFY – INVALID KEYWORD SPECIFIED

Explanation

The attach controller has processed a MODIFY ID=SPI command, but an invalid keyword was detected.

System action

The command stops processing.

User response

See the CICS TG documentation for available keywords for this command.

KGW9402I ATC MODIFY – INVALID SERVER NAME

Explanation

The attach controller has processed a MODIFY ID=SPI command, but no server name was specified.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9403I ATC MODIFY – INVALID PORT NUMBER

Explanation

The attach controller has processed a MODIFY ID=SPI command, but an invalid port number was detected.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9405I ATC MODIFY – PORT NUMBER NOT NUMERIC

Explanation

The attach controller has processed a MODIFY ID=SPI command, but the specified port number was not numeric.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9406I ATC MODIFY – INTERVAL VALUE NOT NUMERIC

Explanation

The attach controller has processed a MODIFY ID=SPI command, but the specified interval value was not numeric.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9407I ATC MODIFY – INTERVAL VALUE NOT SPECIFIED

Explanation

The attach controller has processed a MODIFY ID=SPI command, but the interval value was not specified.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9408I ATC MODIFY – INTERVAL OF ZERO NOT VALID

Explanation

The attach controller has processed a MODIFY ID=SPI command that specifies a zero interval.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9409I ATC MODIFY – TRACE OPTION NOT SPECIFIED

Explanation

The attach controller has processed a MODIFY ID=SPI,CTGTRAC= command, but no tracing option was specified.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9410I ATC MODIFY – TRACE LEVEL NOT NUMERIC

Explanation

The attach controller has processed a MODIFY ID=SPI,CTGTRAC= command, but the trace level was not numeric.

System action

The command stops processing.

User response

See the CICS TG documentation for the correct syntax.

KGW9411I ATC MODIFY – CICS TG STATISTICS API DLL TRACING REQUESTED FOR ALL SERVERS

Explanation

The attach controller has processed a MODIFY ID=SPI,CTGTRAC= command to activate the CICS TG API DLL trace for all monitored daemons.

System action

The command is processed.

User response

To avoid performance degradation, consider enabling the trace for the specific gateway daemon; this can be achieved by adding the CICS TG job name as the third keyword to the MODIFY command.

For example: 
GW MODIFY ID=SPI,CTGTRAC=(n,jjjjjjjj)
Where n is the trace level and jjjjjjjj is the name of the CICS TG daemon.

KGW9700I ATI SUBTASK INITIALIZATION TDA NOT FOUND

Explanation

The system was unable to locate the target descriptor area used to monitor a CICS TG region.

System action

The task does not start.

User response

Contact IBM Software Support.

KGW9701E ATI SUBTASK MODULE E.P. MISSING OR INVALID

Explanation

The program entry point of a module to be started is zero.

System action

The task does not start.

User response

Contact IBM Software Support.

KGW9889I ATC S0C4 MESSAGES ARE ALREADY SUPPRESSED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has received a request to suppress S0C4 log messages, but message suppression is already enabled.

System action

The GW SUPRS0C4 command is ignored.

User response

None.

KGW9890I ATC S0C4 MESSAGE SUPPRESSION ACTIVATED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has acknowledged a request to suppress S0C4 log messages.

System action

Messages are not written to the RKLVLOG when a CICS TG agent abnormally ends with a S0C4 ABEND code.

User response

None.

KGW9891I ATC S0C4 MESSAGE SUPPRESSION NOT ACTIVE

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller received a request to suppress S0C4 log messages, but message suppression was never enabled.

System action

The GW SUPRS0C4 command is ignored.

User response

None.

KGW9892I ATC S0C4 MESSAGE SUPPRESSION DEACTIVATED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has acknowledged a request to stop suppressing S0C4 log messages.

System action

A message is written to the RKLVLOG when CICS TG agents experience S0C4 ABEND codes.

User response

None.

KGW9893I ATC INVALID S0C4 MESSAGE OPTION SPECIFIED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller did not recognize the S0C4 log message suppression option specified in the GW SUPRS0C4 command.

System action

The GW SUPRS0C4 command is ignored.

User response

Reenter the command with an ON or OFF option.

KGW9900I ATC TERMINATION HAS STARTED

Explanation

The OMEGAMON for CICS Transaction Gateway termination routine now has control.

System action

None.

User response

None.

KGW9921I ATC START REJECTED. TASK ID=task_id CURRENTLY RUNNING. ONLY ONE COPY PERMITTED AT A TIME

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller found an active copy of the task_id value running in the agent address space.

System action

The START command is ignored.

User response

None.

KGW9922E ATC UNABLE TO ATTACH PARAMETER LIST STORAGE

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller could not acquire memory for the ATTACH macro.

System action

The task does not start.

User response

Increase the amount of memory available to the agent address space. If problems persist, contact IBM Software Support.

KGW9924I ATC FREEMAIN FAILURE FOR IBM Tivoli Management Services: Engine STORAGE

Explanation

The system was unable to execute a $FMEM request to release IBM Tivoli Management Services: Engine managed storage.

System action

None.

User response

None.

KGW9925I ATC TASK-START RESOURCE ALREADY FREED

Explanation

The system has released resources associated with a task.

System action

None.

User response

None.

KGW9941I function MVS VERSION UNKNOWN

Explanation

The subroutine used to determine the operating system release detected an unsupported release of MVS when called by the function value.

System action

The function identified by the function value does not start.

User response

Contact IBM Software Support.

KGW9942I function GWVRSN FAILURE, R1=r1, R15=r15

Explanation

The subroutine used to determine the operating system release failed with the r1 value when called by the function value.

System action

The task does not start.

User response

Contact IBM Software Support.

KGW9943I ATC NO TABLE ENTRY FOR task

Explanation

The attach controller was unable to locate the task value.

System action

The task does not start.

User response

Verify that you are specifying the correct task name (SPI, XMI, XAM, or XTR). If the problem persists, contact IBM Software Support.

KGW9945I ATC $LOAD ERROR FOR MODULE: module

Explanation

The IBM Tivoli Management Services: Engine service used to load a program failed; the module value is found.

System action

The task is not started.

User response

Contact IBM Software Support.

KGW9947E ATC ID= PARM NOT SPECIFIED OR INVALID

Explanation

The ID keyword on the GW command specifies an incorrect value.

System action

The task does not start.

User response

Correct the task name on the ID parameter and reenter the command.

KGW9948E ATC ID= PARM LENGTH ERROR

Explanation

The ID keyword on the GW command specifies an incorrect value.

System action

The task does not start.

User response

Correct the task name on the ID parameter and reenter the command.

KGW9949E ATC INVALID HEADER FORMAT IN program

Explanation

The internal module header in program program cannot be validated.

System action

The task does not start.

User response

Contact IBM Software Support.

KGW9950I ATC HAS LOADED MODULE: program

Explanation

The attached controller loaded program program.

System action

None.

User response

None.

KGW9989I ATC TRACING HAS BEEN ACTIVATED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has acknowledged a request to turn on trace.

System action

Tracing of OMEGAMON for CICS Transaction Gateway is initiated.

User response

None.

KGW9990I ATC INITIALIZATION HAS ISSUED ADDITIONAL ERROR MESSAGES

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has failed to initialize.

System action

None of the OMEGAMON for CICS Transaction Gateway collection routines function.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9991I ATC TRACING IS NOT CURRENTLY ACTIVE

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller received a request to turn tracing off but tracing was never turned on originally.

System action

The GW TRACE command is ignored.

User response

None.

KGW9992I ATC TRACING HAS BEEN DEACTIVATED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has acknowledged a request to turn off tracing.

System action

Tracing of OMEGAMON for CICS Transaction Gateway discontinues.

User response

None.

KGW9993E ATC INVALID TRACE OPTION SPECIFIED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller did not recognize the tracing option specified in the GW TRACE command.

System action

The GW TRACE command is ignored.

User response

Reenter the command with an ON or OFF option.

KGW9994I ATC TRACING IS ALREADY ACTIVE

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has received a request to activate tracing, but tracing is already active.

System action

The GW TRACE command is ignored.

User response

None.

KGW9995I ATC TEST REJECTED, XDC(Y) NOT IN KDSSYSIN

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has received a TEST command but found that the XDC environment had not been established under the Engine.

System action

The GW TEST command is ignored

User response

Place an XDC(Y) control card in the KDSSYSIN member of TLVPARM and restart the Tivoli Enterprise Monitoring Server address space.

KGW9996I ATC NOW INOPERATIVE. RESTART REQUIRED.

Explanation

In order for OMEGAMON for CICS Transaction Gateway to collect data, the error that caused the attach controller to fail must be corrected and the agent address space restarted.

System action

This message is for informational purposes only.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9997E ATC INITIALIZATION CANNOT BE COMPLETED

Explanation

An error caused the attach controller to fail.

System action

None of the OMEGAMON for CICS Transaction Gateway collection routines function.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9998I ATC OPERATOR INTERFACE IS NOW DISABLED

Explanation

An error caused the attach controller to fail.

System action

None of the OMEGAMON for CICS Transaction Gateway operator commands work under the Tivoli Enterprise Monitoring Agent.

User response

Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact IBM Software Support.

KGW9999I ATC TERMINATION HAS ENDED

Explanation

The OMEGAMON for CICS Transaction Gateway attach controller has terminated.

System action

None.

User response

None.

KGWAG0100E cccccccc Extract transaction summary records failed in routine cccccccc with RC=nn.

Explanation

A failure has occurred during extraction of the transaction summary records.

System action

Extraction of transaction summary records for the monitored region is bypassed. Operation continues with the next monitored region.

User response

Contact IBM Software Support.

KGWAG0101E IRA collection environment error routine=cccccccc.cccccccc reason=cccccccc.

Explanation

A general environment error occurred during Intelligent Remote Agent processing.

System action

Operation continues with the next monitored region if appropriate.

User response

Contact IBM Software Support.

KGWAG0102E pppppppp Session locate failed for jjjjjjjj ASID hhhh with RC=xx

Explanation

The monitored region's session locate operation failed upon return from KGWSAPI Table Services.

Module pppppppp failed to locate address space jjjjjjjj with ASID hhhh in the session table. Return code xx can have one of the following values:
  • 04 = Address space jjjjjjjj with ASID hhhh was not in the session table.
  • 08 = The request failed.
  • 0C = the request abended.

System action

Operation continues with the next monitored region.

User response

Return code 04 might occur while a monitored region is being initialized. If this condition continues, contact IBM Software Support. If the return code is 08 or 0C, contact IBM Software Support.

KGWAG0103E cccccccc Active Transaction AR collector failed in routine cccccccc with RC=nn.

Explanation

A failure has occurred upon return from the active transaction AR collector.

System action

Extraction of the active transaction information for the monitored region is bypassed. Operation continues with the next monitored region.

User response

Contact IBM Software Support.

KGWDIO00E Data set I/O error detected - SYNAD message:

Explanation

During a READ operation, a permanent I/O error was detected on the configuration source member KGWSAPIP in the RKANPARU data set.

System action

Processing continues with default configuration settings. No regions are included for monitoring.

User response

The SYNAD message buffer describes the source of the problem. Take the appropriate action to ensure the success of I/O operations on the data set.

KGWDMP01I Dump of area at x"xxxxxxxx" with length x"nnnn" follows.

Explanation

When preceded by the error message KGWTMI09E, this message displays a memory dump of a work area, which belongs to the home level name and token retriever routine (NTR) for OMEGAMON. If preceded by the warning message KGWXTR05W, this message displays the contents of a transaction record and the first flow of that transaction.

System action

None. Normal operation continues.

User response

For possible actions, refer to the text for message KGWTMI09E or KGWXTR05W.

KGWDMP09I End of dump at x"xxxxxxxx" with length x"nnnn".

Explanation

This indicates the end of display for a memory location being dumped.

System action

None. Normal operation continues.

User response

None. Information only message.

KGWNTR09E cccccccc received return codes hhhhhhhh, SYNCHCOMP hhhhhhhh, SYNCHCODE hhhhhhhh, SYNCHRSN hhhhhhhh from IEAMSCHD.

Explanation

IEAMSCHD macro failure.

System action

The Agent address space was not able to retrieve the home level name and token, which may have been previously established through the OMEGAMON's user exit in the monitored region.

User response

Ensure that each CICS TG monitored region has been correctly configured to enable the monitoring user exits.

KGWRDR01I RDR for session ssssssss ASID aaaa at x"xxxxxxxx_xxxxxxxx".

Explanation

The Raw Data Repository for session ssssssss with ASID aaaa is located at address xxxxxxxx_xxxxxxxx, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • xxxxxxxx_xxxxxxxx is the address of the Raw Data Repository in the monitored region.

System action

None. Informational only message.

User response

None. Informational only message.

KGWRDR02I module The Raw Data Repository (RDR) for session jjjjjjjj is no longer available.

Explanation

The Raw Data Repository for the jjjjjjjj monitored region is no longer available, possibly due to an error situation in the monitored region. The issuing module is module.

System action

None. Information only message.

User response

Review messages in the monitored region to determine the source of this condition. A likely reason is a mismatch between the components of the transaction monitoring exit, described by message KGWRM0039E.

KGWRTA00I RTA control area for jjjjjjjj has been allocated at xxxxxxxx_xxxxxxxx.

Explanation

The RTA control area for the jjjjjjjj monitored region was allocated at the address xxxxxxxx_xxxxxxxx.

System action

None. Information only message.

User response

None. Information only message.

KGWRTA01E Return code=rrrrrrrr and reason code=ssssssss received from IARV64 REQUEST=GETSTOR for gggggggg segments.

Explanation

A request for storage higher than the bar was unsuccessful. This could be due to a site limitation on the amount of storage that can be allocated more than the bar.

System action

Cross memory CICS TG transaction summarizer subtask is not activated.

User response

To accommodate the number of megabytes segments requested, increase the MEMLIMIT= JCL parameter for the job and/or the SMFPRMxx specification in SYS1.PARMLIB.

KGWRTA02E Return code=rrrrrrrr received from qqqqqqqq request.

Explanation

A request to expand a cell or expand an extent more than the bar was unsuccessful.

System action

Cross memory CICS TG transaction summarizer subtask is not activated.

User response

To accommodate the number of megabytes segments requested, increase the MEMLIMIT= JCL parameter for the job and/or the SMFPRMxx specification in SYS1.PARMLIB.

KGWSPI00I Client Manager Status is Terminating or Client Manager Status is Active

Explanation

SAPI Client Manager Information message.

System action

System is either terminating or is active.

User response

None. Information only message.

KGWSPI01I Server=ssssssss, Bind=bbbbbbbb , Port=pppp Added to Included Sessions

Explanation

A request to INCLUDE CICS TG server sssssssss with port pppp and Bind bbbbbbbb has been serviced. Only the first 32 characters of the Bind address are displayed.

System action

Request is included.

User response

None. Information only message.

KGWSPI02I Server=ssssssss Port=pppp Deleted from Included Sessions

Explanation

A request to DELETE CICS TG server ssssssss with port pppp has been serviced.

System action

Request deletes server from included sessions.

User response

None. Information only message.

KGWSPI03I Client=cccccccc SAPI Session aaaaaaaaaaa with CICS TG Server=ssssssss Port=pppp Bind=bbbbbbb Token=xtttttttt

Explanation

The status request information for the SAPI connection. These are the values:
  • cccccccc is the OMEGAMON for CICS TG Client name
  • aaaaaaaaaaa states if the connection is established or terminated
  • ssssssss is the CICS TG SAPI Server name
  • pppp is the CICS TG SAPI Server Port number
  • bbbbbbb is the CICS TG SAPI Bind address.
  • tttttttt is 4 hex bytes of the CICS TG statistics API token.

The status request information for SAPI connection, where only the first 16 characters of the Bind address are displayed.

System action

System shows status information.

User response

None. Information only message.

KGWSPI04I dddddddd(mmmmmmmm) not accessible, default options will be used.

Explanation

The parameter member used to determine:
  • SAPI_CLIENT_INTERVAL
  • SAPI_CLIENT_LOOP_DETECT
  • SAPI_CLIENT_SESSIONS
  • SAPI_CLIENT_SESSIONS_TIMEOUT
  • SAPI_CLIENT_CLIENT_MESSAGES
Could not be opened where dddddddd is the DDName and mmmmmmmm is a member of the dataset in KGWSAPIP. Execution will continue using default settings.

System action

System uses default configuration

User response

None. Information only message.

KGWSPI05I Anchor_Name=aaaaaaaaaaaaaaaa Anchor_Token= tttttttttttttttt

Explanation

Status of the client's identifiers where:
  • Anchor_Name is the Name of the token of the IBM Z OMEGAMON for CICS TG Client.
  • Anchor_Token is the Contents of the token that identifies the IBM Z OMEGAMON for CICS TG Client.

System action

Status is shown.

User response

None. Information only message.

KGWSPI06I Client_Interval=iiiii seconds Client_Loop_Detect= lllll

Explanation

Value of the interval and loop detection limit where:
  • iiiii is the Value of the interval at which the CICS TG statistics API are interrogated.
  • lllll is the Number of seconds that triggers loop recovery.

System action

System shows interval and seconds.

User response

None. Information only message.

KGWSPI07I Maximum Sessions=sssss

Explanation

Maximum number of sessions to monitor CICS TG, where sssss is the number of sessions specified.

System action

System shows maximum sessions.

User response

None. Information only message.

KGWSPI08I Include Server=ssssssss Port=pppp Bind=bbbbbbbb

Explanation

A request to include CICS TG server ssssssss with port pppp and bind bbbbbbbb was detected. The include request can be issued with a parameter at initialization time, or through a MODIFY command.
  • ssssssss is the CICS TG server name.
  • pppp is the CICS TG statistics API port number.
  • bbbbbbbb is the CICS TG bind address as specified in the CICS TG configuration file (ctg.ini). If omitted, LOCALHOST is assumed.

System action

System processes request.

User response

None. Information only message.

KGWSPI09I Session Name=ssssssss ASID=aaaa Port Number=ppppp Sysname=yyyy Jobname=jjjjjjjj Token=x"tttttttt" Status=uuuuuuuu

Explanation

This is an informational message. It displays the attributes of a session, where:
  • ssssssss is the CICS TG server name.
  • aaaa is the address space identification number, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number.
  • yyyy is the SMF ID of the z/OS® system where the CICS TG server runs.
  • jjjjjjjj is the JOBNAME of the CICS TG server.
  • tttttttt is the token that identifies the connections between IBM Z OMEGAMON for CICS TG and the CICS TG server.
  • uuuuuuuu is the status of the connection, which can be:
    • Active
    • Terminating
    • Pending
    • Unknown

System action

System displays the session attributes.

User response

None. Informational only message.

KGWSPI10I Server=ssssssss ASID=aaaa Port=ppppp Deleted from monitored sessions

Explanation

A request to DELETE CICS TG Server ssssssss with port ppppp has been serviced, where:
  • ssssssss is the CICS TG Server name.
  • aaaa is the address space identification number, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number.

System action

System deletes the specified monitored session.

User response

None. Informational only message.

KGWSPI20E Client=cccccccc SAPI session with CICS TG Server ssssssss number of CICS TS regions APPLIDS nnnn exceeds maximum of mmmm

Explanation

The number of CICS APPLIDS returned by the CICS TG statistics API exceeds the storage capacity of the requesting client. Processing continues, and the excess APPLIDS are discarded where:
  • cccccccc is the OMEGAMON for CICS TG Client Name.
  • ssssssss is the CICS TG Server name.
  • nnnn is the number of CICS TS regions APPLIDS (CS_LCLIST).
  • mmmm is the maximum capacity of the client to store APPLIDS.

System action

The system discards the excess APPLIDS.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI21E Failed to connect to CICS TG Server=ssssssss Port=pppp Bind= bbbbbbb Received Return Code=x"rrrrrrrr".

Explanation

The CICS TG statistics API server returned a non zero code in response to the openGatewayConnection request. No statistics are available for the server. These are the values:
  • ssssssss is the CICS TG SAPI server name.
  • pppp is the CICS TG statistics API port number.
  • bbbbbbb is the CICS TG Bind address.
  • rrrrrrrr is the return code received from the server.

Only the first 16 characters of the Bind address are displayed.

System action

System returns a non-zero code.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • RKGWSLOG contents when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI22E Protocol mismatch CICS TG Server=ssssssss Port=pppp Protocol version=vvvvvvv Client=ooooooo Protocol Version=mmmmmmm.

Explanation

The CICS TG statistics API server returned a protocol version that is incompatible with the IBM Z OMEGAMON for CICS TG version. No statistics are available for the server where:
  • ssssssss is the CICS TG SAPI server name
  • pppp is the CICS TG statistics API port number
  • vvvvvvv is the Protocol Version of the CICS TG server
  • oooooooo is the name of the IBM Z OMEGAMON for CICS TG client attempting to connect to the CICS TG server
  • vvvvvvv is the Protocol Version of the OMEGAMON® for CICS Client

System action

System does not produce statistics for the server.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • RKGWSLOG contents when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI23I Trace level n has been ttttttt for Server=ssssssss Port=pppp.

Explanation

IBM Z OMEGAMON for CICS Transaction Gateway has requested that the CICS TG statistics API at server ssssssss port pppp start tracing at level n or that tracing be stopped at CICS TG server ssssssss port number pppp.

System action

System either stops or starts a trace, tttttttt.

User response

None. This is an information message.

KGWSPI24W Unexpected return code=xrrrrrrrr and reason code=xeeeeeeee received for function=xff object=xoo Server=ssssssss port=pppp.

Explanation

A non zero return and reason code were received when attempting to update the statistics repository for a CICS TG server where:
  • rrrrrrrr is the return code from object manager
  • eeeeeeee is the reason code from object manager
  • ff is the function
  • oo is the type of object
  • pppp is the CICS TG statistics API port number

System action

Statistical information for the server are not updated.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • RKGWSLOG contents when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI25E Unexpected return code=x"rrrrrrrr" received from StatsAPI function=fffffffffffffffffffffffff server=sssssssss port=pppp.

Explanation

A request issued to the CICS TG StatsAPI was unsuccessful, and returned a non-zero return code where:
  • rrrrrrrr is the return code from StatsAPI server
  • ffffffff is the function attempted
  • ssssssss is the CICS TG SAPI server name
  • pppp is the CICS TG statistics API port number

System action

System returns a non-zero code.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • RKGWSLOG contents when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI26E The hostname was not resolved to a valid IP address Return Code 132. Bind=bbbbbbbb

Explanation

The CICS TG statistics API server returned code -132 was issued in response to the openRemoteGatewayConnection request. No statistics are available for the server. The bbbbbbb value is the Bind address. Only the first 32 characters of the Bind address are printed.

System action

The system returned a CICS TG statistics API server return code -132 in response to the openRemoteGatewayConnection request.

User response

Correct the hostname or IP address and restart the agent.

KGWSPI27E The connection attempt was refused, Return Code -135. Bind=bbbbbbbb

Explanation

The CICS TG statistics API server returned code -135 was issued in response to the openRemoteGatewayConnection request. No statistics are available for the server. The bbbbbbb value is the Bind address. Only the first 32 characters of the Bind address are printed.

System action

The system returned a CICS TG statistics API server return code -135 in response to the openRemoteGatewayConnection request.

User response

Correct the hostname or IP address and restart the agent.

KGWSPI39I SESSION table element added for Server=ssssssss ASID=aaaa Port=ppppp Table=tttttttt CSECT=cccccccc.

Explanation

A session monitored for statistics or transaction activity was added to the SESSION table, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number, or zeros for a WebSphere Application Server.
  • tttttttt is the name of the table.
  • cccccccc is the name of the CSECT issuing the message.

System action

Processing continues.

User response

None. Informational only message.

KGWSPI40I Server=ssssssss ASID=x aaaa may be swapped out or terminating. System=x yyyy User=x uuuu Reason=x rrrrrrrr

Explanation

A monitored address space may be swapped out or terminating, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • yyyy is the System ABEND Code in hexadecimal format.
  • uuuu is the user ABEND Code in hexadecimal format.
  • rrrrrrrr is the ABEND Reason Code in hexadecimal format.

System action

Processing continues.

User response

None. Informational only message.

KGWSPI73E KGWSAPI Get Keyed Sample Request Failed, routine=aaaaaaaa.bbbbbbbb, RC=xxxxxxxx RS=yyyyyyyy.

Explanation

An attempt to obtain CICS TG statistics has failed. The aaaaaaaa.bbbbbbbb value is the name and label of the failed routine. The xxxxxxxx value is the return code received from the Statistics API. The yyyyyyyy value is the reason code received from the Statistics API.

System action

The current operation failed; attempt subsequent operations normally.

User response

If the problem persists, contact IBM Software Support.

KGWSPI76W KGWSAPI Sample Request Failed routine=cccccccc.

Explanation

An attempt to obtain CICS TG statistics failed with routine cccccccc was not successful.

System action

The current operation failed; the system will attempt subsequent operations normally.

User response

If the problem persists, contact IBM Software Support.

KGWSPI77I SAPI Object Element data.

Explanation

Prints the content of a SAPI Object Element in memory dump format. Each line starts with an offset followed by hexadecimal data and ends with data in character format.

System action

System prints content in memory dump format.

User response

None. This is an informational message.

KGWSPI78I Unable to locate TDA/CET for cccccccc routine=rrrrrrrr

Explanation

The Target Descriptor Area (TDA) or the Exception Table entry for a CICS TG region (CET) cannot be located. This condition occurs when a previously monitored CICS TG region is no longer active. where:
  • cccccccc is the name of the CICS TG region (Gateway daemon or WebSphere Application Server).
  • rrrrrrrr is the name of the routine where this message was issued.

System action

System continues processing, but the CICS TG region identified by the message is no longer monitored.

User response

None. This is an information message.

KGWSPI79I Client Manager Task termination in progress.

Explanation

The Client Manager Task is terminating. This is due to a shutdown request, or an error condition. If an error condition, check for error messages prior to KGWSPI79I.

System action

System shuts down the client manager task.

User response

None. This is an information message.

KGWSPI81E 1-115 bytes CTG SAPI Error Message text

Explanation

SAPI error message produced.

System action

Error message is displayed as text.

User response

None. Error information message.

KGWSPI82E Failed to disconnect from CICS TG Server=ssssssss Port=pppp Received Return Code=x"rrrrrrrr"

Explanation

The CICS TG statistics API server returned a non-zero code in response to the closeGatewayConnection request where:
  • ssssssss displays a return code from StatsAPI server name
  • pppp is the CICS TG statistics API port number
  • rrrrrrrr is the return code received from the server
Session termination continues.

System action

System continues shutting down session.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • RKGWSLOG contents when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI83W cccccccc parameter unknown <text>

Explanation

Unknown keyword parameter specified, where cccccccc is the Parmfile name and <text> describes the keyword specification record.

System action

The specification is ignored.

User response

None. Keyword specification ignored.

KGWSPI84E CEEPIPI cccccccccccccccccccc request failed rc=x"xxxx " subretc=x"xxxx" subrsnc=x"xxxx" subfbc=x"xxxxxxxxxxxxxxxxxxxx"

Explanation

An LE Environment Request failed. Processing stops where:
  • ccccccc is the request description
  • rc is the return code from request
  • retc is the LE environment return code
  • rsnc is the LE environment reason code
  • fbc is the LE environment feedback code

System action

The processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI85E ccccc error processing ddname CSECT=cccccccc

Explanation

Error occurred processing a DDNAME file where:
  • ccccccc is the error type OPEN|CLOSE|READ|WRITE|LOCATE.
  • ddname is the name of the allocated file.
  • CSECT is where the CSECT error occurred.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI86E cccccccc entry point failed EP=cccccccc CSECT=cccccccc rc=x"hhhh"

Explanation

Module Loader system service failed, where:
  • cccccccc is the service request
    • LOAD
    • IDENTIFY
  • EP is the Entry Point name
  • CSECT is the name of the CSECT issuing message
  • rc is the return code from service

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI87E Name Token Service Failed Request=cccccccc CSECT=cccccccc rc=x"hhhh"

Explanation

A Name Token Service Request failed where:
  • Request is the Name Token Service Request Type.
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from Name Token Service.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI88E Unable to Allocate Table=cccccccc CSECT=cccccccc rc=x"hhhh" rs=x"hhhh"

Explanation

Unable to Allocate Table Resources where:
  • Table is the name of Table (SESSION|INCLUDE|RESGRPID|STATID).
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from the SESSION/INCLUDE/RESGRPID/STATID table allocate request.
  • rs is the reason code from the SESSION/INCLUDE/RESGRPID/STATID table allocate request.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWSPI89S Unable to Deallocate Table=cccccccc CSECT=cccccccc rc=x"hhhh" rs=x"hhhh"

Explanation

Unable to Deallocate Table Resources where:
  • Table is the name of Table (SESSION|INCLUDE|RESGRPID|STATID).
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from the deallocate request.
  • rs is the reason code from the table deallocate request.

System action

System cannot deallocate the table resources.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWSPI90W Locate failed for server=ssssssss ASID=aaaa Port=ppppp Table=tttttttt CSECT=cccccccc rc=x"hhhh" rs=x"yyyy"

Explanation

The LOCATE_ELEMENT function of the KGWSAPI_TABLE_SERVICES failed, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number, or zeros for a WebSphere Application Server.
  • tttttttt is the name of one of the following tables where the data is stored:
    • SESSION
    • INCLUDE
    • RESGRPID
    • RESID
    • STATID
  • cccccccc is the name of the CSECT issuing the message.
  • hhhh is the return code from the locate request in hexadecimal format.
  • yyyy is the reason code from the locate request in hexadecimal format.

System action

System will no longer monitor the region identified by ASID.

User response

Contact IBM Software Support with the following information:
  • MCS console log when the incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP, SYSMDUMP)

KGWSPI91W Delete failed for server=ssssssss ASID=aaaa Port=ppppp Table=tttttttt CSECT=cccccccc rc=x"hhhh" rs=x"yyyy"

Explanation

The DELETE_ELEMENT function of the KGWSAPI_TABLE_SERVICES failed, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number, or zeros for a WebSphere Application Server.
  • tttttttt is the name of one of the following tables where the data is stored:
    • SESSION
    • INCLUDE
    • RESGRPID
    • RESID
    • STATID
  • cccccccc is the name of the CSECT issuing the message.
  • hhhh is the return code from the delete request in hexadecimal format.
  • yyyy is the reason code from the delete request in hexadecimal format.

System action

System will no longer monitor the region identified by ASID.

User response

Contact IBM Software Support with the following information:
  • MCS console log when the incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP, SYSMDUMP)

KGWSPI92W Add failed for server=ssssssss ASID=aaaa Port=ppppp Table=tttttttt CSECT=cccccccc rc=x"hhhh" rs=x"yyyy"

Explanation

The ADD_ELEMENT function of the KGWSAPI_TABLE_SERVICES failed, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number, or zeros for a WebSphere Application Server.
  • tttttttt is the name of one of the following tables where the data is stored:
    • SESSION
    • INCLUDE
    • RESGRPID
    • RESID
    • STATID
  • cccccccc is the name of the CSECT issuing the message.
  • hhhh is the return code from the add request in hexadecimal format.
  • yyyy is the reason code from the add request in hexadecimal format.

System action

System will no longer monitor the region identified by ASID.

User response

Contact IBM Software Support with the following information:
  • MCS console log when the incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP, SYSMDUMP)

KGWSPI93I SESSION table element deleted for Server=ssssssss ASID=aaaa Port=ppppp Table=SESSION CSECT=cccccccc

Explanation

The region, identified by ASID, was successfully removed from being monitored. Where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • ppppp is the CICS TG statistics API port number, or zeros for a WebSphere Application Server.
  • cccccccc is the name of the CSECT issuing the message.

System action

System continues to process, but the region identified by ASID is no longer monitored.

User response

None. Informational only message.

KGWSPI94E CICS TG discovery failed for Server=cccccccc CSECT=cccccccc rc=x"hhhh" rs=x"hhhh"

Explanation

Gateway daemon discovery failed where:
  • Server is the name of Server or ALL.
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from CICS TG discovery routine.
  • rs is the reason code from CICS TG discovery routine.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWSPI95E ALESERV failed Request=cccccccc CSECT=cccccccc rc=x"hhhh"

Explanation

An ALESERV request failed, where:
  • Request is the ALESERV Request type.
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from ALESERV.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWSPI97E ESTAEX Recovery entered CSECT=cccccccc System=x"hhhh" User=x"hhhh" Reason=x"hhhhhhhh"

Explanation

An abend was detected while recovery was active. The following information is provided:
  • CSECT is the name of the CSECT issuing message
  • System is the system ABEND Code
  • User is the user ABEND Code
  • Reason is the ABEND Reason Code

System action

ESTAE recovery activates.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWSPI98E SDUMPX Failed during Recovery entered CSECT=cccccccc rc=x"hh" rs=x"hh" SVCDUMP Diagnostics unavailable.

Explanation

SDUMPX Failed during recovery processing, where:
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from SDUMPX.
  • rs is the reason code from SDUMPX.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWSPI99E ESTAEX Failed CSECT=cccccccc rc=x"hhhh" .

Explanation

Unable to set ESTAEX Recovery Environment, where:
  • CSECT is the name of the CSECT issuing message.
  • rc is the return code from ESTAEX.

System action

Processing stops.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced

KGWXTR01E fff failed for cccccccc CtgCorr=x"hhhhhhhhh" Topology=x"hhhh", Table=cccccccc, rc=x"hhhh" rs=x"hhhh" CSECT=cccccccc.

Explanation

CICS TG is unable to add an element to the named table.

System action

None. Normal operation continues.

User response

Contact IBM Software Support with the following:
  • MCS console log when incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP,SYSMDUMP)

KGWXTR02I Marker in RDR for session ssssssss ASID aaaa reset to nnnn.

Explanation

The Raw Data Repository for session ssssssss ASID aaaa was successfully reset to match this agent's XM number, where:
  • ssssssss is the CICS Transaction Gateway or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • nnnn is the cross memory number, in the format XMnn, where nn is the number specified in the START ID=XMI,XM=nn command for this agent.

System action

None. Informational only message.

User response

None. Informational only message.

KGWXTR03W Unable to retrieve data from INCLUDEd session ssssssss ASID aaaa marked with xxxx. This agent is using yyyy.

Explanation

The Raw Data Repository for session ssssssss with ASID aaaa is marked with the XM number xxxx, but this agent has been started with XM number yyyy, where:
  • ssssssss is the CICS Transaction Gateway (CICS TG) or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.
  • xxxx is the XMnn mark in the session's RDR.
  • yyyy is the cross memory number, in the format XMnn, where nn is the number specified in the START ID=XMI,XM=nn command for this agent.

System action

No FLOW data is retrieved.

User response

Verify that a single CICS TG or WebSphere Application Server region is not monitored by multiple OMEGAMON agents.

KGWXTR05W Transaction with nnnn flows from session ssssssss ASID aaaa exceeds storage capacity.

Explanation

A transaction with nnnn flows cannot be processed in its entirety. Only the first 54 flows are processed. Where:
  • nnnn is the number of flows in the transaction.
  • ssssssss is the CICS Transaction Gateway (CICS TG) or WebSphere Application Server jobname.
  • aaaa is the CICS Transaction Gateway or WebSphere Application Server address space ID, in hexadecimal format.

System action

Processing continues. The excess flow records are discarded. A memory dump of the transaction data is produced following this message.

User response

Contact IBM Software Support with the following information:
  • MCS console log when the incident occurred
  • RKGWSLOG contents when the incident occurred
  • JCL and JESLOG of product JOB environment
  • Output of any dumps produced (SYSDUMP, SYSMDUMP)