Messages NGTR200 through NGTR299
| Number | Description |
|---|---|
| NGTR200 | string-1 OPTIONS IN EFFECT ARE: Explanation: This message precedes a list of options settings. If it appears during configuration of NGT utilities for a DB2 subsystem, then it lists a set of default values which apply to that subsystem. If it appears during utility execution, then it represents a set of run-time values; these values are the defaults established for the DB2 subsystem superseded by any execution-time overrides. User response: No action required. |
| NGTR201 | JCL PARMS MUST BE SPECIFIED TO NAME THE DB2 SYSTEM ID. Explanation: All NGT utilities steps must have as the first part of the EXEC statement PARM field the name of the DB2 subsystem. This one does not. User response: Add to the JCL EXEC statement 'PARM=db2id'. |
| NGTR202 | MISSING APOSTROPHE FOLLOWING A PARM FIELD - string-1. Explanation: One of the EXEC statement PARM fields begins with an apostrophe, but no ending apostrophe can be found. User response: Normally, apostrophes are unnecessary. If they are used, there must be a beginning and an ending apostrophe. Correct the PARM and resubmit. |
| NGTR203 | LENGTH OF FIRST PARM (DB2 SSID) EXCEEDS 4-CHAR MAX: string-1. Explanation: The length of the name of the DB2 subsystem exceeds the MVS-specified maximum of four characters. User response: Specify a DB2 id no longer than four characters. |
| NGTR204 | SECOND PARM (UTILITY ID) EXCEEDS 16 CHARS - string-1. Explanation: The second value in the EXEC statement PARM field is the uid. This is an identifier for the utility. Any value up to 16 characters long can be used, apart from the comma. String-1 is the PARM field. User response: Shorten the uid to 16 or fewer characters and resubmit the job. |
| NGTR205 | THIRD PARM (RESTART PARM) IS NOT A RECOGNIZED VALUE - string-1. Explanation: The third value in the EXEC statement PARM field is the restart parameter. It must be one of the following: RESTART, QUICKEXIT, or NORESTART. String-1 is the PARM field. User response: Either specify one of the allowable values or specify nothing. RESTART is the default. |
| NGTR206 | LOGPDS OPEN ERROR - DD=LOGPDS. Explanation: A Log PDS is required for NGT utilities execution. If no LOGPDS DD statement is specified, then the dataset named at installation will be used. The open failed for this dataset. User response: Check if there are any messages on the system messages listing that might indicate a cause of this problem. |
| NGTR207 | LOGPDS DD NOT FOUND - DD=LOGPDS. Explanation: A Log PDS is required for NGT utilities execution. If no LOGPDS DD statement is specified, then the dataset named at installation will be used. No //LOGPDS DD statement exists and the installation name is unspecified. User response: Provide a //LOGPDS DD statement, naming a PDS with LRECL=80. |
| NGTR208 | UTILITY CONTROL STATEMENTS FROM SYSIN. Explanation: This message indicates the beginning of the SYSIN file processing. User response: No action is required. |
| NGTR209 | ERROR OCCURRED PROCESSING CONTROL STATEMENTS - RUN ABORTED. Explanation: Some Utility control statement(s) have been diagnosed with errors. Previous messages should indicate the problem. The run is aborted. User response: Missing data sets do not constitute a control statement error that causes termination. There must be some syntax error in the statement. |
| NGTR210 | //SYSIN DD MISSING - RUN ABORTED. Explanation: The SYSIN file is required. It contains the utility control statements. User response: Check your JCL to determine why SYSIN is missing. |
| NGTR211 | +COPY(NO) - NO COPY WILL BE TAKEN, databaseName.tableSpaceName DSNUM dataSetNumber WILL BE LEFT UNRECOVERABLE +COPY(NO) - NO COPY WILL BE TAKEN, databaseName.tableSpaceName PART partitionNumber WILL BE LEFT UNRECOVERABLE databaseName.tableSpaceName PART partitionNumber IS IN COPYPENDING databaseName.tableSpaceName PART partitionNumber IS NOT IN COPYPENDING Explanation: NGT Reorg does not copy objects during a reorganization. User response: No action is required. |
| NGTR212 | FIFTH PARM (MSGLEVEL) IS NOT A RECOGNIZED VALUE - value Explanation: The MSGLEVEL parameter on the EXEC statement has the indicated value. The utility allows only 0 or 1. The utility terminates. User response: Correct the EXEC statement parameters and resubmit the job. |
| NGTR213 | +SERVER(YES) IS REQUIRED FOR THIS FUNCTION. Explanation: The parameter value +SERVER(YES) was expected but not found for the current function. User response: Add +SERVER(YES) to the job, or change the value of the +SERVER parameter from NO to YES, and resubmit the job. |
| NGTR214 | REXX EXIT 'string-1' DID NOT RELEASE GLOBAL VARIABLE LOCK. Explanation: The REXX exec did a _GUPDATE which locked the Global Variable table. However, the REXX exec did not do a _GWRITE to write the global variables and unlock the table. User response: Correct the REXX exec. Either change the _GUPDATE to a _GREAD or add a _GWRITE. |
| NGTR215 | ENDING APOSTROPHE MISSING FROM DB2ID PARM. Explanation: The EXEC statement PARM field starts with an apostrophe but does not end with one. Apostrophes are not necessary, but if they are used, they must be paired. User response: Remove or pair the apostrophes. |
| NGTR216 | UID string-1 DOES NOT EXIST IN CONTROL MEMBER. Explanation: The named Utility Master UID selected for deletion does not exist and cannot be deleted. User response: The request for deletion of the named UID is ignored. Correct the UID selection. |
| NGTR217 | +RUNSTATS(YES) CONFLICTS WITH +RTS(NO). Explanation: +RTS(NO) cannot be specified if +RUNSTAT(YES) has been specified. User response: Correct the condition and rerun the REORG. |
| NGTR218 | VALUES-: PCTFR=string-1; FREEPG=string-2; ALLOPGS=string-3; USEDPGS=string-4; XTNTS=string-5. Explanation: This identifies the REORG INDEX Summary Report Values. User response: No action is required. |
| NGTR219 | TABLESPACE tableSpaceName PROCESSING ABORTED. Explanation: A previous message specified why NGT Reorg cannot continue for this object. User response: Correct the condition and rerun the reorganization. |
| NGTR220 | USER string-1 IS NOT AUTHORIZED ON DATABASE string-2 TO PERFORM string-3. Explanation: The userid named in string-1 does not have DB2 authorization to perform the utility function named in string-3 on the database named in string-2. User response: Authorize this user to perform the function. |
| NGTR221 | THE FUNCTION LIST MEMBER string-1 IS AT THE WRONG LEVEL. Explanation: The member named in string-1 cannot be used to run NGT/SuperUtilities V3 or V4, because it is back-level. User response: In order to restart this utility, you must execute NGT/SuperUtilities at version 2 or a lower level. If you don't want to restart the utility, then terminate it using NGT/SuperUtilities Interactive. |
| NGTR222 | MULTI-TABLE TABLESPACES NOT SUPPORTED. Explanation: The table space being reorganized is a multi-table table space (segmented). Special processing is not supported in this situation. User response: Correct the REORG statement to run this reorg. |
| NGTR223 | IBM FUNCTIONS CANNOT BE PERFORMED - NO CONNECTION TO DB2. Explanation: IBM functions (IBM utilities, commands, SQL) cannot be performed. No connection was made to DB2 either because DB2 is down or an invalid plan name was specified. User response: The run continues if +ONERROR(CONTINUE) and terminates otherwise. |
| NGTR224 | IBM CHECK INDEX/CHECK DATA UTILITIES CANNOT BE RUN Explanation: These specific IBM utilities, CHECK INDEX and CHECK DATA, cannot be run under NGT utilities due to internal restrictions. User response: The run continues if +ONERROR(CONTINUE) and terminates otherwise. |
| NGTR225 | PROCESSING BEGINS FOR INDEXSPACE indexSpaceName Explanation: The index named is about to be opened and read. The full index name follows this message. User response: No action is required. |
| NGTR226 | WILDCARD PROCESSING CONFLICTS WITH PARTITION NUMBER SPECIFICATION. Explanation: DB2 wildcard processing is not supported for a specific partition. User response: Do not code PART or DSNUM in the same statement with wildcards. |
| NGTR227 | REXX EXEC 'string-1' RECEIVING CONTROL. Explanation: The REXX Exec exit string-1 is about to receive control. User response: No action is required. |
| NGTR228 | REXX EXEC 'string-1' RETURN RC = number-1. Explanation: The return code from the REXX Exec exit string-1 is number-1. User response: No action is required. |
| NGTR229 | NO LOGPDS TO DISPLAY Explanation: The SHOWPDS LOGPDS statement was issued, but there is no LOGPDS defined for this run. User response: Add the //LOGPDS DD statement. |
| NGTR230 | CATALOG INDEXES MAY NOT BE SPECIFIED WITH REORG INDEXES TABLESPACE. Explanation: The REORG INDEXES TABLESPACE statement may not specify a database name of DSNDB06. User response: Change the //SYSIN statement and resubmit. |
| NGTR231 | TYPE-2 LARGE PROCESSING FOR THIS INDEX Explanation: The input being read is a Type-2 Large Index. User response: No action is required. |
| NGTR232 | REORG TERMINATED BECAUSE 'SKIPALL' SET Explanation: Exit XRRGPTNS set variable 'SKIPALL' to 'Y', so the Reorg is skipped. User response: No action is required. |
| NGTR233 | RESOURCES COULD NOT BE DRAINED DUE TO PENDING STATUS Explanation: A STOP will be issued for all resources governed by the current RW-REORG in order to perform the final switch phase. User response: No action is required. |
| NGTR234 | RESOURCES COULD NOT BE DRAINED - RUN ABORTED Explanation: An attempt to drain all claim classes on the resources governed by current RW-REORG has failed. The RW-REORG job fails before executing the final switch phase. User response: Rerun the RW-REORG JOB during a period when transaction activity is at minimum. |
| NGTR235 | REQUESTED STOP(NO) BUT PAGESET IS NOT DRAINABLE Explanation: REXX EXEC 'XRRGRWRO' has requested not to stop the pageset during the final switch phase of RW-REORG. The current status of the pageset does not allow this mode of processing. User response: Change the logic of the REXX EXEC such that if the 'DRAINABLE' variable is set to 'N', then assign a value of 'Y' to the 'STOP' variable. |
| NGTR236 | QUIESCE HAS TIMED OUT, RETRY IS IN PROGRESS.. Explanation: An attempt to quiesce objects governed by the RW-UTILITY has timed out and a retry will take place. The timeout value and the retry count are governed by the +QRETRY parameter. User response: If the RETRY is not successful, you may want to increase the time out interval by changing the +QRETRY parameter in file 'UTLPARMS' and rerunning you job again. |
| NGTR237 | DRAIN(ALL) HAS TIMED OUT, RETRY IS IN PROGRESS.. Explanation: An attempt to drain all class claimers on objects governed by the RW-UTILITY has timed out and a retry will take place. The timeout value and the retry count are governed by the +QRETRY parameter. User response: If the RETRY is not successful, you may want to increase the time out interval by changing the +QRETRY parameter in file 'UTLPARMS' and rerunning you job again. |
| NGTR238 | STATEMENT number-1 SKIPPED BECAUSE OBJECT SET WITH DEFINE NO. Explanation: The object about to be reorganized has been created with DEFINE NO. The VSAM data sets do not exist. The Reorg will be skipped. User response: No action is required. |
| NGTR239 | DSN(string-1) FAILED SERIALIZATION Explanation: An attempt to acquire exclusive control for a database object represented by the above dataset name has failed. The current RW-REORG utility statement will be terminated. User response: This serialization is performed after an internal database stop is issued for the object. If the dataset is allocated by an entity other than DB2, then free the resource and rerun your job again, otherwise contact BMC Customer Support. |
| NGTR240 | QUICKEXIT NOT ALLOWED, FASTSWITCH RENAMES PENDING. Explanation: An attempt is being made to cleanup (QUICKEXIT) after a failure. However, FASTSWITCH renames have started and must be completed before continuing. User response: RESTART the job so FASTSWITCH renames can complete |
| NGTR241 | DB2 AUTHORIZATION REJECT. Explanation: A utility verification has determined that the current user is not authorized by DB2 to perform the specified function. User response: The object is skipped. |
| NGTR242 | DRAINHELD TIMELIMIT EXCEEDED. Explanation: The current utility has exhausted the total number of seconds allowed to hold drains on objects currently being reorganized. As a result the utility fails without affecting the status of the DB2 objects. User response: No action is required. You may want to resubmit the Job at a later time when system activity is light. |
| NGTR243 | TABLESPACE tableSpaceName REORG SKIPPED - TOO SMALL Explanation: The named table space was not reorganized because the number of allocated pages was too low. Objects this small do not need to be reorganized. User response: No action is required. |
| NGTR244 | TABLESPACE tableSpaceName PART number-1 - REORG SKIPPED - TOO SMALL Explanation: The named table space was not reorganized because the number of allocated pages was too low. Objects this small do not need to be reorganized. User response: No action is required. |
| NGTR245 | INDEXSPACE indexSpaceName REORG SKIPPED - TOO SMALL Explanation: The named indexspace was not reorganized because the number of allocated pages was too low. Objects this small do not need to be reorganized. User response: No action is required. |
| NGTR246 | INDEXSPACE indexSpaceName PART number-1 - REORG SKIPPED - TOO SMALL Explanation: The named indexspace was not reorganized because the number of allocated pages was too low. Objects this small do not need to be reorganized. User response: No action is required. |
| NGTR247 | VSAM DATASET MISSING FOR TABLESPACE tablespaceName Explanation: The named table space does not have a VSAM dataset corresponding to the DB2 Catalog definition. User response: The object is skipped. |
| NGTR248 | VSAM DATASET MISSING FOR TABLESPACE tableSpaceName PART number-1 Explanation: The named table space does not have a VSAM dataset corresponding to the DB2 Catalog definition. User response: The object is skipped. |
| NGTR249 | VSAM DATASET MISSING FOR INDEXSPACE indexSpaceName Explanation: The named indexspace does not have a VSAM dataset corresponding to the DB2 Catalog definition. User response: The object is skipped. |
| NGTR250 | VSAM DATASET MISSING FOR INDEXSPACE indexSpaceName PART number-1 Explanation: The named indexspace does not have a VSAM dataset corresponding to the DB2 Catalog definition. User response: The object is skipped. |
| NGTR251 | OBJECT IS IN A RESTRICTED STATE objectName - UTILITY ABORTED. Explanation: The named object is in a restricted state - Utility cannot be done to restricted objects. User response: The object is skipped. |
| NGTR252 | OBJECT IS IN A RESTRICTED STATE objectName PART number-1 - UTILITY ABORTED. Explanation: The named object is in a restricted state - Utility cannot be done to restricted objects. User response: The object is skipped. |
| NGTR253 | REORG INDEX PENDING ALTERS NOT SUPPORTED Explanation: The REORG INDEX command in NGT Reorg does not materialize pending DDL changes for indexes; NGT Reorg materializes these changes on a REORG TABLESPACE. The REORG INDEX command in REORG PLUS does materialize pending DDL changes for indexes. User response: No action is required. |
| NGTR254 | REORG STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REORG process has started for the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR255 | REORG STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates the REORG process has started for the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR256 | REORG PHASE 1 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REORG process has completed the Phase 1 read on the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR257 | REORG PHASE 1 COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates the REORG process has completed the Phase 1 read on the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR258 | INDEX IS DEFERRED - PROCESSING ABORTED. Explanation: Indexes cannot be Reorganized if they are in a deferred state. User response: No action is required. |
| NGTR259 | EXCLUDES PART SPECIFICATION OUT OF RANGE FOR THIS INDEX Explanation: Either the index is non-partitioned or the part numbers specified on the EXCLUDE statement exceed the number of partitions. User response: The object is skipped. |
| NGTR260 | ALL PARTS EXCLUDED - OBJECT IS SKIPPED Explanation: EXCLUDE statement(s) eliminated all specified parts. User response: The object is skipped. |
| NGTR261 | BEGINNING REORG OF INDEXSPACE indexSpaceName Explanation: This message precedes a statistics message about the object about to be reorganized. User response: No action is required. |
| NGTR262 | BEGINNING REORG OF INDEXSPACE indexSpaceName PART number-1 Explanation: This message precedes a statistics message about the object about to be reorganized. User response: No action is required. |
| NGTR263 | ACCESS TO SPACE indexSpaceName ABORTED- OBJECT IN RESTRICTED STATE. Explanation: NGT Reorg did not reorganize the indicated index because the index is in a pending state such as rebuild pending (RBDP). User response: If the index is in RBDP status, consider changing the REBUILDIX option to enable NGT Reorg to rebuild the index during the reorganization. Otherwise, use your standard method to remove the pending state. Rerun the reorganization. |
| NGTR264 | REORG STARTING FOR INDEXSPACE indexSpaceName PART number-1 Explanation: This message indicates the REORG process has started for the named indexspace. The part number is listed if this is a partitioned index. User response: No action is required. |
| NGTR265 | REORG STARTING FOR INDEXSPACE indexSpaceName Explanation: This message indicates the REORG process has started for the named indexspace. The part number is listed if this is a partitioned index. User response: No action is required. |
| NGTR266 | REORG COMPLETED FOR INDEXSPACE indexSpaceName PART number-1 Explanation: This message indicates the REORG process has completed for the named indexspace. The part number is listed if this is a partitioned index. User response: No action is required. |
| NGTR267 | REORG COMPLETED FOR INDEXSPACE indexSpaceName Explanation: This message indicates the REORG process has completed for the named indexspace. The part number is listed if this is a partitioned index. User response: No action is required. |
| NGTR268 | REORG SKIPPED FOR INDEXSPACE indexSpaceName PART number-1 Explanation: This message indicates the REORG process has completed for the named indexspace. The part number is listed if this is a partitioned index. The REORG was skipped after the Read phase because of a return code from XRRGINIT. User response: No action is required. |
| NGTR269 | REORG SKIPPED FOR INDEXSPACE indexSpaceName Explanation: This message indicates the REORG process has completed for the named indexspace. The part number is listed if this is a partitioned index. The REORG was skipped after the Read phase because of a return code from XRRGINIT. User response: No action is required. |
| NGTR270 | TABLESPACE IS DEFERRED - PROCESSING ABORTED Explanation: REORG cannot process a DEFERRED object User response: Load some rows into the table space to DEFINE all the objects. |
| NGTR271 | AN INDEX IS DEFERRED - PROCESSING ABORTED Explanation: REORG cannot process a DEFERRED object User response: Load some rows into the table space to DEFINE all the objects. |
| NGTR272 | REORG TABLESPACE tableSpaceName PART number-1 - READING CLIX (SPACE) string-3 Explanation: This message signals the start of a CLIX read for the named table space. User response: No action is required. |
| NGTR273 | REORG TABLESPACE tableSpaceName - READING CLIX (SPACE) string-3 Explanation: This message signals the start of a CLIX read for the named table space. User response: No action is required. |
| NGTR274 | REORG PHASE 1 COMPLETED FOR TS tableSpaceName PART number-1 - CLIX string-3 Explanation: This message indicates the REORG process has completed the Phase 1 read on the named CLIX indexspace. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR275 | REORG PHASE 1 COMPLETED FOR TS tableSpaceName - CLIX string-3 Explanation: This message indicates the REORG process has completed the Phase 1 read on the named CLIX indexspace. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR276 | REORG PHASE 2 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that REORG has completed the Phase 1 reads and is starting the Logical Reorg. User response: No action is required. |
| NGTR277 | REORG PHASE 2 STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates that REORG has completed the Phase 1 reads and is starting the Logical Reorg. User response: No action is required. |
| NGTR278 | REORG PHASE 2 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REORG process has completed the Phase 2 Logical Reorg processing. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR279 | REORG PHASE 2 COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates the REORG process has completed the Phase 2 Logical Reorg processing. The part number is listed if this is a partitioned table space. User response: No action is required. |
| NGTR280 | REORG PHASE 3 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space is beginning Phase 3 - read and rewrite. User response: No action is required. |
| NGTR281 | REORG PHASE 3 STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space is beginning Phase 3 - read and rewrite. User response: No action is required. |
| NGTR282 | REORG PHASE 3 STARTING FOR TS tableSpaceName PART number-1 - IXSPACE indexSpaceName Explanation: This message indicates that the named indexspace is beginning Phase 3 - read and rewrite. User response: No action is required. |
| NGTR283 | REORG PHASE 3 STARTING FOR TS tableSpaceName - IXSPACE indexSpaceName Explanation: This message indicates that the named indexspace is beginning Phase 3 - read and rewrite. User response: No action is required. |
| NGTR284 | REORG PHASE 3 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space write is complete. User response: No action is required. |
| NGTR285 | REORG PHASE 3 COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space write is complete. User response: No action is required. |
| NGTR286 | REORG PHASE 3 COMPLETED FOR TS tableSpaceName PART number-1 - IXSPACE string-3 Explanation: This message indicates that the indexspace write is complete. User response: No action is required. |
| NGTR287 | REORG PHASE 3 COMPLETED FOR TS tableSpaceName - IXSPACE string-3 Explanation: This message indicates that the indexspace write is complete. User response: No action is required. |
| NGTR288 | REORG PHASE 4 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space is beginning Phase 4 - Log Apply. User response: No action is required. |
| NGTR289 | REORG PHASE 4 STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space is beginning Phase 4 - Log Apply. User response: No action is required. |
| NGTR290 | REORG PHASE 4 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space Log Apply is complete. User response: No action is required. |
NGTR291 | REORG PHASE 4 COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space Log Apply is complete. User response: No action is required. |
| NGTR292 | REORG TS COPY STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space is beginning the COPY phase. User response: No action is required. |
| NGTR293 | REORG TS COPY STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space is beginning the COPY phase. User response: No action is required. |
| NGTR294 | REORG TS COPY COMPLETED FOR TS tableSpaceName PART number-1 Explanation: This message indicates that the table space COPY is complete. User response: No action is required. |
| NGTR295 | REORG TS COPY COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space COPY is complete. User response: No action is required. |
| NGTR296 | ALL PARTS SKIPPED - NPI IS NOT PROCESSED. Explanation: This message indicates that the NPI will not be reorganized because all the partitions specified to be reorganized were skipped. User response: No action is required. |
| NGTR297 | string-1 PASSWORD TAKEN FROM LOCAL RX10 MEMBER. Explanation: The password specified was found in the Local's (DB2 Subsystem's) RX10 member and will override any password specified in the Global (0GBL) RX10 member. User response: No action is required. |
| NGTR298 | XRRGINIT RETURN CODE IGNORED. Explanation: XRRGINIT may result in additional problems during processing so BMC recommends the use of RTMAN to avoid such. User response: USE RTMAN, INSTEAD OF XRRGINIT EXIT. |
| NGTR299 | string-1.string-2 (number-1) number-2 PAGES EXCEEDS MAXIMUM ALLOWABLE SIZE OF number-3 PAGES Explanation: REORG INDEX will process data sets up to a maximum size. The indexspace exceeded that maximum. The value in parentheses is the partition number. User response: Contact BMC Customer Support. |
Comments