Bulk Data Movement Guide

10.5.4
- 10.5.6
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Downloading z/OS Files for Reading on Linux, UNIX, or Windows

To move bulk data from a sequential file on z/OS to a relational table on Linux, UNIX, and Windows, Informatica recommends that you create a workflow that reads the sequential file directly from z/OS and offloads the CPU-intensive mapping of fields to relational columns by specifying the

Filter After

connection attribute.

This processing style avoids the disadvantages of downloading files to Linux, UNIX, or Windows. These disadvantages include scheduling the downloads; the cost of the disk space on Linux, UNIX, or Windows; security issues during the network transfer; and FTP and mapping issues.

However, in certain situations it might be useful to download z/OS files to Linux, UNIX or Windows machines. You might want to download z/OS files in the following scenarios:

You already have file transfers as part of the scheduled production jobs.

The source z/OS system is not accessible from the Integration Service machine. For example, the data comes from an external site.

In certain mapping and testing situations, you might need to download the z/OS file to Linux, UNIX, or Windows.

The following download types are available:

FTP in ASCII mode

FTP in BINARY mode for fixed-length records

FTP in BINARY mode for variable-length records

FTP in ASCII Mode

You can use this download type if the following conditions apply:

The z/OS file contains display fields only. Display fields include CHAR, VARCHAR, NUMCHAR, and UZONED fields.

Character fields are converted correctly from EBCDIC to ASCII. Typically, character fields are converted correctly when character data is all single byte and the default FTP code pages are suitable.

In most cases, you can specify the

Default

record format to open a file that was downloaded in ASCII mode. The system determines the record lengths using the record delimiter character or characters.

FTP in BINARY Mode for Fixed-Length Records

When you perform the download, include the following FTP commands and keywords:

FTP

BINARY keyword to switch from ASCII to binary mode

GET or PUT keyword to transfer the file

When you define the data map, set the following properties:

Set the record format to

Fixed

and specify the size of each record.

Set

Encoding

to EBCDIC so that numeric fields are processed correctly. This is particularly required on low-ended Linux or Windows machines.

Set

Code Page

to the required z/OS code page, such as IBM-037.

FTP in BINARY Mode for Variable-Length Records

When you perform the download, include the following FTP commands and keywords:

FTP.

BINARY keyword to switch from ASCII to binary mode.

QUOTE SITE RDW so that the z/OS FTP system sends the record length prefix prior to the data in each record. This method works only with variable length files such as RECFM=VB.

GET or PUT keyword to transfer the file.

When you define the data map, set the following properties:

In the data map properties, set the record format to

Variable

and specify the variable type as

VBP2

Set

Encoding

to EBCDIC so that numeric fields are processed correctly. In particular, this setting is required on little-endian Linux or Windows machines, and it affects the record length prefix numbers.

Set

Code Page

to the required z/OS code page, such as IBM-037.

Data Map Properties of Sequential Files

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal