Using IBM Application Development Tools for z/OS and OS/390

290 Using IBM Application Development Tools for z/OS and OS/390

11.1 Overview

As mentioned in the prolog, on some occasions you just need to have the data in your hands

and see it on paper. Application Monitor’s online analysis facilities and reports can provide

you with a large amount of data to view. Some developers prefer to have that data on paper

so that they can write their comments beside the data.

Application Monitor’s batch facility provides a way to get those hard-copy reports. Currently

the only limitations are that it cannot do interval reporting and it is not currently possible to

narrow down the number of modules that information is given on. Any reports generated will

be for the whole time period in the analysis file. It may be possible to create a history file with

a limited set of CICS transactions using the named set functionality described in the

Application Monitor Users Guide, SC18-9084-00.

11.2 The JCL - SFBIJCL(FBIBATCH)

Application Monitor ships with a sample piece of JCL that shows how to submit a batch job to

create a text version of the report. The V2R1 Beta version of the JCL is included in

Example 11-1 in its entirety.

Example 11-1 JCL

// (JOBCARD)

//*-------------------------------------------------------------------*

//* *

//* RUN APM 4.1.0 IN BATCH *

//* *

//* THIS JOB PRINTS STARTOOL/APM APPLICATION ANALYSIS REPORTS *

//* *

//* *

//* ONE TIME TAILORING: *

//* *

//* 1. REPLACE "(JOBCARD)" WITH A JOB STATEMENT THAT IS VALID FOR *

//* YOUR INSTALLATION *

//* 2. CHANGE ALL OCCURRENCES OF "FBIINSTALL" TO THE HIGH LEVEL *

//* QUALIFIER OF THE DATA SETS WHERE THE PRODUCT IS INSTALLED. *

//* 3. CHANGE THE ISPF LIBRARIES TO YOUR PRODUCTION LIBRARIES: *

//* "ISP.SISPTENU" TO THE "ISPF PRODUCT TABLES" *

//* "ISP.SISPMENU" TO THE "ISPF PRODUCT MESSAGES" *

//* "ISP.SISPSENU" TO THE "ISPF PRODUCT SKELETONS" *

//* 4. CHANGE "USERID" TO A UNIQUE TSO USERID THAT HAS BEEN LOGGED *

//* ON AT LEAST ONCE IN THE PAST. *

//* 5. REFER TO THE USER'S GUIDE IF YOU WISH TO OVERRIDE ANY *

//* DEFAULTS BY CODING PARAMETERS ON THE ISPSTART COMMAND. *

//* *

//* EACH TIME BEFORE YOU SUBMIT THE JOB: *

//* *

//* 6. CHANGE "HISTORYDSN" TO THE NAME OF THE HISTORICAL DATA SET *

//* WHOSE DATA YOU WANT TO ANALYZE. *

//* 7. IF YOU WANT TO SEE REPORTS OF YOUR COBOL STATEMENTS, *

//* CHANGE "COBOLDSN" TO THE NAME OF THE COBOL LISTINGS DATA SET *

//* AND UNCOMMENT THE //FBICOBOL DD STATEMENT *

//* 8. IF YOU WANT TO SEE REPORTS OF YOUR PL/I STATEMENTS, *

//* CHANGE "PLIDSN" TO THE NAME OF THE PL/I LISTINGS DATA SET *

//* AND UNCOMMENT THE //FBIPLI DD STATEMENT *

//*-------------------------------------------------------------------*

//FBISTEP EXEC PGM=IKJEFT01,REGION=0M,DYNAMNBR=10

Chapter 11. Application Monitor: Generating reports in batch 291

//STEPLIB DD DISP=SHR,DSN=FBIINSTALL.SFBIAUTH

//*

//*-------------------------------------------------------------------*

//* SPECIFY YOUR HISTORY DATA SET ON THE //FBIHIST DD *

//*-------------------------------------------------------------------*

//FBIHIST DD DISP=SHR,DSN=HISTORYDSN

//*

//*-------------------------------------------------------------------*

//* THE //FBIPRINT DATA SET IS RECFM=FBA,RECLEN=133 *

//*-------------------------------------------------------------------*

