|
|
|
SMF MAN file dump processing can be initiated in the following ways using CA SMF Director:
To allow CA SMF Director to automatically dump a full or switched SMF data set, add the CAIRIM control statement provided in the CASFPARM data set member CASFRIMP to the CARIMPRM member used by the CAS9 procedure that executes CAIRIM. CAIRIM dynamically installs a module that receives control in a similar way to the SMF exit IEFU29. To deactivate this facility, modify the CAIRIM control statement by changing the "ENABLE" keyword to DISABLE and rerunning the CAS9 procedure.
See the Installation Guide for more details on CAIRIM and CA LMP.
If you want a procedure name other than CASFDUMP or you want to change the command issued to initiate the SMF MAN file dump process, you can do this with a user exit. A sample user exit, SMFIDTBL, is provided in the CASFSRC library and can be used as a guide for altering the command that is issued by the CA SMF Director MAN file switch process. The exit should be assembled and linked as a separate load module and placed in the system link list (see SMFIDTBL sample JCL in CASFJCL). The exit can have any valid load module name.
The user exit for automated SMF MAN file dump processing is called with the following registers:
Calling Save Area. The calling registers must be saved here and restored when the exit program returns to the caller, with the exceptions noted below.
The return address to branch to when returning.
Note: The addressing mode (AMODE) is not set in the register. The return should be made with a BR R14 instruction.
The entry address of your exit.
A parameter list with the following parameters:
Address of the name of the SMF MAN file to be dumped.
Address of the start command to be Issued.
Address of a 512 byte work area provided to your exit.
The exit may modify the start command to be issued to initiate the dump process, and perform other processing as needed.
Upon return from the exit, registers 0 through 14 should be returned with the same values they had upon entry. Register 15 should be set to the return code from the exit that will indicate what action the automated dumping process is to take:
Issue the start command.
Do not issue the start command.
The automated MAN file dumping exit program includes a prefix that contains the command that is to be issued when dumping as well as a list of pointers to the command and to the actual exit code. To see the layout of this prefix, consult the SMFIDTBL sample in your CA SMF Director samples library.
The exit can be assembled and linked with the SMFIDTBL sample JCL provided in the JCL samples library.
Once you have coded your exit and linked it, you must make it available to CA SMF Director. To do this, change the CAIRIM parameter in CASFRIMP to read “ENABLE,MX=(exitname)” where exitname is the name of the load module for your exit. This will tell the intercept to invoke your exit before issuing the command to start the dump process.
Once CA SMF Director is invoked to perform dump processing, SMFD does the following:
CA SMF Director verifies the SMF Record Header section according to the definition in the IBM z/OS System Management Facilities manual. This product requries that all SMF records adhere to the published standard. Other applications or program products may write SMF records that do not conform to this standard. When detected by this product, these records may be rejected by the SMFD program or cause unpredictable results.
The following illustrates the audit trail from DUMP Processing.
CA AUDIT TRAIL REPORT SMFD PAGE 1 CA SMF Director r12 SPn SYSA 10 JUL yyyy 10:36:24 CAF2207I SMF DATA WILL BE DUMPED FROM MVSXE44.SF16.MAN1 ON VOLUME MVXE44 CAF2218I SMF DATA USING CONFIGURATION XE44 IS BEING PROCESSED CAF2401I PRIMARY DUMP IS TO TAPE VOLUME: 107652 FILE:1 DSN: SYS3.SMFDATA.P1071098.T1036115 CAF2406I XE44 SMF DATA WAS FROM 04/16/yyyy AT 13:15:00 TO 04/16/yyyy AT 13:29:59 CAF2406I ALL SMF DATA WAS FROM 04/16/yyyy AT 13:15:00 TO 04/16/yyyy AT 13:29:59 CAF3300I MVSXE44.SF16.MAN1 HAS BEEN RESET CAF2204I DUMP COMPLETE, 8778 RECORDS COPIED CAF2900I RUN COMPLETE
CA AUDIT TRAIL REPORT SMFD PAGE 2 CA SMF Director r12 SPn SYSA 10 JUL yyyy 10:36:27 SUMMARY OF RECORDS COPIED TYPE AVGL MAXL TOTAL ................................ SUBTYPE COUNTS ................................ 17 100 100 14 18 144 144 8 21 72 72 4 32 230 236 2 1 - 2 41 172 172 1 42 198 212 6 2 - 6 62 176 176 14 99 188 246 5,146 3 - 440 4 - 704 5 - 4,002 100 230 230 1 118 128 128 15 118 - 15 128 163 163 129 187 111 177 123 248 156 156 2 252 87 87 5 254 162 196 3,284 54465 - 179 54467 - 3,105 255 182 204 24 1 - 15 7 - 8 8 - 1 ALL 176 246 8,778
CA SMF Director automatically determines which SMF data set should be dumped. If you want the SMF data to be dumped automatically when a data set is switched or becomes full, we recommend that the CASFDUMP procedure not reference the SYSx.MANx files. This product examines the z/OS control blocks and dynamically allocates the SMF data sets defined. This involves the procedure not having any 4-character DDname beginning with MAN as the first three characters.
If there is a need to point to another set of SMF data sets, they should be specified as follows in the CASFDUMP procedure:
//MANx DD DISP=SHR,DSN=SYS1.MANx
where:
x represents any character A-Z, or 0-9. When scheduling a job to invoke the CASFDUMP procedure to dump the SMF data, the currently active SMF data set must be switched before the SMF data can be unloaded (see the z/OS SWITCH SMF command).
Here is a sample of the provided CASFDUMP procedure:
//CASFDUMP PROC A='*', /* SYSOUT Class // SCDDSN='CAI.CASMF.SCDS', /* SCDS File // STEPLIB='CASFLOAD', /* Load Library // PRIUNIT=TAPE, /* Primary Pool Device // ALTUNIT=TAPE, /* Alternate Pool Device // PRIDS='VOL=PRIVATE', /* Dummy/Use Primary //* CTLLIB=CASFMAC, /* Control Statement Library //* DPCTL=SMFDDUMP, /* Dump Process Ctl Statements // ALTDS=DUMMY /* Dummy/Use Alternate //******************************************************************** //* PROCEDURE: CASFDUMP //* DESCRIPTION: CA-SMF Director utility procedure to unload the //* z/OS system SMF files (SYSx.MANy), allowing the //* CA-SMF Director Utility to manage SMF data storage //* and extraction. //* REFERENCE: DSN=CASFPROC(CASFDUMP) //* NOTES: //* (1) Optionally, you may specify the names of the SMF data sets //* to be dumped and cleared as shown below. We do not //* recommend this, however. Instead, we recommend that the //* CA-SMF Director utility be allowed to dynamically allocate //* the SMF data sets defined to your system. //* //* (2) If the DYNAM customization option and dumping to tape is //* used, comment out the HISTORY1 and HISTORY2 DD statements //* below, as well as the PRIDS, ALTDS, PRIUNIT, and ALTUNIT //* symbolic parameters above. //* If the DYNAM customization option and dumping to DASD is //* used, specify SPACE parameters in HISTORY1 and HISTORY2 DD //* statements. //* //* (3) If the primary pool is to be used for SMF history files with //* the NODYNAM customization option, specify: //* PRIDS='VOL=PRIVATE'. //* //* (4) If duplexing of the primary pool is desired and the NODYNAM //* customization option is used, specify: //* ALTDS='VOL=PRIVATE'. //* //* (5) If you employ tape history files, uncomment the first UNIT //* parameter for each history DD (i.e., the one with the //* DEFER option). //* //* (6) If you employ DASD history files, uncomment the second UNIT //* parameter for each history DD (i.e., the one without the //* DEFER option). You will also need to add a space parameter //* to the DASD History files. //* //* (7) If you need to have more control statements during the dump //* process, such as if you are writing to Split Files, then //* comment the DUMP1 EXEC statement that has PARM=DUMP coded //* and uncomment the DUMP2 EXEC statement. Also see note (8) //* below for further changes that need to be made to this //* procedure to indicate the location of the control statements. //* //* (8) The SYSIN DD is required if the PARM=DUMP is not coded on //* the EXEC statement. If you choose to create Split Files, //* for example, you will need to put all of the control //* statements into the dataset indicated in the DD. You will //* need to change the parameters on the PROC statement above to //* point to the control statement library and member within the //* library that contain the control statements. If a //* sequential dataset is prefered to a library, change the //* DSN and remove the member name reference. //* //* (9) For further details regarding customization options, please //* refer to the CA SMF Director User Guide and Systems //* Programmer Guide. //* //*(10) After you have modified it, you may copy this procedure to a //* PROCLIB of your choice, or you may use it instream. //* Alternatively, you may add the CAI common procedure library //* to the system PROCLIB concatenations. //******************************************************************* //* //DUMP1 EXEC PGM=SMFD,REGION=0M,PARM=DUMP <<- See Note 7. //*DUMP2 EXEC PGM=SMFD,REGION=0M <<- See Note 7. //STEPLIB DD DISP=SHR,DSN=&STEPLIB. //SYSPRINT DD SYSOUT=&A. //SYSXDIAG DD SYSOUT=&A. //SYSOUT DD SYSOUT=&A. //SCDS DD DISP=SHR,DSN=&SCDDSN. //HISTORY1 DD &PRIDS.,DISP=(,KEEP), <<- See Notes 2 and 3. // UNIT=(&PRIUNIT.,,DEFER) <<- See Note 5. //* UNIT=&PRIUNIT. <<- See Note 6. //HISTORY2 DD &ALTDS.,DISP=(,KEEP), <<- See Notes 2 and 4. // UNIT=(&ALTUNIT.,,DEFER) <<- See Note 5. //* UNIT=&ALTUNIT. <<- See Note 6. //*SYSIN DD DISP=SHR, //* DSN=&CTLLIB(.&DPCTL). <<- See Note 8. //*MANX DD DISP=SHR,DSN=SYS1.MANX <<- See Note 1. //*MANY DD DISP=SHR,DSN=SYS1.MANY <<- See Note 1. //*
The parameters specified for the CASFDUMP procedure depend on the options specified for the system configuration defined to CA SMF Director.
Specifies the name of the control data set.
Specifies the JES SYSOUT class to be used.
Specifies the name of the Load Library containing this product.
Allows for allocation of the alternate or duplex history file. If duplexing is not used, or the DYNAM complex-wide customization option is enabled, specify ALTDS=DUMMY. Otherwise specify ALTDS='VOL=PRIVATE'.
Specifies the name of the device to be used for history files in the alternate pool.
Specifies the name of the device to be used for the primary history file data sets.
Allows for allocation of the primary history file. If the primary history file is not used or the DYNAM complex-wide customization option is enabled, specify PRIDS=DUMMY. Otherwise specify PRIDS='VOL=PRIVATE'.
Sample JCL members (loaded during the install process) CASFDMP1 and CASFDMP4 illustrate how the CASFDUMP procedure can be invoked to start the dump process using a batch job. An operator can also start the dump process manually by entering the z/OS START command:
S CASFDUMP,ALTDS=DUMMY
Optionally, CA SMF Director can also write records out to individual files based on the record type, subtype, and other selection criteria using the SPLIT command in the control statements. To do this, the DD statements for these files must be in the DUMP procedure JCL if the TIME operand is not included in the SPLIT statement. The files should be defined the same way as the output files for an EXTRACT process.
If the TIME operand is included in the SPLIT statement, there is no need to code the ddname in the JCL. The files will be allocated using the attributes in the other TIME operands on the SPLIT statement. For more information on the SPLIT command, see the User Guide.
If in the unlikely event that CA SMF Director is unable to unload the SMF data from the SYSx.MANx files, the IBM utility IFASMFDP can be used to dump and clear the SMF data sets and later the output file created by IFASMFDP can be copied or manually added by this product (see the next two sections for further details). In addition, if CA Service Desk is installed and configured, CA SMF Director can open requests to call attention to issues during the dump.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |