Summary:
This is a brief introduction to CA Datacom messaging…and some of the most important messages to look for.
Looking for the most important messages I need to be careful.
Z/os or Z/vse, CA Datacom/DB or AD
Instructions:
CA Datacom will issue message(s) depending on the severity of the situation.
The first three characters of the message indicates what area the message is issued from:
Here are some of the Datacom error messages that you might become familiar with:
DB00109W BACKOUT JOB jjjjjjjj NUMBER-nnnnn TSN-xxxxxxxx WAITING TO COMPLETE DB00137E INVALID RELEASE DBSYSID MODULE x DB00205E MULTI-USER ... ERROR-nnnn [optional-text] error goes 1050 to 1210 DB00216E ERROR IN SYSIN/SYSIPT DATA DB00217E INSUFFICIENT MEMORY FOR SYSTEM STARTUP DB00218E Insufficient 64-bit memory DB00221E SUPPORT FOR xxxx NOT REQUESTED IN MULTI-USER STARTUP OPTION DB00229E FATAL INTERNAL ERROR - JOB TERMINATED - xxx-xxxx DB00234E FATAL RETURN CODE (RCERROR) - rr (iii) DB00242E REQUIRED ENQ NOT AVAILABLE, MUFNAME= DBDVM01 DB00272E IWM4ECRE ERROR R15(R0)=........ DB00409E SPILL FOUND POSSIBLE BAD BLOCK, DUMP TAKEN, ERROR nnn DB00501E OPEN ERROR - RETURN CODE rr (iii) CXX=cxxname (aaannnn)... DB00801W I/O ERR - NO RECORD FOUND - aaannnnn xxxxx-yy-zzz type DB00802W I/O ERR - WRONG LENGTH RECORD - aaannnnn xxxxx-yy-zzz type DB00803W I/O ERR - UNRECOVERABLE - aaannnnn xxxxx-yy-zzz type DB00817E I/O ERR error dd/dtf-name ccccccc:h:r type volser volume DB01004E PXX AREA I/O ERROR DB11002E UNEXPECTED rr (iii) RETURN CODE ON ttt TABLE FOR ccccc DB01208E RESTART, COMPLETE WITH ERROR(S) DB01209E RESTART, INSUFFICIENT TASK AREAS DB13107E BASE(S) ABOVE NEED ACTION, RESEARCH THEN RESUBMIT MUF WITH RESTART OR NORESTART DB01401E MVS DYNAMIC ALLOCATION ERROR,DDNAME=ddname,R15=n, ERROR=n,INFO=n DB01402W AREA aaannnn NEEDS EXTEND, cccccc VS dddddd DB01403E MVS DYNAMIC ALLOCATION ERROR, RSN=n, WRC=n, INFO=n, RC=c, RCF=c DB01409E DATA SET NAME MISMATCH xxx-y DBSIDPR-z DB01410E DATA SET NAME WRONG CXXNAME x y z
For complete information on CA Datacom messages and the actions to take if you encounter the situation, refer to your release's version of the CA Datacom/DB Message Reference Guide. Refer to the CA Datacom/DB Return Codes chapter for full explanations on the various return codes in the DB00501E message.
The Version 14.0 guide is at https://supportcontent.ca.com/cadocs/0/CA%20Datacom%2014%200%20Public-ENU/Bookshelf_Files/PDF/DatacomDB1402--Message_Ref_ENU.pdf
The Version 15.0 Guide is at: CA Datacom® Messages
Note: A Datacom Multi-User (MUF) should never abend. You can minimize the possibility by being up to date in maintenance.