GDSX Manual

User Exit Descriptions
Extended General Device Support (GDSX) Manual–134303
9-5
PROCESS^USER^PARAMS
message input
INT:ref
is a pointer to the ASSIGN system message.
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:
Wait until USER^INITIALIZE to call other service routines.
•
During execution of PROCESS^ASSIGNS, buffers may be allocated from memory
pools, but when this procedure is exited, the buffers are no longer available.
•
The TSCODE-supported FAULT procedure cannot be called from this exit because
the monitor task, which handles the EMS messages, does not exist when
PROCESS^ASSIGNS is executing.
PROCESS^USER^PARAMS
This routine allows you to process the PARAM message sent to GDSX at process
startup time, giving you the chance to retrieve information from external PARAM
commands issued at the TACL prompt. This procedure provides a way to process user-
defined parameters. PROCESS^USER^PARAMS is called once for each user parameter
that is defined.
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:*
BIT^MAP INIT[X]LIST
BIT^RESET INIT^SEM
BIT^SET ^SHUTDOWN
BIT^TEST ^TERMINATE
PROC PROCESS^USER^PARAMS ( parameter ); ! i