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


Chapter 7 Using the TIBCO Service Gateway for CICS : CICS Channels and Containers in the TIBCO Object Service Broker CICS Session Environment

CICS Channels and Containers in the TIBCO Object Service Broker CICS Session Environment
You can do the following using the CICS Channel:
CICS Channel and Container Tools
TIBCO Service Gateway for CICS provides a set of tools for handling CICS Channels and containers. See the following table for the tools along with the equivalent CICS API commands.
$SHOWCHANNEL(channel_name)
EXEC CICS STARTBROWSE CONTAINER CHANNEL(name) BROWSETOKEN(data-value)
$BRCONTAINER(channel, container_list)
EXEC CICS GETNEXT CONTAINER(name) BROWSETOKEN(data-value)
EXEC CICS ENDBROWSE CONTAINER BROWSETOKEN(data-value)
EXEC CICS GET CONTAINER(name) CHANNEL(name) INTO(data-area) FLENGTH(data-area)
$GETCONTAINER(channel, container, area, length)
EXEC CICS PUT CONTAINER(name) CHANNEL(name) FROM(data-area) FLENGTH(data-area)
$PUTCONTAINER(channel, container, area, length)
EXEC CICS MOVE CONTAINER(name) AS(name) CHANNEL(name) TOCHANNEL(name)
$MOVECONTAINER(fromchannel, fromcontainer, tochannel, tocontainer)
EXEC CICS DELETE CONTAINER(name) CHANNEL(name)
$DELCONTAINER(channel, container)
$SETCHANNEL(channel_name)
EXEC CICS LINK PROGRAM(name) CHANNEL(name)
EXEC CICS RETURN TRANSID(name) CHANNEL(name)
EXEC CICS START TRANSID(name) CHANNEL(name)
EXEC CICS XCTL PROGRAM(name) CHANNEL(name)
For a detailed description of the tools, refer to the TIBCO Object Service Broker Shareable Tools manual. For general information and the rules that govern the scope of channels, see the CICS Transaction Server for z/OS CICS Application Programming Guide.
The following table describes the tasks performed by the tools.
Lists the16-character container names and displays the count of the containers associated with the channel. This tool combines the functions of the following CICS API commands:
Nominates a channel for passing to a CICS routine when called in a rule or for passing to a program or transaction through the SESSIONEND action. A blank channel name cancels any previously nominated channel.
Channel Scope
In the TIBCO Object Service Broker CICS execution environment are two session modes, as follows:
Conversational mode (CICSPSEUDOCONVERSE=N) — In this mode, the entire session is considered one program because no EXEC CICS RETURN command is issued until at the end of the session. Therefore, the Current Channel, if one exists, and the Channels created during the session are available throughout the session.
The sessions that are started through LINK or XCTL from a CICS program run in conversational mode.
Pseudo-conversational mode (CICSPSEUDOCONVERSE=Y) — In this mode, a screen display results in EXEC CICS RETURN with TRANSID and a CHANNEL option. Therefore, the Current Channel, if one exists, is passed on to the next leg of the pseudo-conversation. However, the Channels created during the session are not passed and are hence out of scope.
You can configure both modes with the Execution Environment parameter CICSPSEUDOCONVERSE=Y | N.
Predefined Container Names
Two Execution Environment parameters name the container for passing the session parameter to a TIBCO Object Service Broker session and for returning the error messages that are generated by the session, as follows:
CICSPCONTAINER — This container passes the session parameter to an Object Service Broker session for startup. The default name is PARMCONTAINER.
CICSECONTAINER — This container enables the Object Service Broker session to return error messages to the invoker of the session. The default name is HERRCONTAINER.
For details, see the TIBCO Object Service Broker Parameters manual. You can pass user data to and from the session in separate containers with names of your choice.

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