Example: Working with Personal Systems
The System Definitions facility in the CICS PA dialog requires some planning to ensure that you are able to best meet your reporting requirements. CICS PA has some powerful features that will help you to define your System Definitions. This section provides some useful tips on how to use these features.
- The System Definitions menu.
From the Primary Option Menu, option 1 System Definitions takes you to the System Definitions menu. From this menu, you are able to define your CICS® systems, and maintain your SMF Files and Groups.
- Using Take-up to define your CICS systems.
You can explicitly define you CICS systems, but an easier way to define your systems is by using option 4 Take-up from SMF File. Take-up populates your System Definitions with systems found in your SMF File.
File Options Help ------------------------------------------------------------------- Data Take-Up from SMF Command ===> _____________________________________________________ Specify the SMF File for data take-up. Data Set Name . . . 'MVS1.SMFDATA'_______________________________ Specify details if data set is not cataloged: UNIT . . . . . ________ + VOLSER . . . ______ + SEQ Number . . ___ (1 to 255) Execution Mode: 1 1. Submit Batch JCL 2. Edit Batch JCL
Specify the SMF File that contains records from the systems that you want to define, and then press Enter to submit the Take-up job.
Review the Take-up job output to see the systems detected by CICS PA in the File.V5R3M0 17:29:39 1/13/2015 CICS Performance Analyzer Page 1 Take-up from SMF CPA2012I Processing started for SMF file SMFIN001 CPA2017I SMF records for System MVS1 start at 1/13/2015 15:41:38.39 CPA2014I CMF record for CICS system found, APPLID=CICPTOR1 Release=7.0.0 CPA2014I CMF record for CICS system found, APPLID=CICPAOR1 Release=7.0.0 CPA2014I CMF record for CICS system found, APPLID=CICPAOR2 Release=7.0.0 CPA2014I CMF record for CICS system found, APPLID=CICPDOR1 Release=7.0.0 CPA2023I CICS TG record for CICS system found, APPLID=CICSTG01 CPA2015I DB2 Accounting record found, DB2 SSID=DB2P Release=10.1 CPA2016I MVS System Logger record found, System=MVS1LOGR CPA2013I Processing ended for SMF file SMFIN001 - 8 system(s) found CPA2000I Take-up processing has completed, RC=0
After the take-up job has completed, you can then apply the results of the Take-up. Next time you enter System Definitions, you are prompted to apply the results of Take-up.Data Take-Up from SMF Command ===> __________________________________________________ ********************************************* * Take-Up from SMF * ********************************************* CICS PA has completed extracting systems from the following SMF File: Data Set . . : 'MVS1.SMFDATA' Instructions: Press ENTER to continue adding the systems. Enter DEFER command to defer adding the systems. Enter END or CANCEL command to cancel adding the systems.
Press Enter to complete the Take-up process.
- Updating your System Definitions.
You can now update your System Definitions by using option 1 Define Systems, SMF Files and Groups.
Personal System Definitions Row 1 from 8 Command ===> ________________________________________________ Scroll ===> PAGE Select a System to edit its definition, SMF Files and Groups. SMF Files / System Type Image Description System _ MVS1 Image Production MVS Image is MVS1 MVS1 _ CICPAOR1 CICS MVS1 Production AOR #1 MVS1 _ CICPAOR2 CICS MVS1 Production AOR #2 MVS1 _ CICPDOR1 CICS MVS1 Production DOR #1 MVS1 _ CICPTOR1 CICS MVS1 Production TOR #1 MVS1 _ CICSTG01 CICS MVS1 Production CICS TG #1 MVS1 _ DB2P DB2 MVS1 Production DB2 subsystem MVS1 _ MVS1LOGR Logger MVS1 System Logger for Image MVS1 MVS1 ********************************* End of list *********************************
You will notice that your CICS (and possibly DB2®, MQ, System Logger, and CICS Transaction Gateway) systems are defined. Update the System descriptions for easier identification.
Note the SMF Files indicators. Image MVS1 "owns" the SMF File, MVS1.SMFDATA. All other systems can use Image MVS1's file because their definitions specify the same Image name of MVS1, that is, these systems run on Image MVS1.
The systems are now ready for immediate reporting, however we will assign the systems to a Group to demonstrate Cross-System style reporting.
- Defining a Group.
You can group your systems together by defining them to a Group by using option 3 Maintain Group definitions. Use the NEW command to define a new Group.
Systems in this Group Row 1 to 1 of 1 Command ===> ___________________________________________ Scroll ===> PAGE Group . . . . . . PROD Description . . . Production CICS MRO Group / System + Type Image Description S ________ ____________________________________ ********************************* End of list ****************************
Use the S line action to select systems for Group PROD.Systems Row 1 to 11 of 11 Command ===> ____________________________________ Scroll ===> PAGE Select one or more Systems then press EXIT. System Type Image Description S CICPAOR1 CICS MVS1 Production AOR #1 S CICPAOR2 CICS MVS1 Production AOR #2 S CICPDOR1 CICS MVS1 Production DOR #1 S CICPTOR1 CICS MVS1 Production TOR #1 S CICSTG01 CICS MVS1 Production CICS TG #1 S DB2P DB2 MVS1 Production DB2 subsystem _ MVS1 Image Production MVS Image is MVS1 S MVS1LOGR Logger MVS1 System Logger for Image MVS1 *************************** End of List ****************************
All CICS systems, the CICS Transaction Gateway system, the DB2 subsystem, and the System Logger are selected. Exit to insert these systems into Group PROD.Systems in this Group Row 1 to 6 Command ===> ___________________________________________ Scroll ===> PAGE Group . . . . . . PROD Description . . . Production CICS MRO Group / System + Type Image Description _ CICPAOR1 CICS MVS1 Production AOR #1 _ CICPAOR2 CICS MVS1 Production AOR #2 _ CICPDOR1 CICS MVS1 Production DOR #1 _ CICPTOR1 CICS MVS1 Production TOR #1 _ CICSTG01 CICS MVS1 Production CICS TG #1 _ DB2P DB2 MVS1 Production DB2 subsystem _ MVS1LOGR Logger MVS1 System Logger for Image MVS1 ********************************* End of list ****************************
Group PROD is now ready for immediate reporting.
- Running a Report Set.
Select Primary Option Menu option 2 Report Sets to invoke the Report Sets facility.
This section will not go into the detail of specifying reports in a Report Set, but rather give examples of how to specify System Selection at run time. Note that you can specify the System(s) to be reported by defining them explicitly in the Report Set, but we will specify them at run time.Report Sets Row 1 to 4 of 4 Command ===> ________________________________________________ Scroll ===> PAGE Report Sets Data Set . . : user.CICSPA.RSET / Name Description Changed ID ___. CROSSSYS Cross-System reporting 2012/12/13 16:08 CICSPA ___ DAILY Daily CICS Performance reports 2012/12/13 16:08 CICSPA RUN DB2 DB2 reporting 2012/12/13 16:08 CICSPA ___ WEEKLY Weekly CICS Performance reports 2012/12/13 16:09 CICSPA ********************************* End of list *********************************
Enter the RUN command to run Report Set DB2. This displays the Run Report Set panel from where you are able to specify the Systems to be reported.
- Running a Report Set against an individual System. To run a Report Set against an individual System, specify the CICS APPLID, DB2 SSID, MQ SSID, or Logger system name. In this example, we will run the DB2 Report Set against CICS APPLID CICPDOR1 that uses DB2 SSID DB2P.
File Systems Options Help ------------------------------------------------------------------------------- Run Report Set DB2 Command ===> __________________________________________________________________ Specify run Report Set submission options then press Enter to continue submit. System Selection: CICS APPLID . . CICPDOR1 + Image . . MVS1____ + Group . . ________ + DB2 SSID . . . DB2P + Image . . MVS1____ + Group . . ________ + MQ SSID . . . ____ + Image . . ________ + Group . . ________ + Logger . . . . ________ + Image . . ________ + Group . . ________ + _ Override System Selections specified in Report Set _ Read SMF File to EOF ------ Report Interval ----- Missing SMF Files Option: YYYY/MM/DD HH:MM:SS.TH 2 1. Issue error message From 2012/11/08 09:00:00.00 2. Leave DSN unresolved in JCL To 2012/11/08 16:00:00.00 3. Disregard offending reports Enter "/" to select option / Edit JCL before submit F1=Help F3=Exit F4=Prompt F7=Backward F8=Forward F10=Actions F12=Cancel
The generated JCL will request the DB2 report to be run against the specified CICS APPLID CICPDOR1 using DB2 SSID DB2P://JOBNAME JOB (ACCOUNT),'NAME' //* CICS PA V5R3 Report JCL //CICSPA EXEC PGM=CPAMAIN //STEPLIB DD DSN=CPA.V5R3M0.SCPALINK,DISP=SHR //SYSPRINT DD SYSOUT=* //* SMF Input Files //SMFIN001 DD DSN=MVS1.SMFDATA,DISP=SHR . . . //* Command Input //SYSIN DD * * Report Set =DB2 * Description=DB2 reporting CICSPA SMFSTART(2012/11/08,09:00:00.00), SMFSTOP(2012/11/08,16:00:00.00) * Reports for System=CICPDOR1 * Image =MVS1 * Description=Production DOR #1 CICSPA IN(SMFIN001), APPLID(CICPDOR1), DB2(OUTPUT(DB2R0001), SSID(DB2P), LONGSUM) /*
Notice that the APPLID and SSID operands specify the CICS generic APPLID and DB2 Subsystem ID that were requested for reporting.
- Running a Report Set against a Group of Systems. To run a Report Set against a Group, specify the Group name. In this example, we will run the CROSSSYS Report Set against Group PROD.
Run Report Set CROSSSYS Command ===> __________________________________________________________________ Specify run Report Set submission options then press Enter to continue submit. System Selection: CICS APPLID . . ________ + Image . . ________ + Group . . PROD____ + DB2 SSID . . . ____ + Image . . ________ + Group . . ________ + MQ SSID . . . ____ + Image . . ________ + Group . . ________ + Logger . . . . ________ + Image . . ________ + Group . . ________ + _ Override System Selections specified in Report Set _ Read SMF File to EOF ------ Report Interval ----- Missing SMF Files Option: YYYY/MM/DD HH:MM:SS.TH 2 1. Issue error message From 2012/11/08 09:00:00.00 2. Leave DSN unresolved in JCL To 2012/11/08 16:00:00.00 3. Disregard offending reports Enter "/" to select option / Edit JCL before submit F1=Help F3=Exit F4=Prompt F7=Backward F8=Forward F10=Actions F12=Cancel
The generated JCL will request the Cross-System report to be run against the specified Group PROD://JOBNAME JOB (ACCOUNT),'NAME' //* CICS PA V5R3 Report JCL //CICSPA EXEC PGM=CPAMAIN //STEPLIB DD DSN=CPA.V5R3M0.SCPALINK,DISP=SHR //SYSPRINT DD SYSOUT=* //* SMF Input Files //SMFIN001 DD DSN=MVS1.SMFDATA,DISP=SHR . . . //* Command Input //SYSIN DD * * Report Set =CROSSSYS * Description=CICS PA Report Set CICSPA SMFSTART(2012/11/08,09:00:00.00), SMFSTOP(2012/11/08,16:00:00.00) * Reports for Group=PROD * Description=Production CICS MRO Group CICSPA IN(SMFIN001), APPLID(CICPAOR1, CICPAOR2, CICPTOR1, CICPDOR1), CROSS(OUTPUT(CROS0001), EXTERNAL(CPAXW001), PRINTMULTIPLE,NOPRINTSINGLE,NOWRITE) /*
Notice that the APPLID operand specifies all CICS generic APPLIDs belonging to group PROD which was the Group requested for reporting.
- Running a Report Set against all Systems on an MVS™ Image. To run a Report Set against an Image, specify the Image name. In this example, we will run the DAILY Report Set against Image MVS1.
Run Report Set DAILY Command ===> __________________________________________________________________ Specify run Report Set submission options then press Enter to continue submit. System Selection: CICS APPLID . . ________ + Image . . MVS1____ + Group . . ________ + DB2 SSID . . . ____ + Image . . ________ + Group . . ________ + MQ SSID . . . ____ + Image . . ________ + Group . . ________ + Logger . . . . ________ + Image . . ________ + Group . . ________ + _ Override System Selections specified in Report Set _ Read SMF File to EOF ------ Report Interval ----- Missing SMF Files Option: YYYY/MM/DD HH:MM:SS.TH 2 1. Issue error message From 2012/11/08 09:00:00.00 2. Leave DSN unresolved in JCL To 2012/11/08 16:00:00.00 3. Disregard offending reports Enter "/" to select option / Edit JCL before submit F1=Help F3=Exit F4=Prompt F7=Backward F8=Forward F10=Actions F12=Cancel
The generated JCL will request the Performance Summary report to be run against the specified Image MVS1. Note the NOAPPLID operand, which specifies that all CICS systems are reported.
//JOBNAME JOB (ACCOUNT),'NAME' //* CICS PA V5R3 Report JCL //CICSPA EXEC PGM=CPAMAIN //STEPLIB DD DSN=CPA.V5R3M0.SCPALINK,DISP=SHR //SYSPRINT DD SYSOUT=* //* SMF Input Files //SMFIN001 DD DSN=MVS1.SMFDATA,DISP=SHR . . . //* Command Input //SYSIN DD * * Report Set =DAILY * Description=Daily CICS Performance reports CICSPA SMFSTART(2012/11/08,09:00:00.00), SMFSTOP(2012/11/08,16:00:00.00) * Reports for Image=MVS1 * Description=Production MVS Image is MVS1 CICSPA IN(SMFIN001), NOAPPLID, SUMMARY(OUTPUT(SUMM0001), INTERVAL(00:15:00), FIELDS(STOP(TIMES), TRAN, TASKCNT, RESPONSE(AVE), RESPONSE(MAX), DISPATCH(TIME(AVE)), CPU(TIME(AVE)), SUSPEND(TIME(AVE)), DISPWAIT(TIME(AVE)), FCWAIT(TIME(AVE)), FCAMCT(AVE), IRWAIT(TIME(AVE)), SC24UHWM(AVE), SC31UHWM(AVE)), TITLE1( 'Transaction Summary by Time-of-Day ')) /*