ACBSYSIN control statements

A single control statement can be specified in the ACBSYSIN DD statement. The syntax rules are different from the syntax rules for the SYSIN control statements. If this DD statement is not present, the default values for the ACBGEN commands are used.

Subsections:

ACBSYSIN control statement example
Syntax rules
ACBGEN command

ACBSYSIN control statement example

The following figure shows an example of the ACBSYSIN control statement.

Figure 1. Examples of the ACBSYSIN control statement for the ACBGEN utility

  ACBGEN  MONITOR=(PROGRESS=(YES,250))     
                                           
  ACBGEN  TYPERUN=PREVUE                   
                                           
  ACBGEN  REPORTS=(SYSINLST=NO,PSBLIST=YES)

Syntax rules

The control statements for ACBSYSIN must adhere to the following syntax rules:

Control statement content

The statement text is contained within the first 72 positions of an 80-byte record. The last 8 bytes are ignored.
A statement consists of the following fields:
- Label (optional)
- Command code (required)
- Operands (optional)
- Comment (optional)
For example:
```
   LABEL  COMMAND  OPERAND=TEST    /* COMMENT */ 
```
A complete statement can be as long as several 80-byte records.
A control statement data set can contain any number of control statements.

Special characters

The following characters have special meaning within a control statement:

Blank
Comma
Equal sign
Parenthesis
Single quotation mark
Decimal point

Continuation characters

Continuation characters must be used if a control statement does not fit within a single input record.
A continuation character is either a plus (+) or a minus (-) sign.
A continuation character must be the last character in the input record.

Literals

A literal consists of one or more characters enclosed in single quotation marks.
A single quotation mark within a literal must be represented by two consecutive quotation marks, as in 'ISN''T'.
Literals cannot be continued from one record to the next.

Labels

A control statement can, optionally, have a label field.
The label must start in the first position of the control statement.
The label must consist of a period (.) and 1 - 7 alphanumeric characters, as in .LABEL3.
The label must be followed by one or more blanks.

Command codes

A command code consists of predefined words.
A command code must follow a label (if one is present) and must precede the operands (if any are present).
A command code must be followed by one or more blanks.

Keyword operands

A keyword operand consists of a keyword immediately followed by an equal sign. The equal sign can be followed by either a suboperand or one or more optional data values. In REPORTS=(PSBLIST=YES), for example, PSBLIST= is a suboperand of the REPORTS= keyword operand, and YES is the data value for the PSBLIST= keyword operand.
Keyword operands must be separated by a comma.
Keyword operand data values can be enclosed in parentheses or quotation marks. For example:
```
        TYPERUN=PREVUE
        TYPERUN=(PREVUE)
        TYPERUN='PREVUE' 
```

If a keyword operand has suboperands, they must be enclosed in parentheses. For example:

        REPORTS=(PSBLIST=YES)
        REPORTS=(PSBLIST=YES,SYSINLST=NO)
        MONITOR=(PROGRESS=(YES,500))

Comments

A comment must be enclosed within a /* */ pair, such as:
```
   /* THIS IS A COMMENT */
```
A comment can appear only at the end of a control statement.

ACBGEN command

An ACBGEN command can be provided to specify the parameters that the Advanced ACBGEN utility is to use during the ACBGEN process. The ACBGEN command can contain the following operands:

PAGESIZE=

A one- to three-digit number that specifies the number of lines to a page for reports. The default is 60.

REPORTS=

Valid suboperands are SYSINLST=, PSBLIST=, and LOADSTAT=. Each of these suboperands must specify YES or NO.

SYSINLST=: The SYSINLST= suboperand controls whether the BUILD and DELETE lists in the SYSIN DD data set are to be listed. If the TYPERUN=PREVUE operand is specified, this suboperand is ignored. This report might be of interest if the SYSIN data set is being generated through some automated procedure and you want to verify its content. The default is SYSINLST=YES.
PSBLIST=: The PSBLIST= suboperand controls whether you want a listing of the final list of PSBs generated. If the TYPERUN=PREVUE operand is specified, this suboperand is ignored. This list is constructed from the BUILD and DELETE lists in the SYSIN DD data set. This report might be of interest if you want to see the PSBs that were implicitly included because they refer to one of the DBDs in the BUILD list. The default is PSBLIST=NO.
LOADSTAT=: The LOADSTAT= suboperand controls whether you want to display the Load Module Mgmt Stats report. This report is included primarily to give the user some indication of why the ACBGEN process takes as long as it does. The default is LOADSTAT=NO.

TYPERUN= PREVUE

The prevue feature enables you to preview the list of PSB names that will be generated from your SYSIN control statement data set. Its use terminates the Advanced ACBGEN utility program after all SYSIN control statements have been processed, but before the block building begins. It produces the following reports:

DBD/PSB Names Specified Via SYSIN report
ACB Library Members Deleted Due to User Request report
Final PSB Build List report

This feature is useful, when a DBD is changed in the DBD library and an ACBGEN is required. A BUILD DBD=(dbdname) in the SYSIN data set causes the ACBGEN process to scan the entire ACB library for PSBs that contain references to the specified DBD. Each PSB found is added to a build list. Unless you are familiar with the DBD and its use, you might not know whether there are 10, 100, or 1000 PSBs sensitive to that DBD. Without this information, you do not know whether the ACBGEN will take 1 minute or 1 hour. The PREVUE feature enables you to see the scale of the ACBGEN before scheduling it.

If only the TYPERUN=PREVUE operand is removed, the same JCL and SYSIN data set are used to perform the actual ACBGEN.

MONITOR=

This operand enables you to monitor the progress of the ACBGEN process. This option is especially useful during long-running ACBGEN jobs. Progress is measured by the number of PSBs processed. The valid suboperand is PROGRESS=.

PROGRESS=: The PROGRESS= suboperand specifies YES or NO and how often you want to be notified. For example, MONITOR=(PROGRESS=(YES,100)) would cause a notification message to be issued each time 100 PSBs are processed. The notification message is time-stamped and sent to the MVS™ console and the JES job listing. The default is PROGRESS=NO. The frequency value can be blank or a one- to seven-digit number. If PROGRESS=(YES) is specified but the frequency is not, the frequency default is 100.