In the Mainframe Application Tuner (MAT) Performance Management Assistant (PMA), how does one override the SYSDA value in the APCCJINV job?
search cancel

In the Mainframe Application Tuner (MAT) Performance Management Assistant (PMA), how does one override the SYSDA value in the APCCJINV job?

book

Article ID: 17451

calendar_today

Updated On:

Products

Mainframe Application Tuner

Issue/Introduction

Job APCCJINV calls MAT in order to activate one or more CICS measurements. There is a step that adds control cards - one of them specifying SYSDA as a disk type. If SYSDA is not supported, then subsequent processing by TUNBATCH will fail. When one adds their own control cards, APCCJINV fails with duplicate control cards. 



Environment

Release:
Component: MATUNE

Resolution

When one makes no attempt to override the SYSDA value during customization one receives output similar to this:

BATCHREPORTS -REPDSN('CAMAT.MON.PMALIST.J3337AAA.T0935205') -REPPTRKS(00075) -REPSTRKS(00150) -REPUNIT(SYSDA) -MONDSN('CAMAT.MON.PMA.&JOBNAME.&SYSTIME')

This is what it looks like in total:

MATUNER     MONITOR INVOKE -JOBNAME(CICST1E) -ELAPSTIME(15) -SAMPLECNT(1000) -TARGSYS1(*)    -MONDSTRKS(450) -MONDSSEC(450) -BATCHREPORTS -REPDSN('CAMAT.MON.PMALIST.J3337AAA.T0935205') -REPPTRKS(00075) -REPSTRKS(00150) -REPUNIT(SYSDA) -MONDSN('CAMAT.MON.PMA.&JOBNAME.&SYSTIME')ASSEM)

How do you override the REPUNIT value of SYSDA? In order to override the value go to you hlq.PARMS member and do a search for RUSYSDA. For more information on this parameter please see the PMA Administration Guide, the section titled "Parameter File".

The unit is taken from the PMA parameter file, parameter id RU (column 1 + 2)

RUSYSDA

To change the unit definition please edit the PMA Parameter file and change the RU parameter line with the unit definition you want to use.

Example: if you want to user SYSALLDA then the parameter line is RUSYSALLDA.



In order to set the value correctly during PMA Customization, please NOTE that in the PMA Admin Guide, in the Customization Step 3, "Specify Operational Defaults", is where that parm gets it's initial value.