Data Transfer for PC400

This chapter explains file-description files and data conversions for the data transfer function. .

Data Transfer Function Overview

PC400 can transfer data between the host and workstation. The data transfer function can be invoked manually by clicking the Data Transfer icon. The Data Transfer application is automatically invoked from a 5250 session when you click Send File to Host from the Actions menu and Receive File from Host from the Actions menu. You can change this default to invoke normal file transfer functions; to do so, click Preferences -> Transfer from the Edit menu, then click the Data Transfer radio button on the property page with the General tab.

Transferring data, described in this chapter, is quite different from transferring files, which is described in File Transfer for PC400. The main differences are listed in the following table.

Table 18. Data Transfer Summary
Type of Transfer Products required on an iSeries®, eServer™ i5, or System i5® Access Method Sending and receiving unit Type of connection to an iSeries, eServer i5, or System i5
File Transfer Z and I Emulator for Windows Tools (PCT/400 see Transferring Files)
  • Transfer menu in the session window
  • EHLLAPI application that invokes File Transfer
  • DDE application that invokes File Transfer
  • Playing a macro that invokes File Transfer
  • Clicking the Send or Receive button on the tool bar
Entire file Display session
Data Transfer PC Support/400 V2R2 or V2R3, OS/400® V3R1 or later, or i5/OS™1 Data Transfer icon or File Transfer selections from Actions menu Field, record, or file in a database
  • TCP/IP
1OS/400 and i5/OS provide the host transaction program for Data Transfer.

Long Password Support

The Z and I Emulator for Windows Data Transfer utility supports 128-character case-sensitive passwords, when connecting to an iSeries, eServer i5, or System i5 host running i5/OS or OS/400, V5R1 or later. This functionality is determined by the OS/400 or i5/OS system value QPWDLVL. Refer to the iSeries Security Reference (SC41-5302) for details.

Transferring Files from an iSeries, eServer i5, or System i5 System to a Workstation

When using a workstation, you can retrieve and use data from the following file types on an iSeries, eServer i5, or System i5:

When retrieving files, you can do the following:

You can specify the following output destinations:

Transferring Files from a Workstation to an iSeries, eServer i5, or System i5

The PC->iSeries Transfer function enables the transfer of data from a workstation to an iSeries, eServer i5, or System i5 physical file. Data can be transferred to any of the following destinations:

Note:
Data cannot be transferred from a workstation file to an iSeries, eServer i5, or System i5 logical file.

Transferring Data to Existing Members in an Existing File

Note the following considerations when transferring data from a workstation to an existing iSeries, eServer i5, or System i5 member.

Transferring Data to New Members in an Existing File

You can transfer the data in a workstation file to new members in an existing iSeries, eServer i5, or System i5 file. The transfer function automatically creates these members in the specified file in the specified library. New members are created according to the file description in the existing file.

Be particularly careful when only the field subset of the iSeries, eServer i5, or System i5 file can be transferred from the iSeries, eServer i5, or System i5 to a workstation by the previous transfer request. When data is returned to the iSeries, eServer i5, or System i5, new members can receive only the subset defined in that iSeries, eServer i5, or System i5 file. Other character fields that are defined, but not transferred are filled with blanks. Numeric fields are filled with zeros or the valued specified at file creation. The date, time, and time-stamp fields use iSeries, eServer i5, or System i5 default values.

Transferring Data to New Members in a New File

By using a transfer request from a workstation to the iSeries, eServer i5, or System i5 system, you can transfer data to new members in a new iSeries, eServer i5, or System i5 file. This is one of the safest transfer methods, because data already stored in theiSeries, eServer i5, or System i5 file is not replaced with that transferred from the workstation.

There are two ways of transferring data to new members in a new iSeries, eServer i5, or System i5 file. The method used depends on the data to be transferred.

Transferring Data to an iSeries, eServer i5, or System i5 Data File and Source File

You can transfer data to the following two types of iSeries, eServer i5, or System i5 physical files.

Physical data file
The members of a physical data file can contain numeric and character data of any iSeries, eServer i5, or System i5 data type. To transfer data to a physical data file, use the workstation file-description file to define how data is stored in a workstation data file. Besides this definition, the file description of the iSeries, eServer i5, or System i5 file is required to ensure correct conversion of the data.

When data is transferred to an existing iSeries, eServer i5, or System i5 file, the file description becomes part of the iSeries, eServer i5, or System i5 file. When data is transferred to a new iSeries, eServer i5, or System i5 file, the file description is included in the iSeries, eServer i5, or System i5 field-reference file.

Physical source file
Normally, a physical source file stores no data. It contains only text or source statements, as follows:

Note the following considerations when transferring data to and from an iSeries, eServer i5, or System i5 physical source file:

Preparing for Data Transfer

The following topics describe the software products required to transfer data and the points you must understand before transferring data with PC400.

Required Software Products

To use Data Transfer, IBM® PC Support/400 (5738-PC1) must be installed on the iSeries, eServer i5, or System i5. IBM PC Support/400 is not required with OS/400 Version 3 or later, or with i5/OS.

Before using the data transfer function, run the router of PC400 or PC Support/400.

Transfer Function

You can transfer only source programs, records, and the following information:

When using a spreadsheet, for example, you might want to use inventory data to create a cost analysis report. If there is no way to copy the data into the workstation, you must print the data from the iSeries, eServer i5, or System i5 and manually type it into a workstation file. With the transfer function, however, you can access the inventory database directly, select only the data needed for the report, process the data as required, then complete the report using that data.

You can also send data from the workstation to the host system for processing by iSeries, eServer i5, or System i5application. When a remote user is authorized to access the iSeries, eServer i5, or System i5 directly, he or she can access the created cost analysis report to compare with their results.

Figure 9 outlines the joining of two files, transferring the information to the workstation, and creating a report.

Figure 9. Data Transfer Example
(Picture is a diagram of file data transferring from iSeries to workstation.)

To transfer data by using PC400, you must create a transfer request. A transfer request provides the necessary information about the data you want to transfer.

Before creating a transfer request, you must have the answers to the following questions:

When transferring data from the iSeries, eServer i5, or System i5 to a workstation, PC400 allows you to specify which data is to be transferred and whether the data is to be displayed or written to a workstation file.

In addition, a transfer request can be saved to a workstation file, allowing you to easily perform the same transfer at a later date. After a transfer request is saved, you can call the request to make changes or to run it again.

Data Transfer Program

PC400 data transfer is classified into two types, depending on the direction of the transfer:

Data transfer can also be classified according to how the program is started, as follows:

In both cases, data transfer is performed by PCSFT5.EXE on the workstation and by the PC Support/400 transfer program on the iSeries, eServer i5, or System i5.

The Data Transfer icon is registered in the PC400 folder by installing PC400. Double-clicking on this icon displays the iSeries->PC Transfer window (for receiving). This icon includes:

   \Z and I Emulator for Windows\PCSFT5.EXE

The PC->iSeries Transfer window (for sending) opens when the registered contents are changed as follows:

   \Z and I Emulator for Windows\PCSFT5.EXE

The iSeries->PC Transfer and PC->iSeries Transfer windows have a Switch to SEND button and Switch to RECEIVE button, respectively. By clicking either of these buttons, the window for sending can be switched to the window for receiving, and vice versa.

To perform automatic transfer, you must create transfer information, using the interactive screen window, and then save the information. You can then perform data transfer automatically by specifying the file name in which the data was saved.

For example, if you save transfer information to file TENSOU.TTO, contained in directory C:\Z and I Emulator for Windows\PRIVATE, run automatic transfer as follows:

"C:\Z and I Emulator for Windows\PCSFT5.EXE" "C:\Z and I Emulator for Windows\PRIVATE\TENSOU.TTO"

When you save the transfer information, register it as an icon in the PC400 folder. You can then transfer data automatically simply by double-clicking on this icon.

Data Concepts of the iSeries, eServer i5, or System i5 and Your Workstation

The basic components of data management are files, records, and fields. A file is an aggregate of records, referenced by a single name. Each record in a file contains one or more items of correlated information. Each item of information is called a field.

The iSeries, eServer i5, or System i5 and your workstation use different functions to store and group data, and to set the format.

Workstation Files

To transfer data from a workstation to the iSeries, eServer i5, or System i5, the transfer function uses a special-format workstation file, called a file-description file. Using this file, data is stored in a valid format and converted into a valid type.

A file-description file identifies the format of a workstation data file and contains a description of the fields in the data file. The file-description file also contains a name list of all the fields in the data file. This list reflects the order, as well as the names, in which each field appears within the data file. In addition, this list includes a description of the data type, length, and decimal position of each field. Using this information, the transfer function can recognize not only how data has been modified but also where a certain field exists in a file record.

When data is transferred from the iSeries, eServer i5, or System i5 to a workstation, you can use the transfer function to automatically create the file-description file. In this case, the information in the file-description file depends on the file description in the iSeries, eServer i5, or System i5 file.

You must create a file-description file with the same name as the workstation data file to transfer a workstation data file to the iSeries, eServer i5, or System i5.

Distributed Data Management (DDM) Files

Distributed data management (DDM) is one of the functions supported by iSeries, eServer i5, and System i5. This function is used to access database files that are stored on remote iSeries, eServer i5, and System i5 systems. To use the transfer function to access these database files, specify a DDM file name as the name of the iSeries, eServer i5, or System i5 file to be transferred. Refer to DDM Guide for details of how to use DDM files.

iSeries, eServer i5, or System i5 Files

The following list provides a simple explanation of the requirements for transferring data between the iSeries, eServer i5, or System i5 and a workstation.

Library
The iSeries, eServer i5, or System i5 library contains related objects that are used to generate significant groups. For example, the objects might be all the programs and files related to credit sales management. Using the library, you can group objects and find a desired file by name. The transfer function uses the library to locate an iSeries, eServer i5, or System i5 file.
File
iSeries, eServer i5, or System i5 files that you can manipulate consist of a file description and data stored in the file. PC400 processes an iSeries, eServer i5, or System i5 file, called a database file. The database file can be either a physical file or a logical file.

A physical file is a database file that contains data stored in records. It includes a description of the record format in addition to the data itself.

A logical file is a database file, that you can use to access data stored in one or more physical files. Logical files, like physical files, contain a file description. However, logical files do not contain any actual data. Instead, you can access fields in one or more physical files by using the record format included in the logical file description. When a logical file is transferred from the iSeries, eServer i5, or System i5 to a workstation, data is obtained from one or more physical files. You need only specify a logical file as the file to be transferred. The iSeries, eServer i5, or System i5 recognizes which physical file contains the actual data to be transferred.

Note:
Data cannot be transferred from a workstation to logical files.
Member
Data records in a database file are grouped into several members. At least one member must be included in one file.

When data is transferred to and from the iSeries, eServer i5, or System i5, actual data transfer is done between file members. For example, a certain workstation file can be transferred to the iSeries, eServer i5, or System i5. In this case, the file members become new members of a new or existing iSeries, eServer i5, or System i5 file, or substitute for existing members in an existing iSeries, eServer i5, or System i5 file.

Record format
A record format describes the fields contained in a file record and the order in which these fields appear in the record. Record formats are stored in the file description. Both physical and logical database files can have one or more record formats.

Creating a Workstation-to-iSeries Transfer Request

To create a request for data transfer from a workstation to the iSeries, eServer i5, or System i5, do as follows.

  1. Using the router session, establish attachment to the iSeries, eServer i5, or System i5 to which data is to be transferred.
  2. Click the Data Transfer icon.
  3. When the iSeries->PC Transfer window displays, select Switch to SEND. The display is switched to the PC->iSeries Transfer window.

    To choose additional settings, select Advanced.

  4. Specify each item. See Items to Be Specified for details.

Items to Be Specified

The following section explains the items that you specify in the PC->iSeries Transfer window.

FROM

PC file name
This item is always required. It specifies the name of the workstation file containing the data to be transferred to the iSeries, eServer i5, or System i5. Specify this item using the following format. (Items inside brackets [ ] can be omitted.)
[d:][path-name]file-name[.ext]

A list of workstation files can be displayed by selecting Browse. You can limit the number of names listed. To limit the listing, specify a combination consisting of part of a file name and a global file name character (* or ?) in the input area of the workstation file list. For example:

TO

System name
This item is always required. When the router program is active, this item specifies the default system name.
Library/File (Member)
This item is always required. It specifies the name of the iSeries, eServer i5, or System i5 physical file that will receive the data to be transferred from the workstation. You can specify either an existing file name or new file name.

Specify this item using the following format. (Items inside brackets [ ] can be omitted.)

[library-name/]file-name[(member-name[,record-format-name])]
library-name
This is the name of theiSeries, eServer i5, or System i5 library containing the iSeries, eServer i5, or System i5 file to which data is to be transferred. If no library is specified, *LIBL is used. To create a new file to receive transferred data, specify the library name.

