Messages NGTG000 through NGTG999

This topic contains messages for the Next Generation Technology products.
NumberDescription
NGTG000

WAITING FOR RESOURCE string-1.


Explanation: DBMGR is waiting for shared access to the specified resource.

User response: No action required--information only.

NGTG001

string-1 OPEN - DSN=string-2.


Explanation: The specified DBMGR file has been opened.

User response: No action required--information only.

NGTG002

number-1 TRACKS IN DATASET.


Explanation: The DBMGR file contains the specified number of tracks.

User response: No action required--information only.

NGTG003

OPEN FAILED FOR string-1 DATASET.


Explanation: The named dataset could not be successfully opened due to an unexpected condition.

User response: Check the JES message log for indications as to what may have caused the open failure, then contact BMC Customer Support with this message number and text.

NGTG004

NUMBER OF USER DIRECTORIES LIMITED TO number-1 DUE TO CNTL FILE TRACK SIZE.


Explanation: Processing detected a condition where the number of user directories were exceeded.

User response: Limit the number of user directories to the number specified in the message or use a different CNTL file.

NGTG005

CREATE FAILED, FILE string-1 ALREADY EXISTS.


Explanation: Processing attempted to create the file named in the message but the attempt failed because it is already in the MVS catalog.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTG006

FILE string-1 CREATED.


Explanation: The file named in the message was successfully created.

User response: Information message - no action required.

NGTG007

string-1 ANALYSIS OF THE LOG FILE(S).


Explanation: Status message for analysis of the log file(s).

User response: Information message - no action required.

NGTG008

THERE ARE number-1 ORPHAN TRACKS IN THE LOG FILE(S).


Explanation: Processing detected the number of orphan tracks listed in the message.

User response: Information message - no action required.

NGTG009

DBMGR TRACE: FUNCTION=string-1, TCB=hexstring-1, TRACK COUNT=number-1.


Explanation: A DBMGR trace message.

User response: Information message - no action required.

NGTG010

UNABLE TO EXTEND FILE string-1 - ABENDING.


Explanation: Processing was unable to extend the specified file because it has reached its defined allocation limits. The current job is abending as a result.

User response: Use a file defined with more space and re-submit the job.

NGTG011

string-1 OUTPUT DD NOT FOUND.


Explanation: The DBMGR DUMP OUTDDN data set DD was not found in the JCL. For DBMZAP, the AUDIT keyword was specified but the DBMGR ZAP DBMAUDIT data set was not found in the JCL.

User response: Add/correct the output DD statement in the JCL, or change the value of the OUTDDN or AUDIT keyword. Resubmit the job.

NGTG012

string-1 OUTPUT DD OPEN FAILED.


Explanation: The DBMGR DUMP OUTDDN data set DD could not be opened. For DBMZAP, the AUDIT keyword was specified but the DBMGR ZAP DBMAUDIT data set DD could not be opened.

User response: Verify that the data set is defined and specified correctly in the JCL and OUTDDN keyword or change the AUDIT keyword to NOAUDIT. Resubmit the job.

NGTG013

LOG FILE string-1 (HEX) IS NOT KEYED.


Explanation: The value specified for the DBMGR DUMP FILE keyword number does not represent a valid keyed file. For DBMLOAD1, the value specified for the DBMGR LOAD FILE keyword number does not represent a valid keyed file.

User response: Correct the FILE keyword number. Resubmit the job.

NGTG014

LOG FILE string-1 (HEX) CONTAINS NO KEY ENTRIES.


Explanation: The value specified for the DBMGR DUMP FILE keyword number represents a keyed file with no key entries. For DBMLOAD1, the value specified for the DBMGR LOAD FILE keyword number represents a keyed file with no key entries.

User response: Correct the FILE keyword number. Resubmit the job.

NGTG015

LOG KEY CONTAINS NO TRACK ENTRIES.


Explanation: A value specified for the DBMGR DUMP FILE KEY keyword represents a key with no track entries. For DBMLOAD1, a value specified for the DBMGR LOAD FILE KEY keyword represents a key with no track entries.

User response: No action required--information only.

NGTG016

