Other session parameters
This topic lists the remaining attributes of the CONNECTION and SESSIONS resources that are of significance for CICS-to-IMS sessions.
- ATTACHSEC
- Must be specified as LOCAL.
- BUILDCHAIN(YES)
- Specifies that multiple RU chains are to be assembled before being
passed to the application program. A complete chain is passed to
the application program in response to each RECEIVE command, and the
application performs any required deblocking.
BUILDCHAIN(YES) must be specified (or allowed to default) for LUTYPE6.1 sessions.
- DATASTREAM(USER)
- Must be specified with the value USER or allowed to default.
This option is used only when CICS® is communicating with IMS™ by using the START command (asynchronous processing). CICS messages generated by the START command always cause IMS to interpret the data stream profile as input for component 1.
The data stream profile for distributed transaction processing can be specified by the application program by means of the DATASTR option of the BUILD ATTACH command.
- QUEUELIMIT(NO|0-9999)
- Specifies the maximum number of requests permitted to queue for free sessions to the remote system. Further information is given in Intersystem session queue management.
- MAXQTIME(NO|0-9999)
- Specifies the maximum time, in seconds, between the queue for sessions to the remote system becoming full (that is, reaching the limit specified on QUEUELIMIT) and the queue being purged because the remote system is unresponsive. Further information is given in Intersystem session queue management.
- RECORDFORMAT(U|VB)
- Specifies the type of chaining that CICS is to use for
transmissions on this session that are initiated by START commands (asynchronous processing). Two types of data-handling algorithms are supported between CICS and IMS:
- Chained
- Messages are sent as SNA chains. The user can use private blocking and deblocking algorithms. This format corresponds to RECORDFORMAT(U).
- Variable-length variable-blocked records (VLVB)
- Messages are sent in variable-length variable-blocked format with a halfword length field before each record. This format corresponds to RECORDFORMAT(VB).
The data stream format for distributed transaction processing can be specified by the application program by means of the RECFM option of the BUILD ATTACH command.
Additional information on these data formats is given in CICS-to-IMS applications.
- SENDCOUNT and RECEIVECOUNT
- Used to specify whether the session is a SEND session or a RECEIVE
session. A SEND session is one in which the local CICS is the secondary and is the contention winner. Specify:
- SENDCOUNT(1)
- Allow RECEIVECOUNT to default. Do not specify RECEIVECOUNT(0).
A RECEIVE session is one in which the local CICS is the primary and is the contention loser. Specify:- RECEIVECOUNT(1)
- Allow SENDCOUNT to default. Do not specify SENDCOUNT(0).
SEND sessions are recommended for all CICS-to-IMS sessions.
You need not specify a SENDPFX or a RECEIVEPFX; the name of the session is taken from the SESSNAME option.
Note: For SEND sessions, allow RECEIVECOUNT to default. For RECEIVE sessions, allow SENDCOUNT to default.
- SENDSIZE and RECEIVESIZE
- Specify the maximum z/OS® Communications
Server request unit (RU) sizes for these sessions.
- If CICS is the primary
half-session, ensure that:
- The CICS SENDSIZE is less than or equal to the value specified on the RECANY parameter of the IMS COMM macro.
- The CICS RECEIVESIZE is greater than or equal to the IMS OUTBUF size.
- If IMS is the primary half-session,
ensure that:
- The CICS SENDSIZE is greater than or equal to the IMS OUTBUF size.
- The CICS RECEIVESIZE is less than or equal to the IMS RECANY size.
- If CICS is the primary
half-session, ensure that:
| CICS | IMS |
|---|---|
| System initialization parameters |
|
|
|
| CONNECTION resource | |
|
|
| SESSIONS resources | |
|