AOF Rule Tools › AOF Variables › OPS/REXX Global Variables

OPS/REXX Global Variables

OPS/REXX global variables are compound symbols that begin with a reserved stem of GLOBAL., GLOBALx, or GLVTEMPx. They let you share data between different AOF rules for events that occur from any address space. Programs running in CA OPS/MVS OSF TSO servers, batch, TSO, NetView, and UNIX System Services environments can all access OPS/REXX global variables used in AOF rules.

A global variable with a stem of GLOBAL. or GLOBALx is permanently saved across IPLs or restarts of CA OPS/MVS. A global variable with a stem of GLVTEMPx is saved only while CA OPS/MVS is active.

Examples: OPS/REXX Global Variables Used in AOF Rules

• Rule #1: This rule will execute for every DFHSI1517 message that is issued when a CICS region initializes. An OPS/REXX global variable is created using the region name as part of the compound symbol name so that a unique variable exists for each CICS region, such as GLVTEMP1.UPTIME.CICSA (for region CICSA) and GLVTEMP1.UPTIME.CICSB (for region CICSB). The variable is set to the current system time.

  )MSG DFHSI1517
  )PROC
  /****************************************************************/
  /* Rule Purpose : Set a unique OPS/REXX global variable with    */
  /*                the initialization times of all CICS regions. */
  /* DFHSI1517 cicsregion Control is being given to CICS.         */
  /****************************************************************/
  JOB = MSG.JOBNAME      /* set JOB to issuer of this message     */
  CTIME = TIME()         /* set CTIME to current time             */
  /* Create a unique global variable using the JOB value as a stem*/
  /* name to make it unique. Set it to the CTIME value            */
  SET = OPSVALUE('GLVTEMP1.UPTIME.'JOB,'U',CTIME)                 */
  

• Rule #2: This is an AOF request rule (a different event type from Rule #1) that will execute on demand by any TSO user and be able to access and display the GLVTEMP1.UPTIME OPS/REXX variables set by Rule #1. It is using the OPSVALUE OPS/REXX function to retrieve this variable information.

  )REQ CICSINIT
  )PROC
  /****************************************************************/
  /* Rule Purpose : Display initialization times of active CICS   */
  /*         regions when requested. Obtain this info             */
  /*         via any GLVTEMP1.UPTIME global variable.             */
  /*  Invoked when a TSO users issues OPSREQ CICINIT              */
  /****************************************************************/
  ACTREGIONS = OPSVALUE('GLVTEMP1.UPTIME','L')
  if ACTREGIONS = 0 then
    say 'No initialized regions'
  else
    do ACTREGIONS
      PULL REGION
      UPTIME = OPSVALUE('GLVTEMP1.UPTIME'.REGION,'O')
      say 'CICSINIT - 'REGION' INIT TIME = 'UPTIME
    end
  

  return
  

Note: For a detailed description of the uses and characteristics of GLOBAL., GLOBALx, and GLVTEMPx OPS/REXX global variables, see the User Guide.