GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-15
Conversion for Extended Features of D-Series
Systems
corresponding D-series procedures ^FILE_CLOSE_, ^FILE_GETINFOBYNAME_,
^FILE_OPEN_, ^FILE_GETRECEIVEINFO_, ^PROCESS_CREATE_, and
^PROCESS_STOP_.
4. Use D-series file names and process identifiers as required. See the Guardian
Application Conversion Guide for detailed information.
5. Compile user code and bind with GDSX files. See "The GDSX Generation Process"
on page 2-39. The UBINDHI file from the installed subvolume may be used to set
the HIGHPIN object file attribute.
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”
later in this section.
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” in Section 3. You can run GDSX
at a high PIN or low PIN.
See Appendix B for USKELEXC, an example of how to convert the USKELEX
example 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.