RSC/MP 7.2 Programming Manual

Application Development

HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004

6-2

Visual Basic .NET Applications Considerations

When developing Visual Basic .NET (VB.NET) application programs, consider these

factors:

•

RSC/MP provides a declaration file for VB.NET developers, RSC.VB.

•

VB.NET does not permit asynchronous notification; therefore, you cannot use the

RscNotifyWin, RscNotifySem or RscNotifyThread functions.

•

A VB.NET executable requires the .NET Framework in order to run. When

deploying an executable on a workstation that does not have the VB.NET

development environment, make sure the .NET Framework is installed on the

workstation.

COBOL Applications Considerations

When developing COBOL application programs, consider these factors:

•

Converting the C function names into COBOL; for example, the RscConnect

function is RSCCON in COBOL. See Appendix E, Function Cross-Reference.

•

The COBOL compiler requires an underscore in front of a C language API function

call; for example, _RSCCON.

•

Determining the data types of parameters; for example, an unsigned integer equals

PIC 9(4) COMP. See Appendix B, Language Conversion for RSC/MP Function

Calls.

•

Verifying the syntax for passing C parameters; for example, the C parameter

*name is equal to the COBOL parameter BY REFERENCE. See Appendix B,

Language Conversion for RSC/MP Function Calls.

•

Using blank-padded strings in place of NULL-terminated strings in API function

calls.

•

A COBOL header file is not included with RSC/MP. To write your own header file,

convert the header code of the RSC.H file from C into COBOL.