Writing Rules › How Do You Specify CA ACF2 Option for DB2 Rules? › Syntax

Syntax

The syntax of the rule set is:

     $Key(resourcekey)

     $Type(typecode)

     $Sysid(sysidmask)

    [$Lidowner(logonid)|$UIdowner(uidmask)|$ROLOWNER(role)]
    [$MEmber                                ]
    [$MOde(ABORT|LOG|QUIET)                 ]
    [$NORULELNG                             ]
    [$NOSort                                ]
    [$OWNER                                 ]
    [$Prefix(prefix value)                  ]
    [$Roleset                               ]
    [$USerdata(text)                        ]
    [%Change uidmask1,uidmask2,...,uidmaskn ]
    [%Rchange uidmask1,uidmask2,...,uidmaskn]
    [extended resource key                  ]
    [UId(uidmask)|ROle(role)|USer(logonid)  ]
    [USer(logonid)                          ]
    [ROle(role)                             ]
    [SHift(shift)                           ]
    [Active(date)                           ]
    [UNtil(date)                            ]
    [For(date)                              ]
    [SErvice(keyword1,keyword2,...,keywordn)]
    [Column(column1,column2,...,columnn)    ]
    [Data(text)                             ]
    [Allow|Log|Prevent                      ]
    [NEXTKEY(nextkey)                       ]
     *comment

You can use a dash (-) as the last nonblank character on the line to continue input to the compiler on multiple lines. For example, to continue a rule entry (in this example, the line beginning with UID starts the rule entry) in a rule set, enter the dash in this way:

$KEY(ACCT.EMPL_EXEMPTIONS)
$TYPE(TBL)
$SYSID(PROD)
 UID(TFINPAYISO) SHIFT(NORMAL)- 
 SERVICE(UPDATE) COLUMN(NAME,EXMPTION) ALLOW

CA ACF2 Option for DB2 recognizes a continuation unconditionally. This means that if a comment statement is continued, CA ACF2 Option for DB2 treats the next line as a continuation of the comment even if it has the format of a control statement.