This information is for anyone who needs to understand, install, or use the CICS® Interdependency Analyzer.

This information is intended to be read sequentially.

Requirements for running CICS® IA.

CICS® IA assists in understanding, in a controlled manner, the inter relationships between the shared common resources of applications and services.

The affinity related functions of CICS® IA help users of CICS dynamic routing, who need to determine whether any of the transactions in their CICS applications use programming techniques that require them to be run in the same region thus creating an inter-transaction affinity, or in a particular region, thus creating a transaction-system affinity. Application programmers can use CICS IA to detect whether the programs they are developing are likely to cause transaction affinities.

The CICS® IA Command Flow utility allows individual users to capture CICS, IBM® Db2®, MQ and IMS® commands in a chronological order for one or more transactions. Each user can capture information for his or her given transaction or transactions. They can also individually load and view the data that they have captured.

You can use the Collector in real-time to detect transaction resource definitions and transaction affinities in a running CICS® region.

The Dependency database objects contain accumulated data about all your programs and transactions and the resources that they use.

The Affinity database objects contain accumulated data about all your programs and transactions and the affinities between them.

The CICS® IA plug-in for CICS Explorer® (CICS IA plug-in) is an Eclipse plug-in that operates on top of the CICS Explorer to help you analyze the CICS IA data, including the interdependency data, affinity data, and Command Flow data. When you install the CICS IA plug-in for CICS Explorer there is help available on how to use the CICS IA plug-in, Help > Help Contents > CICS IA User Plug-in guide.

CICS® IA can create dependency reports, affinity reports and threadsafe reports by running batch jobs.

The Scanner component consists of two scanners: the Load Module Scanner and the CSECT Scanner.

The Builder is a batch utility that takes as input a file of basic affinity-transaction-group definitions created by the Reporter. It produces a file of combined affinity-transaction-group definitions suitable for input to CICSPlex SM.

CICS® IA uses an ISPF dialog that runs REXX execs to assist you in configuring your CICS IA environments.

The data collected from the Dependency, Affinity and Command Flow collectors are stored in the CICS® IA database. Data collected from the CICS IA scanners are also stored in this database.

CICS® IA provides a number of real-time collectors. To enable the collectors, you must complete a number of tasks to create the resources that are required to facilitate the collection and to define these resources to the CICS regions where the collectors run.

Before you begin upgrading your Db2® configuration, ensure that you have read and followed the instructions to prepare your CICS® IA environment and the Db2 considerations.

How to configure an existing collection environment for upgrade, upgrade an existing collection environment, and run the IVP transaction to verify the installation.

This section describes some optional tasks that you might be required to be perform.

To run the Collector for the first time, configure the region options using option 2 of the Collector Main Administration Screen before gathering any dependency or affinity data.

Use this procedure to display the Collector Main Administration Menu panel.

Use the menu CIU100 to control the collection of dependency and affinity data.

You can control how the Collector operates by changing the options that it uses.

You can manage the Command Flow data collection with the aid of the User Command Flow Utility, which helps you to create new configurations of the Command Flow data collection options, change or define parameters of the configurations that already exist, and display statistics about data collection.

In CICS® IA 6.3, you can manage data collection not only by using the CINC and CINT transactions, but also by using the CICS IA Explorer plug-in.

CICS® IA provides a number of batch jobs to update the database from the VSAM files.

CICS® IA provides the CIUAFFLD batch job to update the database from the VSAM files.

CICS® IA provides batch jobs to update the database from the command flow log stream.

You can reduce the amount of data you initially collect by identifying patterns in your resource names, and by using a collection ID to identify the data you load into IBM® Db2®.

To manage the data that you have collected, you can delete your unwanted data and keep your data sources in sync.

How to create a UDB configuration and access a previous UDB configuration.

To select an existing UDB configuration, select option 6 from the configuration menu.

To create a CICS® IA UDB database, follow these steps.

