06.01.2013 Views

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

After starting each audit policy, DB2 generates specific trace records (IFCIDs) specified for<br />

the category of the audit policy. Each audit policy can be marked for automatic start during<br />

DB2 subsystem startup. You set the DB2START column as Y. Then this audit policy is<br />

activated automatically during the next initialization of the DB2 instance. A DB2 subsystem<br />

can activate up to eight policies during the DB2 startup phase.<br />

Additional information: For information about categories and trace records that are<br />

collected during a DB2 trace, see the DB2 10 for z/OS Administration Guide, SC19-2968.<br />

8.2.2 Collecting and formatting audit reports<br />

All trace records during the audit are collected by using the System Management Facility<br />

(SMF) or Generalized Trace Facility (GTF). Before you activate an audit policy, prepare those<br />

system components to accept DB2 audit trace records. If auditing is going to be activated for<br />

a long time, it is preferable to use SMF to collect the necessary trace data.<br />

To collect audit data, we customized and used GTF. GTF is a base system component of the<br />

z/OS operating system and provides service aid for recording and diagnosis of system and<br />

product problems.<br />

Initialization of GTF is done in internal tracking mode where data is maintained in virtual<br />

storage and is not recorded on any external device. After GTF is stopped, all collected data<br />

can be written to a special data set that is used to create reports. Example 8-5 shows the job<br />

control language (JCL) for the started procedure, GTF.<br />

Example 8-5 JCL for GTF<br />

//GTFDB2 PROC MEMBER=GTFDB2<br />

//IEFPROC EXEC PGM=AHLGTF,PARM='MODE=EXT,DEBUG=NO,TIME=YES',<br />

// TIME=1440,REGION=2880K<br />

//IEFRDER DD DSNAME=MAXIM.GTFDB2.&SYSNAME..D&YYMMDD..T&HHMMSS,<br />

//* DISP=OLD,DCB=NCP=255<br />

// DISP=(,CATLG),SPACE=(CYL,100,RLSE),UNIT=SYSDA<br />

//SYSLIB DD DSNAME=SYS1.PARMLIB(&MEMBER),DISP=SHR<br />

Example 8-6 shows the starting process of GTF in the z/OS system log (syslog).<br />

Example 8-6 Starting process of the GTF<br />

S GTFDB2.GTFDB2<br />

IRR812I PROFILE ** (G) IN THE STARTED CLASS WAS USED 994<br />

TO START GTFDB2 WITH JOBNAME GTFDB2.<br />

$HASP100 GTFDB2 ON STCINRDR<br />

IRR812I PROFILE ** (G) IN THE STARTED CLASS WAS USED 996<br />

TO START GTFDB2 WITH JOBNAME GTFDB2.<br />

IEF695I START GTFDB2 WITH JOBNAME GTFDB2 IS ASSIGNED TO USER STC<br />

, GROUP SYS1<br />

$HASP373 GTFDB2 STARTED<br />

AHL121I TRACE OPTION INPUT INDICATED FROM MEMBER GTFDB2 OF PDS<br />

SYS1.PARMLIB<br />

TRACE=USRP<br />

USR=(FB9)<br />

AHL103I TRACE OPTIONS SELECTED --USR=(FB9)<br />

023 AHL125A RESPECIFY TRACE OPTIONS OR REPLY U<br />

R 023,U<br />

120 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!