SOLUTION parameter
According to FLST/RLST conventions, a resource or record is checked against each SET statement in the RLST.
When a resource matches a SET statement, the RLST process is stopped without interrogating subsequent SET statements. The resource is processed according to the first matching SET statement’s keywords. The SOLUTION parameter changes this behavior, allowing a resource, or record, to be processed against multiple SET statements in a single request.
The AUTO function RLST members usually contain multiple SET statements. Each SET statement uses INC/EXC statements to select resources and then determines actions to take (according to keywords in the SET statement). The SOLUTION parameter is used to associate each AUTO request with one or more individual conditions, SET statements, that should be checked for during the AUTO request.
The SOLUTION parameter is specified in the SOLUTION keyword of the AUTO console command request and in each SET statement in the RLST members of AUTO functions. The SOLUTION parameter is optional, but it is highly recommended on all SET statements in the RLST members of AUTO functions.
When coding RLST members, use caution when processing multiple SET statements without the SOLUTION keyword or with the same SOLUTION keyword value in a single request. When a record matches a SET statement in the RLST, the record is then associated with that SET statement. A record can only be associated with one SET statement. Any subsequent SET statements in the RLST member are bypassed. The result group that is created by a subsequent SET statement could be incomplete if the record also applied to INC/EXC statements of that SET statement. BMC Software highly recommends using the SOLUTION keyword on all SET statements of the RLST members across all AUTO functions except AUTOADDV.
Example of not using the SOLUTION parameter
In the following example, the first SET statement is intended to release free space in PO type data sets; job SRMRLSE is submitted, containing any data sets that have a DSORG of PO and have less than 80% space used.
The second SET statement migrates data sets that have not been recently used. SRMHMIG is submitted to migrate any data sets that have not been referenced in at least 10 days and that are at least 100 tracks in size.
Example of using the SOLUTION parameter
In this example, the SOLUTION parameter is used.
Each data set in the storage group is checked against both SET statements. The data set is included in the SRMRLSE and SRMHMIG jobs.
ACT_JOB=SRMRLSE
INC AD_DSORG = PO
AD_PUSED < 80
SET SOLUTION=HMIGA
ACT_JOB=SRMHMIG
INC AD_DAYS > 10
AD_TRKSA > 100
The resulting AUTO command is:
AUTODS POOL= storageGroup,SOL=(RLSEFREE,HMIGA)
Example of using variables
The following examples show how to define and use variables.
Defining the FINCVOL variable Result | Result |
|---|---|
SET VARIABLE=FINCVOL VALUE=FINC/ VALUE=GLAP/ VALUE=PAY/ VALUE=RECV9? | FINCVOL is a variable that is defined with four volume specifications. |
Using the FINCVOL variable in an AUTO function: | |
|---|---|
SET SOLUTION=AUTOV1 X ACT_JOB=AUTOV1 INC AV_FREEC > 100 VOL=&FINCVOL |
Issuing AUTO command to drive the AUTO function using the variable: | Result |
|---|---|
/SVOS AUTOVOL,SOLUTION=AUTOV1,VOL=/ | This example will cause the volumes that fit the criteria for the FINCVOL variable to be processed against the AUTOV1 solution and all volumes with over 100 free cylinders to be included in the skeleton JCL member AUTOV1. |
INC AD_DSORG = PO
AD_PUSED < 80
SET ACT_JOB=SRMHMIG
INC AD_DAYS > 10
AD_TRKSA > 100
Related topic