Previous Topic

Next Topic

Book Contents

Book Index
Messages GIX0 through GIX0xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

GIX000I CONTROL-V GLOBAL INDEX utilityName STARTED

Explanation: This information message indicates that the utilityName Global Index utility started.

Corrective Action: No action is required.

GIX001I CONTROL-V GLOBAL INDEX utilityName ENDED OK

Explanation: This information message indicates that the utilityName Global Index utility finished successfully.

Corrective Action: No action is required.

GIX003I USER PARAMETERS: parm_1. . . parm_n

Explanation: This information message identifies the input parameters for the CTVUPGDB or CTDDBPRT utility.

Corrective Action: No action is required.

GIX004E INVALID DO= FUNCTION SPECIFIED

Explanation: The function specified in a DO statement is not valid.

The current utility stops.

Corrective Action: Correct the function name in the DO statement and rerun the job.

GIX005E INVALID PARAMETER: parm

Explanation: The parm input parameter for the CTVUPGDB or CTDDBPRT utility is not valid.

The utility stops.

Corrective Action: Correct the invalid input parameter and rerun the job.

GIX006E REDUNDANT PARAMETER: parm

Explanation: The parm input parameter for the CTVUPGDB or CTDDBPRT utility has already been specified. The same parameter is specified twice.

The utility stops.

Corrective Action: Delete the extra input parameter from the JCL and rerun the job.

GIX007E ERROR IN PARAMETERS: FODATE IS HIGHER THAN TODATE

Explanation: The specified starting order date (FODATE) is later than the specified ending order date (TODATE).

The utility stops.

Corrective Action: Correct the value of either FODATE or TODATE in the JCL and rerun the job

GIX008E INVALID DATE SPECIFIED: date

Explanation: Either the starting order date (FODATE) or the ending order date (TODATE) is invalid. The correct format is DD/MM/YY.

In this message, date is the problematic FODATE or TODATE date.

The utility stops.

Corrective Action: Correct the value of the incorrect ODATE parameter and rerun the job.

GIX00BE INVALID PARAMETERS

Explanation: A parameter in the SYSIN stream for the CTVUPGDB utility is invalid. The error was detected during analysis of input parameters.

The CTVUPGDB utility stops.

Corrective Action: Examine other messages relating to the CTVUPGDB utility to identify and fix the problem, and rerun the utility.

GIX00CE THE PARAMETER parm MUST BE SPECIFIED

Explanation: The parm input parameter for the CTVUPGDB utility is missing. The CTVUPGDB utility requires the parm parameter.

The CTVUPGDB utility stops.

Corrective Action: Insert the missing parameter in the JCL and rerun the job.

GIX00DE ERROR OPENING GLOBAL INDEX DATABASE. RC=rc

Explanation: The current utility or IOA application server could not open the Global Index database.

Global Index processing stops.

Corrective Action: Do the following:

Correct the problem, and rerun the job.

GIX010E SET PATH FAILED. RC=rc

Explanation: The Global Index function could not establish a path for retrieving values. The required path does not exist in the Global Index database.

In this message, rc is the internal return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The current utility stops.

Corrective Action: Do the following:

  1. Examine the return code to identify the problem.
  2. Examine the IOA log for messages clarifying the error.
  3. Correct the problem.
  4. Rerun the current utility or restart the IOA Application server.
  5. If necessary, contact your INCONTROL administrator.

GIX014E ERROR OPENING {SORTIN | SORTOUT} FILE

Explanation: The current utility could not open the SORTIN or SORTOUT temporary sorting file.

The current utility ends with a return code of 08.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

GIX015E ERROR ALLOCATING STORAGE FOR utilityName

Explanation: While executing the utilityName utility, the GETMAIN request failed. The GETMAIN request fails when there is not enough storage.

The utilityName utility ends with a return code of 08.

Corrective Action: Increase the region size in the appropriate JCL JOB or EXEC statement and rerun the utility.