INPUT KEY LENGTH IS INVALID FOR LOG FILE string-1 (HEX).


Explanation: A value specified for the DBMGR FILE KEY keyword represents a key with a length that does not match that of the specified FILE keyword number.

User response: Correct the KEY keyword length and/or value(s). Resubmit the job.

NGTG017

INPUT KEY NOT FOUND IN LOG FILE string-1 (HEX).


Explanation: A value specified for the DBMGR FILE KEY keyword represents a key that does not exist in the specified FILE keyword number.

User response: Correct the KEY keyword length and/or value(s). Resubmit the job.

NGTG018

string-1 INPUT DD NOT FOUND.


Explanation: The DBMGR LOAD INDDN data set DD was not found in the JCL.

User response: Add/correct the input DD statement in the JCL, or change the value of the INDDN keyword. Resubmit the job.

NGTG019

string-1 INPUT DD OPEN FAILED.


Explanation: The DBMGR LOAD INDDN data set DD could not be opened.

User response: Verify that the data set is defined and specified correctly in the JCL and INDDN keyword. Resubmit the job.

NGTG020

INPUT LOAD FILE IS INVALID - string-1.


Explanation: The DBMGR LOAD INDDN DD data set is not a valid format file for DBMLOAD1 to process correctly. The explanatory description provides the specific reason for the error.

User response: The input LOAD file does not match the data as previously DUMPed, according to the DBMGR LOAD statement. Correct the input DD statement, change INDDN keyword value, or correct the DBMGR LOAD statement. Contact BMC Customer Support or your local representative.

NGTG021

DBMG string-1 OF string-2 DSN string-3 string-4 FILE DDN string-5.


Explanation: This message indicates that the named CNTL file or LOG file is being DUMPed or LOADed to the OUTPUT file or PRINT file with the specified DDname.

User response: No action required--information only.

NGTG022

END DBMG - string-1 string-2 TRACKS string-3 ED string-4 FILE DDN string-5.


Explanation: This message indicates that number-1 tracks have been DUMPed or LOADed input file to the output file.

User response: No action required--information only.

NGTG023

INPUT TRACK NUMBER string-1 OUTSIDE DATASET BOUNDARY.


Explanation: A DBMGR TRACK keyword contains a value for a track number that lies outside the boundary of the LOG file.

User response: Correct the value of the invalid input track number and validate all other values. Resubmit the job. If the job continues to fail contact BMC Customer Support or your local representative.

NGTG024

NUMBER OF TRACKS IN INPUT LOAD FILE EXCEEDS AVAILABLE SPACE ALLOCATION OF THE OUTPUT string-1 DATASET.


Explanation: LOAD of an entire CNTL or LOG data set was requested but the DBMGR LOAD INDDN DD data set contains more tracks than the amount of available space in the output data set.

User response: Either increase the size of the output CNTL or LOG data set, or reduce the number of tracks to be loaded from the input LOAD file by selecting fewer tracks for processing. Contact BMC Customer Support or your local representative.

NGTG025

OUTSTANDING I/O FOUND FOR DD(string-1) HAS BEEN FLUSHED.


Explanation: An I/O operation was found for the DD definition listed in the message, and was flushed.

User response: Information message - no action required.

NGTG026

INPUT string-1 TRACK NUMBER hexstring-1 IS AN EMPTY TRACK.


Explanation: The DBMGR ZAP string-1 data set TRACK NUMBER X'hexstring-1' does not contain any valid data and is in fact an empty track.

User response: Correct the CNTL or LOG data set TRACK specified to request a TRACK NUMBER that contains valid data and is not an empty track. Resubmit the job. If the job continues to fail contact BMC Customer Support or your local representative.

NGTG027

INPUT RECORD number-1 NOT ON string-1 TRACK NUMBER hexstring-1 .


Explanation: The DBMGR ZAP RECORD number-1 does not exist on string-1 data set TRACK NUMBER X'hexstring-1'.

User response: Correct the CNTL or LOG data set TRACK and/or RECORD specified to request a TRACK NUMBER and/or RECORD NUMBER that co-exist. Resubmit the job. If the job continues to fail contact BMC Customer Support or your local representative.

NGTG028

