Writing Rules › How Do You Maintain Rules? › SET: Establishing the CA ACF2 Option for DB2 Rule Setting › Syntax › Parameters

Parameters

The SET subcommand takes the following parameters:

SET|T

Indicates that you are establishing the CA ACF2 Option for DB2 rule setting.

DB2(typecode)

Indicates that you want to administer an CA ACF2 Option for DB2 rule that covers a particular type of resource in the DB2 class of CA ACF2 infostorage records. If you specify a type code on the SET subcommand different from the one you specified for the $TYPE control statement in the rule, the $TYPE control statement overrides the type code specified on the SET subcommand.

SYSID(sysid)

Specifies the DB2 subsystem ID or group SYSID of the CA ACF2 Option for DB2 rules that you want to process. This SYSID remains active until you change it with the SET subcommand or override it with the SYSID parameter of individual ACF subcommands. You cannot mask this parameter to process multiple records with similar SYSIDs. However, you can use asterisks to identify a SYSID for a single rule that covers multiple DB2 subsystems. For example, use a SYSID of DB** to create a rule set that covers all DB2 subsystems beginning with DB. See SYSID Use in CA ACF2 Option for DB2 in “Defining DB2 Records,” chapter for more information about using the SYSID.

If you specify SYSID, you cannot specify MSYSID.

MSYSID(sysidmask)

Specifies a mask to indicate the subsystem IDs or group SYSIDs of the CA ACF2 Option for DB2 rules that CA ACF2 Option for DB2 processes under the CA ACF2 Option for DB2 rule setting, but you can override it with the SYSID parameter of individual ACF subcommands. See SYSID Use in CA ACF2 Option for DB2 section in the “Defining DB2 Records,” chapter for more information about using the MSYSID.

If you specify MSYSID, you cannot specify SYSID.

FORCE|NOFORCE

The FORCE parameter stores the CA ACF2 Option for DB2 rule set regardless of whether it currently exists in the Infostorage database. NOFORCE stores the CA ACF2 Option for DB2 rule set only if it does not already exist. FORCE is the default. The FORCE or NOFORCE parameter is in effect until it is changed or until you end ACF command processing.

MEMBER(nnnnnnn)

Use this parameter to determine CA ACF2‑generated member names for partitioned data sets. Whenever an CA ACF2 Option for DB2 rule set is decompiled into a partitioned data set (PDS), no member name is specified, and no $MEMBER control statement was specificed in the rule set, CA ACF2 Option for DB2 uses the $KEY of the decompiled rule set to determine the member name. For example, an CA ACF2 Option for DB2 rule set with the $KEY of TABLE would be compiled into the TABLE member.

However, the $KEY might form an invalid member name, particularly when the $KEY is masked. In such a case, CA ACF2 Option for DB2 generates a member name by taking the right five digits of the value of the MEMBER parameter, incrementing the value of these digits by one, and then preceding the result by an at‑sign (@) symbol. For example, if the value of this parameter is 00003, the CA ACF2 Option for DB2‑generated name to replace an invalid member name is @00004.

The most recently used CA ACF2 Option for DB2‑generated member name is stored. It is incremented by one to form the next CA ACF2 Option for DB2‑generated member name unless the MEMBER parameter is respecified in the meantime. This parameter must be a number from 0 to 9999999.

One way to keep CA ACF2 Option for DB2 from generating a member name during decompilation is to specify a $MEMBER control statement in the CA ACF2 Option for DB2 resource rule.