Control Statement Language Rules

Statements are free-form. Control statements and operands need not start in a specific column. Operands can be specified in any order.
smfd
Statements are free-form. Control statements and operands need not start in a specific column. Operands can be specified in any order.
  • Each statement must end with a "." (period). This permits you to write statements that exceed one card image (80 bytes) in length. There is no special continuation indicator.
  • There must be at least one blank space between a control statement and its first operand. Also, we recommend at least one blank space between operands.
  • Operands and their values can be written with or without an intervening blanks; for example, SID(sid1) or SID (sid1).
  • Values for operands are enclosed by parentheses. When you want to specify two or more values, separate them by a "," (comma), a blank, or both. We recommend that you use either commas or blanks consistently.
  • When you are specifying a range of values, the lower and upper limits can be separated by a ":" (colon), to save coding time and space.
  • Comments are specified by placing an "*" (asterisk) in column one. Blank cards are also treated as comments.
  • CA SMF Director checks for sequence numbers only on the first control statement (in positions 73-80; 73-76 must be numeric). If sequence numbers are present in the first statement, it ignores positions 73-80 in all following statements.
  • Date fields that are entered as operands to CA SMF Director control statements can be in one of two formats, Julian (cyyddd) or Gregorian (mmddyy). Some control statements accept either format. For Gregorian date formats, the two-digit year (yy) having a value of 00 through 59 represents the year 2000 through 2059, and 60 through 99 represents the years 1960 through 1999. 'mm' represents the two-digit month (01-12) and 'dd' represents the two-digit day of the month (01-31).
    For Julian date formats, the three-digit year (cyy) having a value of 060 through 099 represents the year 1960 through 1999, and values of 100 through 141 represent the year 2000 through 2041. The three-digit day (ddd) represents the day of the year relative to the first day of the year. For example, January 28, 2008 in Julian date format would be 108028.
  • If the description of an operand indicates that an asterisk (*) is an acceptable value, you can use the asterisk to copy the value that is specified at a higher level. For example, on the OPTIONS statement.
Two special expiration dates are supported:
099000 indicates that the data set does not expire as long as it remains in the system catalog.
099366 indicates that the data set never expire.