CICS® IA provides sample data that you can load into your new CICS IA UDB database. You can then connect to the database by using the CICS IA plug-in for CICS Explorer and verify that your UDB database is working correctly.

When a CICS® IA UDB database is created, you can load the data.

Before you can update a CICS® IA UDB database with new data, you need to convert the VSAM files that are created by the Collector to the QSAM flat files or, in other words, comma-separated values (CSV) files.

This section describes how to run the CICS® IA Dependency Reporter. The Dependency Reporter consists of a batch job, CIUJCLRP, that produces reports of the dependencies found by the Collector.

The CICS® IA Affinities Reporter can be used to produce reports and definitions.

Analyzing the sample output produced by a summary report and a detail report.

You can request a summary report from the Load Module Scanner by editing and running the CIUJCLLS job.

You can request a detailed report from the Load Module Scanner by editing and running the job CIUJCLLD.

To run the CSECT Scanner, you can edit and run the CIUJCLCS job. This job produces a printed report and updates the CIU_PROGRAM_INFO and CIU_CSECT_INFO Db2® tables.

To run the CSECT Scanner, you can edit and run the CIUJCLSS job. This job produces a printed report and creates CSV files.

The printed report has two line formats; one for load module information and one for CSECT information.

To run the Builder, edit and run the CIUAFFBL job.

The syntax in the sequential data sets used as input for the Builder is similar, but not identical, to that allowed by CICSPlex SM.

The Builder produces a file containing a set of definitions of combined affinity transaction groups and a report listing the combinations that occurred.

This CIUJSAMP job produces SQL output for the sample query you have selected.

This section describes tools and techniques that you can use to find the cause of a problem, and suggests one or more actions for solving it.

Steps to take to try to solve errors with CICS® IA.

The IBM® Support structure helps you to resolve problems with IBM products and ensure that you can make the best use of your IBM computing systems. Program support is available to all licensed users of IBM licensed programs.

This section lists the commands monitored by the Collector because they have the potential to create dependencies.

This section lists the affinity-related EXEC CICS® commands detected by the CICS IA Collector.

This section describes what is detected by the Detector and Reporter for each affinity type.

The reported offset of a command is the offset from the start of the load module of the BALR to the CICS® stub.

The reported offset of a command is the offset from the start of the load module of the command CICS® argument zero.

This section describes the tables and views defined in the Dependency database.

This section describes the tables and views defined in the set of Affinity database objects.

This section describes the tables and views defined in the Load Module Scanner database objects.

This section describes the tables and views defined in the CSECT Scanner database.

This section describes the structure of the CICS® regions objects.

This section describes the structure for the Detailed resource objects.

This section describes the CIU_RESOURCE table. This table is used by the CICS® IA plug-in to improve performance and combine resource tables.

This section describes the CIU_VERSION table. This table is used by the CICS IA plug-in for CICS® Explorer to synchronize the CICS IA plug-in version being used and the base IA database objects.

This section describes the Command Flow base table that contains records for each command that is issued by the transactions. You can write your own SQL applications to query the table; these applications must use native SQL to write the queries.

This section describes the structure of two CICS IA tables that are used only to generate the program flows report in the CICS IA plug-in for the CICS Explorer.

Learn about the correspondence between resource type and command function for the monitored CICS® commands.

Information on IBM® support policy can be found on our Web site.

CIUMSGE Language Module Not Found

Begin CICS® IA IVP for TS version: CICS-version-number

Installation verification ended successfully

Transaction verification failed, transaction ID: transaction-name

Program verification failed, program ID: program-name

VSAM file verification failed, file ID: file-name

Transaction verified, transaction ID: transaction-name

Program verified, program ID: program-name

VSAM file verified, file ID: file-name

Verification unsuccessful — highest return code: return-code

TD queue verified, TD queue ID: TDqueue-name

TD queue verification failed, TD queue ID: TDqueue-name

DB2ENTRY verified, DB2ENTRY ID: DB2entry-name

DB2ENTRY verification failed, DB2ENTRY ID: DB2ENTRY-name

