The following is an example of the output produced by the SQL Object Consistency Analyzer. If the summary for each entity-type indicates that all entities were found intact, then your task is complete. Otherwise, use the information printed in the report to correct the problem as described in Correcting Problems. In the following report, note that the name and type of the SQL object involved is printed for each problem found, as well as a specific statement or statements indicating which pieces of that entity-type are missing:
For a sample header for this report, see Sample Report Headers.
ECHO PRINT OF PARMS: WINDIGO.*. RESULTS OF CONSTRAINT CONSISTENCY CHECKING: ERRORS FOUND IN TABLE WINDIGO.ORDR CONSTRAINT MIN_PMT AS FOLLOWS: CONSTRAINT IS MISSING FROM DATADICTIONARY. CONSTRAINTS DEFINED ON THE FOLLOWING DATABASES WILL NOT REBIND DUE TO DD STRUCTURE VERIFY ERRORS: DB ID DB NAME DD ERROR/MODULE DESCRIPTION ----- -------------------------------- --------------- -------------------------------- 481 TEST-DATABASE SV4 / STRUCTURE VERIFY ERROR NOTE: DD STRUCTURE VERIFY ERRORS NOT INCLUDED IN NUMBERS REPORTED IN FOLLOWING TOTAL CONSTRAINTS PROCESSED: 118 VALID CONSTRAINTS: 117 INVALID CONSTRAINTS: 1 --------------------------------- RESULTS OF PLAN CONSISTENCY CHECKING: ERRORS WERE FOUND IN PLAN WINDIGO.XYZ AS FOLLOWS: PLAN IS MISSING FROM DD TABLE PLN. STATEMENT(S) ARE MISSING FROM TABLES DDD AND/OR STM. TOTAL PLANS PROCESSED: 281 VALID PLANS: 280 INVALID PLANS: 1 --------------------------- RESULTS OF VIEW CONSISTENCY CHECKING: ALL VIEWS WERE FOUND INTACT. TOTAL VIEWS PROCESSED: 17 VALID VIEWS FOUND: 17 INVALID VIEWS FOUND: 0 ---------------------------
You could also receive error messages indicating problems that prevented DBSOCPR from running normally. Most of the messages are self explanatory and include instructions for correcting the problem. Following are messages that may be more difficult to interpret:
DB RETURN CODE xx(yyy DEC) PRODUCED BY zzzzz COMMAND. CONSISTENCY CHECKING IS BEING ABORTED.
If you receive this message, xx is the CA Datacom/DB external return code, yyy is the internal return code in decimal, and zzzzz is the record-at-a-time command that produced the error. Look up the return code in the CA Datacom/DB Message Reference Guide, correct the problem as described in that manual, and retry the SQL Object Consistency Analyzer.
DD USRINITI FAILED. RC=return-code, ERROR=dd-error-message,USER=uid,password PLEASE SPECIFY OR CHECK THE UID AND PSW PARAMETERS.
If you receive this message, first follow the printed suggestion to check your UID and PSW parameters for correctness (see the PARM= documentation on the preceding pages). If no problem is found, check for a message in the job output (JES LOG for z/OS) indicating that a requested module was not found. If no problem is found here, contact CA Support for a support person to look at your RC, ERROR, and USER information printed in the error message to determine what the problem is. Only contact CA Support if the first two steps were unproductive.
|
Copyright © 2014 CA.
All rights reserved.
|
|