GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-15
Steps for Coding New Applications and Conversion
Steps for Coding New Applications and
Conversion
Whether you are developing new applications or converting an existing application, this
subsection describes the sequence of steps involved in (1) coding a new GDSX D44
application and (2) converting a GDSX D44 application to use extended D-series
features.
You can migrate an existing Basic GDS or GDSX C30 application to GDSX D10
without converting it to use the extended features of the D-series system. If you wish
to do this, follow the instructions in “Migrating From Basic GDS” or “Migrating From
GDSX C30” in the GDSX D10.00+ manual. If you have an existing Basic GDS or
GDSX C30 application and wish to use extended D-series features, first migrate the
application to GDSX D10 without converting to use extended D-series features (using
the instructions in “Migrating From Basic GDS” or “Migrating From GDSX C30” in the
GDSX D10.00+ manual), and then convert to use the D-series features as desired,
using the instructions in Conversion for Extended Features of D-Series Systems on
page 2-16 later in this section.
If you want to use the USAMPLE code without modification, then (1) use the OGDS
object file in the installed subvolume and (2) run GDSX. You can configure OGDS as
either converted or unconverted. See Running a GDSX Application on page 3-1.
Coding New Applications
Follow these steps when coding new applications:
1. Start by modifying GDSX example programs USKELEX, USKELEXC, or
USAMPLE on the installed subvolume. You can also begin with USKEL, the
skeleton file supplied in the installed subvolume. See The User Source File on
page 2-42.
2. See Data Declarations on page 2-16 for information on sourcing in definitions and
declarations.
3. Code as desired, creating a converted application that uses 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, ^NEWPROCESS, and STOP (not a pseudo procedure), use the
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-40. The UBINDHI file from the installed subvolume may be used to set
the HIGHPIN object file attribute.