Specifications

4-24
Guide to Printers and Printing
Attribute Values
The following conventions have been established for attribute values:
Printer names are of the form 4201–3, reflecting the printer name ( 4201 ) and model
number ( 3 ).
File names in the Predefined Database are of the form PrinterType. DataStreamType; for
example, 4216–31.asc indicates a 4216 Model 31 printer and an ASCII data stream.
File names in the Customized Database are of the form
QueueName:QueueDeviceName, such as proq:mypro.
Attribute values can contain a \ (backslash) followed by one to three octal digits to
represent non–ASCII values. A \ (backslash) that does not begin an octal sequence
should be represented by either \\ or \134.
Characters can be represented by hexadecimal notation of the form \xXX, where XX
represents a hexadecimal value.
Boolean values can be represented by a + (plus sign) for true, and an ! (exclamation
point) for false.
Because attribute values reside in colon files, a colon character must not appear in the
attribute value. Instead, a colon should be represented by \072.
An attribute value that references an integer attribute requiring translation from a lookup
table should always appear in a colon file after the referenced integer attribute: For
example, from the string red to an equivalent integer value of 2. Integer values are
created from a colon file in the same order they are defined in the colon file. Listing the
attribute value first ensures that when the integer attribute is referenced, it has been
converted before it is referenced by the %G escape sequence.
Run all the shell commands using ksh instead of bsh.
Limits Field
The limits field in the colon file contains two types of information. SMIT dialog information
and validation information.
SMIT Dialog Information
Information used in building SMIT objects represent colon file attributes in the object data
manager (ODM). These objects will be used in the Print a File, Printer Setup, and Default
Job Characteristics dialogs.
The limits field gives you some control over the type of sm_cmd_opt ODM object that is built
for every object. You can control whether or not an attribute is always displayed, never
displayed, or displayed only if it is referenced in a pipeline. You can modify the following
fields:
id_seq_num
entry_type
cmd_to_list_mode
required
op_type
multi_select
disp_values
aix_values
values_msg_file
values_msg_set