When the input field is null and Browse is selected, the iSeries, eServer i5, or System i5 displays a list of all libraries defined in *USRLIBL of the iSeries, eServer i5, or System i5 job library list. You can modify this list by changing the job description. Run a change job description (CHGJOBD) command on the iSeries, eServer i5, or System i5.

file-name
This is the name of an iSeries, eServer i5, or System i5 physical database file. When data is transferred to an existing file, the data in that file is replaced with the transferred data. To create a new file to receive transferred data, specify a new file name of 1 to 10 characters.

To list the available files, do one of the following things:

  • To list all files within all libraries defined in *USRLIBL of the iSeries, eServer i5, or System i5 job library list, specify *USRLIBL followed by a slash (/), then select Browse. If a slash (/) is not specified after the library name, the iSeries, eServer i5, or System i5 displays a list of library names rather than the file names.
  • To list the names of the files in a certain library, specify the library name followed by a slash (/), then select Browse. You can also specify a part of a file name followed by an asterisk (*), then select Browse. The iSeries, eServer i5, or System i5 lists all the files whose names begin with the specified character string.
member-name
This is the name of a member in the specified iSeries, eServer i5, or System i5 file to which data is to be transferred. If this member name is not specified, data is transferred to the first member, *FIRST, in the iSeries, eServer i5, or System i5 file.

To transfer data to an existing file, specify the member name. The data within that file member is replaced with the transferred data.

To create a new member in an existing file or in a new file, specify a new member name of 1 to 10 characters.

By selecting Browse with a file name specified, the names of the members in that file are listed. When a left parenthesis, part of a member name, an asterisk (*), and a right parenthesis are specified, in this order, and then Browse is selected, the iSeries, eServer i5, or System i5 can list all member names beginning with the specified character string.

record-format-name
This is the name of the record format in the specified iSeries, eServer i5, or System i5 file. The record format name need not be specified except when a physical file contains more than one record format. Most physical files have only one record format. Before specifying a record format name, a member name or *FIRST must be specified as the member name.

When you transfer data to an existing file without specifying a record format name, it is assumed that the file has only one record format (*ONLY). Therefore, that record format is used.

When a new file is created with no record format name, QDFTFMT is used as the record format name.

Note:
A library name, file name, member name, and record format name can be specified using up to 10 characters each. Each name must begin with one of the following characters: A to Z, ¥, #, or @. For characters subsequent to the first, the numbers 0 to 9, underscores, and periods can also be used.

Advanced Options

The following advanced options are available for PC->iSeries Transfer.

Use of File Description File

This item specifies whether a file-description file is used to transfer data to the iSeries, eServer i5, or System i5. The file-description file is required to transfer a workstation file, containing the data to be transferred (and converted), in fields. Such a workstation file can have either several fields or numeric data fields. To transfer a workstation file containing text (character data) only, the file-description file is not required. For details on creating a file-description file, see File-Description Files.

File Description File Name

This item appears only when item Use of File Description File is specified.

This item is always required. It specifies the name of the workstation file-description file that describes the data to be transferred.

Upon transferring data from the iSeries, eServer i5, or System i5 to a workstation, a file-description file might have been created.

A file-description file must be created when the data has not yet been transferred from the iSeries, eServer i5, or System i5 to a workstation or when no file-description file exists.

PC File Type

This item appears only when Use of File Description File is not specified.

This item is always required. You must specify the type of the workstation file specified in the FROM field. The values provided by the iSeries, eServer i5, or System i5 are recognized as workstation code text. If the file type of a data file is not converted, the file can include nothing other than data that does not require conversion.

iSeries Object

This item is always required. It specifies whether the iSeries, eServer i5, or System i5 member to which data is transferred is a new member or an existing member. When data is transferred to a new member, this item also specifies whether the file to contain the new member is an existing file.

Create New Member
This item specifies that a new member, to which data is transferred, is created in an existing iSeries, eServer i5, or System i5 file.
Notes:
  1. To create a new member, you must have the following authorities:
    • *OBJOPR, *OBJMGT, and *ADD for the file that will include the new member
    • *READ and *ADD for a library that will contain the file

    See Security Descriptions (SC41-8083) for details of object authorities.

  2. To create a member to add to a file, the transfer function uses the iSeries, eServer i5, or System i5 default value for the add physical file member (ADDPFM) command.

When you specify this item, the following item must also be specified:

Member Text
This item is used to add an explanation of a new iSeries, eServer i5, or System i5 member. This explanation helps remind you of the contents of the member. This explanation appears, for example, when a list of all members in a file is requested (Browse is selected). If this item is left blank, no explanation is added to the new iSeries, eServer i5, or System i5 member.