DB2TRAN verified, DB2TRAN ID: DB2TRAN-name

DB2TRAN verification failed, DB2TRAN ID: DB2TRAN-name

JOURNALMODEL verified, model ID: model-name

JOURNALMODEL verification failed, model ID: model-name

CINT already in use by user userid

Collector is not state

Collector is already stopped

Invalid key was pressed

CINT session has ended

Options must be Y(Yes) or N(No)

Size must be integer (10 to 2000 Mb)

Select a valid date/time format

Select a valid date/time separator

No amendments were entered

CINT options are updated

Options must be Y(Yes), N(No) or blank(default)

Records are restored

Dependency files are emptied

Dataspace too large - no storage available

Dataspace too large - IEFUSI limit reached

No records were restored

CICS® is terminating

Press Enter to confirm Start with data restore or PF12 to cancel

Press Enter to confirm Start without restore or PF12 to cancel

Press Enter to confirm Stop or PF12 to cancel

Enter to confirm Start ALL or PF12 to cancel

Enter to confirm Stop ALL or PF12 to cancel

A CINT action must be supplied

No actions to take

Transaction ID prefix is invalid

Language code is invalid

Control file CIUCNTL not open in the FOR

Dependency file CIUINTn not open in the FOR

Control file CIUCNTL is not available

Dependency file CIUINT1 is not available

Error opening Control file CIUCNTL

Error opening Dependency file CIUINT1

CICS® command data failed RESP=eibresp RESP2=eibresp2 RCODE=eibrcode

Exclude list name is invalid

Affinity files are emptied

Options must be Y(Yes), N(No), or D(Detail)

Options must be Y(Yes), N(No), D(Detail) or blank(default)

Value must be between 2 and 9999, or 1 for no updates

Options must be A (Affinity), I (Interdependency), or B (Both)

Options must be A (Affinity), I (Interdependency), B (Both), or blank

Options must be Y (Yes), N (No), A (Aff.), I (Dep.), or B (Both)

Options must be Y (Yes), N (No), A (Aff.), I (Dep.), B (Both), or blank

All files are emptied

Press Enter to confirm REFRESH or PF12 to cancel

Press Enter to confirm REFRESH ALL or PF12 to cancel

CINT applid CICS® Resource options are updated

CINT applid Db2/MQ/IMS/CPSM options are updated

CINT applid General options are updated

CINT applid Time and Date options are updated

CINT applid CICS® Affinity options are updated

CINT applid Global options are updated

CINT applid Task options are updated

CINT applid Natural resource options are updated

Task collection trigger value must be between 1 and 9999

CINC session has ended

CICS® is terminating

Control file CIUCNTL is not available

Error opening Control file CIUCNTL

There are no connected CICS® regions

Too large number of selected regions

Invalid selection of APPLID

Option option is invalid

Options must be 1, 2, 3 or N(No)

CINT region-name Application Collection Options are updated.

Maximum applications-amount applications can be selected for dependency collection.

CINT region-name Application Collection Options are updated by user ID.

Enable collection of Application Data collection-option.

Wrong option for collection of Application Data.

Memory allocation error at point point-number.

For DEFAULTS, Application Collection Option must chosen.

CINT region-name Application Collection Options are set to DEFAULTS

CINT region-name Appl. Coll. Options are set to DEFAULTS by user ID. (Appl. Coll. is abbreviated because of TDQ limits)

Error opening CICS® IA Applications file.

CICS® command data failed RESP=eibresp RESP2=eibresp2 RCODE=eibrcode

VSAM filetype file filename command failed RESP=eibresp RESP2=eibresp2

CINT being used by userid

CICS® command PROGRAM program failed RESP=eibresp RCODE=eibrcode

Db2® table error on tablename SQL code code

CICS® region is not connected to IBM® Db2®

Records in control file CIUCNTL have incorrect format

Create dataspace action failed REASON=reason code ERROR=error code

