Messages BMC24500 through BMC24599 (System and SQL Performance for DB2)
This topic contains messages for the System and SQL Performance for DB2 solution.
Number | Description |
|---|---|
BMC24500 | Invalid trace data set dataSetName Explanation: The indicated trace data set name (specified in the DOMPLEX Profile) is too long to be appended with the .DATA and .RBAT suffix. The indicated trace data set name is not used by the Output Group. User response: Specify a data set name that does not exceed 39 characters. |
BMC24501 | KSDS repository data set name missing in column 10 Explanation: The input to the repository initialization job did not contain a valid repository data set name beginning in column 10. The repository data set name is a required input field. The repository is not initialized. User response: Correct the input to specify a valid repository data set name beginning in column 10. |
BMC24502 | DAIR RC=returnCode DD=ddname DSN=dataSetName Explanation: An error occurred during dynamic allocation. The return code, DDNAME, and data set involved in the error are identified. Depending upon the data set, the product may not be able to continue operation. User response: If the return code is 1708, the data set does not exist or is not cataloged on the current system. Contact your MVS system programmer to analyze other dynamic allocation errors. |
BMC24503 | Error on operation, RC=returnCode, DSN=dataSetName Explanation: An error occurred during a Data Collector I/O operation. The data set name and return code are identified. If the operation is a PUT to a trace data set, the Data Collector attempts to continue writing trace records to the next eligible trace data set. Other I/O errors can cause the Data Collector to terminate or to rebuild the trace data set index (RBAT). User response: If this message is followed by BMC24943, check the following conditions: - If the indicated data set is the VSAM STATUS data set, check that the $C10VSAM job was run to create the STATUS data set. Make sure that the trace data set names are the same as those in the STATUS data set. - If the Data Collector was active at one time, check to see if the trace data sets were migrated. The trace data sets must be recalled or recreated before the Data Collector can be started. If this message persists or these conditions do not apply, contact BMC Customer Support. |
BMC24504 | Cannot access DSN=dataSetName Explanation: A trace data set specified in the DOMPLEX Profile was not allocated with the correct VSAM parameters, or is not cataloged on the current system. The indicated trace data set is not used by the Data Collector. User response: Examine the DOMPLEX Profile to ensure that all trace data sets specified in the profile exist and have correct VSAM attributes. Correct any errors and restart the Data Collector. If the indicated data set is the STATUS data set, check that the STATUS data set that was allocated in the $C10VSAM job matches the one specified in the $C30DOPTS job. The Data Collector looks for the data set name found in *.LOAD(DOMDMDSN). |
BMC24505 | IFI synchronous read failed, RC=returnCode Explanation: This message is issued in response to a DEBUG command. It reports the return code from the DB2 CAF INI when a READS request sent to DB2 to obtain group buffer pool data fails. Normal operation continues; however, if the return code is greater than zero, no group buffer pool data is collected and no data will be displayed on group buffer pool reports. User response: Never issue a DEBUG command unless instructed by a BMC Customer Support representative. Report the return code to the representative and follow the instructions given. Explanations of return codes can be found in the DB2 Messages and Codes manual. |
BMC24506 | SQL Explorer not installed/active in Data Collector Explanation: An Explain request has been received by the Data Collector, but neither SQL Explorer nor the Explain process is active to handle the request. The request is returned to the requester. User response: Make sure your TSO dialog is accessing a correct level of the Data Collector. If it is, contact BMC Customer Support because the Explain function should always be active. |
BMC24507 | Subsystem definition not found in STATUS data set Explanation: The Data Collector subsystem was started with a missing or invalid SUBSYS parameter. The parameter should identify the subsystem ID of a Data Collector record in the STATUS data set. Data Collector initialization terminates. User response: Examine the STATUS data set to ensure that a record exists for the name specified on the SUBSYS parameter. Also examine the JCL used to start the Data Collector to ensure that the correct STATUS data set is referenced. If you are installing this product for the first time, make sure that the Installation Assistant job was run (see member $C97IA in the JCL data set). |
BMC24508 | $*--------------------------------------------------------------------$*-------------------------------------------------------------------- Data Collector DCssid is not at Version 2.2 or higher Explanation: The Data Collector subsystem was started with a STATUS data set that is not at Version 2.2 or higher. The DOMISTCV conversion utility should be run to convert the STATUS data set to V2.2. Data Collector initialization terminates. User response: Examine the STATUS data set to ensure that the DOMISTCV conversion utility is run and completes successfully. |
BMC24510 | **ERROR** Linkage stack overflow - Too many locks Explanation: You attempted to zoom to the Locking Activity by Thread report, but the number of locks being held or waited for by the selected thread was so excessive that they exceeded the available storage. Data collection is aborted. User response: Try to determine why such an excessive number of locks are being held or waited for by this particular thread. You will not be able to display the report until the lock contention is alleviated. |
BMC24511 | Output member already exists - press ENTER to use or specify new name Explanation: The output member name specified during the JCL generation process already exists. The system waits for a response before proceeding. User response: Press Enter to overwrite the specified member or specify a new member name and press Enter. |
BMC24512 | Catalog object scan already in progress for DB2ssid Explanation: The OBSCAN command has been issued against a DB2 for which an OBSCAN command is already in progress. The OBSCAN command refreshes the names of objects created since Data Collector initialization. It is issued by selecting option 3 from the Pool Advisor Configuration Menu (after clicking on the CONFIG button). Pool Advisor issues this command automatically each day at midnight and again any time a DB2 subsystem is initialized, so a conflict could occur if you attempt to issue the command at the same time. The original OBSCAN command continues processing, but the subsequent command is terminated immediately. User response: No action is required. You can wait until the in-progress command is finished and execute the command again. If other problems are encountered at the same time, contact BMC Customer Support for assistance. |
BMC24513 | Copy submitted DSN=dataSetName Explanation: JCL was submitted by the Data Collector to copy the indicated trace data set. Trace data set copies are automatically generated when a trace data set SWITCH occurs if a JCL source is indicated in the DOMPLEX Profile. This message indicates that JCL was submitted, but does not ensure that the JCL executed properly. User response: No action is required. |
BMC24515 | Error on logset op, RC=returnCode, RS=reasonCode Explanation: An error occurred during a request to retrieve historical data from logset. op can be RETRIEVE, KEYRANGE, or RTV-CONT. The return code and reason code are from the NGL component that services the request for retrieval.
User response: Contact BMC Software Customer Support and report the message, including codes. |
BMC24518 | Unable to find an active MV/DB2 PAS Explanation: Hyperlinking is being used to display a view from MainView for DB2, but there is not an active MAINVIEW PAS currently registered to the system. The display process is suspended. User response: Contact BMC Customer Support for assistance. |
BMC24519 | HYPERLINK CONNECTION TO CDC FAILED Explanation: Initialization for the product session failed because the MainView for DB2 session could not connect to the Data Collector (CDC). The session terminates and control returns to MainView for DB2. User response: Check all of the following conditions and make any necessary changes: - Make sure that a Data Collector is active on the MVS system and that the intended DB2 is being monitored by that Data Collector. - Make sure that the MainView for DB2 password member (BDSTBLx) is copied into the Data Collector LOAD library. - Make sure that the Data Collector load library is in the STEPLIB concatenation of the BBI-SS PAS, after the BBLINK data set. - Verify that the CLIST DOMC has been copied from BBSAMP into BBCLIB. Make sure the high-level qualifier (HLQ) of the Data Collector data sets has been specified and is correct. - If more than one Data Collector is active, you can direct the PAS to connect to a specific Data Collector with the CDC parameter in the DMRBEX00 member of BBPARM. Make it the first parameter. - Make sure that the DB2 to which you are trying to connect is defined in both the Data Collector and MVDB2. Ensure that the context is set to that one DB2 in MVDB2 when you try to use a hyperlink. - If the STATUS data set was migrated from a previous version or it is also using APPTUNE, verify that this DB2 has the flag 'Enable with MVDB2/DC' set to Y in the DOMPLEX Profile. |
BMC24520 | Overwriting DSN=dataSetName Explanation: The indicated trace data set has been selected as the target for writing the next trace record buffer and the data set is not empty. The data stored in the trace data set is overwritten with new data. User response: This is a normal condition when a data set contains data. To ensure that data is not lost, examine the JCL specified in your DOMPLEX Profile. Correct any errors and wait for the next submit or force a copy by submitting the JCL manually. |
BMC24521 | DB2ssid release level <v.r.mm> is not supported by product Explanation: The indicated DB2 subsystem is at a level of DB2 that is not supported by the indicated product. The product is not initialized for the indicated release level. User response: If you want to use this product, you must start a DB2 that is at a level supported by the product. |
BMC24522 | DCssid Insufficient data space buffer storage for output group(s) outputGroupNumber Explanation: The total data space specified for all output groups defined to either the Data Collector or to the DOMPLEX exceeds the limit of 2 GB. This message can be issued at product initialization, or on the Output Group Definitions Cross-Check panel after you create or modify your output groups. If this message is issued at product initialization, the Data Collector is not started. The product session is started, but you are limited to functions that do not require an active Data Collector. If this message is issued as a result of a cross-check, all output group specifications for the current session are discarded. User response: If the message was issued at initialization, go to the DOMPLEX Output Group panel of Administration and either delete enough output groups associated with the failed Data Collector or reduce the size of the output groups until the total data space allocation is 2GB or less. If the message was issued during cross-check, you will need to define your output groups again. Be careful that the total defined to either the Data Collector or to the DOMPLEX does not exceed 2GB. See the System and SQL Performance for DB2 Administrator Guide for additional explanation. |
BMC24523 | ssidMSTR uses more than n STEPLIB data sets Explanation: The System Services started task for the indicated subsystem (ssid) has more data sets in its STEPLIB concatenation than the Data Collector supports. The Data Collector allocates data sets referenced by the <ssid>MSTR started task to enable CONNECT processing. If all data sets required for CONNECT processing are included in the first <n> STEPLIB data sets, processing continues without error. User response: If a subsequent connect fails, reorder the STEPLIB concatenation so that the DSNLOAD and DSNEXIT data sets are included in the first <n> data sets. |
BMC24524 | Outgrp nnn trk xxx of yyyy in dataSetName Explanation: This message indicates the current write position track number within the indicated trace data set. It is generated as a result of the Data Collector STATUS command or whenever a trace data set is switched. <nnn> is the output group that owns this trace data set <xxx> is the track number currently being filled <yyyy> is the total number of tracks on this trace data set User response: No action is required. |
BMC24525 | Now formatting DSN=dataSetName Explanation: This message is issued during Data Collector I/O initialization whenever a new trace data set is found. All trace data sets are pre-formatted to their maximum size by the Data Collector prior to use. User response: No action is required. |
BMC24526 | Trace data set writes disabled for output group nnn Explanation: No trace data sets were successfully allocated for the indicated output group so no trace data assigned to this output group can be saved. No data assigned to the indicated output group will be saved. User response: Examine the DOMPLEX Profile to determine if any trace data sets were assigned to save this type of trace data. If this message is preceded by I/O error messages, examine the indicated trace data sets for problems. If the trace data sets are in-use by a Data Collector on a different MVS system, the DOMPLEX Profile definition should be re-examined to ensure that no output group includes multiple DB2 subsystems that can be active on different MVS systems at the same time. |
BMC24527 | function DSN=dataSetName Explanation: The indicated trace data set is in use for writes by the Data Collector (if function = Trace) or a trace data set switch is in progress (if function = Switched). This message might be followed by messages BMC24556 and BMC24557, which indicate the range of data currently in the data set (by timestamp). User response: No action is required. |
BMC24528 | Unable to switch trace data sets for output group nnn Explanation: An attempt was made to switch trace data sets in the referenced output group, but either no data set was assigned to this output group or an unrecoverable I/O error occurred. This message might be followed by BMC24558, BMC24557, or BMC24524 for switches that occurred successfully. The Data Collector does not switch trace data sets in the referenced output group. User response: Examine the DOMPLEX Profile output group definitions to determine if any trace data sets are assigned. If this message is preceded by I/O error messages, contact BMC Customer Support. |
BMC24529 | Outgrp nnn has lost nnnn trace records Explanation: Some data was lost from trace data set recording. The number of records lost and the output group that suffered the loss are indicated. Data is lost for one of the following reasons: - Buffer space shortage. The space allowed to buffer data in the global data space is insufficient to handle the high volume of trace data currently being produced. - Trace data set I/O is either hung or performing poorly. Data is lost and processing continues. User response: Most data loss can be resolved by increasing the size of the data space in the output group definition of the DOMPLEX Profile. You can get better performance from conflicting high-volume data types by splitting them into separate output groups where they will get separate dedicated buffer space and write engines. This problem might be relieved by raising the Dispatch Priority of the Data Collector subsystem to a value higher than DB2. If detailed performance traces are required and no data loss can be tolerated, specify a GTF trace to DB2 and use the product to format the data into reports (AM only). |
BMC24531 | All trace data set writes disabled Explanation: None of the trace data sets has been opened for writing trace records because the trace data sets are either not defined or there was an error allocating and opening the data sets. No records are written to the trace data sets. User response: Verify that the trace data sets are defined in the DOMPLEX Profile for this Data Collector and/or check the JES log for any MVS system errors in opening the trace data sets. |
BMC24532 | Outgrp nnn standby mode Explanation: This message is produced in response to the STATUS command when output group status is listed. It indicates that the indicated output group is in stand-by mode and not being used to record data on this MVS system. Stand-by mode is used when an output group is active on another MVS system because that is where the target DB2 subsystem is active. Normal operation continues. User response: No action is required. |
BMC24533 | Outgrp nnn transitioning to standby mode Explanation: The indicated output group is closing and deallocating its trace data sets because they are needed on another MVS system to collect trace data from a DB2 subsystem that is active there. The referenced output group data sets are closed. User response: No action is required. |
BMC24534 | Outgrp nnn transitioning to active mode Explanation: The indicated output group is trying to allocate its trace data sets because they are needed on this MVS system to collect trace data from a DB2 subsystem that is active here. The indicated output group is activated and begins recording data if the allocations are successful. If the allocations are not successful because they are still in use elsewhere, the Data Collector will try again in one minute. User response: No action is required. |
BMC24535 | Sample data with extrapolation and Exception-only roll-ups: select one Explanation: You have specified 'Y' for two collection options that are mutually exclusive: (1) Sample data with extrapolation, and (2) Exception-only roll-ups. Because both options invoke selective monitoring of statements in different ways, only one or the other (or neither) should be selected. You are not allowed to save these settings. User response: Choose only one or neither of the indicated collection options. |
BMC24536 | SQL detail must be 'Y' if Sample data with extrapolation is 'Y' Explanation: You have specified 'N' for Dynamic SQL detail, but 'Y' for Sample data with extrapolation. A specification of 'N' for Dynamic SQL detail rolls up dynamic PREPARE, DESCRIBE, OPEN, FETCH, and CLOSE as a single 'cursor' statement. A specification of 'Y' for Sample data with extrapolation changes the frequency at which statement executions are monitored and extrapolates captured values to arrive at an estimate of activity as if all statement executions had been monitored. Because the monitoring and extrapolation process can vary depending on statement type, statements of different types should not be rolled together when Sample data with extrapolation is active. The settings are not saved. User response: Specify 'Y' for Dynamic SQL detail so that PREPARE, DESCRIBE, OPEN, FETCH, and CLOSE statements will be reported separately. |
BMC24537 | SQL detail must be 'Y' if Exception-only roll-ups is 'Y' Explanation: You have specified 'N' for Dynamic SQL detail, but 'Y' for Exception-only roll-ups A specification of 'N' for Dynamic SQL detail rolls up dynamic PREPARE, DESCRIBE, OPEN, FETCH, and CLOSE as a single 'cursor' statement. A specification of 'Y' for Exception-only roll-ups causes only statement executions that exceed your thresholds to be reported. Because the monitoring process can vary depending on execution timings and activity, statements of different types should not be rolled together when Exception-only roll-ups is active. You are not allowed to save these settings. User response: Specify 'Y' for Dynamic SQL detail, so that PREPARE, DESCRIBE, OPEN, FETCH, and CLOSE statements will be reported separately. |
BMC24550 | Error RC=returnCode submitting copy JCL Explanation: An attempt was made to submit JCL to the JES internal reader for copying a full trace data set, but the submission failed with the indicated return code. The trace data set is not copied, but processing continues. User response: Examine the JCL specified in your DOMPLEX Profile. Correct any errors and wait for the next submit or force a copy by submitting the JCL manually. If no errors are found in the JCL, contact BMC Customer Support for assistance. |
BMC24551 | Error returnCode reading copy JCL from dataSeName Explanation: An attempt was made to read JCL from the indicated data set, but the read failed with one of the following return codes: 4 - Error opening the COPY data set 8 - Error allocating the COPY data set This can indicate that the data set does not exist, is not cataloged, or is not on disk. The copy JCL is not submitted, but processing continues. User response: Examine the JCL specified in your DOMPLEX Profile. Correct any errors and wait for the next submit or force a copy by submitting the JCL manually. If no errors are found in the JCL, contact BMC Customer Support. |
BMC24552 | Record variable, Column variable: variable Explanation: What happened that caused the message? What will the system do? User response: What should the user do? |
BMC24553 | Rebuilding RBAT <P|F> for dataSetName Explanation: A problem was found with the RBA table data set (an index for trace data sets) and it must be rebuilt before trace data set processing can continue. (P) indicates that a partial rebuild will be performed (only the most recent portion of the trace data set needs to be re-read to bring the RBA table up to date). This is usually what happens when the RBA tables were not properly written to DASD during the last Data Collector shutdown (as when the Data Collector is terminated via an MVS CANCEL command rather than the product SHUTDOWN command, for example). (F) indicates a full rebuild needs to be done (the entire trace data set must be read). This most often happens when the RBAT data set is damaged or deleted and has to be redefined. The trace data set RBA table is rebuilt automatically by the Data Collector during initialization. User response: No action is required. |
BMC24554 | RBAT rebuild complete for dataSetName Explanation: A rebuild operation for a trace data set RBA table has completed. Normal operation continues. User response: No action is required. |
BMC24555 | Updating status for output group nnn Explanation: The STATUS VSAM data set is being updated to include the current write positions of the trace data sets in the indicated output group. Normal operation continues. User response: No action is required. |
BMC24556 | and from timeStamp to timeStamp Explanation: This message is issued after message BMC24557 to show a second time range of data contained in a trace data set when the data is not contiguous. It is generated as a result of the Data Collector STATUS command, or when a trace data set is switched. The time range represented occurs at the end of the trace data set, and is an earlier time range than the one represented by BMC24557. The first time stamp in this message is the time stamp of the oldest record in the data set (will be the next record overwritten) and the second time stamp is the time stamp from either the last record in the data set or the last record stored before the SWITCH command was issued. User response: No action is required. |
BMC24557 | Data from timeStamp to timeStamp Explanation: This message is issued to show the time range of data contained in a trace data set. It is generated as a result of the Data Collector STATUS command, or whenever a trace data set is switched. The time range represented occurs at the beginning of the trace data set, and is a later time range than the one represented by BMC24556. The first time stamp in this message is the time stamp of the first record in the data set and the second time stamp is the time stamp of the most-recently-written record in the data set. Message BMC24556 appears after this message only if the data in the trace data set is not contiguous. User response: No action is required. |
BMC24558 | Writing trace index DSN=dataSetName Explanation: The indicated RBA table data set is being written. This happens at Data Collector termination, or whenever a trace data set is switched. This message precedes messages BMC24556 and BMC245557, which indicate the time range of data in the data set just written. User response: No action is required. |
BMC24559 | RBA Table consistency error (code): DSN=dataSetName Explanation: An error occurred using the indicated RBA table index data set during I/O initialization. The code indicates the kind of error that was detected (but is useful only to BMC Customer Support). This error can occur during an abrupt or hard shutdown, preventing the RBA table from being written to disk. The RBA table rebuild process is invoked to re-establish the RBA indexes to the performance data on the indicated trace data set. User response: In the case of an abrupt or hard shutdown, the rebuild should correct the problem and normal operation can continue. If the rebuild does not correct the problem, contact BMC Customer Support for assistance. Report the error code in the message to your customer support representative. |
BMC24560 | Failure to create global dataspace for trace data writer, RC=returnCode Explanation: The Data Collector was unable to create a global data space (also referred to as a Common Access Data Space) to use for buffering collected trace data. The following return codes are documented in the MVS Services Guide: TTKN-xx The error occurred in the TCBTOKEN service macro. DSPS-xx The error occurred in the DSPSERV service macro. ALES-xx The error occurred in the ALESERV service macro. The most common condition is DSPS-12, in which all allowed global data spaces have already been allocated. The MVS default is 25. The Data Collector cannot function without this resource and will automatically shut down. User response: If yours is a large, heavily-used system, contact your systems programmer about increasing the number of global data spaces allowed. Run the #MAXCADS job (included in the CNTL data set) to list the currently-in-use global data spaces and the current system limit. |
BMC24577 | ******************************************************** Explanation: This message is an informational message header. User response: Refer to message BMC24578 for a possible problem report. |
BMC24578 | ** PMD intercept(s) disabled due to recursive abends. DB2 SSID: db2_ssid ** Explanation: A DB2 intercept for PMD has been disabled due to recursive abends. One or more PMD intercepts have been disabled. The affected DB2 SSID is displayed. The product continues to operate and takes a system dump, if possible. User response: Report the problem to BMC Software Customer Support, providing as much diagnostic information as possible. |
BMC24589 | Error reading source data set dataSetName Explanation: An attempt to read a record from your source data set (as a result of report activation) failed, most likely because the data set specified as the source is not in the correct format for a source data set. Report activation continues if any records have already been read, but does not continue if the format of the source data set is incorrect. User response: Specify one of the following types of sequential data set: - archived trace data set - EXPORT file |
BMC24593 | Report does not require Dynamic Trace IFCIDs Explanation: The 'T' line command was specified for a report, but the selected report does not use IFCIDs that require a Dynamic Trace. The IFCIDs are either instantaneous or are always started automatically. The request is ignored. User response: Do not attempt to start a trace using this report. |
BMC24594 | Trace canceled Explanation: The CANCEL option was selected from the trace confirmation panel. The trace is not scheduled. User response: Schedule the trace if desired. |
BMC24595 | Hiperspace function failed, return code = returnCode, reason = reasonCode Explanation: The virtual file manager was unable to access a hiperspace file during the report-viewing process, resulting in a failure of the indicated function. The indicated return code and reason are returned from the failing hiperspace program call. Possible values for function are: - CREATE - EXTEND - SWRITE - SREAD - DELETE For CREATE, EXTEND, and SWRITE failures, an attempt is made to convert the file to DASD so that the report-viewing process can continue. For an SREAD failure, the report-viewing attempt fails. For a DELETE failure, the hiperspace is not deleted. User response: Refer to IBM documentation for more information about DSPSERV CREATE, EXTEND, and DELETE, or HSPSERV SWRITE and SREAD return and reason codes. If the IBM documentation does not provide a resolution, contact BMC Customer Support for assistance. |
BMC24596 | Start time must fall on 10 second boundary Explanation: You specified a start time for Dynamic Trace that is not divisible by 10 seconds. The start time is rejected. User response: Change the Seconds specification to a multiple of 10. |
BMC24597 | There is no Global filter setting to use Explanation: Under Local filters, you specified GLOBAL to copy settings from Global filters, but there are no Global filter settings to copy. The GLOBAL command is ignored. User response: Specify settings as desired. |
BMC24598 | This report does not use periods Explanation: You attempted to define a period for a report that does not support periods. The specification is ignored. User response: Do not specify a period for this report. |
BMC24599 | Length changed to fall on 10 second boundary Explanation: You specified an interval duration or period that is not divisible by 10 seconds. The length or duration is modified to fall on a 10-second boundary. User response: No action is required. |