What to do if ...?

The error FTR2046 or FTR2047 is displayed as a direct response to TRANSFER-FILE (NCOPY)

Possible cause	Suggested action
Incorrect transfer admission in the local system	Enter a valid transfer admission
If openFT-AC is installed:
Transfer admission in the local system does not grant access to the desired request	Use /SHOW-FT-LOGGING-RECORDS (RECORD-TYPE= (FT=NONE)),NUMBER=n to output the return code (RC) of the FTAC logging record, and then check the reason for the rejection using /HELP-MSG MSG-ID= FTCxxxx, LANG=E (xxxx=RC)

The error FTR2169 as a response to TRANSFER-FILE and in other situations

Possible cause	Suggested action
Incorrect transfer admission in the remote system	Enter a valid transfer admission
Transfer admission in the remote system does not grant access to the required request	Determine the grounds for rejection in the remote system; With BS2000 partners: /SHOW-FT-LOGGING-RECORDS (RECORD-TYPE= (FT=NONE)),NUMBER=n and /HELP-MSG MSG-ID= FTCxxxx, LANG=E (xxxx=RC from logging record) With z/OS partners: FTSHWLOG (RECORD-TYPE=(FT=NONE)),NUMBER=n and FTHELP xxxx With Unix or Windows partners: ftshwl -rt=c and fthelp xxxx (xxxx=RC from logging record)

The error FTRxxxx is displayed as a direct response to TRANSFER-FILE (NCOPY)

Possible cause	Suggested action
Error in the local system	Use /HELP-MSG MSG-ID=FTRxxxx, LANG=E to request additional information or refer to the manual.

The error FTR2212 is displayed following a TRANSFER-FILE command with preprocessing or postprocessing

Possible cause	Suggested action
Problem in the remote system: remote system is not active	Contact system administrator of remote system
FT not started in the remote system
FT limits in the remote system have been reached, e.g. CONN-LIM in a remote BS2000 system
Network problems	Inform network administrator

The error FTR2109 (openFT protocol) resp. FTR0108 (FTAM) is displayed following the file management command

Possible cause	Suggested action
No BCIN or BCACT was entered for the remote system	Inform the system administrator

The error FTR2025, FTR2076 or FTR2199 is displayed following the file management command to an FTAM partner

Possible causes	Suggested action
The local or remote file management system reports an error which cannot be mapped onto any significant FTR message. The return code output is reported by the protocol, not by the file management system in question.	Try to use a normal COPY command to copy the (send) file to the specified receive file. Any error message which occurs in the process can be related to the FT command.

The error FTRxxxx in other situations

Possible cause	Suggested action
Error in the remote system (in most cases) Error in the local system (less common)	Use /HELP-MSG MSG-ID=FTRxxxx, LANG=E to request additional information.
Exception with the error: FTR0035 / FTR 2077 / FTR 2200 FILE LOCKED Both the local and the remote file may be locked.
FTR2043 and FTAM partner: rights for permitted actions may be missing in local system.	Use /MODIFY-FILE-FT-ATTRIBUTES to change rights

The follow-up processing should always be printed

Possible cause	Suggested action
	Define follow-up processing as an ENTER procedure using /LOGOFF or use the corresponding command sequence

Follow-up processing is not executed

Possible cause	Suggested action
Error in follow-up processing command and follow-up processing log was intercepted and suppressed. A space character after a semicolon, if several followup processing sessions were specified.	Check follow-up processing commands or prevent error interception in order to receive a log indicating the cause of the problem.

Problems during the execution of preprocessing or postprocessing commands

Possible cause	Suggested action
Error in the pre- or postprocessing command or a space character after a semicolon, if several pre/postprocessing commands were specified.	Check the pre-/postprocessing commands.
The job class, in which the processing job is to be started does not allow processing to be immediately carried out
The SPOOL sub-system has not started	Start the subsystem SPOOL (have it started)
The instance-specific jobs TSOVVJOB or TSONVJOB are incorrectly structured	Ask the FT administrator if there are fundamental problems with preprocessing or postprocessing

Remote follow-up processing in event of error (FAILURE PROCESSING) is not executed

Possible cause	Suggested action
The file transfer command was accepted (FTR0000), but an error was discovered before file transfer started (e.g. receive file locked)

No result information is displayed at the terminal

Possible cause	Suggested action
No input after the TRANSFER- FILE (NCOPY) command	Enter data at the system
Message overlooked, or a LOGOFF/ LOGON command was entered after the TRANSFER-FILE (NCOPY) command	View logging records
Asynchronous messages have been suppressed with MODIFY- MSG-OPTIONS OPERATOR- MSG=NO	Specify /MODIFY-MSG-OPTIONS OPERATOR-MSG=YES
A program has been loaded as a background task	Terminate the program
	Wait

A cancelled request is still in the request queue

Possible cause	Suggested action
The request was already active when the connection to the remote system was lost	Wait until the connection is restored so that openFT can notify the partner system about the cancellation. If the request does not “disappear” after restoring the connection, it can ultimately be deleted by the FT administrator using CNFT with FORCE- CANCELLATION=*YES.

Despite issuing the CANCEL-FILE-TRANSFER (NCANCEL) command, the request has been executed

Possible cause	Suggested action
CANCEL-FILE-TRANSFER (NCANCEL) came too late; the request had already been executed

A very large file cannot be transferred

Possible cause	Suggested action
There is not enough contiguous disk space on a public volume set.	Discuss the problem with the system administrator.

No information on a T RANSFER-FILE ( NCOPY ) request

Possible cause	Suggested action
	Check using /SHOW-FT-LOGGING-RECORDS NUMBER=n

No result list

Possible cause	Suggested action
Specify LIST=*NONE (default value)
Printout lost
The default public volume set of the request initiator was not attached at the end of transfer
The instance-specific job PRTJOB is incorrectly structured	Ask the FT administrator if there are fundamental problems with result lists

The file is locked, though the file transfer was completed

Possible cause	Suggested action
	Contact the system administrator; the file lock can be reset by the administrator with the VERIFY command

The request is not displayed with the SHOW-FILE-TRANSFER (NSTATUS) command, although MONJV is set to W or R

Possible cause	Suggested action
JV was changed illegally	Check in the dialog or the result list for the warning FTR0802
The public volume set for MONJV was not available during the update

The request marked with * remains in WAIT status

Possible cause	Suggested action
Partner deactivated by the FT administrator	If necessary, inform the system administrator

The request marked with ! remains in WAIT status

Possible cause	Suggested action
Connection setup failed
remote system not active	Contact system administrator of remote system
FT not active in the remote system	Contact system administrator of remote system
In a BS2000 system there was no BCIN/BCACT for the local system	Contact system administrator of remote system
Maximum number of connections permitted in remote system currently reached.

The request marked with ? remains in WAIT status

Possible cause	Suggested action
There is no BCIN/BCACT for the remote system (in the local system)	If necessary, inform the system administrator
The local system is not entered in the remote FT system	Contact system administrator of remote system.
No valid partner key is stored in the local system (STATE RAUTH in SHOW-FT-PARTNERS)	The FT administrator must store a current, public partner system key in the SYSKEY library on the configuration user ID of the local instance (element type D, name: symbolic name of the partner system as in the network descriptions file.
No valid local system key is stored in the remote system (STATE LAUTH in SHOW-FT- PARTNERS)	The local FT administrator must transmit a current, public key to the FT administrator of the partner system, which then must be stored in the appropriate location.

The request not marked remains in WAIT status

Possible cause	Suggested action
Normal waiting time for system resources	wait