What to do if ...

The error FTR2047 is displayed as a direct response to 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 FTSHWLOG (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 FTHELP xxxx (xxxx=RC)

The error FTR2169in 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 NCOPY

Possible cause	Suggested action
Error in the local system	Refer to the manual.

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)	Refer to manual
Exception with the error: FTR0035 File locked to prevent multiple access. Both the local and the remote file may be locked.

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.
Follow-up processing is required to access files that do not exist or that cannot be accessed with the PROCESSING-ADMISSION	Check the existence of the required files and their access control settings, if necessary correct PROCESSING-ADMISSION
JES rejects follow-up processing because a required "account number" was not specified in the PROCESSING-ADMISSION	Enter the "account number" in the PROCESSING-ADMISSION
The instance-specific job TSOJOB or JCLJOB is incorrectly structured	Ask the FT administrator if there are fundamental problems with follow-up processing

Problems during the execution of preprocessing or postprocessing commands and ftexec calls

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.

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 NCOPY command	Enter data at the system
Message overlooked, or a LOGOFF/ LOGON command was entered after the NCOPY command	View logging records
File transfer not yet terminated	Use NSTATUS to obtain information on the FT request
The initiator is not identical to the user ID in the TRANSFER-ADMISSION	Log on under the user ID specified in the TRANSFER-ADMISSION or ask its user whether a message has been output
The user has disabled message output with PROFILE NOINTERCOM	Output the message with LISTBC MAIL; for subsequent requests enable message output with PROFILE INTERCOM
	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 NCANCEL with FORCE- CANCELLATION=*YES.

Despite issuing the NCANCEL command, the request has been executed

Possible cause	Suggested action
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 onthe DASD volume.	Discuss the problem with the system administrator.

No information on a TNCOPY request

Possible cause	Suggested action
	Check using FTSHWLOG NUMBER=n

No result list

Possible cause	Suggested action
Specify LIST=*NONE (default value)
Printout lost

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
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 FTSHWPTN)	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 FTSHWPTN)	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