Previous Topic: How VRM Variable Definitions Are UsedNext Topic: How VRM Variable Definitions Differ from Other VRM Definitions

Virtual Resource Management › Resource Types › VRM Variable Definitions › Examples

Examples

In Examples 1 through 3, consider the following variables that are defined for job A:

OPT  SCHID   RESOURCE NAME                STEPNAME     TYPE FREE

     0       SCHENV.SHIFT1                             VAR  N
     2       SCHENV.SHIFT2                             VAR  N
     15      SCHENV.SPECIAL                            VAR  N
     20      SCHENV.NONE                               VAR  N

Example 1

WLMSE=YES is coded on the OPTIONS statement in the initialization file. If job A is demanded with SCHID=2, CA WA CA 7 Edition inserts SCHENV='SHIFT2' on the JOB statement for A.

Example 2

WLMSE=YES is coded on the OPTIONS statement in the initialization file. Suppose that job A is demanded with SCHID=3. Because you have no specific definition for SCHID=3, the value from the definition for SCHID=0 is used (SCHENV.SHIFT1).

Example 3

WLMSE=YES is coded on the OPTIONS statement in the initialization file. Schedule scan brings in job A with SCHID=20. 'SCHENV.NONE' is a reserved resource name in a VRM variable definition. The name indicates that the job is submitted without inserting the SCHENV keyword.

In Examples 4 and 5, consider the following variables that are defined for job B. No variable has been defined for SCHID 0.

OPT  SCHID   RESOURCE NAME                STEPNAME     TYPE FREE

     5       SCHENV.FIVE                               VAR  N
     55      SCHENV.FIFTY_FIVE                         VAR  N
     100     SCHENV.NONE                               VAR  N

Example 4

WLMSE=VANILLA is coded on the OPTIONS statement in the initialization file. Job B is demanded with SCHID=30. SCHID 30 has no specific definition. Since SCHID 0 has no definition, CA WA CA 7 Edition uses the global value and inserts SCHENV='VANILLA' on the JOB statement for B.

Example 5

WLMSE=YES is coded on the OPTIONS statement in the initialization file. Job B is demanded with SCHID=20. Because SCHID 20 has no specific definition, no generic definition for SCHID 0 and no global default that is specified for WLMSE, the job is submitted without any SCHENV keyword.