Planning and Storage Requirements

This chapter helps you plan for SOLVE:CPT. It includes these sections:

CICS Storage Requirements for Cobol

All CICS storage is shared and allocated from above the 16M line, if possible. Storage requirements for a TCP connection or a UDP endpoint within the CICS address space are:

where xxx is either ACM for TCP connections or ADT for UDP endpoints.

Note: For TCP server applications, an additional 1080-byte overhead is required to allocate the listening token/socket. This computation accounts only for the TCP connection that is subsequently established by a listening token/socket or by the storage for a UDP endpoint.
Note: The send buffer queue is allocated only if an application calls the SEND or SENDTO services. Determining the xxxMSEND and xxxQSEND values is explained below. The receive buffer queue is allocated only if an application calls the RECEIVE or RCVFRM services. Determining the xxxMRECV and xxxQRECV values is explained below.
Note: The receive buffer queue is allocated only if an application calls the RECEIVE or RECVFROM services. For SOLVE:TCPaccess, determining the xxxMRECV and xxxQRECV values is explained below.

The maximum send and receive data sizes, the maximum send and receive buffer sizes, and the send and receive queues' sizes (maximum number of outstanding requests per endpoint) are determined initially by the TIB statement in the SOLVE:TCPaccess configuration. Read the SOLVE:TCPaccess Customization Guide for information. The TCP maximum data size default that can be sent or received is 32K. The maximum data buffer size default is 64K. SOLVE:CPT negotiates with SOLVE:TCPaccess to determine these values:

If xxxSEND is not specified,
    use the lesser of 4 or the value in DFQSEND
else
    use the lesser of the value specified in xxxQSEND or DFQSEND.
 
If xxxQRECV is not specified,
    use the lesser of 4 or the value in DFGRECV
else
    use the lesser of the value specified in xxxQRECV or DFQRECV.
 
If xxxMSEND is not specified,
    use the lesser of 4096 or the value in MXLTSND
else
    use the lesser of the value specified xxxMSEND or MXLTSND
    either of which must be less than the following computation:
        (the lesser of DFLSEND or 61440) / the final xxxQSEND value
    else
    use the quotient from this computation as the final xxxMSEND value.
 
If xxxMRECV is not specified,
    use the lesser of 4096 or the value in MXLTRCV
else
    use the lesser of the value specified in xxxMSEND or MXLTRCV
    either of which must be less than the following computation:
    (the lesser of DFLRECV or 61440) / the final xxxQRECV value
     else
    use the quotient from this computation as the final xxxMRECV value.
 

CICS Storage Requirements for Assembler

All CICS storage is shared and allocated from above the 16M line, if possible. Storage requirements for a TCP connection or a UDP endpoint within the CICS address space are:

where xxx is either ACM for TCP connections or ADT for UDP endpoints.

Note: For TCP server applications, an additional 1080-byte overhead is required to allocate the listening token/socket. This computation accounts only for the TCP connection that is subsequently established by a listening token/socket or by the storage for a UDP endpoint.
Note: The send buffer queue is allocated only if an application calls the SEND or SENDTO services. Determining the xxxMSEND and xxxQSEND values is explained below. The receive buffer queue is allocated only if an application calls the RECEIVE or RCVFRM services. Determining the xxxMRECV and xxxQRECV values is explained below.
Note: The receive buffer queue is allocated only if an application calls the RECEIVE or RECVFROM services. For SOLVE:TCPaccess, determining the xxxMRECV and xxxQRECV values is explained below.

The maximum send and receive data sizes, the maximum send and receive buffer sizes, and the send and receive queues' sizes (maximum number of outstanding requests per endpoint) are determined initially by the TIB statement in the SOLVE:TCPaccess configuration. Read the SOLVE:TCPaccess Customization Guide for information. The TCP maximum data size default that can be sent or received is 32K. The maximum data buffer size default is 64K. SOLVE:CPT negotiates with SOLVE:TCPaccess to determine these values:

If xxxSEND is not specified,
    use the lesser of 4 or the value in DFQSEND
else
    use the lesser of the value specified in xxxQSEND or DFQSEND.
 
If xxxQRECV is not specified,
    use the lesser of 4 or the value in DFGRECV
else
    use the lesser of the value specified in xxxQRECV or DFQRECV.
 
If xxxMSEND is not specified,
    use the lesser of 4096 or the value in MXLTSND
else
    use the lesser of the value specified xxxMSEND or MXLTSND
    either of which must be less than the following computation:
      (the lesser of DFLSEND or 61440) / the final xxxQSEND value
    else
    use the quotient from this computation as the final xxxMSEND value.
 
If xxxMRECV is not specified,
    use the lesser of 4096 or the value in MXLTRCV
else
    use the lesser of the value specified in xxxMSEND or MXLTRCV
    either of which must be less than the following computation:
    (the lesser of DFLRECV or 61440) / the final xxxQRECV value else
    use the quotient from this computation as the final xxxMRECV value.
 

