ftpdocs.broadcom.com Datacom 14... · CA Technologies Product References This document references the following CA products: CA Datacom®/DB CA Datacom® CICS Services A Datacom®

Message Reference Guide Version 14.02

CA Datacom®/DB

This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2015 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA products:

■ CA Datacom®/DB

■ CA Datacom® CICS Services

■ CA Datacom® Datadictionary™

■ CA Dataquery™ for CA Datacom® (CA Dataquery)

■ CA Datacom® DB2 Transparency

■ CA Datacom® DL1 Transparency

■ CA Datacom® Fast Restore

■ CA Datacom® IMS/DC Services

■ CA Datacom® Presspack

■ CA Datacom® Server

■ CA Datacom® SQL (SQL)

■ CA Datacom® STAR

■ CA Datacom® TOTAL Transparency

■ CA Datacom® VSAM Transparency

■ CA Dynam®/D Disk Management for z/VSE (CA Dynam/D for z/VSE)

■ CA Ideal™ for CA Datacom® (CA Ideal)

■ CA IPC

■ CA Librarian®

■ CA Scheduler® Job Management (CA Scheduler JM)

■ CA SYSVIEW® Performance Management (CA SYSVIEW)

■ CA Common Services for z/OS

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/supportmailto:[email protected]://ca.com/docshttp://ca.com/docs

Documentation Changes

The following documentation updates have been made since the last release of this documentation:

Version 14.02

■ DB02818 (see page 237)I—ONLINE_AREA_MOVE dbid area STATUS - variable-info

■ DB02819I (see page 239)—ONLINE_AREA_MOVE 897 C01 MOVED BLOCK 1 OF 60

■ DB02820I (see page 240)—ONLINE_AREA_MOVE STATUS_OAM dbid area variable-info

