GDSX Manual

Overview of GDSX
Extended General Device Support (GDSX) Manual–134303
1-8
Hardware and Software Requirements
transparent to USCODE, providing you with a consistent interface to facilities similar to
those of the Tandem NonStop Kernel. This layer of software allows TSCODE to keep
track of each internal I/O operation and ensures that every I/O operation is handled
correctly at completion time.
See Section 8, “Service Routines,” for descriptions of all procedures supported internally
by GDSX.
Hardware and Software Requirements
The GDSX D44.00 product runs only on the D-series NonStop Kernel operating system.
Although customized management applications may be developed to use the SPI
interface provided by GDSX, for standard external system management with the GDSX
D44.00 product you should use D30 SCP and D30 SCF. The Subsystem Control Facility
(SCF) Reference Manual describes the SCF, and the restrictions on using SCF and SCP
to manage applications in a network having C-series systems and D-series systems.
You also need ZGDSSCF, the GDSX standalone product module (not bound in with all
other subsystem modules) that interfaces with the SCF kernel. This module is
automatically installed when you install SCF and SCP.
GDSX product modules should have their file security set for network execution. For
example, the file security should be set to xxNx, where x is any valid level of security.
The read, write, and purge security attributes are not significant, except that if the
SCFLIB library is moved from $SYSTEM.SYSTEM, the GDSX product module must
allow write access for the user who issues the first command to the product module.
To allow GDSX to send event messages to the primary collector ($0), EMS is necessary.
Tools needed for USCODE development include a text editor, a TAL compiler, and the
Binder program. Tools that are helpful during USCODE development include the
PTrace trace formatter and the Inspect debugging program.
For GDSX applications requiring specific protocols, a particular controller, for example,
CP6100, may be necessary.
GDSX and Pathway/TS
The Pathway/TS transaction processing software, together with its parent product,
NonStop Transaction Services/MP (TS/MP), provides an easy-to-use, powerful, and
effective means of implementing online transaction processing (OLTP) applications.
Pathway/TS was designed to support the following terminals:
•
6510, 6520, 6530, 6540, and IBM 3270 terminals operating in block mode.
•
6510, 6520, 6530, 6540, and IBM 3270 terminals, or any other devices that the
Guardian file system recognizes as operating in conversational mode.
Caution. The pseudo procedure calls must be used instead of their Guardian file system,
Pathway/TS, or NonStop TM/MP procedure counterparts.