SPI Programming Manual (G06.24+, H06.03+, J06.03+)

SPI Programming in TACL
SPI Programming Manual—427506-006
8-9
#SSINIT
You can use #SSINIT only to initialize a buffer for a command or a response; it cannot
be used to initialize an event-message buffer.
TYPE 0
indicates the header type of the SPI message buffer being initialized. Type 0, a
command or response header, is the default. It is also the only header type
currently supported by TACL.
buffer-var
is the name of the variable to be initialized as an SPI buffer. This variable must be
a writable STRUCT. #SSINIT automatically passes the data length of the STRUCT
to SSINIT. The current contents of the STRUCT are lost.
ssid
is the subsystem ID of the subsystem. For requester functions, this ID identifies the
target subsystem, and the version field must identify the version of the subsystem
definitions that your requester program is using. For server functions (subsystems),
this ID must identify your server program, including its version.
command
is the command number.
type-0-option
can be any of:
CHECKSUM checksum
gives the checksum flag. If checksum is zero or if you do not supply this
option, checksum protection of the buffer is disabled; if
checksum is nonzero,
checksum protection is enabled.
MAXFIELDVERSION max-field-version
is an unsigned integer value that initializes the maximum field version field of
the buffer header. The default value is zero.
MAXRESPONSES max-resp
gives the maximum number of response records to be returned by the
subsystem in each response message. A
max-resp value of zero (the default)
specifies one response record per response, not enclosed in a list. Any positive
value specifies up to that number of response records, each enclosed in a list.
A value of -1 specifies as many response records as will fit, each enclosed in a
list.
#SSINIT [ / TYPE 0 / ] buffer-var ssid
command [ / type-0-option [ , type-0-option ]... / ]