Updates that apply to DB2 Log Analysis Tool V3.3 User's Guide (SC19-3492-00)
The most recent update is listed first.
Date of change: May 1, 2012
Topic: Multiple topics
Change description: Multiple changes
Page 23: Documentation change--Upgrading versions of DB2, paragraph 1
The reference to DB2VER(10.1) in the last sentence should be changed to DB2VER(101).
Also, there is a note after the first paragraph:
Important: The DB2VER bind parameter values are changed in version 3.3 so that they no longer have decimal points: 8.1 is now 810, 9.1 is now 910, and 10.1 is now 101.
Page 190: New report: IDMAP Report
The IDMAP Report is used primarily for support purposes, providing information about each of the tables in the General Report. When requesting technical support and supplying the IDMAP report with the JOBLOG, you help Customer Support to make better decisions on the remaining documentation needs.
Important: This report will not print if you remove the INFOM DD from the JCL.
Sample IDMAP Report
DB2 LOG ANALYSIS- IDMAP REPORT: SS1A
START DATE : 2012/04/05
START TIME : 11:57:00
END DATE : 2012/04/05
END TIME : 11:57:59
SHOW UPDATES : Y
SHOW INSERTS : Y
SHOW DELETES : Y
SHOW ROLLBACKS : N
CATALOG DATA : N
MISC WITH 'OR ':
DBNAME TSNAME: SWMDB01S.TSSWM002
DBID PSID PARTS PGSZ SGSZ TYPE DSSZ XML
------ ----- ----- ---- ---- ----- ---- ---
0x10c 0x18 0 4k 16k BASIC 0G NO
OWNER TABLE NAME: PDUSER.D310_TV_BIGINT
OBID PART TP EDITPROC FLD CSSID VERS CUR CREATED RBA/LRSN DCC LF
----- ---- -- -------- --- ------ ---- --- ---------------- --- ---
0x19 0 T NO EBCDIC NO 0 0x79e1738142 OFF OFF
Page 196: General report files: New documentation about the INFOM DD:
DD INFOM--This DD identifies the file that holds the informational messages that are useful in resolving most problems during job execution. Informational messages are sent to this file when you have specified Y for ‘Send informational messages to file’ on the User settings panel. Additionally, when this DD is in the JCL, the IDMAP report is generated which is useful in support situations. If you remove this DD from the JCL, the report will not print. See ‘IDMAP Report’ in ‘DB2 Log Analysis Tool reports’ chapter.
Page 238: Changed message ALAA156I
ALAA156I: Processing_information Compile_date Compile_time
Explanation: These informational messages are emitted as Log Analysis Tool is processing. They are intended to assist Customer Support in diagnosing product-related issues.
User response: None required.
Page 265: New messages:
ALAA575E: PDS directory update failed for member: membername RC: rc Res: reason
Explanation: The directory update for named member failed while using the STOW macro. The return code and reason code are listed in hexadecimal. Return code 12 and Reason Code 0 mean the directory blocks need to be increased for the LOB PDS being used.
User response: Check the return code and reason code included in the message in the IBM document "DFSMS Macro Instructions For Datasets" in the chapter "Non-VSAM Macro Descriptions" for explanations of STOW completion codes.
ALAA576E: Dyn Alloc Err: DDNAME: ddname, Ret: returncode, Res: reasoncode, More info: text
Explanation: Dynamic allocation attempt failed for the specified ddname. The return code and reason codes are SVC 99 standard codes and can be found in the IBM manual "Authorized Assembler Services Guide" in the chapter "Requesting Dynamic Allocation Functions". The most common codes likely to be encountered are:
021c - device name is undefined, check unit parameter
9700/970c - primary allocation amount cannot be fulfilled
User response: Check the parameters in the TICSPECS DD, correct any problems, and retry. If that does not solve the problem, contact the vendor.
ALAA577E: Invalid value found in TICSPECS DD for device type
Explanation: The TICSPECS DD has an invalid value for device type. The valid values are:
Correct the value in the TICSPECS DD and rerun.
Page 268: New message:
ALAA619E: Invalid DB2 version format
Explanation: An invalid DB2 version format was specified for the DB2VER field while attempting to bind the SQL for the Log Analysis Tool.
User response: Enter the DB2 version in the correct format and run the bind again.