Messages for file transfer and file management commands

All the messages listed below, with the exception of the message with exit code 5, can also be output during logging. In this case, however, the specified code is increased by 2000, e.g. 2169 instead of 169.

5	Request <Request id>. File '<local file>' transferred Meaning: The file transfer request <Request id> has been successfully completed. Follow-up processing has been started for both the local system and the remote system, as requested, provided no error occurred. Local errors are indicated as a message.
6	Request <Request id>. Directory '<local file>' transferred Meaning: The directory transfer request <Request id> has been successfully completed. Follow-up processing has been started for both the local system and the remote system, as requested, provided no error occurred. Local errors are indicated as a message.
14	No file attribute changes requested Meaning: No further file attributes besides the file name were specified. Measure: Enter the desired file attributes in addition to the file name.

15	openFT is not authorized to execute requests for this user Meaning: The user has not informed openFT of his or her logon password or an openFT command has been called by a user other than the user under which the openFT service is running when a service has been started under user rights. Measure: Store the password or call the command from the ID under which the openFT service is running in another operating mode.
16 17	Directory '<local file>' is not empty File attributes do not match request parameters Meaning: The specified attribute combination is not permissible. Measure: Specify a permissible combination.
18	Attributes could not be modified Meaning: The properties of the file could not be changed as specified in the command. The following reasons are possible: For the remote file: No access rights to the file. The required combination of access rights is not supported by the remote system. If the remote system is a BS2000: the file is protected by ACL. For the local file: No access rights to the file. The requested transfer attributes are not compatible with the BS2000 properties of the file.
19	'<local file>' could not be created Meaning: The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Measure: Match the user ID in the receiving system's transfer admission to the ID of the receive file's owner. Repeat the command.

20	'<local file>' not found Meaning: The command was not executed because the send file is not in the catalog or on a volume of the local system. The command was not executed because either the send file is not/no longer or the receive file is no longer in the catalog or on a volume of the relevant system. Measure: Correct the file name, read in file from tape or restore the send file. Repeat the command.
21	CCS name unknown Meaning: The request could not be carried out because the CCS names of the send and receive files could not be mapped to each other or because the partner system does not support the transparent receipt of files.
22	Higher-level directory not found Meaning: In the case of a receive request, the local file could not be created because the specified path does not exist. Measure: Create or correct the path for the receive file and repeat the command.
23	'<local file>' already exists Meaning: The command was not executed because an existing receive file cannot be created again with option -n. Option -n may also have been set due to a restriction in the access authorization used. Measure: Either delete the receive file and repeat the command, or repeat the command specifying option -o or using different access authorization.
24	Transfer of file generation groups not supported Meaning: The command was not executed because the FT system only transfers single file generations. Measure: Repeat the command using the name of a single file generation.

25	Error accessing '<local file>' <2> Meaning: <2>: DMS error, possibly the transfer ID. The FT system continues to run after the message has been issued. Measure: Take the appropriate action in accordance with the error code.
26	Resulting file name'<local file>' too long Meaning: The relative file name was specified in the transfer request. The absolute file name completed by openFT is longer than permitted. Measure: Shorten the file name or path and repeat the command.
27	No file or directory name specified Meaning: The command was not executed because the file name was neither specified explicitly nor by the 'transfer admission' used. Measure: Repeat the command, specifying the file ID explicitly or a transfer admission that defines the file ID.
28 29	Invalid management password '<local file>' not available Meaning: The command was not executed because the volume for either the send file or the receive file is not mounted, unknown or reserved, or the file extends over more than one private disk. Measure: Inform the operator if necessary. Repeat the command.
30 31	Home directory not found Renaming not possible

32	Not enough space for '<local file>' Meaning: The command was not (fully) executed because the permissible storage space on the receive system is used up for the user ID specified in transfer admission, or the send file contains too long a sequence of empty blocks, or the primary and/or secondary allocation of the password-protected receive file is too small. The receive file can not be created/extended after the problem occurs. Measure: Take the appropriate action depending on the cause of the error: delete all files no longer required on the receive system, or ask the system administrator to allocate more storage space, or remove empty blocks from the send file, or increase the receive file's primary/secondary allocation. If option -e is specified, restore the receive file. Repeat the command.
33	File owner unknown Meaning: The command was not executed because the owner of either the send file or the receive file was not defined in the local system or because the file owner and the user requesting the creation of a receive file are not the same. Measure: Define the file owner, correct transfer admission or file name. Repeat the command.
34	Invalid file password Meaning: The command was not executed because the password for the send file or the receive file is missing or incorrect. Measure: Correct the password in the file description or the command. Repeat the command.

