Pathway/iTS TCP and Terminal Programming Guide

Introduction to TCP and Terminal Application
Programming
Compaq NonStop™ Pathway/iTS TCP and Terminal Programming Guide—426751-001
1-11
Development Tools and Utilities
Development Tools and Utilities
When you are writing requester and server programs for your Pathway application, a
variety of program development tools and utilities are available to you. These tools and
utilities allow you to shorten the amount of time it takes to code, debug, and test your
programs.
Programming Languages and Related Tools
You can write application programs for the TNS environment on NonStop™ Himalaya
systems in C, C++, COBOL85, SCREEN COBOL, Transaction Application Language
(TAL), FORTRAN, and Pascal. You use the Binder product to bind TNS object files for
creating executable object files.
You can write application programs for the TNS/R native environment in C, C++, and
portable Transaction Application Language (pTAL). You use the native nld utility for
linking TNS/R native object files and for creating executable object files.
For D40 and later releases, you must use the pTAL compiler and nld utility for
compiling and linking your TCP user-conversion procedures.
The Inspect Symbolic Debugger
The Compaq Inspect product is the symbolic program debugging tool for NonStop™
Himalaya systems. You can use it interactively to examine and modify the execution of
Guardian processes (for example, Pathsend requesters and Pathway servers) as well as
SCREEN COBOL requesters. An online help facility is available for all Inspect
commands and topics.
Using the Inspect product in a Pathway environment requires the use of two terminals or
a terminal emulator with windowing capability. One terminal or window acts as the
application terminal, while the second terminal or window acts as a command or Inspect
terminal.
Because SCREEN COBOL programs are interpreted by the TCP and therefore are not
running directly as Guardian processes, you use the TCP for the Inspect session. To use
the TCP for an Inspect session, you set a TCP configuration parameter to support the
Inspect product and then issue a PATHCOM command to initiate the Inspect session.
The SCREEN COBOL Utility Program (SCUP)
The SCREEN COBOL Utility Program (SCUP) provides a means for maintaining
libraries of SCREEN COBOL pseudocode. SCUP also provides a means for obtaining
information about certain aspects of the code, such as versions and compile dates and
times, data sizes, screen sizes, programs called, and code sizes.
SCUP allows you to operate on the SCREEN COBOL object library files without
recompiling the source programs. In addition, SCUP allows you to:
•
Display information about the library files or about programs in a SCREEN COBOL
library