■ DB02821I (see page 49)—OLDEP (CBLDBMS/DATACOM? PROGRAM ACCESSED dbid table, job, tranid

■ DB02824I (see page 248)—TABLE_ALTER_24X7 dbid table-name ALTERED ROW 1 of ABOUT 10

■ DB13155W (see page 410)—INVALID BLOCK FORMAT, DBID-nnnn area-aaa BLOCK/TTTR-nnnnnnnn CASE-n COUNT-n

■ DDPIFP0001 (see page 1165) - INVALID FOR TABLE PARTITION

■ DB03300I - DB03380W - DBCDSPR Replication Sending Program messages

■ DB03400I - DB03486E - DBCDRPR Replication Receiver Program messages

Version 14.01

■ DB00289I (see page 89)—ESTAE CXX UPDATES t

■ DB02817E (see page 232)—ONLINE_AREA_MOVE dbid area ERROR - variable-info

■ DB02818I—ONLINE_AREA_MOVE dbid area STATUS - variable-info

■ DB02819I—ONLINE_AREA_MOVE nnnn aaa ON BLOCK bbbbbb of bbbbbb

Contents 7

Contents

Chapter 1: Introduction 19

Chapter 2: Processing, DBUTLTY and SQL Messages 21

CA Datacom/DB Processing Messages (DB0xxxxc) .................................................................................................... 22

DB00214W .......................................................................................................................................................... 64

DB02818I ........................................................................................................................................................... 237

DB02819I ........................................................................................................................................................... 239

DBUTLTY Messages (DB1xxxxc) ................................................................................................................................ 326

SQL Preprocessor Messages (DB2xxxxc) .................................................................................................................. 448

AutoScope Messages (DB3xxxxc) ............................................................................................................................. 511

CA Datacom/DB Messages for Invocation of CAIRIM (DB9xxxxc) ............................................................................ 521

CA Datacom/DB Health Checker Messages ............................................................................................................. 531

Chapter 3: CA Datacom/DB Return Codes 535

Explanation of Code Descriptions ............................................................................................................................ 535

Return Codes ............................................................................................................................................................ 536

blanks - THE COMMAND WAS SUCCESSFUL ..................................................................................................... 536

Return Code 01 - INVALID REQUEST COMMAND ............................................................................................. 537

Return Code 02 - INVALID TABLE NAME ........................................................................................................... 539

Return Code 03 - INVALID KEY NAME ............................................................................................................... 540

Return Code 04 - INVALID RECORD ID .............................................................................................................. 540

Return Code 05 - TABLE NOT OPEN .................................................................................................................. 542

Return Code 06 - TABLE NOT OPEN FOR UPDATE ............................................................................................. 544

Return Code 07 - DATA AREA FULL ................................................................................................................... 545

Return Code 08 - SYSTEM AREA FULL ............................................................................................................... 546

Return Code 09 - PREREQUISITE COMMAND ERROR........................................................................................ 547

Return Code 10 - DUPLICATE MASTER KEY NOT ALLOWED .............................................................................. 549

Return Code 11 - MASTER KEY HAS BEEN MODIFIED—UPDATE REJECTED ...................................................... 550

Return Code 12 - SPECIAL DELETED RECORD .................................................................................................... 551

Return Code 13 - INTERNAL ERROR .................................................................................................................. 552

Return Code 14 - NO RECORD FOUND .............................................................................................................. 557

Return Code 15 - SECURITY VIOLATION ............................................................................................................ 558

Return Code 16 - EXCLUSIVE CONTROL INTERLOCK ......................................................................................... 559

Return Code 17 - INPUT/OUTPUT ERROR ......................................................................................................... 562

Return Code 18 - EXCLUSIVE CONTROL DUPLICATE.......................................................................................... 563

Return Code 19 - END OF TABLE FOR GETIT, END OF AREA FOR GETPS ........................................................... 564

8 Message Reference Guide

Return Code 21 - COMPRESSION ERROR .......................................................................................................... 564

Return Code 22 - ELEMENT NAME NOT FOUND ............................................................................................... 566

Return Code 23 - ELEMENT SECURITY CODE VIOLATION .................................................................................. 567

Return Code 24 - EXCLUSIVE CONTROL EVENTS EXCEEDED ............................................................................. 567

Return Code 25 - INVALID DATABASE ID ........................................................................................................... 568

Return Code 27 - GETIT BLOCK SIZE TOO SMALL .............................................................................................. 569

Return Code 28 - RCD.TOO BIG/LOG BLK.TOO SMALL or LOG AREA BLOCK SIZE TOO SMALL ......................... 570

Return Code 29 - EOF DURING LOGLB COMMAND ........................................................................................... 571

Return Code 31 - KEY LENGTH INCONSISTENCY................................................................................................ 572

Return Code 35 - SOFTWARE INTEGRITY ERROR DETECTED ............................................................................. 573

Return Code 36 - USER VIEW NOT OPEN .......................................................................................................... 573

Return Code 37 - INVALID ADDRESS ................................................................................................................. 574

Return Code 38 - PREVIOUS LOGGING ERROR .................................................................................................. 575

Return Code 39 - CANNOT PROCESS OLD REQUEST ......................................................................................... 575

Return Code 40 - TASK SAVE AREA ERROR ....................................................................................................... 576

Return Code 43 - NO VALID INDEX .................................................................................................................... 577

Return Code 44 - SECURITY ENVIRONMENT ERROR ......................................................................................... 579

Return Code 45 - OPERATOR REQUEST ERROR ................................................................................................. 580

Return Code 46 - TABLE ALREADY OPEN FOR UPDATE ..................................................................................... 581

Return Code 47 - INVALID DIRECTORY (CXX) .................................................................................................... 582

Return Code 48 - A REPLICATED OR PARTITIONED DATABASE OPEN ERROR ................................................... 584

Return Code 51 - INVALID MIX OF JOBS INCLUDING DBUTLTY FUNCTIONS ..................................................... 584

Return Code 52 - RECOVERY FILE OPEN/CLOSE FAILURE .................................................................................. 585

Return Code 55 - BAD USER REQUIREMENTS TABLE ........................................................................................ 586

Return Code 56 - BAD MASTER LIST .................................................................................................................. 586

Return Code 57 - BAD DBRW ADDRESS ............................................................................................................ 587

Return Code 58 - TABLE NOT LOADED .............................................................................................................. 587

Return Code 59 - SECURITY VALIDATION FAILURE ............................................................................................ 588

Return Code 60 - DB CANNOT OPEN THE LOG AREA ........................................................................................ 588

Return Code 61 - EXCLUSIVE CONTROL, WAIT EXCEEDED ................................................................................ 590

Return Code 63 - BAD DEVICE TYPE .................................................................................................................. 591

Return Code 65 - AN OPEN ERROR OCCURRED ................................................................................................ 591

Return Code 66 - MULTI-VOLUME OPEN FAILURE ............................................................................................ 593

Return Code 67 - CXX INTERLOCK ..................................................................................................................... 593

Return Code 68 - MULTI-USER FACILITY ........................................................................................................... 594

Return Code 69 - TABLE HAS NO CURRENT INDEX ............................................................................................ 601

Return Code 70 - BUFFER TOO SMALL .............................................................................................................. 602

Return Code 71 - DB INTERFACE COULD NOT INITIALIZE .................................................................................. 604

Return Code 72 - INVALID DATA AREA .............................................................................................................. 604

Return Code 73 - DATA SYNCHRONIZATION CHECK ......................................................................................... 606

Return Code 74 - OPEN ALLOCATION ERROR.................................................................................................... 607

Return Code 75 - DIRECTORY MAINTENANCE ERROR ....................................................................................... 608

Contents 9

Return Code 76 - OPEN ERROR ......................................................................................................................... 616

Return Code 78 - FBA DISK ERROR .................................................................................................................... 619

Return Code 79 - CXX IS WRONG VERSION ....................................................................................................... 620

Return Code 80 - DDM ENVIRONMENTAL ERROR ............................................................................................ 620

Return Code 81 - DDM PROCESSING ERROR ..................................................................................................... 628

Return Code 82 - DB SVC PROGRAM PSW-KEY ERROR ..................................................................................... 629

Return Code 83 - SVC INTEGRITY ERROR .......................................................................................................... 629

Return Code 84 - MULTI-TASKING ERROR ........................................................................................................ 630

Return Code 85 - INSUFFICIENT TASKS ............................................................................................................. 632

Return Code 86 - THE MULTI-USER FACILITY HAS ABENDED ............................................................................ 633

Return Code 87 - RESOURCE ACCESS VIOLATION DURING OPEN ..................................................................... 637

Return Code 88 - DATABASE HAS BEEN DISABLED ........................................................................................... 637

Return Code 89 - INSUFFICIENT MEMORY ........................................................................................................ 639

Return Code 91 - COMPOUND BOOLEAN SELECTION FACILITY ERROR ............................................................ 640

Return Code 92 - SET SELECTION INTERRUPT ................................................................................................... 647

Return Code 93 - ATTEMPT TO POSITION PAST END/BEG-OF-SET ................................................................... 648

Return Code 94 - GENERAL ERROR INDICATOR ................................................................................................ 649

Return Code 95 - INCOMPLETE REQUEST ......................................................................................................... 680

Chapter 4: Recovery File Read (READRXX) Return Codes 681

Chapter 5: SQL Codes 683

SQL Memory Guard .................................................................................................................................................. 683

SQL Preprocessor Return Codes ............................................................................................................................... 686

SQL Return Codes 0 through 243 ............................................................................................................................. 686

0 - THE COMMAND WAS SUCCESSFUL .............................................................................................................. 686

100 - NO ROW FOUND ...................................................................................................................................... 687

170 - CONSTRAINT(S) DID NOT CONFIRM - TABLE PLACED IN CHECK STATUS ................................................. 687

243 - EXTENSION TO ANSI SQL-86 (SQLMODE-ANSI/FIPS) ................................................................................ 687

SQL Return Codes -1 through -999 ........................................................................................................................... 688

-1 - NULL INDICATOR VARIABLE REQUIRED FOR OUTPUT HOST VARIABLE NUMBER nnn ............................... 688

-2 - EMPTY QUERY STRING ................................................................................................................................ 688

-3 - CANNOT REVOKE FROM YOURSELF ............................................................................................................ 688

-4 - OVERFLOW: TYPE ACTION .................................................................... 689

-5 - TABLE tablename IN DDD AND NOT IN CXX ............................................................................................... 689

-6 - STRING CONSTANT TOO LONG ................................................................................................................... 690

-7 - INCOMPLETE STRING. CHECK FOR MISSING QUOTES ................................................................................ 690

-8 - CANNOT GRANT TO YOURSELF ................................................................................................................... 690

-10 - UNABLE TO ALLOCATE MEMORY .............................................................................................................. 691

-12 - COLUMN FUNCTIONS NOT ALLOWED IN SET CLAUSE OF QUERY ............................................................ 691

-14 - TABLE/VIEW DOES NOT EXIST:(table/new-name) AUTHID:(auth-id) ....................................................... 691


-15 - AUTHID (auth-id) NOT DEFINED................................................................................................................ 692

-16 - DEPENDENT PLAN (auth-id.plan-name) IN USE ........................................................................................ 692

-17 - MODIFICATION OF COLUMN TO INCOMPATIBLE DATATYPE IS NOT ALLOWED ....................................... 693

-18 - WITH CHECK OPTION IS NOT ALLOWED ON NON-UPDATABLE VIEWS .................................................... 693

-19 - INDEX AND TABLE AUTHIDS DO NOT MATCH: aaaa, bbbb ....................................................................... 694

-20 - BAD SYNTAX: description WHEN THE ERROR OCCURRED, THE SYNTAX BELOW HAD BEEN PARSED: statement ........................................................................................................................................... 694

-21 - DEFAULT CHARACTER LITERAL TOO LONG ............................................................................................... 694

-24 - VIEWS CONTAINING FUNCTIONS OR GROUP BY CANNOT BE JOINED...................................................... 695

-25 - INCOMPLETE COMMENT .......................................................................................................................... 695

-26 - EXCEEDS MAX NUMBER OF TABLES/VIEWS PERMITTED IN SUBSELECT ................................................... 695

-27 - CANNOT USE GROUP BY IN QUERY THAT REFERENCES A GROUPED VIEW .............................................. 696

-29 - HAVING CLAUSE IS ILLEGAL WHEN A REFERENCED VIEW CONTAINS A HAVING ..................................... 696

-30 - SQL IDENTIFIERS MAY NOT EXCEED 32 BYTES IN LENGTH ........................................................................ 696

-31 - CANNOT REFERENCE A VIEW CONTAINING SELECT DISTINCT IN THIS STATEMENT................................. 697

-32 - STATEMENT IS TOO LARGE TO COMPILE .................................................................................................. 697

-33 - AMBIGUOUS COLUMN REFERENCE: x...x .................................................................................................. 697

-34 - ILLEGAL CORRELATION NAME nnnn ......................................................................................................... 698

-35 - TTM IS UNUSABLE: SQLCODE xxx, DB RC yy(zzz) ON INITIALIZATION ...................................................... 698

-36 - BAD FOREIGN KEY: reason code,A,B,C,D,E,F,G ......................................................................................... 699

-37 - CONSTRAINT REBIND FAILED: A,B,C,D,E,F ................................................................................................ 701

-38 - DB2 TRANSPARENCY OPTION IS NOT INSTALLED ..................................................................................... 702

-39 - NEGATIVE RESULT FOR UNSIGNED DECIMAL TARGET .............................................................................. 702

-40 - CONSTRAINT AUTO-REBIND IN PROGRESS. PLEASE TRY AGAIN. .............................................................. 702

-41 - DATATYPES OF OPERATION op-string NOT COMPATIBLE ......................................................................... 703

-42 - INVALID USE OF ESCAPE CHARACTER IN PATTERN OF LIKE PREDICATE ................................................... 703

-43 - COLUMN FUNCTION ON INVALID TYPE .................................................................................................... 703

-44 - HOST VARIABLE NUMBER HAS INVALID DATA TYPE ............................................................. 704

-53 - STRING TOO LONG FOR COLUMN nnn ..................................................................................................... 704

-54 - UNEQUAL NUMBER OF COLUMNS AND VALUES ...................................................................................... 704

-55 - DUPLICATE NAMES IN INSERT/ALTER/CREATE LIST: aaaa ....................................................................... 705

-56 - entity-type entity-name ALREADY EXISTS ................................................................................................. 705

-57 - SPECIFIED MORE COLUMNS OR VALUES THAN THE TABLE HAS............................................................... 705

-58 - COLUMN aaaa DATATYPE INCOMPATIBLE WITH bbbb DATATYPE ........................................................... 706

-60 - nnnn IS GREATER THAN MAXIMUM ALLOWABLE NUMBER OF COLUMNS .............................................. 706

-66 - ILLEGAL NUMBER nnnn IN ORDER SPECIFICATION ................................................................................... 706

-67 - COLUMN FUNCTIONS NOT ALLOWED IN WHERE CLAUSE OF QUERY ...................................................... 707

-69 - TOO MANY SET CLAUSES IN UPDATE COMMAND .................................................................................... 707

-70 - ODER BY COLUMN aaaa IS NOT IN SELECT LIST OR IS A DUPLICATE ........................................................ 707

-71 - SELECTING MORE THAN ONE ITEM IN A SUBQUERY ................................................................................ 707

-72 - CANNOT NEST COLUMN FUNCTIONS ....................................................................................................... 708

-73 - SELECTED COLUMNS MUST BE IN THE GROUP BY CLAUSE ...................................................................... 708

Contents 11

-75 - CANNOT USE COLUMN FUNCTIONS WITH NO GROUP BY CLAUSE .......................................................... 708

-76 - colName IN HAVING NOT GROUP COLUMN OR COLUMN FUNCTION ARGUMENT ................................. 709

-79 - UPDATE/DELETE WHERE CURRENT OF cursorname ON READ ONLY CURSOR ......................................... 709

-80 - ONLY ONE DISTINCT CLAUSE ALLOWED PER QUERY ................................................................................ 709

-82 - EACH QUERY IN A UNION MUST HAVE THE SAME NBR OF PROJECTED COLUMNS ................................. 710

-101 - A SYNONYM ON A SYNONYM IS NOT ALLOWED .................................................................................... 711

-103 - MUST USE COLUMN FUNCTIONS IF HAVING CLAUSE WITH NO GROUP BY ........................................... 712

-105 - aaa IN bb ................................................................................................................................................. 713

-109 - VIEW COLUMN CONTAINING EXPRESSION OR FUNCTION USED ILLEGALLY .......................................... 714

-110 - ORDER BY IS NOT ALLOWED IN A VIEW DEFINITION .............................................................................. 714

-111 - THE VIEW IS NOT UPDATABLE BECAUSE IT CONTAINS A SUBQUERY ..................................................... 715

-113 - THE VIEW'S COLUMN IS NOT UPDATABLE: aaaa .................................................................................... 715

-117 - RAAT/CBS ERROR: CMD=xxxxx TBL=ttt DBID=nnnn KEY=kkkkk RC=rr (iii) .............................................. 715

-118 - DSF dsf-code ERROR OCCURRED DURING SQL DSF PROCESSING ........................................................... 716

-119 - product_name: error_text ...................................................................................................................... 716

-120 - PROGRAM TIMESTAMP timestamp-in-decimal NOT = PLAN TIMESTAMP timestamp-in-decimal......... 717

-121 - STATEMENT REBIND ERROR ................................................................................................................... 717

-122 - STATEMENT aaaa NOT FOUND ............................................................................................................... 717

-123 - PLAN ALREADY EXISTS ............................................................................................................................ 718

-124 - PLAN authid.planname DOES NOT EXIST ................................................................................................ 718

-125 - PLAN CURRENTLY IN USE ........................................................................................................................ 718

-126 - NO MORE WORK SPACE .......................................................................................................................... 719

-127 - sql-object-name NOT FOUND ................................................................................................................. 719

-128 - LUW ABORTED ........................................................................................................................................ 720

-129 - RRS COMMIT ROLLBACK ......................................................................................................................... 720

-130 - CURSOR NOT UPDATEABLE ..................................................................................................................... 721

-131 - RESULT TABLE LENGTH TOO LONG ......................................................................................................... 721

-132 - INVALID PLAN OPTION: STRING DELIMITER ........................................................................................... 722

-133 - CURSOR NAME aaaa NOT DECLARED ..................................................................................................... 722

-134 - UNKNOWN DYNAMIC/CURSOR STATEMENT-ID (aaaa) .......................................................................... 722

-135 - INVALID CURSOR STATE (STMT-ID=aaaa) ............................................................................................... 723

-136 - SQLDA TRUNCATED - NEEDED aaaa ENTRIES ......................................................................................... 723

-137 - PLAN OPTION CBSIO EXCEEDED .............................................................................................................. 724

-138 - INVALID ‘PRIORITY’ PLAN OPTION: ......................................................................................................... 724

-139 - INVALID PLAN OPTION: TIMEMIN ........................................................................................................... 724

-140 - INVALID PLAN OPTION: TIMESEC ............................................................................................................ 725

-141 - INVALID ‘PLNCLOSE’ PLAN OPTION: x ..................................................................................................... 725

-142 - MORE THAN 1 ROW SELECTED ............................................................................................................... 725

-143 - INVALID PLAN OPTION: DECPOINT ......................................................................................................... 726

-144 - TRX ISOLATION LEVELS UNMATCHED ..................................................................................................... 726

-145 - INVALID ‘ISOLEVEL’ PLAN OPTION: ......................................................................................................... 726

-146 - AUTHORIZATION ID LENGTH > 18 ........................................................................................................... 727


-147 - OP. NOT ALLOWED AT ISOL. LEVEL U ..................................................................................................... 727

-148 - SUBQUERY AT LVL aaaa NBR bbbb RETURNED MORE THAN 1 ROW ..................................................... 727

-149 - PLAN CAN'T SPECIFY DATACOM SQLMODE WHEN MUF OPTION SPECIFIES ANSI ................................. 728

-150 - AUTHORIZATION ID MUST MATCH SCHEMA'S AUTHORIZATION ID ....................................................... 728

-151 - INVALID PRECISION OR SCALE SPECIFICATION ON aaaa ......................................................................... 728

-152 - MAXIMUM NUMBER OF TABLES EXCEEDED FOR OPERATION ............................................................... 729

-153 - DUPLICATE CURSOR NAME DETECTED ................................................................................................... 729

-155 - NUMBER OF COLUMNS IN VIEW NOT EQUAL TO NUMBER IN QUERY ................................................... 729

-156 - VIEW xxx WITH CHECK OPTION VIOLATION ........................................................................................... 730

-157 - TTM INIT. FAILED. SQL CODE xxx, DB RC yy(zzz). .................................................................................. 730

-158 - CANNOT CREATE SYNONYM FOR INVALID VIEW aaaa ........................................................................... 731

-159 - HOST VARIABLE INCOMPATIBLE WITH COLUMN AT POSITION aaaa ..................................................... 731

-161 - colname datatype(prec,scale) INVALID DATA: hh.................................................................................. 732

-162 - CANNOT INSERT AND SELECT ON THE SAME TABLE ............................................................................... 732

-163 - MORE THAN 1 DEFAULT SPECIFIED FOR A COLUMN .............................................................................. 733

-164 - CHARACTER DEFAULT MORE THAN 20 BYTES ........................................................................................ 733

-165 - DUPLICATE CONSTRAINT NAME: nnnnnnnn mmmmmmmm ................................................................ 733

-166 - TBL authid.tblname CHECK PENDING ..................................................................................................... 734

-167 - DOMAIN CONSTRAINT nnnnnnnn.mmmmmmmm VIOLATION ............................................................. 734

-168 - THE TABLE ALREADY HAS A PRIMARY KEY, ONLY ONE MAY BE DEFINED ............................................... 734

-169 - THE REFERENCED COLUMNS DID NOT REFER TO A CANDIDATE KEY ..................................................... 735

-171 - THE REFERENCED TABLE DOES NOT CONTAIN A PRIMARY KEY ............................................................. 735

-172 - THE NUMBER OF REFERENCING AND REFERENCED COLUMNS DOES NOT MATCH ............................... 735

-173 - THE REFERENCING AND REFERENCED COLUMNS ARE NOT EQUIVALENT.............................................. 736

-174 - UPDATE/DELETE CANNOT HAVE CORRELATED SUBQRY ........................................................................ 736

-175 - FOREIGN KEY REFERENCE VIOLATION ........................................................... 736

-176 - FOREIGN KEY VALUE VIOLATION ................................................................... 737

-177 - PRIMARY/UNIQUE CONSTRAINT CANNOT BE DROPPED DUE TO REFERENCE ....................................... 737

-178 - WITH CHECK OPTION CANNOT BE DROPPED FROM A VIEW DEFINITION .............................................. 737

-179 - CONSTRAINT mmmmm nnnnn NOT FOUND .......................................................................................... 738

-180 - ROW HELD BY PREVIOUS LOGICAL UNIT OF WORK WAS DELETED ........................................................ 738

-181 - ROW HELD BY PREVIOUS LOGICAL UNIT OF WORK WAS UPDATED ....................................................... 738

-182 - UNIQUE/PRIMARY CANNOT BE SPECIFIED DUE TO NULL ON nnnnnn ................................................... 739

-183 - MUST SPECIFY DATACOM SQLMODE FOR CURSORS TO SURVIVE UNITS OF WORK .............................. 739

-184 - COLUMN NAME LIST REQUIRED ON CREATE VIEW CONTAINING NON-SIMPLE COLUMN..................... 739

-185 - accessor-id HAS NO action-type AUTHORITY ON object ........................................................................ 740

-188 - DROP NOT ALLOWED DUE TO FOREIGN REFERENCES ............................................................................ 742

-189 - NO RESULT FORMAT SPECIFIED .............................................................................................................. 743

-190 - OPERAND 1 OR RESULT FORMAT MUST BE INTERNAL TO DO CONVERSION ......................................... 743

-191 - BOTH OPERANDS MUST BE IN INTERNAL FORMAT ................................................................................ 743

-192 - RESULT FORMAT MUST BE INTERNAL TO DO VERIFICATION ................................................................. 744

-193 - CENTURY nn IS LARGER THAN 99............................................................................................................ 744

Contents 13

-194 - IT IS INVALID TO ADD xx AND zz DATATYPES .......................................................................................... 744

-195 - IT IS INVALID TO SUBTRACT xx AND zz DATATYPES ................................................................................ 745

-198 - YEAR yy IS LARGER THAN 99 ................................................................................................................... 745

-199 - MONTH mm IS NOT BETWEEN 1 AND 12 INCLUSIVE ............................................................................. 745

-200 - DAY dd OUT OF RANGE FOR MONTH mm, YEAR yy ............................................................................... 746

-201 - HOUR hh OUT OF RANGE ........................................................................................................................ 746

-202 - MINUTE mm OUT OF RANGE .................................................................................................................. 746

-203 - SECOND ss OUT OF RANGE ..................................................................................................................... 747

-204 - MICROSECOND ssssss GREATER THAN 99 .............................................................................................. 747

-205 - INVALID DATATYPE xx FOR SCALAR FUNCTION nn ................................................................................. 747

-206 - OP2 NOT ALLOWED IF OP1 IS A TIMESTAMP FOR SCALAR FUNCTION CHAR ......................................... 748

-207 - RESULT DATATYPES IN CASE/COALESCE/NULLIF EXPRESSION ARE INCOMPATIBLE .............................. 748

-208 - CASE EXPRESSION MUST CONTAIN AT LEAST ONE NON-NULL RESULT EXPRESSION ............................. 748

-209 - operation DISALLOWED ON object ......................................................................................................... 749

-210 - ROLLBACK INCOMPATIBLE WITH USE OF RESOURCE RECOVERY SERVICES ........................................... 749

-214 - ARRAY INDEX MUST BE A LITERAL IN THIS CONTEXT ............................................................................. 750

-215 - INDEX index-value MUST BE BETWEEN lower-limit AND upper-limit INCLUSIVE ....... 750

-216 - BAD ARRAY VALUE: reason ..................................................................................................................... 750

-217 - disallowed-language-element NOT ALLOWED disallowed-context ........................................................ 751

-218 - CANNOT DETERMINE JULIAN DATE WITH MONTH = mm ...................................................................... 751

-219 - JULIAN DATE HAS GONE NEGATIVE: dddd .............................................................................................. 751

-223 - A TIME STRING CANNOT CONTAIN MORE THAN ONE A: aa ................................................................... 752

-224 - A TIME STRING CANNOT CONTAIN MORE THAN ONE P: pp ................................................................... 752

-225 - A TIME STRING CANNOT CONTAIN MORE THAN ONE BLANK BEFORE THE A OR P ............................... 752

-226 - NO M AFTER THE A OR P OR TOO MANY COLONS IN A TIME STRING .................................................... 753

-227 - THERE MUST BE AN M AFTER THE A OR P IN A TIME STRING ................................................................ 753

-228 - TOO MANY NODES IN CHARACTER STRING: node count is n ................................................................. 753

-229 - TOO MANY DIGITS PER NODE IN STRING: xxxx ....................................................................................... 754

-230 - THE VALUE OF A NODE IS OUT OF RANGE: xxxx ..................................................................................... 754

-231 - NUMBER OF SLASHES IS n, ONLY TWO ALLOWED: xxxx ......................................................................... 754

-232 - NO AM OR PM FOUND IN TIME CHARACTER STRING WITH ONE COLON: xxxx ..................................... 755

-233 - NUMBER OF COLONS MUST BE 1 OR 2. FOUND n .................................................................................. 755

-234 - FOUND AN M BUT NO A OR P TO GO WITH IT: xxxx ............................................................................... 755

-235 - NUMBER OF PERIODS CAN ONLY BE 2. FOUND n ................................................................................... 756

-236 - NUMBER OF DASHES CAN ONLY BE 3. FOUND n .................................................................................... 756

-237 - NUMBER OF DIGITS FOR MICROSECONDS CANNOT EXCEED 6, FOUND n: xxxx ..................................... 756

-238 - UNRECOGNIZABLE DATE/TIME FORMAT: xxxx ....................................................................................... 757

-241 - SQL REFERENTIAL INTEGRITY IS NOT ALLOWED ON A DL1/T TABLE ...................................................... 757

-242 - CONFLICT ALTERING COLUMN xxx ......................................................................................................... 757

-243 - ANSI EXTENSION ..................................................................................................................................... 758

-244 - NOT ALLOWED WITH SQLMODE=ANSI/FIPS ........................................................................................... 758

-245 - CONFLICTING SECURITY MODES ............................................................................................................. 758


-246 - INVALID AREA NAME: aaaa ..................................................................................................................... 759

-247 - accessor-id HAS NO CREATE SCHEMA AUTHORITY ................................................................................. 759

-248 - accessor-id HAS NO AUTHORITY TO USE "GRANTED BY" FORM OF REVOKE ......................................... 759

-249 - REFERENCED TABLE aaa.ttt PLUS n OTHERS IN CHECK STATUS.............................................................. 760

-250 - EXCEPTION TABLE authid.tblname NOT FOUND .................................................................................... 761

-251 - TABLE HAS NO CONSTRAINTS ................................................................................................................. 761

-252 - TABLE NOT IN A CHECK STATE ................................................................................................................ 761

-254 - REVOKE WOULD CASCADE BUT "CASCADE" NOT SPECIFIED .................................................................. 762

-255 - COLUMN xxx NOT NULL WITHOUT DEFAULT ......................................................................................... 762

-256 - RQA TOO LARGE FOR TABLE ttt .............................................................................................................. 763

-257 - FOREIGN KEY COLUMN xxx NOT FOUND ................................................................................................ 764

-258 - TABLE FULL - DBID=nnnn INTERNAL NAME aaa...................................................................................... 764

-259 - INDEX FULL - DBID=nnnn ........................................................................................................................ 765

-260 - UNIQUE CONSTRAINT constraint-name DUPLICATES KEY key-name ..................................................... 765

-261 - UNIQUE constraint-name COLUMN column-name NOT FOUND ........................................................... 765

-262 - REFERENCING TABLE xxx.xxx IN CHECK-RELATED STATE ........................................................................ 766

-263 - DUPLICATE KEY VALUE REJECTED DBID TBL ................................................... 766

-264 - INDEX ALREADY EXISTS xxx ..................................................................................................................... 766

-265 - INDEX DOES NOT EXIST aaaa.bbbb ......................................................................................................... 767

-269 - FOREIGN KEY LOOP ................................................................................................................................. 767

-272 - ERROR DURING AUTOMATIC REBINDING OF VIEW authid.viewname ................................................... 767

-273 - GRANT AND REVOKE STATEMENTS NOT ALLOWED ............................................................................... 768

-274 - CANNOT CREATE AN INDEX ON A VIEW ................................................................................................. 768

-275 - SQLDA SPECIFIES n MORE HOST VARIABLES THAN IN STATEMENT ....................................................... 768

-276 - SQLDA SPECIFIES n FEWER HOST VARIABLES THAN IN STATEMENT ...................................................... 769

-277 - aaaa RECEIVED UNKNOWN DURATION TYPE ......................................................................................... 769

-278 - INVALID PREC(xxx) OR SCALE(zzz) FOR DECIMAL DATATYPE .................................................................. 769

-279 - INVALID DATE TABLE INDEX (xxx) ........................................................................................................... 770

-280 - INVALID TIME TABLE INDEX (xxx)............................................................................................................ 770

-281 - INVALID TIMESTAMP TABLE INDEX (xxx) ................................................................................................ 770

-282 - NO OPERAND NODE RECEIVED ............................................................................................................... 770

-283 - NO OPERAND VALUE RECEIVED .............................................................................................................. 771

-284 - NON-NUMERIC ITEM FOUND IN STRING ............................................................................. 771

-286 - SUBSTR FUNCTION ARGUMENTS ARE OUT OF RANGE ......................... 771

-287 - DL1/T CONSTRAINT ENFORCEMENT MODULE DLSERV NOT FOUND ..................................................... 772

-289 - LITERAL TOO LARGE/SMALL ...................................................................................................... 772

-290 - DATATYPE OF FIRST OPERAND OF LIKE NOT CHARACTER STRING ......................................................... 772

-291 - INDEX NOT IN SEQUENCE .......................................................................................................... 773

-292 - VARIABLES PROVIDED FOR SELECT LIST COLUMNS ...................................................... 773

-293 - PREDICATE INVALID BECAUSE HOST VARIABLE HAS THE NULL VALUE ....................................... 773

-294 - INVALID MIXED DATA IN VALUE ASSIGNED TO column_name ............................................................... 774

-296 - INVALID MIXED DATA IN COLUMN column_name ................................................................................. 774

Contents 15

-297 - INVALID MIXED DATA IN LIKE PATTERN .................................................................................................. 774

-298 - INVALID MIXED DATA IN VARGRAPHIC OPERAND .................................................................................. 775

-299 - LIKE ESCAPE OPTION NOT ALLOWED WITH MIXED DATA ...................................................................... 775

-300 - CANNOT EXECUTE UNPREPARED/INVALID STATEMENT statement_name ............................................ 775

-301 - PREPARE OF SELECT REJECTED - CURSOR cursor_name IN OPEN STATE ............................................... 776

-302 - INVALID USE OF PARAMETER MARKER .................................................................................................. 776

-303 - STATEMENT-NAME OF CURSOR cursor_name NOT PREPARED SELECT STATEMENT ............................ 776

-304 - CANNOT DESCRIBE UNPREPARED STATEMENT statement_name ......................................................... 777

-305 - SQLDA HAS count HOST VARIABLES - STATEMENT HAS count PARAMETER MARKERS ......................... 777

-306 - STATEMENT TYPE CANNOT BE PREPARED .............................................................................................. 777

-307 - STATEMENT-NAME statement_name CAN ONLY BE USED WITH ONE CURSOR .................................... 778

-308 - PREPARE HOST VARIABLE SOURCE STATEMENT LENGTH INVALID ........................................................ 778

-309 - HOST VARIABLES CANNOT BE USED IN DYNAMICALLY PREPARED STATEMENTS .................................. 778

-310 - COMBINATION OF CHECKPLAN=checkplan_value, CHECKWHO=checkwho_value, AND CHECKWHEN=checkwhen_value IS INVALID ..................................................................................................... 779

-311 - EMBEDDED UPDATE OR DELETE REFERENCES DYNAMIC CURSOR ......................................................... 779

-312 - NO SQLDA FOR EXECUTE OF A STATEMENT WITH PARAMETER MARKERS............................................ 779

-313 - NO SUCH PRIVILEGE IS grantable or revokable ON object_name .......................................................... 780

-314 - EXTERNALLY SECURED PLANS REQUIRE AUTHID.PLAN-NAME < 26 BYTES ............................................. 780

-315 - ONLY THE PLAN CREATOR MAY MODIFY PLAN SECURITY OPTIONS DURING REBIND ........................... 780

-316 - %s.%s OUTSIDE SCOPE OF JOINED TABLE ............................................................................................... 781

-317 - CURSOR cursor-name ERROR: MULTIPLE stmt-type STATEMENTS ATTEMPTED ................................... 781

-317 (alternate version) - CURSOR REQUIRED ERROR: CURSOR REQUIRED FOR NON-DYNAMIC SELECT ........ 781

-318 - URI=YES IS REQUIRED FOR SQL TO USE TABLE (DATACOM-NAME) ttt DBID nnnn ................................ 782

-319 - LUW IS TIMING OUT - TRY AGAIN (LUWID=luw-id-string, TASK=task-nbr, JOB=job-name) ................... 782

-320 - message describing user error ................................................................................................................ 783

-321 - INVALID SQLCODE sqlcode HAS BEEN GENERATED ................................................................................ 783

-322 - INVALID SQLSTATE .................................................................................................................................. 783

-323 - LUW_STATEMENT_LIMIT OF x STATEMENTS EXCEEDED - TRY A COMMIT ............................................ 784

-324 - BAD NUMERIC LITERAL: n (NON-DIGIT/SPACE EMBEDDED) ................................................................... 784

-326 - MAXIMUM NUMBER (number) OF DIAGNOSTICS AREAS EXCEEDED ..................................................... 785

-435 - USER CONDITION user-cond-name SIGNALLED WITH NO ATTACHED ERROR MESSAGE ....................... 786

-436 - RESIGNAL FOR SQLSTATE sqlstate REQUESTED WHEN HANDLER NOT ACTIVE ...................................... 787

-437 - NO HANDLER EXISTS FOR USER-DEFINED CONDITION NAME name-string ............................................ 787

-438 - SQLSTATE sqlstate-value WAS SIGNALLED WITH NO ATTACHED ERROR MESSAGE ............................... 787

-439 - sqlstate-value IN handler-name:error-description ................................................................................. 788

-441 – PROC: msg-text ...................................................................................................................................... 788

-501 - INVALID CURSOR STATE (STMT - ID=aaaa) ............................................................................................. 789

-502 - CURSOR ALREADY OPEN ......................................................................................................................... 789

-504 - PLAN OPTION ERROR: error-string ......................................................................................................... 790

-505 - ON-CLAUSE ERROR: x NOT ALLOWED ..................................................................................................... 790

-530 - PROC authid.name: msg-string ............................................................................................................... 791



-532 - TRIG authid.name: msg-string ................................................................................................................ 792

-533 - TRIG authid.name: msg-string ................................................................................................................ 792

-534 - msg-string ............................................................................................................................................... 792


-537 - msg-string ............................................................................................................................................... 793

-559 - SECURITY FACILITY NOT ENABLED .......................................................................................................... 793

-560 - TEMPORARY TABLE AREA (TTM) FULL .................................................................................................... 794

-561 - TTM TOO SMALL, SEE ERROR ACTION .................................................................................................... 795

-562 - INVALID DATACOM NAME ...................................................................................................................... 795

-563 - INVALID ORDER: ---USE 'ASC' OR 'DESC' ........................................................................................ 796

-564 - ONLY ONE PRIMARY KEY MAY BE DEFINED ............................................................................................ 796

-565 - HEX LITERALS MUST HAVE EVEN NUMBER OF HEX DIGITS: xxx ............................................................. 796

-566 - INVALID HEX DIGIT IN HEX LITERAL --USE 0-9, A-F ....................................................................... 797

SQL States ................................................................................................................................................................. 798

SQLCA Formats .................................................................................................................................................. 798

SQL State Classes ............................................................................................................................................... 808

SQL States Table ................................................................................................................................................ 810

Chapter 6: DB2 Mode Codes 819

Chapter 7: SVC or z/OS PC Error Codes 823

Chapter 8: Communication Return Codes 833

Chapter 9: General Description 837

Chapter 10: Unnumbered Messages 839

Chapter 11: Numbered Reporting Facility Messages (DRxxxxxa) 849

Chapter 12: Online Panel Error Codes 931

Record/Table Field Maintenance Panel Error Codes ............................................................................................... 931

Element Structure Maintenance Panel Error Codes ................................................................................................ 934

Key Structure Maintenance Panel Error Codes ........................................................................................................ 934

Attribute Update Panel Error Codes ........................................................................................................................ 935

Profile Maintenance Panel Error Codes ................................................................................................................... 936

Contents 17

Chapter 13: Input Creation Facility Error Messages 937

Chapter 14: CA Datacom Datadictionary Unnumbered Messages 939

Chapter 15: CA Datacom Datadictionary Numbered Messages 949

SDC Message Identifier Format .............................................................................................................................. 1257

Chapter 16: DSF Return Codes 1387

Chapter 17: Abend Codes 1489

Chapter 18: DSF Internal Return Codes 1497

Chapter 1: Introduction 19

Chapter 1: Introduction

Use this book with CA Datacom/DB.

Error messages and return codes are tools you can use to identify problems and the actions required to correct the situation causing the problem. The messages and codes listed in this guide provide the following information:

■ Message or return code

■ Reason the message was generated

■ Recommended action in response to the message:

If the message indicates an error, procedures are provided for correction and, if required, recovery.

If the message is a warning or is for information only, it is so labeled.

When operating CA Datacom/DB, you can receive messages from another CA product installed on your system. In addition to this manual, you need the message guides for the other CA products that you have installed.

For certain error messages or return codes, you are referred to other CA Datacom manuals for details about specific tasks. Also, in your support of other products, you may need to see the manuals for those other products.


Chapter 2: Processing, DBUTLTY and SQL Messages

All CA Datacom/DB processing and DBUTLTY messages are numbered and have an identifying prefix in the form DBnxxxxc:

Processing and DBUTLTY Messages

DB Product code indicating CA Datacom/DB

c Subsystem identifier as follows:

■ 0 - Processing message (Documented in CA Datacom/DB Processing Messages (DB0xxxxc) (see page 22).)

■ 1 - DBUTLTY message (Documented in DBUTLTY Messages (DB1xxxxc) (see page 326).)

■ 2 - SQL Precompiler message (Documented beginning on SQL Preprocessor Messages (DB2xxxxc).)

■ 9 - CA Datacom Transparency message (Documented beginning on CA Datacom/DB Messages for Invocation of CAIRIM (DB9xxxxc).)

H Subsystem identifier as follows:

■ H - Health Checker message (Documented in CA Datacom/DB Health Checker Messages (see page 531))

xxxx Numeric message identifier

c Message type indicator as follows is a general guideline because the line between the various types is often a matter of opinion. Once a message is documented with a given type, it is a risk to all users for the type to be changed to another.

■ A - Action

■ C - Critical

■ E - Error

■ I - Information

■ W - Warning

CA Datacom/DB Processing Messages (DB0xxxxc)


Message Prefix

If you have coded the MUF startup option MUFMSG, certain CA Datacom/DB messages (see MUFMSG in the CA Datacom/DB Database and System Administration Guide) are prefixed by one or more pieces of information in the format a:b:c:d identified as follows:

a JOBNAME

b SVC number

c MUFNAME

d CA Datacom/DB numbered message

The z/OS default prints all three prefixes. The z/VSE default does not print the SVC number prefix because the SVC number is meaningless in z/VSE.

Message Suffix

Allows the same choices but the suffix occurs after zero or more spaces after a message.


DB00010W

PROGRAM LOAD FAILURE FOR nnnnnnnn RC=rr

Reason:

An attempt was made to load phase nnnnnnnn, but the CDLOAD service failed with a return code of rr.

Action:

Determine the reason for the return code by referring to the appropriate IBM z/VSE messages and codes documentation.



DB00101I

STARTED JOB-jjjjjjjj NUMBER-nnnnn CXX=cxxname [SUBID=x] [SVC=yyy]

Reason:

Run unit number nnnnn of job jjjjjjjj The displayed job name is derived from the job card. CA Datacom/DB assigns the run unit number. A run unit starts when a task, which has no open User Requirements Tables, opens a User Requirements Table.

If the specified job is running under a Multi-User Facility, the SUBID and, in z/OS, then the SVC is identified if the SVC is used to communicate with MUF. If the SVC is not used then the SVC= and number are not printed.

If TARGET_MUFLIST= has been specified in the DBSYSID macro of the DBSIDPR module, MUFNAME=nnnnnnnn replaces the SUBID= in the message text. nnnnnnn is the particular MUFNAME to which this application connected.

Action:

None. This message is for information only.

DB00102I

ENDED JOB-jjjjjjjj NUMBER-nnnnn ttt-FROM=ssssssss

Reason:

Run unit nnnnn of job jjjjjjjj successfully completed CA Datacom/DB processing. The displayed job name is derived from the job card. The run unit number is assigned by CA Datacom/DB. (A run unit ends when a task, which has only one User Requirements Table open, closes that User Requirements Table. A new run unit starts if the task reopens the same or a different User Requirements Table.)

In z/OS, if the specified job was an application which used XCF to communicate with MUF, ttt will be XCF, and ssssssss is the name of the originating z/OS system. If the specified job was an application which used CAICCI to communicate with MUF, ttt will be CAICCI, and ssssssss will be the CAICCI name of the originating z/OS system.

The message occurs in the Multi-User Facility region for jobs which have done maintenance logged to the Log Area (LXX). The message may be useful in case backward recovery is required. For Multi-User Facility jobs that do not do maintenance to the Log Area, the message does not occur unless so specified in the MUF MUF startup option. The message does not occur during Single User, including DBUTLTY functions that run as Single User.

Action:




DB00103I

BACKOUT JOB-jjjjjjjj NUMBER-nnnnn [ID=monitor] [CP=chkpt] RC=rr TSN=xxxxxxxx

Reason:

Transaction backout for run unit number nnnnn of job name jjjjjjjj with a TSN (transaction sequence number) of xxxxxxxx was invoked by one of the following:

■ A ROLBK or LOGTB request

■ A monitor response to a user abend

■ CA Datacom/DB response to either a user abend or a termination with an open User Requirements Table

The return code (RC=rr) indicates the status. Look up the numeric value of the return code to identify the cause of the aborted transaction backout.

The ID field is displayed under the following circumstances:

■ Under CICS using the DBNTRY entry point, the format for the displayed monitor is ID=trantermoprxxxxx where tran is the transaction ID, term is the terminal ID, opr is the operator ID, and xxxxx is the task ID.

■ Under CA Datacom Server, the ID field contains the logical terminal name (a one- to eight-character field).

If the task issued a LOGCP command to checkpoint CA Datacom/DB processing, CP= displays eight bytes from the work area as passed by the task issuing the LOGCP.

Action:




DB00104I

CHKPT JOB-jjjjjjjj NUMBER-nnnnn TSN=xxxxxxxx

Reason:

A task, for which transaction backout is specified, is probably not issuing checkpoints frequently enough to permit the spills required to clear the Log Area. CA Datacom/DB forced an artificial checkpoint for this task, identified by run unit number nnnnn of job name jjjjjjjj with a TSN (transaction sequence number) of xxxxxxxx, so that the required spill could be accomplished.

Action:

Evaluate the program to determine whether it is issuing checkpoints as frequently as needed. If not, modify the program. If the program is issuing checkpoints at a reasonable rate, enlarge the Log Area as follows:

1. Stop the Multi-User Facility by using the EOJ option of the DBUTLTY COMM function or the related console command.

2. If using inactive recovery, execute the SPILL function to clean out the old Log Area.

3. Allocate and initialize the new Log Area with the INIT AREA=LXX function.

4. Execute DBMUFPR to initiate the Multi-User Facility with a new Log Area.

DB00105I

STAR ACTIVATED

Reason:

CA Datacom STAR has successfully started.

Action:




DB00106E

SEVER JOB-jjjjjjjj NUMBER-nnnnn a=ss-ttuu-vv mmmm RC-rr

Reason:

The MUF has detected an error processing a request using IUCV or CAICCI facilities. The error has forced the MUF to sever communication with the application. The jjjjjjjj specifies the job name and the nnnnn specifies the application from which communication is being severed. The communication mode, CAICCI or IUCV, is indicated by mmmm. RC indicates the return code for CAICCI or IUCV. The a= is information provided to assist in correcting the problem. See Communication Return Codes.

Action:

Based on information provided in the message, correct the error and resubmit the job.

DB00107E

UNKNOWN TARGET TARGET-xxxxxxxx SOURCE-yyyyyyyy,zzzzzzzz FUNCTION-ff

Reason:

The CA Datacom/DB IUCV interrupt handler has received a message but the target VM application is not recognized by the interrupt handler as an active application. TARGET is the application to which the message is being sent. Source is the VM guest machine ID (yyyyyyyy) and application (zzzzzzzz) from which the message came. FUNCTION is the CA-IUCV function that is being requested (see Communication Return Codes).

Action:

This message indicates a probable system error. Collect console logs for the machines involved and contact CA Support. For information about contacting CA Support, see Troubleshooting.

DB00108E

SYSTEM FUNCTION ERROR FUNC-xxxxxxxx RC-rr (text)

Reason:

An error has been detected processing an IBM System Function. FUNC is the function being executed. RC-rr is the return code received from the function call. An additional short textual description of the meaning of the return code (text) is also provided.

Action:

For more information about return codes, see the IBM System Macro Reference. Make appropriate correction and rerun the job if possible. If the return code indicates an error that cannot be corrected by redefining the system, contact CA Support. For information about contacting CA Support, see Troubleshooting.



DB00109W

BACKOUT JOB jjjjjjjj NUMBER-nnnnn TSN-xxxxxxxx WAITING TO COMPLETE

Reason:

Using the MUF startup option RXXROLLBACK YES, this message is displayed on the console to indicate that the rollback has encountered a forced spill. JOB and NUMBER specify the name and number of job and TSN is the transaction sequence number that needs to be backward recovered.

Action:

If the RXXROLLBACK MUF startup option was directly or indirectly specified as YES, to prevent the MUF task from remaining in a WAIT E/C DBSTXB you must do one of the following:

■ Perform a REQABORT to cause a force-checkpoint condition to occur with the transaction not at a stable state.

■ Wait upon the spill and perform backward recovery for the transaction. The completion of the backward recovery posts the waiting rollback.

Note: The DB00109W message must always be manually deleted by an operator after they have dealt with the required situation.



DB00110W

FORCED SPILL JOB-jjjjjjjj NUMBER-nnnnn

Reason:

All the log data recorded for this transaction cannot be contained in the Log Area. This occurs when the Log Area reaches 100 percent full (or a lower percent when the MUF startup option LOGSPILL is specified with a 'b' option of less than 100) and log records for an active transaction exist in the oldest Log Area block. The transaction reflected by the job name and run unit number has log blocks spilled and is not available for direct transaction backout access.

This condition is best avoided, when possible, by allocating a larger Log Area or by having the job in question issue interim commits.

This message does not indicate a problem, it is informational. If the transaction being forced to spill were to later fail for any reason and be subject to transaction backout (rollback), then transaction backout would reverse any of the transaction work still on the Log Area. At that time, the actions taken are based upon the MUF startup option RXXROLLBACK.

When RXXROLLBACK is set to NO, the backout stops and issues the DB00103I message indicating completion of the backout. When a return code (RC) of 94(085) is received, it indicates that the backout of the transaction did not complete and the status of the database is now inconsistent relative to the transaction. Some manual effort should be attempted to correct the partial rollback.

When RXXROLLBACK is set to YES, when transaction backout completes backing out the data on the Log Area to a forced checkpoint, it presents the DB00109W message. This message indicates the backout job is waiting to complete.

Action:

Evaluate the program to determine whether it is issuing checkpoints as frequently as needed. If not, modify the program. If the program is issuing checkpoints at a reasonable rate, enlarge the Log Area as follows:

1. Stop the Multi-User Facility by using the EOJ option of the DBUTLTY COMM function or the related console command.

2. If using inactive recovery, execute the SPILL function to clean out the old Log Area.

3. Allocate and initialize the new Log Area with the INIT AREA=LXX function.

4. Execute DBMUFPR to initiate the Multi-User Facility with a new Log Area.



DB00111I

CCISYS=CAICCI system name SYSTEM=MVS system name

Reason:

This message displays after the DB00101I started message if the DBSIDPR module indicates access to Multi-User Facility is through CAICCI. The system names represent the system names of the originating system of the job as known to CAICCI and z/OS.

Action:


DB00112I

BACKOUT JOB-jjjjjjjj NUMBER-nnnnn [ID=monitor] [CP=chkpt] RC=N

Reason:

Transaction backout for run unit number nnnnn of job name jjjjjjjj was invoked by one of the following:




The return code (RC=N) indicates that transaction backout completed successfully, but found no data to back out.

Note: Message DB00112I defaults to be suppressed to reduce console clutter, but it can be set to print if desired using the MESSAGE MUF startup option.


■ Under CICS using the DBNTRY entry point, the format for the displayed monitor is ID=.trantermoprxxxxx where tran is the transaction ID, term is the terminal ID, opr is the operator ID, and xxxxx is the task ID.



Action:




DB00113I

BACKOUT JOB-jjjjjjjj NUMBER-nnnnn [ID=monitor] [CP=chkpt] RC=Y TSN=xxxxxxxx

Reason:

Transaction backout for run unit number nnnnn of job name jjjjjjjj with a TSN (transaction sequence number) of xxxxxxxx was invoked by one of the following:




Note: Message DB00113 can be suppressed by users to reduce console clutter, if desired.


■ Under CICS using the DBNTRY entry point, the format for the displayed monitor is ID=trantermoprxxxxx where tran is the transaction ID, term is the terminal ID, opr is the operator ID, and xxxxx is the task ID.



The return code (RC=Y) indicates that transaction backout completed successfully after backing out one or more maintenance transactions.

Action:


DB00114I

FORCED SCAN JOB-jjjjjjjj NUMBER-nnnnn [ID-monitor] TSN-xxxxxxxx

Reason:

The last maintenance command for a transaction is aging in the Log Area (LXX). It has reached the percent of log full to move the transaction information from the Log Area to the Force Area (FXX). CA Datacom/DB forced a scan job for this task, identified by run unit number nnnnn of job name jjjjjjjj with a TSN (transaction sequence number) of xxxxxxxx.

Note: Most transactions are short and are not normally forced. However, longer running transactions (or when running with a small Log Area) can be forced.

Action:




DB00115I

FORCED REDO JOB-jjjjjjjj NUMBER-nnnnn (ID-monitor) TSN-xxxxxxxx

Reason:

An active maintenance command aging in the Log Area (LXX) has reached the percent of log full to move the request information from the Log Area to the Force Area (FXX). That is, a maintenance command is running a long time, and the reason can be investigated, if desired. CA Datacom/DB forced a redo job for this task, identified by run unit number nnnnn of job name jjjjjjjj with a TSN (transaction sequence number) of xxxxxxxx.

Action:


DB00116I

CLOSE JOB-jjjjjjjj NUMBER-nnnnn tttaaa FOR pppnnnn POSSIBLE INCOMPLETE DATA

Reason:

This message is generated when a User Requirements Table is closed that included table ttt in area aaa which was opened using the ANY partitioning Parent ppp in DBID nnnn. At some time during the life of this User Requirements Table, area aaa was either ACCESS OFF or ACCESS READ with the table opened for update. The jjjjjjjj specifies the job name and the nnnnn is the run unit number.

Action:


DB00117I

CLOSE JOB-jjjjjjjj NUMBER-nnnnn ANY PARENT POSSIBLE INCOMPLETE DATA

Reason:

This message is generated when all User Requirements Tables currently opened by job jjjjjjjj are being closed. During the life of this run unit (indicated by nnnnn in the message text) there was at least one open of a Any Parent partitioned table, and a Child table's area within this Any Parent table was either ACCESS OFF, ACCESS UTLTY, or ACCESS READ with the table opened for update.

Note: When CA Datacom STAR is being used, STAR NUMBER.....n appears at the end of the message text, where n is the remote run unit or user job number.

Action:




DB00118I

XCF TOGROUP=name SYSTEM=system name

Reason:

This message is generated when a batch job connects to a Multi-User Facility using XCF. In the message text, the TOGROUP=name gives the group name, as specified in the DBSIDPR module. SYSTEM= gives the z/OS name of the system on which the MUF resides. The SYSTEM name can be blanks if it is not known at the time the message is printed

Action:


DB00119E

INSUFFICIENT MEMORY AVAILABLE

Reason:

RRM could not obtain memory that it needs for its processing.

Action:

Recycle RRM and provide it with a larger region.

DB00120I

MISSING JOB-job-name NUMBER-number

Reason:

(z/OS only) The Multi-User Facility (MUF) has detected the user address space JOB, identified in the message by JOB-job-name NUMBER-number, is no longer present and executing. If the task is currently executing a request, it is allowed to complete. After it completes, or immediately if no request is active, a rollback is generated on behalf of the task and executed, followed by a close command.

Action:




DB00121I

UNAVAILABLE - target_muf_list

Reason:

This message tells you that a list of MUFs are unavailable. In the message text, target_muf_list represents the list of target mufs targetmuf1...,targetmufn (where n can have a value of up to seven) as specified in the DBSYSID macro TARGET_MUF_LIST= parameter (see the CA Datacom/DB Database and System Administration Guide).

This message appears when either one or both of the DBSYSID macro parameters DELAY68= or DELAY85= have been specified with non-zero values, a return code 68 or 85 has occurred, and none of the MUFs specified in the TARGET_MUF_LIST= parameter are available.

Action:


DB00122I

ACCESS TYPE access1,access2,access3 TASKS=nnn

Reason:

In the text of the message, access1,access2,access3 are based on types specified in the DBSYSID macro (for example, LOCAL, XCF, and CAICCI). Also in the message text, TASKS=nnn is the number of task areas requested by the application.

This message appears with DB00121I and indicates the attempted access methods (based on DBSYSID). The sequence in which the access types appear corresponds to the sequence specified by CONNECT_ALLOW_PRIORITY in the DBSYSID macro. The specification for XCF is XCF(gggggggg), where gggggggg is specified by the DBSYSID parameter, TOGROUP. The specification for CAICCI is CAICCI(ssssssss), where ssssssss is specified by the DBSYSID parameter, CCISYS.

Action:




DB00123I

WAITING FOR MUF AVAILABILITY

Reason:

The system is waiting for Multi-User Facility (MUF) availability. This also appears with DB00121 and DB00122 as information

Action:


DB00124W

REMAINING DELAYnn TIME - nnn MINUTES

Reason:

In the message text, DELAYnn can be either DELAY68 or DELAY85. The message indicates that the remaining time that was specified with one or both of the DBSYSID macro parameters DELAY68= or DELAY85= is nnn minutes.

This message can appear periodically to indicate how much of the original time specified by DELAY68= or DELAY85= remains.

Action:

The expected action is to start one of the MUFs specified in the TARGET_MUF_LIST= parameter.



DB00126I

ROLLBACK S xxxxxxxx nnnnn xxxxxxxx L-n IO-n identifier

Reason:

This message is generated at the beginning of a rollback with enough log records to be defined as a long transaction. For a definition of a long transaction, see the information about the MUF startup option LOG_ROLLBACK_RECORDS in the CA Datacom/DB Database and System Administration Guide.

In the message text, the S following ROLLBACK indicates this message was generated by the start of the rollback.

Regarding the next three variables in the message text, the first xxxxxxxx is the job name, the nnnnn is the run unit number, and the second xxxxxxxx is the Transaction Sequence Number (TSN).

In the message text next, the n in L-n is a number indicating a count of total log records written by the transaction.

The n in IO-n is the count of I/Os this task has generated up to the point when the message was generated.

The identifier at the end of the message text occurs when there are transactions that executed through controlled APIs such as CA Datacom CICS Services.

This message is not generated for a transaction that has been force check-pointed.

Action:




DB00127I

ROLLBACK C xxxxxxxx nnnnn xxxxxxxx L-n IO-n identifier

Reason:

This message is generated during the continuation of a long transaction. For a definition of a long transaction, see the information about the MUF startup option LOG_ROLLBACK_RECORDS in the CA Datacom/DB Database and System Administration Guide. For information about the frequency of this message, see the information about the MUF startup option LOG_ROLLBACK_MINUTES in the CA Datacom/DB Database and System Administration Guide.

In the message text, the C following ROLLBACK indicates this message was generated during the continuation of a rollback. The message only occurs during the transition from one log record to another, with the result that it can occur either at the time or later.

Regarding the next three variables in the message text, the first xxxxxxxx is the job name, the nnnnn is the run unit number, and the seco

Documents

ftpdocs.broadcom.com Datacom 14... · CA Technologies Product References This document references the following CA products: CA Datacom®/DB CA Datacom® CICS Services A Datacom®