35	File locked to prevent multiple access Meaning: The command was not executed because either the send file or the receive file is already locked by another process to prevent it from being updated simultaneously. Measure: Repeat the command later or unlock the file. After a system crash you may need to verify files that are not closed correctly. If the lock is caused by an FT request, it will be canceled automatically when the request is finished.
36	Retention period of file not yet expired Meaning: The command was not executed because the retention period protecting the receive file against overwriting has not yet expired (RETENTION PERIOD). Measure: Correct the transfer direction, retention period or file name. Repeat the command.
37 38 39	'<local file>' is read only File structure not supported Syntax error in resulting file name '<local file>' Meaning: The local file cannot be accessed because, for example, the absolute file name is too long. Measure: Shorten the path or file name. Repeat the command.
40	Transparent file transfer not supported Meaning: The request could not be carried out because the CCS names of the send and receive files cannot be mapped to each other or because the partner system does not support the receipt of files in a transparent format.
41	Request queue full Meaning: The command was not executed because the maximum number of permissible file transfer requests has been reached. Measure: Notify the FT administrator. Repeat the command later.

42	Extension of file not possible for transparent transfer Meaning: The command could not be executed because it is not possible to add to a file in a transparent transfer. Measure: Start transfer without option -e.
43	Access to '<local file>' denied Meaning: The command was not executed because either the send file or the receive file only permits certain access modes (e.g. read only). Measure: Correct the file name or file protection attributes. Repeat the command.
44	Follow-up processing exceeds length limit Meaning: Prefix + suffix (from prof) + local follow-up processing together are too long. Measure: Shorten the follow-up processing, or use procedures. Repeat the command.
45	Processing admission invalid Meaning: The command was not executed because the specifications in one of the PROCESSING-ADMISSION operands were incorrect. Measure: Define the required PROCESSING ADMISSION or correct it. Repeat the command if necessary.
46	Local transfer admission invalid Meaning: The command was not executed because the specifications in one of the transfer admission operands were incorrect. Measure: Define the required transfer admission or correct it. Repeat the command if necessary.

47	Request rejected by local FTAC Meaning: The command was not executed because the request was rejected by the FTAC due to a lack of authorization. Measure: Use the return code in the log record to determine and remove the cause. Repeat the command.
48	Function not supported for protocol '<partner protocol type>' Meaning: The desired function is not available for the selected protocol. Measure: Select a different protocol.
49	Remote follow-up processing not supported Meaning: Remote follow-up processing is only available for the openFT protocol. Measure: Select a different protocol, or specify follow-up processing by means of an admission profile.
50	Data integrity check not supported Meaning: The partner system does not support the data integrity check function. Measure: Repeat the request without a file integrity check.
51	User data encryption not possible for this request Meaning: The partner system does not support the data encryption function. Measure: Repeat the request without data encryption or install openFT-CR (or have it installed) on the remote system.

52	Administration request rejected by remote administration server Meaning: The administration request was rejected by the remote administration server because it clashes with the settings in the configuration file of the remote administration server. The ADM administrator can determine the precise reason for rejection from the associated ADM log record on the remote administration server. Possible reason codes:
	7001	The administrator ID is invalid. It was not possible to determine a valid administrator ID from the user ID or the profile name in the configuration data of the remote administration server.
	7002	The routing information is invalid. The specified openFT instance specified in the routing information could not be found in the configuration data of the remote administration server.
	7003	The specified remote administration command is invalid. The remote administration server rejects the specified command because it is not a supported remote administration command.
	7101	Infringement against the access rights list. On checking the access rights, the system identified that the administrator ID has not been assigned the necessary rights in the configuration data of the remote administration server to be able to execute the valid remote administration command on the specified openFT instance.
	7201	Infringement against the maximum command length. In particular in the case of BS2000 commands, the remote administration server replaces the shortest command names, which are guaranteed by openFT, by the full command names. If this replacement of the command name causes the entire remote administration command to become longer than the maximum command length of 8192 characters, the command is rejected.
	Measure: Have the ADM administrator carry out the necessary adjustments to the configuration data or check the command. Repeat the changed command if necessary.
