Академический Документы
Профессиональный Документы
Культура Документы
×××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××
×××××××××
_
U0002 - IMS control region down
- This indicates that a program has filled the region and
the region has abended. It may be: 1) A program running in
the same region as a program that fills a region; 2) Your
program which has filled the region (either because of a
program problem like infinite looping or because you have
not taken a checkpoint for a long time); or 3) A bad
version of IMS is in place (especially likely if it is
experienced on a Sunday).
| U0102 - IMS cannot find the checkpoint ID when you are restarting
| the job. Here is a list of items to check.
| - Check to make sure that the checkpoint ID is the
| correct one that you want to use. Check typing of
| checkpoint id.
| - Ensure that the jobname of the abend and the jobname of
| the restart job are the same.
| - The IMS disk log dataset may have been written to tape.
| Use the Plano supported IMS Checkpoint VOLSER Locator
| (option L.O.I), to find the tape, and data set name of
| the IMS tape log.
| - Check data set name, tape VOL=SER, for log data set if
| IMS log has gone to tape.
U0144 - BMP abended because there were too many BMP's running at
one time. Restart when there are fewer BMP's running.
| U0240 - An IMS online program, (MPP), has timed out. Each and
| every IMS online transaction/program has a set time limit
| as to how many CPU seconds this program will be allowed to
| have. Once the limit has been exceeded the program will
| abend.
| - Check for loops in the program
| - Check for 'GB', end of data base condition, and make
| sure that the program is processing this condition OK.
| - Check the Boolean SSA to make sure that you do not read
| thru the entire data base to get your result.
| - Check your SSA when using secondary indexes and make
| sure the names used in the SSA are valid.
| - Verify the CPU second limit with the DBA group for the
| transaction code.
| U0826 - IMS was unable to open an index data base data set. Check
| for:
| - The index data base data set exist.
| - The index data base data set name is correct
| - The index data base data set DDNAME is correct
| - All index data base data set DDNAMEs are present and
| correct
| - That you have a buffer large enough to hold the data
| - Check for a "DFS730I" error message. There will be
| additional information with this message. Use the
| reason code given and look into the IMS/ESA Messages
| and Code manual for more info.
|
| U0844 - This is a data base full error. Check the DBDLIB that you
| using to make sure it is the correct one. Also check on
| how many records you are adding/inserting.
| U0929 - IMS has found an error when trying to match the DBD and
| the PSB. Verify that the correct libraries are being used.
| U3303 - This implies that the data base were not available for
| use. Check to see that the databases have been started.
|
| DFS057 - The REQUESTED BLOCK ####MODNAME NOT AVAIL.....
| where the ####MODNAME, where #### are HEX NUMBERS
| check MFS source code and make sure that
| .... MSG TYPE=OUTPUT,SOR=(MID,IGNORE)
| .... and the DEV.. has FEAT IGNORE
| ... the name of FORMAT, MID, MOD do not match
|
| SIMLOGON - An MPP tried to send a message to a device. IMS sent
| the message to VTAM. VTAM tried to do an "OPEN DEST"
| on the device but got no response back. Check to make
| sure the device is up and active, and make sure that
| the device you are sending something to is a valid
| device.
|
| BMC2849 - VSAM DATASET NOT EMPTY - DDNAME = ???????? BMC Load
| Utility when VSAM data set is not properly created.
|
| BMC2660 - OSAM Relative BYTE ADDRESS exceeds 31 BIT capacity
|
| BMC2954 - from BMC SECONDARY INDEX BUILD. DBD is not in LIBRARY
| that you are pointing to.