Compiler Directive Statements

IPSB compiler-directive statements allow you to:
idms19
IPSB compiler-directive statements allow you to:
  • Specify the amount of storage required by the IPSB compiler to compile the IPSB
  • The range of input columns in which IPSB statements can be coded
  • Sequence checking of input to the ISPB compiler
  • Formatting of reports output by the IPSB compiler
 
Syntax
 
►►─┬────────────────────────────────────────────┬────────────────────────────► └── CORe size = ─┬── (48) ◄────┬─────── k ───┘ └── (nnnnnn) ─┘ ►─┬────────────────────────────────────────────────────────────┬────────────► └─ ICTL = ──┬── (1,80) ◄───────────────────────────────────┬─┘ └─ (start-column-number,end-column-number) ───┘ ►─┬───────────────────────────────┬─────────────────────────────────────────► └─ OCTL = ─┬── (60) ◄────────┬──┘ └── (line-count) ─┘ ►─┬─────────────────────────────────────────────────────────┬───────────────► └─ ISEQ = ──── (start-column-number,end-column-number) ───┘ ►─┬───────────────────────────────┬─────────────────────────────────────────► │ ┌───────────────────────┐ │ └─▼-- SPACE space-count ──┴─────┘ ►─┬─────────────────────┬───────────────────────────────────────────────────► | ┌────────────┐ | └─▼-- EJECT ───┴──────┘ ►─┬───────────────┬─────────────────────────────────────────────────────────►◄ └─ *comments* ──┘
 
Parameters
 
  •  
    CORE 
    size=nnnnnn k
     
    Specifies the amount of storage the IPSB compiler is to acquire (by a GETMAIN under OS and a GETVIS or COMREG under z/VSE) for the IPSB being generated.
    Nnnnnn
     is a 1- to 6-digit numeric value.
    If the optional K is included, the amount of storage acquired is 
    nnnnnn
     increments of K (1,024 bytes). If K is omitted, 
    nnnnnn
     represents the actual number of bytes of storage acquired, which the compiler rounds up to the next doubleword.
    If this statement is omitted, the IPSB compiler acquires 48K of storage.
  •  
    ICTL=
    (start-column-n,end-column-n)
     
    Specifies the columns within which IPSB input statements can be coded. This compiler-directive statement, if coded, must precede the input for the five IPSB sections.
    Valid values for both 
    start-column
     and 
    end-column
     are 1 through 80.
    The default values for 
    start-column
     and 
    end-column
     are 1 and 80, respectively.
  •  
    OCTL=
    (line-count-number)
     
    Specifies the number of lines to print per page of printed output. If coded, this compiler-directive statement must precede the input for the five IPSB sections.
    The default value for 
    line-count
     is 60: acceptable values are 1 through 66.
  •  
    ISEQ=
    (start-column-number,end-column-number)
     
    Specifies that the compiler is to perform sequence checking on all input and specifies the start and end columns of the sequence number generated for each input statement.
    If coded, this statement must precede all IPSB input statements. If this statement is omitted, sequence checking is not performed.
    Valid values for 
    start-column-number
     and 
    end-column-number
     are in the range 1 through 80. The minimum allowable difference between the entry for 
    start-column
     and the entry for 
    end-column
     is 10.
  •  
    SPACE=
    space-count
     
    Directs the compiler to skip the specified number of lines on the output report. Only one blank is allowed between SPACE and the value specified for 
    space-count
    .
    Acceptable values for 
    space-count
     are 1 through 9. Several SPACE statements can appear in the compiler input.
  •  
    EJECT
    Directs the compiler to stop printing the current page and begin printing a new page. This statement must be on a line by itself and can be interspersed among IPSB input control statements (that is, EJECT statements can appear throughout compiler input).
  •  
     
    *comments*
     
    Directs the compiler to interpret subsequent characters as comments.
    Comments can be embedded in IPSB statements and are terminated automatically at the end of the input line, unless the compiler encounters a second asterisk (*) in the input line, which causes explicit termination.
    Be sure to keep track of the number of asterisks. An odd number turns on comment text; an even number turns it off.
 
Example
 
ICTL=(1,72) OCTL=(45) ISEQ=3,72 EJECT SPACE 2 *Begin comments with an asterisk
 
Figure 33. Sample compiler-directive statements