To specify an apostrophe (') in the explanation, enter two apostrophes (' ').

Create New Member in New File
This item specifies that a new member, to which data is to be transferred, is created in a new iSeries, eServer i5, or System i5 file.
Notes:
  1. To create a new member in a new file, *READ and *ADD authorities are required for the library that will contain that file. Authority to use the create physical file (CRTPF) command of the iSeries, eServer i5, or System i5 is also required.
  2. To create a new member in a new file, the transfer function uses the default value for the create physical file (CRTPF) command of the iSeries, eServer i5, or System i5. It does not, however, use the following values:
    • (MAXMBRS[*NOMAX]). This indicates that the file can contain up to 32,767 members.
    • (SIZE[*NOMAX]). This indicates that each member of the file can contain an unlimited number of records.

When this item is specified, also specify the following item:

Member Text
This item is optional. It is used to add an explanation of a new iSeries, eServer i5, or System i5 member. This explanation helps remind you of the contents of the member. This explanation appears, for example, when a list of all the members in a file is requested (Browse is selected). If this item is left blank, no explanation is added to the new iSeries, eServer i5, or System i5 member.

To specify an apostrophe (') in the explanation, enter two apostrophes (' ').

iSeries File Type
This item is always required. It specifies the type of iSeries, eServer i5, or System i5 file and the members to be created (same type for both).

Specify one of the following things:

  • To create an iSeries, eServer i5, or System i5 physical source file and its members, specify Source. These members are created with two fields (order number and date) added to the beginning of the data transferred from the workstation file. A new iSeries, eServer i5, or System i5 source file and its members have the following record format:
    Field         Type       Length       Decimal Places
     
    Order number  Zoned         6            2
    Date          Zoned         6            0
    Data          Character   1 to 32755
                  or Open

    Note that in an iSeries, eServer i5, or System i5 physical source file, each record can be up to 32 755 bytes in length. But, the maximum size of a source file created using the workstation-to-iSeries transfer function is 4,107 bytes. Also, this file must include the order and date fields. Therefore, the maximum amount of data that can be transferred is 4,096 bytes per record.

    The data portions of members inherit the workstation file characteristics. In other words, when a workstation file is a workstation code text file consisting of many records containing text, the created data fields will be the same.

  • To create aniSeries, eServer i5, or System i5 physical data file and its members, specify Data. The file and members will contain only the data fields described in the file-description file.

The value of the iSeries File Type is assumed to be Data when a file-description file is used to transfer data. If a file-description file is not used for data transfer, the value of this item is assumed to be Source.

Field Reference File Name
This item appears only when Use of File Description File is specified for the creation of a new file.

When Use of File Description File is not specified, an iSeries, eServer i5, or System i5 physical source file is created. iSeries File Type and Field Reference File Name are not displayed. Instead, Record Length opens.

This item is always required. A new iSeries, eServer i5, or System i5 file is created using the field name in a file-description file and the field definitions in an iSeries, eServer i5, or System i5 field-reference file.

The format of a field-reference file name is as follows. (Items inside brackets [ ] can be omitted.)

[library-name/]file-name
library-name
This is the name of an iSeries, eServer i5, or System i5 library containing a field-reference file. If this library name is not specified, *LIBL is assumed. If you cannot find the desired library, selecting Browse displays a list of all libraries in *USRLIBL of the iSeries, eServer i5, or System i5 job library list. *USRLIBL of the library list can be changed by modifying the job description by executing a CHGJOBD command on the eServer i5 or iSeries processor.
file-name
This is the name of the iSeries, eServer i5, or System i5 physical database file containing the field definitions. Always specify this file name. When a library name is specified concurrently, use a slash (/) to delimit the library name and file name. If the desired file cannot be found, enter the library name and a slash, then select Browse. The system displays a list of files in that library. To list all the files in the libraries defined in *USRLIBL of theiSeries, eServer i5, or System i5 job library list, enter *USRLIBL/ then select Browse.

If you enter part of a file name followed by an asterisk (*) and then select Browse, the system displays a list of available file names, each beginning with the specified part of the name.

For example, enter ARLIB/AR* in the Field Reference File Name item, then select Browse. The system displays a list of all physical file names beginning with AR in library ARLIB.

Note:
You must have *OBJOPR authority for the field-reference file to be specified. To list certain files, you must also have *OBJOPR authority for those files.
Record Length
This item is always required. It specifies the record length of an iSeries, eServer i5, or System i5 physical source file. When the data receiver is an iSeries, eServer i5, or System i5 physical source file, the specified value must include the length of the order number and date fields that are added to a workstation file at transfer (the total length of these two fields is 12 bytes).
Authority
This item is always required. It specifies the authority level of a new iSeries, eServer i5, or System i5 file.

Specify one of the following things:

  • Read/Write. This enables other users to read from and write to the iSeries, eServer i5, or System i5 file and allows the file name to be displayed in lists. However, users cannot delete the file (*OBJOPR, *READ, *ADD, *OBJMGT, *UPD, and *DLT authorities). If other users might be transferring data from a workstation file to the iSeries, eServer i5, or System i5 file, specify Read/Write or All.
  • Read. This enables other users to read from the iSeries, eServer i5, or System i5 file, and allows the file name to be displayed in lists. However, other users can neither write to the file nor delete it (*USE authority).
  • All. This enables other users to read from and write to the iSeries, eServer i5, or System i5 file as well as delete it. The file name is displayed in lists (*ALL authority).
  • None. This prevents other users (except for the system administrator) from writing to or deleting the iSeries, eServer i5, or System i5 file. The file name does not appear in lists (*EXCLUDE authority).
File Text
This item is optional. It is used to add an explanation of a new iSeries, eServer i5, or System i5 file. This explanation helps remind the user of the contents of the file. This explanation appears, for example, when a list of all files in a library is requested (Browse is selected). If this item is left blank, no explanation is added to the new iSeries, eServer i5, or System i5 file.

To specify an apostrophe (') in the explanation, enter two apostrophes (' ').

Replace Existing Member
This item transfers data to an existing iSeries, eServer i5, or System i5 member, specified in the Library/File (Member) item. The existing data in that iSeries, eServer i5, or System i5 member is replaced with the transferred data.

Saving, Opening, Changing, and Executing a Transfer Request

The following section explains how to save, open, change, and execute, as a file, information (transfer request) on data to be transferred.

Saving a Transfer Request

Save a transfer request when the request is likely to be executed repeatedly. This eliminates the need to create a transfer request every time data is to be transferred. To save a transfer request, do as follows:

  1. Specify the information needed for transfer, using the PC->iSeries Transfer window.
  2. After specifying the necessary information, click Save or Save As from the File menu.

    The Save Transfer Request File As window opens.

  3. Specify each item, referring to the following explanation, then click OK.
    File Name
    Disk to which data is to be saved. Specify a file name or diskette file name. The default extension is TFR. Extension TFR identifies a file as a transfer request file.
    Description
    This item can be used to add an additional explanation of a transfer request, as required. The explanation can be up to 40 characters in length. This explanation is saved with the transfer request, and displayed in the list of transfer request names. It is, therefore, useful for identifying a transfer request.
  4. The system asks whether the saved transfer request is to be registered in the PC400 folder.

    When you click OK, the transfer request is registered as an icon. Subsequently selecting this icon transfers data according to the contents of the registered data transfer request.

Opening and Changing a Saved Transfer Request

To open and change a saved transfer request, do as follows:

  1. Display the PC->iSeries Transfer window.
  2. Click Open from the File menu.
  3. Specify the name of the file to be opened using the Open Transfer Request File window, then click OK.

    The PC->iSeries Transfer window reopens, and the transfer request information, saved to the specified file, appears for each item. This opens the saved transfer request.

  4. Change the contents of the transfer request as necessary.
  5. To save the changed contents, follow the procedure explained in Saving a Transfer Request.

Performing a Transfer Request

A transfer request can be performed in any of the following ways:

Clicking the Icon with Which the Transfer Request Has Been Registered

This method can be used only when a transfer request has been saved as an icon by using the PC->iSeries Transfer window.

Clicking the corresponding icon starts data transfer.

Using the PC->iSeries Transfer Window
  1. Before executing a transfer request, operations such as creating, opening, and changing a transfer request must be completed.
    Note:
    When data is transferred from a workstation to an existing member in an iSeries, eServer i5, or System i5 file, the transferred data replaces the existing data in that member.
  2. Select Send from the PC->iSeries Transfer window.

    Data transfer starts.

  3. After the transfer has been completed, click Cancel or Exit from the File menu.

Conversion Errors That Can Occur during Transfer

Upon executing a transfer request, a file-description file (when specified) is read from the disk or diskette to be processed. The iSeries, eServer i5, or System i5 and workstation exchange information, if the data is transferable.

The workstation transfers records, one at a time, from the file specified in FROM. Transferred records are converted and stored in the iSeries, eServer i5, or System i5 member specified in TO.

During this conversion process, conversion errors might occur. For example, the values in a workstation file might have to be rounded to fit the iSeries, eServer i5, or System i5 fields. Another example is the case where the record length of a workstation file differs from that expected by the iSeries, eServer i5, or System i5.

If such an error occurs, an error message is issued with the number of the workstation file record for which the error occurred and, sometimes, information about certain fields in that record.

If a severe error occurs, data transfer might stop. In such a case, stop the transfer request, correct the error, then rerun the transfer request.

When the error is not so severe, you can request that the system continue transferring data. By doing so, even if the same error occurs in another record, an error message does not appear and the transfer function automatically continues executing the transfer request.

Creating an iSeries-to-Workstation Transfer Request

To create a transfer request to receive data from the host, do as follows:

  1. Click the Data Transfer icon.
  2. When the PC->iSeries Transfer window opens, select Switch to RECEIVE to switch the display to the iSeries->PC Transfer window.

    For the additional settings, click the Advanced button.

  3. Which items are to be specified by the user vary with the data type, as follows: Before specifying each item, while referring to Items to Be Specified, note the following points regarding the data to be received.

Receiving an Entire iSeries, eServer i5, or System i5 File

This is the simplest way of transferring data from the iSeries, eServer i5, or System i5 to a workstation. All records in a file and all the data in each record are transferred.

The FROM items are as follows:

System name
This item specifies the name of the system.
Library/File (Member)
This item specifies the name of the iSeries, eServer i5, or System i5 file.
SELECT
Specifying an asterisk (*) for this item indicates that all fields are to be transferred, or lists all the fields in the iSeries, eServer i5, or System i5 file.
ORDER BY
This item is optional. It specifies how records are grouped. When this item is left blank, records are not grouped (data is transferred in the same order it appears in the iSeries, eServer i5, or System i5 file).

Receiving Part of an iSeries, eServer i5, or System i5 File

Only part of an iSeries, eServer i5, or System i5 file is transferred to the workstation.

The FROM items are as follows:

System name
This item specifies the name of the system.
Library/File (Member)
This item specifies the name of the iSeries, eServer i5, or System i5 file.
SELECT
This item specifies a field to be transferred.
WHERE
This item specifies the requirements that must be satisfied before records can be selected for transfer.
ORDER BY
This item is optional. It specifies how records are grouped. When this item is left blank, records are not grouped (data is transferred in the same order it appears in the iSeries, eServer i5, or System i5 file).

Receiving Data Combined from Several iSeries, eServer i5, or System i5 Files

The data to be transferred can be stored in two or more iSeries, eServer i5, or System i5 files. These files are assumed to be related. Based on this relationship, they can be linked or joined, as if all the data existed in a single file. The files can be transferred to the workstation after they have been joined. By using the iSeries->PC Transfer function, this "join and transfer" function can be performed in a single step.

The FROM items are as follows:

System name
This item specifies the name of the system.
Library/File (Member)
This item specifies the names of all iSeries, eServer i5, or System i5 files from which data is to be transferred.
JOIN BY
This item specifies how to join or combine the data in each file.
SELECT
This item specifies a field to be transferred.
WHERE
This item specifies the requirements that must be satisfied before records can be selected for transfer.
ORDER BY
This item is optional. It specifies how records are grouped. When this item is left blank, records are not grouped (data is transferred in the same order as it appears in the iSeries, eServer i5, or System i5 file).

Receiving a Summary of Record Groups

A summary record is a single record that includes information on each set of records grouped from one or more iSeries, eServer i5, or System i5 files.

The FROM items are as follows:

System name
This item specifies the name of the system.
Library/File (Member)
This item specifies the names of all files from which data is to be transferred.
JOIN BY
This item is optional. It specifies the join conditions that must be satisfied before records can be joined.
GROUP BY
This item is optional. It must be specified only when the records of iSeries, eServer i5, or System i5 files are classified into several groups. To group all records into a single group, this item need not be specified.
SELECT
Specifying this item creates a summary record. The field names specified in GROUP BY can be specified.
WHERE
This item is optional. It specifies the requirements that each record to be grouped must satisfy. To group all records, this item need not be specified.
HAVING
This item is optional. It specifies the summary record to be transferred. To transfer all summary records, this item need not be specified.
ORDER BY
This item is optional. It specifies how summary records will be grouped. When this item is left blank, records are not grouped (data is transferred in the same order as it appears in the iSeries, eServer i5, or System i5 file).

Items to Be Specified

The following section explains the items to be specified using the iSeries->PC Transfer window.

FROM

System name

This item specifies the name of the host system that contains the data to be received. When the router program is active, this item specifies the default system name.

Library/File (Member)

This item is always required. It specifies the name or names of one or more files used to store data to be transferred. Up to 32 file names can be specified. To specify several files, delimit them with commas and use JOIN BY, displayed after all FROM items have been specified. Only the file name must be specified. Do not specify a comma as a part of a file name. When the other optional items are not specified, they are assumed automatically. For example, the library name, member name, and format name can be assumed to be *LIBL, *FIRST, and *ONLY, respectively. When the cursor is on the input field of FROM, selecting Browse lists libraries, files, members, and formats.

Note:
To transfer data from an iSeries, eServer i5, or System i5 physical file, you must have *USE authority for that file. To transfer data from an iSeries, eServer i5, or System i5 logical file, you must have *OBJOPR authority for that file and *READ authority for each subordinate file.

Specify file names as follows. (Items inside brackets [ ] can be omitted.) To specify several file names, delimit the names with commas.

[library-name/]file-name[(member-name[,record-format-name])],
[library-name/]file-name[(member-name[,record-format-name])],...
library-name
This is the name of the iSeries, eServer i5, or System i5 library that contains the iSeries, eServer i5, or System i5 file to be transferred. This iSeries, eServer i5, or System i5 file contains the data to be transferred from the iSeries, eServer i5, or System i5 to a workstation. If this library name is not specified, *LIBL is assumed. If you cannot find the desired library, selecting Browse displays a list of all libraries defined in *USRLIBL of the iSeries, eServer i5, or System i5 job library list. *USRLIBL of the library list can be changed by modifying the job description by executing the CHGJOBD command on the iSeries, eServer i5, or System i5.
file-name
This is the name of the iSeries, eServer i5, or System i5 physical file, logical file, or DDM file from which data is transferred. This file name must always be specified. To specify a file name and library name concurrently, delimit them with a slash (/). If you cannot find the desired file name, enter the library name followed by a slash, then select Browse. The system then displays a list of files contained in that library. To display a list of all the files in the libraries defined in *USRLIBL of the iSeries, eServer i5, or System i5 job library list, enter *USRLIBL/, then select Browse.
member-name
This is the name of the iSeries, eServer i5, or System i5 member containing the data to be transferred, or *FIRST. If this member is not specified, the system assumes *FIRST, and the first member of that file is used.
record-format-name
This is the name of the record format contained in the specified iSeries, eServer i5, or System i5 file, or *ONLY. Before specifying the record format name, specify the member name or *FIRST. If the record format name is not specified, the system assumes *ONLY, and the only record format for that file is used. To specify a record format name, delimit the record format name and member name with a comma.

When the specified iSeries, eServer i5, or System i5 file has several record formats, a record format name must be specified. If the file member name is not specified, a record format name cannot be specified.

Notes:
  1. A library name, file name, file member name, and record format name can be specified using up to 10 characters for each. Each name must begin with A to Z, ¥, #, or @. For characters subsequent to the first, 0 to 9, underscores, and periods can also be used.
  2. When the FROM field remains blank or a comma is entered to specify the next file name, selecting Browse displays a list of libraries defined in *USRLIBL of the iSeries, eServer i5, or System i5 job library list.
  3. Enter part of the file name, member name, or record format name, followed by an asterisk (*), then select Browse. The system displays a list of names beginning with the specified characters.

For example, you might want to transfer data from file member ITEMMBR1 (first member) of file ITEMMAST in library ITEMLIB. ITEMFMT is the only record format of this file. The specification will be as follows:

ITEMLIB/ITEMMAST(ITEMMBR1,ITEMFMT)

Alternatively, specify:

ITEMLIB/ITEMMAST

Receiving a Summary of Record Groups

The following information is necessary to receive summary records.

To transfer a summary record, do not leave this input area blank or specify an asterisk (*) (except when all the fields of the file specified at the prompt are specified in GROUP BY). The field names specified in SELECT (except for those specified in functions) must also have been specified in GROUP BY.

The functions and fields specified in SELECT return actual summary information for each group. Enter the field names and functions in SELECT in the order in which they are to be displayed.

Note:
Null values are not included in the functions. When an entire value is null, the function output is set to null, except for COUNT. The COUNT output is 0.

The function format is as follows.

function (field-name)

This has the following meaning:

function
This is one of the following functions:
AVG
Transfers the average value of the specified fields for each record group. This function can be used only for numeric fields.
MIN
Transfers the minimum or lowest value of the specified fields for each record group.
MAX
Transfers the maximum or highest value of the specified fields for each record group.
SUM
Transfers the total value of the specified fields for each record group. This function can be used only for numeric fields.
COUNT
Transfers the total number of records that satisfy the WHERE condition for each record group. Specify COUNT(*).
field-name
This is the field name defined with the record format specified in FROM.

Each function returns one value for each record group. In SELECT, several functions can be specified. To do so, delimit the functions by commas, as follows:

SUPPNO, AVG(PRICE), MIN(PRICE), MAX(PRICE)

This indicates that the average, minimum, and maximum values for PRICE are calculated for each supplier after SUPPNO has been selected. A summary record is transferred according to the function selection. Specify SUPPNO in GROUP BY, because SUPPNO has not been used for the functions.

Advanced Options

The following advanced options are available for iSeries->PC Transfer.

JOIN BY

When several files have been specified in FROM, specify JOIN BY. When only one file has been specified in FROM, JOIN BY does not appear.

JOIN BY specifies how to link or join the records of the files specified in FROM. Each file specified in FROM must be joined with at least one other file that has been specified in FROM.

Use JOIN BY to specify one or more join conditions. The join conditions indicate the similarity of two files. Therefore, they indicate which records of one file are joined with those of another.

The join conditions are as follows:

field-name = field-name

Field name is the name of the field defined in the record format specified in FROM. The join conditions require two field names, one for each file to be joined.

Field names must be delimited by one of these:

=
Equal
<> or ><
Not equal
>
Greater than
>=
Greater than or equal to
<
Less than
<=
Less than or equal to

When specifying fields in JOIN BY, observe the following rules.

The field name to be specified might have been defined in the files specified in FROM. When such a field name is used in the following items, prefix the field name with the file qualifier:

The file qualifier is the character T (uppercase or lowercase) followed by a one- or two-digit number. Use T1 for fields defined with the first record format, T2 for fields defined with the second record format, and so on. Delimit the file qualifier and field name with a period (.). See Receiving Records Using File Qualifiers for details of the file qualifiers.

If the field name of the file specified in FROM cannot be found, select Browse when the cursor is on the JOIN BY input area. Then, a list of file qualifiers and field names of the files appears.

To join three or more files, or to join two files based on two or more common fields, two or more link conditions must be used. To specify several join conditions, join the conditions with AND. For example:

T1.EMPNO = T2.EMPNO AND T2.EMPNO = T3.EMPNO

In this case, records having the same value as EMPNO are joined between the first and second files specified in FROM. Then, such records are joined between the second and third files specified in FROM.

Up to 32 join conditions can be specified.

After JOIN BY is specified, each of SELECT, WHERE, and ORDER BY can be completed, by following the procedure described earlier in this chapter. To browse a field name that has been defined in several files, prefix the field name with a file qualifier.

GROUP BY

This item is required only to classify iSeries, eServer i5, or System i5 file records into several groups. When no value is specified in GROUP BY, all the records are treated as a single group.

If GROUP BY is not displayed, select Group functions at the bottom right of the screen. Then, GROUP BY appears. GROUP BY and HAVING are displayed concurrently. You can specify either, both, or neither.

When GROUP BY and HAVING are displayed but you do not want to specify either, select Remove Group functions. The two items disappear.

To classify several records into groups, specify one or more fields to act as the base for grouping. Records are grouped according to the field specified first, then by the field specified second, and so on. For example, suppose that the following groupings are specified:

SHIFT, DEPTNO

In this example, the records are first grouped by SHIFT. Records belonging to a single group will subsequently have the same value as SHIFT. Then, the records in each group are grouped by DEPTNO. When there is only one record having a certain SHIFT value, the group has only one record.

Delimit field names with commas. Blanks can be specified to improve readability. Up to 50 field names can be specified. These fields must have been defined in the record format defined in FROM.

If a field cannot be found, selecting Browse displays a list of all the fields contained in the record.

With GROUP BY specified, specify SELECT to transfer the summary record of each group.

SELECT

This item is always required. It specifies the field to be transferred or the function that indicates the type of summary information to be transferred.

The field to be specified must have been defined in the record format specified in FROM.

To transfer all the fields in the specified record, specify an asterisk (*) in this input field. (Specifying an asterisk causes all fields in the record to be transferred.)

Note:
Up to 256 fields can be transferred. When more than 256 fields have been defined in a file, an asterisk cannot be used. In this case, specify the names by selecting the fields to be transferred.

To transfer fields by selecting from a record, enter the field names in the order in which the fields are arranged. One or more blanks can be placed between the field names to improve readability. However, the names must be delimited by commas, as follows:

ITEMNO,  QONHAND,  PRIC

You can also specify:

ITEMNO,QONHAND,PRICE

When records are transferred from an iSeries, eServer i5, or System i5 source file, specifying an asterisk (*) causes all fields in the file to be transferred, with the exception of the order number field and date field. (To transfer all the fields, including the order number field and date field, specify all the field names, including each data field name.)

A field can be specified repeatedly as required. However, bear in mind that no more than 256 fields can be selected. A list of field names can be displayed by selecting Browse.

WHERE

This item is optional. It specifies one or more conditions that records to be transferred must satisfy.

To transfer summary records, use this item to specify which records are to be grouped, then group the records. Using this item, you can specify one or more conditions that the record must satisfy to belong to a certain group. When WHERE is not specified, all records are grouped.

As the conditions, specify the test to be applied to the records in the specified file member. All the records in the specified file member are tested for the conditions specified here. Only those records that pass this test are transferred.

When WHERE is not specified, all records in the specified file member are transferred.

The condition format is as follows:

field-name  test  value
field-name
This must be a field substring or field name defined in the record format.

Fields or constants can be manipulated by specifying a supported function, with the results being used for comparison. The supported functions and usage are as follows:

SUBSTR
Returns the specified part of a character string. This function contains three parameters: the field name, starting position, and length of the returned substring. The following example returns the 20 characters starting from the 10th character of the FULLNAME field:

SUBSTR(FULLNAME 10 20)

VALUE
Returns the first non-null value in the parameter list. (If all parameters are null, null is returned.)

VALUE(DEPOSIT WITHDRAW BALANCE)

CURRENT
Returns DATE, TIME, TIMEZONE, or TIMESTAMP for the current system.

CURRENT(TIMEZONE)

DIGITS
Returns a character string representation of a numeric field.

DIGITS(EMPLOYEE#)

CHAR
Returns a character string representation of the date field, time field, or time-stamp field. The second parameter is used to specify the format of the Systems Application Architecture® (SAA) of the string to be returned (supported values are USA, EUR, ISO, or JIS).

CHAR(DATEHIRE USA)

DATE
Returns the date of the time-stamp field.

DATE(TIMECRTD)

TIME
Returns the time of the time-stamp field.

TIME(TIMECRTD)

TIMESTAMP
Returns the time-stamp, combining the date field and time field.

TIMESTAMP(DATESEND TIMESEND)

YEAR
Returns the year of the date field or time-stamp field.

YEAR(DATEHIRE)

MONTH
Returns the month of the date field or time-stamp field.

MONTH(DATEHIRE)

DAY
Returns the date of the date field or time-stamp field.

DAY(DATEHIRE)

DAYS
Returns the day of the year, counted from January 1, of the date field or time-stamp field.

DAYS(DATEHIRE)

HOUR
Returns the time of the time field or time-stamp field.

HOUR(TIMESEND)

MINUTE
Returns the minute of the time field or time-stamp field.

MINUTE(TIMESEND)

SECOND
Returns the second of the time field or time-stamp field.

SECOND(TIMESEND)

MICROSECOND
Returns the microsecond of the time field or time-stamp field.

MICROSECOND(TIMECRTD)

test
This is the comparison type to be applied to fields or functions.

The following tests can be used. One or more blanks can be placed before and after these tests.

Note:
Values are searched according to the exact characters specified by the user. In other words, when the user's specification consists only of uppercase characters, only uppercase character strings are returned. Similarly, when the specification consists only lowercase characters, only lowercase character strings are returned.
=
Equal
<> or ><
Not equal
>
Greater than
>=
Greater than or equal to
<
Less than
<=
Less than or equal to
LIKE
The field is similar to the specified value.
BETWEEN
The field is equal to one of two constants, or to a value between them.
IN
The field is the same as one of the values in the constant list.
IS
The field contains null values.
ISNOT
The field contains no null values.

Test usage is as follows:

Using the LIKE Test
The LIKE test checks the field specified with the field name for a character pattern specified as a value. The field to be specified must be a character field.

The values to be tested must be character-string constants. This string can contain any characters. A percent (%) character indicates a character string consisting of zero or more characters. A 1-byte underscore (_) character indicates any single 1-byte character. A 2-byte underscore (_) character indicates any single 2-byte character.

The following example explains how to use the LIKE test:

NAME LIKE '%ANNE%'

The previous example searches for names containing character string ANNE, such as ANNE, ANNETTE, and SUZANNE.

The following example searches for names beginning with character string ANNE, such as ANNE and ANNETTE.

NAME LIKE 'ANNE%'

The following example searches for names ending with character string ANNE, such as ANNE and SUZANNE.

NAME LIKE '%ANNE'

The following example searches for all names whose second character is A.

NAME LIKE '_A%'

The following example searches for all last names beginning with character J.

LSTNAM LIKE 'J%'

This has the same effect as the following example:

SUBSTR (LSTNAM,1,1) = 'J'

When the pattern does not include a percent character (%), the length of the character string must be identical to that of the field.

Using the BETWEEN Test
The BETWEEN test checks the fields specified in the field name for character strings or numeric values that are equal to or between the specified constants. The values to be tested must be two character-string constants or two numeric constants. The types of these constants must be identical to that of the field name specified by the user. Delimit the two constants with AND.

The following example searches for those records for which the price is between 50.35 and 75.3, inclusive:

PRICE BETWEEN 50.35 AND 75.3

The following example searches for those records for which the name begins with C:

NAME BETWEEN 'C' AND 'CZZZZZZZZZ'

The following example searches for those records for which the balance is between 0 and 5 000.

BALDUE BETWEEN 0 AND 5000

This has the same meaning as the following expression.

BALDUE >= 0 AND BALDUE <= 5000
Note:
Specify the values to be tested in the form of BETWEEN (minimum) AND (maximum). For instance, BETWEEN 1 AND 10 is a valid specification. However, BETWEEN 10 AND 1 returns no records.
Using the IN Test
The IN test checks the fields specified in the field name for the character strings or numeric values in the list specified as the value. The value to be tested must be a list of character-string constants or numeric constants. In addition, the types of these constants must be identical to that of the specified field. Delimit the constants with blanks and enclose them in parentheses. Up to 100 constants can be specified. The following example shows how to use the IN test:
NAME IN ('SMITH' 'JONES' 'ANDERSON')
This example searches for those records for which the name is SMITH, JONES, or ANDERSON.

The following example searches for the values in the STATE field for which the value is other than NY, MN, or TX:

NOT STATE IN ('NY' 'MN' 'TX')
Note:
Values are searched according to the exact characters specified by the user. In other words, when the user's specification consists of only uppercase characters, only uppercase character strings are returned. Similarly, when the specification consists of only lowercase characters, only lowercase character strings are returned.
Using the IS Test
The IS test checks the fields specified in the field name for null values.

The following example searches for those records for which the commission field contains null values:

COMMISSIONS IS NULL
Using the ISNOT Test
The ISNOT test checks the fields specified in the field name for non-null values.

The following example searches for those records for which the commission field does not contain null values:

COMMISSIONS ISNOT NULL

In the test, logical AND and logical OR can be combined. When both AND and OR are specified, AND comparison is performed first. Up to 50 conditions can be specified. For example:

MONTH=2 AND LOC='MIAMI' OR LOC='CHICAGO'

In this example, each record to be selected must satisfy the following condition:

MONTH=2 AND LOC='MIAMI'

or must satisfy the following condition:

LOC='CHICAGO'

This command can be modified by using parentheses. For example:

MONTH=2 AND (LOC='MIAMI' OR LOC='CHICAGO')

In this example, each record to be selected must satisfy the following condition:

MONTH=2

and it must satisfy the following condition:

LOC='MIAMI' OR LOC='CHICAGO'

NOT can also be used. The following example selects items where data is transferred not only from those records in which the DEPT field is not equal to 470, but also from those records for which the DEPT field is equal to 470 and, additionally, STATE is equal to NY.

NOT (DEPT = 470) OR (DEPT = 470 AND
  STATE = 'NY')

Comparison can start from a certain line and end at the next line. However, a field name cannot start from a certain line and end at the next line. Field names must not exceed one line.

When a value to be tested is a character string enclosed in quotation marks, the value can start from a certain line and continue to the next line.

HAVING

This item is optional. It specifies which summary record is transferred.

Pay particular attention to the difference between HAVING and WHERE. WHERE operates on each record within a certain group. HAVING, on the other hand, operates only on summary records (records that contain summary information for each group).

With this item, you can specify one or more conditions that a summary record must satisfy prior to being transferred.

As the conditions, specify the tests that should be applied to the summary records. The specified test conditions are applied to all summary records, only those summary records that pass the tests are transferred. To transfer all summary records, leave the HAVING item blank.

The format of the conditions is as follows:

function (field-name)  test  value

This indicates:

function
This is a function supported for SELECT. See the description of SELECT in this section for details of these functions.
field-name
This is the field defined by the record format specified in FROM. A field name is acceptable even when it has not been specified in SELECT.
Test
This is the comparison type for functions. The types are listed below.
=
Equal to
<> or ><
Not equal
>
Greater than
>=
Greater than or equal to
<
Less than
<=
Less than or equal to
value
This is a function operating on certain fields or a constant. See WHERE for details of constants, expressions, and tests.
Note:
A comma is treated as a decimal point. Therefore, do not separate numbers with commas.

Test conditions can be combined by using logical AND or logical OR. When both AND and OR are specified, AND comparison is performed first. Up to 50 tests can be specified. By using parentheses, the operation order can be modified, or a description can be added to an operation. For example, you can specify:

COUNT(*) >=2 AND MAX(PRICE) > 100

In this case, the following conditions are applied concurrently: groups to be transferred must contain more than one record, and the summary records in such groups are transferred only when the maximum price is greater than 100.

If the desired field cannot be found, selecting Browse displays a list of the names of all fields in the record.

The type, length, digit, and number of decimal places of the value returned for each function are:

            Type     Length    Digit       Decimal Places
SUM         Packed     16       31    (Same as tested field)
AVG         Packed     16       31     31 (Total of the digit
                                           and decimal places
                                           of the field)
COUNT       Binary      4       10         0
MAX              (Same as tested field)
MIN              (Same as tested field)
ORDER BY

This item is optional. It specifies the order in which the requested records are grouped. When ORDER BY is not specified, record transfer is not done according to a certain order.

Records are grouped according to the field specified first. Those records having the same value in each field specified first are grouped by the field specified second, and so on. Records containing null values are grouped after all records without null values have been grouped.

For example, you can specify:

DEPT,NAME,PHONE

In this case, records are first grouped according to DEPT. Then, the records having the same value for DEPT are grouped by NAME. The records with the same DEPT and NAME values are finally grouped by PHONE.

When a field name is specified in ORDER BY, it must also have been specified in SELECT, or SELECT* must have been specified.

Fields can be grouped in ascending or descending order. To do this, specify one blank after a field name then enter ASC or DESC. The default value is ASC. For example, specify:

DEPT DESC, NAME ASC

This indicates that the DEPT fields are to be grouped in descending order, after which the NAME fields are to be grouped in ascending (alphabetic) order.

Absolute values (ABS) can be specified for numeric fields. To do this, add a blank after a field name then enter ABS. For those fields having negative values, the negative signs are ignored and the absolute values are used.

The total length of the fields to be specified must not exceed 120 digits.

Return Record at Missing Field Value

When joining records from several files, joining might fail because a record is missing. This item specifies whether records with missing fields are transferred.

When you specify that records with missing fields are to be transferred, the alternative values for the missing fields are transferred. These values are normally blanks for character fields and zeros for numeric fields.

When you do not specify transfer of records with missing fields, those records are not transferred.

Specify this item to transfer data records that have alternative values for missing fields.

Do not specify this item if data records that have alternative values for missing fields are not to be specified. In this case, only those data records created from those records that exist in all files specified in FROM are transferred.

TO

Output device

This item specifies where received data is to be sent.

Display
The received data is displayed on the screen.
Disk
The received data is written to a workstation diskette or hard disk file.
Printer
The received data is printed on the printer.

When Disk is selected as the output device, also specify the following items.

PC file
This item specifies the name of the workstation disk file or diskette file to which the data is to be written.
Replace old file
This item is always required. It specifies whether the records in the file specified by PC File are to be replaced with the transferred records.

The default value is Replace old file.

Workstation file type
This item is always required. It specifies the type of the workstation disk file or diskette file to which the transferred records are written.

The system default is PC code test.

Save transfer description
This item is always required. It specifies whether the workstation file description is written to a workstation file. This file description describes the transferred data and it is required to subsequently return data to the iSeries, eServer i5, or System i5.

The system default is Save.

Description file name
This item is always required. It appears only when Save Transfer Description is selected. The File Description File Name specifies the name of the workstation disk file or diskette file to which the file description is written.

This item automatically sets the desired file name. This file name is the same as that specified by the user for TO, but to which extension .FDF has been added. Extension .FDF indicates that this file is a file-description file.

The use of extension .FDF is recommended when using a unique file name. To specify a file name in this item, use the same format as that in TO. (Items inside brackets [ ] can be omitted.)

[d:][path-name]file-name[.ext]

After Save File Description File is specified or a name is specified for File Description File Name, the iSeries->PC Transfer Request window reopens after the Return key is pressed. Using this screen, a transfer request can be changed, saved, or executed.

Saving, Opening, Changing, and Executing a Transfer Request

The following section explains how to save, open, change, and execute, as a file, the information (transfer request) on the data to be transferred.

Saving a Transfer Request

You should save a transfer request, especially when the request will be executed repeatedly. This eliminates the need to create a transfer request every time a request is executed. To save a transfer request, do as follows:

  1. Specify the information needed for transfer, using the iSeries->PC Transfer window. See Creating an iSeries-to-Workstation Transfer Request for an explanation of how to specify the required data.
  2. After specifying the necessary data, click Save or Save As from the File menu of the menu bar.

    The Save Transfer Request File As window opens.

  3. Specify each item, referring to the following explanation, then click OK.
    File Name
    Disk to which data is to be saved. Specify a file name or diskette file name. The default extension is TTO. Extension TTO identifies a file as a transfer request file.
    Description
    This item can be used to add a short explanation of a transfer request, as required. The explanation can be up to 40 characters in length. This explanation is saved with the transfer request, and displayed in the list of transfer request names. It is useful, therefore, for identifying a transfer request.
  4. The system asks whether the saved transfer request is to be registered in the PC400 folder.

    When you click OK, the transfer request is registered as an icon. Subsequently selecting this icon transfers data according to the registered data transfer request.

Opening and Changing a Saved Transfer Request

To open and change a saved transfer request:

  1. Display the iSeries->PC Transfer window.
  2. Select Open from the File menu.

    The Open Transfer Request File window opens.

  3. Specify the name of the file to be opened using the Open Transfer Request File window. Then click OK.

    The iSeries->PC Transfer window reopens, with the information specified for each item for the transfer request displayed. This completes opening of the saved transfer request.

  4. Change the contents, as necessary.
  5. To save the changed contents, follow the procedure given in Saving a Transfer Request.

Executing a Transfer Request

You can execute a file transfer request in one of the following two ways:

Selecting the Icon with Which the Transfer Request Has Been Registered

This method can be used only when a transfer request has been saved as an icon by using the iSeries->PC Transfer window.

Data transfer starts as soon as you select the icon with which a transfer request has been registered.

Using the iSeries->PC Transfer Window
  1. Before attempting to execute a transfer request, all operations such as creating, opening, and changing a transfer request must have been completed.
    Note:
    When data is transferred from a workstation to an existing member in an iSeries, eServer i5, or System i5 file, the transferred data replaces the existing data in the member.
  2. Select Receive from the iSeries->PC Transfer window.

    Data transfer starts.

  3. After the transfer has been completed, click Cancel, or click Exit from the File menu.

Status during Transfer

Display can be specified as the output device, when the current transfer request is created or changed. This sends the transferred record to the screen. On the screen, each record is displayed on one line.

Each field in a transferred record is converted from the iSeries, eServer i5, or System i5 data type to workstation code.

Note:
The workstation receives the iSeries, eServer i5, or System i5 records in order and then writes them to a temporary file of the default directory in the default drive (usually, the directory in which PC400 is installed). The maximum number of records that can be transferred is 4096 records, limited by the amount of records that can be stored in free space of the default drive.

When Disk is selected as the output device, the following actions are performed:

  1. The workstation file description is written to a workstation disk file or diskette file according to the Save File Description File specification. (If Save File Description File has not been specified, this procedure is not performed.)
  2. The transferred records are written to a workstation disk file or diskette file.

Limited Usage of File Names and Field Names

For a transfer request from a workstation to the iSeries, eServer i5, or System i5, none of the following reserved words can be specified as a file name or field name:

CRTFILE
CRTMBR
FILETEXT
FILETYPE
INTO
MBRTEXT
PUBAUT
RCDLEN
REFFILE

For a transfer request from the iSeries, eServer i5, or System i5 to a workstation, none of the following reserved words can be used as a file name or field name:

ABS
AND
ASC
AVG
BETWEEN
BY
COLUMNS
COUNT
DESC
EXTRACT
FROM
GROUP
HAVING
IN
INNER
IS
ISNOT
LIKE
MAX
MIN
NOT
OPTIONS
OR
ORDER
PARTOUT
REPLACE
SELECT
SUBSTR
SUM
TABLES
WHERE

To use one of these reserved words as a file name or field name, use the reserved word in uppercase, enclosed in quotation marks:

TO MYLIB/"INTO"

Examples of Transfer Requests for Receiving

This section provides examples of transfer requests for receiving. The contents of this section provide supplementary information to help you better understand transfer requests for receiving.

This section describes how to transfer data from the iSeries, eServer i5, or System i5, based on the inventory control file INVENTORY and supplier file SUPPLIERS.

The INVENTORY file contains information about the various parts in stock. Each part has a three-digit identification number, PARTNUM. The INVENTORY file contains the names of parts (DESCRIPTION) and the quantity on hand (QONHAND) for each part.

        File: INVENTORY
 Field name: PARTNUM  DESCRIPTION  QONHAND
              -------  -----------  -------
    Record 1:     209          CAM       50
           2:     221         BOLT      650
           3:     222         BOLT     1250
           4:     231          NUT      700
           5:     232          NUT     1100
           6:     207         GEAR       75
           7:     241       WASHER     6000
           8:     285        WHEEL      350
           9:     295         BELT       85
 

The SUPPLIERS file contains information about the suppliers of each part. Each supplier is identified by a two-digit number, SUPPNO. The SUPPLIERS file contains the number of parts delivered (PARTNO), their prices (PRICE), times of delivery (DELIVTIME), and ordered quantities (QONORDER). The parts listed in the SUPPLIERS file are the same as those listed in the INVENTORY file.

        File: SUPPLIERS
  Field name: SUPPNO   PARTNO   PRICE   DELIVTIME   QONORDER
              ------   ------   -----   ---------   --------
    Record 1:     51      221     .30          10         50
           2:     51      231     .10          10          0
           3:     53      222     .25          15          0
           4:     53      232     .10          15        200
           5:     53      241     .08          15          0
           6:     54      209   18.00          21          0
           7:     54      221     .10          30        150
           8:     54      231     .04          30        200
           9:     54      241     .02          30        200
          10:     57      285   21.00          14          0
          11:     57      295    8.50          21         24
          12:     61      221     .20          21          0
          13:     61      222     .20          21        200
          14:     61      241     .05          21          0
          15:     64      207   29.00          14         20
          16:     64      209   19.50           7          7

Receiving Part of an iSeries, eServer i5, or System i5 File

Specify the following items:

Library/File (Member) INVENTORY
SELECT PARTNUM, QONHAND
WHERE QONHAND < 100
ORDER BY PARTNUM

In this case, only part of the INVENTORY file is to be transferred. Specifically, only the part number (PARTNUM) and quantity on hand (QONHAND) fields of the records for which the number of parts in stock is less than 100 (QONHAND < 100) are transferred. Records are transferred in ascending order of parts numbers (PARTNUM).

The following data is transferred:

     Field:   PARTNUM  QONHAND
              -------  -------
  Record 1:      207       75
         2:      209       50
         3:      295       85

Receiving Records Joined from Several iSeries, eServer i5, or System i5 Files

Two iSeries, eServer i5, or System i5 files, INVENTORY and SUPPLIERS, are assumed. Note that both files contain records including part number fields. The INVENTORY file contains inventory information about individual parts. The SUPPLIERS file contains information about purchasing and ordering.

You might want to transfer information on part numbers, part names, and the prices of the parts to be ordered from supplier 51. The desired fields are PARTNO (SUPPLIERS file), DESCRIPTION (INVENTORY file), and PRICE (SUPPLIERS file).

By comparing the data in the INVENTORY file and the SUPPLIERS file, the user can determine that supplier 51 provides part numbers 221 and 231, called BOLT and NUT, respectively, and that their prices are 30 cents and 10 cents, respectively. The following table summarizes this information:

     Field:   PARTNO   DESCRIPTION   PRICE
              ------   -----------   -----
  Record 1:    221     BOLT            .30
         2:    231     NUT             .10

The same results are available by joining the data in these two files by using the iSeries->PC Transfer function. To do this, specify both files (INVENTORY and SUPPLIERS) in the FROM item. For SELECT, specify which fields are to be transferred (PARTNO, DESCRIPTION, and PRICE). For WHERE, specify which records are to be transferred (records for which SUPPNO = 51).

Respecify the relationship between the two files in JOIN BY. From these results, the user can determine, by checking the SUPPLIERS file, that part number 221 is delivered from supplier 51 at a cost of 30 cents. In addition, to determine the part name, the user must check the INVENTORY file for part number 221 and its product name. In other words, the user observes that data is joined from the records in both the SUPPLIERS file and the INVENTORY file and that those records have the same part number. Therefore, to link the two records in these files, the records must have the same part number.

In short, to obtain this information, specify:

Library/File (Member) SUPPLIERS, INVENTORY
JOIN BY PARTNO = PARTNUM
SELECT PARTNO, DESCRIPTION, PRICE
WHERE SUPPNO = 51
ORDER BY PARTNO

Receiving Records Using File Qualifiers

To join records from several iSeries, eServer i5, or System i5 files, fields of the same type must be joined.

For example, the part number fields in the INVENTORY and SUPPLIERS files can have the same name PARTNO. To specify the desired PARTNO fields, you must specify which file contains those fields. To do so, file qualifiers are used.

A file qualifier is the character T (uppercase or lowercase) followed by a one- or two-digit number. Use a comma to delimit the file qualifier and field name. In the previous example, prefix T1. and T2. to the PARTNO field names. T1. indicates the first file of FROM, while T2. indicates the second.

To obtain the same information as in the previous example, specify:

Library/File (Member) SUPPLIERS, INVENTORY
JOIN BY T1.PARTNO = T2.PARTNO
SELECT T1.PARTNO, DESCRIPTION, PRICE
WHERE SUPPNO = 51
ORDER BY T1.PARTNO

T1.PARTNO indicates the PARTNO fields in the SUPPLIERS file, while T2.PARTNO indicates the PARTNO fields in the INVENTORY file.

Qualifiers are not needed for the names of the DESCRIPTION, PRICE, and SUPPNO fields, because they exist in one file only. However, the user can specify the following qualifiers for clarity:

T2.DESCRIPTION, T1.PRICE, T1.SUPPNO

The following examples of joining several iSeries, eServer i5, or System i5 files describe more sophisticated techniques. You should now be familiar with the basics of how to join two files. For a more detailed explanation, refer to the following sections.

Receiving with Field Missing Records Joined

The joining of records from several files could fail because one or more records is missing. For example, the record containing part number 221 might not be found in the INVENTORY file. This means that the records that can be joined to the 1st, 7th, and 12th records in the SUPPLIERS file do not exist in the INVENTORY file. In this case, the PARTNO field and PRICE field for part number 221 can be determined, but the DESCRIPTION field cannot be determined. So, the DESCRIPTION field is missing.

To transfer field missing records, use Return Record at Missing Field Value.

When Return Record at Missing Field Value has been specified, the default iSeries, eServer i5, or System i5 values are transferred instead of the missing field values. The default values for character fields are blanks, while those for numeric fields are zeros. For example, if the INVENTORY file does not contain the part number 221 record, the result of the previous example will be as follows:

     Field: PARTNO   DESCRIPTION   PRICE
            ------   -----------   -----
  Record 1:    221                   .30
         2:    231   NUT             .10

If Return Record at Missing Field Value has not been specified, the field missing records are not transferred. For example, if the INVENTORY file does not contain the part number 221 record, the result of the previous example will be as follows:

     Field: PARTNO   DESCRIPTION   PRICE
            ------   -----------   -----
  Record 1:    231   NUT             .10

Receiving with Records in a Same File Joined

Records in the same file can be joined. In other words, a file can be repeatedly specified in FROM. For instance, data in certain records can be compared using this function.

For example, the SUPPLIERS file shows that several suppliers provide the same part. The user might want to know which supplier sets a price that is double, or greater than double, that of another. To transfer the necessary information to a workstation, specify:

Library/File (Member) SUPPLIERS, SUPPLIERS
JOIN BY T1.PARTNO = T2.PARTNO
SELECT T1.PARTNO, T1.SUPPNO, T1.PRICE, T2.SUPPNO, T2.PRICE
WHERE T1.PRICE > 2 * T2.PRICE
ORDER BY T1.PARTNO

The same file has been specified in FROM twice. JOIN BY specifies that records having the same part number are joined. This creates a joined record containing information about two suppliers of a single part. The user can spot those records for which the price is double, or greater than double, that of another supplier.

Records in the SUPPLIERS file are compared, one by one, with all the records (including itself) in the SUPPLIERS file. When the same part number is found, the two corresponding records are linked. This processing is performed for each record in the SUPPLIERS file.

For each record, the first supplier's price is compared with the second supplier's price. When the first supplier's price is double, or greater than double, that of the second, only the record containing the first supplier price is kept.

The final result is as follows:

     Field:  T1.PARTNO   T1.SUPPNO   T1.PRICE   T2.SUPPNO   T2.PRICE
             ---------   ---------   --------   ---------   --------
  Record 1:       221          51        .30          54        .10
         2:       231          51        .10          54        .04
         3:       241          53        .08          54        .02
         4:       241          61        .05          54        .02

Specifying Records To Be Included in a Group

You might want to limit which records will be included in a group. To do so, use WHERE. The following example transfers the average and lowest prices of each part for those records for which the delivery time (DELIVTIME) is less than 30 days.

Library/File (Member) SUPPLIERS
GROUP BY PARTNO
SELECT PARTNO, AVG(PRICE), MIN(PRICE)
WHERE DELIVTIME < 30

The result is as follows:

     Field: PARTNO   AVG(PRICE)   MIN(PRICE)
           ------   ----------   ----------
  Record 1:   221          .25          .20
         2:   231          .10          .10
         3:   222          .23          .20
         4:   232          .10          .10
         5:   241          .07          .05
         6:   209        18.75        18.00
         7:   285        21.00        21.00
         8:   295         8.50         8.50
         9:   207        29.00        29.00

Note that the conditions specified in WHERE are checked first, then the records that satisfy those conditions are included in the group.

Specifying Summary Records To Be Transferred

In some cases, you might want to transfer only summary records that satisfy certain conditions. The use of HAVING enables the selection of which summary records are to be transferred. WHERE is applied to certain records in a group, while HAVING is applied only to summary records.

The following example transfers the highest and lowest prices for each part. However, the summary records to be transferred are only those for which the highest price exceeds 10.00.

Library/File (Member) SUPPLIERS
GROUP BY PARTNO
SELECT PARTNO, MAX(PRICE), MIN(PRICE)
HAVING MAX(PRICE) > 10.00

The following table shows the result of removing unnecessary summary records by using HAVING

     Field: PARTNO   MAX(PRICE)   MIN(PRICE)
            ------   ----------   ----------
  Record 1:    209        19.50        18.00
         2:    285        21.00        21.00
         3:    207        29.00        29.00

One summary record for an entire file can be transferred. To do this, specify only the summary function in SELECT and nothing in GROUP BY. As a result, an entire file can be recognized as one group, while one summary record can be transferred for the group.

You can concurrently use the concept of summarizing groups and that of joining records from several files. To obtain the desired results, do as follows:

  1. Specify a file in FROM, and specify the join conditions to join the records in JOIN BY.
  2. Specify the conditions in WHERE to remove unnecessary records.
  3. Specify the fields used for grouping the remaining records in GROUP BY.
  4. Specify the function in SELECT, then create summary records.
  5. Specify the conditions in HAVING to remove unnecessary records.
  6. Specify the items for grouping the final summary records in ORDER BY.

Functions Available from the Pull-Down Menu

The following section provides a simple explanation of the menu bar of the iSeries->PC Transfer window and PC->iSeries Transfer window.

File

Transfer request files can be processed.

Create
Creates a transfer request file
Open
Displays the contents of an existing transfer request file
Save, Save As
Save the current settings to the transfer request file being used or to a new transfer request file, respectively
Exit
Terminates the operation started by selecting the Data Transfer icon

Setup (Only for iSeries->PC Transfer)

User Options

Time, date, and numeric value format for receiving can be specified.

Ignore Decimal Data Error
Specifies whether decimal data errors found in packed or zoned decimal fields upon executing requests are to be ignored. Selecting Yes to ignore decimal data errors and using existing indices can considerably reduce the time needed to execute a request. If this item is not specified, the transfer request creates indices again and modifies any detected decimal data errors. This requires extra processing time.
Time Format
Specifies a desired time format for fields of iSeries, eServer i5, or System i5 field type having a selected time. If no time format is specified, the default value in the workstation's national information file is used when the transfer request starts, and that in an existing transfer request is assumed when the request is called again.

Supported time formats are as follows:

HMS
Hours, minutes, seconds (hh:mm:ss)
ISO
International Standard Organization (hh.mm.ss)
USA
USA Standard (hh:mm AM or PM)
EUR
IBM European Standard (hh.mm.ss)
JIS
Japanese Industrial Standard (hh:mm:ss)
DDS
iSeries, eServer i5, or System i5 DDS (Format given by iSeries, eServer i5, or System i5 file attribute)
DFT
iSeries, eServer i5, or System i5 default format (Host job default is used)
Time separator
Specifies enabled delimiters. The fields of the iSeries, eServer i5, or System i5 field type for the selected time must be in a format that supports delimiters.

When no delimiters are specified, the default value in the workstation's national information file is used when the transfer request starts, and that in an existing transfer request is assumed when the request is called again.

Supported time delimiters are as follows:

Colon
(:)
Period
(.)
Comma
(,)
Blank
( )
Null
(NULL) No Separator
Default value
(DFT) iSeries, eServer i5, or System i5 Default Separator
Date Format
Specifies the date format for fields of iSeries, eServer i5, or System i5 field type for the selected date.

If this date format is not specified, the default value in the workstation's national information file is used.

Supported values are as follows:

MDY
Month, day, year (mm/dd/yy)
DMY
Day, month ,year (dd/mm/yy)
YMD
Year, month, day (yy/mm/dd)
JUL
Julian (yy/ddd)
ISO
International Standard Organization (yyyy-mm-dd)
USA
USA Standards (mm/dd/yyyy)
EUR
IBM European Standard (dd.mm.yyyy)
JIS
Japanese Industrial Standard (yyyy-mm-dd)
DDS
iSeries, eServer i5, or System i5 DDS (Format given by iSeries, eServer i5, or System i5 file attribute)
DFT
iSeries, eServer i5, or System i5 default format (Host job default is used)
Date separator
Specifies delimiters. The fields of the iSeries, eServer i5, or System i5 field type for the selected date must be in a format that supports delimiters.

When no date delimiters are specified, the default value in the workstation's national information file is used when the transfer request starts, and that in an existing transfer request is used when the request is called again.

Supported date delimiters are as follows:

Slash
(/)
Dash
(-)
Period
(.)
Comma
(,)
Blank
( )
Null
(Null) Delimiters are not used.
DFT
(DFT) iSeries, eServer i5, or System i5 default separator
Decimal separator
Specifies the decimal point character in an iSeries, eServer i5, or System i5 field whose type is packed decimal or zoned decimal.

When decimal points are not specified, the default value in the workstation's national information file is used when the transfer request starts, and that in an existing transfer request is used when the request is called again.

Supported decimal point delimiters are as follows:

Period
(.)
Comma
(,)
DFT
(DFT) - Default decimal separator

Sort Sequence

Specifies which sort sequence should be used for this transfer request.

iSeries job default
Sort by the table identified on the iSeries, eServer i5, or System i5 as the job sort table.
Hexadecimal
Sort by the internal hexadecimal representation.
User specified table
Sort by the table identified by the user in a subsequent prompt.
Shared Weight Table
Sort by the shared weight table associated with the language named in a subsequent prompt.
Unique Weight Table
Sort by the shared unique table associated with the language named in a subsequent prompt.

Changing the sort sequence affects the order in which records appear only if the ORDER BY clause is being used. The sort sequence affects all character comparisons that depend on the order of the alphabet. Such comparisons can occur in the WHERE clause, the GROUP BY clause, the HAVING clause, the JOIN BY clause, the IN predicate, the LIKE predicate, the BETWEEN predicate, the MAX function, and the MIN function. Comparison operations are =, <>, >, >=, and >=.

Sort Sequence Table Name

Type the name of the sort sequence table that you want to use for this transfer request. The format of the table name should be library/table. *LIBL and *CURLIB are allowed for the library name.

Translation Table

Translation tables for ASCII-to-EBCDIC translation or for EBCDIC-to-ASCII translation can be specified, created, and customized.

Current Table
Specifies whether the default translation or the user-defined translation table is to be used.
Host Code Page
Specifies the host code page to be used for translation.
Workstation Code Page
Specifies the workstation code page to be used for translation.
File Name
Specifies the file name of the user-defined table to be used for translation.

Signon Options

Use Kerberos principal, no prompting
This function enables Kerberos authentication, using the ticket generated by the Windows user credentials. This option is disabled by default.
Prompt as needed
The host will prompt you for signon information. For each host, the signon dialog is presented only once during the transfer session.

File-Description Files

A file-description file is a workstation file that contains all field descriptions of the data in the corresponding workstation data file. Each field descriptor contains the field name, data type, and field length. There is one field descriptor for each field in the workstation file.

A file-description file defines the following:

The workstation files require field definitions when the files are transferred. The field definitions describe the file as it exists on the workstation. These definitions contain data that is similar to the field definitions (DDS) required by iSeries, eServer i5, or System i5 files. The data must be defined for both the iSeries, eServer i5, or System i5 and the workstation files, because the field names from each file are needed to send the data to the iSeries, eServer i5, or System i5 and the data in each file might be in different formats.

A file-description file is created on request during the transfer process of data from an iSeries, eServer i5, or System i5 file to a workstation file. Therefore, you usually do not need to worry about the contents or the format of the file-description file. However, if you transfer data that has not been previously transferred to the system, you must create a file-description file.

Creating a File-Description File

You can create a file-description file using a workstation text editor. The file-description file must be an ASCII text file. Therefore, each record must end with a carriage return (CR) character (hex 0D) followed by a line feed (LF) character (hex 0A). All tab characters (hex 09) are treated as ASCII spaces. The last byte of the file must contain an end-of-file (EOF) character (hex 1A). Workstation editors that create ASCII text files usually use these special character designators, so normally you do not need to be concerned about them.

File-Description File Format

The format of the file-description file is as follows:

PCFDF [comment]
PCFT file-type-indicator [comment]
PCFO time-format,time-separator, date-format, date-separator, decimal-separator [comment]
PCFL field-name-1 data-type-1 length-1[/decimal-position-1][comment]
    .
    .
    .
PCFL field-name-n data-type-n length-n[/decimal-position-n][comment]
[* comment]

Items within brackets are optional. Use either uppercase or lowercase characters anywhere in the file.

PCFDF Entries

PCFDF is a keyword that identifies this file as a workstation file-description file. It must appear in the first line of the file, starting in column 1. A comment is the only other entry allowed on the first line. If you type a comment, it must be separated from the PCFDF keyword by a space.

PCFT Entries

PCFT is a keyword that identifies this record as containing the file type indicator. It is followed by an indicator identifying the type of file in which the data is stored. It must appear only once, and must start in column 1, after the PCFDF record and before any PCFL records. An optional comment can follow this file-type indicator if separated from the indicator by at least one space.

Following is an example of a PCFT entry:

PCFT 4 BASIC RANDOM FILE

Table 19 shows the valid file-type indicators.

Table 19. File-Type Indicators
Indicator File Type
1 ASCII text
2 DOS random
3 BASIC sequential
4 BASIC random
5 Data interchange format (DIF**)
6 No-conversion file
7 Reserved
8 DOS random type 2
9 BIFF format
PCFO Entry

The PCFO entry is optional. PCFO is a keyword that identifies this record as containing information about the date and time formats, time stamp, and separator characters for applicable formats. It must appear only once and must start in column 1, after the PCFT record and before any PCFL records. If there is no PCFO entry, the information or characters assigned as defaults for the host system are used.

Table 20 shows the valid time formats.

Table 20. Time Formats
Indicator Format Name Time Format
1 HMS hh:mm:ss
2 ISO - International Standards Organization hh.mm.ss
3 USA - USA standard hh:mm AM or PM
4 EUR - European hh.mm.ss
5 JIS - Japanese Industrial Standard Christian Era hh:mm:ss
6 DDS Format given by iSeries, eServer i5, or System i5 file attribute
7 DFT Host job default is used
* Unspecified Host job default is used

Table 21 shows the valid time separators.

Table 21. Time Separators
Indicator Separator
1 Colon (:)
2 Period (.)
3 Comma (,)
4 Blank ( )
5 Null (N)
6 Default (D) (host job default)
* Unspecified (host job default)

Table 22 shows the valid date formats.

Table 22. Date Formats
Indicator Format Name Date Format
1 MDY mm/dd/yy
2 DMY dd/mm/yy
3 YMD yy/mm/dd
4 Julian yy/ddd
5 ISO yyyy-mm-dd
6 USA mm/dd/yyyy
7 EUR dd.mm.yyyy
8 JIS yyyy-mm-dd
9 DDS Format given by iSeries, eServer i5, or System i5 file attribute
10 DFT Host job default is used
* Unspecified Host job default is used

Table 23 shows the valid date separators.

Table 23. Date Separators
Indicator Separator
1 Slash (/)
2 Dash (-)
3 Period (.)
4 Comma (,)
5 Blank ( )
6 Null (N)
7 Default (D) (host job default)
* Unspecified (host job default used)

Table 24 shows the valid decimal separators.

Table 24. Decimal Separators
Indicator Separator
1 Period (.)
2 Comma (,)
* Unspecified (workstation default used)

Following is an example of a PCFO entry:

PCFO 1,1,1,1,1 OPTIONS SETTINGS
PCFL Entries

PCFL identifies a definition for a field. Enter a PCFL entry in the file-description file for each field in the data file. The PCFL records must be in the same order as the fields they define in the data file.

Define as many as 256 PCFL records in the file-description file and start PCFL records in column 1. If you enter more than 256 PCFL records, you receive an error message. You cannot continue a record on one line, and only the first 80 characters of a record are used.

Following is an example of a PCFL entry:

PCFL CUSTNAME 1 20  CUSTOMER NAME

Each PCFL entry contains the following things:

Table 25. Data Type Indicators
Indicator Data Type
1 ASCII1
2 ASCII numeric
3 Hexadecimal
4 Binary
5 Zoned
6 Packed
7 BASIC integer
8 BASIC single-precision floating point
9 BASIC double-precision floating point
10 EBCDIC
11 EBCDIC zoned
12 EBCDIC packed
1
Includes date, time, and time stamp except for files that are not converted.

The data type indicator you enter must be valid for the file type entered earlier. Any other data types are not valid and are diagnosed as errors during a data transfer to the iSeries, eServer i5, or System i5.

Table 26 shows the valid single-byte character set (SBCS) data types for each file.

Table 26. Valid SBCS Data Types for File Types
File Type Valid Data Type
ASCII text
ASCII
ASCII
numeric
DOS random
ASCII
Binary
Hexadecimal

ASCII Packed Zoned
BASIC sequential ASCII ASCII numeric
BASIC random ASCII BASIC double-precision floating point BASIC integer BASIC single-precision floating point Hexadecimal
DIF ASCII ASCII numeric
No-conversion Binary EBCDIC EBCDIC packed EBCDIC zoned Hexadecimal
DOS random type 2 ASCII Binary Hexadecimal Packed Zoned
BIFF format ASCII ASCII numeric
Note:
ASCII (SBCS) includes date, time, and time stamp types if converted. EBCDIC includes date, time, and time stamp if not converted.

For numeric fields in BASIC sequential and DIF files, a size specification must be present. However, because the data in these fields is of variable length, the data transfer function assumes a maximum length of 65 characters. This length more than covers the largest possible exponential ASCII numeric value. The size specifications for character fields must be the maximum size of any data item in that field.

Table 27 shows the allowed data length limits for each workstation data type. These are the maximum lengths you can specify for size in the PCFL entry.

Table 27. Allowable Data Length Limits for Personal Computer SBCS Data Types
Personal Computer Data Type Data Length Limit (in Bytes)
ASCII 4093
ASCII numeric 33 (65 for DIF and BASIC sequential)
BASIC double-precision 8 (only allowed length)
BASIC integer 2 (only allowed length)
BASIC single-precision 4 (only allowed length)
Binary 4
EBCDIC 4093
Hexadecimal 2048
Packed decimal (ASCII and EBCDIC) 16
Zoned decimal (ASCII and EBCDIC) 31
Time
  • HMS 1
  • USA
  • ISO, EUR, and JIS 1
  • DDS, DFT
  • 8
  • 8
  • 8
  • 8 or 10 2
Date
  • MDY, DMY, YMD
  • Julian
  • ISO, EUR, JIS, USA (see note 1)
  • DDS, DFT
  • 8
  • 6 (only allowed length)
  • 10
  • 6, 8, or 10 2
Time stamp
  • 26
Notes:
1
These abbreviations appear in the time and date parameter sections.
HMS
Hours Minutes Seconds
EUR
IBM European Standard
JIS
Japanese Industrial Standard Christian Era
ISO
International Standards Organization
2
The length is determined by the format defined in the host file for DDS, or from the iSeries, eServer i5, or System i5 job default (DFT keyword).

Table 28 shows the allowed data length limits for each iSeries, eServer i5, or System i5 data type.

Table 28. Allowable Data Length Limits for iSeries, eServer i5, or System i5 Data Types
iSeries, eServer i5, or System i5 Data Type Data Length Limit in Bytes 1
Binary 2 or 4 (only allowed lengths)
EBCDIC 4096
Hexadecimal 2048
Packed decimal (EBCDIC) 16
Zoned decimal (EBCDIC) 31
Time
   HMS 8
   USA 8
   ISO, EUR, and JIS 8
   DDS, DFT 8 or 10 2
Date
   MDY, DMY, YMD 8
   Julian 6 (only allowed length)
   ISO, EUR, JIS, USA 10
   DDS, DFT 6, 8, or 10 2
Time stamp 26
Notes:
1
The data length limits for the workstation and the system data fields are different in some cases. For these cases, the transfer function attempts to fit the workstation data into the system field. If the data does not fit into the field, a message is displayed. Refer to Data Conversions for more details.
2
The length is determined by the format defined in the host file for DDS, or from the iSeries, eServer i5, or System i5 job default (DFT keyword).

If there is a decimal position associated with the data in that field, place a forward slash (/) and then the number of decimal positions after the length specification. There are no spaces between the length, slash, and decimal position specifications.

The decimal position specification refers to the number of positions from the right-hand byte of the resulting decimal number. Do not specify a decimal position for floating-point numbers unless the data type is one of the following types:

Note:
The number of decimal positions in a field ranges from 0 to 9 or the maximum number of decimal digits in this number, whichever is smaller. The data transfer function might round the number to fit it into the field. Refer to Data Conversions for more details.
Comment Entries

Enter comment lines anywhere in the file-description file, observing the following restrictions:

Following is an example of a comment:

* This is a comment

File-Description File Example

Following is an example of a file-description file for an inventory file:

PCFDF
PCFT 3 BASIC SEQUENTIAL FILE
* ITEM INVENTORY FILE
PCFO 1,1,1,2,1 OPTIONS SETTINGS
PCFL ITEMNO 2 8  ITEM NUMBER
PCFL ITEMDESC 1 20  DESCRIPTION OF ITEM
PCFL COLOR 1 8  COLOR
PCFL WEIGHT 2 7/2  ITEM WEIGHT
PCFL PRICE 2 7/2  PRICE PER ITEM
PCFL INSTOCK 2 6  ITEMS IN STOCK

Data Conversions

The data transfer function needs data conversions for transferring data from the system to the workstation, and vice versa. For both types of transfers, the necessary conversion depends on the record size, the type of data being transferred, the type of workstation file being used, the system data type, and, in some cases, the data length.

Record Size

Each transferred record contains data indicating whether each field contains a null value. There is a restriction on the maximum data record that can be sent or received from the iSeries, eServer i5, or System i5 because of this data.

The following formula determines the maximum record length that can be transferred:

Data Types

The data transfer function supports the following system data types:

The data transfer function supports the following workstation data types:

Date, Time, and Time-Stamp Data Types

Date, time, and time-stamp values can be used in certain arithmetic and character operations and are compatible with certain character constants, but they are neither characters nor numbers.

A date is a three-part value (year, month, and day) designating a point in time on the calendar. The range of the year is 0001 to 9999. The range of the year for a non-SAA format is 1940 to 9999. The range of the month is 1 to 12. The range of the day is 1 to x, where x depends on the month.

A time is a three-part value (hour, minute, and second) designating a time of day under a 24-hour clock. The range of the hour is 0 to 24 and the range of the other values is 0 to 59.

A time stamp is a seven-part value (year, month, day, hour, minute, second, and microsecond) that designates a date and time including the specified microseconds. The maximum length of the time stamp is a character string of 26.

Dates, times, and time stamps can be assigned to result fields. A valid character-string representation of a date can be compared with a date field, or a valid character-string representation of a time can be compared with a time field.

BASIC Numeric Data

Double-Precision Data

Double-precision data is defined only for the workstation. The iSeries, eServer i5, or System i5 does not support this data type. BASIC applications use double-precision data. This data type is a positive or negative number from 2.938735877055719 x 10-39 to 1.701411834604692 x 1038. Double-precision numbers are stored in 8 bytes, with 7 bytes representing the mantissa and 1 byte representing the exponent.

Integer Data

Integer data is defined only for the workstation. BASIC applications use integer data. Integer data is stored in 2 bytes and represents a whole number from -32768 to 32767.

Single-Precision Data

Single-precision data is defined only for the workstation. The iSeries, eServer i5, or System i5 does not support this data type. BASIC applications use single-precision data. This data type is a positive or negative number from 2.938736 x 10-39 to 1.701412 x 1038. Single-precision numbers are stored in 4 bytes, with 3 bytes representing the mantissa and 1 byte representing the exponent and sign.

Binary Data

This data represents signed or unsigned numbers in twos complement form. Binary numbers of 1, 2, 3, or 4 bytes in length are allowed on the workstation, but the iSeries, eServer i5, or System i5 allows only numbers 2 or 4 bytes in length. The bit on the left side of the high-order bit determines the sign of the number (0 for positive, 1 for negative). The system stores the data with the high-order byte on the left side of the field, whereas the workstation stores the data with the high-order byte in the right-hand position of the field.

The decimal position, if specified by the file description, represents the number of decimal digits to the right of the decimal point. The file description specifies the presence of a decimal position.

For example, the binary number 3BF5 is equivalent to the decimal number 15349, and the binary number FFB4 is equivalent to the decimal number -76.

Character Data for SBCS

You can think of this data as a string of bits that represents particular characters and symbols.

The tables used to translate characters from ASCII to EBCDIC and from EBCDIC to ASCII contain the following kinds of values:

The data transfer function uses tables to translate data from ASCII to EBCDIC and EBCDIC to ASCII. You can change these default tables using the translation table utility (TRTABLE).

Note:
ASCII (SBCS) data includes date, time, and time stamp types if converted. EBCDIC data includes date, time, and time stamp if not converted.

Hexadecimal Data

You can think of this data as a string of bits representing base 16 numbers. For example, you can represent hex 3D with the following string of bits:

0011 1101

Packed Decimal Data

For both the iSeries, eServer i5, or System i5 and the workstation, each half-byte represents a value from 0 through 9. The hexadecimal value in the half-byte on the right side of the right-hand byte specifies the sign.

For the iSeries, eServer i5, or System i5, a value of hex B or hex D in this half-byte represents a negative number.

For DOS random files, only the last half-byte (the half-byte that contains the sign) is changed. For the sign half-byte, the workstation uses hex 3 to indicate a positive number or hex B to indicate a negative number.

For example, X'0865431F' appears as X'08654313'.

For DOS random type-2 files, the last half-byte (the half-byte that contains the sign) is not changed. The sign convention used on the workstation and on the host system is the same.

For example, X'0865431C' appears as X'0865431C'.

The decimal position, if specified, represents the number of decimal digits to the right of the decimal point. The presence of a decimal position is specified in the file description.

Zoned Decimal Data

This data is represented in a form in which each byte corresponds to one decimal digit. Each of these bytes is stored in character form. For example, the digit 7 is stored on the iSeries, eServer i5, or System i5 as F7, which is the EBCDIC representation, and is stored on the workstation as 37, which is the ASCII representation.

The size of each digit is determined by its half-byte on the right side. Valid values for the half-bytes are decimal 0 through 9.

The sign in both the iSeries, eServer i5, or System i5 and workstation zoned decimal fields is specified by the hexadecimal value in the left half-byte of the right byte of the field. For the iSeries, eServer i5, or System i5, a hex B or hex D in this half-byte represents a negative number (for example, X'F6D2' represents -62).

For DOS random files, zoned decimal fields from the system change from EBCDIC to ASCII, as do character fields, except that the sign half-byte in the workstation field is changed to a hex 3 to indicate a positive number or a hex B to indicate a negative number.

For DOS random type-2 files, zoned decimal fields from the system change from EBCDIC to ASCII, as do character fields, except that the sign half-byte in the workstation field is changed to a hex 3 to indicate a positive number or a hex 7 to indicate a negative number.

The decimal position, if specified, represents the number of decimal digits to the right of the decimal point and is specified by the file description.

ASCII Numeric Data

The data transfer function defines ASCII numeric data to represent any numeric value stored in ASCII format. This is not a valid iSeries, eServer i5, or System i5 system data type. The number -123.45 in ASCII format is:

2D 31 32 33 2E 34 35

The decimal point and sign are stored explicitly for ASCII numeric data. The character on the left displays the sign (space or plus (+) for positive, minus (-) for negative). Leading zeros to the left of the decimal point change to spaces. The decimal point, if any, is added in the correct position.

BASIC sequential and DIF file types also support another form of ASCII numeric data called exponential numbers.

An exponential number is a decimal number followed by the letter E or D and a signed integer of two or three digits. E represents a single-precision number and D represents a double-precision number. The exponent portion (E or D and the integer) represents "times 10 to the power of the integer specified".

For example, the number -1.0E+03 (representing -1.0 x 103 in ASCII numeric format) is:

2D 31 2E 30 45 2B 30 33

For example, the number 9.5D-15 (representing 9.5 x 10-15 in ASCII numeric format) is:

39 2E 35 44 2D 31 35

Personal Computer File Types

The following workstation file types are supported:

ASCII Text Files

ASCII text files are normally used with programs that work with text (such as editors and print routines). The characteristics of an ASCII text file are as follows:

Transferring Data to ASCII Text Files

When you create an ASCII text file, the data coming from the iSeries, eServer i5, or System i5 changes as follows:

Table 29. Binary-to-ASCII Field Length Mapping
Binary Length ASCII Length   Value Range
2 6 -32768 to 32767
4 11 -2147483648 to 2147483647
Transferring Data from ASCII Text Files

When you transfer data from ASCII text files to system files, the data changes as follows:

Errors When Transferring Data from ASCII Text Files

When you transfer data from a workstation ASCII text file to an iSeries, eServer i5, or System i5 file, the following errors can occur:

When you transfer data from an ASCII text file to an iSeries, eServer i5, or System i5 file without using a file-description file, any extra data found past the record length specified for the file is not transferred.

BASIC Random Files

BASIC random files are the most general-purpose BASIC file type. They contain fixed-length records with:

Transferring Data to BASIC Random Files

When you create a BASIC random file, system data changes as follows:

Transferring Data from BASIC Random Files

When you transfer data from BASIC random files to system files, the data changes as follows:

Note:
Because the change of floating-point numbers into decimal fractions is not always exact, each number automatically changes into the most precise number possible with respect to the system field length. If you want more precision, specify a larger system field size.
Errors When Transferring Data from BASIC Random Files

When you transfer data from a workstation BASIC random file to a system file, the following errors can occur:

When you transfer data from a BASIC random file to an iSeries, eServer i5, or System i5 file, any data shorter than the record length defined for the system file is padded with EBCDIC spaces.

Because there are no record delimiters in BASIC random files, this error can occur only on the last record of the file. This probably indicates that the record length of the system file does not match the record length of the workstation file.

BASIC Sequential Files

BASIC uses BASIC sequential files for sequential processing (for example, INPUT and WRITE statements). The fields written are considered either character or numeric. Characteristics of BASIC sequential files are as follows:

Transferring Data to BASIC Sequential Files

The following list describes how iSeries, eServer i5, or System i5 data created by a BASIC-sequential-file-defined data definition changes:

Transferring Data from BASIC Sequential Files

When you transfer data from BASIC sequential files to iSeries, eServer i5, or System i5 files, the data changes as follows:

Errors When Transferring Data from BASIC Sequential Files

When you transfer data from a BASIC sequential file to a iSeries-, eServer i5-, or System i5-defined file, the following errors can occur:

Data Interchange Format Files

Data Interchange Format (DIF) files represent data in rows and columns. DIF files contain character and numeric data (positive and negative decimal numbers).

DIF is used for data interchange between spreadsheet programs and other application programs.

The data transfer function supports only the following two data types within DIF files:

Transferring Data to DIF Files

When creating a DIF file, system data changes as follows:

Transferring Data from DIF Files

If an error cell is found when data is transferred from a DIF file to the iSeries, eServer i5, or System i5, one of the following things can occur, depending on the type of data in the file:

When you transfer data from a system file to a DIF file, the field names are placed in the first record and you can consider them column headings. When you transfer DIF files back to the system, the first row must either be these field names (exactly as they are defined on the system) or data. If the first row does not consist of field names, the file is processed as if it contains only data.

No DIF header information is used when sending the file to the iSeries, eServer i5, or System i5. To correctly transfer a DIF file to the system, ensure that the file is in the correct format (row and column). It is essential that the field names, if present, make up the first row of data. The subsequent records make up the remaining rows of data. Therefore, when you transfer the data to the iSeries, eServer i5, or System i5, the file must be saved in the same format as originally created by the data transfer function.

When you transfer data from DIF files to iSeries, eServer i5, or System i5 files, the data changes as follows:

Errors When Transferring Data from DIF Files

When you transfer data from a workstation DIF file to a system file with data definitions, the following errors can occur:

BIFF Files

The BIFF file format is used by Microsoft Excel. In a BIFF file, data is expressed in lines and columns. A BIFF file contains character and numeric data (both positive and negative decimal values).

BIFF format versions 4 and 8 are supported for 5250 Data Transfer. Both BIFF4 and BIFF8 support 256 columns, which is the maximum for a Microsoft Excel worksheet. Documentation on both formats is freely available from the Microsoft Web site.

BIFF4 handles data for Microsoft Excel V2, V3, and V4. The format supports a maximum of 16 384 rows.

BIFF8 is a superset of BIFF4 and stores data as an OLE compound document. BIFF8 handles data for Microsoft Excel V5, V7 (Excel 95), V8 (Excel 97), and V9 (Excel 2000). The format supports a maximum of 65 536 rows.

The transfer facility supports only the following two data types for a BIFF file:

Transferring Data to BIFF Files

When a BIFF file is created, the system data is converted to equivalent Excel cell data.

If untranslatable data is found, the entire field is treated as an error cell.

Transferring Data from BIFF Files

If an error cell is found during data transfer from a BIFF file to the iSeries, eServer i5, or System i5, either of the following things can occur depending on the data type of the file:

When you transfer data from a system file to a BIFF file, the first record contains field names, which can be treated as column headers.

To return a BIFF file to the system, the first line must contain these field names (as defined in the system) or data. If the first line does not contain field names, the file is regarded as containing data only.

When a file is sent to the iSeries, eServer i5, or System i5, cell information (such as the character size and font information) is ignored. This means that cell information is lost, even if the contents of a BIFF file that have been sent to the iSeries, eServer i5, or System i5 are retransmitted to a workstation.

When you transfer data from a BIFF file to an iSeries, eServer i5, or System i5 file, the data is converted as follows:

When you transfer data from a BIFF file to the iSeries, eServer i5, or System i5, the following specific processing is performed:

Errors When Transferring Data from BIFF Files

When you transfer data from a BIFF file on a workstation to the system file with the data definition, the following errors can occur:

DOS Random Files

DOS random files are fixed-length files used by the DOS random read and write routines. The characteristics of DOS random files are as follows:

Note:
DOS random and DOS random type-2 files are identical, except for the way in which the signs are represented for packed decimal and zoned decimal numbers.
Transferring Data to DOS Random Files

When creating DOS random file data definitions, system data changes as follows:

Transferring Data from DOS Random Files

When you transfer data from DOS random files to iSeries, eServer i5, or System i5 files, the data changes as follows:

Errors When Transferring Data from DOS Random Files

When you transfer data from a DOS random file to an iSeries, eServer i5, or System i5 file, the following errors can occur:

When you transfer data from a DOS random file to a system file without data definitions, any data shorter than the record length defined for the system file is padded with EBCDIC spaces.

Because DOS random files have no record delimiters, this error occurs only on the last record and probably indicates that the record length of the system file does not match that of the workstation file.

DOS Random Type-2 Files

DOS random type-2 files are fixed-length files used by the DOS random read and write routines. The characteristics of DOS random type-2 files are as follows:

Note:
This workstation file type is identical to the DOS random file type, except that the internal sign representation for packed decimal and zoned decimal data types follow Systems Application Architecture (SAA) standards. Some workstation applications, such as applications written in IBM COBOL/2 programming language, need to have the signs for packed decimal and zoned decimal data types represented this way. Use the DOS random type-2 file type for those workstation applications.
Transferring Data to DOS Random Type-2 Files

When you create DOS random type-2 file data definitions, system data changes as follows:

Transferring Data from DOS Random Type-2 Files

When you transfer data from DOS random type-2 files to iSeries, eServer i5, or System i5 files, the data changes as follows:

Errors When Transferring Data from DOS Random Type-2 Files

When you transfer data from a DOS random type-2 file to an iSeries, eServer i5, or System i5 file, the following errors can occur:

When you transfer data from a DOS random type-2 file to a system file without data definitions, any data shorter than the record length defined for the system file is padded with EBCDIC spaces.

Because DOS random type-2 files have no record delimiters, this error occurs only on the last record and probably indicates that the record length of the system file does not match that of the workstation file.

No-Conversion Files

No-conversion files, defined by the data transfer function, consist of data that has not changed. For example, when data transfers from the system to a workstation no-conversion file, the data transfers exactly as it is stored on the iSeries, eServer i5, or System i5. Date, time, and time-stamp data transfers to EBCDIC character data on the workstation.

Transferring Data to No-Conversion Files

When you transfer data from the iSeries, eServer i5, or System i5 to a no-conversion file, the data transfers exactly as it is stored on the system.

Variable-length iSeries, eServer i5, or System i5 fields are converted to fixed-length fields, and trailing EBCDIC blanks are added to the maximum length of the field.

Date, time, and time-stamp data is converted to EBCDIC character data.

Variable-length and null fields are converted to fixed length, and trailing EBCDIC blanks (for character, hex, date, time, and time stamp) or EBCDIC zeros (for binary, zoned, and packed) are added to the maximum length of the field.

Transferring Data from No-Conversion Files

The data types that exist in a no-conversion file are EBCDIC system data types only. When a no-conversion file transfers to the system, the data transfer function performs no data change or translation. Date, time, and time-stamp data transfers to EBCDIC character data on the workstation.

However, the data transfer function verifies that all numeric data is in the correct EBCDIC format. If any numeric data is found that is not in the correct EBCDIC format, that data and any remaining data does not transfer.

Errors When Transferring Data from No-Conversion Files

When you transfer data from a workstation no-conversion file to a system file, the following errors can occur:

iSeries, eServer i5, or System i5 System-to-PC Performance Considerations

Transferring data from the iSeries, eServer i5, or System i5 to the workstation depends on the following performance considerations:

These factors and others influence the time needed to determine which data should be transferred. For example, the time needed to receive the first record of a transfer in which all the records are chosen is less than the time needed to start transferring a smaller group of records based on complicated WHERE or HAVING values. However, transferring all the records in a large file is sometimes impractical or unnecessary.

The iSeries-to-workstation data transfer function uses many functions within the iSeries, eServer i5, or System i5 to determine the fastest method of selectively retrieving records. When it selects a smaller group of records to transfer, the iSeries-to-workstation data transfer function uses the existing access paths whenever possible to improve performance.

For the iSeries-to-workstation data transfer function to consider using an existing access path (logical file), the access path must meet the following conditions:

When you meet these conditions, you must then match the transfer request to the access path. The following considerations might be helpful when you define your transfer request: