ACF2 Question on the format of $USERDATA and DATA in a rule set

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

What is the format for $USERDATA rule control card and what limitations might be in the $USERDATA that is added?
What is the format the DATA rule entry parameter USERDATA and what limitations might be in the DATA that is added?

For example, $USERDATA(MY COMMENT(FOR MY DATA)) be added, or would that cause an issue?

Would the $USERDATA need to be enclosed in apostrophes $USERDATA('MY COMMENT(FOR MY DATA)')?

Are there any rules or restrictions for how to code $USERDATA on a rule?

Also, what rules are there for entering DATA on a rule line?  Could DATA(ADDED BY ME (2020)) be added?  Would the DATA text need to put it into apostrophes?

Are there any any rules or restrictions on how to enter DATA on a rule?

 

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

$USERDATA specifies any text string specified within parentheses up to 64 characters including special characters, parentheses and apostrophes. Both $USERDATA(MY COMMENT(FOR MY DATA)) and  $USERDATA('MY COMMENT(FOR MY DATA)') will work. Apostrophes are not required. Note, if using parentheses as part of the text there must be an opening parenthesis for each closing parenthesis.

The DAta(text) on a rule entry specifies a one to 64-character comment specified within parentheses including special characters, parentheses and apostrophes that you want to store with the rule. CA ACF2 stores the comment with the rule set and displays it when you decompile the rule. Apostrophes are not required. Rule entry DATA(ADDED BY ME (2020)) will work without apostrophes. Note, if using parentheses as part of the text there must be an opening parenthesis for each closing parenthesis.