A fix is available
APAR status
Closed as program error.
Error description
When transferring a file to a WebSphere MQ File Transfer Edition agent running on the z/OS platform, if the block size (BLKSIZE) dataset attribute was specified with the value zero (0) on the managed transfer request, the actual dataset BLKSIZE will be set equal to the LRECL which is inefficient. If the same dataset is allocated directly on the mainframe using TSO 3.2, the optimum system determined block size is used.
Local fix
na
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ File Transfer Edition who are performing file transfers to destination datasets on z/OS who specify a block size (BLKSIZE) attribute on the destination dataset with value zero. Platforms affected: z/OS **************************************************************** PROBLEM DESCRIPTION: When a block size of zero for a transfer destination dataset was specified, WebSphere MQ File Transfer Edition should have allowed the system to determine the optimum block size to use. However, this was being filtered by the WebSphere MQ File Transfer Edition code such that no block size value was passed to the underlying z/OS C/C++ routines. This resulted in the block size being provided by these routines to the z/OS system which typically used a low value. For example a VB dataset will get a block size of 6144.
Problem conclusion
The WebSphere MQ File Transfer Edition code has been corrected to ensure that when transferring to a file to a destination dataset, and the block size (BLKSIZE) attribute for the dataset is specified with the value zero, the destination agent will ensure that the system determined block size will be used when the dataset is allocated. This will also apply when other dataset attributes are specified but the block size is allowed to default. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.5 v7.5 7.5.0.5 v8.0 8.0.0.2 The latest available FTE maintenance can be obtained from 'Fix List for WebSphere MQ File Transfer Edition 7.0' http://www-01.ibm.com/support/docview.wss?uid=swg27015313 The latest available MQ maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
PI29633
Reported component name
WMQ FTE Z/OS
Reported component ID
5655U8000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-11-14
Closed date
2014-11-28
Last modified date
2014-11-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ FTE Z/OS
Fixed component ID
5655U8000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"704"}]
Document Information
Modified date:
16 October 2021