Return codes for the CALL macros NCOPY, NCANCEL and NSTAT

The field MAIN-RETURN-CODE contains the error class and can have the following values:

0	No error.
1	Error; however, the program can successfully repeat the same call later without further intervention.
2	Error; however, the program can repeat the call unchanged after an intervention by a terminal user or operator.
3	Error which does not belong to class 1 or 2.

MAIN- RETURN- CODE	SUB- RETURN- CODE	Meaning
0	0	The CALL macro was saved in the request file of the local system.
0	1	Follow-up processing in the local system was not executed, because the entries in the PROCESSING-ADMISSION are erroneous.
0	2	Follow-up processing was not executed for the system whose PROCESSING-ADMISSION is missing.
0	3	The FT request was only started with normal priority.
1	1	The CALL macro cannot be accepted/executed, since the send or receive file is protected via another process from simultaneous updating.
1	2	The CALL macro cannot be accepted, since the maximum permissible limit for file transfer requests has been exceeded.
2	1	The CALL macro cannot be accepted/executed, since the specifications in one of the TRANSFER-ADMISSIONs are erroneous.
2	2	The CALL macro cannot be accepted/executed, since the owner of the send or receive file is not defined in the corresponding system, or since the file owner and the user who wishes to create a receive file do not correspond.
2	3	The CALL macro cannot be accepted, since the remote system is not in the partner list of the local system.
2	4	The CALL macro cannot be accepted/executed, since the password for the send or receive file is missing or wrong.
2	5	The CALL macro cannot be accepted/executed, since the send or receive file does not allow multiple users.
2	6	The CALL macro cannot be accepted/executed, since the send or receive file only permits certain access operations (e.g. read only).
2	7	The CALL macro cannot be accepted/executed, since the protection time for the overwriting of the receive file has not expired.
2	8	The CALL macro cannot be (further) executed, since the space which the user (as defined in the TRANSFER-ADMISSION) is permitted to use for saving in the receiving system is full, either because the send file contains too many consecutive blanks or because the primary assignment of the password-protected receive file is too small. The receive file cannot be created or expanded.
2	9	The CALL macro was not executed because the system was generated without job variables or the user does not have access to the job variable specified or the job variable specified is monitoring another FT request or the password specified is not the right one for the job variable.
2	10	The CALL macro was not executed because the job variable in question is not present.
2	11	The CALL macro was not executed because the job variable specified does not monitor an FT request.
2	12	The CALL macro was not executed because the contents of the job variable specified are not consistent.
2	13	The CALL macro was not executed due to an error in the local PROCESSING-ADMISSION.
2	14	The macro was not executed because the file encryption function is not installed.
2	15	The macro was not executed because the file expansion for transparent transfer is not permitted.
2	20	The CALL macro was not executed because the request has not yet been cancelled with FORCE-CANCELLATION=NO.
2	129	The macro cannot be accepted because the local FT system is currently unavailable.
3	1	The macro cannot be accepted because at least one operand is missing.
3	2	The macro cannot be accepted because it contains a syntax error unlike “operand missing” or “keyword unknown”. Such syntax errors include: value assignments outside the permitted value range, wrong operand separators, wrong characters assigned to the value or partially qualified filenames.
3	3	The macro cannot be accepted/executed because the FT system only transfers individual data generations.
3	4	The CALL macro cannot be accepted because the send file is not in the catalog or on a data carrier of the local system. The CALL macro cannot be executed because the send or receive file is no (longer) in the catalog or on a data carrier of the corresponding system.
3	5	The CALL macro cannot be accepted/executed because the send file is empty.
3	6	The CALL macro cannot be accepted because no requests could be found.
3	7	The CALL macro cannot be accepted/executed because an existing receive file cannot be recreated.
3	8	The CALL macro cannot be accepted/executed because the file owner and the user requesting the creation of a receive file do not correspond.
3	9	The CALL macro cannot be accepted/executed because the data carrier for the send or receive file is either not mounted, unknown or unnamed or multiple data carriers are not supported.
3	10	The CALL macro cannot be accepted because it can only be input by authorized users.
3	11	The CALL macro cannot be accepted/(further) executed because there is a file structure error. File structure errors include: the attributes of the send file are incomplete. The data of the send file do not correspond to the structure attributes. The send file sentences are too long. The send file and the receive file have a different structure for WRITE-MODE=EXTEND-FILE (e.g.: sentence fixed/variable length).
3	12	During the processing of a CALL macro, a DVS error occurred. The DVS error code is in the DMS-RETCODE field in hexadecimal notation.
3	13	During the processing of a CALL macro, an NDMS error, FJAM error or operating system error occurred which was neither a DVS error nor a transport system error.
3	17	The CALL macro cannot be accepted because the start time is more than 32767 minutes in the future, or because the abort time is either in the past, before the start time or more than 32767 minutes in the future.
3	18	An error occurred while loading the FT runtime module. The return code returned by the LINK macro is in the field LINK-RETCODE in hexadecimal notation.
3	19	The CALL macro was not executed because the local and remote systems are not compatible. Neither system can connect with the other, or at least one of the systems does not support the function called.
3	20	The CALL macro was not executed, because the filename was neither explicitly entered nor indicated by means of the TRANSFER-ADMISSION used.
-1	1	The function NSTAT is not supported by the FT version installed (version is smaller than V3.0).
-1	2	FT runtime module not available.
-1	3	The version of the one of the COPY elements used is not supported.
-1	129	The CALL macro cannot be accepted because there is not yet an output for asynchronous end messages.
-1	130	The CALL macro cannot be accepted because the FT system has not yet completed a previous shutdown command (e.g. FTSTOP).