Your Browser is not longer supported
Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...
{{viewport.spaceProperty.prod}}
&pagelevel(4)&pagelevel
FTR0000
| OPENFT: Request (&00) accepted.
Meaning The command has been stored in the local system's request queue. File transfer will begin once all the resources have been assigned in both the local and remote system. (&00): transfer ID assigned by the local FT system. You need the transfer ID in case you wish to cancel (NCANCEL) the FT request later. |
FTR0005
| OPENFT: Request (&00). File '(&01)' transferred.
Meaning The file transfer request (&00) has been completed successfully. Follow-up processing for both the local and remote system, if requested, has been initiated (provided no error occurred). Local Errors are indicated by a message. |
FTR0006
| OPENFT: Request (&00). Directory '(&01)' transferred.
Meaning The directory transfer request (&00) has been completed successfully. Follow-up processing for both the local and remote system, if requested, has been initiated (provided no error occurred). Local Errors are indicated by a message. |
FTR0020
| OPENFT:'(&00)' not found.
Meaning The command has not been executed because the send file is not cataloged or not on a volume of the local system. The command has not been executed because either the send file is not/is no longer, or the receive file is no longer in the catalog or on a volume of the relevant system. Response Correct the file name, read in file from tape or restore send file. Repeat the command. |
FTR0035
| OPENFT: File locked to prevent multiple access.
Meaning The command has not been executed because either the send file or the receive file is already locked by another process against simultaneous updating. Response Repeat the command later or unlock the file. After a system crash you may need to verify files that are not closed correctly. |
FTR0041
| OPENFT: Request queue full.
Meaning The command has not been executed because the maximum number of permissible transfer requests has been reached. |
| Response Notify the FT administrator. Repeat the command later. |
FTR0108
| OPENFT: Request (&00). Remote system not accessible.
Meaning The command could not be accepted because the partner system is currently not available. Response Repeat the command later. If the error persists, contact the system or network administrator. |
FTR0236
| OPENFT: Current instance (&00) no longer found
Meaning The command was rejected. The instance (&00) could not be found. |
FTR0301
| OPENFT: Partner '(&00)' entered state NOCON.
Meaning The partner system (&00) has switched to the state NOCON. This state means that the partner is no longer accessible. Response If necessary, check whether the connection to the partner system has been interrupted. |
FTR0302
| OPENFT: Partner '(&00)' entered state ACTIVE.
Meaning The partner system (&00) has switched to the state ACTIVE. Response For information only. |
FTR0303
| OPENFT: Partner '(&00)' entered state LUNK.
Meaning The partner system (&00) has switched to the state LUNK. This state means that the local FT system is not known in the remote FT system. Response Ask the remote system’s FT administrator to enter the local system in the remote system’s network description file/partner list. |
FTR0304
| OPENFT: Partner '(&00)' entered state RUNK.
Meaning The partner system (&00) has switched to the state RUNK. The state RUNK means that the remote system is not known in the local transport system. Response Make the remote system known on the local system. |
FTR0305
| OPENFT: Partner '(&00)' entered state INACT.
Meaning The partner system (&00) has switched to the state INACT. The state INACT means that the FT administrator has locked outbound requests for this partner system. Response Remove the lock if necessary. |
FTR0306
| OPENFT: Partner '(&00)' entered state AINACT.
Meaning The partner system has switched to the state AINACT. The state AINACT means that the partner system has been automatically deactivated because a certain number of consecutive connection attempts have failed. Response Check whether partner system should be accessible and reactivate the partner system. |
FTR0307
| OPENFT: Partner '(&00)' may be unreachable.
Meaning A number of consecutive attempts to connect to the partner system (&00) have failed. Further attempts will be made. Response For information only. |
FTR0308
FTR0309
| OPENFT: Partner '(&00)' does not allow more inbound requests.
OPENFT: Partner '(&00)' added.
Meaning The specified remote system has been entered in the partner list. |
FTR0310
| OPENFT: Partner '(&00)' removed.
Meaning The specified remote system has been removed from the partner list. |
FTR0311
| OPENFT: Partner '(&00)' entered state LAUTH.
Meaning The partner system (&00) has switched to the state LAUTH. The state LAUTH means that the local system could not authenticate itself at the remote system. Response Send the current key file to the administrator of the remote system. |
FTR0312
| OPENFT: Partner '(&00)' entered state RAUTH.
Meaning The partner system (&00) has switched to the state RAUTH. The state RAUTH means that the remote system could not authenticate itself at the local system. This may either be due to an out-of-date key in the key file or to may indicate an access attempt by an unauthorized system. Response Contact the administrator of the remote system. |
FTR0313
| OPENFT: Partner '(&00)' entered state DIERR.
Meaning The partner system (&00) has switched to the state DIERR. File integrity errors have been detected on the transmission path. This may also indicated deliberate manipulation of the transmission data. |
FTR0314
| OPENFT: Partner '(&00)' entered state NOKEY.
Meaning The partner system (&00) has switched to the state NOKEY. The state NOKEY means that the partner will not accept a connection without encryption or that no key is present. Response Generate a new key pair. |
FTR0315
| OPENFT: Partner '(&00)' entered state IDREJ.
Meaning The partner system (&00) has switched to the state IDREJ. The local identification was not accepted by the local identification or by an intermediate entity. Possible causes: both the local identification and the migrated ID %.<processor>.<entity> are entered in the remote system’s request file. the identification has been rejected by an intermediate entity for security reasons
Response Ask for your entity’s partner entry to be checked. |
FTR0320
| OPENFT: Abnormal termination initiated.
Meaning Abnormal termination of FT has been initiated due to an internal error. Response Check the cause of the abnormal termination and restart FT. |
FTR0330
| OPENFT: Request queue 85 percent full.
Meaning Approximately 85% of the spaces for request storage in the request file are occupied. Issuing a number of additional requests could completely fill the request queue with the result that FT will reject new requests. Response If necessary, increase the size of the request queue. |
FTR0331
| OPENFT: At least 20 percent of request queue unoccupied.
Meaning At least 20% of the FT request queue is available. This message is only output if a previous FTR0330 message has warned of a possible queue overflow. The threat of a bottleneck has receded. |
FTR0340
| OPENFT: Transfer '(&00)' successfully completed.
Meaning The request designated in greater detail by the insert (&00) has been terminated successfully. (&00): *LOC/*REM;SID;PARTNER;USERID;FILE Since the length of the insert is limited to a maximum of 180 characters, the file name may be truncated if necessary. This is indicated by the character ’*’ at the end of the file name. Response For information only. |
FTR0341
| OPENFT: Transfer '(&00)' terminated with error.
Meaning The request designated in greater detail by the insert (&00) terminated with an error (&00): MSGNR;*LOC/*REM;SID;PARTNER;USERID;FILE Since the length of the insert is limited to a maximum of 180 characters, the file name may be truncated if necessary. This is indicated by the character ’*’ at the end of the file name. Response For information only. |
FTR0360
| OPENFT: openFT control process started
Response For information only. |
FTR0361
| OPENFT: openFT control process terminated
Response For information only. |
FTR0500
| OPENFT: openFT (&00) started. Protocols: (&01).
Meaning The openFT file transfer system openFT has been activated for the protocols (&01). |
FTR0501
| OPENFT: openFT terminated.
Meaning The file transfer system openFT has been terminated by means of an administration command. |
FTR0502
| OPENFT: No log records available for the selection criteria.
Meaning No logging records meet the selected criteria. Response Change the selection criteria. |
FTR0503
| OPENFT: No partner available for the selection criteria.
Meaning There are no partners that meet the specified selection criteria. Response Change the selection criteria. |
FTR0504
| OPENFT: No requests available for the selection criteria.
Meaning There are no requests that meet the specified selection criteria. Response Change the selection criteria. |
FTR0505
| OPENFT: Requests carried out; (&00) files were transferred
Meaning The file transfer requests have been successfully completed. A total of (&00) files have been transferred. If you have specified commands for follow-up processing, follow-up processing is carried out for every file. |
FTR0509
| Protocol: (&00) not installed or not licensed
Meaning Configuration and activation of protocol don't match. Response Check configuration and activation of protocol. |
FTR0510
| OPENFT: Requests carried out; (&00) directories were transferred
Meaning The directory transfer requests have been successfully completed. A total of (&00) directories have been transferred. If you have specified commands for follow-up processing, follow-up processing is carried out for every file. |
FTR0511
| OPENFT: Requests accepted; (&00) file transfers initiated
Meaning The file transfer requests have been successfully accepted. A total of (&00) file transfers have been initiated. If you have specified commands for follow-up processing, follow-up processing is carried out for every file. |
FTR0560
| OPENFT: Cancel all specified requests? Reply (y=yes; n=no)
Meaning A CANCEL-TRANSFER command applies to more than one file transfer. Y: All the transfer requests affected are deleted. N: The entire deletion request is withdrawn. |
FTR0561
| OPENFT: Do you really want to delete this key pair set? Reply (y=yes; n=no)
Meaning Deletion of a key pair set prevents connection to all partners working with these keys. If the last key pair set is deleted, there is no encryption. |
FTR0562
FTR0600
| OPENFT: (&00):
OPENFT: Shutdown processing delayed. FT tasks pending.
Meaning openFT could not be terminated. Response Check if there are console messages that need to be answered for FT tasks connected to the FT subsystem. |
FTR0604
| OPENFT: Request (&00). Follow-up processing not started.
Meaning The follow-up processing of a transfer request was not started because the local processing admission may be incorrect. Response Correct the local processing admission and repeat the command. |
FTR0605
| OPENFT: Tracefile changed
Meaning There has been a switch to a new trace file. |
FTR0606
| OPENFT: Trace terminated.
Meaning The trace status has been switched off. |
FTR0607
| OPENFT: Trace started: (&00).
Meaning The trace status for the protocols specified in (&00) has been switched on. |
FTR0700
| Parameter '(&00)' and '(&01)' must not be specified at the same time
Meaning The selected parameters could not be specified simultaneously. Response Omit one of the two parameters and repeat the command. |
FTR0701
FTR0702
| OPENFT: Input error
OPENFT: Parameter value '(&00)' too long
Meaning The specified parameter value (&00) is too long; see the command syntax. Response Reduce the length of the parameter value (&00) and repeat the command. |
FTR0703
| OPENFT: Mandatory parameter missing
Meaning A mandatory parameter is missing; see the command syntax. Response Correct the command and try again. |
FTR0704
| OPENFT: Mandatory parameter '(&00)' missing
Meaning The mandatory parameter (&00) was not specified. Response Correct the command and try again. |
FTR0705
| OPENFT: Parameter '(&00)' specified more than once
Meaning The parameter (&00) was specified more than once. Response Correct the command and try again. |
FTR0706
| OPENFT: Parameter '(&00)' can only be specified together with '(&01)'
Meaning The parameter (&00) can only be specified together with (&01). Response Add the parameter (&01) to the command and repeat the command. |
FTR0707
| OPENFT: Invalid parameter '(&00)'
Meaning An invalid parameter (&00) was specified; see the command syntax. Response Correct the command and try again. |
FTR0708
| OPENFT: Value of parameter '(&00)' not within valid range
Meaning The parameter value (&00) is not within the specified value range; see the command syntax. Response Correct the parameter value (&00) and repeat the command. |
FTR0709
| OPENFT: Too many positional parameters
Meaning The maximum number of positional parameters was exceeded. Response Correct the command and try again. |
FTR0710
| OPENFT: Invalid parameter value '(&00)'
Meaning The assigned parameter value (&00) is incorrect; see the command syntax. Response Correct the parameter value (&00) and repeat the command. |
FTR0711
| Parameter '(&00)' or '(&01)' must be specified
Meaning At least one of the parameters must be specified. |
FTR0750 OPENFT: Command not found
FTR0751 OPENFT: Command name ambiguous with regard to '(&00)'
FTR0752 OPENFT: Closing parenthesis missing for operand '(&00)'
FTR0753 OPENFT: Invalid delimiter '(&00)' after operand '(&00)'
|
FTR0755 OPENFT: List value of operand '(&00)' is not consistent with data type '(&00)'
FTR0756 OPENFT: Operand value introducing the structure is mandatory for '(&00)'
FTR0757 OPENFT: Value of operand '(&00)' is not consistent with data type '(&00)'
FTR0758 OPENFT: Keyword value of operand '(&00)' is ambiguous with regard to '(&00)'
FTR0759 OPENFT: Too many closing parentheses
FTR0760 OPENFT: The mandatory operand '(&00)' is missing
FTR0762 OPENFT: Operand name '(&00)' ambiguous with regard to '(&00)'
FTR0763 OPENFT: Operand '(&00)' is not known
FTR0764 OPENFT: Operand '(&00)' specified more than once
FTR0765 OPENFT: Too many list elements for operand '(&00)'
FTR0766 OPENFT: Too many positional operands
|
FTR0767
| OPENFT: Too many positional operands for '(&00)'
|
| Meaning (applies to FTR0750 through FTR0767) An operand value that introduces a structure can only be omitted if there is only one possible structure specification for the corresponding operand or if this structure specification is the default value for the operand. The following command, for example, will be rejected with this message: FTMODPRF MYPROF01,PARTNER=((REMSYS1,REMSYS2))
Reason: It is not clear which of the following specifications is meant: FTMODPRF MYPROF01,PARTNER=*ADD((REMSYS1,REMSYS2))
or FTMODPRF MYPROF01,PARTNER=*REM((REMSYS1,REMSYS2))
Response Repeat the command using the correct syntax. |
FTR0780 OPENFT: Internal error: operand buffer overflow
FTR0781 OPENFT: Internal error: structure nesting too deep
FTR0790 OPENFT: Available commands: '(&00)'
FTR0791 OPENFT: Available list-values: '(&00)'
FTR0792 OPENFT: Available operands: '(&00)'
FTR0793 OPENFT: Available values: '(&00)'
|
FTR0801
| OPENFT: Request (&00). Internal error
Meaning NDMS, FJAM or operating system error that is neither a DMS error nor a transport system error, possibly the transfer ID. The FT system continues to run after the message has been issued. |
FTR0802
| OPENFT: Request (&00). Warning: Monitor file contents inconsistent
Meaning At the end of the file transfer request, the contents of the job variable monitoring the request were found to be inconsistent. Possible reason: During the transfer, the job variable was accessed externally in a mode other than read mode. The result of the transfer is not affected and is given in the result list or asynchronous end message. |
FTR0803
| OPENFT: Request (&00). Follow-up processing could not be started.
Meaning The command was not executed because the specifications in one of the PROCESSING- ADMISSION operands are incorrect. Response Define the required PROCESSING ADMISSION or correct it. Repeat the command if necessary. |
FTR0804 OPENFT: Request (&00). Request data inconsistent.
FTR0851 OPENFT: Internal error.
FTR0852 OPENFT: Internal error. Current instance '(&00)' incompatible.
|
| Meaning The system data was not created with the version of the openFT file transfer system currently in use. Response Update the instance to the current openFT version using the appropriate command (FJGEN). |
FTR0854
| OPENFT: Writing of log records no more possible. Process terminated.
Meaning There is not enough space on the disk/partition on which the logging files are stored. Response Increase the disk space (or have it increased). |
FTR0855
| OPENFT: No space left on device for internal files.
Meaning There is not enough space on the disk/partition on which the internal files are stored. Response Increase the disk space (or have it increased). |
FTR0856 OPENFT: Error during ops generation.
FTR0857 OPENFT: Error in key file (&00)
FTR0858 OPENFT: Internal error. Set / release file-locks not possible
|
| Meaning A problem occurred when setting/resetting the file locks for all open requests in FT-REQUEST-FILE. Response Check whether the request file SYSRQF is accessible on the config user ID of the current instance. |
FTR0862
| OPENFT: Protocol stack (&00) not installed
Meaning The required transfer protocol is not installed. Response Install the transfer protocol. |
FTR0863
| OPENFT: FTAC subsystem not available
Meaning Install openFT-AC. |
FTR0864
| OPENFT: Server (&00) accepts no requests
Meaning The control process cannot access the server to assign new requests. Response Check if the server is blocked e.g. by a system dump or the output of a message and correct the error situation. |
FTR0865
| OPENFT: Not all files transferred successfully
Meaning At least one source file could not be transferred to the local system. The previous messages indicate the files concerned: Transfer of file '<file>' failed. Reason: '<rc>' |
FTR0999
FTR1020
| OPENFT: openFT panic (&00). Abnormal termination
OPENFT: openFT already started.
Meaning openFT can only be started once in each instance. Response Terminate openFT if necessary. |
FTR1021
| OPENFT: Request must be canceled without FORCE option first
Meaning Before the FORCE option is used, the command must be called without the FORCE option. Response Issue the command without the FORCE option first. |
FTR1029
| OPENFT: Maximum number of key pairs exceeded.
Meaning The maximum number of key pair sets has been reached. Response Before new key pair set can be created, an older key pair set must be deleted. |
FTR1030
| OPENFT: Warning: last key pair deleted.
Meaning The last key pair set has been deleted. Without a key pair set, encrypted transfer, authentication and data integrity checking are not possible. Response Create a new key pair set. |
FTR1031
| OPENFT: No key pair available.
Meaning All transfers are carried out without encryption. Response Create a new key pair set, if necessary. |
FTR1032
FTR1033
| OPENFT: Last key pair must not be deleted
OPENFT: The public key files could not be updated.
Meaning The contents of the SYSPKF file could not be fully updated. Possible reasons: |
| Response Take the appropriate action depending on the cause of the error: Update the key with UPDATE-FT-PUBLIC-KEY. |
FTR1034
| OPENFT: Command only permissible for FT or FTAC administrator
Meaning Only the FT or FTAC administrator is permitted to use the command. Response Have the command executed by the FT or FTAC administrator. |
FTR1035
| OPENFT: Command only permissible for FT administrator.
Meaning Only the FT administrator is permitted to use the command. Response Have the command executed by the FT administrator. |
FTR1036
| OPENFT: User not authorized for other user IDs.
Meaning The user is not authorized to use a different user ID in the command. Response Specify your own ID, or have the command executed by the FT or FTAC administrator. |
FTR1037
| OPENFT: Key reference unknown.
Meaning The specified key reference is unknown. Response Repeat the command with an existing key reference. |
FTR1038
FTR1039
| OPENFT: Request '(&00)' is in the termination phase and can no longer be canceled
OPENFT: openFT not active.
Meaning openFT is not started. Response Start openFT, if necessary. |
FTR1040
| OPENFT: Config user ID unknown or not enough space
Meaning The CONFIG USERID of the current instance (SYSFJAM) is unknown or the disk space allocated is insufficient to allow creation of the FT-REQUEST-FILE, the file for storing trace data, or the key files. Response Either create the CONFIG-USERID or increase its disk space allocation or have your system administrator do it. |
FTR1041 OPENFT: Specified file is not a valid trace file
FTR1042 OPENFT: openFT could not be started
FTR1043 OPENFT: Partner with same attribute '(&00)' already exists in partner list.
|
| Meaning There is already a partner entry with the same attribute '(&00)' in the partner list. Response The attribute '(&00)' in partner entries must be unique. Correct the command accordingly and try again. |
FTR1044
| OPENFT: Maximum number of partners exceeded.
Meaning The partner list already contains the maximum permissible number of partner entries. Response Delete partners that are no longer required. |
FTR1045
| OPENFT: No partner found in partner list.
Meaning A partner for the specified selection could not be found in the partner list. Response Check if the specified partner name or address was correct. If necessary, repeat the command using the correct name or address. |
FTR1046
| OPENFT: Modification of partner protocol type not possible
Meaning The protocol type of the partner entry cannot be changed subsequently. Response Delete the partner from the partner list, if necessary, and enter it again with a new protocol type. |
FTR1047
| OPENFT: Request (&00) not found.
Meaning The request with the transfer ID (&00) could not be found. Response Specify the existing transfer ID and repeat the command. |
FTR1048
| OPENFT: Active requests could not yet be deleted
Meaning Active requests for the specified partner were cancelled. After the negotiation of termination with the partner the requests will be automatically deleted. |
FTR1049 OPENFT: CCS name (&00) unknown
FTR1057 OPENFT: Inbound requests cannot be modified
|
FTR1059
| OPENFT: Monitoring is not active
Meaning The command is only supported if monitoring is activated. Response Activate monitoring in the operating parameters. |
FTR1060 OPENFT: File could not be created '(&00)'
FTR1061 OPENFT: Higher-level directory not found
FTR1062 OPENFT: File already exists
FTR1063 OPENFT: Resulting file name too long
FTR1064 OPENFT: File locked to prevent multiple access
FTR1065 OPENFT: File not found
FTR1066 OPENFT: Not enough space for file
FTR1067 OPENFT: Syntax error in resulting file name
FTR1068 OPENFT: Access to file denied (&00)
FTR1069 OPENFT: Error accessing file (&00)
|
FTR1073
| OPENFT: Command aborted
Meaning The user has interrupted the command. |
FTR1076 OPENFT: selected key file not found
FTR1077 OPENFT: Change of transport access system not possible. Reason: (&00)'
FTR1078 OPENFT: Too short time interval since last logging file switch
|
| Meaning At this moment the logging file cannot be switched, as the time dependant part of the logging file name does not differ from this name part in the actual logging file name. Response If necessary, repeat the command after an appropriate waiting time. |
FTR1082
| OPENFT: User data encryption not supported
Meaning User data encryption is supported only when openFT-CR is installed. Response Install openFT-CR |
FTR1083
| OPENFT: Structure of key file not supported
Meaning The key cannot be imported because of the not supported key file structure. |
FTR1084 OPENFT: Invalid password
FTR1085 OPENFT: Password missing
FTR1086 OPENFT: Duplicate key pair
|
| Meaning No import of duplicate keys allowed. |
FTR1087
| OPENFT: Key expired
Meaning The expiration date lies in the past. |
FTR1092
| OPENFT: Warning: The RSA key length was aligned to the minimum key length
Meaning The RSA key length was less than the configured minimum key length and had to be enlarged. |
FTR2014
| OPENFT: No file attribute changes requested.
Meaning No further file attributes besides the file name were specified. Response Enter the desired file attributes in addition to the file name. |
FTR2015 OPENFT: openFT is not authorized to execute requests for this user
FTR2016 OPENFT: Directory (&00) is not empty
FTR2017 OPENFT: File attributes do not match request parameters (&00)
|
| Meaning The specified attribute combination is not permissible. Response Specify a permissible combination. |
FTR2018
| OPENFT: Attributes could not be modified (&00).
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: |
FTR2019
| OPENFT: (&00)' could not be created (&01).
Meaning The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Response Match the user ID in the receiving system's TRANSFER-ADMISSION to the ID of the receive file's owner. Repeat the command. |
FTR2021
| OPENFT: CCS name unknown.
Meaning The request could not be completed because the CCS name specified for the local file does not correspond to any of the supported code tables. |
FTR2022
| OPENFT: 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. Response Create or correct the path for the receive file and repeat the command. |
FTR2023
| OPENFT: (&00)' already exists.
Meaning The command was not executed because an existing receive file cannot be created again with WRITE-MODE=NEW. WRITE-MODE=NEW may also have been set due to a restriction in the access authorization used. Response Either delete the receive file and repeat the command, or repeat the command specifying WRITE-MODE=REPLACE-FILE or using different access authorization. |
FTR2024
| OPENFT: Transfer of file generation groups not supported.
Meaning The command was not executed because the FT system only transfers single file generations. Response Repeat the command using the name of a single file generation. |
FTR2025
| OPENFT: Error accessing '(&00)'(&02).
Meaning (&02): Further details, possibly DMS error The FT system continues to run after the message has been issued. Response Take the appropriate action in accordance with the error code. |
FTR2026
| OPENFT: Resulting file name '(&00)' too long (&01).
Meaning The relative file name was specified in the transfer request. The absolute file name completed by openFT is longer than permitted. Response Shorten the file name or path and repeat the command. |
FTR2027
| OPENFT: 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. Response Repeat the command, specifying the file ID explicitly or a TRANSFER-ADMISSION that defines the file ID. |
FTR2028
FTR2029
| OPENFT: Invalid management password.
OPENFT: (&00)' not available (&01).
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 HSM without specifying the local transfer admission (TRANSFER-ADMISSION operand). Response Inform the operator if necessary or carry out an HSM recall for the file or specify the local transfer admission. Repeat the command. |
FTR2030 OPENFT: Home directory not found (&00)
FTR2031 OPENFT: Renaming not possible (&00)
FTR2032 OPENFT: Not enough space for (&00).
|
| 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. The receive file can not be created/extended after the problem occurs. Response 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 increase the receive file's primary/secondary allocation.
If WRITE-MODE=EXTEND-FILE is specified, restore the receive file. Repeat the command. |
FTR2033
| OPENFT: 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. Response Define the file owner, correct TRANSFER-ADMISSION or FILE-NAME. Repeat the command. |
FTR2034
| OPENFT: Invalid file password.
Meaning The command was not executed because the password for the send file or the receive file is missing or incorrect. |
| Response Correct the password in the file description or the command. Repeat the command. |
FTR2036
| OPENFT: 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). Response Correct the transfer direction, retention period or file name. Repeat the command. |
FTR2037 OPENFT: '(&00)' is read only.
FTR2038 OPENFT: File structure not supported (&00).
FTR2039 OPENFT: Syntax error in resulting file name '(&00)' (&01).
|
| Meaning The local file cannot be accessed because, for example, the absolute file name is too long. Response Shorten the path or file name. Repeat the command. |
FTR2040
| OPENFT: Transparent file transfer not supported.
Meaning The request could not be carried out because the partner system does not support the receipt of files in a transparent format. |
FTR2042
| OPENFT: 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. Response Start transfer without EXTEND. |
FTR2043
| OPENFT: Access to '(&00)' denied (&01).
Meaning The command was not executed because either the send file or the receive file only permits certain access modes (e.g. read only). Response Correct the file name or file protection attributes. Repeat the command. |
FTR2044
| OPENFT: Follow-up processing exceeds length limit.
Meaning Prefix + suffix (from prof) + local follow-up processing together are too long. |
| Response Correct the file name or file protection attributes. Repeat the command. |
FTR2045
| OPENFT: Processing admission invalid.
Meaning The command was not executed because the specifications in one of the PROCESSING- ADMISSION operands were incorrect. Response Define the required PROCESSING ADMISSION or correct it. Repeat the command if necessary. |
FTR2046
| OPENFT: Local transfer admission invalid.
Meaning The command was not executed because the specifications in one of the TRANSFER- ADMISSION operands were incorrect. Response Define the required TRANSFER ADMISSION or correct it. Repeat the command if necessary. |
FTR2047
| OPENFT: Request rejected by local FTAC.
Meaning The command was not executed because the request was rejected by the product openFT-AC due to a lack of authorization. Response Use the return code in the logging record to determine and remove the cause. Repeat the command. |
FTR2048
| OPENFT: Function not supported for protocol '(&00)'.
Meaning The desired function is not available for the selected protocol. Response Select a different protocol. |
FTR2049
| OPENFT: Remote follow-up processing not supported
Meaning Remote follow-up processing is only available for the openFT protocol. Response Select a different protocol, or specify follow-up processing by means of an FTAC profile. |
FTR2050
| OPENFT: Data integrity check not supported.
Meaning The partner system does not support the data integrity check function. |
| Response Repeat the request without a file integrity check. |
FTR2051
| OPENFT: User data encryption not possible for this request.
Meaning The partner system does not support the data encryption function. Response Repeat the request without data encryption or install openFT-CR (or have it installed) on the remote system. |
FTR2052
| OPENFT: Administration request rejected by remote administration server
Meaning The command was not executed because the request was rejected by the remote administration server. Response Use the return code in the log record on the remote administration server to determine and remove the cause. Repeat the command. |
FTR2053
| OPENFT: Destination format not supported for transparent transfer
Meaning The destination file organization parameter is not supported for transparent transfer Response Repeat the request without destination file organization parameter. |
FTR2054
| OPENFT: Invalid command
Meaning The specified command is not allowed in this context. Response Repeat the request with a valid command. |
FTR2056
| OPENFT: Syntax error in partner name (&00)
Meaning The syntax of the partner name is wrong. Response Correct partner name. Repeat the command. |
FTR2058
| OPENFT: User data encryption is mandatory
Meaning The data encryption function is mandatory. Response Repeat the request with data encryption. |
FTR2070
| OPENFT: Request (&00). openFT is no longer authorized to execute requests for this user
|
FTR2071 OPENFT: Request (&00). User data encryption not installed.
|
| Meaning The user data encryption function cannot be used unless openFT-CR is installed. Response Use openFT-CR. |
FTR2072
| OPENFT: Request (&00) has been canceled.
Meaning The FT request was canceled because 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 FTR0604 at the start of follow-up processing. |
FTR2073
| OPENFT: Request (&00). Encryption error
Meaning Encryption not possible. |
FTR2074
| OPENFT: Request (&00). '(&01)' could not be created (&02).
Meaning The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Response Match the user ID in the receive system's TRANSFER ADMISSION to the ID of the receive file owner. Repeat the command. |
FTR2075
FTR2076
| OPENFT: Request (&00). Higher-level directory no longer found
OPENFT: Request (&00). I/O error for '(&01)'(&02).
Meaning The file can no longer be accessed. It may have been deleted during a transfer. Response Repeat the request. |
FTR2077
| OPENFT: Request (&00). 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. |
| Response 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. |
FTR2078
| OPENFT: Request (&00). '(&01)' no longer available (&02).
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. Response Inform the operator if necessary. Repeat the command. |
FTR2079
| OPENFT: Request (&00). '(&01)' 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. Response Restore the file. Repeat the command. |
FTR2080
FTR2081
| OPENFT: Request (&00). Home directory no longer found (&01)
OPENFT: Request (&00). '(&01)' gets no more space.
Meaning The command was not executed (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 receive file has already reached the maximum number of allocations.
Take the appropriate action depending on the cause of the error: Response 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 reorganize the file so that it requires fewer allocations, or increase the receive file's primary/secondary allocation.
If WRITE-MODE=EXTEND-FILE is specified, restore the receive file. Repeat the command. |
FTR2082
| OPENFT: Request (&00). 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. Response Define the file owner, or correct TRANSFER-ADMISSION or FILE-NAME. Repeat the command. |
FTR2083
| OPENFT: Request (&00). Pre-/post-processing error(&01).
Meaning The command executed as part of local pre-/postprocessing returned a result other than OK. Response Correct and repeat the command. |
FTR2084
| OPENFT: Request (&00). Exit code (&01) for pre-/post-processing (&02).
Meaning The command executed as part of local pre-/postprocessing returned the exit code (&01). Response Correct the command using the exit code (&00) and issue it again. |
FTR2085
| OPENFT: Request (&00). 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. Response Correct the password in the file description or the command. Repeat the command. |
FTR2086
FTR2087
| OPENFT: Request (&00). '(&01)' is now read only.
OPENFT: Request (&00). File structure error(&01).
Meaning The command was 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 WRITE-MODE=EXTEND-FILE or -e is specified, the send file and receive file have different structures (e.g. fixed-/variable-length records). The send file or receive file in a remote BS2000 system is a member of an old LMS library (not PLAM).
Response Correct the file or file attributes. If WRITE-MODE=EXTEND-FILE or -e is specified, restore the receive file. Repeat the command. |
FTR2088
| OPENFT: Request (&00). NDMS error (&01).
Meaning The request was rejected because the partner system currently does not have the resources available to accept requests. Response Repeat the request a little later. |
FTR2089
| OPENFT: Request (&00). Recovery failed (&01).
Meaning The restart attempts were unsuccessful (for example, a pre-/postprocessing command could not be completed before the termination of openFT). Response Repeat the command. |
FTR2090
| OPENFT: Request (&00). 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. Response Repeat the request, if necessary. |
FTR2091
| OPENFT: Requests only partially completed; (&00) of (&01) files were transferred
Meaning In the case of a synchronous send request with wildcards, not all files were successfully transferred. Response Transfer unsuccessfully transferred files again. |
FTR2092
| OPENFT: Request (&00). Access to '(&01)' no longer permissible (&02).
Meaning The command was not executed because either the send file or the receive file only permits certain access modes (e.g. read only) or because a directory was specified as either the source or destination of a file transfer. |
| Response Correct the transfer direction, write mode, file name or file protection attributes. Repeat the command. |
FTR2094
| OPENFT: Request (&00). 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). Response Correct the transfer direction, retention period or file name. Repeat the command. |
FTR2095
| OPENFT: Request (&00). 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. Response Start transfer without EXTEND. |
FTR2096
FTR2097
| OPENFT: Request (&00). File structure not supported (&01).
Request (&00). Resulting file name '(&01)' too long(&02)
Meaning The relative file name was specified in the transfer request. The absolute file name as extended by openFT is longer than permitted. Response Shorten the file name or path and repeat the command. |
FTR2100
| OPENFT: Requests only partially completed; '(&00)' of '(&01)' directories were
transferred
Meaning In the case of a synchronous send request with wildcards, not all directories were successfully transferred. Response Transfer unsuccessfully transferred directories again. |
FTR2109
FTR2110
| OPENFT: Request (&00). Connection setup rejected by local transport system.
OPENFT: Request (&00). Data integrity check indicates an error.
Meaning The integrity of the data was violated. |
FTR2111
| OPENFT: 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. Response Repeat the request without data encryption, create a key or set a key length >0. |
FTR2112
| OPENFT: Request (&00). Data integrity check not supported by partner.
Meaning The partner system does not support the data integrity check. Response Repeat the request without a data integrity check. |
FTR2113
| OPENFT: Request (&00). User data encryption not possible for this request.
Meaning The partner system does not support the data encryption function. Response Repeat the request without data encryption or install openFT-CR (or have it installed) on the remote system. |
FTR2114
| OPENFT: Request (&00). Identification of local system rejected by remote system
'(&01)'.
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 a network description file both the instance identification and migration identification %.prozessor.entity occur for different partners). Response Ensure that the local identification has been entered correctly on the partner system and has not been assigned to a different partner. |
FTR2115
FTR2116
| OPENFT: Request (&00). Interrupted by remote system
OPENFT: Local application (&00) not defined
Meaning The local application is not defined in the transport system. Response Make the local application known to the local transport system. |
FTR2117
FTR2118
| OPENFT: Local application (&00) not available
OPENFT: Request (&00). Authentication of local system failed.
Meaning The local system could not be authenticated by the partner system. Response Give the current public key file to the partner and name it correctly there. Repeat the command. |
FTR2119
| OPENFT: Request (&00). Local system unknown in remote system.
Meaning The local system is not known on the partner system (e.g. BS2000/OSD or z/OS). Response Make the local system known on the partner system and repeat the command. |
FTR2120
| OPENFT: Remote system '(&00)' unknown.
Meaning The partner specified as the remote system cannot be expanded to an address on the local system. Response Correct the specification for the partner or add the partner to the partner list and repeat the command. |
FTR2121
| OPENFT: Request (&00). Authentication of partner failed.
Meaning The remote system could not be authenticated by the local system. Response Get the current public key file from the partner and name it correctly. |
FTR2122
FTR2123
| OPENFT: Request (&00). FT session rejected or disconnected. Reason (&01)
OPENFT: Request (&00). OSS call error (&01).
Meaning The command was not executed because the session instance detected a communication error. (&00): error code. Response Take the appropriate action in accordance with the error code. |
FTR2124
| OPENFT: Request (&00). No free connection
Meaning No more transfers are possible because the maximum number of simultaneous transfers has been reached. Response Check whether the transport system is working (or have it checked). |
FTR2125
| OPENFT: Request (&00). Connection lost.
Meaning No data transfer took place because of a line interrupt or a line protocol error. Response Repeat the request. |
FTR2126
| OPENFT: Request (&00). Transport system error. Error code (&01)
Meaning An error occurred in the transport system during processing of a FTSTART command or a file transfer or file management request. Response 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. |
FTR2127
| OPENFT: Request (&00). No data traffic within (&01) 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. Response Repeat the request. |
FTR2129
| OPENFT: No further files will be transferred
Meaning Check the previous transfer error code. |
FTR2140 OPENFT: Request (&00). Remote system: openFT is not authorized to execute
requests for this user.
FTR2141 OPENFT: Request (&00). Remote system: Directory (&01) is not empty
|
| Meaning The command could not be executed because there are files in the specified directory of the partner system. Response Delete all the files in the directory first and repeat the command. |
FTR2142
| OPENFT: Request (&00). Remote system: File attributes do not match the request
parameters (&01)
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). Response Check the file name on the remote system and correct it. Repeat the command. |
FTR2143
| OPENFT: Request (&00). Remote system: Attributes could not be modified (&01).
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.
|
FTR2144
| OPENFT: Request (&00). Remote system: File/directory (&01) could not be created
(&02)
Meaning The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Response Match the user ID in the receive system's TRANSFER-ADMISSION to the ID of the receive file owner. Repeat the command. |
FTR2145
| OPENFT: Request (&00). Remote system: CCS name unknown or not supported.
Meaning The request could not be completed because the CCS is unknown in the partner system. |
FTR2146
| OPENFT: Request (&00). 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. Response Create the directory on the remote system or correct the remote directory name and repeat the command. |
FTR2147
| OPENFT: Request (&00). Remote system: File/directory '(&01)' already exists.
Meaning The command was not executed. Possible reasons: The command was not executed because an existing receive file cannot be created with 'WRITE-MODE=NEW' or the -n option. WRITE-MODE=NEW or -n may also have been set by a restriction in the access authorization used. ftcredir: The specified directory already exists.
Response Either delete the receive file before repeating the command or reenter the command specifying WRITE-MODE=REPLACE-FILE or using different access authorization. |
FTR2148
| OPENFT: Request (&00). 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. Response Repeat the command using the name of a single file generation. |
FTR2149
| OPENFT: Request (&00). Remote system: Access error for '(&01)' (&02).
Meaning (&02): DMS error, possibly the transfer ID. The FT system continues to run after output of the message. Response Take the appropriate action in accordance with the error code. |
FTR2150
| OPENFT: Request (&00). Remote system: Resulting file name too long (&01).
Meaning A syntax error other than 'operand missing' (FTR0010) or 'keyword unknown' (FTR0011) has been detected. Possible reasons: Values assigned outside the valid range Invalid operand separators Invalid value assignment characters Partially qualified file names
Response Repeat the command using the correct syntax. |
FTR2151
| OPENFT: Request (&00). 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. Response Repeat the command later or unlock the file on the remote system. After a system crash in BS2000 you may need to verify files not closed correctly. If the lock is caused by an FT request, it will be released automatically when the request is finished. |
FTR2152
| OPENFT: Request (&00). 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. Response Repeat the command, specifying the file ID explicitly or using a TRANSFER ADMISSION that defines the file ID. |
FTR2153 OPENFT: Request (&00). Remote system: Invalid management password.
FTR2154 OPENFT: Request (&00). Remote system: File/directory '(&01)' not available (&02).
|
| 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 HSM without specifying the remote transfer admission. Response Inform the operator if necessary or carry out an HSM recall for the file or specify the remote transfer admission. Repeat the command. |
FTR2155
| OPENFT: Request (&00). Remote system: File/directory '(&01)' 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. Response Correct the remote file name, read the file in from tape or restore the send file. Repeat the command. |
FTR2156 OPENFT: Request (&00). Remote system: Home directory not found (&01)
FTR2157 OPENFT: Request (&00). Remote system: Renaming not possible (&01)
FTR2158 OPENFT: Request (&00). Remote system: Not enough space for '(&01).
|
| 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.The receive file is no longer created/extended after the problem has occurred. Response 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 increase the receive file's primary/secondary allocation.
If WRITE-MODE=EXTEND-FILE is specified, restore the receive file. Repeat the command. |
FTR2159
| OPENFT: Request (&00). 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. Response Define the file owner, correct TRANSFER-ADMISSION or FILE-NAME. Repeat the command. |
FTR2160
| OPENFT: Request (&00). 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. Meaning Correct the password in the file description or the command. Repeat the command. |
FTR2161
| OPENFT: Request (&00). 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. Response Correct the transfer direction, retention period or file name. Repeat the command. |
FTR2162
| OPENFT: Request (&00). Remote system: File/directory '(&01)' is read only.
Meaning The file or directory is write-protected. Response Correct the remote file name or remove the write protection of the remote file. Repeat the command. |
FTR2163
| OPENFT: Request (&00). Remote system: File structure not supported(&01).
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. Response Transfer the file transparently. |
FTR2164
| OPENFT: Request (&00). Remote system: Syntax error in resulting file name(&01).
Meaning A syntax error other than 'operand missing' (FTR0010) or 'keyword unknown' (FTR0011) has been detected. Possible reasons: Values assigned outside the valid range Invalid operand separators Invalid value assignment characters Partially qualified file names
Meaning Repeat the command using the correct syntax. |
FTR2165
| OPENFT: Request (&00). 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. |
FTR2166
| OPENFT: Request (&00). 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. |
FTR2167
| OPENFT: Request (&00). Remote system: Access to '(&01)' denied (&02).
Meaning The command was not executed because the remote file only permits certain access modes. Response Correct the transfer direction, file name or file protection attributes on the remote system. Repeat the command. |
FTR2168
| OPENFT: Request (&00). Remote system: Follow-up processing exceeds length limit.
Meaning The maximum length of follow-up processing was exceeded; see the command syntax description. Response Shorten the follow-up processing, or use procedures. Repeat the command. |
FTR2169
| OPENFT: Request (&00). 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. Response Define the requisite TRANSFER-ADMISSION or correct it or check the authorization entered in FTAC. Repeat the command if necessary. |
FTR2170
FTR2171
| OPENFT: Request (&00). Remote system: Function not supported (&01).
OPENFT: Request (&00). Remote system: Processing admission invalid.
Meaning The command was not executed because the specifications in one of the PROCESSING- ADMISSION operands are incorrect. Response Define the required PROCESSING ADMISSION or correct it. Repeat the command if necessary.. |
FTR2172
| OPENFT: Request (&00). Remote system: Request queue full.
Meaning The command was not executed because the maximum number of permissible file transfer requests has been reached. Response Notify the FT administrator. Repeat the command later. |
FTR2173
| OPENFT: Request (&00). Remote system: User data encryption is mandatory
Meaning The remote system only accepts requests using data encryption. Response Repeat the request using data encryption. |
FTR2174
| OPENFT: No files corresponding to specified pattern found
Meaning Specify the correct file name pattern. |
FTR2195
| OPENFT: Request (&00). Remote system: openFT is not longer authorized to execute requests for this user.
|
FTR2196 OPENFT: Request (&00) has been canceled in the remote system.
|
| Meaning The request was deleted on the remote system before termination. |
FTR2197
| OPENFT: Request (&00). Remote system: File/directory '(&01)' could not be
created(&02).
Meaning The command was not executed because the file owner and user requesting the creation of a receive file are not the same. Response Match the user ID in the receive system's TRANSFER-ADMISSION to the ID of the receive file owner. Repeat the command. |
FTR2198
FTR2199
| OPENFT: Request (&00). Remote system: Higher-level directory no longer found
OPENFT: Request (&00). Remote system: I/O error for '(&01)' (&02).
Meaning An error occurred at input/output. Possible cause: The FT system continues to run after the message has been issued. Response Take the appropriate action in accordance with the error code. |
FTR2200
| OPENFT: Request (&00). 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. Response 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. |
FTR2201
| OPENFT: Request (&00). Remote system: File/directory '(&01)' no longer
available(&02).
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 to transfer a file migrated by HSM. Response Inform the operator if necessary or carry out an HSM recall for the file. Repeat the command. |
FTR2202
| OPENFT: Request (&00). Remote system: File/directory '(&01)' 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). Response Restore the remote file. Repeat the command. |
FTR2203
FTR2204
| OPENFT: Request (&00). Remote system: Home directory no longer found (&01)
OPENFT: Request (&00). Remote system: File/directory '(&01)' 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. Response 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 WRITE-MODE=EXTEND-FILE is specified, restore the receive file. Repeat the command. |
FTR2205
| OPENFT: Request (&00). 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. Response Define the file owner, correct TRANSFER-ADMISSION or FILE-NAME. Repeat the command. |
FTR2206
| OPENFT: Request (&00). Remote system: Pre-/post-processing error (&01).
Meaning The command executed in local pre-/postprocessing returned a result value other than OK. Response Correct the pre-/postprocessing command and issue it again. |
FTR2207
| OPENFT: Request (&00). Remote system: Exit code (&01) during
pre-/postprocessing (&02).
Meaning The command executed in local pre-/postprocessing returned the exit code (&01). Response Correct the pre-/postprocessing command in accordance with the exit code and issue it again. |
FTR2208
| OPENFT: Request (&00). 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. Response Correct the password in the file description or the command. Repeat the command. |
FTR2209
FTR2210
| OPENFT: Request (&00). Remote system: File/directory '(&01)' is now read only.
OPENFT: Request (&00). Remote system: File structure error (&01).
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 WRITE-MODE=EXTEND-FILE or the -e parameter are 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.
Response Correct the file or file attributes. If WRITE-MODE=EXTEND-FILE is specified, restore the receive file. Repeat the command. |
FTR2211
| OPENFT: Request (&00). Remote system: NDMS error (&01).
Response Repeat the request a little later. |
FTR2212
| OPENFT: Request (&00). Recovery failed (&01).
Meaning The restart could not be carried out. It may not have been possible to complete restartcapable pre-/postprocessing before termination of the server process (waiting time: max. minutes). |
| Response Repeat the command. |
FTR2213
| OPENFT: Request (&00). Remote system: Resource bottleneck.
Meaning The order was rejected because the partner system currently does not have the resources available to accept requests. Response Repeat the request a little later. |
FTR2214
| OPENFT: Request (&00). Remote system: Access to '(&01)' is no longer
permissible(&02).
Meaning The command was not executed because the send file or receive file only permits certain access modes (e.g. read only) or a directory was specified as the source or destination of a file transfer. or because no valid password for an FTAC profile has been stored in the local system for executing the ftexec command from a remote system.
Response Correct the transfer direction, write mode, file name or file protection attributes or specify a valid password for the FTAC profile. Repeat the command. |
FTR2216
| OPENFT: Request (&00). Remote system: File structure not supported (&01).
Meaning The request cannot be carried out because the file structure is not supported. An attempt was made, for example, to get a PLAM library or ISAM file from BS2000. Response Transfer the file transparently. |
FTR2217
| OPENFT: Request (&00). 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. Response Correct the transfer direction, retention period or file name. Repeat the command. |
FTR2218
| OPENFT: Request (&00). 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. |
FTR2225
| OPENFT: Information output canceled.
Meaning A show command was interrupted, for example. Response Repeat the command. |