54	Invalid command Meaning: The specified command is not a command that is permitted to be executed on the specified system using the remote administration facility. Measure: Specify an admissible command or add the missing routing information.  Repeat the command.

55 56 57	Transfer of protection attributes not supported Syntax error in partner name ’<partner>’ openFT is not authorized to execute administration requests Meaning: openFT is not (no longer) authorized to process administration requests. This is, for example, the case if a remote administration server has been demoted to a normal server (ftmodo -admcs=n) or if commands that are only allowed to be executed on a remote administration server are processed by an openFT instance that has not been configured as a remote administration server.
70	Request <Request id>. openFT is no longer authorized to execute requests for this user Meaning: The user has not informed openFT of his or her logon password or an openFT command has been called by a user other than the user under which the openFT service is running when a service has been started under user rights. Measure: Store the password or call the command from the ID under which the openFT service is running in another operating mode.
71	Request <Request id>. User data encryption not installed Meaning: The user data encryption function cannot be used unless openFT-CR is installed. Measure: Use openFT-CR.
72	Request <Request id> has been canceled Meaning: The FT request was canceled because the ftcanr command was specified, or the time specified in the transfer request has been reached. Follow-up processing has been started for the local system, provided no error occurred. Follow-up processing is started for the remote system once all the resources are allocated. Local errors are indicated by the message FTR0050 at the start of follow-up processing.
73	Request <Request id>. Encryption error Meaning: Encryption not possible.

74	Request <Request id>. '<local file>' could not be created Meaning: The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Measure: Match the user ID in the receive system's transfer admission to the ID of the receive file owner. Repeat the command.
75 76	Request <Request id>. Higher-level directory no longer found Request <Request id>. I/O error for '<local file>' Meaning: The file can no longer be accessed. It may have been deleted during a transfer. Measure: Repeat the request.
77	Request <Request id>. File now locked to prevent multiple access Meaning: The command was not executed because the send file or the receive file is already locked by another process so that it cannot be simultaneously updated. Measure: Repeat the command later or unlock the file. After a system crash you may need to verify files that are not closed correctly. If the lock is caused by an FT request, it will be released automatically when the request is finished.
78	Request <Request id>. '<local file>' no longer available Meaning: The command was not executed because the volume for either the send file or the receive file is not mounted, unknown or reserved, or the file extends over more than one private disk. Measure: Inform the operator if necessary. Repeat the command.

79	Request <Request id>. '<local file>' no longer found Meaning: The local send or receive file can no longer be accessed because, for example, it was deleted during an interruption of the openFT system. Measure: Restore the file. Repeat the command.
80 81	Request <Request id>. Home directory no longer found Request <Request id>. '<local file>' gets no more space Meaning: The command was not (any further) executed because the permissible storage space on the receive system for the user ID specified in transfer admission has been used up, or the send file contains too long a sequence of empty blocks, or the primary and/or secondary allocation of the password-protected receive file is too small. The receive file can not be created/extended once this problem occurs. Measure: Take the appropriate action depending on the cause of the error: delete all files no longer required on the receive system, or ask the system administrator to allocate more storage space, or remove empty blocks from the send file, or increase the receive file's primary/secondary allocation. If option -e is specified, restore the receive file. Repeat the command.
82	Request <Request id>. File owner no longer known Meaning: The command was not executed because the owner of the send file or receive file is not defined on the relevant system or because the file owner and the user who wants to create a receive file are not the same. Measure: Define the file owner, or correct transfer admission or file name. Repeat the command.

83	Request <Request id>. Pre-/post-processing error Meaning: The command executed as part of local pre-/post-processing returned an exit code other than 0. Measure: Correct and repeat the command.
84	Request <Request id>. Exit code <2> for pre-/post-processing Meaning: The command executed as part of local pre-/post-processing returned the exit code <2>. Measure: Correct the command using the exit code <2> and issue it again.
85	Request <Request id>. File password no longer valid Meaning: The command was not executed because the password for send file or the receive file is missing or incorrect. Measure: Correct the password in the file description or the command. Repeat the command.
86 87	Request <Request id>. '<local file>' is now read only Request <Request id>. File structure error Meaning: The command was not executed due to a file structure error. File structure errors include: The attributes of the send file are incomplete. The data of the send file is incompatible with its structure attributes. The records of the send file are too long. If -e is specified, the send file and receive file have different structures (e.g. fixed-/variable-length records). The send file or receive file is a member of an old LMS library (not PLAM). The source file has an odd block factor (e.g. BLKSIZE=(STD,1)) and the receive file is to be stored on an NK4 pubset. Measure: Correct the file or file attributes. If option -e is specified, restore the receive file. Repeat the command.

