OCOPY of binary PTFS from Unix filesystem to MVS datasets with CONVERT(YES) can corrupt PTF

book

Article ID: 49808

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

If downloading binary PTFs from the CA Support site into a UNIX filesystem, corruption can occur within the PTF when using OCOPY to copy the PTF to a sequential data set or PDS member if CONVERT(YES) is specified on the OCOPY.

CONVERT(YES) specifies the default conversion table BPXFX000, which is an alias that points to BPXFX111, to convert the data. BPXFX111 specifies a conversion table to convert between code pages IBM-037 and IBM-1047.

Their will be no outward symptoms of a problem. The corruption would not be easily identified. The only indication would be a problem when the bad code is executed.

Solution:

Do not specify CONVERT(YES) or any conversion values on the OCOPY command.

Environment

Release:
Component: CCS390