GIX016E ERROR FREEING STORAGE FOR utilityName RC=rc

Explanation: While executing the utilityName utility, the FREEMAIN request failed. FREEMAIN failed to free storage that GETMAIN allocated.

For an explanation of the return code (rc) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The utilityName utility ends with a return code of 08.

Corrective Action: No action is required.

GIX017E DYNAMIC ALLOCATION OF fileName FAILED, RC=rc, REASON CODE=rsn

Explanation: Dynamic allocation failed. This error occurred when the CTVUPGDB utility tried to allocate the fileName file.

For an explanation of the internal return code (rc) and the reason code (rsn) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Use the information provided by the return and reason codes to correct the problem. If necessary, contact your system programmer.

GIX018E DYNAMIC DEALLOCATION OF fileName FAILED, RC=rc, REASON CODE=rsn

Explanation: Dynamic deallocation failed. This error occurred when the CTVUPGDB utility tried to deallocate the fileName file.

For an explanation of the return code (rc) and the reason code (rsn) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: No action is required.

GIX019E INTERNAL ERROR - PATH TREE NOT FOUND

Explanation: The internal routine of the CTVUPGDB utility that scans the index tree encountered an empty path.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

GIX020E INTERNAL ERROR - ORPHAN SUBINDEX

Explanation: The internal routine of the CTVUPGDB utility that scans lower level index trees encountered an empty parent path.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

GIX022E SORT FAILED RC=rc

Explanation: The sort routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the sort routine it invokes ends with a return code other than 0.

For an explanation of the return code value rc, refer to the documentation for your SORT utility.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the return code rc to identify the problem.
  2. Correct the problem.
  3. Rerun the current utility or restart the IOA Application server.
  4. If necessary, contact your system programmer for assistance.

GIX023E CTVGDB FAILED RC=rc

Explanation: The CTVGDB routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the CTVGDB routine it invokes ends with a return code other than 0.

Possible values for the internal return code from CTVGDB (rc) are explained in the following table:

rc

Explanation

04

No values for subindex.

08

Error during open.

12

Error during close.

16

Error during GETMAIN operation.

20

Error during FREEMAIN operation.

24

Error during dynamic allocation.

28

Error during dynamic deallocation.

32

Error during load.

36

User Report List file access error.

40

Internal error in path tree.

44

Internal error during OPENSUB operation.

48

Internal error. Path not found for sort record.

52

Sort failed.

56

Global Index database access error.

60

Two paths with the same name and different lengths.

64

Sort file is full.

68

IOAMEM error.

72

CHKPTID member in use by another job.

80

Path not found in the CTDGIDB2 member.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error and rerun the CTVUPGDB utility.
  3. If necessary, contact your INCONTROL administrator.

GIX024E parm PARAMETER INVALID. ONLY YES OR NO IS VALID

Explanation: The value of the parm input parameter is invalid. The value of the parm parameter must be YES or NO.

The current utility stops.

Corrective Action: Correct parm in the JCL and rerun the utility.

GIX025W MAXIMUM NUMBER OF PROCESSED INDEXES procIndex REACHED. PROCESSING STOPPED

Explanation: The CTVUPGDB utility tried to add another main index to the Global Index database when it had already added the maximum number for this run. The MAXINDX parameter defines the maximum number of indexes that may be added to the Global Index database in each run of the CTVUPGDB utility.

The utility adds MAXINDX main indexes and ends with a return code of 04. Other indexes will be added during the next run of the CTVUPGDB utility.

Corrective Action: Increase the value of the MAXINDX parameter and run the CTVUPGDB utility again.

GIX026E parm PARAMETER INVALID. ONLY YES, NO OR ALL IS VALID

Explanation: The value of the parm input parameter is invalid.

Valid values for the parm parameter are:

The current utility stops.

Corrective Action: Correct the parm input parameter in the JCL, and rerun the utility.

GIX027E JOBID PARAMETER INVALID. SHOULD BE Jnnnnn or Jnnnnnnn

