EasyManua.ls Logo

Oce PRISMAproduction - Control Statement Format and Parameter Syntax for Files SPSPRINT; Setupxxx; Msgsuxxx; Lscoxxxx

Oce PRISMAproduction
139 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Installation and Customization
U20944-J-Z247-6-7600
Figure 11: SPSPARM library members
Control Statement Format and Parameter Syntax for files SPSPRINT / SETUPxxx / MSGSUxxx /
LSCOxxxx
Each member is a collection of one or more control statements related to a printer or form.
Each control statement contains one or more parameters defining some facet of the
processing. A control statement is coded in positions 1-71 of the records in the parameter
members with any non-blank character in 72 indicating continuation to the next record. A
control statement may be a maximum of 10 records long (9 continuation records). Blank
lines may appear anywhere between the control statements. Comments may be placed
anywhere on or between the control statements except in the middle of a key word
parameter. This includes starting on one record of a control statement and ending on any
following record in the control statement. A comment on a control statement without
parameters is valid and is processed as a null control statement. Comments are
introduced by '/*' and terminated with '*/'. The only restriction on the contents of a
comment is that a comment terminator (*/) should not be used as text within the comment.
Please refer to Figure 8 for allowable syntax examples.
All parameters are keywords. Their general format is KEYWORD(value1,...,valuen).
Keyword values must be enclosed by parentheses. Multiple keyword values must be
separated by commas. Blanks will be taken as part of the value if present. This means
keyword parameters interrupted by a continuation to the next record must be coded
through column 71 and begin in column 1 of the next record to avoid unwanted blanks.
Keyword parameters may be coded in any order on the control statement, however the
order suggested in the parameter descriptions will help to avoid errors and simplify
maintenance.
A keyword should not be coded more than once in a member unless specifically allowed.
1 COLUMNS 72
/* This example illustrates all the rules for statements and */
/* keywords. The entire example is valid syntax from the blank */
/* line above this comment to the blank line following the end */
/* of example comment. This comment is 5 null control statements */
/* of 1 line each */
/* Statement 1 */ KEYWORD1(value1,...,valuen) /* Possible comment */C
KEYWORD2(value1,...,valuen) /* Possible comment */C
KEYWORDn(value1,...,valuen) /* Possible comment */
/* The following statement illustrates key word continuation C
situations that are allowed. This comment is 1 null control C
statement of 3 lines */

Table of Contents

Other manuals for Oce PRISMAproduction