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

The SPI Procedures
SPI Programming Manual—427506-006
3-23
Considerations
This example illustrates the second exception:
CALL SSGETTKN (buffer, ZSPI-TKN-LEN, , , len)
Before the call, the positioning is:
current next
| |
v v
<TKN-A> <TKN-B> <TKN-C> <TKN-A>
After the call, the positioning is unchanged:
current next
| |
v v
<TKN-A> <TKN-B> <TKN-C> <TKN-A>
This example illustrates the third exception:
CALL SSGETTKN (buffer, ZSPI-TKN-LEN, TKN-A, , len)
Before the call, the positioning is:
current next
| |
v v
<TKN-A> <TKN-B> <TKN-C> <TKN-A>
However, after the call, the positioning is:
current + next
|
v
<TKN-A> <TKN-B> <TKN-C> <TKN-A>
A position (ZSPI-TKN-POSITION), a token address (ZSPI-TKN-ADDR), or a token
offset (ZSPI-TKN-OFFSET) returned by SSGET remains valid until a token is
deleted using the SSPUT operations ZSPI-TKN-DELETE or ZSPI-TKN-DATA-
FLUSH or until a call to SSMOVE replaces a token in the buffer. If the contents of
the buffer are copied to another buffer with SSMOVE, the position, address, or
offset is still valid when used with the original buffer, but is not valid for use with the
target buffer of the SSMOVE.