A fix is available
APAR status
Closed as program error.
Error description
User tried to copy non-VSAM dataset from the File Manager panel 3.3 (Copy Utility), but the FM first reported the IEC020I 001-4 message,(ERROR1) and then the TSO session seems to be hang after customer continue to allocate the data set. The TSO user himself cannot do anything because the session seems to be hang, and the z/OS system is quite slow during this "hang" period (ERROR2). . When IAM is present on a system, File Manager always allocates IAMPRINT DD to a temporary dataset. It then issues a LISTCAT which would populate this IAMPRINT dataset IF the dataset was an IAM dataset. In this case the temporary dataset is empty (because the input dataset is a PDS) and because the dataset is allocated on a non-SMS volume File Manager issues a GET which in ERROR1 issued an ABEND001-4 and in ERROR2 finds some records and continues on the invalid assumption that it is an IAM dataset. This problem is not seen on SMS managed volumes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: File Manager users with IAM data sets. * **************************************************************** * PROBLEM DESCRIPTION: MSGIEC020I 001-4 is produced when * * running data set copy option 3.3 for * * File Manager. * * * **************************************************************** * RECOMMENDATION: Apply the provided PTF * **************************************************************** IAMPRINT work file is allocated but not necessarily initialized before File Manager reads it. This problem occurs when the work file is allocated on a non SMS managed volume.
Problem conclusion
File Manager has been changed to ensure the IAMPRINT work file is properly initialized before it is read.
Temporary fix
Comments
APAR Information
APAR number
PM09608
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-03-11
Closed date
2010-06-09
Last modified date
2010-07-02
APAR is sysrouted FROM one or more of the following:
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 UK57733
UP10/06/16 P F006
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 July 2010