The ACS routines are used to determine the SMS classes for data
sets created by Distributed FileManager/MVS. You can use the &JOB, &PGM,
and &USER read-only variables to distinguish Distributed
FileManager/MVS data set creation requests. The following examples
show how each of these variables can be used.
- &JOB
- The value of the &JOB variable is the job specified in the
Advanced Program to Program Communications (APPC) transaction program
established by the installation systems programmer. Figure 1 shows
how each &JOB can be used to determine the SMS storage class for
a data set being created using Distributed FileManager/MVS:
Figure 1. Example Showing &JOB
Read-Only Variable PROC &STORCLASS
.
.
IF &JOB = 'GDEDFM' AND &STORCLAS = '' THEN
SET &STORCLAS = 'DFMCLASS'
ELSE
.
.
.
- &PGM
- The value of the &PGM variable is specified in the transaction
program profile and is always GDEISASB. Figure 2 shows
how &PGM can be used to determine the SMS storage class for a
data set being created using Distributed FileManager/MVS:
Figure 2. Example Showing &PGM
Read-Only Variable PROC &STORCLAS
.
.
IF &PGM = 'GDEISASB' AND &STORCLAS = '' THEN
SET &STORCLAS = 'DFMCLASS'
ELSE
.
.
.
- &USER
- You can designate a specific user ID under which all Distributed
FileManager/MVS transaction programs are to run. You can then check
the user ID to determine if the data set is being created using Distributed
FileManager/MVS. The user ID is specified in the job statement in
the Distributed FileManager/MVS transaction program profile.
Figure 3 shows how &USER can be used to determine the SMS
storage class for a data set being created using Distributed FileManager/MVS:
Figure 3. Example Showing &USER
Read-Only Variable PROC &STORCLAS
.
.
IF &USER = 'user_ID' AND &STORCLAS = '' THEN
SET &STORCLAS = 'DFMCLASS'
ELSE
.
.
.