GDSX (Extended General Device Support) Manual

Extended General Device Support (GDSX) Manual—529931-001
3-1
3 Operations and Support
This section contains information about:
•
Running a GDSX application
•
Managing a GDSX application with SCF
•
Using the code and data spaces
•
Setting GDSX configuration parameters
•
Dealing with a GDSX abend
•
Interpreting console and EMS messages
Running a GDSX Application
Running a GDSX application can involve six steps:
1. Running a filter to display EMS messages. This is optional. For instructions on
writing and running a filter, see EMS Filters and GDSX on page 2-79.
2. Entering TACL ASSIGN and/or PARAM commands. The commands entered
depend on the application.
3. Entering a TACL command to SET HIGHPIN ON or OFF.
4. Running a GDSX process or several GDSX processes.
5. Running SCF. SCF is usually needed to manage the GDSX subsystem, although
in some cases SCF may not be necessary, or another management application
may be used instead.
6. Running a requester process, or several requester processes. The requester may
be a Pathway/iTS TCP.
Tutorials on running GDSX example applications are presented in Section 4,
DEVICE^HANDLER Example, Running and Managing and Section 6, LINE^HANDLER
Example, Running and Managing.
Running GDSX at a High or Low PIN
A GDSX process started with a RUN command can run at a high PIN only if all three of
the following conditions are true:
•
The process’s HIGHPIN object file attribute is set ON (as a result of settings made
at compile time or bind time).
•
Either the TACL #HIGHPIN built-in variable is ON or the HIGHPIN ON option is
specified when you run the GDSX process.
•
D^plus^enabled of the CONTROLFLAGS configuration parameter is set to 1.