Create table action failed REASON=reason code TABLE=table number

Add element action failed REASON=reason code TABLE=table number

Stop of collector has failed during Start processing

Collector is now state

Stop of Collector has failed

Destroy pool action failed REASON=reason code ERROR=error code

Destroy table action failed REASON=reason code TABLE=table number

CINT has abended abend code in program program

Data type collector is now state

Create CPOOL action failed REASON=reason code

Function call failed: FUNCTION=function code REASON=reason code

Destroy CPOOL action failed REASON=reason code

Error calculating space utilisation

Unsupported type of CINT task initiation

Incorrect CINT action: action

Non-terminal CINT task initiating

Replace element action failed REASON=reason code TABLE=table number

UT/TT table update failed FUNC=function code REASON=reason code TABLE=table number

VSAM dependency file filename header READ failed RESP=eibresp RESP2=eibresp2

Number of records restored = count

CICS® Release release is not supported by the Collector

CIUINTDT call failed REASON=reason code

EXEC CICS DISABLE STOP for program exitprog OK

EXEC CICS DISABLE EXITALL for program exitprog OK

DISABLE EXITALL for program exitprog failed RESP=eibresp RCODE=reason code

EXEC CICS ENABLE EXIT for program exitprog, EXIT exit OK

EXEC CICS ENABLE EXIT START for program exitprog OK

EXIT PROGRAM exitprog already disabled

EXEC CICS ENABLE TRUE for program exitprog OK

Exclude list name has invalid contents at offset offset

Dump domain function function failed RESP=resp RCODE=rcode

Collector is not in START or PAUSED state

CICS® IA dataspace is nn percent full

CINT applid CICS® Resource options are updated by userid

CINT applid Db2/MQ/IMS/CPSM options are updated by userid

CINT applid General options are updated by userid

CINT applid Time and Date options are updated by userid

CINT applid CICS® Affinity options are updated by userid

CINT applid Global options are updated by userid

CINT applid Task options are updated by userid

CINT applid Natural resource options are updated by userid

CINT command_name is requested by userid for applid

CINT Collector runtime options for applid:

options_list

Control file CIUCNTL not open in the FOR

CICS® command data failed RESP=eibresp RESP2=eibresp2 RCODE=eibrcode

USER record is not found in the CIUCNTL control file

USER record in the CIUCNTL control file has incorrect format

CONTROL1 record is not found in the CIUCNTL control file.

REGION record is not found in the CIUCNTL control file.

CINC has abended abend in program program

CINC being used by userid

Records in control file CIUCNTL have incorrect format

Unsupported type of CINC task initiation

CICS® Release release is not supported by the CINC

CINC abending - internal error elsewhere in the CINC

CINC command flow options are updated by userid

options_list

CICS® command PROGRAM program failed RESP=eibresp RCODE=eibrcode

EXEC CICS® ENABLE EXIT for program exitprog, EXIT exit OK

CINC Collector is already active for userid

Max concurrent CINC Collector sessions limit reached

User journal name journal_name value is already used by other active user

CINC Collector runtime options for userid

CINC Collector is not started in all/some your regions

CINC Collector is started in your regions

CINC Collector is not started. All options are empty.

CINC Collector is not started. Option option is empty

CINC Collector is not started. Some regions are not connected.

CINC Collector is not stopped. There are no active collector sessions.

CINC Collector is not stopped. There are no connected regions.

CINC Collector is stopped by uuuu

CINC Collector has logged nnnn records for uuuu

CINC Collector is not stopped. Option option is empty.

CINC Collector is stopped for uuuu. Limit of tasks: nnnn .

CINC Collector is stopped for uuuu. Limit of records: nnnn .

Invalid cursor position

CINC already in use by user userid

CINC Collector is not started. All regions are not connected

CINC Collector is already active for some regions

Updates are rejected because CINC Collector is running for userid

CINC Collector is stopped. Total records written: number

APPLIDs applidID is not found in control file. Updates are rejected.

