3.2 LANSA RDML Client

The RDML BIF has been changed to support 256 byte message and command parameters.

Note: Any RPG program binding to the DCXS882X service program must still use 255 byte parameters.
RPG programs should be binding to the JSMRPGSRV service program and not the DCXS882X program. Refer to 3.1 RPG Client for RPG coding.

Five Built-In Functions are required for a LANSA RDML client to have complete interaction with the Java Service Manager services.

These Built-In Functions only allow a single connection within the same job.

3.2.1 JSM_OPEN	Open service.
3.2.2 JSM_COMMAND	Send command.
3.2.3 JSM_CLOSE	Close service.

The LANSA developer only needs to understand how to use the commands offered by JSM services.

The overall structure of the LANSA RDML functions will be the same.

The function will perform the following operations:

• OPEN connection to the Java Service Manager.

• Issue a COMMAND to LOAD the service.

• Execute COMMANDs supported by the service.

• Issue a COMMAND to UNLOAD the service

• CLOSE connection to the Java Service Manager

Overview of field and list exchange

Command		No fields	No list
Command SERVICE_EXCHANGE(*FIELD|*FIELDS)		Fields	No list
Command	#WRKLST	Fields	List
Command SERVICE_EXCHANGE(*FIELD|*FIELDS)	#WRKLST	Fields	List

 

Note 1: All function fields are sent with a list.

Note 2: Command keyword SERVICE_LIST(...) is required for working list #WRKLST.