GDSX (Extended General Device Support) Manual

User Exit Descriptions
Extended General Device Support (GDSX) Manual—529931-001
9-6
PROCESS^USER^PARAMS
A PARAM message received by TSCODE contains a parameter string that is scanned
for configuration parameters. During the scan, each time TSCODE encounters a
parameter name that begins with “USERPARAM,” PROCESS^USER^PARAMS is
called with a pointer to the parameter string byte that indicates the length of the
parameter name. If “USERPARAM” is not encountered when TSCODE scans a
PARAM message, PROCESS^USER^PARAMS is not called.
See the Guardian Programmer’s Guide for more information on the structure of the
PARAM message and its parameter string.
parameter input
STRING:ref:*
is a pointer to the first byte of the string that contains the user parameter name and
value specified by the USERPARAM command. Offsets within the string are as
follows:
Considerations
•
The USER^INIT^CONFIG^PARAMS, PROCESS^ASSIGNS,
PROCESS^USER^PARAMS, and USER^VERSION user exits are called very
early in the GDSX initialization process. Buffer pools and task and file
management structures have not been initialized. Consequently, within these exits
TSCODE-supported service procedures should not be called, except for the
following:
•
During execution of PROCESS^USER^PARAMS, buffers may be allocated from
memory pools, but when this procedure is exited, the buffers are no longer
available.
PROC PROCESS^USER^PARAMS ( parameter ); ! i
Byte 0 parm-len , the length in bytes of the user
parameter name
Byte 1 for parm-len User parameter name, any character string
from 1 to 5 bytes long
Byte (parm-len+1) value-len, the length in bytes of the value
of the user parameter
Byte (parm-len +2) for value-
len
Value given to the user parameter name
BIT^MAP INIT[X]LIST
BIT^RESET INIT^SEM
BIT^SET ^SHUTDOWN
BIT^TEST ^TERMINATE