Created On: 12 October 2011
Problem:
Does Mainframe Express support channels and containers (to overcome the 32k Commarea limitation in CICS)?
Resolution:
In order to provide channel and container support in Mainframe Express (MFE), it is necessary to upgrade to MFE3.1 and apply WebSync5 or greater. This then provides commands such as EXEC CICS ASSIGN CHANNEL so that the following code could be used for example:
01 CUR-CHANNEL PIC X(16).
MOVE 'Channel_data' TO CUR-CHANNEL.
EXEC CICS ASSIGN CHANNEL(CUR-CHANNEL)
END-EXEC.
Also EXEC CICS PUT and EXEC CICS GET will work with channels and containers.
The following new features are available in WrapPack 5. Support is now provided for Channels and Containers.
The supported API is:
ASSIGN CHANNEL
DELETE CONTAINER (CHANNEL)
ENDBROWSE CONTAINER
GET CONTAINER (CHANNEL)
GETNEXT CONTAINER
LINK CHANNEL
MOVE CONTAINER (CHANNEL)
PUT CONTAINER (CHANNEL)
RETURN CHANNEL
START CHANNEL
STARTBROWSE CONTAINER
XCTL CHANNEL
The following restrictions apply:
The FROMCCSID and INTOCCSID options are not currently supported, but will be made available in a future release. There is a limitation of 32K for a channel when using the inter-systems communication (ISC) LINK command. This limitation will be lifted in a future release. There is no DFHROUTE channel in this implementation.
01 CUR-CHANNEL PIC X(16).
MOVE 'Channel_data' TO CUR-CHANNEL.
EXEC CICS ASSIGN CHANNEL(CUR-CHANNEL)
END-EXEC.
Also EXEC CICS PUT and EXEC CICS GET will work with channels and containers.
The following new features are available in WrapPack 5. Support is now provided for Channels and Containers.
The supported API is:
ASSIGN CHANNEL
DELETE CONTAINER (CHANNEL)
ENDBROWSE CONTAINER
GET CONTAINER (CHANNEL)
GETNEXT CONTAINER
LINK CHANNEL
MOVE CONTAINER (CHANNEL)
PUT CONTAINER (CHANNEL)
RETURN CHANNEL
START CHANNEL
STARTBROWSE CONTAINER
XCTL CHANNEL
The following restrictions apply:
The FROMCCSID and INTOCCSID options are not currently supported, but will be made available in a future release. There is a limitation of 32K for a channel when using the inter-systems communication (ISC) LINK command. This limitation will be lifted in a future release. There is no DFHROUTE channel in this implementation.
Incidents #2540013, #1062363, #2190124
Old KB# 34909
#MFDS
#EnterpriseDeveloper