How to identify when a utility has executed when utilizing Database Management for Db2 for z/OS utilities
search cancel

How to identify when a utility has executed when utilizing Database Management for Db2 for z/OS utilities

book

Article ID: 20949

calendar_today

Updated On:

Products

Database Management for DB2 for z/OS - Utilities Suite Fast Load for DB2 for z/OS Fast Unload for DB2 for z/OS Quick Copy for DB2 for z/OS Fast Recover for DB2 for z/OS Rapid Reorg for DB2 for z/OS

Issue/Introduction

How to identify tables against which Fast Load for DB2 for z/OS has been used.
Although Fast Load makes a SYSCOPY entry for a load, it's not distinguishable from an entry made
by IBM Load, and since both Fast Load and IBM Load are used, that is not very useful.

 

Environment

Release: R19, R20
Component: PUT

Resolution

Database Management for Db2 for z/OS utilities are able to write log records to this table each time they execute.

PTI.PTGL500_HISTORY

If the the history parm in hlq.CDBAPARM(UTIL) member is set to YES.

HISTORY (YES) /* CREATE HISTORY TABLE ROWS (NO/YES)

Online help for this field:

Field:  Create History Table Rows

Description:  Indicate whether to create history table rows containing utility history information. (HISTORY)

YES  Create utility history table rows containing utility history information.

NO  (Default) Do not create history table rows.

Then each time a utility like Fast Load, Fast Unload, Rapid Reorg, Quick Copy, Fast Recover and others executes a log record is written such as this one:

 

RUBROWF  20.0   ---------- RC/Browse: Form Mode ---------- yyyy/mm/dd hh:mm:ss
COMMAND ===>                                                  SCROLL ===> CSR

For Table   => PTI.PTGL500_HISTORY           >   Row number=> 1 OF 10386
Browse Mode => F                                 Max Char  => 256
SSID: DT32 ----------FETCH STATUS: COMPLETE-------------------------- authid
##.COLUMN NAME        NULL  DATA FOR ROW # 1
A1.PUT_JOBNAME              PFLJOBB
A2.PUT_JOBID                JOB53131
A3.PUT_USER                 <authid >
A4.PUT_STEPNAME             <PFL     >
A5.PUT_SYSID                ssid
A6.PUT_UTIL                 LOAD
A7.PUT_CREATOR              creator
A8.PUT_DBNAME               dbname
A9.PUT_TSNAME               tsname
B1.PUT_TBNAME               tablename
B2.PUT_IXNAME
B3.PUT_PARTNUM              0
B4.PUT_DB2_LVL              1210
B5.PUT_SMFID                ssid
B6.PUT_START_DATETIME       yyyy-mm-dd-hh.mm.ss.msmsms
B7.PUT_END_DATETIME         yyyy-mm-dd-hh.mm.ss.msmsms
B8.PUT_ELAPSED_TIME         1.4
B9.PUT_CPU_TIME             4.74
C1.PUT_ELAPSED_WIND         0.0
C2.PUT_CPU_WIND             0.0
C3.PUT_AVG_CPU_BUSY         0.0
C4.PUT_RC                   0
C5.PUT_EXCP                 0
C6.PUT_UTIL_ID              <authid          >
C7.PUT_UTIL_SOURCE          PFL
C8.PUT_UTIL_VERSION         200
C9.PUT_HASH                 ................................
D1.PUT_CMD_TEXT             FASTLOAD.ENABLE-PFL20 YES.OUTPUT-CONTROL BUILD.SE>

 

Any utility jobs will display a message like this one:

PUT0050I - History LOG Record created - UTILITY ID: authid.authidA

As can be seen from the above log record it does record a extensive information regarding the utility execution.
You can look up the table to obtain the information you need.