Messages REPG00 through REPGxx

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

REPG01E INDEX CREATION ERROR. RC = rc, INTERNAL RC = int_rc, REASON = rsn

Explanation: Control-V was unable to create an index file.

Even though the index file is not created, the decollated report is produced.

Possible causes are:

Return Code	Explanation
4	RDJFCB of INDEX file error
8	OPEN INDEX file error
12	CLOSE INDEX file error
16	Insufficient memory.
20	Insufficient space on the volumes to create the index file.
28	Size of the index file calculated internally is not big enough for all entries.
40	Dynamic allocation error.
44	Dynamic deallocation error.
48	Sort error.
Other	Internal error.

This message is followed by message REPG06E.

The index is not created.

Corrective Action: Take appropriate actions to correct the problem associated with the specified return code:

Return Code	Explanation
4	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
8	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
12	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
16	Increase the REGION size of the Control-D or Control-V Decollation monitor.
20	Clear space on the volumes defined for index files in Control-V Installation Parameters or add another volume to the Control-V Installation Parameters.
28	First check that definition of every subindex is correctly defined in the decollation mission. If this is not the source of the problem, turn to BMC Customer Support, supplying the decollation mission definition and sample pages of the report.
40	For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the return code, internal return code and reason code. Contact BMC Customer Support.
44	Take the same action outlined for return code 40 above.
48	Check the sort messages in the Control-D or Control-V Decollation monitor sysout. If you cannot resolve the problem, record the sort messages and contact BMC Customer Support.
other	Record the return code, internal return code and reason code and contact BMC Customer Support.

REPG02E INDEX CREATION ERROR - INDEX SPANS OVER MORE THAN ONE CDAM DATASET

Explanation: A Report Decollation Mission attempted to index a report which spanned more than one Compressed Dataset Access Method (CDAM) data set.

Different CDAM data sets are created for each sysout of a report. An index file cannot index more than one CDAM data set. Use separate indexes, meaning, indexes with different names, to index different CDAM data sets.

The index is not created.

Corrective Action: Determine how many sysouts the job has and create an index for each, or alternately modify the decollation mission so that it creates indexes with different names for each CDAM data set by using the DCAM expression ALLOCTOPT=ONEDSN. See the Control-D and Control-V User Guide.

REPG03E INDEX CREATION ERROR - NO INDEXES CREATED

Explanation: The creation of the index file was not successful.

The index is not created. The status of the decollating mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log file and the Control-D or Control-V monitor job log for additional messages relating to this decollating mission.

REPG04W TOO MANY RESIDENT INDEXES FOR REPORT report - MAXIMUM 3

Explanation: An attempt was made to create more than three DASD-resident indexes for a single report. The maximum number of resident indexes for one report is three.

The index is created but is not designated DASD-resident. It will be deleted from DASD when the corresponding report is deleted and will be available on migrated media, if the report is migrated.

Corrective Action: Redefine the Report decollating mission to specify not more than three indexes that will remain DASD-resident.

REPG05E TOO MANY INDEXES FOR REPORT report - ONLY 9 CREATED

Explanation: An attempt was made to create more than nine indexes for a single report.

A maximum of nine indexes can be defined for one report.

Only the first nine indexes are created.

Corrective Action: Redefine the Report decollating mission to specify a maximum of nine indexes for this report.

REPG06E INDEX DSNAME=dsn BLOCKS=blk

Explanation: An error occurred during the creation of the dsn index file containing blk blocks.

This message is preceded by message REPG01E. See message REPG01E for more information.

Corrective Action: No action is required.

REPG07E "DDNAMES" INDEX NOT CREATED - ALLOCOPT "ONEDSN" OR "JOBSDSN1" REQUIRED

Explanation: The user attempted to create a DDNAMES index for a report created by a decollating mission whose ON CLASS statement does not contain ALLOCOPT=ONEDSN or JOBSDSN1 in the PRINT/CDAM PARMS field.

The index is not created.

Corrective Action: Add the expression ALLOCOPT=ONEDSN or ALLOCOPT=JOBSDSN1 to the decollation mission definition. For more information on the ALLOCOPT parameter, see the CDAM chapter in the Control-D and Control-V User Guide.

REPG08W MORE THAN ONE SUBINDEX WITH THE SAME NAME. ONLY THE FIRST ONE IS DEFINED

Explanation: The user attempted to specify the same name for more than one subindex of a main index.

All subindexes of a main index must have unique names. It is recommended that all indexes specified for a report have unique names.

When a subindex is encountered whose name was specified for a previously specified subindex, that subindex and all the indexes under it (if any) are not created.

Corrective Action: Change the subindex’s name.

REPG09W INCONSISTENT INDEX TREE STRUCTURE. SOME INDEXES/VALUES ARE NOT CREATED.

Explanation: The index tree defined for the report in the decollation mission is not consistent in structure.

During a run of a decollation mission, a main index was encountered that does not have the same subindexes defined throughout the mission definition. The topology of the index tree must be consistent.

Some of the subindexes are not created because of this inconsistency. Other subindexes may have incorrect values.

Corrective Action: Correct the index definition in the decollation mission and rerun the mission.

REPG0EE GLOBAL INDEX CREATION ERROR - NO GLOBAL INDEXES CREATED.

Explanation: This message is issued when loading the Global Index database immediately during the decollation mission run, if the database is not loaded successfully. This message is preceded by CTD and GIX messages explaining the cause of the problem.

Control-D decollates the reports without loading the index values into the Global Index database.

Corrective Action: Perform the following:

Examine the preceding messages to find out reason for the problem, and fix the problem.
Use the CTDGBILD job to load index values from reports decollated by this mission to the Global Index database.

REPG0GW UNSUPPORTED MULTI-VALUE INDEX STRUCTURE. SOME VALUES ARE NOT CREATED.

Explanation: The indexing report has the value structure of a multi-value index that is not supported by the current implementation of Control-V.

Corrective Action: Contact your INCONTROL administrator.

REPG0HE SYSTEM VARIABLE %%var ISN'T SUITABLE FOR CURRENT ENVIRONMENT.

Explanation: This message is issued when the current environment does not provide the ability to use the %%var system variable in SET/DO SET statements in decollation missions. The reason for the problem is due to the value of %%var.

Variable and value	Possible reason
$MEMORY=ABOVEBAR	The environment does not support 64-bit addressing mode

The Control-D monitor terminates the mission with the status of NOTOK.

Corrective Action: Start the CONTROL -D monitor in another environment, or remove the SET/DO SET statement for the %%var system variable from the decollation mission definition.

Parent Topic

REP messages