Duplicate APPLIDs applidID specified. Updates are rejected.

Journal Copy Criteria option is invalid. Enter LAST, USER or CFID

CINC Collector is not started in all your regions

CINC Collector is started in some your regions

CINC was not completed for userid

CICS® ApplIDs option is empty

CINC Collector was not completed for userid

An abend occurred in program program for region region

CINC Collector for USERID userid1 is already started by userid2

Privileged Collection not started. In use by another privileged user userid

Privileged Collection not started. In use by general users.

General Collection not started. In use by privileged user userid

The value for the Authority field is incorrect

Wildcard characters in the UserID field are not allowed for general users

Invalid journal type in model

Logstream lsname assigned for CINC user userid

Different Control file names

User exit exit was loaded

There is no action to process.

No more users allowed. Maximum limit of users reached.

No users were added.

User userid was not copied.

Cannot manage user userid. It is in use by someone else.

User userid has "ACTIVE" status. Stop CINC collector and try again.

User userid was not updated.

Confirm the deletion of user userid.

The deletion of user userid was cancelled.

Journal name must begin with a letter.

Cannot delete user userid – CINC session is active.

User name can contain national characters. It must be alphanumeric.

Journal name can contain national characters. It must be alphanumeric

Cannot update user userid – CINC session is active.

User userid was added.

Cannot add user userid – CINC user or CINT region already exists.

Cannot add user userid – internal error occurred.

Cannot update user userid – CINC collector is active.

User userid updated.

Update failed – user userid does not exist.

Cannot update user userid – internal error occurred.

CICS® TS release is current_release. Release required_release or higher is required.

Consequences of deleting user with unknown status are unpredictable.

CICS® Interdependency Analyzer for z/OS® - nnnnnn

CINT options refreshed

CINB task is starting

CINB received an unrecognizable request

CINB has abended abend code in program program

CINB abending - system error elsewhere in the Collector

CINB save started - because of reason

CINB save ended - count records saved

CINB terminated - Collector is stopping

Message received from program program

Collector action by date/time options

Invalid file number for table in GWA

Transaction CINB must be initiated by transaction CINT

CINB abending - CICS® is terminating

Invalid address for program in the GWA

Function call failed FUNCTION=function code REASON=reason code TABLE=table number

File filename is full

Unexpected resource type resourcetype

Tasks before stopping:: nnnn .

Records before stopping: nnnn .

CIUCPOOL: Limit of cells is exceeded. NNNNN records rejected

Performance Monitoring is activated.

Performance Monitoring is deactivated

The TCB switch counter data is not available

CINB: count type records saved

CINB: DETAILED: count records type type saved

New dependencies total: count

New resource details total: count

Transaction CINS is starting

Transaction CINS has abended with abend code in program program.

Transaction CINS must be initiated by transaction CINT.

Transaction CINS has terminated - Collector is stopping.

Collector Statistics not available for this period of time.

Master System trace flag is set ON

Master User trace flag is set ON

Master System trace flag is restored OFF

Master User trace flag is restored OFF

Error at setting Master trace flag. Response code: eibresp

ENTER TRACENUM for program name failed RESP=eibresp . HL_TRACE forced to N

Function call failed FUNCTION=function code REASON=reason code TABLE=table number

Dataspace is full

Interaction with Natural failed REASON=reason

Service service failed RCODE=rcode REASON=reason

Interface with Natural is disabled.

Interaction with Natural failed REASON=reason

CICS® command data failed RESP=eibresp RESP2=eibresp2 RCODE=eibrcode

Interaction with Natural has abended abend code

Function call num is invalid for module

filename control record not found for applid applid. Run canceled

Some action failed. Return/ABEND code=return reason=reason

GENCB failed for filename CB=control block RC=return code REASON=reason code

File number filenum is invalid

Attempt to actionfilename. File is type

RPL number rplnum is invalid for filename

Table number table number is invalid

Invalid PARM specified. Program terminated.

