RSC/MP 7.2 Programming Manual

Application Development
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
6-4
Upgrading NonStop Applications Written in SCREEN
COBOL
Upgrading NonStop Applications Written in
SCREEN COBOL
To upgrade an existing NonStop application to an RSC/MP application, you must
convert screens written in SCREEN COBOL to PC COBOL or to Windows screens.
With RSC/MP, the user interface on PC workstations can communicate directly with
Pathway servers (the Pathway server does not need any changes) or servers other
than Pathway. SCREEN COBOL screens can communicate only with Pathway servers.
Building an Application
The RSC/MP API is provided through a header file for compiling and a library for
linking and execution. The rsctest.c and rsctest.mak files delivered with RSC/MP
provide an example of using the RSC/MP API.
RSC/MP Header File
The RSC/MP header file for applications written in C is RSC.H. It contains:
•
Prototypes for API functions
•
Defines for use with RSC/MP API calls
•
Defines for API errors
•
UMS and ACS structure definitions
The header file is further discussed in RSC.H Header File on page 2-3.
Windows
On Windows, these preprocessor symbols must be defined before RSC.H is included:
RSC_USE_32BIT_MODEL
_WIN32 (defined automatically by Microsoft Visual C++)
UNIX
On UNIX, this preprocessor symbol must be defined before RSC.H is included:
RSC_USE_32BIT_MODEL
Linking the RSC/MP Libraries
The RSC/MP API is released as a library that has specific names and conventions.
These conventions are discussed in the following subsections.