INPUT VER/REP DATA AT OFFSET hexstring-1 BEYOND RECORD number-1 BOUNDARY.


Explanation: The DBMGR ZAP VER/REP offset X'hexstring-1' or data string length extends beyond the record length for RECORD number-1.

User response: Correct the CNTL or LOG data set TRACK and/or RECORD specified or correct the VER/REP data offset and/or length specified for the selected TRACK RECORD NUMBER. Check all other VER/REP data offsets and lengths specified. Contact BMC Customer Support or your local representative.

NGTG029

ZAP VER string-1 TRACK NUMBER hexstring-1 RECORD number-1 AT OFFSET hexstring-2 FAILED.


Explanation: The DBMGR ZAP VER of the string-1 data set for TRACK NUMBER X'hexstring-1' RECORD number-1 at offset X'hexstring-1' did not match the current contents of the record data.

User response: Correct the CNTL or LOG dataset TRACK and/or RECORD specified or correct the VER/REP data offset and/or length specified for the selected TRACK RECORD NUMBER. Check all other VER/REP data offsets and lengths specified. Contact BMC Customer Support or your local representative.

NGTG030

ZAP CHECKSUM VALUE hexstring-1 INCORRECT. EXPECTING hexstring-2.


Explanation: The DBMGR ZAP CHECKSUM X'hexstring-1' is not correct and does not match the calculated checksum value of X'hexstring-2'.

User response: Check that all the ZAP VER/REP data is present, and correct the CHECKSUM value for the selected TRACK RECORD NUMBER. Contact BMC Customer Support or your local representative.

NGTG031

LOG TRACK 0 IS FULL - PLEASE USE RESET TO RE-INSTATE AUDIT TRAIL PROCESSING.


Explanation: The DBMGR ZAP audit trail data cannot be saved because there is no more space available on LOG TRACK 0.

User response: Specify RESET as the keyword for audit processing and resubmit the job. This will allow the oldest audit data to be replaced with the newest audit data in track 0 of the log data set. Contact BMC Customer Support or your local representative.

NGTG032

DBMGR TRACE: DBMGR CNTL DSN=string-1.


Explanation: A DBMGR trace message.

User response: Information message - no action required.

NGTG033

INVALID REPOSITORY HEADER PAGE DSN=string-1.


Explanation: The DBMGR repository in the above named dataset has invalid format. A dump of the hdr page will be printed following this message.

User response: A drop and a redefine of the vsam dataset may correct the problem. Before doing so, back up the dataset using DFDSS or DBMGR DUMP utility provided by BMC Software. Send the backup to BMC Customer Support for diagnosis and correction if applicable.

NGTG034

string-1 R8=hexstring-1 R9=hexstring-2 R10=hexstring-3 CUR TCB=hexstring-4 OWNING TCB=hexstring-5 RESMGR=hexstring-6.


Explanation: A DBMGR trace message.

User response: Information message - no action required.

NGTG035

SHUTTING DOWN IDB(hexstring-1) ENVIRONMENT


Explanation: The internal database (IDB) numbered above has been shutdown due to prior failures in the jobstep. If this is IDB(0001), then the server will be abended with a U4095 abend code.

User response: Correct the original error that cause this message to be issued, then restart the JOB.

NGTG036

UNABLE TO CONNECT TO DB2 string-1, SO IF AVAILABLE, PLEASE SPECIFY THE DB2 GROUP ATTACH NAME AS PARM=.


Explanation: The DB2 subsystem is not available to obtain the group attach name for the user, so the user must specify the DB2 group attach name instead of the SSID name in PARM=.

User response: Correct the PARM= field that caused this message to be issued, then restart the JOB.

NGTG040

string-1 OPEN - DSN=string-2.


Explanation: String-1 is 'CDB_SPACE'. String-2 names the internal dataset that is being opened. This message is displayed after the dataset has been successfully opened.

User response: No action required--information only.

NGTG041

number-1 number-2 KPAGES IN string-1 (HIGH-USED RBA).


Explanation: Based on the internal dataset High-Used RBA, the space just opened contains number-1 pages in units of number-1 Kilo bytes. Not all these pages contain data. Subsequent messages describe the page counts by page type.

