Using Global Variables › Global Variable Basics and OPS/REXX › Temporary Global Variables: Duration Specified

Temporary Global Variables: Duration Specified

CA OPS/MVS provides two temporary variable types that exist only for the duration of either an event or a job. GLVEVENT variables are associated with the duration of a specified event and GLVJOBID variables are associated with the duration of a specified job.

• GLVEVENT.stem variables are deleted when the event for which they were created terminates.

  For example, suppose that CA OPS/MVS creates GLVEVENT.MSGTEXT during the processing of an IEF405I message rule; the variable exists for all rules that process that particular IEF405I message. After the last rule associated with that individual message issuance executes, this example occurrence of GLVEVENT.MSGTEXT is automatically deleted.

  Uses for such a variable could include passing data between rules or accumulating data about a message.

• GLVJOBID.stem variables are deleted when the job or started task for which they were created terminates.

  For example, suppose that CA OPS/MVS creates GLVJOBID.MSGTEXT during the processing of a particular job; the variable exists only while that job is active. Furthermore, the variable is associated only with that job. Other jobs could have a variable by the same name containing a different value; after the last rule associated with our example job executes, this occurrence of GLVJOBID.MSGTEXT is automatically deleted.

  You can use such a variable to save data generated by one event in a job for processing in another event in that same job.

Note: As with all CA OPS/MVS temporary global variables, the number of GLVEVENT and GLVJOBID variables you have influences the amount of storage you must allocate using the GLOBALTEMPMAX parameter.