General Parameters

Administration of the CICS Feature › Defining Parameters › General Parameters

General Parameters

The General Parameters panel is displayed when option C1 on the PARAMETERS selection window is chosen.

APCDPP01 --- PMA CICS Feature - General Parameters ---------------------------- COMMAND ===> TOP Limit of most important TRAN : 010 0-999 (0 = no alerts generated) Threshold value for module statements: 00.01 00.01-99.99 % CPU Time Threshold value for SQL statements: 00.01 00.01-99.99 % CPU Time Threshold value for DLI statements: 00.01 00.01-99.99 % CPU Time Threshold value for lib. subroutines : 00.01 00.01-99.99 % CPU Time Delete stored measurements in the PMA Profile Pool after : 2 1-9 executions of the PMA Interpret Measurements Job Delete measurement data if older than: 06 01-18 months Delete SMF System data older than : 06 01-18 months Delete SMF TRX data older than : 180 01-540 days Delete SMF Interval data older than : 180 01-540 days For transaction runaway test use : P A = TX CPU time absolute seconds P = TX CPU time total percentage S = TX CPU Service Units per call C = TX CPU time per call Cancel: CAN Save: END OR PF3

Use the General Parameters panel to view or edit parameters that control the report information maintained by the CICS Feature.

Field Name	Description
TOP Limit for most important transactions	Enter the number that you want PMA to use when identifying the top most consuming transactions. For example, if you enter 25, the batch TOP Limit processing determines the top 25 consuming transactions. A number from 1 to 999 is valid. If this field is blank, top consuming transactions are NOT identified. If the TOP Limit parameter is greater than 0 and transactions are found that exceed the statistical limits based on the database, an alert is generated. Use the Alert Management option of the Main Menu to view alerts. If the TOP Limit parameter is 0, alert management is deactivated.
Threshold value for:	Enter the threshold percentage of CPU time from which you would like PMA to save information. If a module statement (or a 64 byte part (standard resolution)), SQL statement, DLI statement or library subroutine exceeds this percentage of CPU time, the information is kept, if not the information is ignored by PMA.
Delete stored measurements in the Measurement Pool after:	Enter the number of times the Interpret Measurements Job should execute and process the measurements of CICS regions before deleting them from the Measurement Pool. A number from 1 to 9 is valid. The Measurement Pool is a wrap around file, meaning older measurement reports are dropped off as new ones are added. All measurement reports of at least one execution are stored in the Measurement Pool Cluster.
Delete measurement data if older than:	Enter the number of months (01 - 18) that you would like to keep the CICS measurement data available. PMA saves a lot of information, thus allowing you to compare performance of transactions, modules, DB2 statements, and so on, over a period of time. However, be aware that the longer the information is kept, the bigger the measurement pool cluster becomes. A monthly scheduled job will delete the CICS measurement data from the VSAM cluster if the expiration time is reached.For details about the job that maintains this file, see Job APCBJREO - Maintenance of Batch Data Cluster.
Delete SMF System data if older than:	Enter the number of months (01 - 18) that you would like to keep the CICS SMF system data available. A monthly scheduled job will delete all CICS SMF system records that have reached the defined expiration time.
Delete SMF TRX data if older than:	Enter the number of days (01 - 540) that you would like to keep the CICS SMF transaction data available. A monthly scheduled job will delete all CICS SMF transaction records that have reached the defined expiration time.
Delete SMF Interval data if older than:	Enter the number of days (01 - 540) that you would like to keep the CICS SMF interval data available. A monthly scheduled job will delete all CICS SMF interval records that have reached the defined expiration time.
For transaction runaway test use:	Enter P for percentage if online runaway tests of transactions will be done with the CPU time total percentage value of the transactions. Enter A for absolute if online runaway tests of transactions will be done with the transactions' absolute CPU time. Enter S for transaction CPU service units per call to be used as a base for calculations of a transaction runaway alert.