ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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 Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ecoMeter Server Component FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA On Demand Portal CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware 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