Messages NGTC000 through NGTC999

OUTPUT THRESHOLD COMPARISON: OBJECT SIZE numberOfPages (IN PAGES) VERSUS THRESHOLD numberOfPages

Explanation: This message displays a comparison between the output object size and the limit specified in the THRESHOLD option.

User response: No action is required.

CONNECTING TO DB2 SUBSYSTEM subsystemID USING ID userID

Explanation: The utility is connecting to the indicated DB2 subsystem by using the indicated user ID. This user ID is the value of the +SQLID parameter.

User response: No action is required.

OUTPUT THRESHOLD EXCEEDED: USING OUTPUT outputName FOR OBJECT

Explanation: The threshold specified on the OUTPUT statement was reached so the outputName OUTPUT statement is used for the object.

User response: No action is required.

DISCONNECTING FROM DB2 SUBSYSTEM string-1 string-2

Explanation: The output object size exceeds the limit specified in the THRESHOLD option, so the NGT product will use the specified OUTPUT option.

User response: No action is required.

FAILED TO OPEN FILE string-1

Explanation: Open failed for the dataset named in the //string-1 DD statement.

User response: Check system messages for any indications why this open has failed. Contact BMC Support or your local representative.

IMAGE COPY STARTED ON LOGICAL FILE NO. number-1

Explanation: The current task has started the image copy for the specified file.

User response: No action is required.

IMAGE COPY COMPLETED ON LOGICAL FILE NO. number-1

Explanation: The current task has successfully completed the image copy of the specified file.

User response: No action is required.

IMAGE COPY DATASET CLOSED. TOTAL RECORDS= number-1

Explanation: This message indicates that the image copy data set has been closed successfully and that it contains number-1 4K records.

User response: No action is required.

DYNAMIC ALLOCATION FAILURE FOR TABLESPACE string-1.string-2

Explanation: An attempt to dynamically allocate the dataset for table space string-1 has failed.

User response: Refer to the reason indicated in the message following this one. Attempt to correct the error, or contact BMC Support or your local representative.

OPEN FAILED FOR TABLESPACE

Explanation: The Tablespace dataset open failed. A previous message should describe the problem. It may be a VSAM error. Check the system messages for any errors that may help to diagnose the problem.

User response: If you cannot find any system messages, contact BMC Support or your local representative.

TABLESPACE string-1.string-2 HIGH-USED RBA IS ZERO

Explanation: The Tablespace dataset is found empty. That is, its High-Used RBA is zero. It is not possible to copy an empty data set. String-1 is the tablespace name.

User response: This is a terminating error for the table space. The table space must be recovered before an image copy.

string-1 SPACE OPEN - DSN=string-2

Explanation: String-1 names the VSAM data set that is being opened. This message is displayed after the dataset has been successfully opened for image copy. The dataset name is followed by the number of pages in the dataset up through the High-Used RBA.

User response: No action is required.

READ ERROR IN TABLESPACE, RPLFDBK=(hexstring-1)

Explanation: A table space data set read failed. X'hexstring-1' is the feedback code in hex from the access method. There should be a previous message describing the problem. Check the system messages for any errors that might help to diagnose the problem.

User response: If you cannot find any system messages, contact BMC Support or your local representative.

BROKEN PAGE IN TABLESPACE, PAGE number-1 (hexstring-1)

Explanation: Page number number-1 (X'hexstring-1') is marked by DB2 as broken.

User response: This is a terminating error. Attempt to recover the broken page before running the copy utility.

INCONSISTENT PAGE IN TABLESPACE, PAGE number-1, PGCOMB=hexstring-1, PGTAIL=hexstring-2

Explanation: Page number number-1 is inconsistent because the PGCOMB and PGTAIL values do not match.

User response: This is a terminating error. Attempt to recover this page before running the copy utility.

DSN1COPY RAN AGAINST THIS TABLESPACE

Explanation: A DB2 page(s) indicate that the DSN1COPY utility was run against this space.

User response: No action is required.

UPDATE PAGE ERROR IN TABLESPACE, RPLFDBK=(hexstring-1)

Explanation: A tablespace data set page update failed. X'hexstring-1' is the feedback code from the access method. There should be a previous message describing the problem. Check the system messages for any errors that may help to diagnose the problem.

User response: If you cannot find any system messages, contact BMC Support or your local representative.

string-1 CLOSED. CTL=number-1, DATA=number-2, EMPTY=number-3, CHG=number-4, UPD=number-5, %CH=number-6

Explanation: This message is issued after the table space has been successfully read. It shows the numbers of control pages, data pages, empty pages, changed pages and updated pages, and the percentage of changed pages.

User response: No action is required.

number-1 CONTROL PAGE(S) UPDATED SUCCESSFULLY

Explanation: This message is issued after successful update of all control pages. Number-1 is the number of updated pages.

User response: No action is required.

ABOVE FUNCTION FAILED, COPY TERMINATED

Explanation: This message is issued after a failure to identify the task which requested a specific function.

User response: No action is required.

THE SPECIFIED PARTITION (number-1) DOES NOT EXIST

Explanation: The copy table space specification contains a PART number greater than the maximum defined for the table space.

User response: Correct the part no and rerun the copy.

INCONSISTENT SPACEMAP PAGE (hexstring-1) ,CATALOG SEGSIZE=hexstring-2, PAGE SEGSIZE=hexstring-3

Explanation: A discrepancy was detected between the DB2 catalog and the tablespace space map page whose number is X'hexstring-1'. The catalog segment size is X'hexstring-2', and the page segment size is X'hexstring-3'.

User response: This is a terminating error, attempt to recover this page before running the copy utility.

INCONSISTENT HEADER PAGE (hexstring-1), CATALOG DBID=hexstring-2, PAGE DBID=hexstring-3

Explanation: A discrepancy was detected between the DB2 catalog and the tablespace header page whose number is X'hexstring-1'. The catalog DBID is X'hexstring-2', and the header page DBID is X' hexstring-3 '.

User response: This is a terminating error. Attempt to recover the tablespace before running the copy utility.

SQL ERROR CODE - number-1 (hexstring-1), SQL TERMINATED

Explanation: This message identifies the SQL statement as well as the SQL error returned from DB2. Number-1 is the SQL code value in decimal, and X'hexstring-1' is the SQL code value in hex.

User response: Check the SQL code in the DB2 Messages and Codes. If the code does not seem appropriate, contact BMC Support or your local representative.

DB2Message

Explanation: This is a line of output from DB2 commands and utilities. It is an uncompacted form of message NGTR808. To view the compacted format, do not specify +DSCRL(000999,9) in UTLPARMS. Refer to IBM DB2 message DSNT397I for an explanation of the information.

User response: No action is required.

string-1 DD STATEMENT IS MISSING, STMT NO. number-1

Explanation: Either string-1 is specifically referenced in the COPY statement or the DDname was generated because the +COPIES parameter specified more copies than on the statement. No //string-1 DD statement is in the JCL.

User response: Supply a //string-1 DD statement for this copy.

ERROR ON DD string-1 IN COPY STMT NO. number-1, IT IS NOT A SEQUENTIAL DATASET

Explanation: The //string-1 DD statement must reference a sequential non-temporary dataset.

User response: Change the string-1 DD statement to reference a sequential file.

ERROR ON DD string-1 IN COPY STMT NO. number-1, IT IS A SYSIN/SYSOUT DATASET

Explanation: The //string-1 DD statement must reference a sequential non-temporary dataset.

User response: Change the string-1 DD statement to reference a sequential file.

string-1 DDNAME USED IN COPY STMTS number-1 AND number-2

Explanation: The //string-1 DD statement is referenced by more than one COPY statement.

User response: Correct the COPY statements. Each DD can be referenced by only one COPY statement.

DUPLICATE DSNAME USED IN DD string-1 IN COPY STMT number-1 AND IN DD string-2 IN COPY STMT number-2

Explanation: The //string-1 DD statement is referenced by more than on COPY statement.

User response: Correct the COPY statements. Each DD can be referenced by only one COPY statement.

....DDNAME string-1, FSEQ number-1 IN COPY STMT number-2

Explanation: This message shows the detailed information for other messages, such as NGTC036. string-1 is the DD name, number-1 is the relative file number on the tape and number-2 is the COPY statement number.

User response: This message is informational only.

DUPLICATE FILE ON TAPE

Explanation: The same file sequence number is specified for more than one COPY on a tape. Message NGTC035 is issued for each.

User response: Correct the COPY statements. Each file on tape can be referenced by only one COPY statement.

DB2 CURRENT FUNCTION LEVEL IS VxxRxMxxx

Explanation: You are running on the indicated DB2 version, release, and function level.

User response: No action is required.

DB2 HIGHEST ACTIVATED FUNCTION LEVEL IS VxxRxMxxx

Explanation: The indicated DB2 function level is the highest function level for which the subsystem has been activated.

User response: No action is required.

DB2 CATALOG LEVEL IS VxxRxMxxx

Explanation: The DB2 catalog is at the indicated DB2 version, release, and function level.

User response: No action is required.

DB2 SERVICES TASK INITIALIZATION COMPLETE FOR string-1 string-2

Explanation: This message indicates that the current task has successfully connected to the DB2 subsystem string-1 whose version is string-2. A version of #### indicates that the program is not running APF-authorized.

User response: No action is required.

DYNAMIC ALLOCATION FAILURE FOR DDNAME ddname

Explanation: An attempt to dynamically allocate a new temporary data set for the indicated DD name failed. This allocation is required in order to execute the DSNUTILB utility.

User response: Check for the following possible problems:

• If the indicated DD name is SYSIN, check for parameters that were suppressed by /* in column 1. MVS has interpreted the /* as an end-of-file indicator for the parameter library. Any subsequent parameters are assigned to an MVS-allocated SYSIN data set and the utility freed the original SYSIN data set. You can correct this by deleting or shifting the lines so that /* is no longer in column 1.

• Ensure that the unit name specified in +WORKUNIT is valid.

UNABLE TO OPEN SYSIN

Explanation: An attempt to open the temporary data set previously allocated under the ddname 'SYSIN' has failed. This dataset is required for the execution of the DSNUTILB utility.

User response: Refer to the reason indicated in system message IEC161I. Attempt to correct the error, or contact BMC Support or your local representative.

UNABLE TO OPEN SYSPRINT

Explanation: An attempt to open the temporary data set previously allocated under the ddname 'SYSPRINT' has failed. This dataset is used by the DSNUTILB utility.

User response: Refer to the reason indicated in system message IEC161I. Attempt to correct the error, or contact BMC Support or your local representative.

ALL IMAGE COPY WRITERS FAILED, COPY TERMINATED

Explanation: All image copy writers for the current table space have failed. The existing copy function is terminated.

User response: Refer to the reason indicated in the message prior to this message. Attempt to correct the error, or contact BMC Support or your local representative.

PAGE ANALYSIS COMPLETED %CHANGED=number-1.0

Explanation: The tablespace modified page analysis has completed successfully. Number-1 indicates the percentage of changed pages in the tablespace.

User response: No action is required.

DUPLICATE DATASET IN SYSIBM.SYSCOPY, DSN=string-1. STMT number-1

Explanation: The copy statement whose number is number-1 references a cataloged image copy data set whose name already exists in the DB2 catalog table SYSIBM.SYSCOPY.

User response: Correct the dataset name referenced by the copy statement and rerun the job.

FULL(YES) CHANGED TO FULL(NO), +FULLIFCHGD(number-1) > number-2.0

Explanation: The full image copy of the current table space will be converted to incremental image copy because the percentage of changed pages number-2 is less than the threshold number-1.

User response: No action is required.

FULL(NO) CHANGED TO FULL(YES), +FULLIFCHGD(number-1) < number-2.0

Explanation: The incremental image copy of the current table space will be converted to full image copy because the percentage of changed pages number-2 exceeds the threshold number-1.

User response: No action is required.

COPY TASK(string-1) STARTED

Explanation: This message is issued by the copy task manager to identify the task which will process copy statements. String-1 is the identifier of the new task. Messages issued by the new task will be tagged with this identifier.

User response: No action is required.

IMAGE COPY TASK(string-1) STARTED

Explanation: The indicated copy task has started.

User response: No action is required.

'GET INFO' FAILED FOR TABLESPACE - ERROR CODE number-1

Explanation: LISTCAT failed with return code number-1 .

User response: It is possible the data set does not exist. A following message names the dataset.

DATASET NAME - string-1

Explanation: This message names the dataset that is the object of a previous message.

User response: No action is required.

FULL(NO) CHANGED TO FULL(YES), FULL(NO) NOT ALLOWED

Explanation: The incremental image copy of the current table space will be converted to full image copy because incremental image copy is disallowed by DB2 rules.

User response: No action is required.

FULL(NO) CHANGED TO FULL(YES), BECAUSE OF RESTART

Explanation: The incremental image copy of the current table space will be converted to full image copy because incremental image copy is disallowed during restart.

User response: No action is required.

NO OUTPUT FROM DB2 COMMAND

Explanation: The DB2 command displayed in message NGTC028 either returned no output or contains a DB2 error message (DSN9nn).

User response: Any output received from DB2 will be printed. Look up the DSN9nnn message in the DB2 Messages and Codes manual. If you do not understand why there is a problem, contact BMC Support or your local representative.

DISPLAY COMMAND MESSAGE 'DSNT362I' FORMAT ERROR

Explanation: The output from a DB2 display command contained DB2 message 'DSNT362I' in an unexpected format.

User response: Any output received from DB2 will be printed. Contact BMC Support or your local representative.

DISPLAY COMMAND MESSAGE 'DSNT362I' NOT FOUND

Explanation: The output from a DB2 display command did not contain message identifier 'DSNT362I'.

User response: Any output received from DB2 will be printed. Contact BMC Support or your local representative.

THE FOLLOWING DATA SET IS MIGRATED OR NOT FOUND, THE COPY OPERATION HAS BEEN SKIPPED

Explanation: Locate for the data set failed because it was migrated or not found and the Tablespace/Indexspace was created with 'DEFINE NO'.

User response: The copy operation will be skipped for the objects associated with the data set.

SPACE string-1.string-2 number-1 IS RESTRICTED BY DB2

Explanation: Processing of the current space will not start. It is in one of the following states: Recovery-Pending, Restarting, Indoubt, or Check-Pending. This can also occur if the space is in status REORGP, STOP, UTRO, UTUT or UTRW.

User response: The appropriate DB2 utility must be used to correct the space status.

IMAGE COPY TASK ABENDED CODE=hexstring-1, RETRY IN PROGRESS

Explanation: This message is issued whenever an image copy task encounters an abend involving OPEN/CLOSE/EOV processing. X'hexstring-1' is the abend code. The current unit of work will be bypassed because +ONERROR(CONTINUE) is specified.

User response: No action is required.

SYSCOPY POST FOR string-1.string-2 DSNUM number-1 ICTYPE(string-3) START_RBA(hexstring-1) WAS SUCCESSFUL

Explanation: This message indicates that a record was successfully inserted in table SYSIBM.SYSCOPY on behalf of tablespace string-1. The column values of DSNUM, ICTYPE and START_RBA are string-2 string-3 X'hexstring-1'.

User response: No action is required.

TABLESPACE SYNCHRONIZATION STARTED

Explanation: All tablespaces specified in the input stream will be synchronized and placed in a state as specified by the +BEFOREACC parameter. This process is done only if +SYNC(ALL) is in effect.

User response: No action is required.

TABLESPACE SYNCHRONIZATION FAILED, RESETING SPACES

Explanation: A synchronization error occurred, the usual cause being a QUIESCE failure. As a result, all tablespaces will be reset to their original state at the start of the utility.

User response: Examine the SYSERROR dataset in order to determine the cause of the error. Attempt to rerun the JOB by specifying +QBEFORE(INDIVIDUALLY), or +SYNC(INDIVIDUALLY) or both. ('INDIVIDUALLY' may be abbreviated 'I'.)

TABLESPACE SYNCHRONIZATION ENDED

Explanation: This message is issued to mark the end of the process described by the previous NGTC063 message.

User response: No action is required.

-STOP DID NOT TAKE EFFECT FOR SOME SPACES WITHIN RETRY LIMIT - RUN ABORTED

Explanation: A -STOP was issued for the spaces to be processed. -DISPLAY commands were issued at intervals as specified in the +DSCRL parameter. After repeating the command the specified number of times, the space was still not in a stopped state.

User response: Determine why the space(s) cannot be stopped. An application may be processing against them. Rerun the utility when the space(s) can be stopped.

QUIESCE DID NOT TAKE EFFECT FOR SOME SPACES WITHIN RETRY LIMIT

Explanation: A QUIESCE was issued for the spaces to be processed but failed. The QUIESCE was retried at intervals as specified in the +QRETRY parameter. After repeating the command the specified number of times, a QUIESCE point can not be obtained.

User response: Determine why the space(s) cannot be quiesced. For example, it may be that an application is processing against them. Rerun the utility when the space(s) can be quiesced.

DATA BASE DSNDB07 CANNOT BE COPIED

Explanation: The DB2 temporary data base, DSNDB07, cannot be copied.

User response: Change the data base name.

IMAGE COPY REQUIRED FOR string-1 SPACE string-2.string-3 string-4

Explanation: This message is issued after successful LOAD of a TableSpace or a copyable IndexSpace. It indicates that the OBJECT may have been placed in COPY-PENDING status. This status will remain in effect until a full image copy is performed.

User response: Take a full image copy of the above named object string-1.string-2. Note: COPY-PENDING will not be set if +COPYPENDING(NO) is in effect

PASSING CONTROL TO IBM COPY

Explanation: This message is issued to indicate that the current object will be copied using the IBM utility 'DSNUTILB'. This can occur if the Tablespace is DSNDB06.SYSCOPY or if you are not licensed to run NGT Copy.

User response: No action is required.

INCREMENTAL IMAGE COPY IS DISALLOWED

Explanation: Incremental image copy is disallowed because either the table space is in COPY-PENDING status or a full image copy does not exist. The current copy will be terminated with a return code of 8.

User response: Change the 'FULL NO' specification on the COPY statement to 'FULL YES' and rerun the job. Alternatively, change the parameter +FULLIFCHGD(-2) to +FULLIFCHGD(-1) and rerun the job.

NO COPIES WILL BE PRODUCED, BECAUSE +COPIES(-1)

Explanation: The specification '+COPIES(-1)' forces NGT Copy to become non-operational. That is, only +BEFOREACC() and +AFTERACC() parameters are honored with the +SYNC(ALLATONCE) global parameter.

User response: No action is required.

MODIFY BITS WILL NOT BE RESET, DUE TO string-1

Explanation: The specification '+RESETMOD(YES)' or '+RESETMOD(FULL)' was not honored for the reason specified by string-1

User response: No action is required.

QUIESCE UTILITY OUTPUT MESSAGE FORMAT ERROR

Explanation: The output from a DB2 QUIESCE Utility contained messages in an unexpected format.

User response: Any output received from DB2 will be printed. Contact BMC Support or your local representative.

COPY WILL NOT BE TAKEN: +NOCHANGE(DELETE)

Explanation: According to the space map pages in the current tablespace, there have been no changes since the most recent image copy. Given that +NOCHANGE(DELETE) has been specified, this will cause the copy to be skipped and the imagecopy dataset to be deleted.

User response: No action is required.

FULL(NO) CHANGED TO FULL(YES): +INCRMAX(number-1) <= number-2

Explanation: The incremental image copy of the current table space will be converted to full image copy because the number of incrementals number-2 exceeds the threshold number-1.

User response: No action is required.

FULL COPY WILL BE DONE: +FULLIFDAYS(number-1) < number-2

Explanation: Regardless of the specification of FULL YES|NO on the COPY control statement, a local FULL image copy will be performed because the number of days since the most recent full copy number-2 exceeds the threshold number-1.

User response: No action is required.

+SYNC(ALLATONCE) FAILED. CHANGING TO +SYNC(INDIVIDUALLY)

Explanation: A synchronization error occurred, the usual cause of which is a QUIESCE failure. As a result, the +SYNC(A) parameter will be changed to +SYNC(I) so that the QUIESCE can be retried at the object level.

User response: No action is required.

REXX EXIT 'XCPYDYNM' ENCOUNTERED AN ERROR DURING ITS EXECUTION

Explanation: The REXX exit XCPYDYNM encountered an error during its execution.

User response: Check the XCPYDYNM REXX exec output to determine the cause of the error. Fix the error and rerun the utility. If you still receive this error, contact BMC Support.

DB2 SERVICES TASK IS NOT ACTIVE. #DB2REQ TERMINATED

Explanation: This message indicates that the DB2I services task responsible for carrying out the execution of DB2 commands and utilities had abnormally terminated. The current request will also be terminated.

User response: Check for a prior message indicating the reason for the abnormal termination of the DB2I services task. Correct the error and rerun the JOB.

NO RESTART CONDITION (code) DETECTED

Explanation: The copy restart processor has detected a condition that does not allow you to restart the current utility. The indicated code describes the reason as follows:

• 1—Unit type change

• 2—Disposition change

• 3—+POST(ALLATONCE) and DD third DISP is DELETE/UNCATLG

• 4—Label change

• 5—non-GDG DSN change

• 6—GDG base name change

• 7—GDG base name change

• 8—Not cataloged

• 9—DD missing 

User response: No action is required. However, if you want to restart the copy utility, do not change the JCL before submitting the restart job.

IMAGE COPY DATASET IS EMPTY, RETURN CODE=hexstring-1

Explanation: The current task has detected that the tablespace had not changed since the last image copy. The result of this incremental image copy will be an empty dataset. The dataset itself will not be deleted due to +NOCHANGE(KEEP).

User response: No action is required.

VOLUME string-1 IS NOT MOUNTED FOR DSN(string-2)

Explanation: The copy task manager has detected that the space whose data set name is string-2 resides on the volume with volser string-1 However, a UCBSCAN for this volume resulted in a not found condition.

User response: Ensure that the reported volser is mounted on the system. If the volser indicates that it is migrated by a product other than HSM, contact BMC Support or your local representative.

REXX EXIT 'string' NOT FOUND

Explanation: The specified COPY REXX exit was not found. If the missing REXX exit is XCPYDYNM, the COPY and the REORG TABLESPACE utilities require the existence of the XCPYDYNM REXX exit in the library specified in the DDname CDBEXEC or NGTAUTO.

User response: If the missing REXX exit is XCPYDYNM, this is a terminating error. Otherwise, no action is required.

CHANGING +BEFOREACC TO 'STOP' DUE TO +DISP(OLD)

Explanation: The +BEFOREACC parameter for all NGT Utilities products has been changed to 'STOP'. This change will affect the current job only and is done because it conflicts with +DISP(OLD) global parameter.

User response: No action is required.

COPY TASK IS WAITING FOR WORK

Explanation: The current task has gone idle. It will wait until work becomes ready.

User response: No action is required.

STMT number-1 ON string-1, UNIT=hexstring-1, hexstring-2

Explanation: The copy task manager has queued the copy statement No. designated by number-1 to the copy task whose ID is string-2 This task will be the owner of the device unit addresses specified by X'hexstring-3'

User response: No action is required.

STMT number-1 OFF string-1, UNIT=hexstring-1, hexstring-2

Explanation: The copy task manager has dequeued the copy statement No. designated by number-1 from the copy task whose ID is string-2 This task is no longer the owner of the devices specified by X'hexstring-3' for this statement.

User response: No action is required.

COPYDDN string-1 MUST NOT BE ALLOCATED FOR WILD CARD PROCESSING

Explanation: A COPY statement having wild cards and yielding more than one table space can not have a permanently allocated DD statement.

User response: Remove the above named DD statement from the job or remove the wild cards from the COPY statement.

TASK(copyTaskID) PAGES=numberOf4KPages CPU=time ELAPSED=time WAITS=numberOfWaits STMT=numberOfStatements SPEED=speed

Explanation: This message summarizes statistics for the indicated copy task as follows:

• PAGES indicates the total number of input 4-KB pages that were processed.

• CPU indicates the time, in seconds, to include all writer tasks.

• ELAPSED indicates the elapsed time in seconds.

• WAITS indicates the number of times the task went into a wait for work.

• STMT indicates the total number of copy statements that were processed. 

User response: No action is required.

COPY TASK MANAGER ENTERING A WAIT DUE TO 'reason'

Explanation: The copy task manager is entering a wait for the indicated reason, as follows:

• CONFLICT indicates that there is a device conflict.

• SHORTAGE indicates that there is a control block shortage.

• TASK END indicates that there is no more work to schedule. 

User response: No action is required.

CONTIG BELOW=number-1 K TOTAL BELOW=number-2 K CONTIG ABOVE=number-3 K TOTAL ABOVE=number-4 K

Explanation: This information message shows total and contiguous available virtual storage below and above the 16M line.

User response: No action is required.

SOME DDNAMES SPECIFIED ARE NOT INCLUDED IN THE JCL

Explanation: The Automation Exit XCPYDYNM cannot be invoked, but one or more DDnames from the COPY statement are not in the JCL. The job will fail.

User response: No action is required.

PAGE NUMBERS ARE NOT ASCENDING PAGE number-1 (hexstring-1)

Explanation: Page number number-1 (X'hexstring-1') is not higher than the previous page number.

User response: This is a terminating error and indicates a serious problem with the object. Contact BMC Support or your local representative.

DB2Message

Explanation: This is a trace message issued to show the results of a DB2 utility or command.

User response: No action is required.

CPUTIME USED FOR(string-1) = string-2 SECONDS

Explanation: This is a trace message issued to summary CPU time used during a function.

User response: No action is required.

IRLMRWT TIMEOUT VALUE : nnnn SECONDS

Explanation: nnnn is the IRLMRWT time value represented in seconds. A runtime instance of this message is as follows:

10:32:23.17 DB2I.CPYDBSVC NGTC098 IRLMRWT TIMEOUT VALUE : 30 SECONDS.

This message is always printed to the CDBPRINT output file. .

User response: This is an information-only message that requires no further action.

IMAGE COPY COMPLETE - ELAPSED TIME hexstring-1:hexstring-2:hexstring-3

Explanation: This message is issued to mark the end of the copy process for the current task. It shows the elapsed time (HH:MM:SS) in decimal since the start of the process, which was indicated by the previous message NGTC000.

User response: No action is required.

#ERREL MESSAGE TEXT

Explanation: The message will be on SYSERROR - it is an internal logic error.

User response: If the message does not indicate a solution, contact BMC Support.

CONSISTENCY POINT RBA rbaValue IN USE BY JOBNAME(jobID)

Explanation: While attempting to make a consistent point-in-time connection for the table space of the table being unloaded, BMC AMI Unload found an existing connection for the table space. The message specifies the 10-byte RBA value and job ID for the existing consistency point. The job receiving this message terminates if +POC_SHARE(FAIL) is set in ULDPARMS.

User response: No action is required.

CDB/SUBSYSTEM CONNECTION BEING FAILED DUE TO +POC_SHARE(FAIL)

Explanation: The +POC_SHARE(FAIL) parameter in the BMC AMI Unload ULDPARMS does not allow two jobs to run concurrently on the same table space and the same LPAR. This message appears if an existing connection was found for this table space. The job receiving this message gets a nonzero return code and this second concurrent unload is put on the error queue.

User response: No action is required.

CDBSS CONNECTION BEING SHARED DUE TO +POC_SHARE(YES)

Explanation: The +POC_SHARE(YES) parameter in the BMC AMI Unload ULDPARMS allow two jobs to run concurrently on the same table space and the same LPAR. This message appears if an existing connection was found for this table space.

User response: No action is required.

INVALID KEYWORD 'string-1'

Explanation: The keyword named in string-1 is invalid for COPY.

User response: Correct the statement and rerun.

KEYWORD 'string-1' HAS INVALID PARAMETER 'string-2'

Explanation: The parameter named in string-2 is invalid for the keyword named in string-1.

User response: Correct the statement and rerun. Refer to the syntax diagrams in the documentation for valid keyword parameters.

FSEQ CAN BE CHANGED ONLY FOR TAPE MEDIA AND MUST BE '1'

Explanation: FSEQ must be 0 for DASD copies. For TAPE (or VTS) copies, a value of '1' indicates to start a new tape volume. Otherwise the value passed will be the next file sequence number on the tape.

User response: Correct the text and rerun.

TAPEDD CANNOT BE CHANGED IN THE XCPYDYNM EXIT - USE XCPYMDIA

Explanation: TAPEDD can be set only by the XCPYMDIA REXX exit. Use the exit to set the TYPEDD.

User response: Create a XCPYMDIA exit (all the same variables as XCPYDYNM) or do not change TYPEDD in XCPYDYNM.

THE KEYWORD 'string-1' WAS SPECIFIED MORE THAN ONCE

Explanation: The text string in string-1 is a keyword that has been previously specified in the same statement.

User response: Correct the text and rerun.

THE KEYWORD 'TABLESPACE' WAS EXPECTED AFTER 'COPY'. KEYWORD FOUND WAS 'string-1'

Explanation: The text string in string-1 was supposed to be 'TABLESPACE'.

User response: Correct the text and rerun.

THE 'COPY' KEYWORD MUST BE FIRST. 'string-1' IS NOT VALID

Explanation: The text string in string-1 was supposed to be 'TABLESPACE'.

User response: Correct the text and rerun.

INSUFFICIENT CONTROL STATEMENT RECORDS PASSED FOR UTILITY STATEMENT number-1

Explanation: The COPY utility statement named in number-1 does not have the minimum required keywords for the utility.

User response: Correct the text and rerun.

CURRENT KEYWORD 'string-1' IS MISSING PARAMETERS

Explanation: The current keyword being parsed as shown in string-1 is incomplete. Required parameter(s) is(are) missing.

User response: Complete the statement and rerun.

THE DSNUM VALUE 'string-1' IS NOT A VALID VALUE

Explanation: The value supplied for DSNUM must be the value ALL or it must be a valid number between 1 and 64, inclusive.

User response: Complete the statement and rerun.

GDG DATA SET NAME NOT VALID FOR A FLASHCOPY DATA SET

Explanation: The REXX variable DSNAME set by the REXX exit contains an incorrect data set name. 

User response: Correct the REXX exit and rerun the job.

'string-1' DDNAME IS BAD, DDNAME IS 'string-2', LENGTH IS number-1

Explanation: A COPYDDN or RECOVERYDDN DDNAME value is invalid. This could be due to a missing DDNAME, or too many DDNAMES, or the length of a DDNAME. String-2 is the DDNAME in question and number-1 is the DDNAME length.

User response: Correct the COPYDDN or RECOVERYDDN DDNAME or both, and rerun.

DDNAME IS MISSING FOR KEYWORD 'string-1'

Explanation: A COPYDDN or RECOVERYDDN DDNAME value is missing. This could be due to a misplaced comma or a missing DDNAME. String-1 is the keyword associated with the DDNAME.

User response: Correct the COPYDDN or RECOVERYDDN DDNAME or both, and rerun.

'DSNAME' VALUE NOT SET BY REXX EXIT 'XCPYDYNM'

Explanation: The REXX variable 'DSNAME' was not set by the REXX exit 'XCPYDYNM' for dynamic allocation of image copy dd statement.

User response: Correct the REXX EXEC and rerun the JOB.

'FULL' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'FULL' was incorrectly set by the REXX exit to a value other than 'Y' or 'N'.

User response: Correct the REXX EXEC and rerun the JOB.

'FULL' VALUE SET BY REXX EXIT 'XCPYDYNM' IS IMPROPER

Explanation: The REXX variable 'FULL' was set by the REXX exit to 'N' for a space which is currently in a restricted status. That is if the 'RESTRICT' variable is set to 'Y', the 'FULL' variable can not be set to 'N'.

User response: Correct the REXX EXEC and rerun the JOB.

'SHRLEVEL' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'SHRLEVEL' was incorrectly set by the REXX exit to a value other than 'C' or 'R'.

User response: Correct the REXX EXEC and rerun the JOB.

'MEDIA' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'MEDIA' was incorrectly set by the REXX exit to a value other than 'T' or 'D'.

User response: Correct the REXX EXEC and rerun the JOB.

'DISP' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'DISP' was incorrectly set by the REXX exit to a value other than 'K' or 'C'.

User response: Correct the REXX EXEC and rerun the JOB.

'UNITNAME' VALUE NOT SET BY REXX EXIT 'XCPYDYNM'

Explanation: The REXX variable 'UNITNAME' was not set by the REXX exit to a DASD unitname.

User response: Correct the REXX EXEC and rerun the JOB.

INCORRECT GDG NUMBER PASSED BY REXX EXIT 'XCPYDYNM'

Explanation: The REXX variable 'DSNAME' set by the REXX exit contains a relative GDG number other than '+1'.

User response: Correct the REXX EXEC and rerun the JOB.

DEFINE GDG FAILED

Explanation: Prior output messages indicates the reason for this failure. It is probable that the REXX exit 'XCPYDYNM' did not set the proper value for the variable 'GDGLIMIT'

User response: Correct the REXX EXEC and rerun the JOB.

DYNAMIC ALLOCATION FAILED

Explanation: Prior output messages indicates the reason for this failure. It is probable that the REXX exit 'XCPYDYNM' did not set the proper value for allocation variables

User response: Correct the REXX EXEC and rerun the JOB.

'RESETMOD' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'RESETMOD' was incorrectly set by the REXX exit to a value other than 'Y' or 'N'.

User response: Correct the REXX EXEC and rerun the JOB.

'TAPEDD' VALUE SET BY REXX EXIT 'XCPYDYNM' IS INCORRECT

Explanation: The REXX variable 'TAPEDD' was incorrectly set by the REXX exit to a DD that does not exist or is in use by a backup copy of the same tablespace.

User response: Correct the REXX EXEC and rerun the JOB.

'DSNAME' VALUE SET BY REXX EXIT 'XCPYDYNM' OR AN OUTPUT COMMAND IS NOT UNIQUE

Explanation: The DSNAME value specified on the OUTPUT command or the XCPYDYNM Automation Routine is not unique.

User response: Change the OUTPUT command or the XCPYDYNM Automation Routine to another unique value and re-submit the job.

'DSNAME' VALUE SET BY 'OUTPUT' COMMAND OR 'XCPYDYNM' REXX EXIT IS INCORRECT

Explanation: The DSNAME option on the OUTPUT command or the XCPYDYNM REXX exit was set to a syntactically incorrect value.

User response: Correct the OUTPUT command or XCPYDYNM REXX exit, and rerun the job.

'CONCURRENT' KEYWORD IS MISSING

Explanation: The keyword 'CONCURRENT' must be specified when more than one tablespace keyword is specified on a single copy statement. For example: 'copy tablespace a tablespace b concurrent'

User response: Correct the syntax and rerun your job.

CONNECT SUCCESSFUL FROM STMT(number-1) TO GROUP(number-2)USING LRSN(hexstring-1)

Explanation: The current NGTUTIL job step has successfully connected to point-in-time subsystem (PITS). This connection is for utility stmt No. number-1 to a group of objects having sequence number number-2 and lrsn X'hexstring-3'.

User response: No action is required.

DISCONNECT SUCCESSFUL FROM STMT(number-1)

Explanation: The current NGTUTIL job step under utility statement number-1 has disconnected from the point-in-time subsystem (PITS).

User response: No action is required.

STOP IS WAITING ON numberOfSubtasks CONNECTIONS AND numberOfIOEvents EVENTS

Explanation: A STOP command was issued while the point-in-time subsystem was busy processing other work as indicated. The subsystem is put into a drain state to prevent future events and connections from taking place. When all events are complete the subsystem will terminate normally.

User response: No action is required.

CDB/SUBSYSTEM TERMINATED DURING STEP-MUST-COMPLETE

Explanation: The subsystem address space was forced out of the system while in step must complete status. Unpredictable results may occur.

User response: You may have to IPL the system

CDB/SUBSYSTEM TERMINATED AT END OF MEMORY

Explanation: This message indicates that services of the CDB subsystem are no longer available and that the subsystem terminated due to an error or an ABEND. You may restart the subsystem.

User response: If the address space was terminated using the CANCEL command then this message is expected, if not, then gather error information including system dumps and the joblog and contact BMC Support.

CRITICAL BUFFER SHORTAGE

Explanation: This message indicates that I/O could not be performed due to buffer pool depletion. The current unit of work will be terminated.

User response: Issue the command to find out which group of objects are using most of the buffer pool and issue the appropriate 'cancel' command to relieve the shortage if necessary.

SQA STORAGE LIMIT EXCEEDED. ALLOCATED=number-1, LIMIT=number-2

Explanation: This message indicates that I/O could not be performed due to excessive usage of SQA storage. The current unit of work will be terminated.

User response: If the numbers seem reasonable, then you may need to increase the +SQALIMIT parameter to a higher value. If the numbers are large, then take an SVC dump of the subsystem and contact BMC Support.

IOERR SEQN=hexstring-1, V=string-1, DSN=string-2

Explanation: This message indicates that an I/O error has occurred reading the dataset named above on DASD volume serial number string-1. Message NGTC155 will further describe this I/O error having sequence number X'hexstring-1'.

User response: The I/O will be automatically retried and the result of the retry if not successful will be indicated by message NGTC156.

IOERR SEQN=hexstring-1, V=string-1, CC=hexstring-2, CSW=hexstring-3, SENSE=hexstring-4, IOCB=hexstring-5

Explanation: This message describes details of the I/O error presented by a prior NGTC154 message. CC is the completion code of the I/O, CSW is the channel status word and 2 bytes of sense are provided to further diagnose the problem.

User response: The I/O will be automatically retried and the result of the retry if not successful will be indicated by message NGTC156.

IOERR SEQN=hexstring-1, V=string-1 RETRY FAILED

Explanation: This message indicates that a prior I/O error has been marked permanent and the current unit of work will be terminated.

User response: If this message occurs frequently, then start a GTF trace and take an SVC dump of the CDB subsystem. Forward the GTF trace and the DUMP to BMC Support for diagnosis.

CDB/SUBSYSTEM DISABLED

Explanation: This message indicates that the subsystem has internally disabled its functions due to excessive abends.

User response: To activate the subsystem, you may issue the 'ACT' command. Meanwhile, gather all error documentation including SVC DUMPS and forward to BMC Support for diagnosis.

CDB/SUBSYSTEM IS ALREADY ACTIVE

Explanation: This message indicates that the subsystem is already active on this processor and that two subsystems can not coexist on same processor.

User response: Issue the operator command 'D A,JOBNAME' where 'JOBNAME' is the name of the subsystem proc. If 'JOBNAME' does not exist in the system, then contact BMC Support for a resolution.

'CONCURRENT' MODE IS NOT SUPPORTED IN DATASHARING ENVIRONMENT

Explanation: The utility does not support concurrent mode in a DB2 data-sharing environment.

User response: Run the utility without the concurrent keyword for exclusive utility access.

CDB/SUBSYSTEM IS DRAINING

Explanation: This message is issued as a response to the subsystem command 'INACT' and it indicates that subsystem will not accept any more connection but will allow existing utility jobs to continue.

User response: If you have entered this command by mistake, you can immediately issue the 'ACT' command to reverse the effect.

CDB/SUBSYSTEM IS NOW INACTIVE

Explanation: This message is issued as a response to the subsystem command 'INACT' and it indicates that subsystem has successfully drained all current activities.

User response: To activate the subsystem, issue the 'ACT' command.

command COMMAND PROCESSING COMPLETE

Explanation: This message marks the end of response to the indicated subsystem command.

User response: No action is required.

SQAUSED=number-1K SQALIMIT=number-2K EVENTS=number-3 UTLMEM=number-4M LOG=number-5K

Explanation: This message is issued as a response to a DISPLAY STORAGE command. It displays all SQA storage utilization for I/O control blocks in kilobytes. SQALIMIT is the initialization parameter and EVENTS are the number of active STARTIOs.

User response: No action is required.

string-1 hexstring-1 string-2 number-1 number-2

Explanation: This is the body of message NGTC164. One line is printed for each connected thread.

User response: No action is required.

GROUP LRSN ALLOC FIXED ACTIVE LOCK OBJS

Explanation: This message provides the heading for the NGTC167 message and is issued as the first response to the DISPLAY GROUP command. The report provides the following information:

• GROUP is the group number.

• LRSN is the LRSN or RBA.

• ALLOC indicates the total number of 4-KB pages allocated for this group in the subsystem data space.

• FIXED indicates the total number of fixed 4-KB pages in the data space for I/O use.

• ACTIVE is the number of threads connected to this group.

• LOCK is the internal contents of the group lock. It also represents the number of I/O processes in progress for this group.

• OBJS is the total number of objects or data sets under this group. 

User response: No action is required.

groupNumber LRSNOrRBA numberOf4KPages numberOf4KPages numberOfThreads lock numberOfObjects

Explanation: This is the body of message NGTC166. One line is printed for each possible group.

User response: No action is required.

DSN=string-1, HURBA=hexstring-1

Explanation: This is the first response to 'DISPLAY GROUP x E'. It shows the name of the object or dataset name and its High-Used-Rba 'HURBA'.

User response: No action is required.

IO=number-1 ALLOC1=number-2 ALLOC2=number-3

Explanation: This is a continuation of message NGTC168. IO is the total number of I/O issued against this dataset. ALLOC1 is the total number of 4k pages having an lrsn > group lrsn and ALLOC2 is the total number of 4k pages having an lrsn <= group lrsn.

User response: No action is required.

V=string-1, RPT=hexstring-1, EXT=hexstring-2, HU=hexstring-3, HA=hexstring-4

Explanation: This is a continuation of message NGTC168. V is volume serial on which the dataset reside. RPT is record per track for this volume. EXT is total extents on volume for this dataset. HU and HA are High USED and High allocated RBA's on this volume.

User response: No action is required.

CCL=hexstring-1, CCH=hexstring-2, LRB=hexstring-3, HRB=hexstring-4, TRKS=number-1

Explanation: This is a continuation of message NGTC170. It describes an extent on a volume for the current object. CCL is the low CCHH. CCH is High CCHH. LRB is low RBA and HRB is high RBA in extent. TRKS is the total number of tracks governed by this extent.

User response: No action is required.

string-1 hexstring-1 number-1

Explanation: This is the body of message NGTC172. One line is printed for each connected thread under the current group x

User response: No action is required.

GROUP DATASET NAME

Explanation: This is the heading for NGTC175 message and is issued as the first response to 'DISPLAY DSN' command. GROUP is the group No. associated with the reported dataset name.

User response: No action is required.

number-1 string-1

Explanation: This is the body of message NGTC174. One line is printed for each monitored dataset.

User response: No action is required.

INVALID SYSPLEX GROUP NAME string-1

Explanation: The specified group name conflicts with IBM naming conventions

User response: Specify a correct group name. See the sysplex user's guide

A REQUIRED KEYWORD IS MISSING

Explanation: The command is not complete. Another keyword is expected.

User response: Check the syntax and issue the command again if desired.

KEYWORD 'string-1' NOT RECOGNIZED

Explanation: string-1 is not a recognized command or an operand. It is may be misspelled.

User response: Check the syntax and issue the command again if desired.

CONNECTED TO CDB/SUBSYSTEM USING RBA hexstring-1

Explanation: This message is issued by the NGTUTIL utility after successful connection to the CDB subsystem. The reported rba is the synchronization level of the tablespace being processed by the utility. The Subsystem will also issue message NGTC147.

User response: No action is required.

CONNECT TO CDB/SUBSYSTEM FAILED DUE TO GROUP number-1 CONFLICT

Explanation: This message is issued by the NGTUTIL utility after an attempt to connect to the CDB subsystem. The reason being that the current tablespace is being used by another concurrent utility at a different synchronization level.

User response: To find out the conflicting utility, issue the operator command 'Dis group number-1 thread'

CONNECT TO CDB/SUBSYSTEM FAILED DUE TO FULL DSN TABLE

Explanation: This message is issued by the NGTUTIL utility after an attempt to connect to the CDB subsystem. The reason being that there is no room in global dataset name monitoring table used by the subsystem.

User response: Resubmit the JOB when concurrent utility activity is light. If this message occurs often, consider increasing the DSNMAX subsystem parameter.

CONNECT FAILED. CDB/SUBSYSTEM IS NOT ACTIVE

Explanation: This message is issued by the NGTUTIL utility after an attempt to connect to the CDB subsystem. The reason being that the subsystem has not been started or currently is not active.

User response: If the subsystem address space does not exist, then start the subsystem, otherwise activate the subsystem using the 'ACT' command.

SUBSYSTEM I/O ERROR CODE(errorCode) SEQN(IOSequenceNumber)

Explanation: The NGTUTIL utility was unable to fetch a DB2 page from the CDB subsystem. The subsystem encountered an I/O error on the indicated I/O sequence number. The errorCode can be one of the following codes:

• 4—A control interval (CI) could not be located.

• 8—An I/O was issued but no interrupt resulted.

• 12—There was a critical buffer shortage to perform the I/O process.

• 16—There is a permanent I/O error at the device.

User response: Check the subsystem's SYSPRINT log output for all messages with the indicated I/O sequence number. Refer to the instructions associated with these messages.

CI(hexstring-1) DSN(string-1

Explanation: This is a continuation of message NGTC184 to reveal the Control interval number (CI) and the data set name that encountered the error.

User response: See the user response for message NGTC184.

INITIALIZATION PARAMETER SYNTAX ERROR AT COLUMN number-1

Explanation: An initialization parameter was found to be incorrect at byte location number-1 Following message will explain the reason for the error.

User response: Check the syntax and correct the parameter.

INVALID NUMERICAL VALUE 'string-1' FOR PARAMETER 'string-2'

Explanation: An invalid numerical value was specified for the initialization parameter string-2 This parameter takes only numerical values.

User response: Check the syntax and correct the value of the parameter.

VALUE 'string-1' FOR PARAMETER 'string-2' IS BELOW MINIMUM VALUE OF number-1

Explanation: An invalid numerical value was specified for the initialization parameter string-2 The value specified string-1 is less than the predefined values for this parameter.

User response: Check the syntax and correct the value of the parameter.

VALUE 'string-1' FOR PARAMETER 'string-2' EXCEEDS MAXIMUM VALUE OF number-1

Explanation: An invalid numerical value was specified for the initialization parameter string-2 The value specified string-1 is greater than the predefined values for this parameter.

User response: Check the syntax and correct the value of the parameter.

AN EQUAL SIGN '=' IS EXPECTED AFTER KEYWORD 'string-1'

Explanation: An equal sign must be coded to separate the keyword from its value.

User response: Check the syntax and add the '=' sign.

DSNMAX=number-1 DSPMAX=number-2 SQALIMIT=number-3 RST=number-4 ID=string-1 GROUP=string-2 LOGLIMIT=number-5 K XIPL=string-3 CSM=string-4 MXMM=number-6

Explanation: This message is issued at system initialization and it shows all parameters in effect for this run.

User response: No action is required.

DISCONNECTED FROM CDBSS

Explanation: This message is issued by the NGTUTIL utility after successful completion of the concurrent mode utility statement. The CDB subsystem also issues message NGTC148.

User response: No action is required.

WAITING FOR A DSNE SLOT

Explanation: This message is issued by the NGTUTIL utility after an attempt to establish a connection. The connection could not be completed due to a shortage of DSN slots managed by the CDB subsystem. The utility will wait until the shortage is relieved.

User response: No action is required.

CDBSS TERMINATION COMPLETE

Explanation: This message indicates that services of the CDB subsystem are no longer available and that the subsystem has terminated due to a 'STOP' system operator command. You may restart the subsystem.

User response: No action is required.

CDBSS Vnumber-1.number-2 RESTART IN PROGRESS

Explanation: This message is issued as a response to XIPL=YES parameter specification and indicates that JOB restart with other members in the complex has been initiated.

User response: Do not restart DB2 while restart is in progress until message NGTC196 is issued.

CDBSS Vnumber-1.number-2 RESTART COMPLETE

Explanation: This message is issued after successful restart and connect to all jobs in the sysplex. Normal connect activity resumes.

User response: You may safely restart DB2 now.

CDBSS Vnumber-1.number-2 SHUTDOWN IN PROGRESS

Explanation: This message is issued as a response to XIPL=YES parameter specification and indicates that all resources held by this member will be released to owning members.

User response: Ensure that DB2 is shut down before shutting down CDBSS.

CDBSS Vnumber-1.number-2 SHUTDOWN COMPLETE

Explanation: This message is issued after successful release if all resources held by the current member and are owned by other members.

User response: You may safely shut down the operating system.

CONNECT ERROR MAY BE DUE TO DB2 LIBRARY LEVEL MISMATCH. RUN TERMINATED

Explanation: Connect error 00C10823 indicates a mismatch between the release of the Call Attach Facility and the current release of DB2.

User response: If multiple versions of DB2 are running, check STEPLIBs or JOBLIBs and whether they match the DB2 id specified in the PARM.

+DB2DOWN(OK) CANNOT BE HONORED FOR DB2 V4

Explanation: +DB2DOWN(OK) was the specified parameter, but requirements of DB2 V4 force interfaces with DB2 for utility functions. +DB2DOWN(OK) cannot be honored and the run must fail.

User response: DB2 must be up. If it is, check the plan name and DB2 id in the PARM field.

PROCESSING CHANGE DATASET string-1

Explanation: The copy merge program is currently merging the changes from the above named dataset with the base file produced during R/W REORG in order to produce the final image copy dataset.

User response: No action is required.

PROCESSING BASE DATASET string-1

Explanation: The copy merge program is currently merging from the base image copy dataset named above with the changes produced during R/W REORG in order to produce the final image copy dataset.

User response: No action is required.

hexstring-1 DB2 LOG PAGES PROCESSED

Explanation: This message shows the number of DB2 LOG pages processed so far.

User response: No action is required.

MEMBER(string-1) ADDED TO THE SYSPLEX TABLE

Explanation: This message indicates that the above named sysplex member has been added to the local sysplex table.

User response: No action is required.

MEMBER(string-1) IS NOW ACTIVE

Explanation: This message indicates that the above named sysplex member has been activated and is ready to process work.

User response: No action is required.

MEMBER(string-1) IS NOW INACTIVE

Explanation: This message indicates that the above named sysplex member has been deactivated.

User response: No action is required.

MEMBER(string-1) HAS FAILED, RECOVERY IN PROGRESS

Explanation: This message indicates that the above named sysplex member has suffered a failure or an error and that all related work will be scheduled for termination.

User response: Determine the reason for the sysplex member failure by scanning its joblog or system log. Correct the problem and restart the terminated units of work.

MEMBER(string-1) HAS JOINED SYSPLEX GROUP(string-2)

Explanation: This message indicates that the above named sysplex member has successfully joined the CDB subsystem group whose name is string-1

User response: No action is required.

SYSPLEX JOIN FAILED FOR GRP(string-1) AND MEM(string-2 string-3), R15=hexstring-1, R0=hexstring-2

Explanation: This message indicates a failure in joining the sysplex under group string-1 and member string-2 R15 and R0 are the return code and reason code from the IXCJOIN macro.

User response: An S0C3 abend will be generated following this message. Gather all appropriate documentation and contact BMC Support for assistance.

MEMBER(string-1) HAS BEEN QUIESCED

Explanation: This message indicates that the above named sysplex member has been disabled due to errors occurring in the CDB subsystem. All related units of work will be terminated by owning members.

User response: See message NGTC157 for further information.

SEND ERROR TO 'string-1' R15=hexstring-1 R0=hexstring-2

Explanation: This message indicates that the current sysplex member has attempted to send a message to the above named sysplex member but the request failed. R15 and R0 are the return code and reason code from the IXCMSGO service.

User response: Contact BMC Support for further assistance.

GROUP(number-1) LOGGED ON TO 'string-1' USING GROUP(number-2)

Explanation: The current connection having a group sequence No of number-1 has successfully logged on to sysplex member under connection group sequence No number-2

User response: No action is required.

GROUP(number-1) LOGON TO 'string-1' FAILED RC=hexstring-1

Explanation: The current connection having a group sequence No of number-1 has attempted to logon to above named sysplex member, but failed. The reason could be that the target member is no longer active.

User response: Check the joblog, syslog for any messages produced by the target member that may give the reason for this failure. Correct the problem and rerun your JOB.

GROUP(number-1) LOGGED OFF FROM 'string-1'

Explanation: The current connection having a group sequence No of number-1 has successfully logged off from the above named sysplex member.

User response: No action is required.

GROUP(number-1) LOGOFF FROM 'string-1' FAILED

Explanation: The current connection having a group sequence No of number-1 has attempted to logoff from the above named sysplex member, but failed. The reason could be that the target member is no longer active.

User response: Check the joblog, syslog for any messages produced by the target member that may give the reason for this failure. Correct the problem and rerun your JOB.

GROUP(number-1) FETCH DATA FROM 'string-1' FAILED

Explanation: The current connection having a group sequence No of number-1 has attempted to fetch data from the above named sysplex member, but failed. The reason could be that the target member is no longer active.

User response: Check the joblog, syslog for any messages produced by the target member that may give the reason for this failure. Correct the problem and rerun your JOB.

NGTSS IS NOT ACTIVE ON SYSTEM 'string-1'

Explanation: The current connection requires the activation of the CDB subsystem 'CDBSS' on the MVS machine whose name is string-1

User response: Start The CDBSS on the target machine or activate it using the 'F CDBSS,ACT' command.

NGTSS DOES NOT TOLERATE CONFIGURATION CHANGES

Explanation: The current connection has determined that a configuration change has taken place since the initial startup of NGTUTIL utility statement. Configuration changes include the starting of a DB2 sysplex member while a connection has already been established.

User response: Refrain from Joining sysplex members dynamically while a BMC/Utility requiring sysplex services is active. The current job will fail and may requires resubmission.

PURGE COMPLETED SUCCESSFULLY FOR MEMBER(string-1)

Explanation: This message marks the end of the process that started earlier by message NGTC208. It indicates that all remote connections from the member named above has been cleaned up.

User response: No action is required.

CONNECTION TO CDB/SUBSYSTEM FAILED DUE TO SYSPLEX ERROR

Explanation: This message is issued by the NGTUTIL utility after an attempt to connect to the CDB subsystem. A SYSPLEX error has prevented the connection from successful completion.

User response: Check the CDBSS LOG to determine the reason for this failure. Correct the error and rerun your job.

DATA CHANGES IN READ-ONLY MODE OCCURRED AT MEMBER string-1

Explanation: The subsystem sysplex controller have detected data changes at the above named member to a tablespace that has been placed in READ-ONLY mode. This error will cause the RW-REORG utility to fail.

User response: Check the CDBSS LOG to find out the exact reason for this failure. Correct the error and rerun your job.

CONFIGURATION CHANGE DETECTED NEW MEMBER(memberName) ON SYSTEM(systemName)

Explanation: The current connection determined that a configuration change has taken place since the initial startup of the NGTUTIL utility statement. In this case, the indicated DB2 member was started on the indicated system while a read/write reorganization is running.

User response: Refrain from joining SYSPLEX members dynamically while a BMC utility that requires SYSPLEX services is active. The current job will fail and might require resubmission.

STATUS CHANGE DETECTED FOR MEMBER(memberName) ON SYSTEM(systemName)

Explanation: The current connection determined that the status of the indicated DB2 member has changed from active to inactive or inactive to active. This status change occurred on the indicated system while a read/write reorganization was running.

User response: Refrain from joining SYSPLEX members dynamically while a BMC utility that requires SYSPLEX services is active. The current job will fail and might require resubmission.

JOB(string-1) STMT(number-1) ON SYSTEM(string-2)FAILED TO CONNECT. REASON CODE=( number-2 )

Explanation: The above named job running a NGTUTIL program statement number number-1 on the above named MVS system has failed to connect to the local CDB subsystem 'CDBSS' due to an error. number-2 is the reason code for the failure.

User response: For reason code(12) see message NGTC181. For reason code(16) see message NGTC182.

LOGON FROM SYSTEM(string-1) REJECTED. SYSTEM IS DRAINING

Explanation: A 'LOGON' request from the above named sysplex member has been received but rejected because the receiving system is in a draining or inactive state.

User response: To activate the local subsystem, issue the 'ACT' operator command

JOB(string-1) STMT(number-1) ON SYSTEM(string-2) PENDING RESTART

Explanation: The above named job running a NGTUTIL program statement number number-1 on the above named MVS system has failed and is awaiting restart for a number of minutes not exceeding 'RSTLIMIT'

User response: No action is required.

JOB(string-1) STMT(number-1) ON SYSTEM(string-2) RESTARTED

Explanation: The above named job running a NGTUTIL program statement number number-1 on the above named MVS system has successfully reactivated its connection to the local CDB subsystem 'CDBSS'

User response: No action is required.

STARTED COLLECTING INFO FROM SYSCOPY FOR number-1 OBJECTS

Explanation: A process to collect information from sysibm.syscopy catalog table has just started. The collected data is in response to specifying the keyword 'FROM' on the 'COPY' utility statement.

User response: No action is required.

COLLECTION COMPLETE. CPU TIME: number-1 SECONDS

Explanation: Signals the end of the process that started when message NGTC231 was issued. The amount of CPU time for the process is reported in seconds.

User response: No action is required.

IMAGECOPY DATASET IS NOT CATALOGED

Explanation: The dataset name reported in the next message was not found in the system catalog. This name was extracted from sysibm.syscopy catalog table.

User response: If +onerror(continue), the copy statement will be skipped, otherwise the job will fail. You may correct the situation by removing the 'FROM' keyword from the COPY utility statement and rerunning the JOB.

FOR TABLESPACE string-1.string-2 number-1

Explanation: This message names the table space and its dsnum in error. Prior messages indicate the reason for the error.

User response: No action is required.

NO IMAGECOPY EXISTS IN SYSIBM.SYSCOPY

Explanation: The Tablespace name reported in the next message did not have any image copies in the catalog table sysibm.syscopy that matches the 'FROM' criteria specified on the copy utility statement.

User response: See action for message NGTC233.

FROM COPY OPENED DSN=string-1, DDN=string-2

Explanation: The FROM image copy dataset named in the string-1 has been successfully opened for input. This is in response to specifying the 'FROM' keyword on the COPY utility statement.

User response: No action is required.

UNABLE TO FIND STACKING POINT

Explanation: An attempt to find the last written Filesequence No. on tape has failed due to excessive number of utility statements in error.

User response: See prior error messages for a detailed description of the error. Correct the error and resubmit the job.

Error opening COPY report file 'CDBCPRPT'

Explanation: An attempt to open for output the above named file has resulted in error. This is the final copy report file and may be used by other steps to generate recovery JCL. The copy of tablespaces has completed successfully.

User response: See JOB LOG for IEC messages relating to this file. Correct the DD statement by not specifying any DCB information, then rerun your job. Alternatively, remove the DD stmt if the report is not desired and rerun your job to complete utility processing.

'CTL_DSNAME' value set by REXX exit 'XCPYDYNM' is not UNIQUE

Explanation: The REXX variable 'CTL_DSNAME' was incorrectly set by the REXX exit to a name that is currently in use by the JOB.

User response: Ensure that the CTL_DSNAME is unique. Correct the REXX EXEC and rerun the JOB.

'CTL_DSNAME' value set by REXX exit 'XCPYDYNM' is incorrect

Explanation: The REXX variable 'CTL_DSNAME' was incorrectly set by the REXX exit to a name that is syntactically incorrect.

User response: Correct the REXX EXEC and rerun the JOB.

'CTL_MEDIA' value set by REXX exit 'XCPYDYNM' is incorrect

Explanation: The REXX variable 'CTL_MEDIA' was incorrectly set by the REXX exit to a value that is not 'T' or 'D' or inconsistent with variable 'MEDIA'.

User response: Ensure that this variable has a value of 'D' or the same value as variable 'MEDIA'. Correct the REXX EXEC and rerun the JOB.

GROUP(number-1) CONNECTING TO DB2 GROUP(string-1)

Explanation: The CDBSS group whose number is number-1 is attempting to connect to the DB2 group whose name is string-1 on behalf of the current job. Details of the connection will be echoed via MSG NGTC244 from all active members of the db2 group.

User response: No action is required.

GROUP(number-1) DISCONNECTING FROM DB2 GROUP(string-1)

Explanation: This message concludes the function that was started by an earlier NGTC242 message.

User response: No action is required.

CONNECTING TO DB2(string-1) FOR GROUP(number-1) ON SYSTEM(string-2)

Explanation: The CDBSS group whose number is number-1 and originating from system string-2 has logically connected to the DB2 whose SSID is string-1

User response: No action is required.

DISCONNECTING FROM DB2(string-1) FOR GROUP(number-1) ON SYSTEM(string-2)

Explanation: This message concludes the function that was started by an earlier NGTC244 message.

User response: No action is required.

RESTART LRSN QUERY FAILED DUE TO SYSPLEX ERROR. (SEE NGTSS LOG)

Explanation: An error has occurred while attempting to obtain an LRSN for a shrlevel change copy in a datasharing environment. See the CDBSS job log for details of the error.

User response: A Quiesce of the tablespace will be done to obtain the LRSN and if successful, the JOB will continue processing.

INDEX string-1.string-2 DOES NOT HAVE THE 'COPY YES' ATTRIBUTE. COPY SKIPPED

Explanation: The COPY utility cannot process the identified INDEXSPACE because it was not defined with the 'COPY YES' attribute.

User response: The COPY utility skips this object but continues processing the other objects in the list.

UNABLE TO LOCATE TSNAME FOR DBNAME.TABLENAME STATEMENT SKIPPED

Explanation: The COPY utility was unable to match a TSNAME with the specified INDEX/INDEXSPACE.

User response: The COPY utility skips this object but continues processing the other objects in the list.

number-1 TAPE UNIT(S) ADDED TO TAPE ALLOCATION TABLE

Explanation: The utility has detected number-1 tape units or DD statements in the current Jobstep and has added them to the tape allocation table for use by the XCPYDYNM and XULDDYNM REXX exits

User response: No action is required. However, to add more units to the table dynamically, use the _ALLOT() REXX function.

TAPE UNIT(hexstring-1) ALLOCATED TO DDNAME(string-1)

Explanation: The _ALLOT() REXX function has successfully allocated the above named DDNAME to the above named tape unit. The unit can now be used by the COPY and UNLD products.

User response: No action is required.

'CONCURRENT' ADDED TO STATEMENT BECAUSE ADREC IS ACTIVE

Explanation: 'CONCURRENT' was added to the 'COPY CATALOG' statement because ADrec is active on the system. ADrec requires the DB2 catalog copied using the CONCURRENT keyword.

User response: No action is required.

ECSAU=number-1K MAXDSPU=number-2 DSPFREE=number-3 FIXED=number-4 PAGES_READ=number-5

Explanation: This message is issued as a response to a DISPLAY STORAGE command. It displays all ECSA storage utilization for data set name tables as well as other statistics.

User response: No action is required.

QUIESCE MANAGER HAS SYNCHRONIZED OBJECTS

Explanation: This message is issued to mark the point of object synchronization during the concurrent copy

User response: No action is required.

QUIESCE MANAGER STARTED MULTITASKING PROCESS

Explanation: This message is issued to mark the invocation of QUIESCE MANAGER

User response: No action is required.

QUIESCE MANAGER SUBTASK TCB hexstring-1 IS INITIALIZED

Explanation: This message is issued to mark the invocation of an individual subtask running under the QUIESCE MANAGER

User response: No action is required.

QUIESCE MANAGER HAS COMPLETED ITS FUNCTIONS

Explanation: This message is issued to indicate the completion of QUIESCE Manager functions

User response: No action is required.

CDB SUBSYSTEM IS ACTIVE. VERSION hexstring-1.hexstring-2

Explanation: This message is issued to indicate that CDB subsystem is active and supports connections

User response: No action is required.

CDB SUBSYSTEM IS NOT ACTIVE

Explanation: This message is issued to indicate that CDB subsystem is not active and no NGT utility will be able to run

User response: Activate CDB subsystem

UCB FOR VOLSER(string-1) ON SYSTEM(string-2) NOT FOUND

Explanation: This message is issued to indicate that volser on the specified system not found and the job will fail

User response: Allocate volser and rerun the job

NO INDEXES WERE FOUND IN THE DB2 CATALOG FOR string-1.string-2 string-3

Explanation: This message is issued to indicate that we were unable to find Indexes for the specified DB.TS when +CPYINDEX(YES) was specified.

User response: No action is needed.

IMAGE COPY TASK ABENDED CODE=hexstring-1

Explanation: An unexpected abend has occurred in one of the image copy tasks.

User response: Contact BMC Support for further assistance.

SQL ERROR ATTEMPTING TO QUERY THE CATALOG. COPY CATALOG CANNOT BE PERFORMED

Explanation: The attempt to query the DB2 Catalog failed. The Copy Catalog request cannot be performed.

User response: Look at the CDBPRINT to determine why the Query failed. Correct the problem and re-run the job.

CONVERTING string-1.string-2 DSNUM number-1 FROM CONCURRENT TO SHRLEVEL CHANGE

Explanation: The above named object has failed quiesce processing prior to the start of concurrent copy but since shrlevel change was coded on the copy statement, the copy will be made in shrlevel change mode.

User response: No action is needed.

'CONCURRENT' IS REQUIRED FOR COPY CATALOG

Explanation: A COPY CATALOG operation was requested but the CONCURRENT keyword was missing.

User response: Add the keyword CONCURRENT to the COPY CATALOG statement and resubmit the job.

DRAIN(string-1) FAILED. DB(string-2) SP(string-3) PART(number-1) RETRY(number-2)

Explanation: An attempt to drain string-1 CLASS claimers on objects governed by the RW-UTILITY has timed out and a retry may take place. The timeout value and the retry count are governed by the +QRETRY parameter.

User response: string-2 string-3 names the object that could not be drained. number-1 identifies the partition of the space if any and number-2 is the number of remaining retries.

DRAINING TAPE UNIT(hexstring-1) - DDNAME(string-1)

Explanation: The requested tape unit is being freed.

User response: No action is required.

DRAIN(string-1) SUCCESSFUL AT RBA/LRSN hexstring-1/hexstring-2

Explanation: An attempt to drain string-1 CLASS claimers on objects governed by the RW-UTILITY was successful at the above indicated RBA or LRSN.

User response: No action is required.

CASTOUT PROCESS FAILED FOR string-1.string-2 PART number-1

Explanation: An attempt to CASTOUT or externalize buffers in DB2 for the above named object has failed. This is a terminating error for the current utility but it can be restarted to retry the CASTOUT process again.

User response: This error is usually associated with I/O errors. Examine the DB2 syslog error information for a cause. Correct the error and rerun your utility again.

RBA MISMATCH - string-1.string-2 string-3 string-4 LP(hexstring-1) string-5 (hexstring-2)

Explanation: An attempt to take an incremental copy was not allowed. The last FULL LP copy RBA does not match the incremental copy type(LB,RP,RB) last FULL copy RBA. Both RBA's are shown.

User response: The incremental is not allowed and the copy is forced to a full copy.

DB2 FUNCTION FAILED FUNC_CODE=hexstring-1

Explanation: An attempt to perform an internal DB2 function has failed. This is probably due to unavailable resource. Check the system log for a possible DSNT500I message.

User response: Correct the error and rerun your utility again.

UNABLE TO OBTAIN X LOCK ON DBID(hexstring-1). DBD UPDATE FAILED

Explanation: Several unsuccessful attempts were made to obtain the EXCLUSIVE lock on the DBD whose internal id is X' hexstring-1

User response: Check the system log for a possible DSNT500I message. Correct the error and rerun your utility again.

POST OF string-1.string-2 PART number-1 FAILED. RETRY WILL BE ATTEMPTED number-2 MORE TIMES

Explanation: Several unsuccessful attempts were made to POST SYSCOPY for the object being specified.

User response: Check the system log for a possible DSNT500I message. Correct the error and rerun your utility again.

HURBA MISMATCH FOUND BETWEEN DB2 HEADER (hexstring-1) AND DATASET (hexstring-2) - COPY NOT TAKEN

Explanation: A check between the DB2 HURBA from the header page and the computed value from the System Catalog does not match. The copy is not taken.

User response: Obtain an IDCAMS LISTC ALL of the dataset(s) in question. Contact BMC Support for further assistance.

DB2 FUNCTION FAILED FUNC_CODE=hexstring-1 DUE TO DROPPED DBID(hexstring-2)

Explanation: An attempt to perform an internal DB2 function has failed. This is because the reported dbid has been dropped while in-use by the current thread. The thread could not be shut because other DBD's in use could not be serialized.

User response: Check the system log for a possible DSNT500I message. Correct the error and rerun your utility again.

DBID(hexstring-1) NO LONGER EXISTS IN SYSTEM

Explanation: An attempt to fetch the database whose descriptor is DBID has resulted in a failure. Possibly dropped

User response: Check the system log for a possible DSNT500I message. Correct the error and rerun your utility again.

RETURN CODE FROM IBM COPY WAS number-1

Explanation: Message shows the return code from the IBM Copy Utility.

User response: No action is required.

STATEMENT number-1 ABORTED - EMPTY OBJECTS AND 'DSNUM ALL'

Explanation: Prior messages named the specific objects that are empty. Empty objects cannot be included in a 'DSNUM ALL' COPY. The COPY run will abort.

User response: Insert rows into the empty partitions so DB2 will format them.

POST OF string-1.string-2 PART number-1 (LP number-2) string-3 - ICTYPE string-4, LOGRBA =hexstring-1

Explanation: The COPY (either from COPY or Reorg Tablespace) has been posted to SYSCOPY.

User response: No action is required.

BEGINNING COPY OF INDEXSPACE string-1.string-2

Explanation: This message precedes a statistics message about the object about to be copied.

User response: No action is required.

BEGINNING COPY OF INDEXSPACE string-1.string-2 PART number-1

Explanation: This message precedes a statistics message about the object about to be copied.

User response: No action is required.

COPY OF INDEXSPACE string-1.string-2 ABORTED- OBJECT IN RESTRICTED STATE

Explanation: The copy of the named index has been skipped because the index is in a pending state, e.g., rebuild pending.

User response: The index probably needs to be Rebuilt.

COPY STARTING FOR INDEXSPACE string-1.string-2 PART number-1

Explanation: This message indicates the COPY process has started for the named indexspace. The part number is listed if this is a partitioned index.

User response: No action is required.

COPY STARTING FOR INDEXSPACE string-1.string-2

Explanation: This message indicates the COPY process has started for the named indexspace. The part number is listed if this is a partitioned index.

User response: No action is required.

COPY COMPLETED FOR INDEXSPACE string-1.string-2 PART number-1

Explanation: This message indicates the COPY process has completed for the named indexspace. The part number is listed if this is a partitioned index.

User response: No action is required.

COPY COMPLETED FOR INDEXSPACE string-1.string-2

Explanation: This message indicates the COPY process has completed for the named indexspace. The part number is listed if this is a partitioned index.

User response: No action is required.

COPY SKIPPED FOR INDEXSPACE string-1.string-2 PART number-1

Explanation: This message indicates the COPY process has completed for the named indexspace. The part number is listed if this is a partitioned index. The COPY was skipped because of a return code from XCPYDYNM.

User response: No action is required.

COPY SKIPPED FOR INDEXSPACE string-1.string-2

Explanation: This message indicates the COPY process has completed for the named indexspace. The part number is listed if this is a partitioned index. The COPY was skipped because of a return code from XCPYDYNM.

User response: No action is required.

string-1.string-2 NOT PARTITIONED BUT PART NUMBERS SPECIFIED - COPY ABORTED

Explanation: The COPY statement for this object specified part numbers but the object is not partitioned. The COPY run will abort.

User response: Correct the COPY statement and resubmit.

string-1.string-2 - SPECIFIED PART # EXCEEDS number-1 PARTS - COPY ABORTED

Explanation: The COPY statement for this object specified part numbers higher than the number of partitions. The COPY run will abort.

User response: Correct the COPY statement and resubmit.

string-1.string-2 - ALL PARTS EXCLUDED - COPY ABORTED

Explanation: The COPY statement for this object specified EXCLUDE and all parts were excluded. The COPY run will abort.

User response: Correct the COPY statement and resubmit.

STATEMENT number-1 SKIPPED - NO OBJECTS TO COPY

Explanation: COPY SCOPE PENDING found no objects in COPY PENDING or all parts were excluded. This statement is skipped.

User response: No action is required.

STATEMENT number-1 ABORTED - OBJECTS RESTRICTED

Explanation: Prior messages named the specific objects in DB2 Restricted states. The COPY run will abort.

User response: No action is required.

COPY STARTING FOR TABLESPACE string-1.string-2 PART number-1

Explanation: This message indicates the COPY process has started for the named tablespace. The part number is listed if this is a partitioned tablespace.

User response: No action is required.

COPY STARTING FOR TABLESPACE string-1.string-2

Explanation: This message indicates the COPY process has started for the named tablespace. The part number is listed if this is a partitioned tablespace.

User response: No action is required.

COPY COMPLETED FOR TABLESPACE string-1.string-2 PART number-1

Explanation: This message indicates the COPY process has completed for the named tablespace. The part number is listed if this is a partitioned tablespace.

User response: No action is required.

COPY COMPLETED FOR TABLESPACE string-1.string-2

Explanation: This message indicates the COPY process has completed for the named tablespace. The part number is listed if this is a partitioned tablespace.

User response: No action is required.

string-1 COPY OF number-1 (HIUSED RBA) string-2 KPAGES

Explanation: This message specifies whether a FULL or INCR COPY has started and shows the number of pages to be copied.

User response: No action is required.

string-1 COPY DONE - number-1 (string-2K) PGS WRITTEN OF number-2 ALLOC (number-3 XTNTS), string-3 FRSPC/PAGE

Explanation: The COPY has completed.

User response: No action is required.

ALL COPIES MARKED WITH DISP=D - NO COPIES MADE - STATEMENT SKIPPED

Explanation: Check the XCPYDYNM exit - 'DISP=D' was specified for each.

User response: No action is required.

number-1 LVLS, #8 RIDS, #8 KEYRECS, #8 VERSND, #8 TREE PGS, #8 LEAF PGS

Explanation: The COPY has completed.

User response: No action is required.

NON ZERO RETURN CODE FROM 'string' - RUN ABORTED

Explanation: The indicated REXX exit must return code 0.

User response: Correct the REXX exit and rerun.

NON ZERO RETURN CODE FROM SWARQ - RUN ABORTED

Explanation: This routine is attempting to extract the esoteric device type from the unitname supplied by XCPYDYNM.

User response: Check the value supplied for UNITNAME in XCPYDYNM and rerun.

NON ZERO RETURN CODE FROM CDBDEVTP - RUN ABORTED

Explanation: This routine is attempting to extract the esoteric device type from the unitname supplied by XCPYDYNM.

User response: Check the value supplied for UNITNAME in XCPYDYNM and rerun.

NON ZERO RETURN CODE FROM SYSCOPY CHECK - RUN ABORTED

Explanation: This routine checks that no error would occur if this copy were registered in SYSIBM.SYSCOPY.

User response: Check the value supplied for DSNAME in XCPYDYNM and rerun.

OBJECT string-1.string-2 string-3 string-4 WILL NOT BE COPIED. IT IS MARKED AS DEFINE=NO

Explanation: This message is issued to indicate that the specified object will not be copied. The object does not exist.

User response: No action is needed.

SOME DATASETS ARE MISSING - COPY ABORTED

Explanation: The locate for some data sets failed because they were either migrated or not found. The copies for these datasets are aborted.

User response: This message should be accompanied by others. Take the action recommended by them.

DRAIN RETRY DELAYED numberOfSeconds SECONDS

Explanation: The process waits the specified number of seconds between attempts to acquire the drain.

User response: No action is required.

NO NGTSS CONNECTION FOR DSN=string-1

Explanation: CDBSS connection for the above named data was either lost or not established. Job can not continue without a connection

User response: This message should be accompanied by others. Take the action recommended by them.

MEDIA=mediaValue + UNIT=unitName  IS INVALID – COPY ABORTED. 

Explanation: There is a mismatch between the MEDIA value specified in the XCPYMDIA automation control point and the UNITNAME value specified in the XCPYDYNM automation control point. One points to a TAPE device and the other points to a DASD device.

User response: Correct one or both of the automation control points so that mediaValue and unitName point to the same type of device.

UNIT=unitName CAN NOT BE FOUND ON THE SYSTEM – COPY ABORTED. 

Explanation: The UNIT returned from the XCPYDYNM automation control point cannot be found on the system. 

User response: Correct the unitName returned from the XCPYDYNM automation control point so that a valid name is specified.

FLASHCOPY=YES AND +SVRDISK(-1) ARE MUTUALLY EXCLUSIVE - COPY ABORTED

Explanation: The UTLPARMS parameter +SVRDISK(-1) specifies that a disk server should not be started, but FLASHCOPY YES specifies that a copy file should be written to disk. These two keywords are mutually exclusive.

User response: Remove one of the mutually exclusive keywords and resubmit the job.

DRAIN(string-1) RELEASED

Explanation: The utility drain that was obtained earlier has been released.

User response: No action is required.

DRAIN(string-1) STARTED. TIMEOUT=timeoutValue SECONDS FOR DB(databaseName) SP(spaceName) PART(partitionNumber)

Explanation: The utility is starting a process to drain the objects identified in this message. The message includes the object's database name, space name, and associated partition number.

User response: No action is required.

NGTSS SHUTDOWN FAILED. DB2(string-1.string-2) IS ACTIVE AND JOB(string-3)ON SYS(string-4) IS ALSO

Explanation: CDBSS detected a conflict during orderly shutdown. The above named utility job on the above named system can not co-exist with the above named DB2 member.

User response: Either shutdown the utility job or the above named DB2 subsystem. Then retry the CDBSS shutdown command again.

SHUTDOWN DATA TRANSFER STARTING FOR JOB(string-1) STMT(number-1) FROM SYS(string-2)

Explanation: A process to transfer data pages from the above named system has started for the above named job and utility statement number on the local system.

User response: No action is required. However this process results from a shutdown command on the remote system.

SHUTDOWN DATA TRANSFER COMPLETE AT hexstring-1. NEW=number-1 OLD=number-2

Explanation: This signifies a successful end to the process that was started when NGTC334 was issued and shows the number of datapages transferred.

User response: No action is required.

SHUTDOWN DATA TRANSFER FAILED

Explanation: This signifies an unsuccessful end to the process that was started when NGTC334 was issued.

User response: This message should be accompanied by others. Take the action recommended by them.

SHUTDOWN DATA TRANSFER FAILED ON SYSTEM(string-1)

Explanation: A request to transfer data pages to the above named system has failed possibly due to insufficient memory.

User response: This message should be accompanied by others. Take the action recommended by them then retry the shutdown command again.

SHUTDOWN FAILED DUE TO number-1 ACTIVE JOBS ON LOCAL SYSTEM

Explanation: A shutdown command was issued but there are active jobs connected and therefore the command is rejected.

User response: Terminate utility jobs currently running on local system, then retry the shutdown command again after shutting down all DB2 systems

SESSION VERIFICATION FAILED ON SYSTEM(string-1) REASON CODE number-1

Explanation: The current connection has determined that an existing DB2 member has changed its status from Active to inactive or vice versa on the above named system while a RW-REORG was running.

User response: This message could also occur if improper shutdown of CDBSS on the above named system has been carried out.

OLD_FETCH(number-1) NEW_FETCH(number-2) OLD_USED(number-3) NEW_USED(number-4) FREE=number-5

Explanation: This shows connection statistics totals. OLD pages are below the connect LRSN and new pages are above the LRSN. Fetch is the count requested by the utility. USED is the number of 4K pages saved in CDBSS dataspace.

User response: No action is required.

CHANGE LIMIT EXCEEDED. ROLLING BACK

Explanation: The CDBSS dataspace has been exhausted, due to too many updates to the tablespace while the REORG is running. Message NGTC185 displays the object name that exhausted the dataspace, resulting in this message.

User response: Check the subsystem's sysprint log output for all messages having a I/O sequence number of X' hexstring-1 ' Refer to the instructions associated with these messages.

string-1.string-2 PART number-1 FAILED DB2 AUTHORIZATION. COPY SKIPPED

Explanation: It has been determined that the current user is not authorized by DB2 to perform the specified function. The copy process for this object will be skipped.

User response: Take the appropriate action to ensure the job is run by a user with the necessary DB2 authorization. Rerun the job.

string-1.string-2 PART number-1 RESTRICTED. REASON string-3 .

Explanation: The Copy has been restricted to a FULL YES copy for the specified reason.

User response: No action is required.

XCPYMDIA REQUESTED TAPE BUT +SVRTAPE(0) SPECIFIED

Explanation: The XCPYMDIA exit set MEDIA to a 'T' however +SVRTAPE(0) was also specified.

User response: Change XCPYMDIA to specify 'D' or specify a value for +SVRTAPE that is greater than zero.

string-1.string-2 - DSNUM ALL REQUESTED BUT SOME PARTS EXCLUDED OR SKIPPED, COPY ABORTED

Explanation: Some parts in the DSNUM ALL copy were EXCLUDED or SKIPPED. The Copy is aborted.

User response: Run the Copy again without EXCLUDES or RTS specified.

LOST DB2 CONNECTION - VERIFY DB2 IS OPERATIONAL

Explanation: The connection to DB2 has been broken, and needs to be restored as soon as possible. Check the status of DB2.

User response: DB2 must be operational to perform this functionality.

SPACEUNIT AS SET BY REXX EXIT XCPYDYNM IS INCORRECT. USE XSUTDYNM TO SET VALUES OTHER  THAN T OR C

Explanation: The REXX variable SPACEUNIT was incorrectly set by the XCPYDYNM REXX exit to a value other than C or T.

User response: Correct the REXX exit and rerun the job. Otherwise use the REXX exit XSUTDYNM to specify SPACEUNIT.

WRITER DRAIN SKIPPED DUE TO PENDING CONDITIONS

Explanation: This is a trace message.

User response: No action is required.

OUTPUT FILE OPENED

Explanation: This is a trace message.

User response: No action is required.

ASASET CODED WITHOUT WILDCARDS AND 1 OR MORE OBJECTS INCOMPLETE

Explanation: Specific Tablespaces were specified in a COPY ASASET. At least one of those Tablespaces were flagged by DB2 as incomplete.

User response: Correct the SYSIN and resubmit the Utility

string-1.string-2 string-3 string-4 - NO CHANGES FOUND - COPY ABORTED

Explanation: Incremental COPY of a Tablespace was specified. A read of the Tablespace found no changed pages.

User response: No action is required.

string-1 COPY OF string-2 string-3K PAGES WITH AN RBA > hexstring-1

Explanation: Incremental COPY of a Tablespace was specified. The message details the number of changed pages that will be copied.

User response: No action is required.

TABLESPACE string-1.string-2 IS A CLONE OR CLONED - PROCESSING IS SKIPPED FOR THE TABLESPACE

Explanation: Cloned Tablespaces will not be Copied in this release.

User response: No action is required.

DUPLICATE TAPE DDNAME(string-1) FOUND IN THE TIOT. ONLY THE FIRST OCCURRENCE WILL BE USED

Explanation: The utility has detected a tape data set (string-1) that has already been added to the tape allocation table for use by the XCPYDYNM and XULDDYNM REXX exits.

User response: Correct the statements. Each file on tape can be referenced only once.

ERROR - OBJECT string-1.string-2 NOT IN SAME DB2 STATUS AS BEGINNING OF JOB

Explanation: The AFTERACC process for the referenced object was not successful. The status of the object in DB2 may have changed since the start of this job.

User response: The status of the object did not allow the AFTERACC process to complete successfully. Ensure that no other utilities are being run on this object. Correct the SYSIN and resubmit the Utility.

WRITING ON VOL hexstring-1 string-1 TTR(hexstring-2) TTT(hexstring-3)

Explanation: Trace message from parallel dataset writer indicating the relative volume number and volser and track range for this subtask.

User response: No action is required.

string-1 string-2.string-3 (number-1) - ON VOL hexstring-1 string-4 TTR(hexstring-2) TTT(hexstring-3)

Explanation: Trace message from parallel dataset writer indicating the relative volume number and volser and track range for this subtask.

User response: No action is required.

IO COMPLETE. EXCP=number-1 WRITTEN=number-2 RESIDUAL=number-3

Explanation: Trace message from parallel dataset writer indicating the subtask has completed. I/O stats are printed.

User response: No action is required.

string-1 string-2.string-3 (number-1) - IO CMPLT, EXCP=number-2 WRT=number-3 RESID=number-4

Explanation: Trace message from parallel dataset writer indicating the subtask has completed. I/O stats are printed.

User response: No action is required.

VSQ1(number-1) VSQE(number-2) TTT1(number-3) TTTT1(number-4) TTTTE(number-5)

Explanation: Trace message from parallel dataset writer indicating the subtask has completed. I/O stats are printed.

User response: No action is required.

string-1 string-2.string-3 (number-1) - VSQ1(number-2) VSQE(number-3) TT1(number-4) TTT1(number-5) TTTE(number-6)

Explanation: Trace message from parallel dataset writer indicating the subtask has completed. I/O stats are printed.

User response: No action is required.

DATASET SIZE=number-1 TRACKS ON number-2 VOLUMES

Explanation: Trace message from parallel dataset writer indicating the output dataset has been extended.

User response: No action is required.

string-1 string-2.string-3 (number-1) - DATASET SIZE=number-2 TRACKS ON number-3 VOLUMES

Explanation: Trace message from parallel dataset writer indicating the output dataset has been extended.

User response: No action is required.

string-1.string-2 (number-1) - BFMGR PAGE READ ERROR - PG hexstring-1, RC=number-2

Explanation: An error occurred trying to read the spacemap pages for the named tablespace. COPY XP will be bypassed.

User response: No action is required.

string-1.string-2 (number-1) - COPY XP NOT USED IF string-3

Explanation: COPY XP will be done only for FULL copies to DASD for datasets with at least 320 cylinders to be copied. This message indicates that COPY XP will not be used for this COPY due to the reason described. Normal COPY will be done.

User response: No action is required.

string-1.string-2 (number-1) - number-2 PGS/SPCMP , number-3 ALLO, number-4 SM, number-5 SYSP

Explanation: These values are the characteristics of the segmented tablespace about to be copied. It shows the number of pages per spacemap, the number of pages allocated to the tablespace, the number of spacemap pages and the number of system pages.

User response: No action is required.

string-1.string-2 (number-1) - number-2 ALLO, number-3 SYSP, number-4 PAGES TO COPY

Explanation: These values are the characteristics of the non-segmented tablespace about to be copied. It shows the number of pages allocated to the tablespace, the number of system pages and the total number of pages to be copied.

User response: No action is required.

string-1.string-2 (number-1) - number-2 OUTPUT PAGES, number-3 4K PGS, number-4 CYLS

Explanation: This message describes the total number of output pages to be written to the COPY dataset. It shows the count in DB2 pages, in 4K pages and in cylinders.

User response: No action is required.

string-1.string-2 (number-1) - number-2 WRITER TASKS, number-3 CYLS PER TASK

Explanation: This message describes the number of parallel output writer tasks and how many output cylinders that will be written by each task.

User response: No action is required.

text

Explanation: This is a trace message that prints internal values for the writer tasks. These messages should be copied if there is an error in COPY XP.

User response: No action is required.

IMAGE COPY string-1 DSN= string-2,DDN= string-3

Explanation: The image copy data set specified by string-2 is currently open or closed as indicated by string-1. 

User response: No action is required.

ONE OR MORE CATALOG OBJECTS CAN NOT BE COPIED, PROCESSING ENDS

Explanation: One or more objects cannot be copied. Additional messages, such as NGTB136, NGTB106, NGTC356, NGTU082 and NGTC308 provide more information about the reason. The utility skips processing for this object.

User response: If applicable, change and resubmit the job, or contact BMC Support.

CDBSS ON ssid VERSION vr IS BACK LEVELED. VERSION 5.1 OR HIGHER IS REQUIRED

Explanation: The version of installed the CDB subsystem (CDBSS) on the indicated z/OS system is below the required version. CDBSS version 5.1 or later is required for proper functioning under DB2 Version 11 or later.

User response: Re-Install the latest version of CDBSS

CDBSS ON ssid VERSION vr IS BACK LEVELED. VERSION 6.1 IS REQUIRED

Explanation: You are attempting to use the NGT utility under DB2 Version 12, but you do not have the required version of the CDB subsystem installed.

User response: Install the latest version of the CDB subsystem.

Reconnect to CDBSS ON ssid VERSION vr Failed. VERSION 6.1 OR HIGHER IS REQUIRED

Explanation: You are attempting to operate on an object with a DSSIZE defined that is greater than 64 GB, but you do not have the required version of the CDB subsystem installed.

User response: Install the latest version of the CDB subsystem.

diagnostic text.

Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages.

User response: No action is required.