88	Request <Request id>. NDMS error <2> Meaning: The request was rejected because the partner system currently does not have the resources available to accept requests. Measure: Repeat the request a little later.
89	Request <Request id>. Recovery failed Meaning: The restart attempts were unsuccessful (for example, a pre-/post-processing command could not be completed before the termination of openFT). Measure: Repeat the command.
90	Request <Request id>. Error in file transfer completion Meaning: An error occurred during the final phase of the file transfer. If it was a long transfer, the recipient is advised to check if the file has still been transferred correctly. However, error follow-up processing will be started if it was specified. Measure: Repeat the request, if necessary.
91	Requests only partially completed; <1> of <2> files were transferred Meaning: In the case of a synchronous send request with wildcards, not all files were successfully transferred. Measure: Transfer unsuccessfully transferred files again.
92 93 94 95 96 97 99	Request <Request id>. Access to ’<local file>’ no longer permissible Request <Request id>. FTAM error <2> Request <Request id>. Retention period of file not yet expired Request <Request id>. Extension of file not possible for transparent transfer Request <Request id>. File structure not supported Request <Request id>. Resulting file name ’<local file>’ too long Request <Request id>. Transfer of protection attributes not supported

108	Request <Request id>. Remote system not accessible Meaning: The command could not be accepted because the partner system is currently not available. Measure: Repeat the command later. If the error persists, contact the system or network administrator.
109 110	Request <Request id>. Connection setup rejected by local transport system Request <Request id>. Data integrity check indicates an error Meaning: The integrity of the data was violated.
111	Encryption/data integrity check not possible. Encryption switched off Meaning: There is no key pair set or the key length was set to 0. Requests can only be carried out without data encryption or a data integrity check. Measure: Repeat the request without data encryption, create a key or set a key length >0.
112	Request <Request id>. Data integrity check not supported by partner Meaning: The partner system does not support the data integrity check. Measure: Repeat the request without a data integrity check.
113	Request <Request id>. User data encryption not possible for this request Meaning: The partner system does not support the data encryption function. Measure: Repeat the request without data encryption or install openFT-CR (or have it installed) on the remote system.

114	Request <Request id>. Identification of local system rejected by remote system '<partner>' Meaning: For security reasons or because of an inconsistency, the partner did not accept the instance identification of the local system (for example, because in the partner list both the instance identification and migration identification %.processor.entity occur for different partners). Measure: Ensure that the local identification has been entered correctly on the partner system and has not been assigned to a different partner.
115 116	Request <Request id>. Interrupted by remote system Local application '<1>' not defined Meaning: The local application is not defined in the transport system, or the tnsxd process is not running in the Unix system. Measure: Make the local application known to the local transport system, or start the tnsxd process.
117 118	Local application '<1>' not available Request <Request id>. Authentication of local system failed Meaning: The local system could not be authenticated by the partner system. Measure: Give the current public key file to the partner and name it correctly there. Repeat the command.
119	Request <Request id>. Local system unknown in remote system Meaning: The local system is not known on the partner system (e.g. BS2000 or z/OS system). Measure: Make the local system known on the partner system and repeat the command.

120	Remote system '<partner>' unknown Meaning: The partner specified as the remote system cannot be expanded to an address on the local system. Measure: Correct the specification for the partner or add the partner to the partner list and repeat the command.
121	Request <Request id>. Authentication of partner failed Meaning: The remote system could not be authenticated by the local system. Measure: Get the current public key file from the partner and name it correctly.
122	Request <Request id>. FT session rejected or disconnected. Reason <2>
123	Request <Request id>. OSS call error <2> Meaning: The command was not executed because the session instance detected a communication error. <2>: error code. Measure: Take the appropriate action in accordance with the error code.
124	Request <Request id>. No free connection Meaning: No more transfers are possible because the maximum number of simultaneous transfers has been reached. Measure: Check whether the transport system is working (or have it checked).
125	Request <Request id>. Connection lost Meaning: No data transfer took place because of a line interrupt or a line protocol error. Measure: Repeat the request.

