A long running Log Analyzer for Db2 for z/OS (PLA) extract which usually completes within minutes is being cancelled with a timeout and Abend S322
SURF920I STEP START: JOB=xxxxxxxx STEP=xxxxxxx PGM=PTLDRIVM STEP#=004
BPA0080I: BATCH PROCESSOR EXECUTION: DATE=yyyy/mm/dd TIME=hh:mm.ss.s.ss
IDI0002I Module LAL@LOG, CSECT LAA@LOG, offset X'D6C': Abend S322
IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION REQU
WER999A xxxxxxxx,xxxxxxx, - UNSUCCESSFUL SORT 322 S (
IEF450I xxxxxxxx xxxxxxx - ABEND=S322 U0000 REASON=00000000 615
TIME=hh:mm:ss
SURF931I STEP ENDED: JOB=xxxxxxxx STEP=xxxxxx CC=S0322
DB2 for Z/OS
A possible peak of catalog activity could be caused by scheduled utilities executions like runstats for many objects updating many catalog tables. Typically updates of the statistics are not important for reports but still add up for catalog updates.
The workload of an extract differs greatly when including or excluding catalog objects from the extract.
With the catalog tables excluded, tests showed significantly less workload than when the catalog objects are included.
Recommendation is to monitor the volume of activity of the catalog tables. DML Summary or Totals reports are designed for such a purpose. A possible peak of catalog activity could be caused by scheduled utilities executions like runstats for many objects updating many catalog tables.
In this event consider excluding the catalog tables involved in it from further Log Analyzer reports.
Typically updates of the statistics are not important for reports but still add up for catalog updates.
Instead of the following specified in the DMLREPT control cards:
,CATALOG (INCLUDE)
Specify :
,CATALOG (EXCLUDE)
CATALOG (INCLUDE|EXCLUDE)
Specifies whether updates to the Db2 catalog are included in the analysis.
INCLUDE
Includes catalog updates.
EXCLUDE
Excludes catalog updates.