Posted: Thu Feb 05, 2004 7:54 am Post subject: System Performance
Hi,
i want to know what is the functionality of parameter PERFORM in the
JOBCLASS. i refered few books,which specifies that PERFORM
determines the rate of programs being executed for accessing the
system resources.the values given to these parameter is 0 to 999.
will it help in system performance if i define this parameter in
JES2PARM ? presently the value defined for PERFORM in JES2PARM is
000 and if i increase to 10, how is it going to effect?
Joined: 26 Nov 2002 Posts: 12378 Topics: 75 Location: San Jose
Posted: Thu Feb 05, 2004 9:19 am Post subject:
Meghana,
Use the PERFORM parameter in WLM compatibility mode to specify the performance group for the job. The installation-defined performance groups determine the rate at which associated jobs have access to the processor, storage, and channels.
In WLM goal mode, the PERFORM parameter on the JOB statement can be used to classify jobs and started procedures to a service class and/or report class. This classification method is provided to reduce the need to modify existing JCL when migrating to goal mode. Note that PERFORM on the EXEC statement is ignored in goal mode for jobs and started procedures.
Syntax
PERFORM=n
Subparameter Definition
n
In WLM compatibility mode, requests a performance group. The n is a number from 1 through 999 and must identify a performance group that has been defined by your installation. The specified performance group should be appropriate for your job type according to your Installation's rules.
In WLM goal mode, n can be used to classify the job or started task to a service class and/or report class.
Defaults :
In compatibility mode, if no PERFORM parameter is specified or if the specified PERFORM number fails validity checks, the system uses an installation default specified at initialization. If the installation did not specify a default, the system uses a built-in default:
Default Use
1 For non-TSO/E jobs
2 For TSO/E sessions
Overrides
A JOB statement PERFORM parameter applies to all steps of the job and overrides any EXEC statement PERFORM parameters.
Code EXEC statement PERFORM parameters when each job step executes in a different performance group. The system uses an EXEC statement PERFORM parameter only when no PERFORM parameter is on the JOB statement and only during the job Step.
Examples of the PERFORM Parameter
Example 1: PERFORM in compatibility mode
//STEP1 JOB ,MARLA,CLASS=D,PERFORM=25
In this example, CLASS=D determines the class in which the system will execute the job. Once in the system, the job will run in performance group 25. The installation must have defined the significance of this performance group.
Example 2: PERFORM in goal mode
//STEP1 JOB , KIRTS,PERFORM=26
In this example, the job will be associated with service class PBATCH because the PERFORM value is specified as 26, and the PERFORM value of 26 is defined to workload management as being associated with the service class named PBATCH. To associate the PERFORM value with a service class, you need to define a classification rule in the workload management service definition. The following panel from the WLM application shows a rule for subsystem type JES that assigns any job with a PERFORM value of 26 to service class PBATCH.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum