In this section: |
The following chart lists common FOCUS error messages and IDMS response codes.
IDMS Abend Message |
Description |
---|---|
D002 |
A DC###### error was issued with a severity code of 3, 4, or 5 causing the IDMS system to terminate the task. |
D003 |
A program check has occurred during run-unit processing. Probable storage overwritten. |
D004 |
Runaway task has been terminated by the IDMS system because it executed longer than the time specified in the SYSGEN "RUNAWAY INTERVAL" parameter without an intervening wait. |
D005 |
IDMS/DC program has invoked an invalid CA-IDMS function or specified an invalid address for a valid function. |
D009 |
Task terminated by the IDMS system because it exceeded its registered stack space. |
11## 30##
|
Usually indicates a corrupt data source or problem left behind by a DBA change. |
3005 |
An attempt to open a data source file has failed. Check the JCL for a missing or invalid DD command or a mismatch between the DMCL page size and the disk data set blocksize. |
3010 |
An attempt to read from the data source or disk journal has failed: 1) a physical I/O error, 2) attempt to read a relative block outside of the range, 3) failed attempt to initialize the file, 4) with VSAM, insufficient space in the storage pool. |
ABRU |
An external request unit executing under SYSCTL has abended. The abend may have been caused when the request unit exceeded the maximum time allowed between data source requests, or it may have been caused by other factors, as described in the system log. If the abend condition was detected by the check-user, lookaround-time, or external-wait mechanism, the system writes a SNAP DUMP to the log file. |
CKUR |
The CheckUser task has detected that the program ABENDed. |
DC001003 |
Program ABENDed because it exceeded a wait time on a resource, such as a lock (a DBKEY, page lock, or area lock). |
Major |
Minor |
Description |
Action |
---|---|---|---|
09 |
66 |
Data source offline for a reason. |
DBA may be doing updates to or maintenance on an IDMS area. |
nn |
11 |
Insufficient space. |
Time must be scheduled to expand the data source. |
03 nn |
01 01 |
Required area not readied. |
Relates to separating an index out from the data area and the new index area was not added to the program, or the program did not recompile properly. |
09 |
71 |
Page range does not match DMCL. |
DMCL or segment problem. |
Major |
Minor |
Description |
Action |
---|---|---|---|
nn |
69 |
Run Unit could not start or contention problem. |
Rerun job. Check CV log for abend in module IDMSDBMS or other critical system module. |
14 |
69 |
CV not active. |
Bring up CV and rerun job. Also, check the SYSCTL DD card and the rest of the JCL to make sure you are pointing to the correct CV. |
09 |
66 |
Area not available in desired usage mode. Look at SYSOUT to find problem area-name. |
Check to see if any batch local job is running. If so, wait until local job finishes and re-submit. |
nn |
29 |
Deadlock caused by two or more programs locking the same records. |
Allow one of the programs to finish, then rerun the program that failed. |
Information Builders |