126	Request <Request id>. Transport system error. Error code <2> Meaning: An error occurred in the transport system during processing of a /START-FT command or ftstart or a file transfer or file management request. Measure: Take the appropriate action in accordance with the error code. Most often the occurrence of this message indicates that the partner addressed is not known to the transport system. Contact system administrator to make sure there is an entry for the partner system.
127	Request <Request id>. No data traffic within <2> seconds Meaning: No data transfer took place within the period of seconds specified because, for example, the connection is interrupted, the partner is not sending and the local system is waiting for data. Measure: Repeat the request.
140	Request <Request id>. Remote system: openFT is not authorized to execute requests for this user Measure: If the remote system is a Windows system: Declare the password of the user to openFT (e.g. using the ftsetpwd command).
141	Request <Request id>. Remote system: Directory '<remote file>' is not empty Meaning: The command could not be executed because there are files in the specified directory of the partner system. Measure: Delete all the files in the directory first and repeat the command.

142	Request <Request id>. Remote system: File attributes do not match the request parameters Meaning: The command could not be executed because the file attributes on the remote system do not agree with the request parameters (e.g. a directory was specified instead of a remote file). Measure: Check the file name on the remote system and correct it. Repeat the command.
143	Request <Request id>. Remote system: Attributes could not be modified Meaning: The properties of the file could not be modified as desired in the command. Possible reasons are: For the remote file: No access rights to the file. The combination of access rights required is not supported by the remote system. If the remote system is a BS2000: the file is protected by ACL.
144	Request <Request id>. Remote system: File/directory '<remote file>' could not be created Meaning: The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Measure: Match the user ID in the receive system's transfer admission to the ID of the receive file owner. Repeat the command.
145	Request <Request id>. Remote system: CCS name unknown or not supported Meaning: The request could not be carried out because the CCS names of the send and receive files cannot be mapped to each other or because the partner system does not support the receipt of files in a transparent format.

146	Request <Request id>. Remote system: Higher-level directory not found Meaning: The command was not executed because the higher-level directory could not be found on the partner system. Measure: Create the directory on the remote system or correct the remote directory name and repeat the command.
147	Request <Request id>. Remote system: File/directory '<remote file>' already exists Meaning: The command was not executed. Possible reasons: The command was not executed because an existing receive file cannot be created with the -n option. -n may also have been set by a restriction in the access authorization used. ftcredir: The specified directory already exists. Measure: Either delete the receive file before repeating the command or reenter the command specifying option -o or using different access authorization.
148	Request <Request id>. Remote system: Transfer of file generation groups not supported Meaning: The command was not executed because the FT system can only transfer single file generations. Measure: Repeat the command using the name of a single file generation.
149	Request <Request id>. Remote system: Access error for ’<remote file>’ <3> Meaning: <3>: DMS error, possibly the transfer ID The FT system continues to run after output of the message. Measure: Take the appropriate action in accordance with the error code.

150	Request <Request id>. Remote system: Resulting file name too long Meaning: A syntax error other than 'Mandatory parameter missing' (703) or 'keyword unknown' has been detected. Possible reasons: Values assigned outside the valid range Invalid operand separators Invalid value assignment characters Partially qualified file names Measure: Repeat the command using the correct syntax.
151	Request <Request id>. Remote system: File locked to prevent multiple access Meaning: The command was not executed because either the send file or the receive file is already locked by another process to prevent it from being updated simultaneously. Measure: Repeat the command later or unlock the file on the remote system. After a system crash in BS2000 you may need to call VERIFY for files not closed correctly. If the lock is caused by an FT request, it will be released automatically when the request is finished.
152	Request <Request id>. Remote system: No file or directory name specified Meaning: The command was not executed because the file ID was neither specified explicitly nor by the transfer admission used. Measure: Repeat the command, specifying the file ID explicitly or using a transfer admission that defines the file ID.
153 154	Request <Request id>. Remote system: Invalid management password Request <Request id>. Remote system: File/directory '<remote file>' not available Meaning: The command was not executed because the volume for either the send file or the receive file is not mounted, unknown or reserved, the file extends over more than one private disk, or an attempt has been made to transfer a file migrated by HSMS. Measure: Inform the operator if necessary or carry out an HSMS recall for the file. Repeat the command.

