|
|
This chapter explains the causes of the messages issued by the FTP Server and suggests appropriate responses.
Messages are presented in numerical order.
Explanation The user requests logoff from the host, and when the current file transfer completes, the logoff is processed.
Explanation The file transfer is started.
Explanation This is a multi-line server message produced during data transfer. The 150 message provides information about the file being transferred and about the settings associated with the data transfer.
This table shows the fields in this 150 message:
| Field | Description |
|---|---|
| type struct mode | Describe the settings associated with the data transfer. Read the FTP chapters of the Cisco IOS for S/390 User's Guide for details about these settings. |
| dsname | Indicates the data set being transferred. |
| lrecl blksize volser unit tracks1 tracks2 | Indicates the value for each field. These fields relate to the data set being transferred in the dsname field. |
Explanation The space allocation information supplied by the user is ignored because the space allocation was previously specified in a SITE command.
Explanation FTP is ready for command processing.
Explanation This reply is issued by the FTP server in response to the SITE QDISK command. It provides information on DASD devices.
Explanation The accounting information supplied by the user is unnecessary and is ignored.
Explanation This message marks the beginning of the listing from the STAT command.
Explanation This message marks the end of the listing from the STAT command.
Explanation This message marks the beginning of the listing from the HELP command.
Explanation This message marks the end of the listing from the HELP command.
Explanation This reply is issued by the FTP server in response to the SYST command. It identifies the operating system on which the server resides.
Explanation This message directs the user to supply a user command and user ID.
Explanation The user ID for logon to either Host A or Host B is logged off the host. The values for BYTE, ALLO, TYPE, STRU, and MODE parameters are reset to the defaults.
Explanation The user ID for logon to either Host A or Host B is logged off the host. The values for BYTE, ALLO, TYPE, STRU, and MODE parameters are saved.
Explanation The FTP server process at site sitename is ready to accept commands.
Explanation The command connection either to Host A or to Host B is closed.
Explanation The abort command issued successfully aborted the file transfer.
Explanation The file transfer completes successfully, and the disk file of the retrieving host is closed. However, the file contains zero data bytes.
Explanation The file transfer completes successfully, and the disk file of the receiving host is closed.
Explanation The FTP server produces a multi-line 226 response after a successful data transfer. Within the 226 response, statistics about the data transfer are reported back to the user. The following multi-line 226 response read data from an MVS data set and sent it across the network.
Transfer complete. 3439 bytes sent in 2.49 seconds (1381 bytes/s) Path FILE.NAME User UID Data bytes sent 6480 Disk tracks read 1 226
These are the fields in this 226 message:
| Field | Description |
|---|---|
| numbers bytes rate | Statistics about bytes transferred across the network and the rate of transfer per second. |
| dsname | Name of the data set read from disk and transferred over the network. |
| user | Indicates that user ID UID initiated the file transfer. |
| numwritten | Total number of data bytes read from disk for dsname. |
| tracks | Total number of disk tracks read. |
If the file transfer had been read from the network and written to a file on MVS, a multi-line 226 response might look like this:
226-Transfer complete 19 bytes received in 8.00 seconds (2 bytes/s) Dataset name: MVS.TEMP.DATA User UID Data bytes received 17 Disk tracks written 1 Records padded 1 226
This message is similar to the previous multi-line 226 response, except the data transfer is from the network to be stored on an MVS data set.
Depending on the file attributes of the file being written to, certain events will happen to records as they are placed into a file. Some messages that might appear in this 226 response are:
| Field | Description |
|---|---|
| Records padded n | Indicates the total number of records that had pad characters inserted at the end to accommodate the file structure. |
| Records truncated n | Indicates the total number of records truncated because the record sent was larger than the record size for the file. |
| Records folded n | Indicates the total number of records broken into multiple records because the record sent was larger than the record size for the file. |
| Records suspect n | Indicates total number of records shipped in block mode by the sending side that may contain suspect data (i.e., the data sent is suspected of errors and is not reliable). |
Explanation If SUNIQUE filename was specified, this message reflects the remote host's unique file name.
Explanation The user user is logged in with working directory dir. The IP address of the FTP server is address.
Explanation The specified file is deleted successfully.
Explanation The specified file is renamed successfully.
Explanation The file action is performed successfully.
Explanation This reply is issued by the FTP server when a change directory (CD/CWD) command is received with a path name of *DEV.NULL. Subsequent data transfers which cause data to be written to the file system by the FTP server will be written to a dummy data set (NULLFILE). To reverse this, enter another change directory command, specifying a different path name.
Explanation This reply is issued by the FTP server in response to the DELE command. It identifies the data set which has been successfully deleted.
Explanation prefix is the current default prefix for the user.
Explanation There is no default prefix defined.
Explanation The partitioned data set 'pathname' is the working directory.
Explanation A partitioned data set was created in response to a MKD command. The file attributes follow.
Explanation The user is directed to enter a password command and password.
Explanation The user is logged out, and the values for BYTE, ALLO, TYPE, STRU, and MODE parameters are saved.
Explanation The user is logged out, and the values for BYTE, ALLO, TYPE, STRU, and MODE parameters are not saved.
Explanation The user is directed to enter an accounting command and accounting information.
Explanation This is an interim reply indicating the completion of a part of a multi-part request. For instance, a RNFR (ReName FRom) command has been received, and the server is awaiting a RNTO (ReName TO) command.
Explanation A privileged user in DDNMVSOP mode (the operator control mode of OPEN-Link for IBM/MVS) cancels the FTP session.
Explanation FTP processing is incomplete because a software error was encountered in the host network's software.
Explanation The connection could not be opened.
Explanation File transfer is incomplete because the data connection between hosts is lost.
Explanation The file transfer operation aborts.
Explanation The file transfer aborts and FTP is ready for further user commands.
Explanation The DATAIDLE time specified for FTP expired before the last receive request completed. The transfer aborts.
Explanation File transfer is incomplete because input file is variable blocked and an invalid record descriptor word (RDW) length value was detected.
Explanation No access paths are available to write a file to or read a file from the device (volume).
Explanation Another user has exclusive control of the data set to be processed by FTP. Generally, the other user issued a PUT command to the data set causing an enqueue for exclusive control. Cisco IOS for S/390 provides resource serialization on the data set level, which has certain consequences for partitioned data sets. In particular, only one user at a time can access a data set for the purpose of storing data. If one FTP user is attempting to store a member into a partitioned data set, other users are prevented from accessing the same data set, even if the access is for a different member. However, multiple users can simultaneously retrieve members from the same partitioned data set because retrieve operations do not require exclusive control.
Explanation The operating system cannot access the device (volume) from which a file is to be read or to which a file is to be written.
Explanation This message is sent when the VTOC information cannot be retrieved.
The type of operation being processed to the PDS (oper) can be one of the following:
| DELETE | Delete a member. |
| RENAME | Rename a member. |
The type of MVS function being attempted for this operation (oper), where function can be one of the following:
| ENQUEUE | Enqueue a resource to the MVS system. |
| DEQUEUE | Dequeue a resource from the MVS system. |
| RESERVE | Reserve the disk volume where the PDS resides. |
The return code generated by the above MVS function (nn) is in hexadecimal. The return codes for the MVS function are described in the IBM Application Development Reference documentation set.
The name of the queue (queue) can be one of these:
| SPFEDIT | Used for text, source, or object data set. |
| SYSIEWLP | Used for load module data set. |
The DSNAME of the PDS is represented by (dsname); The name of the PDS member to be processed is represented by membername; the length of the RNAME field, in decimal, is represented by lll. The length of dsname is 44; if membername is included, the length of the RNAME field will be 52.
The type of operation being processed to the PDS (oper) can be one of the following:
| DELETE | Delete a member. |
| RENAME | Rename member. |
| STOR | Store a member. |
This message is sent when the PDS member is tied up by another user.
Explanation A block mode (Mode B) file transfer was in progress and a block header received contained invalid data in the flag field of the header.
Explanation A block mode (Mode B) file transfer was in progress and a block header received contained invalid data in the flag field of the header. This may be caused by the sender not being in Mode B.
Explanation An attempt to load a single or double byte character set translation table failed.
Explanation The file to be processed by FTP cannot be opened for reading or writing.
Explanation A host software error occurs, causing abnormal termination of the requested action.
Explanation An HSM recall of a migrated file does not occur within a specified amount of time. The request is cancelled.
Recommended Action Verify system default parameters with system programmer or issue a SITE RECALL command to increase default wait time.
Explanation The file being read or written contains an I/O error.
Explanation The file being written at the receiving host or read from the sending host contains an I/O error. The file transfer terminates abnormally.
Explanation The requested data set is currently allocated to another user, or otherwise cannot be mounted at this time.
Recommended Action Retry the FTP transfer later, or contact the tape librarian or operator for an explanation, as appropriate.
Explanation One of the modules required to initiate or complete the file transfer was missing at the time of execution of the command.
Explanation An attempt to mount and open a data set on magnetic tape failed. The return code is rrrrrrrr.
Explanation A request to mount a tape was cancelled by the operator. The request is cancelled.
Recommended Action Retry the FTP transfer later, or contact the tape librarian or operator for an explanation, as appropriate.
Explanation Either all tape units of the type requested are currently off-line or allocated to other users, or a PARALLELMOUNT or UNITCOUNT parameter has requested more units than are currently available.
Recommended Action Retry the FTP transfer when device(s) are available.
Explanation The wait time specified in the configuration or on a SITE command for a tape mount has expired. The request is cancelled.
Recommended Action Retry the FTP transfer later, or contact the tape librarian or operator for an explanation, as appropriate.
Explanation During either End-of-Volume (EOV) or close processing, the data management DCB ABEND exit was driven. An ABEND would have occurred had the exit not suppressed the ABEND. The file transfer is terminated. The system code of the suppressed ABEND is represented by xxx; The reason code of the suppressed ABEND is represented by rc.
Recommended Action Check the appropriate MVS manuals to identify the cause of the ABEND using the ABEND code xxx and the reason code rc. If the ABEND is issued during EOV processing due to insufficient space in the data set, make sure sufficient space exists in the data set or on the volume before restarting the file transfer. Certain close ABENDs such as the B14 occur when there is insufficient room in either the PDS directory or PDS data areas. After correcting the condition causing the ABEND, restart the file transfer.
Explanation During the CHECK of either a READ or WRITE macro, the synchronous error exit was driven. This exit extracted the error data listed in line two of the error via the SYNADF macro. The file transfer was terminated.
Recommended Action Attempt to diagnose the error using data provided by SYNADF. If possible, correct it and restart the data transfer. If the error is a wrong length record condition, it is likely that there is a record in the data set that exceeds the data set's block size. If this is the case, either delete the record or PDS member or change the attributes of the data set to have a larger block size.
Explanation An ABEND with the specified system ABEND code (xxx) occurred during the file transfer. The file transfer did not complete.
Recommended Action If the ABEND is due to an I/O error condition such as end of volume or data set close, correct the data management problem that caused the error and retry the file transfer. If the ABEND is of a programmatic nature, contact Customer Support.
Explanation Either the data transfer PTASK PABENDed with the specified user code (xxx) or the data transfer task PEXITed with the specified return code (xxx). Module FTPSFTDR could not match the code with a list of known exit codes and cannot determine whether the file transfer was successful. It is assumed that the file transfer failed.
Recommended Action Contact your Customer Support for assistance in diagnosing the cause of this message.
Explanation A CLOSE macro was issued after writing a member of a partitioned data set and an ABEND SB14 occurred indicating an I/O error occurred while updating the PDS directory. This condition is accompanied by MVS system message IEC217 B14-xx which explains in detail the reason IOS issued the SB14 ABEND. This error usually occurs when there is no room left in a PDS directory.
Explanation A host system error occurred during file transfer. The file transfer halts abnormally before completion.
Explanation The table of contents on the volume (VTOC) to which a file is to be written is full and can accept no more entries.
Explanation The host system had a problem with the allocation. Other IBM SVC99 messages may follow if SMS is coded on the GLOBAL statement in the APPCFGxx member. These messages are in the IBM documentation, MVS/ESA Vx System Messages Volume 1-5, GC28-1656 through GC28-1660. The value xxxxxxxx is the dynamic allocation (SVC99) return code.
Explanation This message indicates that the FTP transfer has aborted. The XX of RTNCD is the recovery action codes; YY is the specific error code; ZZZZ is the diagnostic and Sense codes.
Recommended Action Refer to the API Return Codes for a complete explanation of RTNCD.
Explanation No memory is available on the host attempting to execute the FTP command.
Explanation No memory is available on the host attempting to interpret the FTP command.
Explanation The entered command exceeds the maximum length of 82 characters.
Explanation The FTP software does not recognize the entered command.
Explanation An empty command line is entered and FTP ignored it.
Explanation Excessive operands found for a valid keyword or a parenthesis is missing from the command line.
Explanation The ending quote expected at the end of the FTP command is not entered.
Explanation Delimiter entered is unrecognizable or invalid.
Explanation A SITE DCBDSN command was received, but the model data set is migrated and cannot be recalled (possibly because NORECALL was specified in the FTP configuration, or by a previous SITE command).
Recommended Action If possible, recall the data set. Otherwise, change the DCBDSN data set name.
Explanation A SITE DCBDSN command was received, but the model data set cannot be found.
Recommended Action Change the DCBDSN data set name to the name of a cataloged data set.
Explanation A SITE DCBDSN command was received, but the model data set does not reside on a direct access device.
Recommended Action Change the DCBDSN data set name to the name of a cataloged data set on a DASD device.
Explanation A SITE command was received which specified the DCBDSN parameter, but the data set name specified (when appended to the current prefix) exceeds 44 characters.
Recommended Action Check the data set name specified. If it is a fully-qualified data set name, enclose it in single quotes.
Explanation A SITE command was received which specified an unknown parameter.
Recommended Action Read the Cisco IOS for S/390 User's Guide for a list of SITE parameters and syntax.
Explanation A SITE command was received which contained a keyword parameter specifying an invalid value for one or more subparameters.
Recommended Action Read the Cisco IOS for S/390 User's Guide for a list of SITE parameters and syntax.
Explanation A SITE command was received which contained the EXPDT parameter, but the RETPD had been previously specified. EXPDT and RETPD are mutually exclusive. The EXPDT parameter is ignored.
Recommended Action Use SITE RESET to remove the RETPD value before specifying EXPDT.
Explanation A SITE command was received which contained the RETPD parameter, but the EXPDT had been previously specified. EXPDT and RETPD are mutually exclusive. The RETPD parameter is ignored.
Recommended Action Use SITE RESET to remove the EXPDT value before specifying RETPD.
Recommended Action A SITE command was received that contained a keyword parameter which specified an over-long subparameter
Recommended Action Read the Cisco IOS for S/390 User's Guide for a list of SITE parameters and syntax.
Explanation A SITE command was received that contained a keyword parameter which requires a subparameter, but no subparameter was specified.
Recommended Action Read the Cisco IOS for S/390 User's Guide for a list of SITE parameters and syntax.
Explanation Indicates that one or more errors were detected in the SITE command.
This message is preceded by one or more 500 replies. Refer to accompanying messages to determine appropriate action.
Explanation Invalid or conflicting parameters are specified in the command.
Explanation The record format value entered in the SITE RECFM record format is invalid.
Explanation A MOUNT request specified a greater value than the maximum wait time allowed by the system configuration.
Explanation A char value other than Z, O, or B is specified in the SITE PAD char command.
Explanation A parameter value specified in the command line has a value outside its valid numeric range.
Explanation A SITE command specified BLP or NL where that LABEL option is not allowed by the system configuration.
Explanation A required operand or keyword is omitted from the command.
Explanation An attempt to load a single or double byte character set translation table failed.
Explanation An invalid value of zero (0) is specified on the SITE RECALL command.
Recommended Action Reissue SITE RECALL command with a value of 1-1439.
Explanation Wildcard characters ('*') are not permitted within the data set name of a partitioned data set.
Explanation An MKD command was received specifying a directory name within the current PDS directory.
Explanation A LIST or NLST command was received in directory mode and the path name specified a wildcard pattern character (* or %) in a qualifier other than the last qualifier. In directory mode, only the final qualifier can contain wildcard characters.
Recommended Action Change the path name or enter data set mode.
Explanation The requested facility is not implemented on the host, and the command cannot be performed.
Explanation The FTP functions that list data set information have not been implemented on the host. The user should use the LISTCAT and LISTDS TSO commands.
Explanation A SITE RECALL command is issued, but HSM is not defined to the system.
Recommended Action Verify ACFSFTP macro parameter HSM is not NORECALL. Edit APPCFGxx with HSM defined to FTP.
Explanation A SITE command was received to modify a parameter for tape, but tape processing has been disallowed by the system administrator.
Explanation Mode type compress (C) is not supported by the FTP Server.
Explanation The ABORT command is ignored because no file transfer was in progress when it was issued.
Explanation A RESTART or APPEND was attempted for a data set on magnetic tape. These commands are not supported for magnetic tape.
Explanation The entered command does not logically follow previous commands and cannot be processed.
Explanation The entered command is unacceptable because it is entered after the ALLO function for the specified file.
Explanation The entered command is unacceptable at this time and is refused.
Explanation The entered RENAME command is invalid.
Explanation The RESTART command is ignored because the STORE, RETRIEVE, or APPEND command was expected.
Explanation The message directs the user to supply user ID information to the host system.
Explanation Logoff from the host cannot be processed until the current file transfer completes.
Explanation The command entered is not acceptable because a PUT command cannot be accepted after a SITE SUBMIT.
Explanation A parameter used on the preceding command is not implemented on the specified host system.
Explanation The requested processing option is not implemented on the specified host.
Explanation The specified file TYPE/STRUcture combination is not supported by FTP.
Explanation BLOCK mode must be specified for a restart.
Explanation The CONN command request cannot be completed successfully; the open for the remote host connection fails.
Explanation Server FTP cannot create a data connection due to an SOS failure during the TOPEN for the data connection session.
Recommended Action Ensure that sufficient storage is available for the Cisco IOS for S/390 address space.
Explanation A MKD command attempted to create a partitioned data set 'pathname', but a cataloged data set already exists by that name.
Explanation An invalid user ID or password has been entered.
Explanation The user is directed to supply a user ID to the host system.
Explanation The user's password has expired. The user should update the password as shown.
Explanation The user's new password is invalid. Re-enter a new password as shown.
Explanation Accounting exit ACEXIT00 rejected the sign-on attempt. ACEXIT00 is a local exit under control of the Cisco IOS for S/390 System Administrator. Read the Cisco IOS for S/390 Customization Guide for more information about ACEXIT00. The account was probably entered incorrectly.
Recommended Action Retry the sign-on with a valid user ID/password/account combination. Contact your local Cisco IOS for S/390 System Administrator if the problem persists.
Explanation A bad parameter list was passed to the external security system (ACF2, RACF, or Top Secret). The signon fails.
Recommended Action Contact your Cisco IOS for S/390 support personnel.
Explanation A signon was attempted and the external security system (ACF2, RACF, or Top Secret) has become inactive.
Recommended Action Contact your local external security System Administrator.
Explanation A signon was attempted with an invalid password. The password was probably entered incorrectly.
Recommended Action Retry the signon with a valid user ID/password combination.
Explanation A signon was attempted without a password.
Recommended Action Retry the signon with a valid user ID/password combination.
Explanation A signon attempt was rejected because your external security system (ACF2, RACF, or Top secret) has revoked your user ID.
Recommended Action Contact your local external security Cisco IOS for S/390 System Administrator.
Explanation A signon attempt was rejected because your external security system (ACF2, RACF, or Top Secret) has revoked your user ID access to the group you are attempting to sign on with.
Recommended Action Contact your local external security System Administrator.
Explanation A signon attempt was rejected by a local installation security exit.
Recommended Action Contact your local external security System Administrator.
Explanation A signon attempt failed due to application security by your external security system (ACF2, RACF, or Top Secret).
Recommended Action Contact your local external security System Administrator.
Explanation A signon attempt failed due to terminal security by your external security system (ACF2, RACF, or Top Secret).
Recommended Action Contact your local external security System Administrator.
Explanation A signon was attempted using an unknown user ID. The user ID was probably entered incorrectly.
Recommended Action Retry the signon with a valid user ID/password combination.
Explanation A signon was attempted using a group that the user ID is not connected to.
Recommended Action Contact your local external security System Administrator.
Explanation A sign-on was attempted using the user ID of the Cisco IOS for S/390 address space. As a security precaution, Cisco IOS for S/390 will not accept its own user ID for a sign-on attempt.
Explanation The name supplied for the member of a partitioned data set is incorrect.
Explanation Dynamic allocation returned an information reason code of 5708. The attempted operation did not complete due to security reasons or an invalid catalog structure.
Recommended Action Determine if the catalog is password protected or whether the catalog structure is invalid.
Explanation The file specified for processing cannot be located on the host system.
Explanation A RENAME has been requested but the data set is on magnetic tape.
Explanation A serious error occurs during ACDYNAL processing of the PDS directory.
Explanation Access to the specified file is denied by the security (access control) system of the host.
Explanation File has been migrated and HSM recall abnormally terminates with an x'16D'.
Recommended Action Verify HSM is supported by the host operating system or HSM uses SVC 109 (x'6D'). Contact your local Cisco IOS for S/390 support personnel.
Explanation A DELETE for a data set failed, either because the SCRATCH routine returned an error code, or because the expiration date has not occurred.
Explanation A data set on a tape volume has been requested, but tape processing has been disallowed by the system administrator.
Explanation File has been migrated and HSM recall ability is not enabled for the user.
Recommended Action Issue a SITE RECALL command to enable HSM for file transfer.
Explanation The new member name must be enclosed in parentheses () and must not be qualified (i.e., no quotes).
Explanation FTP does not support multi-volume data sets.
Explanation The new member name given in the RNTO command already exists as a member in the PDS.
Explanation The STOW system command returned with an error indicating there were not enough directory blocks available to complete the rename.
Explanation A RENAME for a data set failed because the GDG base name was invalid.
Explanation A RENAME for a data set is issued but the new data set name specified a member name in addition to the data set name.
Explanation A RENAME for a data set is issued but the data set was not found.
Explanation A RENAME for a data set failed because a data set by that name already exists in the catalog.
Explanation A RENAME for a data set failed due to an OBTAIN error.
Explanation A RENAME for a data set failed due to a catalog error.
Explanation A RENAME failed because the name contained an invalid generation.
Explanation A RMD command was received specifying a non-partitioned data set.
Explanation A RMD command was received for a partitioned data set that contains members. Delete the members first, or use DELE to delete the PDS.
Explanation The file specified for processing cannot be located or no matching directory entries are found on the host system.
Explanation A SITE DCBDSN command was received, but the model data set has a record format (RECFM) or data set organization (DSORG) that is invalid for a PDS.
Recommended Action Change the DCBDSN data set name, or issue SITE RESET to reset SITE parameters.
Explanation A store unique (STOU) command was received. The server attempts to generate a unique name by appending 1-999 to the last qualifier of the data set name. It has exhausted the set of unique names.
Recommended Action Change the file name
A directory command (LIST/NLST) was received, but no entries were found to match the request. entries is one of the following:
| members | if the current working directory is a partitioned data set. |
| volumes | if the filetype is VTOC. |
| data sets | in all other cases. |
Recommended Action Change the file name
Explanation The device to which the transferred file is being written has run out of storage space. The file transfer is incomplete.
Explanation The receiving host does not have sufficient storage space for the data being transferred to it. The file transfer cannot continue.
Explanation The file name specified is incorrect, or it violates the syntax or naming conventions defined by the remote host.
Explanation The file transfer completes unsuccessfully. A SITE command probably was issued to a specific VOLUME or UNIT and the file (data set) exists as a cataloged entry on another volume.
Explanation One of the SITE commands (i.e., SPACE, TRACK, CYLINDER, BLOCKS) implies that the data set is to be created, but the data set already is defined.
Explanation This message indicates one of these conditions:
Explanation The logical record length and blocksize specified are either invalid or inconsistent.
Explanation Data transferred from the sending host does not replace the existing data set on the receiving host because the data set organizations conflict.
Explanation The logical record length, blocksize, and/or record format specified in the preceding SITE command(s) are not consistent with the characteristics of the existing file on the receiving host.
Explanation A RETR command was received specifying a partitioned data set as the pathname. A member name must be supplied.
|
|