GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-5
Coding and Testing Considerations
returns file-system error 29 or 560. See Section 8 for descriptions of all these
procedures.
°
In general, if GDSX is run unconverted, only the GDSX pseudo Guardian,
Pathway/TS and NonStop TM/MP procedures that correspond to the C-series
procedures are available to USCODE (except for ^FILE_OPEN_,
^FILE_CLOSE_, and ^FILE_GETINFO_). If other calls are attempted,
TSCODE returns file-system error 29 or 560. See Section 8 for descriptions of
all these procedures.
GDSX D44 supports both C-series and D-series file name structures and C-series and
D-series-format system messages. If GDSX is run as a converted process, system
messages passed to USCODE by TSCODE are in D-series format. If GDSX is run as an
unconverted process, system messages passed to USCODE by TSCODE are in C-series
format.
GDSX D44 supports the ability of a GDSX process to create high PIN processes.
Coding and Testing Considerations
The following considerations and suggestions may be helpful when coding, compiling,
binding, and testing a GDSX application. Guidelines for running GDSX and managing
it with SCF are provided in Section 3, “Operations and Support.”
•
Before coding your application, install GDSX and run the example
DEVICE^HANDLER—see Section 4, “DEVICE^HANDLER Example, Running
and Managing,”and Section 5, “DEVICE^HANDLER Example, Design.”
•
Read about the GDSX application generation process in Section 4,
“DEVICE^HANDLER Example, Running and Managing” and later in this section.
•
See "Steps for Coding New Applications and Conversion" on page 2-14 for the tasks
necessary to code a new GDSX application and to convert an existing application to
use the extended D-series features.
•
See Section 9, “User Exit Descriptions,” for details on customizing other user exits
and providing stubs for the remaining user exits.
•
If possible, test DEVICE^HANDLER tasks by themselves, or with dummy
LINE^HANDLERs.
Coding the DEVICE^HANDLER
•
See Sections 4 and 5 of the tutorial and the USAMPLE example program for
examples. USAMPLE design is described in "USAMPLE Example Program" on
page 2-94.
•
See Section 9, “User Exit Descriptions,” for a description of the
DEVICE^HANDLER user exit.
•
See Section 8, “Service Routines,” for syntax of the utilities and pseudo procedures.
Use pseudo Guardian procedures instead of the Guardian counterparts. TSCODE
supports a set of pseudo Guardian procedures that correspond to the D-series