The messages you are showing are from a Natural RPC Server trace. Thus, to call this server from Natural, you would use a CALLNAT statement and SYSRPC or DFS parameters to point your Natural (calling) environment to the appropriate Natural (server) environment…
which is at odds with what you describe when you say that the client is VB Script.
Could you give a description of the application and environments involved? I think there is some confusion as to what is the client and what is the server here?
A typical setup for a VB Script client would be:
- define a Natural subprogram to perform the work desired. Input and output from the subprogram is entirely through the PDA (parameter data area). No global variables are involved or available.
- a Natural RPC Server is established, either in batch or CICS. Typically, it is easier to set up the server in batch. A server is needed in CICS only if you are accessing CICS-specific services (for example, Natural VSAM or the application calls some CICS/COBOL routines).
- use the EntireX Natural IDL generator to obtain the PDA and create the IDL.
- use the EntireX Workbench to generate a wrapper (probably a DCOM wrapper for VB Script). Make the generated DLL available to be called from the VB Script host.
If, on the other hand, you are attempting to have a CICS/Natural program invoke a VB program on Windows, you will need to establish a server (ACI or RPC) on the Windows platform (not the mainframe). Let us know if this is what you are attempting to do and we can elaborate on some of the possible ways to solve this too.