GDSX (Extended General Device Support) Manual

User Exit Descriptions
Extended General Device Support (GDSX) Manual—529931-001
9-5
PROCESS^ASSIGNS
PROCESS^ASSIGNS
This routine processes ASSIGN messages sent to GDSX at process startup time,
giving you the chance to retrieve information from external ASSIGN commands issued
from the TACL prompt. TSCODE calls this procedure once for each ASSIGN message
in effect at startup time. If there are no ASSIGN messages in effect, it is not called.
The ASSIGN message structure is presented in the Guardian Programmer’s Guide.
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.
PROC PROCESS^ASSIGNS ( message ); !
i
BIT^MAP INIT[X]LIST
BIT^RESET INIT^SEM
BIT^SET ^SHUTDOWN
BIT^TEST ^TERMINATE