GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual529931-001
2-56
DEVICEINFO
Poolcheck^flag
Poolcheck^flag is used to indicate whether memory pools should be checked when
tasks are dispatched. If poolcheck^flag is set, each time a task is dispatched TSCODE
checks the buffer pool, message pool, extended buffer pool, and extended message
pool for corruption. This pool checking is in addition to that always done when the
GETLOCALPOOL and GETEXTPOOL procedures are called. If corruption is detected,
GDSX stops with abend error 230 or 231. The poolcheck^flag can be set when
debugging a program and turned off during production to allow GDSX to run more
efficiently.
Debug^fatal^flag
Debug^fatal^flag is used to indicate that TSCODE is to invoke DEBUG if any fatal error
is detected.
DEVICEINFO
Because GDSX runs as a subtype 30 process, it receives DEVICEINFO (-40) system
messages when external applications call the file-system DEVICEINFO and
DEVICEINFO2 procedures. This dynamic parameter determines how TSCODE
responds to external processes issuing a DEVICEINFO or DEVICEINFO2 on the SUs
under the GDSX process. Also, when this parameter is set, SCF accepts
DEVICETYPE, DEVICESUBTYPE, and PHYSRECLEN attributes defined for SUs or
LINEs.
Regardless of the setting of DEVICEINFO, if GDSX receives a DEVICEINFO message
requesting information about the GDSX process itself, TSCODE replies with device
type 57 (for the GDSX process), subtype 0, and physical record length 132. See the
logic box diagram below.
The GDSX process name must be specified in one of these formats:
$GDSX-process-name
$GDSX-process-name.#GDS
$GDSX-process-name.#GDS.qualifier
Internal DEFINE Name CONFIG^PARAMS Name Default Value Range
support^devinfo device^info 0 (OFF) 0–1
Does the DEVICEINFO message specify the GDSX process?
Yes No