Installation and Customization › Modifying #PMGEN Parameters › Parameters

Parameters

CASE=UPLOW/UPPER

Specifies if literals and help text is to appear in uppercase and lowercase (UPLOW) or uppercase only (UPPER). The default is UPLOW. Specify UPPER if the lowercase English alphabet causes problems with your site's terminals.

CONV=PSEUDO/YES

Indicates if the component is to run pseudo-conversationally. PSEUDO (default) indicates that it runs pseudo-conversationally. YES indicates that it runs conversationally. Generally, this parameter is PSEUDO for the Interval and Application Monitors; YES for the Realtime Monitor. NO is a synonym for PSEUDO.

EDIT=YES/NO

Specifies whether the person running the monitor can edit windows. The default is YES.

DSTREAM=FULL/MODIFIED

Specifies whether the data stream sent to the terminal is to be compressed. FULL (default) indicates that the data stream will not be compressed and will use relatively less CPU time but more transmission time. MODIFIED indicates that the data stream will be compressed and will use relatively more CPU time but less transmission time.

PFKEYS=12/24

Defines the number of PF keys in use. The default is 12. If you specify 24, any keys not explicitly used by the monitors are shadow keys (PF17 shadows PF5, PF18 shadows PF6, and so forth).

REFRESH=NO/YES/refresh-interval

Specifies whether Performance Monitor automatically refreshes monitor screens with current statistics. The default is NO. This parameter should be NO for the Interval and Application Monitors. Specify NO, YES, or refresh-interval for the Realtime Monitor:

• YES— the default refresh interval is 10 seconds
• refresh-interval— Performance Monitor automatically refreshes the screen at the interval specified; Refresh-interval must be in the range 1-99
• YES or refresh-interval— Performance Monitor refreshes the screen automatically regardless of the CONV=PSEUDO/YES specification

Note: By default, REFRESH=NO is forced for UCF terminals regardless of the setting in #PMGEN. The REFRESH value will be honored for the setting in #PMGEN. The REFRESH value will be honored for UCF terminals if optional bit 34 is set in RHDCOPTF. Limitations still exist, however, on the use of automatic refresh when using UCF terminals. These limitations arise because the REFRESH option is implemented by issuing a READ BUFFER instead of a READ MODIFIED command when it is checking for input before refreshing the screen.

The limitations are as follows:

• The z/VM front-end UCF module does not support screen refresh. Optional bit 34 should not be applied to a back-end that is to be accessed through UCFCMS.
• Screen refresh is not supported for any other environment where READ BUFFER is not supported. These include TCAM terminals and z/VM PASSTHRU. Do not set the optional bit in these environments.
• Under TSO, the front-end UCF module must be created with the parameter VTAM=YES on the #UCFTSO parameter. This is the recommended value for most sites. For more information, see the Systems Operations Guide.
• Under CICS, we recommend that a special version of the UCF front-end be created for use only with PERFMON. Create this version by assembling the #UCFCICS macro with the parameters RESETKB=ASIS and LASTOUT=TASKEND. This lets multiple WRITE datastreams be sent to the terminal between READ commands, but allows input from the terminal while the front-end UCF task is running. Without these options, terminal hangs or CICS task abends such as ATNI or ATCV can result. These parameters might not be desirable for UCFCICS applications other than PMRM. That is why we recommend a special UCFCICS module.

  Also ensure the CICS terminal control table entry has a TOTAL buffer size large enough to accommodate the realtime monitor READ BUFFER and datastream write commands. In addition, each #UCFUTD macro associated with the UCF front-end should specify BUFSIZ=8192.

  Note that the READ BUFFER command causes the front-end UCFCICS task, which is accessing PMRM, to run conversationally. This means that a CICS task will be running as long as PMRM is running. This task might use increasing amounts of CICS resources such as storage. This might necessitate terminating the PMRM task periodically to release resources.

• For all TP monitors, UCF lets the terminal operator modify the PMRM session only at the REFRESH interval. Attempts to update the screen prematurely can result in problems such as INPUT INHIBITED (X-F at the bottom of the terminal screen). To avoid these problems, the terminal operator should observe the following procedures before pressing a function key or the Enter key:
  • Move the cursor off the command line.
  • Wait for the <<SCREEN HELD>> message to appear on the screen.

    This indicates that PMRM has issued the READ BUFFER and recognized that operator input is pending.

  • Press the desired function key or Enter key.

  It may be helpful to reduce the default refresh interval of 10 seconds by reassembling the #PMGEN macro and relinking the PMRTINIT program. Alternatively, the REFRESH command can be issued from within PMRM.

  Note that optional bit 34 has no effect on non-UCF terminals.

SITESAV=YES/NO

Specifies whether a Performance Monitor user can save version 1 of the monitor screens. The default is YES. As system administrator, you can tailor the screens with YES at installation and then specify NO once Performance Monitor is in production.

Note: For more information about tailoring screen displays, see Tailoring Screens, Task Codes, and Entry Options.

SNAP=NO/YES

Specifies whether Performance Monitor writes a snap dump to the log file whenever the STAE detects an abend within the Performance Monitor. The default is NO. If SNAP=YES, STAE must also be YES.

SORT=YES/NO

Specifies whether the Performance Monitor user can sort windows. The default is YES.

STAE=YES/NO

Specifies whether the Performance Monitor STAE receives control when an abend occurs within the Performance Monitor. The default is YES.

USERSAV=YES/NO

Specifies whether users can save a test version of the monitor screens (any version other than version 1). The default is YES.

Note: For more information about saving modified screen versions, see Tailoring Screens, Task Codes, and Entry Options.