Defining a CPU loop check profile

Using criteria that you define, CPU loop check profiles automatically detect jobs or STCs that might be caught in a CPU loop or are using excessive CPU. Whenever jobs or STCs meet the profile criteria, MainView Alarm Management generates an alert, and you can define other actions that MainView should take.

To define a CPU loop check profile

1. From the MainView for z/OS easy menu (EZMZOS), select the View RealTime Menu option at the top of the panel.
2. From EZMZOSR, select Solutions.
3. From EZMSOL, select Max Check.
4. From EZMMXCK, select List Profiles.

5. From the COMMAND line of the LPCKPL menu, type ADD. 

   Success

   Tip

   Alternatively, you can copy and edit an existing profile. To copy a profile, place the cursor in the CMD column of the existing profile and type R (repeat).

6. Specify the profile's name, description, and criteria:

   Field	Description
   Profile Identity	Enter information about the profile.
   Profile Name	Enter a unique alphanumeric name for the profile. The name can contain up to 12 characters and must start with an alphabetic or national character.
   Profile Desc	(Optional) Enter a short description of the profile.
   Loop Criteria	Define whether the profile should detect jobs that might be in a CPU loop, or only jobs that are using excessive CPU.
   Accumulated CPU time before start	Enter one of the following values: To detect potential CPU loops, enter the amount of CPU time that a job can use before the profile starts monitoring it. To detect excessive CPU usage, specify a time. Use the format hh:mm:ss. The maximum valid value is 23:59:59.
   CPU usage and Delay percent trigger value	Enter one of the following values: To detect potential CPU loops, enter the percentage of the reporting period that an address space can use (or wait to use) the CPU.Valid values are 0 through 100. BMC recommends 95. To detect excessive CPU usage, enter 0.
   Job Names	Specify the jobs to which this profile should or should not apply.
   Include	(Optional) Enter up to five jobs to which this profile should apply. Warning Note When specifying job names, job classes, or service classes, you can specify full or generic names. For generic names, you can use a single trailing asterisk (*), but you cannot use the plus sign (+) wildcard. If you leave any Include field blank, the profile applies to all jobs except those that you list in the corresponding Exclude field.  Information Example Entering PROD* in the job name Include field applies this profile to all jobs that start with PROD. Similarly, entering PROD123* in the job name Exclude field does not apply this profile to any job that starts with PROD123, even if you entered PROD* in the Include field.
   Exclude	(Optional) Enter up to four jobs to which this profile should not apply.
   Job Classes	Specify the job classes to which this profile should or should not apply.
   Include	(Optional) Enter up to five job classes to which this profile should apply.
   Exclude	(Optional) Enter up to four job classes to which this profile should not apply.
   Service Classes	Specify the service classes to which this profile should or should not apply.
   Include	(Optional) Enter up to five service classes to which this profile should apply.
   Exclude	(Optional) Enter up to four service classes to which this profile should not apply.
   Action(s)	Specify the action or actions that MainView should take when a job or STC meets all of the profile's criteria.
   WTO	Specify whether MainView should write a write-to-operator (WTO) message to the system console. Valid values are YES or NO. Enter S next to YES to write the message.
   CANCEL	(Optional) Specify whether MainView should cancel the job or STC. Valid values are YES or NO. Enter S next to YES to cancel the job. Warning MainView for z/OS cannot cancel an STC that was started using an identifier in conjunction with the PROC name. The Cancel, Quiesce, and MVS Command fields are mutually exclusive and optional. A profile can take only one of these three actions.
   QUIESCE	(Optional) Specify whether MainView should quiesce the job. Valid values are YES or NO. Enter S next to YES to quiesce the job. Warning Note If you enter S, you can either define automation to resolve the issue or ask an administrator to resolve the issue manually. Otherwise, the job continues to run with extremely limited resources available.
   MVS Command	(Optional, and for authorized users only) Enter an IBM MVS console command for MainView Alarm Management to run. Warning Note Only users with READ or UPDATE access to the BBM.COMMON.OPERCMD.PA security resource can define an MVS command action. This security resource must be defined in the ESM (using the IBM RACF security product, the CA Technologies CA-ACF2 product, or the CA Technologies CA-Top Secret product). Also, if you specify an MVS command here, MainView for z/OS automatically writes a WTO message to the system console (that is, MainView for z/OS automatically sets the WTO action to Yes). MainView Alarm Management runs this command when a job meets all of the profile's criteria and the profile's alarm generates a START-type alarm message. You can use the following variables in the command: Variable Description &JOBNAME Name of the job that meets all of the profile's criteria &STEPNAME Step name (or job qualifier) associated with an STC that was started using the procName.stepName format of the START command &JOBNUM JES job number &ASID Job's address space ID &CPUMIN Job's current number of CPU minutes used &CPUPCT Job's current CPU usage percentage &JOBCLASS Job's job class &SRVCLASS Job's service class

   Success

   Tip

   For more information about defining the profile criteria, including usage examples, enter HELP at the COMMAND line.

7. To save the profile, at the COMMAND line, type END.
   Saving the profile automatically enables it.

   MainView Alarm Management creates an alarm based on the profile and based on a default alarm definition. If a job meets all of the profile's criteria, MainView Alarm Management takes any actions defined in the profile and generates an alert.

Where to go from here

If you are using an automation product, such as MainView AutoOPERATOR for z/OS, you can configure additional automation to take actions when a job meets all of a CPU loop check profile's criteria and MainView AutoOPERATOR receives the message. Messages start with BBDLC1nnt. For more information about the messages, see the MainView for z/OS online Help. For information about configuring automation for handling messages, seeMainView AutoOPERATOR Basic Automation Guide Volume 1 Using Rules.

See Managing-CPU-loop-and-maximum-value-check-profiles for information about:

• Managing CPU loop check profiles
• Viewing the maximum value check profile alarm
• Viewing alarm reports