User response: No action required--information only.

NGTG042

string-1 CLOSE - DSN=string-2.


Explanation: String-1 is 'CDB_SPACE' and String-2 names the internal dataset that is being closed. This message is displayed after the dataset has been successfully closed. Subsequent messages will show page I/O statistics.

User response: No action required--information only.

NGTG043

UNABLE TO OBTAIN VALID TRACK LIST. REASON CODE =number-1.


Explanation: The reason code provides some additional information.

User response: Intended for internal use only. Contact BMC Customer Support or your local representative. Check the assembler source code for the applicable reason code. Diagnose and correct the problem, accordingly.

NGTG044

TOTAL NUMBER OF RECORDS UNLOADED TO DD string-1 = number-1.


Explanation: This message indicates the number of records unloaded.

User response: No action required--information only.

NGTG045

NEW TOKEN STORED IN DBMPARM (hexstring-1 hexstring-2 hexstring-3).


Explanation: A DBMGR trace message.

User response: Information message - no action required.

NGTG050

FAILURE IN MODULE string-1, FC=hexstring-1, RC=hexstring-2.


Explanation: The return code from the named module was non-zero.

User response: A message printed by the named module should indicate the nature of the failure.

NGTG051

DBUT string-1 FUNCTION FAILED, RC=hexstring-1.


Explanation: The return code from the named function was non-zero.

User response: A prior message printed by the named function should indicate the nature of the failure.

NGTG052

FREE string-1 LIST FAILED, RC=hexstring-1.


Explanation: The return code from a LISTFREE function was non-zero.

User response: This may indicate a logic error if the list has already been freed.

NGTG053

string-1 VALUE IN FNC (DBUT SYSIN) IS INVALID.


Explanation: The value of the named keyword in the DBUT SYSIN command is unrecognized.

User response: Check the DBUT SYSIN syntax, and correct the value of the named keyword in the command.

NGTG054

string-1 FILE FOR string-2 NOT ALLOCATED.


Explanation: The output DUMP or input LOAD file for the DDNAME specified by OUTDD or INDD, respectively, was not available.

User response: An output DUMP DD or input LOAD DD statement must be present in the JCL for the specified OUTDD or INDD DDNAME. Verify that the JCL DD statement matches the specified DDNAME or appropriate default DDNAME for the function.

NGTG055

NO MATCHING LIST ENTRIES FOUND IN string-1 FILE.


Explanation: There were no entries found by a query of the named IDB file that match the specified criteria.

User response: Verify that all required IDB files, especially the CheckPoint dataset, exist for any dump data being requested. If not, a dump of the requested data is not possible.

NGTG056

INVALID RECORD FOUND IN string-1 FILE, REASON=hexstring-1.


Explanation: An invalid record or data within the record, was found to be invalid in the named IDB file or input LOAD file.

User response: Contact BMC Customer Support. The reason code identifies the specific data that is invalid.

NGTG057

DUPLICATE DATA FOUND IN string-1 FILE, REASON=hexstring-1.


Explanation: Unexpected duplicate data found in the named IDB file.

User response: Contact BMC Customer Support. The reason code identifies the specific data that is duplicated.

NGTG058

NUMBER OF SERVERS (number-1) DOES NOT MATCH MASTER TOTAL.


Explanation: The number of server jobs relating to this master job does not correspond to number of servers for the master.

User response: Contact BMC Customer Support. This may indicate a logic error. The number of servers, specified within the master, should always match the actual number of servers.

NGTG059

string-1 FAILED FOR 'string-2' IDB FILE.


Explanation: The named IDB file could not be opened (INIT) or closed (TERM). A prior message, if present, may indicate the nature of the failure.

User response: Verify that all required IDB files, especially the CheckPoint dataset, exist for any dump data being requested. If not, a dump of the requested data is not possible. For a LOAD function, this may indicate a logic error.

NGTG061

BMC CHECKPOINT DUMP STARTING.


Explanation: The DUMP of the Checkpoint data set is starting.

User response: Information message - no action required.

NGTG062

BMC CHECKPOINT DUMP DDNAME (string-1) NOT FOUND.


