GDSX Manual

Overview of GDSX
Extended General Device Support (GDSX) Manual–134303
1-7
Support for Service Routines
customized or copied from an example program. The GDSX developer includes stubs,
such as those provided in the USKEL file in the installed subvolume, for all user exits
that do not provide user-defined function. After the USCODE is developed, it is bound
with TSCODE to form a runnable object file. See Section 9, “User Exit Descriptions,”
for descriptions of all user exits supported by GDSX.
Support for Service Routines
To help with the development of USCODE routines, the following service routines are
supported by TSCODE:
•
Utility procedures
•
Pseudo Guardian file system, Pathway/TS, and NonStop TM/MP procedures
By calling one of these routines, a user task transfers control to the TSCODE kernel.
TSCODE carries out the requested processing internally or passes the procedure call on
to the operating system. When TSCODE subsequently wakes up the task to resume
execution, control is returned to the task at the instruction immediately following the
procedure call.
Utility Procedures
TSCODE provides utility procedures that can be used in developing USCODE. The
following groups of procedures are available to developers. See Section 8, “Service
Routines,” for descriptions of all procedures supported internally by GDSX.
•
Bit map control
•
Break handling
•
Debugging facilities
•
Fault-tolerance facilities
•
Identifier manipulation
•
Intertask communication
•
I/O control block (IOCB) maintenance
•
List manipulation
•
Pool management
•
Semaphore control
•
Task maintenance
Pseudo Procedures
TSCODE provides you with a set of pseudo procedure calls that, with some exceptions,
have the same parameters, syntax, meaning, and resultant capabilities as their Guardian
file system, Pathway/TS, and NonStop TM/MP counterparts. They comprise a layer of
TSCODE software between USCODE and the Guardian file system that is virtually