Using action variables

You can use RUV action variables in backup and restore job JCL records to control the variable substitution process.

Action variable syntax

Action variables are enclosed by the less-than symbol and the colon (<:) and a greater-than (>) symbol; <:BEGIN_LOOP> is an example of an action variable.

Note

The <: combination is reserved by RUV and is always interpreted as an action variable. Do not use this combination for any other purpose.

RUV action variables

The following table lists the RUV action variables that you can use:

Examples of action variable usage

The following examples demonstrate the use of RUV action variables in job JCL records.

<:VSOFF> and <:VSON>

In the following example, the <:VSOFF> and <:VSON> action variables are used in a comment to document how a data set name was constructed.

...
//* THIS DSN WAS BUILT USING <:VSOFF><NODE1>.<NODE2>.BACKUP<:VSON>
//DDNAME1 DD DISP=SHR,DSN=<NODE1>.<NODE2>.BACKUP
...

If the input data set name is APY.PAYROLL.EMPL, the following statements result when RUV performs variable substitution:

...
//* THIS DSN WAS BUILT USING <NODE1>.<NODE2>.BACKUP
//DDNAME1 DD DISP=SHR,DSN=APY.PAYROLL.BACKUP
...

<:IMBED outside_source>

In the following example, the <:IMBED outside_source> variable is used to insert a set of IDCAMS Delete statements from a member of a partitioned data set into the generated job.

...
//DLETCMDS DD DSN=IDCAMS.DELETE.COMMANDS(APYDLET),DISP=SHR
...
<:IMBED DLETCMDS>
...

<:BEGIN_LOOP> and <:END_LOOP>

The example in Creation of a Job JCL Record to Perform Backups shows the use of the <:BEGIN_LOOP> and <:END_LOOP> action variables.