155	Request <Request id>. Remote system: File/directory '<remote file>' not found Meaning: The command was not executed because the send file is not or no longer in the catalog or on a volume of the remote system. Measure: Correct the remote file name, read the file in from tape or restore the send file. Repeat the command.
156 157 158	Request <Request id>. Remote system: Home directory not found Request <Request id>. Remote system: Renaming not possible Request <Request id>. Remote system: Not enough space for '<remote file>' Meaning: The command was not executed (any further) because the permissible storage space on the receive system for the user ID specified in transfer admission has been used up, or the send file contains too long a sequence of empty blocks, or the primary and/or secondary allocation of the password-protected receive file is too small. The receive file is no longer created/extended after the problem has occurred. Measure: Take the appropriate action depending on the cause of the error: delete all files no longer required on the receive system, or ask the system administrator to allocate more storage space, or remove empty blocks from the send file, or increase the receive file's primary/secondary allocation. If option -e is specified, restore the receive file. Repeat the command.
159	Request <Request id>. Remote system: File owner unknown Meaning: The command was not executed because the owner of either the send file or the receive file was not defined on the relevant system or because the file owner and the user requesting the creation of a receive file are not the same. Measure: Define the file owner, correct transfer admission or file name. Repeat the command.

160	Request <Request id>. Remote system: Invalid file password Meaning: The command was not executed because the password for the send file or the receive file is missing or incorrect. Measure: Correct the password in the file description or the command. Repeat the command.
161	Request <Request id>. Remote system: Retention period of file not yet expired Meaning: The command was not executed because the retention period protecting the receive file against overwriting has not yet expired. Measure: Correct the transfer direction, retention period or file name. Repeat the command.
162	Request <Request id>. Remote system: File/directory '<remote file>' is read only Meaning: The file or directory is write-protected. Measure: Correct the remote file name or remove the write protection of the remote file. Repeat the command.
163	Request <Request id>. Remote system: File structure not supported Meaning: The request cannot be carried out because the file structure is not supported. For example, an attempt was made to get a PLAM library or ISAM file from the BS2000 system. Measure: Transfer the file transparently.

164	Request <Request id>. Remote system: Syntax error in resulting file name Meaning: A syntax error other than 'Mandatory parameter missing' (703) or 'keyword unknown' has been detected. Possible reasons: Values assigned outside the valid range Invalid operand separators Invalid value assignment characters Partially qualified file names Measure: Repeat the command using the correct syntax.
165	Request <Request id>. Remote system: Transparent file transfer not supported Meaning: The request could not be carried out because the partner system does not support the transfer of files in a transparent format.
166	Request <Request id>. Remote system: Extension of file not possible for transparent transfer Meaning: The command could not be executed because it is not possible to add to a file in a transparent transfer.
167	Request <Request id>. Remote system: Access to '<remote file>' denied Meaning: The command was not executed because the remote file only permits certain access modes. Measure: Correct the transfer direction, file name or file protection attributes on the remote system. Repeat the command.
168	Request <Request id>. Remote system: Follow-up processing exceeds length limit Meaning: The length of follow-up processing was exceeded; see the command syntax description. Measure: Shorten the follow-up processing, or use procedures. Repeat the command.

169	Request <Request id>. Remote system: Transfer admission invalid Meaning: The command was not executed because the specifications in one of the transfer admission operands are incorrect or the request was rejected by FTAC because of insufficient authorization. Measure: Define the requisite transfer admission or correct it or check the authorization entered in FTAC. Repeat the command if necessary.
170 171 172 195	Request <Request id>. Remote system: Function not supported Request <Request id>. Remote system: Processing admission invalid Request <Request id>. Remote system: Request queue full Request <Request id>. Remote system: openFT is no longer authorized to execute requests for this user Measure: If the remote system is a Windows system: Declare the password of the user to openFT (e.g. using the ftsetpwd command).
196	Request <Request id> has been canceled in the remote system Meaning: The request was deleted on the remote system before termination.
197	Request <Request id>. Remote system: File/directory '<remote file>' could not be created Meaning: The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Measure: Match the user ID in the receive system's transfer admission to the ID of the receive file owner. Repeat the command.
198	Request <Request id>. Remote system: Higher-level directory no longer found

