GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-16
Conversion for Extended Features of D-Series
Systems
6. Run GDSX. See Running a GDSX Application on page 3-1. Ensure that
d^plus^enabled of the CONTROLFLAGS configuration parameter is set to 1.
Conversion for Extended Features of D-Series Systems
Follow these steps when converting your application to use the extended features of
the D-series systems:
1. Ensure that d^plus^enabled of the CONTROLFLAGS configuration parameter is
set to 1. There are several ways to do this. See Setting Configuration Parameters
on page 2-49.
2. Use the D-series pseudo Guardian procedures instead of the corresponding C-
series procedures. That is, instead of using C-series procedures ^CLOSE,
^DEVICEINFO2, ^OPEN, ^RECEIVEINFO, and ^NEWPROCESS, use the
corresponding D-series procedures ^FILE_CLOSE_, ^FILE_GETINFOBYNAME_,
^FILE_OPEN_, ^FILE_RECEIVEINFO_, and ^PROCESS_CREATE_. (Converting
^CLOSE procedure calls to ^FILE_CLOSE_ calls is optional, as the two
procedures are functionally equivalent.)
3. If the ^SETMYTERM procedure is used, the object name length parameter must
be supplied. If the GET^TASK^NAME or ^MYTERM procedures are called, invoke
them implicitly with an assignment statement instead of a CALL in order to obtain
the length of the object name.
4. Use D-series file names and process identifiers as required. Any process IDs and
12-word SU or LINE data structures must be changed. See the Guardian
Application Conversion Guide for detailed information.
5. Compile user code and bind with GDSX files. See “The GDSX Generation
Process” in Section 2. The UBINDHI installed subvolume file may be used to set
the HIGHPIN object file attribute.
6. Run GDSX. See Running a GDSX Application on page 3-1. You can run GDSX at
a high PIN or low PIN.
See Appendix B, USKELEX and USKELEXC Listings for USKELEXC, an example of
how to convert the USKELEX sample application to take advantage of the extended
features of the D-series systems. Wherever possible, C-series service routines in
USKELEX are replaced in USKELEXC by D-series service routines.
Data Declarations
TSCODE sources in global data declarations from the DCCBDECS, DGCBDECS, and
PEXTGDS files of the installed subvolume. These declarations define:
•
Configuration parameters
•
Control block tables
•
Memory pools