Guardian Programmer's Guide

Table Of Contents
Using the Sequential Input/Output Procedures
Guardian Programmer’s Guide 421922-014
15 - 14
Setting Up File Access
This form of the INITIALIZER call also works in TAL programs. However, because TAL
does not support the WADDR data type, you must include a declarative such as the
following in your TAL program:
DEFINE WADDR INT #;
For TNS callers, the basic INITIALIZER call has the form:
CALL INITIALIZER(CONTROL^BLOCK);
To call the INITIALIZER procedure without reading Assign or Param messages, use
the following call.
Native callers:
FLAGS := 0;
FLAGS.<11> := 1;
CALL INITIALIZER(CONTROL^BLOCK,
!passthru!,
!startupproc!,
!paramsproc!,
!assignproc!,
FLAGS,
!timelimit!,
NUM^FCBS,
FCB^ARRAY);
TNS callers:
FLAGS := 0;
FLAGS.<11> := 1;
CALL INITIALIZER(CONTROL^BLOCK,
!passthru!,
!startupproc!,
!paramsproc!,
!assignproc!,
FLAGS);
Setting bit 11 of the flags parameter to 1 inhibits reading of the Assign and Param
messages.
Setting Up File Access
The following paragraphs describe how to set up the characteristics that control access
to an SIO file. You will learn how to set the access mode, exclusion mode, record
length, file code, extent sizes, and block length.
Note. When using INITIALIZER with SIO procedures, the setting up of FCBs with the
information contained in the Startup and Assign messages is automatic. You do not need to
provide user-written procedures to process the Startup and Assign messages as you would in
a non-SIO environment (see Section 8, Communicating With a TACL Process) unless you
want to perform additional processing of these messages.