This site will undergo a maintenance outage on Saturday, 13 September beginning at 2:30 AM Central/1 PM IST for a platform upgrade. The downtime will be ~three hours.

Controlling the TMTM Extensible Agent on z/OS platforms

Two prompt commands are available as listed in the table below. BMC recommends that you run the z/OS TMTM Extensible Agent and monitoring extension as started tasks, although they can be run as batch jobs, if required. This section also includes details on setting the TZ environment variable (ENVAR).

Command

Function

START procnamea

Starts the monitoring extension. Procname is the name of the JCL procedure or job used for the monitoring extension.

STOP procnameb

Stops the monitoring extension. Procname is the name of the JCL procedure or job used for the monitoring extension.

Note

For performance reasons, we recommend running the QPEA address space as non-swappable. Consult the Program Properties Table (PPT) section of the z/OS Initialization and Tuning Reference for further information.

We also recommend assigning the QPBTM and QPEA address spaces to a service class that maintains a dispatching priority at least as high as the highest-priority application you are monitoring.

Related topics

Installing-the-Agent-and-monitoring-extensions

Basic-command-parameters-to-control-the-TMTM-Configuration-Agent 

To run the TMTM Extensible Agent and monitoring extensions as started tasks in z/OS

To run the z/OS agent and monitoring extensions as started tasks, customize the JCL procedures QPEA, QPCFG, QPBTM, and QPMON in HLQ.INSTALL.CNTL and copy them into the appropriate procedure library (for example, SYS1.PROCLIB). We also suggest you use the names QPEA, QPCFG, QPBTM, and QPMON, although you can choose any names. For documentation purposes, we assume that you chose QPEA, QPCFG, QPBTM, and QPMON.

To run the TMTM Extensible Agent and monitoring extensions as batch jobs in z/OS

To run the agent and monitoring extensions as jobs, customize and submit the JQPEA, JQPCFG, JQPBTM, and JQPMON jobs. JQPEA, JPQCFG, JQPBTM, and JQPMON must be configured and run on each z/OS image or LPAR in which WebSphere MQ is running.

To set the TZ environment variable (ENVAR) in runtime option member (CEEOPTS DD)

The recommended approach is to define a CEEOPTS DD in the started task procedure and to point it to the CEEOPTS member in the product's HLQ.INSTALL.CNTL library. Then adjust the ENVAR example setting in CEEOPTS to your needs. Refer to the example procs (members QPEA, QPCFG, QPMON, and QPBTM) in the HLQ.INSTALL.CNTL library for how to configure the CEEOPTS DD.

It is good practice when doing a version upgrade to review the current started task procedures and to carry forward all changes that were introduced by the new version.

For example:

Add this line to the started task procedure: //CEEOPTS DD DSN=&THISPDS(CEEOPTS),DISP=SHR

Edit the example CEEOPTS member so it looks similar to the one below:

HEAP(500M,16M,ANY,KEEP,16K,16K) 
HEAPP(ON,8,1,32,23,128,12,256,1,1024,1,2048,1) 
MSGFILE(SYSOUT,FBA,121,0,ENQ) 
ENVAR(TZ=CST6CDT)

Below is a list of other possible values for the TZ environment variable:

  • EST5EDT: Eastern Standard Time, Eastern Daylight Time
  • CST6CDT: Central Standard Time, Central Daylight Time
  • MST7MDT: Mountain Standard Time, Mountain Daylight Time
  • PST8PDT: Pacific Standard Time, Pacific Daylight Time
  • AKST9AKDT: Alaska Standard Time, Alaska Daylight Time
  • GMT0BST: Greenwich Mean Time, British Summer Time
  • WET0WEST: Western Europe Time, Western Europe Summer Time
  • CET-1CEST: Central Europe Time, Central Europe Summer Time
  • EET-2EEST: Eastern Europe Time, Eastern Europe Summer Time

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*