199	Request <Request id>. Remote system: I/O error for '<remote file> Meaning: An error occurred at input/output. Possible cause: BS2000: DMS error, possibly the transfer ID. The send or receive files was deleted during transfer. The FT system continues to run after the message has been issued. Measure: Take the appropriate action in accordance with the error code.
200	Request <Request id>. Remote system: File now locked to prevent multiple access Meaning: The command was not executed because either the send file or the receive file is already locked by another process to prevent it from being updated simultaneously. An attempt is made, for example, to access a library opened in z/OS. Measure: Repeat the command later or unlock the file. After a system crash you may need to verify files not closed correctly. If a lock is caused by an FT request, it will be released automatically when the request is finished.
201	Request <Request id>. Remote system: File/directory '<remote file>' no longer available Meaning: The command was not executed because the volume for either the send file or the receive file is not mounted, unknown or reserved, or because the file extends over more than one private disk or an attempt has been made to transfer a file migrated by HSMS. Measure: Inform the operator if necessary or carry out an HSMS recall for the file. Repeat the command.
202	Request <Request id>. Remote system: File/directory '<remote file>' no longer found Meaning: The command was not executed because the remote file is not or no longer in the catalog or on a volume of the corresponding system (e.g. after a restart). Measure: Restore the remote file. Repeat the command.
203	Request <Request id>. Remote system: Home directory no longer found

204	Request <Request id>. Remote system: File/directory '<remote file>' gets no more space Meaning: The command was not executed (any further) because the permissible storage space on the receive system for the user ID specified in transfer admission has been used up, or the send file contains too long a sequence of empty blocks, or the primary and/or secondary allocation of the password-protected receive file is too small. The receive file can no longer be created/extended after the problem occurs. Measure: Take the appropriate action depending on the cause of the error: delete all files no longer required on the receive system, or ask the system administrator to allocate more storage space, or remove empty blocks from the send file, or increase the receive file's primary/secondary allocation. If option -e is specified, restore the receive file. Repeat the command.
205	Request <Request id>. Remote system: File owner no longer known Meaning: The command was not executed because the owner of either the send file or the receive file is not defined on the relevant system, or because the file owner and the user requesting the creation of the receive file are not the same. Measure: Define the file owner, correct transfer admission or file name. Repeat the command.
206	Request <Request id>. Remote system: Pre-/post-processing error Meaning: The command executed in local pre-/postprocessing returned an exit code other than 0. Measure: Correct the pre-/post-processing command and issue it again.
207	Request <Request id>. Remote system: Exit code <2> during pre-/post-processing Meaning: The command executed in local pre-/postprocessing returned the exit code <2>. Measure: Correct the pre-/post-processing command in accordance with the exit code and issue it again.

208	Request <Request id>. Remote system: File password no longer valid Meaning: The command was not executed because the password for the send file or receive file is missing or incorrect. Measure: Correct the password in the file description or the command. Repeat the command.
209	Request <Request id>. Remote system: File/directory '<remote file>' is now read only
210	Request <Request id>. Remote system: File structure error Meaning: The command was not executed due to a file structure error. File structure errors include: The attributes of the send file are incomplete. The data of the send file is incompatible with its structure attributes. The records of the send file are too long. If the -e option is specified, the send file and receive file have different structures (e.g. fixed-/variable-length records). BS2000: The send or receive file is a member of an old LMS library (not PLAM). BS2000: The send file has an odd block factor (e.g. BLKSIZE=(STD,1)), and the receive file is stored on an NK4 pubset. Measure: Correct the file or file attributes. If -e option is specified, restore the receive file. Repeat the command.
211	Request <Request id>. Remote system: NDMS error <2> Meaning: Repeat the request a little later.
212	Request <Request id>. Recovery failed Meaning: The restart could not be carried out. It may not have been possible to complete restart-capable pre-/post-processing before termination of the server process (waiting time: max. minutes). Measure: Repeat the command.

213	Request <Request id>. Remote system: Resource bottleneck Meaning: The order was rejected because the partner system currently does not have the resources available to accept requests. Measure: Repeat the request a little later.
214	Request <Request id>. Remote system: Access to ’<remote file>’ is no longer permissible
215 216 217 218	Request <Request id>. FTAM error <2> Request <Request id>. Remote system: File structure not supported Request <Request id>. Remote system: Retention period of file not yet expired Request <Request id>. Remote system: Extension of file not possible for transparent transfer
510	Requests carried out; <1> directories were transferred Meaning: In the case of a synchronous send request all directories were successfully transferred.
2100	Requests only partially completed; <1> of <2> directories were transferred In the case of a synchronous send request with wildcards, not all directories were successfully transferred. Measure: Transfer unsuccessfully transferred directories again.