GDSX Manual

Service Routines
Extended General Device Support (GDSX) Manual–134303
8-2
Bit Map Control
Utility procedures flagged with an asterisk (*) can be called only if TSCODE recognizes
the application as converted. All other procedures can be called by USCODE, whether
the application is converted or unconverted.
Bit Map Control
You can test TSCODE line maps (CMAP and AMAP) and define and maintain their
own bit maps by means of the following procedures:
BIT^MAP
BIT^RESET
BIT^SET
BIT^TEST
Break Handling
The following procedures are used by a task to take and release break ownership of the
device that the task controls. The break-handling facility is enabled by means of the
BREAKENABLED configuration parameter.
GIVEBREAK
TAKEBREAK
Debugging Facilities
As an aid to debugging, TSCODE supports the trace facility and the FAULT procedure,
by which a task can report a fault and suspend itself.
ADD^TRACE^DATA USER^CLOSE^TRACE^FILE
ADD^TRACE^DATA^INT USER^OPEN^TRACE^FILE
FAULT
Fault-Tolerance Facilities
If a backup CPU is specified when the GDSX process is started, persistent operation is
possible without checkpointing by USCODE. In this case, after a switchover TSCODE
starts the backup process, checkpoints TSCODE global data, and restarts from the
beginning each task that was active at the time of the failure. The following facilities are
also supported by TSCODE to allow you to checkpoint user-defined globals, stack
images, and dynamically allocated memory to the backup process:
^CHECKPOINT GIVE^CPSEM
DO^CP Q^CP[X]
GET^CPSEM ^RECLAIMBUFFER
Identifier Manipulation
The following procedures manipulate process handles and extract CPU and node
information from process handles. They are called only by converted applications.
GET_PROCESS_HANDLE_FROM_NAME_
GET_PROCESS_HANDLES_CPU_