Transferring Data to Existing Members in an Existing File
- When data is transferred to an existing member, data in that member is replaced with that transferred from a workstation.
- When iSeries, eServer i5, or System i5 members already contain data, a message appears, indicating that the data in the existing members will be replaced with the data that is about to be transferred.
- Consider the effect of returning data that was previously transferred
from the iSeries, eServer i5,
or System i5 (such as when an iSeries, eServer i5,
or System i5 master file is updated on a workstation).
For example, you can transfer only the field subset of an iSeries, eServer i5, or System i5 file by issuing a transfer request from the iSeries, eServer i5, or System i5 to a workstation. In this case, when returning data from the workstation to the iSeries, eServer i5, or System i5, only the subset included in that iSeries, eServer i5, or System i5 file can be transferred. Other fields that had been defined in the iSeries, eServer i5, or System i5 file but not transferred, are filled with blanks if they are character fields or, if they are numeric fields, with zeros or the values specified at file creation.
Therefore, the data must be transferred to another iSeries, eServer i5, or System i5 file and the transferred data must be embedded in the iSeries, eServer i5, or System i5 file by running the iSeries, eServer i5, or System i5 application program. Follow this procedure to control the update processing for an iSeries, eServer i5, or System i5 master file.
To prevent users from transferring data to a certain iSeries, eServer i5, or System i5 file, check that the authority level for that file is defined correctly.