Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Using the TIBCO Service Gateway for IMS TM : Input Message Segment Overview

Input Message Segment Overview
Message Segment Types
The TIBCO Object Service Broker IMS TM client style determines the number and format of message segments sent to the session. Only conversational clients use a Scratch Pad Area (SPA) designated as segment 0. Only non-seamless clients use a session parameter string designated as segment 1. All clients have a data segment.
Scratch Pad Area (SPA)
IMS TM uses the first eight bytes of the SPA for the trancode. Your application can use the remainder of the SPA (up to the maximum available SPA size) to pass data to a conversational IMS TM client program.
$GETENVCOMMAREA(0) returns the SPA (including the trancode) if it exists.
Session Parameter String Segment
The session parameter string is the first message segment for non-seamless ( S6BIMxx2) TIBCO Object Service Broker IMS TM client programs. You can use this segment to pass data by specifying values to the rule in the RULE session parameter. $GETENVCOMMAREA(1) returns this segment for non-seamless IMS TM clients (if non-conversational, the session parameter string follows the trancode in the first eight bytes).
Data Segment
For seamless clients, data supplied by MFS or through program-to-program switching is in segment 1. $GETENVCOMMAREA(1) returns the data segment. If non-conversational, the data segment includes the trancode in the first eight bytes.
For non-seamless clients, data supplied by MFS or through program-to-program switching is in segment 2. $GETENVCOMMAREA(2) returns the data segment.
S6BIMxC1 Client Program Input Message Format
The S6BIMxC1 client programs are seamless and conversational as shown in the following table:

1
The SPA is segment 0, in the cases where it exists.

2
Segment 1 can contain either user data (seamless interface) or the session parameter string (non-seamless interface).

Input Message Format for S6BIMSC1 and S6BIMTC1
S6BIMxC2 Client Program Input Message Format
The S6BIMxC2 client programs are non-seamless and conversational, as shown in the following table:

1
The SPA is segment 0, in the cases where it exists.

2
Segment 1 can contain either user data (seamless interface) or the session parameter string (non-seamless interface).

3
Segment 2 can contain only user data.

Input Message Format for S6BIMSC2 and S6BIMTC2
S6BIMxN1 Client Program Input Message Format
The S6BIMxN1 client programs are seamless and non-conversational, as shown in the following table:

1
The SPA is segment 0, in the cases where it exists.

2
Segment 1 can contain either user data (seamless interface) or the session parameter string (non-seamless interface).

Input Message Format for the S6BIMSN1 and S6BIMTN1
S6BIMxN2 Client Program Input Message Format
The S6BIMxN2 client programs are non-seamless and non-conversational, as shown in the following table:
Interface Program
Session parameter string

1
The SPA is segment 0, in the cases where it exists.

2
Segment 1 can contain either user data (seamless interface) or the session parameter string (non-seamless interface).

3
Segment 2 can contain only user data.

Input Message Format for S6BIMSN2 and S6BIMTN2
See Also
TIBCO Object Service Broker Shareable Tools about the tools.
TIBCO Object Service Broker Parameters about parameters.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved