To Execute this Example
Before executing this example please refer to Setting Up Your JSM Environment.
If you are working inside the LANSA development environment, execute process SET_219.
If you are working outside the LANSA development environment, use the LANSA command LANSA REQUEST(RUN) PROCESS(SET_219) PARTITION(<ppp>) where <ppp> is the identifier of the partition into which the SET collection has been installed.
From the SET_219 process menu you may execute any of these RDML functions:
Note: You do not necessarily need two iSeries systems to execute this demonstration. If the host URL you specify for the remote iSeries host system is the same as your client iSeries system then the examples will execute with the client (ie: Caller) and server (ie: Called) portions executing on the same iSeries system.
Using the JSM for Remote Procedure Calls between iSeries Systems | The Things that Make Up this Example |
Before executing this example please refer to Setting Up Your JSM Environment.
If you are working inside the LANSA development environment, execute process SET_219.
If you are working outside the LANSA development environment, use the LANSA command LANSA REQUEST(RUN) PROCESS(SET_219) PARTITION(<ppp>) where <ppp> is the identifier of the partition into which the SET collection has been installed.
From the SET_219 process menu you may execute any of these RDML functions:
Function | Title Shown on Process Menu |
SET219A | Caller Example -> Calculator |
SET219C | Caller Example -> Display Employee |
SET219E | Caller Example -> Employee List |
SET219G | Caller Example -> Execute OS/400 Command |
Note: You do not necessarily need two iSeries systems to execute this demonstration. If the host URL you specify for the remote iSeries host system is the same as your client iSeries system then the examples will execute with the client (ie: Caller) and server (ie: Called) portions executing on the same iSeries system.