(SYSLIB) Programming Reference Manual - Public Support Login ...

SIR$–Symbolic Input/Output Routine
Different ASCII-like CCSs often have different graphic characters associated with an
octal value, particularly for octal values of 0200 and over. Conversely, there are
cases where characters in different ASCII-like CCSs have identical graphic
representations but have different octal values. Of particular note in this case are
certain special characters in the ASCII-like ISO 646 CCSs (decimal CCS 17 through
28). For example, the small letter “c” with the cedilla diacritical mark is represented
by the octal value 0134 in ISO_646_Italy (decimal CCS 22); the octal value 0175 in
ISO_646_Spain (decimal CCS 23); and the octal value 0347 in ISO_8859_2 (decimal
CCS 36).
SIR$ character comparisons and replacements are always based on the octal values
of characters in the runstream partial line editing statement and in the source input
image, never on their graphic representation. As a result
− Old-data characters that graphically match a source input image string may result
in an unexpected SIR$ “no find.”
− Old-data characters that do not appear to match a source input image string may
result in an unexpected SIR$ “find.”
− New-data characters may not have the same graphic representation once they
are placed into the source input image.
• Runstream images in CCSs other than Fieldata, ASCII, or ASCII-like can only
represent images to be inserted into the source output following a “-n” line change
statement or images to replace source input images following a “-n,m” line change
statement.
When an updated or new symbolic element is specified on the processor call statement,
the updated or new symbolic is written to the program file. If a two-pass processor call
is made to SIR$ and an update element is not specified on the processor call statement,
the processor must provide a scratch file to hold the updated symbolic for the second
pass. GETPSF$ can be called to get the scratch file. The internal file name of the
scratch file must be in PARTBL+14,15 and PARTBL+16 must be set to zero prior to
entering SIR$.
To read from and write to an SDF file, PARTBL + 16,17 and PARTBL + 29,30 must be
set to zero.
Label Control Record
Whenever symbolic output is written by SIR$, a label control record is the first image
written. The format of the label control record created by SIR$ is the following.
0 5 6 11 12 17 18 29 30 35
0 050 01 030 CCS
1 *SDFF*
7833 1733–004 23–3