EDIT JCH.SPFTEMP2.CNTL Columns 00001 00072 Command ===> SUB_____________________________________________ Scroll ===> CSR_ ****** ***************************** Top of Data ****************************** 000001 //CICSPA JOB ,NOTIFY=&SYSUID 000002 //* CICS PA V5R1 HDB Report JCL 000003 //CICSPA EXEC PGM=CPAMAIN 000004 //STEPLIB DD DISP=SHR,DSN=CPA.V5R1M0.SCPALINK 000005 //CPAHDBRG DD DISP=SHR,DSN=CICSPROD.CICSPA.XYX.REPOSTRY 000006 //SYSPRINT DD SYSOUT=* 000007 //* Command Input 000008 //SYSIN DD * 000009 * HDB=CICSWEEK 000010 * Description=Weekly CICS Transactions 000011 CICSPA SMFSTART(2004/12/07,09:00:00.00), 000012 SMFSTOP(2004/12/07,16:00:00.00) 000013 CICSPA NOAPPLID, 000014 LINECNT(60),PRECISION(4), 000015 FORMAT(':','/'), 000016 HDB(OUTPUT(HDBR0001),REPORT(CICSWEEK), 000017 NOTOTALS, 000018 INTERVAL(01:00:00)) 000019 /* 000020 //* HDB Container Data Sets. HDB Report processing does not require 000021 //* these data sets to be included in the JCL as they are dynamically 000022 //* allocated when required. They are included: 000023 //* 1) for your reference 000024 //* 2) to ensure that all required data sets are cataloged 000025 //* 3) to allow DFHSM to recall required data sets up front 000026 //HDB00001 DD DISP=SHR,DSN=CICSPA.HISTORY.CICSWEEK.D03219.T092846.HDB ****** **************************** Bottom of Data ****************************
The HDB container data sets are listed at the end of the JCL. They are not required here because the CICS PA batch reporting utility will dynamically allocate the data sets when they are required. CICS PA adds the data sets into the JCL primarily for the purpose of DFHSM recall, if required. It is more efficient to recall data sets in the JCL (where job initiation can recall migrated data sets en masse) rather than one at a time when dynamically allocated.
HDB(OUTPUT(HDBR0001),REPORT(CICSWEEK))
Enter SUBmit in
the command line to submit the job to run the report.