The methods in this section are deprecated and have been retained for use by existing, legacy applications. New applications should use \RPCManager\Send() which subsumes all the functionality provided by these legacy methods.
RPC
Executes the specified RPC on a named workstation, i.e. a directed RPC.
\RPCManager\RPC(MachineName, ModuleName, ModuleContext, [UpdateObject, Parameters])
MachineName The IP or name of the workstation to be used for a directed RPC. Invalid for service RPCs.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
ModuleContext The context in which the "ModuleName" will be executed. The "base" context for a VTS layer-based application is \Code. For a non-VTS (pure script) application, the base context is \System. Must be valid.
UpdateObject If valid, is an object that will act as a holding point for the RPC until it is actually transmitted to the remote workstation. A subsequent RPC with the same UpdateObject value will discard the previous RPC, if it has not yet been transmitted and replace it with the new one. This is of most use to services whose updates completely negate the effect of previous updates and serves to minimize the transmission of redundant RPCs.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
SendClients
Broadcasts an RPC to all instances of the specified service that are clients of the originating workstation.
\RPCManager\SendClients(Service, ModuleName, ModuleContext, [UpdateObject, Parameters])
Service Name of the service to transmit this to.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
ModuleContext The context in which the "ModuleName" will be executed. The "base" context for a VTS layer-based application is \Code. For a non-VTS (pure script) application, the base context is \System. Must be valid.
UpdateObject If valid, is an object that will act as a holding point for the RPC until it is actually transmitted to the remote workstation. A subsequent RPC with the same UpdateObject value will discard the previous RPC, if it has not yet been transmitted and replace it with the new one. This is of most use to services whose updates completely negate the effect of previous updates and serves to minimize the transmission of redundant RPCs.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
SendAll
Broadcasts an RPC to all instances of the specified service that are clients of the originating workstation and, recursively, to all clients of the receiving workstations.
\RPCManager\SendAll(Service, ModuleName, ModuleContext, [UpdateObject, Parameters])
Service Name of the service to transmit this to.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
ModuleContext The context in which the "ModuleName" will be executed. The "base" context for a VTS layer-based application is \Code. For a non-VTS (pure script) application, the base context is \System. Must be valid.
UpdateObject If valid, is an object that will act as a holding point for the RPC until it is actually transmitted to the remote workstation. A subsequent RPC with the same UpdateObject value will discard the previous RPC, if it has not yet been transmitted and replace it with the new one. This is of most use to services whose updates completely negate the effect of previous updates and serves to minimize the transmission of redundant RPCs.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
Broadcast
Broadcasts an RPC to all instances of the specified service that are clients of the originating workstation. Same as SendClients, except that the UpdateObj parameter is replaced with a mode limit, specifying a synchronization mode cut-off.
\RPCManager\Broadcast(Service, ModuleName, ModuleContext, ModeLimit, Parameters]);
Service Name of the service to transmit this to.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
ModuleContext The context in which the "ModuleName" will be executed. The "base" context for a VTS layer-based application is \Code. For a non-VTS (pure script) application, the base context is \System. Must be valid.
ModeLimit The service synchronization mode above which this message should not be sent. Normal RPCs should set this to RPC_ACCEPT_ALL mode.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
RPCExecute
Executes the specified RPC on a named workstation, i.e. a directed RPC. Identical to \RPCManager\RPC().
\RPCManager\RPCExecute(MachineName, ModuleName, ModuleContext, [UpdateObject, Parameters])
MachineName The IP or name of the workstation to be used for a directed RPC. Invalid for service RPCs.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
ModuleContext The context in which the "ModuleName" will be executed. The "base" context for a VTS layer-based application is \Code. For a non-VTS (pure script) application, the base context is \System. Must be valid.
UpdateObject If valid, is an object that will act as a holding point for the RPC until it is actually transmitted to the remote workstation. A subsequent RPC with the same UpdateObject value will discard the previous RPC, if it has not yet been transmitted and replace it with the new one. This is of most use to services whose updates completely negate the effect of previous updates and serves to minimize the transmission of redundant RPCs.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
RPCExecuteServer
Executes an RPC on the server instance of the local workstation, of the specified service. If the server of the originating workstation has a server for the service, the RPC is propagated, recursively, to its server.
\RPCManager\RPCExecuteServer(Service, ModuleName, [UpdateObject, Parameters])
Service Name of the service to transmit this to.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
UpdateObject If valid, is an object that will act as a holding point for the RPC until it is actually transmitted to the remote workstation. A subsequent RPC with the same UpdateObject value will discard the previous RPC, if it has not yet been transmitted and replace it with the new one. This is of most use to services whose updates completely negate the effect of previous updates and serves to minimize the transmission of redundant RPCs.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.
RPCExecuteAll
Executes an RPC on the server instance of the local workstation (recursively, like \RPCManager\RPCExecuteServer()) and all clients of that server instance, for the specified service.
\RPCManager\RPCExecuteAll(Service, ModuleName, [Parameters])
Service Name of the service to transmit this to.
ModuleName The textual name of the RPC subroutine to be executed. Must be valid.
Parameters A set of up to 32 parameters to the RPC subroutine. Can be any mixture of the legal types. Supplying a parameter of an illegal type will cause it to be replaced with Invalid, when the RPC subroutine is invoked.