Explanation: The DD name specified for the Dump of the BMC Checkpoint data set was not found.

User response: Verify the DD name specified in the CDBDBT CKPTDUMP statement.

NGTG063

STARTING DUMP OF string-1 CHECKPOINT TABLE


Explanation: The Dump of the string-1 table in the BMC Checkpoint data set is starting.

User response: Information message - no action required.

NGTG064

string-1 CHECKPOINT TABLE IS EMPTY (0 ROWS DUMPED).


Explanation: The string-1 table in the BMC Checkpoint data set was found to be empty, so no rows were dumped.

User response: Information message - no action required.

NGTG065

DUMP COMPLETED FOR string-1 CHECKPOINT TABLE (number-1 RECORDS DUMPED).


Explanation: The string-1 table in the BMC Checkpoint data set was dumped successfully with number-1 records written to the output data set.

User response: Information message - no action required.

NGTG066

BMC CHECKPOINT DUMP COMPLETE (number-1 RECORDS DUMPED).


Explanation: The BMC Checkpoint data set was dumped successfully with number-1 records written to the output data set.

User response: Information message - no action required.

NGTG067

BMC CHECKPOINT LOAD STARTING.


Explanation: The Load of the Checkpoint data set is starting.

User response: Information message - no action required.

NGTG068

BMC CHECKPOINT LOAD DDNAME (string-1) NOT FOUND.


Explanation: The DD name specified for the Load of the BMC Checkpoint data set was not found.

User response: Verify the DD name specified in the CDBDBT CKPTLOAD statement.

NGTG069

BMC CHECKPOINT LOAD COMPLETE (number-1 RECORDS LOADED).


Explanation: The BMC Checkpoint data set was loaded successfully with number-1 records read from the input data set.

User response: Information message - no action required.

NGTG070

STARTING LOAD OF string-1 CHECKPOINT IDB


Explanation: The Load of the string-1 table in the BMC Checkpoint data set is starting.

User response: Information message - no action required.

NGTG071

LOAD COMPLETED FOR string-1 CHECKPOINT IDB (number-1 RECORDS LOADED).


Explanation: The string-1 table in the BMC Checkpoint data set was loaded successfully with number-1 records read from the input data set.

User response: Information message - no action required.

NGTG072

string-1 RECORD (hexstring-1) ALREADY DEFINED, RECORD SKIPPED.


Explanation: A record to be inserted into the string-1 table, already exists in the table. This record (hex-1) will be skipped.

User response: Information message - no action required.

NGTG073

BMC CHECKPOINT DATA SET string-1 OPEN FAILED.


Explanation: An OPEN of the BMC Checkpoint data set (string-1) was attempted, but the OPEN failed.

User response: Verify the BMC Checkpoint data set exists and is defined with the correct attributes. Contact BMC Customer Support or your local representative

NGTG074

BMC CHECKPOINT DATA SET string-1 OPENED.


Explanation: An OPEN of the BMC Checkpoint data set (string-1) was successful.

User response: Information message - no action required.

NGTG075

REPLACE NOT ALLOWED ON ACTIVE BMC CKPT DATA SET (string-1).


Explanation: A CDBDBT CKPTLOAD REPLACE has been requested, but the data set specified (string-1) is the same as the BMC Checkpoint data set in use by the CKPTLOAD utility. The CKPTLOAD REPLACE must be for a different BMC Checkpoint data set.

User response: Specify a different BMC Checkpoint data set in the REPLACE parameter. Contact BMC Customer Support or your local representative

NGTG083

DB2 DSNHDECP MODULE SETTINGS DSNHDECPmoduleSettings


Explanation: This message displays DSNHDECP module settings.

User response: No action is required.

NGTG076

MAXIMUM DSNUM REACHED FOR DSN(string-1).


Explanation: The above named dataset has reached the architectural limit of 255 datasets and can not be expanded.

User response: Determine the reason for reaching this limit. It could be that the primary or secondary allocations are low. Correct the allocation parameters accordingly or consider using Extended VSAM datasets.

NGTG999

diagnostic text.


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

User response: No action required--information only.

Was this page helpful? Yes No Submitting... Thank you

Comments