//FBIPRINT DD SYSOUT=*

//*

//*-------------------------------------------------------------------*

//* USE THE //SYSTSIN DD STATEMENT TO OVERRIDE PROCESSING PARAMETERS *

//*-------------------------------------------------------------------*

//SYSTSIN DD *

PROFILE PREFIX(USERID)

ISPSTART NEWAPPL(FBI) CMD(FBILPM00 PAGELINES=64,TRACE=80,+

SUBSYS=FBI0,+

MAXLINKS=20,MAXREPORTS=500) +

BDISPMAX(10000)

/*

//*

//*-------------------------------------------------------------------*

//* OPTIONALLY, SPECIFY YOUR COBOL LISTINGS FBICOBOL DD *

//*-------------------------------------------------------------------*

//*FBICOBOL DD DISP=SHR,DSN=COBOLDSN

//*

//*-------------------------------------------------------------------*

//* OPTIONALLY, SPECIFY YOUR PL/I LISTINGS FBIPLI DD *

//*-------------------------------------------------------------------*

//*FBIPLI DD DISP=SHR,DSN=PLIDSN

//*

//SYSTSPRT DD SYSOUT=*

//SYSTERM DD SYSOUT=*

//ISPMLIB DD DISP=SHR,DSN=FBIINSTALL.SFBIMENU

// DD DISP=SHR,DSN=ISP.SISPMENU <==CHANGE?

//ISPLLIB DD DISP=SHR,DSN=FBIINSTALL.SFBIAUTH

//ISPPLIB DD DISP=SHR,DSN=FBIINSTALL.SFBIPENU

//ISPTLIB DD DISP=SHR,DSN=ISP.SISPTENU <==CHANGE?

//ISPPROF DD DISP=(NEW,DELETE),DSN=&TEMPPROF,

// SPACE=(TRK,(1,1,1)),UNIT=SYSDA,

// RECFM=FB,LRECL=80,BLKSIZE=6400

//ISPTABL DD DISP=(NEW,DELETE),DSN=&TEMPTABL,

// SPACE=(TRK,(1,1,1)),UNIT=SYSDA,

// RECFM=FB,LRECL=80,BLKSIZE=6400

//ISPSLIB DD DISP=SHR,DSN=ISP.SISPSENU <==CHANGE?

//ISPLOG DD SYSOUT=*,

// DCB=(RECFM=VA,LRECL=125,BLKSIZE=129)

//ISPLST0 DD UNIT=SYSDA,

// SPACE=(TRK,(5,5)),

// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210),

// DISP=(,DELETE,DELETE)

//ISPLST1 DD UNIT=SYSDA,

// SPACE=(TRK,(5,5)),

// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210),

// DISP=(,DELETE,DELETE)

//ISPLST2 DD UNIT=SYSDA,

// SPACE=(TRK,(5,5)),

// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210),

292 Using IBM Application Development Tools for z/OS and OS/390

// DISP=(,DELETE,DELETE)

//*! CHANGELOG <-- USED AS FIND KEY: DO NOT MODIFY !*//

//*! FIXCR=CR20378 30OCT2003 11:01:15 !*//

//*! DSC=ADD LOG/LIST DATA SETS !*//

//*! FIXCR=CR20113 15OCT2003 11:10:28 !*//

//*! DSC=PROVIDE DD STATEMENTS FOR COBOL AND PL/I LISTINGS !*//

//*! PREVMB=Z01BATCH DS=APM410.PCOCHRA.SFBIJCL !*//

//*! FIXCR=CR19915 10OCT2003 19:55:53 !*//

//*! DSC=VSAM DETAILS REPORT DOES NOT PRINT WELL !*//

//*! PREVMB=Z00BATCH DS=APM410.PCOCHRA.SFBIJCL !*//

//*!:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::!*//

The instructions for customization are at the top of the file. It is important to note that the

generated report is written to the FBIPRINT DD name. The file is expected to be

RECFM=FBA, LRECL=133. For ease, we usually pre-allocate a very large data set that we

can use to hold this file, rather than directing it to SYSOUT=*.

We customized the JCL for our CICS run as follows:

{REDBK1.DEV.JCL(FBIBATCH)