GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-14
Steps for Coding New Applications and Conversion
procedure supports communication between any two user tasks. The procedures
supported are:
In order to be consistent with TSCODE, when doing intertask communication,
USCODE should use these procedures rather than another means. For further
information on these procedures see Section 8, “Service Routines.”
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” 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” in Section 3.
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-40.
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
GET^ITC^FCB SEND^ITC^MSG[X]
ITC^OPENX WAIT^EVENT
^LISTEN WAKE^TASK
NOTIFY^IO^COMPLETION WRITE^ITC^MESSAGE[X]