Invalid {MATCH | STATE | CONTEXT} value specified. Correct and rerun

DSPSIZE value is not numeric. Correct and rerun

DSPSIZE is invalid. It must be between 2 and 2000

Load of modname has failed AC=abcode RC=reason_code

Dataspace too large - no storage available

Dataspace too large – IEFUSI limit reached

Create dataspace failed REASON reason_code ERROR error_code

Create table failed REASON reason_code TABLE table_number

Keyword keyword is invalid or unexpected

Keyword keyword is missing

A value of value is invalid for keyword keyword

Invalid CREATE type

Incorrect number of brackets

Missing semicolon

Keyword keyword is duplicated

No valid statements in REPGRPS – processing terminated

CIUTABM error function element TABLE table_number REASON reason_code MODULE progname

No HEADER record found – statement ignored

Duplicate TRANGRP name

Transaction group has not been previously created

Dependency data may be be incomplete because of abend type abend

Dataspace is full

No valid transaction IDs in REPGRPS – processing terminated

Invalid AFFLIFE for AFFINITY

PARM keyword is duplicated. Correct and rerun

Invalid REMOVE type

Report type is not recognized — processing terminated

Error reading Applid input – processing terminated

Error reading CIUCNTL file – processing terminated

Db2® table error on tablename SQL code code

OPTION ERROR: modulename A VALUE OF optionvalue IS INVALID FOR OPTION optionname.

modulename ERROR ON OPEN OF CIUOPTS

Bad parameter: xxx

Last use timestamps will not be updated

Last use timestamps will be updated

Number of new rows added to tablename = nnnn

Number of existing rows in tablename = nnnn

Number of rows updated in tablename = nnnn

SQL error: xxxxxxxx, yyyyyyyyy

File error: xxxxxxxx, yyyyyyyyy

**** QSAM OUTPUT STATISTICS FOR TABLE tablename ****

-------------------------------------

Number of processed records:

Number of existing rows:

Number of rows updated:

CIU_THREADSAFE_CMD table is empty.

QSAM CSV files will be produced

QSAM error, xxxxxxxx, yyyyyyyy. X=program name; y=diagnostic information

Journal records read = nnnnnnnn

Trace records written = nnnnnnnn

No rows selected for processing from tablename

**** UPDATE STATUS FOR TABLE tablename ****

Number of new rows added:

SQLERRMC: sqlerrmc

CONTROL1 record added to control file

CONTROL1 record already exists

Defaults record added to control file

DEFAULTS record already exists

APPLID region record added to control file

APPLID region record already exists

Number of regions added =number

Number of existing regions =number

Number of error records =number

No input records found for //REGIONS

Input record error – add region(aaaaaaaa,ssss,_dumphlq_)

CICS® APPLID must be 1 to 8 characters

CICS® SYSID must be 1 to 4 characters

No input records found for //CIUMIGXT

Parse OK - Number of APPLS added =

Parse failed - XML-EVENT: XML-TEXT:

Number of duplicate rows fixed in tablename = count

Number of applications migrated =

Length of APPLIC code > 8

Length of APPLIC name > 50

Length of APPLIC tran > 4

Length of APPLIC program > 8

Unknown record type type was read from file file. The record is skipped.

Data records read: number.

Data records processed: number.

Data records skipped: number.

procedure_name warning. SQL contention occurred while modifying Db2 tables data.

procedure_name error. Invalid parameter specified: parameter.

procedure_name SQL error. SQLCODE=sql_code ERRMSG="db2_error_message".

Db2 procedure procedure_name ended with RC=return_code.

CICS IA Dump HLQ must be 1 to 8 characters and non-blank - for DEFAULTS.

SYSID must be ''DFTS'' for DEFAULTS.

Translation table modname length is invalid

5655-U86 (C) Copyright IBM® Corp. 2001, 2025

An irrecoverable error has occurred in module module.

Enter a valid option

No regions defined to CICS® IA

Invalid action code.

Action processed successfully.