CICS Storage Requirements for C

All CICS storage is shared and allocated from above the 16M line, if possible. Storage requirements for a TCP connection or a UDP endpoint within the CICS address space are:

where xxx is either ACM for TCP connections or ADT for UDP endpoints.

Note: For TCP server applications, an additional 1080-byte overhead is required to allocate the listening token/socket. This computation accounts only for the TCP connection that is subsequently established by a listening token/socket or by the storage for a UDP endpoint.
Note: The send buffer queue is allocated only if an application calls the SEND or SENDTO services. Determining the xxxMSEND and xxxQSEND values is explained below. The receive buffer queue is allocated only if an application calls the RECEIVE or RCVFRM services. Determining the xxxMRECV and xxxQRECV values is explained below.
Note: The receive buffer queue is allocated only if an application calls the RECEIVE or RECVFROM services. For SOLVE:TCPaccess, determining the xxxMRECV and xxxQRECV values is explained below.

The maximum send and receive data sizes, the maximum send and receive buffer sizes, and the send and receive queues' sizes (maximum number of outstanding requests per endpoint) are determined initially by the TIB statement in the SOLVE:TCPaccess configuration. Read the SOLVE:TCPaccess Customization Guide for information. The TCP maximum data size default that can be sent or received is 32K. The maximum data buffer size default is 64K. SOLVE:CPT negotiates with SOLVE:TCPaccess to determine these values:

If xxxSEND is not specified,
    use the lesser of 4 or the value in DFQSEND
else
    use the lesser of the value specified in xxxQSEND or DFQSEND.
 
If xxxQRECV is not specified,
    use the lesser of 4 or the value in DFGRECV
else
    use the lesser of the value specified in xxxQRECV or DFQRECV.
 
If xxxMSEND is not specified,
    use the lesser of 4096 or the value in MXLTSND
else
    use the lesser of the value specified xxxMSEND or MXLTSND
    either of which must be less than the following computation:
   (the lesser of DFLSEND or 61440) / the final xxxQSEND value
    else
    use the quotient from this computation as the final xxxMSEND value.
 
If xxxMRECV is not specified,
    use the lesser of 4096 or the value in MXLTRCV
else
    use the lesser of the value specified in xxxMSEND or MXLTRCV
    either of which must be less than the following computation:
     (the lesser of DFLRECV or 61440) / the final xxxQRECV value
    else
    use the quotient from this computation as the final xxxMRECV value.
 

CICS Storage Requirements for PL/I

All CICS storage is shared and allocated from above the 16M line, if possible. Storage requirements for a TCP connection or a UDP endpoint within the CICS address space are:

where xxx is either ACM for TCP connections or ADT for UDP endpoints.

Note: For TCP server applications, an additional 1080-byte overhead is required to allocate the listening token/socket. This computation accounts only for the TCP connection that is subsequently established by a listening token/socket or by the storage for a UDP endpoint.
Note: The send buffer queue is allocated only if an application calls the SEND or SENDTO services. Determining the xxxMSEND and xxxQSEND values is explained below. The receive buffer queue is allocated only if an application calls the RECEIVE or RCVFRM services. Determining the xxxMRECV and xxxQRECV values is explained below.
Note: The receive buffer queue is allocated only if an application calls the RECEIVE or RECVFROM services. For SOLVE:TCPaccess, determining the xxxMRECV and xxxQRECV values is explained below.

The maximum send and receive data sizes, the maximum send and receive buffer sizes, and the send and receive queues' sizes (maximum number of outstanding requests per endpoint) are determined initially by the TIB statement in the SOLVE:TCPaccess configuration. Read the SOLVE:TCPaccess Customization Guide for information. The TCP maximum data size default that can be sent or received is 32K. The maximum data buffer size default is 64K. SOLVE:CPT negotiates with SOLVE:TCPaccess to determine these values:

If xxxSEND is not specified,
    use the lesser of 4 or the value in DFQSEND
else
    use the lesser of the value specified in xxxQSEND or DFQSEND.
 
If xxxQRECV is not specified,
    use the lesser of 4 or the value in DFGRECV
else
    use the lesser of the value specified in xxxQRECV or DFQRECV.
 
If xxxMSEND is not specified,
    use the lesser of 4096 or the value in MXLTSND
else
    use the lesser of the value specified xxxMSEND or MXLTSND
    either of which must be less than the following computation:
    (the lesser of DFLSEND or 61440) / the final xxxQSEND value
    else
    use the quotient from this computation as the final xxxMSEND value.
 
If xxxMRECV is not specified,
    use the lesser of 4096 or the value in MXLTRCV
else
    use the lesser of the value specified in xxxMSEND or MXLTRCV
    either of which must be less than the following computation:
      (the lesser of DFLRECV or 61440) / the final xxxQRECV value
    else
    use the quotient from this computation as the final xxxMRECV value.