RSC/MP Programming Manual

6 Application Development
This section provides information for developing RSC/MP applications, transaction
monitoring for RSC/MP, and application persistence.
Development Considerations
When developing RSC/MP applications, consider these factors:
If the application is to be written in Microsoft Visual Basic or Microsoft Visual Basic
.NET, the programming considerations that are specific to Visual Basic.
If the application is to be written in COBOL, programming considerations that are
specific to COBOL.
Data conversion and formatting for the application‘s language or for the type of
workstation running the application.
If the application was originally written in SCREEN COBOL, possible conversion to
Windows.
Compiling applications.
Linking the RSC/MP API libraries.
Designing for persistence.
These considerations are discussed in the following subsections.
Visual Basic Applications Considerations
When developing Visual Basic application programs, consider these factors:
RSC/MP provides a declaration file for Visual Basic developers, RSC.BAS.
Ordinary applications developed in Visual Basic are single-threaded; therefore,
Visual Basic applications do not need to use the RscRegisterThread and
RscUnRegisterThread functions. However, an ActiveX object that is run from a
multi-threaded environment (such as Microsoft transaction server) might need to
use these functions. Because such a component can be called by any thread from
a thread pool, code to call RscRegisterThread after any entry into the object, but
before making other RSC API calls. In this case, you can ignore the return code
RSC_ALREADY_REGISTERED.
Visual Basic does not permit asynchronous notification (therefore, yo u cannot use
the RscNotifyWin, RscNotifySem or RscNotifyThread functions).
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
6- 1