File distribution attributes
When IBM® MQ Managed File Transfer transfers files to a destination agent running on an IBM 4690 store controller, it must set the file distribution attributes of the files. These distribution attributes determine whether the IBM 4690 store controller duplicates the file's contents with other store controllers and how it duplicates the file's contents in a Multiple Controller Feature (MCF) Network. IBM MQ Managed File Transfer file distribution attributes combine MCF's file type and file mode attributes.
- Using the Add transfer item panel in IBM MQ Explorer.
- Using the -dfa parameter on the fteCreateTransfer command.
If you do not specify the -dfa parameter for a transfer with a 4690 destination, the default distribution attribute is LOCAL. If the file already exists at the destination, the current distribution attribute of the existing file is used.For more information, see Parameters for specifying the destination.
|Symbolic value||Numeric value||Description|
A local file exists on one store controller only. When a local file is updated, other store controllers in the network are not affected.
|DIST(MIRRORED,UPDATE)||DIST(2)||Mirrored file, distribute at update
A mirrored file exists on two store controllers and consists of a prime version and an image version. When a record in the prime version of the file is changed or deleted, the same record in the image version is also changed or deleted.
|DIST(MIRRORED,CLOSE)||DIST(3)||Mirrored file, distribute at close
A mirrored file exists on two store controllers and consists of a prime version and an image version. When the prime version of the file is closed, the image version of the file is then updated.
|DIST(COMPOUND,UPDATE)||DIST(4)||Compound file, distribute at update
A compound file is distributed to all store controllers except ineligible subordinate store controllers. When a record in the prime version of the file is changed or deleted, the same record in the image versions of the file is also changed or deleted.
|DIST(COMPOUND,CLOSE)||DIST(5)||Compound file, distribute at close
A compound file is distributed to all store controllers except ineligible subordinate store controllers. When the prime version of the file is closed, the image versions of the file are then updated.
For more information about MCF, see Chapter 22, "Using the Multiple Controller Feature" in 4690 OS Version 6 Release 3 User's Guide.
Directory requirements for using file distribution
For files to be distributed as you expect, ensure that the same directory structure exists on all the store controllers in the network. Typically, this directory structure is created on the store controllers by the operating system or the user at installation. If the directory structure is not replicated on all controllers, the distribution fails for the controllers that do not have the required directories. Distribution failures are ignored and not logged.
For example, if files with a distribution attribute MIRRORED,UPDATE are transferred to IBM 4690 and the destination agent creates directories, the files transferred to those new directories are not distributed because the directories on the other controllers are not created by IBM MQ Managed File Transfer.
Drives that support distribution
Distributed files can only be located in directories off the root directory and normally are only found in directories created by the operating system during installation. Generally, distributed files are located on drives that use the 8.3 naming convention, that is, drives C: and D:. Files with distribution attributes are not supported on the F: drive. The logical drives M: and N: are the exceptions because they are created using the 4690 Virtual File System, which was created to support long file and directory names.
|IBM 4690 drive letter||Supports file distribution?|
Information on the logical M: drive is stored on the C: drive using VFS
Information on the logical N: drive is stored on the D: drive using VFS