Explanation: The JOBID input parameter is invalid. The format of the parameter name must be the character J followed by five or seven digits, depending on how your system is set up.

The utility stops.

Corrective Action: Correct the JOBID input parameter in the JCL, and rerun the utility.

GIX028W INDEX EXISTS IN GLOBAL INDEX DATABASE, USE FORCE PARAMETER TO ADD IT AGAIN

Explanation: The CTVUPGDB utility is trying to add an index that is already in the Global Index database. The GIX029I message, which follows the current message, provides details about the index that caused the error.

The index is not processed.

Corrective Action: To replace values in an existing index, run the CTVUPGDB utility with the FORCE input parameter set to YES.

GIX029I USER userName, REPORT reportName, JOBNAME jobName, JOBID jobId, ODATE orderDate

Explanation: This information message provides detailed information about the situation that caused the GIX028W message to be issued.

Corrective Action: No action is required.

GIX02AI INDEX: index DSNAME: dsn

Explanation: This information message is issued by the CTVUPGDB utility before the GIX017E error message and displays the index name and data set name of the index file for which the dynamic allocation error occurs.

The variables in this message are:

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: See the description of the GIX017E message.

GIX02BE CHKPTID MEMBER memName IS IN USE

Explanation: The memName CHECKPOINT member is in use by the CTVUPGDB utility, which has been invoked by another user.

The CTVUPGDB utility ends with a return code of 00.

Corrective Action: Try to run the utility again later.

GIX02CI WAITING FOR GLOBAL INDEX DATABASE index

Explanation: The index Global Index file is being used by another task for writing data.

The CTVUPGDB utility checks the Global Index file every 30 seconds until its use by the other task ends and the file is released. The CTVUPGDB utility then starts.

Corrective Action: No action is required.

GIX02DE LIST=DB2 OR LIST=ONLY SHOULD BE SPECIFIED

Explanation: The required LIST parameter is not specified or an incorrect value is specified.

The utility stops.

Corrective Action: Add the missing LIST parameter or set it to a valid value then rerun the job.

GIX02EW PATH NOT FOUND IN CTDGIDB2: pathName

Explanation: The pathName Index path was not found in the CTDGIDB2 member, which contains a list of index path names

This message is only issued if the LIST input parameter of the CTVUPGDB utility is set to DB2.

The CTVUPGDB utility does not unload the values of the pathName Index path into the sequential file from which they can be copied into the DB2 table.

Corrective Action: No action is required.

GIX02FE RECORD KEY vsaKey

Explanation: This information message follows the CTD908S message. The GIX02FE message identifies the VSA key of the record that was being accessed when the error occurred that caused the CTD908S message to be issued.

In this message, vsaKey is the VSA key of the problematic record.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: No action is required.

GIX031I TO GLOBAL INDEX DATABASE WERE ADDED: reportsQuantity REPORTS, indexQuantity INDEXES, indexValueNum INDEX VALUES

Explanation: This information message identifies the data that was added to the Global Index database.

Corrective Action: No action is required.

GIX034S INTERNAL ERROR CREATING TABLE tableName

Explanation: An internal error occurred in the CTVUPGDB utility. CTVUPGDB did not find the SYSDATA entry in the internal table.

The CTVUPGDB utility ends with a return code of 8.

Corrective Action: Contact your INCONTROL administrator.

GIX035E INDEX tableName HAS INCORRECT LENGTH

Explanation: The CTVUPGDB utility tried to add a path that was already in the Global Index database with different length parameters. This message occurs during an attempt to change the length of the index value in the definition of the decollation mission for a path that is already in the Global Index database.

The CTVUPGDB utility continues without adding the values in the indicated path to the Global Index database.

Corrective Action: Either change the length of the index value in the definition of the decollation mission that is causing the incorrect path or delete the old path from the Global Index database.

GIX036I GLOBAL INDEX HOUSEKEEPING UTILITY STARTED

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started.

Corrective Action: No action is required.

GIX037I GLOBAL INDEX HOUSEKEEPING UTILITY ENDED

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility ended.

Corrective Action: No action is required.

GIX038I SEARCHING THE ACTIVE AND MIGRATED USER FILES

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started searching ACTIVE and MIGRATED user files. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Corrective Action: No action is required.

GIX039I DELETING VSA ENTRIES

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started deleting VSA entries from the Global Index database. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Corrective Action: No action is required.

GIX03CE ERROR IN PARAMETERS

Explanation: The CTVGICL Global Index housekeeping utility detected one or more invalid parameters. CTVGICL detected the error while it was analyzing parameters.

The CTVGICL utility stops.

Corrective Action: Examine other messages relating to the job to identify and correct any errors, and rerun the utility.

GIX03DE IOAMEM ERROR func memName, RC rc, REASON CODE rsn

Explanation: The CTVUPGDB Global Index utility could not read the specified library member of the CTD PARM library. CTVUPGDB was trying to read GLOBIDB or the member specified by the CHKPTID input parameter to see if the member needed to be restarted from the checkpoint as a result of an earlier abnormal ending.

The CTVUPGDB utility starts from the beginning to try to write the member.

Corrective Action: If there are no other messages, and the utility ended normally, no action is required. This message may be triggered by the first run of the CTVUPGDB utility. Otherwise, examine the other error messages and respond accordingly.

If the problem persists, report the information returned in the message to your INCONTROL administrator.

GIX03EI INDEX PATH: pathName

Explanation: This information message is issued for each loaded Index Path by loading the Global Index immediately during decollation mission run.

In this message, pathName is the name of the loaded Index Path.

Corrective Action: No action is required.

GIX03FE DELRPT FUNCTION FAILED. RC=rc

Explanation: The CTVGICL Global Index utility could not finish processing the DELRPT function. The CTVGICL utility invokes the DELRPT function to delete reports.

In this message, rc is the internal return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The CTVGICL utility stops.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX03GI reportsQuantity REPORTS WERE SELECTED FROM file USER FILE

Explanation: This information message indicates the number of reports selected for checking from the ACTIVE or MIGRATED user file by the CTVGICHK utility.

The variables in the message are:

Corrective Action: No action is required.

GIX03HW NO REPORTS WERE SELECTED

Explanation: No reports were selected by the CTVGICHK utility for checking.

The CTVGICHK utility ends with a return code of 4.

Corrective Action: Correct the input selection parameters in the JCL member and rerun the utility.

GIX040E DELPATH FUNCTION FAILED. RC=rc

Explanation: The CTVGICL Global Index housekeeping utility could not finish processing the DELPATH function. The CTVGICL utility invokes the DELPATH function to delete paths.

In this message, rc is the internal return code from the Global Index interface routine. Possible values are explained in the following table.

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility stops.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX041I USER PARAMETERS FOR GLOBAL INDEX CLEAR parmList

Explanation: This information message displays the parameters specified for the CTVGICL Global Index housekeeping utility.

Corrective Action: No action is required.

GIX042I PATH DELETED: pathName

Explanation: This information message indicates that the CTVGICL Global Index utility deleted the pathName path from the Global Index database.

Corrective Action: No action is required.

GIX043E ERROR IN DELPATH FOR pathName RC rc

Explanation: The DELPATH Global Index function could not delete the pathName path. The CTVGICL utility invokes the DELPATH function to delete paths.

A possible cause for this error is that the PATH to be deleted was in use when DELPATH tried to delete it.

The variables in this message are:

DELPATH skips the path that caused the error and continues to delete the next path.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX044E parm PARAMETER INVALID. SHOULD BE AFTER PATH PARAMETER

Explanation: The parm input parameter for the CTVUPGDB Global Index housekeeping utility is in the wrong position. The ALT and BASELEN parameters may be specified only once each and must appear after the PATH parameter because they refer to a specific path.

