Return codes for NCOPY, NDEL, NLMOD, NLSHOW, NMOD and NSHOW

The table below lists only the return codes for the current version.

Return code			Meaning
SC2	SC1	MC
00	00	0000	The macro call was stored in the local system's request queue or the request was concluded successfully.
00	01	FFFF	In the expansion of the L-form of the macro call, a function is demanded which is not supported by FT.
00	02	FFFF	In the expansion of the L-form of the macro call, a function unit is demanded which is not supported by FT.
00	03	FFFF	In the expansion of the L-form of the macro call, a version is demanded which is not supported by FT.
00	20	0320	The macro call could not be executed because the system was generated without job variables, or the maximum number of job variables for the user has been reached, or a temporary job variable was specified, or the specified job variable for the user is not accessible, or the specified job variable is monitoring another FT request, or the specified password for the job variable is incorrect.
00	20	0321	FTAM, NDMS, FJAM, or operating system error other than a DMS or transport system error.
00	20	0322	Following termination of the file transfer request, the job variable monitoring the request has inconsistent contents. Possible cause: During transfer, the job variable was accessed other than for reading. This does not affect the result of the transfer and can be determined from the result list or the asynchronous end message.
00	20	0324	The macro call was not executed due to inconsistent request data.
00	20	0352	The macro call was not executed because the system was generated without job variables, or the maximum number of job variables for the user has been reached, or a temporary job variable was specified, or the specified job variable for the user is not accessible, or the specified job variable is monitoring another FT request, or the specified password for the job variable is incorrect.
00	20	0353	The macro call was not executed because of an internal error.
00	20	0356	The macro call was not executed because there is insufficient space on the disk/partition on which the logging files are stored.
00	20	0357	The macro call was not executed because there is insufficient space on the disk/partition on which the internal files are stored.
00	20	035B	The macro call was not executed because of teleservice restrictions. Possible cause: Only one partner with the teleservice name is supported.
00	20	035E	The macro call was not executed because the required transfer protocol is not installed.
00	20	03E7	The macro call was not executed because of an abnormal termination.
00	40	0014	The command was not executed because the send file is not located in the catalog or on a data volume in the local system, or the send file is not or is no longer or the receive file is no longer located in the catalog or on a data volume in the corresponding system.
00	40	00EC	The macro call was rejected because the set instance is not present.
00	40	03FD	The macro call was not executed because the request has not yet been terminated with FORCE=NO.
00	40	040C	The macro call cannot be accepted because it can only be entered by authorized users.
00	40	040E	The macro call could not be executed because the request is terminating and can no longer be deleted.
00	40	0417	The macro call cannot be accepted because no requests were found.
00	40	07E0	The macro call could not be executed because the local directory is not empty.
00	40	07E1	The macro call ca not be accepted because the local send or receive file only permits certain access operations.
00	40	07E2	The macro call cannot be executed because the file properties could not be modified as desired. Possible causes: no access rights for the local file the desired transfer attributes for the local file are not compatible with the file's BS2000 properties
00	40	07E3	The macro call cannot be executed because the file owner is not the same as the user who requested the setting up of a local receive file.
00	40	07E5	The macro call could not be executed because the local CCS name is unknown, or the CCS names of the send and receive files cannot be mapped to one another or the partner system does not support the retrieval of files in transparent format.
00	40	07E6	The macro call cannot be accepted because the local file could not be created on a receive request because the specified path does not exist.
00	40	07E7	The macro call cannot be executed because a local receive file which already exists cannot be set up with WRITE-MODE=NEW. WRITE-MODE=NEW may also have been set as a result of a restriction in the employed transfer admission.
00	40	07E8	The macro call was not executed because the FT system only transfers individual file generations.
00	40	07E9	A DMS error occurred during the processing of the macro call. Additional information can be found in the field xxDMSCO (4 bytes).
00	40	07EA	The macro call cannot be executed because the relative file name was specified in the transfer request. The absolute file name as extended by openFT is no longer than permitted.
00	40	07EB	The macro call was not executed because the local file name was not specified either explicitly or via the employed TRANSFER-ADMISSION.
00	40	07EC	The macro call was not executed because the management password of the local file is missing or incorrect.
00	40	07EE	The macro call was not executed because the local home directory was not found.
00	40	07F1	The macro call was not executed because the owner of the send or receive file is not defined in the local system, or the file owner is not the same as the user who requested the creation of a receive file.
00	40	07F2	The macro call was not executed because the password for the local send file or the receive file is missing or incorrect.
00	40	07F4	The macro call was not executed because the retention period which protects the local receive file against being overwritten (RETENTION PERIOD) has not yet expired.
00	40	07F5	The macro call cannot be executed because the local file is write-protected.
00	40	07F6	The macro call was not executed because of a file structure error.
00	40	07F7	The macro call was not executed because it is not possible to access the local file, for example because the absolute file name is too long.
00	40	07F8	The macro call was not executed because the CCS name of the send and receive files cannot be mapped to one another or the partner system does not support the retrieval of files in transparent format.
00	40	07FA	The macro call could not be executed because it is not possible to add an extension to a local file for transparent transfer.
00	40	07FB	The macro was not executed because the local send file or the receive file only permits certain access modes (e.g. read only).
00	40	07FC	The macro call could not be executed because the total of follow-up processing + prefix + suffix (from profile) is too long.
00	40	07FD	The macro call was not executed because the specifications in one of the operands of the local PROCESSING-ADMISSION is incorrect.
00	40	07FE	The macro call was not executed because the specifications in one of the operands of the local TRANSFER-ADMISSION is incorrect.
00	40	07FF	The macro call was not executed because the request was rejected by the product FTAC-BS2000 due to missing admissions.
00	40	0800	The macro call was not executed because the required function for the selected protocol is not available.
00	40	0801	The macro call was not executed because local follow-up processing is only available for the openFT protocol.
00	40	0802	The macro call cannot be executed because the partner machine does not support the data integrity check function.
00	40	0803	The macro call cannot be executed because the partner machine does not support the data encryption function.
02	40	07DE	No file attributes apart from the file name were specified.
00	40	0816	The macro call was not executed because openFT is not authorized to process requests for this user.
00	40	0818	The macro call was cancelled because of the command CANCEL-FILE-TRANSFER or NCANCEL or because the time specified in TRANSFER-FILE or NCOPY has elapsed. Follow-up processing for the local system has started if no error occurred during this operation. Follow-up processing for the remote system will be started as soon as all the resources have been assigned.
00	40	0819	The macro call cannot be executed because errors occurred during encryption.
00	40	081A	The macro call cannot be executed because the file owner is not the same as the user who requested the setting up of a local receive file.
00	40	081B	The macro call cannot be executed because the higher-level local directory could no longer be found.
00	40	081C	The macro call cannot be executed because the local file can no longer be accessed. It may have been deleted during a transfer.
00	40	081D	The macro call cannot be executed because the local send or receive file can no longer be accessed, for example because it was deleted during an interruption at the openFT system.
00	40	0820	The macro call was not executed because the local home directory could no longer be found.
00	40	0822	The macro call was not executed because the owner of the local send file or the receive file is not defined in the corresponding system, or the file owner is not the same as the user who requested the creation of a receive file.
00	40	0823	The macro call was not executed because the command executed by local preprocessing/postprocessing returned a result other than 'OK'.
00	40	0824	The macro call was not executed because the command executed by local preprocessing/postprocessing returned an exit code.
00	40	0825	The macro call was not executed because the password for the local send file or the receive file is missing or incorrect.
00	40	0826	The macro call was not executed because the request is now writeprotected.
00	40	0827	The macro call was not executed because of a file structure error in the local file. File structure errors may be, for example: The attributes of the send file are incomplete. The data in the send file do not match the structure attributes. The records in the send file are too long. The send and receive files have a different structure in WRITE-MODE=EXTEND-FILE or -e (e.g. records of fixed/variable length). The send or receive file is an element from an old LMS library (not PLAM). The send file has a non-even blocking factor (e.g.BLKSIZE=(STD,1)) and the receive file is to be stored in an NK4 pubset.
00	40	0829	The macro call was not executed because the local restart attempt was unsuccessful. Possible cause: A preprocessing/postprocessing command could not be completed before openFT terminated.
00	40	082A	The macro call was not executed because an error occurred during the final phase of local file transfer. In the case of extended transfers, the recipient should check whether the file was nevertheless transferred correctly. However, error follow-up processing is still performed if it has been specified.
00	40	082C	The command was not executed because the local send file or the receive file only permits certain access modes (e.g. read only), or a directory was specified as the source or destination for a file transfer.
00	40	082E	The macro call was not executed because the retention period which protects the local receive file against being overwritten (RETENTION PERIOD) has not yet expired.
00	40	082F	The macro call could not be executed because it is not possible to add an extension to a local file for transparent transfer.
00	40	0830	The macro call could not be executed because the file structure is not supported.
00	40	083D	The macro call cannot be executed because the request to establish a connection was rejected by the local transport system.
00	40	083E	The macro call cannot be executed because the data integrity check indicates an error.
00	40	083F	The macro call cannot be executed because no key pair set is present, or the key length was set to 0. Requests can only be carried out without data encryption or data integrity checking.
00	40	0840	The macro call cannot be executed because the partner machine does not support the data integrity check function.
00	40	0841	The macro call cannot be executed because the partner machine does not support the data encryption function.
00	40	0842	The macro call cannot be executed because the partner has rejected the instance ID of the local system for security reasons or because of an inconsistency. Possible cause: A network description contains both the instance ID and the migration ID %.processor.entity for different partners.
00	40	0843	The macro call cannot be executed because the remote system has interrupted the request.
00	40	0844	The macro call cannot be executed because the local application is not defined in the transport system, or the tnsxd process is not running in the Unix system.
00	40	0846	The macro call cannot be executed because the local system could not be authenticated at the partner.
00	40	0847	The macro call cannot be executed because the local system is not known in the partner system (e.g. BS2000/OSD or z/OS)
00	40	0848	The macro call cannot be executed because the partner specified as the remote system cannot be expanded into an address in the local system.
00	40	0849	The macro call cannot be executed because the remote system could not be authenticated at the local system.
00	40	084A	The macro call cannot be executed because the connection has been rejected or interrupted.
00	40	085C	The macro call could not be executed because openFT is not authorized to process requests for this user.
00	40	085D	The macro call could not be executed because the remote directory is not empty.
00	40	085E	The macro call could not be executed because the file attributes in the remote system do not correspond to the request parameters. Possible cause: A directory was specified instead of a remote file.
00	40	085F	The properties of the remote file could not be modified as desired in the macro call. Possible causes: no access rights for the file the desired combination of access rights is not supported by the remote system if the remote system is a BS2000 system: the file is protected by ACL
00	40	0860	The macro call cannot be executed because the file owner is not the same as the user who requested the setting up of a remote receive file.
00	40	0861	The macro call could not be executed because the CCS names of the send and receive files cannot be mapped to one another or because the partner system does not support the retrieval of files in transparent format.
00	40	0862	The macro call cannot be executed because the higher-level local directory in the partner system could not be found.
00	40	0863	The macro call was not executed. Possible causes: The command was not executed because an existing receive file may not be set up again with WRITE-MODE=NEW or the -n switch. WRITE-MODE=NEW or -n may also have been set via a restriction in the employed transfer admission. ftcredir: The specified directory already exists.
00	40	0864	The macro call was not executed because the FT system only transfers individual file generations.
00	40	0865	A DMS error occurred during the processing of the macro call.
00	40	0866	The macro call was not executed because the resulting remote file name is too long. Possible causes: value assignments outside of the permitted range of values invalid operand separator invalid value assignment character partially qualified file names BS2000: The syntax error which occurred does not relate to a 'missing operand' or 'unknown keyword'.
00	40	0868	The macro call was not executed because the remote file name was not specified either explicitly or via the employed TRANSFER-ADMISSION.
00	40	0869	The macro call was not executed because the management password of the remote file is missing or incorrect.
00	40	086B	The macro call cannot be executed because the send file is not or is no longer located in the catalog or on a volume in the remote system.
00	40	086C	The macro call was not executed because the remote home directory was not found.
00	40	086F	The macro call was not executed because the owner of the remote send file or the receive file is not defined in the corresponding system, or the file owner is not the same as the user who requested the creation of a receive file.
00	40	0870	The macro call cannot be executed because the password for the send file or the receive file in the remote system is missing or incorrect.
00	40	0871	The macro call cannot be executed because the retention period which protects the receive file in the remote system against being overwritten (RETENTION PERIOD) has not yet expired.
00	40	0872	The macro call cannot be executed because the remote file or remote directory is write-protected.
00	40	0873	The macro call cannot be executed because the file structure is not supported. An attempt was made, for example, to retrieve a PLAM library or ISAM file from the BS2000 system.
00	40	0874	The macro call cannot be executed because of a syntax error other than 'missing operand' or 'unknown keyword' in the remote system. Possible causes: value assignments outside of the permitted range of values invalid operand separator invalid value assignment character partially qualified file names
00	40	0875	The macro call could not be executed because the partner system does not support the transfer of files in transparent format.
00	40	0876	The macro call could not be executed because it is not possible to add an extension to a remote file for transparent transfer.
00	40	0877	The macro call cannot be executed because the remote system only permits certain access modes.
00	40	0878	The macro call cannot be executed because the length of remote follow-up processing has been exceeded.
00	40	0879	The macro call cannot be executed because the specifications in one of the operands of the remote TRANSFER-ADMISSION are incorrect, or the request was rejected by the FTAC because of missing admissions.
00	40	087A	The macro call cannot be executed because the required function is not supported.
00	40	087B	The macro call was not executed because the specifications in one of the operands of the remote PROCESSING-ADMISSION are incorrect.
00	40	0893	The macro call was not executed because openFT is not authorized to process requests for this user.
00	40	0894	The macro call was cancelled because the request was deleted in the remote system before termination.
00	40	0895	The macro call was not executed because the file owner is not the same as the user who requested the setting up of a remote receive file.
00	40	0896	The macro call was not executed because the higher-level remote directory could no longer be found.
00	40	0897	The macro call was not executed because an error occurred during input/output. Possible cause: The remote send or receive file was deleted during the transfer.
00	40	089A	The macro call was not executed because the remote file is not or is no longer located in the catalog or on a volume in the corresponding system (e.g. after a restart).
00	40	089B	The macro call was not executed because the remote home directory could no longer be found.
00	40	089D	The macro call was not executed because the owner of the send or receive file is not defined in the corresponding remote system, or the file owner is not the same as the user who requested the creation of a receive file.
00	40	089E	The macro call was not executed because the command executed by remote preprocessing/postprocessing returned a result value other than 'OK'.
00	40	089F	The macro call was not executed because the command executed by remote preprocessing/postprocessing returned an exit code.
00	40	08A0	The macro call was not executed because the password for the remote send file or the receive file is missing or incorrect.
00	40	08A1	The macro call was not executed because the remote file or remote directory is write-protected.
00	40	08A2	The macro call was not executed because of a file structure error in the remote system. File structure errors may be, for example: The attributes of the send file are incomplete. The data in the send file do not match the structure attributes. The records in the send file are too long. The send and receive files have a different structure in WRITE-MODE=EXTEND-FILE or parameter -e (e.g. records of fixed/variable length) BS2000: The send or receive file is an element from an old LMS library (not PLAM). BS2000: The send file has a non-even blocking factor (e.g. BLKSIZE=(STD,1)) and the receive file is to be stored in an NK4 pubset.
00	40	08A4	The restart could not be executed. It is possible that a restartable preprocessing/postprocessing operation could not be concluded before termination of the server process (max. waiting time: 10 minutes).
00	40	08A6	The macro call was not executed because the remote send file or the receive file only permits certain access modes (e.g. read only), or a directory was specified as the source or destination for a file transfer.
00	40	08A8	The macro call cannot be executed because the file structure is not supported in the remote system. An attempt was made, for example, to retrieve a PLAM library or ISAM file from the BS2000 system.
00	40	08A9	The macro call was not executed because the retention period which protects the remote receive file against being overwritten (RETENTION PERIOD) has not yet expired.
00	40	08AA	The macro call could not be executed because it is not possible to add an extension to a remote file for transparent transfer.
00	40	08B2	The macro call cannot be accepted because the content of the specified job variable is inconsistent. Possible cause: The user made a non-read access to the job variable while it was monitoring an FT request. The content of the job variable can therefore no longer be used.
00	40	08B3	The macro call cannot be accepted because another process as well as openFT is using the job variable.
00	40	08B4	The macro call was not executed because the referenced job variable is not present.
00	80	0023	The macro call cannot be executed because the local send or receive file is already protected against simultaneous updating by another process.
00	80	0029	The macro call cannot be accepted because the maximum limit for file transfer requests has been reached.
00	80	006C	The macro call could not be accepted because the partner system is not currently available.
00	80	07ED	The macro call cannot be executed because the volume for the local send file or the receive file is not mounted, is unknown or occupied, or the file extends over more than one private disk, or an attempt was made to transfer a file migrated with HSMS.
00	80	07F0	The macro call was not executed (or was discontinued) because the permitted storage space in the receive system for the user ID specified in TRANSFER-ADMISSION has been reached, or the send file contains an excessively long sequence of empty blocks, or the primary and/or secondary assignment of the password-protected receive file is too small. Once this problem has occurred, the local receive file will no longer be extended or generated.
00	80	081D	The macro call was not executed because the local send or receive file is already protected against simultaneous updating by another process.
00	80	081E	The macro call was not executed because the volume for the local send file or the receive file is not mounted, is unknown or occupied, or the file extends over more than one private disk, or an attempt was made to transfer a file migrated with HSMS.
00	80	0821	The macro call was not executed (or was discontinued) because the permitted storage space in the local receive system for the user ID specified in TRANSFER-ADMISSION has been reached, or the local send file contains an excessively long sequence of empty blocks, or the primary and/or secondary assignment of the password-protected local receive file is too small. Once this problem has occurred, the local receive file will no longer be extended or generated.
00	80	0828	The macro call was rejected because the partner system does not currently possess any resources for the acceptance of requests.
00	80	082D	The macro call was rejected because the request was rejected by FTAM with the specified FTAM diagnostic code.
00	80	084D	The macro call cannot be executed because there was no data exchange due to a line interruption or line procedure error.
00	80	084E	The macro call cannot be executed because no further transfers are currently possible since the maximum number of simultaneous transfers has been reached.
00	80	084F	The macro call cannot be executed because no data was transferred within the specified number of seconds because, for example, the connection is interrupted, the partner is not sending and the local system is waiting for data.
00	80	0867	The macro call was not executed because the remote send or receive file is already protected against simultaneous updating by another process.
00	80	086A	The macro call was not executed because the volume for the remote send file or the receive file is not mounted, is unknown or occupied, or the file extends over more than one private disk, or an attempt was made to transfer a file migrated with HSMS.
00	80	086E	The macro call was not executed (or was discontinued) because the permitted storage space in the receive system for the user ID specified in TRANSFER-ADMISSION has been reached, or the remote send file contains an excessively long sequence of empty blocks, or the primary and/or secondary assignment of the password-protected remote receive file is too small. Once this problem has occurred, the remote receive file will no longer be extended or generated.
00	80	087C	The macro call was not executed because the maximum limit for file transfer requests has been reached.
00	80	0898	The macro call was not executed because the remote send or receive file is already protected against simultaneous updating by another process. An attempt was made, for example, to access a library which is open in z/OS.
00	80	0899	The macro call was not executed because the volume for the remote send file or the receive file is not mounted, is unknown or occupied, or the file extends over more than one private disk, or an attempt was made to transfer a file migrated with HSMS.
00	80	089C	The macro call was not executed (or was discontinued) because the permitted storage space in the remote receive system for the user ID specified in TRANSFER-ADMISSION has been reached, or the remote send file contains an excessively long sequence of empty blocks, or the primary and/or secondary assignment of the password-protected remote receive file is too small. Once this problem has occurred, the remote receive file will no longer be extended or generated.
00	80	08A3	An NDMS error occurred during the processing of the macro call.
00	80	08A5	The macro call was rejected because the partner system does not currently possess any resources for the acceptance of requests.
00	80	08A7	The macro call was rejected by FTAM with the specified FTAM diagnostic code.

Table 1: Return codes for NCOPY, NDEL, NLMOD, NLSHOW, NMOD and NSHOW