About Cross-OS File Exchange Operations
Hitachi USP V Cross-OS File Exchange User’s Guide
Warning: Do not write a signature on FX Volumes having emulation types 3390-3X, or 3390-9X,3390-LX, or 3380-KX,3380-3X (X=A,B,C) in a Windows 2000/2003/Windows NT environment. If a signature-writing attempt is made by the Disk Administrator with Windows 2000/2003/Windows NT, a Write Error will appear in order to stop the signature from being written. When the Windows 2000/2003/Windows NT Disk Administrator starts again, a request will be made again to write the signature. Do not write the signature.
FCU File Transfer Options
For each FX operation, FCU requires that the transfer direction (mto or otm) and the source and target files be identified. (An FXoto operation consists of one FXotm operation followed by one FXmto operation.) In addition to these required parameters, FCU provides the following options for FX file transfer operations:
Notes for Windows 2000/2003/Windows NT:
When the UserID is not the root, a patch is required. AIX V5.1 can be used with 64bitFAL.
Please contact your IBM technical representative for assistance.
Note for Microsoft Cluster Server: When installing FX devices in a Microsoft Cluster Server (MSCS) environment, you must write signatures on the FX volumes before configuring MSCS.
•
•
Note for AIX: notes apply:
When installing FX devices in an AIX environment, the following
•The MSCS server cannot connect volumes that do not have signatures.
•The volume on which a signature is written cannot be accessed from another server.
•The volume on which a signature is written cannot be shared.
•Only the mainframe and the server that wrote the signature can access the volume that has the signature.
•Signatures cannot be written to FX volumes for which the emulation type is 3390-3X, 3390-9X3390-LX , or 3380-KX, 3380-3X(X = A, B, C), when the OS server is Windows 2000/2003/Windows NT.
•When configuring MSCSand the server OS is Windows 2000/2003/Windows NT, FXotm and FXmto cannot be started.
•Service Pack 1 must be installed when MSCS is configured
•A signature is not necessary for the MSCS configuration. A Write Error will occur if a signature is attempted.
2-7