The CTVUPGDB utility stops.

Corrective Action: Correct the input parameters in the JCL and rerun the job.

GIX045W NO RECORDS WERE ADDED TO THE GLOBAL INDEX DATABASE

Explanation: The CTVUPGDB Global Index housekeeping utility did not add any records to the Global Index database.

The CTVUPGDB utility continues processing.

Corrective Action: To add records to the Global Index database, correct the input parameters in the JCL for the CTVUPGDB utility and rerun it.

GIX046I LIST OF DELETED REPORTS:

Explanation: This information message is the header for a list of reports that the DELRPT function of the CTVGICL Global Index housekeeping utility deleted. The GIX046I message is followed by one or more instances of the GIX047I message.

Corrective Action: No action is required.

GIX047I USER userName JOBNAME jobName KEY vsaKey - entryNum ENTRIES

Explanation: This information message identifies a report that was deleted by the CTVGICL utility. The first GIX047I message in a series is preceded by either the GIX046I or the GIX04II message.

The variables in this message are:

Corrective Action: No action is required.

GIX048I FROM GLOBAL INDEX DATA BASE WERE DELETED: nr REPORTS, ne ENTRIES.

Explanation: This information message provides the number of reports and Global Index entries deleted by the current run of the CTVGICL utility.

The variables in this message are:

Corrective Action: No action is required.

GIX049E file_typ USER FILE READ ERROR, RC=rc

Explanation: An error occurred while reading the User report list file.

The variables in this message are:

Valid values for rc are:

rc

Explanation

004
  • Read operation: EOF.
  • Add index operation: Duplicate Key.
  • Update operation: Record was changed.

008

Duplicate key.

012

Incorrect record for update.

016

The record was not found (probably deleted), or an invalid record was read, or the function is not correct.

020

Insufficient memory to open an IOA Access Method file.

024

Not enough space in data file.

028

Not enough space in index file.

032

The current call terminates because the previous open failed.

036

Incorrect record length.

040

Internal error.

044

Internal error.

052

Invalid key fields.

056

Key is too long.

058

For future use.

060

Index record does not match data record.

064

Wish WD1164 setting does not match file contents.

068

Incorrect parameter for Interface routine.

072

Incorrect file type.

106

Record not found.

108

Record not found. Invalid extent number.

109

Record not found. Invalid block number.

110

Internal error. Record not found. Invalid extent number.

111

Internal error. Record not found. Invalid block number.

112

Insufficient memory for internal buffers.

113

Open failed for database file.

114

RDJFCB failed for database file.

116

Corrupted free list.

118

Corrupted record.

119

Record not found.

120

Invalid QNAME.

121

Bad record in free list.

122

Invalid data set name in control record.

124

Invalid function.

128

IOAPARM load failed.

132

Add failed. Record too long.

136

I/O error.

144

EXCP init error.

146

For future use.

148

Invalid data set name or DD name is too long.

150

Locate failed.

152

SVC 99 allocate failed.

154

SVC 99 unallocate failed.

156

Dual database not up to date - aborting.

158

For future use.

160

Link of IOADBF failed.

164

A dynamic allocation error occurred (for example, out of space condition, security problems). See dynamic allocation error messages in the job log.

166

Control record cannot be updated because it is not enqueued.

168

Update failed. Record too long. No room in block.

170

IOADBSB# load failed.

172

READQ failed. Another block is already enqueued.

174

Function OPEN0 (exclusively) failed.

176

Function UPDATE0 failed. Data corrupted.

178

Function UPDATE0 failed. No appropriate enq.

180

Buffering not initialized. Internal error.

182

ENQ error.

184

Error during record compression / decompression.

186

Attempted to write the wrong extent of a multi-extent data set.

204

Record not found.

208

Error accessing the file.

212

Insufficient memory for internal buffers.

216

Internal error.

218

The structure of the index tree is corrupted. A key on a higher level of the tree does not match the last key on a lower level.

219

The structure of the index tree is corrupted. The indicated key value, or a higher value, was not found in the block.

220

Invalid function.

224

Invalid timestamp

284

Invalid chain of index elements - rebuild index and rerun process.

The CTVGICL utility ends with a return code of 16.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error and rerun the CTVGICL utility.
  3. If necessary contact your INCONTROL administrator.

GIX04AE GLOBAL INDEX READ ERROR, RC=rc

Explanation: An error occurred while reading data from the Global Index database.

In this message, rc is the return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The Global Index request is not performed.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Restart the IOA application server or rerun the job.
  4. If necessary contact your INCONTROL administrator.

GIX04BE DELETE REPORT FROM DB2 TABLE tableName FAILED, RC=rc

Explanation: An attempt to delete report entries from a DB2 table failed.

The variables in this message are:

Possible values for rc are:

Return Code

Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The CTVGICL utility ends with a return code of 16.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX04CW REQUEST IS REJECTED. PLEASE TRY AGAIN LATER

Explanation: A request to retrieve data from the Global Index DB2 database is rejected because the corresponding DB2 table is in use by another job that is loading or deleting data. This message is directed to the WebAccess user who issued the request.

The Global Index request is not performed.

Corrective Action: Reissue the request later.

GIX04DE DELVAL FUNCTION FAILED, RC=rc

Explanation: An error occurred while deleting an index value from the Global Index IOA Access Method database file.

In this message, rc is the internal return code from the Global Index interface routine. Possible values are explained in the following table.

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Search the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX04EE PARAMETER DELPATH IS MISSING FOR DELVAL FUNCTION

Explanation: The CTVGICL utility detected that the DO Control-D input parameter was set to DELVAL, but the DELPATH input parameter that is mandatory in this case was not found.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Insert the DELPATH parameter in the JCL and rerun the job.

GIX04FE ERROR DELETING VALUE: indexValue, RC=rc

Explanation: An error occurred while deleting an index value from the Global Index IOA Access Method database file.

The variables in this message are:

Possible values for rc are:

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.
  2. Correct the error.
  3. Rerun the CTVGICL utility.
  4. If necessary contact your INCONTROL administrator.

GIX04GI VALUE DELETED: indexValue

Explanation: This information message identifies the index value which is being deleted when you invoke the DO=DELVAL function of the CTVGICL utility.

In this message, indexValue is the identity of the index value that is being deleted.

Corrective Action: No action is required.

GIX04II FROM DB2TABLE tableName

Explanation: This information message identifies the DB2 table name from which the reports were deleted. This message is followed by one or several instances of messages GIX047I.

Corrective Action: No action is required.

GIX04JE REQEST REJECTED. INDEX NAME/VALUE CANNOT BE SPECIFIED AS A MASK

Explanation: The index name or index value specified in the Control-D Web/Access Filter window contains a mask character (* or ?).

The request is rejected.

Corrective Action: Specify the index name or index value in the Filter in full, without any mask character, and reissue the request.

GIX04KE DB2 TABLE tableName READ ERROR, RC=rc

Explanation: An attempt to read data from a DB2 table failed.

The variables in this message are:

Possible values for rc are:

rc

Explanation

76

DB2 open error

84

SQL error

85

SQL error if timeout occurred

The CTVGICL utility skips this DB2 table and continues to work with other tables specified in the parameters.

Corrective Action: Do the following:

  1. Examine the IOA Log file for messages clarifying the source of the error.
  2. Correct the error and if the specified DB2 table should be cleaned, rerun the utility

GIX04LI FROM DB2 TABLE tableName WERE DELETED number ENTRIES

Explanation: This information message provides the number of entries deleted from the tableName DB2 table.

The variables in this message are:

Corrective Action: No action is required.

GIX04NI USER userName JOBNAME jobName KEY key - entry

Explanation: This information message identifies a report that was deleted by the CTVGICL utility.

The variables in this message are:

Corrective Action: No action is required.

Parent Topic

GIX messages