The GetMessagePutReply command

Label

Specifies the unique label of this process command. This label allows other commands to branch to this command. The label that you type here appears in the Label column on the EC Gateway Process Window.

Disable command

Disabling the command will allow temporary modification of the process statements. This allows for testing of the statements for error-free robustness. The command that has been disabled will not show in the script file (.pfs file).

Put Channel (Optional)

This Put Channel parameter specifies the queue to which the Reply will be sent. This parameter is optional and if blank, the Reply will be sent to the Return Queue specified in the header of the incoming message. Note that if a Return Queue is specified in both the Put Channel parameter and the message header, then the Put Channel Return Queue overrides the one in the message header. If both fields are blank, it is an error.

Put Data

Specifies the Message variable or memory in which the Reply data will be found.

Get Channel

Name of the channel on which you want to receive a Request message.

Get Data

Specifies in which Message, Memory, or Filename the input message will be placed after being read from the queue.

Overwrite/Append

Overwrite or append the earlier response.

Time Out (ms)

Specifies the number of milliseconds the GetMessage command should wait for a message before returning a timeout. This quantity may be specified in the Count variable or Constant. On Time Out condition, an error is written to the log file and the status returned indicates an error.

Process Mode

Choose either Asynchronous or Synchronous. Choose Asynchronous for handling multiple messages simultaneously by creating a child wsproces, in a separate thread to handle the development and queuing of the response. Choose Synchronous for handling messages one at a time developing and queuing the response without starting a child process.

End Label

This label marks the last line +1 of the script-fragment that builds the reply to the input message. When the End Label is reached, the Reply found in Put Data, is written out. For example:

GetMessagePutReply
...

...                (Build the Reply and store in Put                    Data by additional commands (such as RunMapIN,                    RunMapOUT, PutMessageGetReply) …

End Label: Comment (At this point the Reply is expected to be                    in Put Data and will be written to the Put Channel.)

Note that asynchronous mode just executes the GetMessagePutReply section. Synchronous mode executes both the GetMesasgePutReply and End Label sections. If you are in Asynchronous mode, the command at the end is not executed by the child wsproces and is executed by the parent wsproces. When a child or parent process sees the end label, a Put Data is written to the Put Channel. If Synchronous, the End Label can be an If-Then-Else statement that checks to see if the response was put on the Put Channel.

All code needed for building the reply should be physically between the GetMessagePutReply command and the End Label as in the above example.