Start/Stop request cancelled.

Connection to remote region not acquired

Connection to remote region not found

Enter new Applid and Sysid

New Applid already exists

Press Enter to confirm delete or PF12 to cancel

Request cancelled

State must be STOPPED before you can delete

Options 1-3 not valid for single region file

Press Enter to confirm action or PF12 to cancel

CICS® IA not installed in target region

Option number not valid for item

Maximum of 200 records in control file

CINC Action processed successfully.

CINC user userid entry not found.

CINC Unknown request has been received.

Region name record Control file has an incorrect format.

Region name record is not found in Control file.

CICS IA beta trial period is over.

The file you have selected could not be found. Please select another file.

File read error: an internal key value is not a valid integer. Please select another file.

File read error: an internal key value is not a valid integer. Please select another file.

File read error: an internal key value is not a valid integer. Please select another file.

File read error: an internal key value is not a valid key value. Please select another file.

File read error: an internal key value is not a valid key value. Please select another file.

File read error: an internal key value is not a valid key value. Please select another file.

File read error: APPS must be a 3 character code.

File read error: error reading the selected file.

Error closing file.

The URL provided in the CICS® IA Preferences appears invalid. Please check the Host URL given in the CICS IA Preferences.

Communication with the host failed.

Communication with the host failed.

The data could not be displayed in a table. Please try the client again. If the problem persists contact IBM® support.

Copy fail: Cannot copy row numbers. Select another cell and try again.

Copy fail: No Cell in the table was selected. Select an individual cell and try again.

FileIO error: error saving FILENAME. Please try again.

FileIO error: error overwriting file. Please try again.

All available data for this query retrieved from the host.

There are more records to be retrieved.

No data to retrieve for this query.

CICS® region is not connected to IBM® Db2®. See message CIU8200I in the CINT log.

Invalid Application code. See message CIU8202W in the CINT log.

Enter a valid 2 digit KEY1 field. See CIU8203W in the CINT log.

Enter correct WHERE clause. See message CIU8204W.

No columns selected for display. See message CIU8206W.

Bad CICS® return code. See message CIU8205E in the CINT log.

Bad SQL return code. See message CIU8201E in the CINT log.

Client and server not compatible. See message CIU8207E in the CINT log.

No message file found on host.

Invalid return code from the host. Contact IBM® support.

CICS® region is not connected to IBM® Db2®

Db2® table error on function SQL code code

Enter a valid 3 digit application code.

Enter a valid 2 digit KEY1 field.

One or more WHERE fields are not alphanumeric.

CICS® command failed RESP=resp RESP2=resp2

No columns SELECTED for display.

Client and server not at the same service level.

This section lists the meaning for each possible value of the call parameters that are included in the error messages issued if an error occurs on a call to the Collector table manager, CIUTABM.

This section lists the meaning for each possible value of the call parameters that are included in the error messages issued if an error occurs on a call to the Collector CINB request queue manager, CIUCINP.

To calculate the space allocation requirements, estimate some values for the environment in which you want to run CICS® IA.

The data space consists of a number of tables, both permanent and temporary. The number and size of the tables varies depending on whether you are collecting Interdependency data or Affinities data.

There are ten VSAM files associated with CICS® IA.

Calculate the Db2® space allocations using these assumptions and guidance.

CICS® IA has no internal RACF® security classes. The two main interfaces are application programs. These two interfaces are the Operations and Administration Interface that is driven by transaction CINT and the Eclipse-based Query Interface.

CICS® IA uses Db2® packages to control access to the tables in CICS and batch. All the packages are bound in to both the batch plan and the CICS plan. The plan names can be defined at customization time.

You can use the CICS® IA External Interfaces to directly access different types of collected data from you application.

The CICS® IA Command Flow user exit provides additional options when you are saving information about the traced commands into the dataspace.

The CICS® IA plug-in for CICS Explorer uses hover help to provide you with extra information, however tooltips might not be readily available when using a screen reader such as JAWS.