The Common Format Buffer (CFB) contains the formatted information that is passed between a CA Gen client and a CA Gen server over various transports including TCP/IP, Tuxedo, and WebSphere MQ. Earlier to this release, the size of the buffer was limited to 32,768 bytes (32 KB) but could contain only 31,400 bytes of actual user data.
CA Gen 8.5 supports a maximum CFB limit 16,777,215 bytes, but is enforced as 16,775,847 bytes of actual user data.
To take advantage of these larger sizes, you have to change the view sizes appropriately, regenerate, and re-build the applications. In a similar vein, check any sizing parameters on the transports that you may use. This includes, but is not limited to, default WebSphere MQ message length, and on z/OS, user exits like TIRSIPEZ, temporary work datasets that are allocated by parameters TICASUTP and TICASUTS (found in PARMLIB members TIUHE and TIUIT).
z/OS CA Gen CICS applications, generated by CA Gen 8.x and executing CA Gen 8.5 Runtimes, use a TSQ named MMCB<APPLID>…. to handle memory management. This TSQ is automatically deleted when dialog flows are executed under the control of CA Gen but need to be manually deleted when flows are executed from EABs, particularly when using CICS XCTL or CICS START API commands.
z/OS CA Gen CICS applications, generated by CA Gen 7.6 or earlier release and executing CA Gen 8.5 Runtimes use a TSQ named AMCB<APPLID>…. to handle memory management. This TSQ is automatically deleted when dialog flows are executed under the control of CA Gen but need to be manually deleted when flows are executed from EABs, particularly when using CICS XCTL or CICS START API commands.
z/OS Servers that use TCP/IP must use the CICS Multi Sockets Server implementation for transactions with CFBs larger than 32 KB.
z/OS encryption and decryption routines have been modified to use a temporary buffer if the view data size is greater than 32K. The temporary size allocated is twice the size of the view data size, making sure that it does not exceed the max size of 16.7 MB. This temporary buffer is released as soon as the algorithm has completed processing the buffer. Messages TIRM640 and TIRM644 have been modified to indicate the user area that is used by encryption and decryption routines when that area exceeds the maximum size that is allowed, instead of 32K.
Note: PTF RO72754 corrected allocation for temporary buffer. Previously, it was always allocated at the max size of 16.7 MB which caused a performance degradation.
Current applications that conform to the 32-KB CFB does not require any changes to operate with the new runtimes.
Note: The maximum cardinality for z/OS Server Managers Import and Export views remains 9999.
Currently, applications generated entirely for Java and the .Net environment have no view size limit. The CFB Extensions on Windows, UNIX, and Linux (for TCP/IP and WebSphere MQ) have a limit of 16.7 MB.
The following CA Gen components do not allow exceeding the 32-KB limit:
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|