A fix is available
APAR status
Closed as program error.
Error description
After unload a PDS (RECFM=VB, LRECL=32756, BLKSZ=32760) to a sequential spanned dataset (RECFM=VS, LRECL=32760, BLKSZ=32760). Trying to view this sequential dataset using the File Manager shows up message: Incorrect spanned record segmentation, block 7, record 6 block 6 starts with: 7FF80000 7FF40100 00000000 block 7 starts with: 00160000 00120200 40404040 So block 6 carries a 1st segment, block 7 a last segment. This looks valid as described in DFSMS Using Data Sets manual.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: File Manager Base Users * **************************************************************** * PROBLEM DESCRIPTION: When reading spanned data sets that * * have a logical record length exceeding * * the record length of the file as * * allocated, * * and the data set has not been allocated * * as an LRECL=X data set, then a message * * FMNBA363 Incorrect spanned record * * segmentation, block n, record m * * occurs. * * DSP (print) and DSC (COPY) functions * * fail when the spanned record length * * exceeds 32752 with the following * * DFSORT message. * * ICE141A 2 SPANNED RECORD ON SYS00001 * * COULD NOT BE ASSEMBLED * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** File Manager's reading of spanned data sets assumes the logical record length will not exceed the defined lrecl of the data set, with the exception of LRECL=X data sets. This assumption proves to be invalid in the user case of a data set created by IEBCOPY.
Problem conclusion
File Manager has been updated in order not to check if the logical record length (being reassembled from segments) is exceeding the lrecl of the data set. File Manager will not use DFSORT when processing large spanned records.
Temporary fix
Comments
APAR Information
APAR number
PM07487
Reported component name
FILE MANAGER ZO
Reported component ID
5655V5200
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-02-15
Closed date
2010-11-25
Last modified date
2010-12-02
APAR is sysrouted FROM one or more of the following:
PM07349
APAR is sysrouted TO one or more of the following:
Modules/Macros
FMN0LVL
Fix information
Fixed component name
FILE MANAGER ZO
Fixed component ID
5655V5200
Applicable component levels
RA10 PSY UK62400
UP10/12/01 P F011
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 December 2010