WTO MESSAGE - OVERFLOW AREA OVERFLOWED
Explanation: Module addresses are stored in a hash table. This error occurs when the hash table overflow area is full and thus no new entries can be stored.
User response: Contact BMC Support.
ABEND U0016 AT ADDRESS xxxxxxxx in MODULE DX10ROLL
Explanation: This abend occurs because of a fatal processing error in module DX10ROLL as Extractor data set and volume records are concatenated together. Message DSO501 often appears with abend U0016. The most common cause of the abend is improper concatenation of Extractor data. An error condition results where multiple data sets with the same name are recognized on a single volume.
User response: Attempt to isolate the conditions that cause the abend by performing the following steps:
Remove the NOSTAE parameter from the Analyzer JCL to allow error messages to appear in the job.
Verify the concatenation order of input Extractor data sets.
Eliminate collecting optional VSAM catalog mapping records by removing the VSAM=YES parameter from the Extractor HEADMOVE control statement.
WTO MESSAGE - MODULE xxxxxxxx NOT FOUND
Explanation: Module xxxxxxxx is not present in the current load library.
User response: Contact BMC Support.
WTO MESSAGE - NO LEXICONS LOADED
Explanation: The lexicon tables are the definitions of all valid commands. This message indicates that the system could not load these tables, probably because they are missing from the current load library.
User response: Contact BMC Software to determine why these tables are missing.
WTO MESSAGE - UNABLE TO OPEN PRINT DCB
Explanation: The SYSPRINT or RPTCONTS DD statement is missing.
User response: Resubmit the Analyzer with the appropriate DD statement.
WTO MESSAGE - 999 - EXCESSIVE ERRORS, SYSTEM CLOSING DOWN
Explanation: The failsoft system allows 10 program interruptions per phase before terminating the run. This limit was exceeded.
User response: Use the SNAP dump produced by the abend to determine program interruptions and contact BMC Software.
WTO MESSAGE - 999 - EXTERNAL MODULE FAILED, SYSTEM CLOSING DOWN
Explanation: The failsoft system intercepted a program check in a module external to the Analyzer. The Analyzer does not attempt to recover.
User response: Contact BMC Support.
WTO MESSAGE - 999 - NO RETURN POINT SPECIFIED, SYSTEM CLOSING DOWN
Explanation: The failsoft system intercepted a program check, but a return point has not been specified by the highest level caller. The Analyzer does not attempt to recover.
User response: Contact BMC Support.
WTO MESSAGE - +CMFERR-P-CMFnnnnn6 - TEXT OF LAST ERROR MESSAGE ENCOUNTERED
Explanation: The last error encountered by the system was critical enough to make further processing impossible. The Analyzer does not attempt to recover.
User response: See the CMF Analyzer message for error number and message and take appropriate action based on the Action statement.
INSUFFICIENT DISK SPACE
Explanation: This error is detected when an attempt is made to use more space in a BDAM data set than could be preformatted.
User response: Register R10 plus 8 bytes points to a word. The ddname is located 12 bytes off the address contained in that word. If the error occurred while running the CMF MONITOR Analyzer in load module DM32DMSS, the data set specified on the DMSSMAIN DD card has insufficient space. Reallocate a larger data set and rerun the job. If the problem recurs, contact BMC Support.
ABEND U101 IN DMSS: DD STATEMENT MISSING or LOAD MODULE ERROR
Explanation: The DD statement for a DMSS file cannot be located. This condition can also occur if the DMSS subsystem is relink-edited without the linkage editor parameter REUS specified to mark the load module with the reusable attribute. Some generic copy utilities do not preserve aliases. If this happens, then DMSS will fail with this abend. To verify that this is the case, browse the STEPLIB or Link List library that is the source for the load modules being executed. If all the DMSSxxxx modules excluding DMSSSTAT are not aliases of DM32DMSS, then they have been linked or copied incorrectly. Also, verify that they have been link edited with the REUS option (this can be seen on the member list of browse as RU under the ATTRIBUTES column.)
User response: If it is a missing DDNAME, register R4 points to the ddname. If the ddname is not recognizable, contact BMC Support. Otherwise, supply the needed DD statement and rerun the job. If it is a link edit problem, reapply the latest maintenance to FMID BBMCHnn. If it is a copy problem, recopy using an option that preserves aliases. Verify that all entries are now aliases of DM32DMSS and that all aliases are marked RU.
DMSS DID NOT INITIALIZE THE DATA SET
Explanation: This error is detected when the data set pointed to was initialized to DMSS DCB specifications, but the data in the records is not recognized as DMSS data.
User response: The ddname is located at register R2 plus 12 bytes. If this DD statement points to a file normally used by DMSS, see abend U0109. Otherwise, allocate a new data set and rerun the job. If the problem recurs, contact BMC Support.
SEQUENTIAL UPDATE BEFORE READ
Explanation: An attempt was made to update a record that had not been read.
User response: Contact BMC Support.
READ AFTER CLOSE
Explanation: An attempt was made to read a record after closing the DMSS data set.
User response: Contact BMC Support.
CREATE SET WITH NO SET CHARACTERISTICS
Explanation: A request was made to create a DMSS set, but no information to define the set was supplied.
User response: Contact BMC Support.
INSUFFICIENT NUMBER OF BUFFERS
Explanation: DMSS ran out of internal buffer area.
User response: Contact BMC Support.
TGET ISSUED FOR SET BEFORE IGET
Explanation: This error is detected if an attempt is made to close a set for sequential processing before it is opened.
User response: Contact BMC Support.
NO MERGE ROUTINE SUPPLIED
Explanation: This error is detected when two sets are being merged and no routine was supplied to handle a duplicate record ID.
User response: Contact BMC Support.
FORMAT ERROR ON DMSS HISTORY FILE
Explanation: If a DMSS history type file is not closed by DMSS, the contents of the file cannot be addressable.
User response: The ddname is located at register R9 plus 12 bytes. Restore the data set from the last backup and rerun all updates since the backup. If the problem recurs, contact BMC Support.
MULTIPLE REQUEST FOR ALL AVAILABLE CORE
Explanation: A simultaneous request was made by two or more DMSS files to use all available core for buffer space.
User response: Contact BMC Support.
BDAM DATA SET CANNOT BE RE-INITIALIZED
Explanation: This error is detected if the data pointed to was not initialized to DMSS format and the host system requested that no automatic reinitialization should take place.
User response: The dsname is located at register R11 plus X'32F' bytes. Assign a new file to the corresponding DD statement and rerun the job. If the problem recurs, contact BMC Support.
OBTAIN FAILURE FOR DMSSMAIN DD STATEMENT
Explanation: OBTAIN failure for data set name specified by the DMSSMAIN DD statement. The data set does not exist on volume specified. Register R4 contains an error return code returned from OBTAIN.
User response: Check catalog entry location. If the data set is not there, reallocate, recatalog, and set the DMSS control statement up with request to initialize new data set, then rerun the Analyzer job. If data set does exist and the catalog entry does point to it correctly, contact BMC Support.
INSUFFICIENT CORE FOR INTERNAL TABLES
Explanation: This error is detected when main storage for certain internal tables cannot be acquired.
User response: Increase the region size for the abending step and rerun the job. If the problem recurs, contact BMC Support.
DUPLICATE SET ON FILE
Explanation: An attempt was made to save a DMSS set onto a DMSS history type file. A DMSS set with a duplicate name was already saved.
User response: Contact BMC Support.
SETS NOT RELEASED
Explanation: While attempting to close a DMSS file, not all sets assigned to the file were released.
User response: Contact BMC Support.
INITIALIZATION ATTEMPTED ON OPENED FILE
Explanation: An attempt was made to initialize a DMSS file that is currently open.
User response: Contact BMC Support.
CHANGE ATTEMPTED ON READ ONLY DATA SET
Explanation: An add or change operation was attempted on a file opened for read only.
User response: Contact BMC Support.
INTERNAL ERROR IN DMSS
Explanation: One of several serious problems occurred.
User response: Contact BMC Support.
ABEND -- INTERNAL ERROR
Explanation: This abend can be generated by any of the following programs: DX10ANAL, DX10CARD, DX10PARM, DX10PRTI, DX10SPLS, or DX10VOLL. The abend indicates that an internal error has occurred while the internal register stack was being processed. The error message may also be issued if the DSO Analyzer error recovery routines are processed incorrectly. (Issued by module DX10ANAL.)
User response: Isolate the conditions that have caused this error and refer to programs and conditions above. Contact BMC Support.
GETMAIN FAILURE
Explanation: A GETMAIN failure occurred while the initial work area for the DSO Analyzer was being obtained. (Issued by module DX10ANAL.)
User response: Check system message IEF374I in the listing for the maximum virtual storage used by the job step. Because this GETMAIN occurs early in processing, the region size must be increased by 256K or more to get the Analyzer to run.
INITIAL GETMAIN FAILED
Explanation: A GETMAIN failure occurred while obtaining the initial work area for the DSO Analyzer. This GETMAIN occurs early in processing. (Issued by module DX10ANAL.)
User response: Check system message IEF374I for the maximum virtual storage used by the job step. The region size should be increased by 256K or more so that the Analyzer can run.
INITIAL GETMAIN FAILED
Explanation: Early in processing, a GETMAIN failure occurred while obtaining the initial work area for the DSO Analyzer. (Issued by module DX10ANAL.)
User response: Check system message IEF374I for the maximum virtual storage used by the job step. The region size should be increased by 256K or more so that the Analyzer can run.
ABEND -- INCORRECT ASSEMBLY
Explanation: This is an internal error that should not occur. (Issued by module DX10ANAL.)
User response: Check the DATETIME statement and contact BMC Support.
ABEND -- RECOVERY WORK AREAS UNUSABLE
Explanation: An abend has occurred and the recovery work areas are unusable. (Issued by module DX10ANAL.)
User response: Contact BMC Support.
ABEND -- RECOVERY WORK AREAS UNUSABLE
Explanation: An abend has occurred and the recovery work areas are unusable. (Issued by module DX10ANAL.)
User response: Contact BMC Support.
INITIAL GETMAIN FAILED
Explanation: A GETMAIN failure occurred early in processing. (Issued by module DX10PARM.)
User response: Check system message IEF734I for the maximum virtual storage used by the job step. The region size may need to be increased by 256K or more so that the Analyzer can run.
DUMP
Explanation: An abend was forced because the ordinal in the existing DSI and the ordinal from the incoming record do not have the same data set names.
User response: Contact BMC Support.
DUMP
Explanation: An abend was forced because the ordinal in the existing DSI and the ordinal from the incoming record do not have the same data set names.
User response: Contact BMC Support.
OUTPUT BLOCKSIZE NO GOOD
Explanation: The block size defined for the SYSPRINT file was not a multiple of 133. Rather than overwriting the data set, the DSO Analyzer abends during the OPEN. (Issued by module DX10PRTI.)
User response: Contact BMC Support.
DUMP
Explanation: A logic error occurred while converting the date-time to an internal format. (Issued by module DX10CARD.)
User response: Contact BMC Support.
DUMP
Explanation: A logic error was detected in converting the date-time to an internal format. (Issued by module DX10CARD.)
User response: Check the DATETIME statement and contact BMC Support.
DUMP
Explanation: An abend was forced because message DSO4418 exceeded the MAXCC value. (Issued by module DX10SPLS.)
User response: Change MAXCC to a value greater than 12 to ignore the serious error conditions reported by message DSO4418.
UNABLE TO ACQUIRE A SPOOL RECORD AREA
Explanation: A GETMAIN failed. (Issued by module DX10SPLS.)
User response: Increase the region size or contact BMC Support.
ERROR IN REGION SIZE
Explanation: Message DSO4419 exceeded the MAXCC= value. (Issued by module DX10SPLS.)
User response: Refer to message DSO4419 for recommended action.
DUMP
Explanation: Because of an earlier processing error, an internal error occurred while processing mount records: the volume ordinal was zero. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: An internal error occurred while processing mount records and trying to infer the device type from input data. (Issued by module DX10SPLS.)
User response: Explicitly specify the device type.
DUMP
Explanation: This is an internal error: the DATETIME tables were overlaid. (Issued by module DX10SPLS.)
User response: Check the DATETIME statement and contact BMC Software.
INTERNAL ERROR: REJECT COUNTER OVERFLOWED
Explanation: Too many records from the input data sets have been rejected. (Issued by module DX10SPLS.)
User response: Limit the size of the data set used as input.
INTERNAL ERROR: DATETIME TABLES CLOBBERED
Explanation: (Issued by module DX10SPLS.)
User response: Check the DATETIME statement and contact BMC Support.
INTERNAL ERROR: REJECT COUNTER OVERFLOWED
Explanation: Too many records from the input data set have been rejected. (Issued by module DX10SPLS.)
User response: Limit the size of the data set used as input.
INTERNAL ERROR: DATETIME TABLES CLOBBERED
Explanation: (Issued by module DX10SPLS.)
User response: Contact BMC Support.
INTERNAL ERROR: REJECT COUNTER OVERFLOWED
Explanation: Too many records from the input data set have been rejected. (Issued by module DX10SPLS.)
User response: Limit the size of the input data set.
INTERNAL ERROR: SELECT TABLE CLOBBERED
Explanation: (Issued by module DX10SPLS.)
User response: Contact BMC Support.
INTERNAL ERROR: SELECT REJECT COUNTER OVERFLOWED
Explanation: Too many records from the input data set have been rejected. (Issued by module DX10SPLS.)
User response: Limit the size of the input data set.
INTERNAL ERROR: TOTAL SAMPLE COUNTER OVERFLOWED
Explanation: Too many records from the input data set have been rejected. (Issued by module DX10SPLS.)
User response: Limit the size of the input data set.
INTERNAL ERROR DURING SPOOL RECORD SIZE CALCULATION
Explanation: This is an internal error that should not occur. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
INTERNAL ERROR DURING SPOOL RECORD SIZE CALCULATION
Explanation: This is an internal error that should not occur. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The data set ordinal counter overflowed. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The component name was missing from a VSAM map record. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The VSAM data set ordinal counter overflowed. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: An option setting was detected that is not currently implemented. The main DSO load module may have been entered at the wrong offset. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: Message DSO4421 exceeded the MAXCC value. Reports for this volume are suppressed. (Issued by module DX10SPLS.)
User response: Refer to message DSO4421 for the recommended action, or change MAXCC to a value greater than 12 to ignore the error.
APPARENT SEQUENCE ERROR IN OUTPUT FROM SORT/MERGE
Explanation: The message above appears whenever one of the following conditions exists:
A device constants description reflects fewer than the actual number of tracks per cylinder for the device.
User-defined UCB device type descriptions conflict with IBM usage.
User response: Contact BMC Support.
SERIOUS ERROR IN CODE
Explanation: The OS data set counters do not agree. This is an internal error.
User response: Contact BMC Support.
DUMP
Explanation: The VSAM data set counters do not agree. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
MAXCC VALUE EXCEEDED
Explanation: Message DSO4420 exceeded the MAXCC value.
User response: Refer to message DSO4420 for recommended action.
INTERNAL ERROR IN READ ROUTINES FOR EXTRACTION DATA
Explanation: (Issued by module DX10SPLS.)
User response: Contact BMC Support.
INTERNAL ERROR IN READ ROUTINES FOR EXTRACTION DATA
Explanation: No READ was issued for a buffer about to be checked. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: Input data set could not be opened. (Issued by module DX10SPLS.)
User response: Check the DD statement for the data set.
DUMP
Explanation: Message DSO4426 exceeded the MAXCC value. (Issued by module DX10SPLS.)
User response: Refer to message DSO4426 for recommended action.
DUMP
Explanation: Caused by a serious error detected in the integrity of the input or a program logic error occurred. The DIE sample counters do not agree. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
NO VOLUMES WERE ACCEPTED
Explanation: At the end of the INPUT/SORT phase, every volume requested is rejected because no mount, VTOC mapping, VSAM mapping, or head movement records were accepted. Messages DSO4428 or DSO4429 appear before this abend and explain why each volume was rejected. More processing by the Analyzer is impossible. This error may also be caused by invalid concatenation of Extractor files or by using the VOLMAP and NOVOLMAP keywords on the DATA control statement. (Issued by module DX10SPLS.) Some of the reasons that cause this failure are:
The input data files are missing a needed record type(s).
The record types used by the DSO analyzer are:
- 240-0 Record Record, created each recording interval. (Optional, not absolutely required.)
- 240-12 Mount Record, created at extractor startup. Also if volume mounted.(Required).
- 240-13 Head movement record, created continuously. (Required).
- 240-14 VTOC mapping record, created at startup. Also if volume mounted. (Required).
- 240-22 VSAM mapping record, created at startup. (Optional, not absolutely required.)
The 240-12, 240-13, 240-14, and 240-22 records are created by the HEADMOV control card. The subtype 12 and 13 records are keyed by the unit address selection criteria (for example ALL, CHANNEL, NUMBER, RANGE, EXCEPT). The subtype 14 records are generated by VTOC=YES being specified. The subtype 22 records are generated by VSAM=YES.
The CX10HMOV or CM40HMOV extractor module aborted. This may be caused if the REPORT control card did not specify enough CSA, or VSAM=YES was specified and catalog structure caused the extraction process to take excessive time causing the extractor to run out of WSA area.
Either the extractor or the analyzer has specified a CMF record ID other than 240, and the other did not indicate the same CMF record ID.
The DATETIME control cards have excluded all the head movement records.
No system ID was specified, or an incorrect system ID was specified on the DATA control cards.
The wrong extractor ID was specified on the DATA control cards.
User specified NOVOLMAP on DATA control card which excluded all the VTOC records; at least one input file must not have NOVOLMAP specified and it must also contain 240-14 records.
The volume name specified in VOLUME control card was not included in the extractor collection, or there was no activity for the volume(s) specified.
An invalid unit type was specified on the VOLUME control card(s).
User presorted the input data, or concatenated the data in an order that confused DSO analyzer. Insure that for each system ID, the input files are in the order created.
Note
DSO analyzer sorts data as needed. The DSO Analyzer expects data to arrive in the order that the extractor created the data.
The SORT/MERGE failed. Most common is SYSOUT DD card is not specified.
User coded two VOLUME control cards for the same volume. This confuses the analyzer into dropping both volume requests, leaving no volumes to analyze.
The HEADMOVE control card is missing for the extractor run.
User response: Contact BMC Support.
DUMP
Explanation: The integrity of volume blocks was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The device descriptor chain was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The device descriptor chain was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The E35 exit detected an internal error in the control block structure relating to device characteristics for a particular volume. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The volume block chain was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
DUMP
Explanation: The volume mapping processor volume chain was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
VOLUME CHAIN DAMAGED
Explanation: The VSAM map processor volume chain was damaged. This is an internal error. (Issued by module DX10SPLS.)
User response: Contact BMC Support.
MAXIMUM ALLOWABLE CONDITION CODE EXCEEDED
Explanation: Message DSO4439 exceeded the maximum allowable condition code. (Issued by module DX10SPLS.)
User response: Refer to message DSO4439 for recommended action.
MAXIMUM ALLOWABLE CONDITION CODE EXCEEDED
Explanation: Message DSO4440 exceeded the maximum allowable condition code (MAXCC). (Issued by module DX10SPLS.)
User response: Refer to message DSO4440 for recommended action.
