|
|
This chapter describes the messages issued by the FTP program. These include messages T01F1001 through T01F1999.
VLT invocation option specified, but file SYSVLT is not allocated Explanation Client program FTP or FTP2 was running in batch mode. The VLT invocation option was specified. File SYSVLT does not exist.
Recommended Action Add a file in the JCL setup for the batch FTP job:
//SYSVLT DD SYSOUT=*,DCB=BLKSIZE=133GETMAIN FAILED FOR DSA IN programExplanation This message appears when the client software wants to attempt to extract an encrypted password. Not enough core was available to perform a GETMAIN. The client cannot extract an encrypted password. The program parameter identifies the program where the failure occurred. If the client program is running interactively the client prompts the user for a password.
Recommended Action The user should allocate a larger region size to their TSO session. If the problem persists, contact Customer Support.
FREEMAIN FAILED FOR DSA IN programExplanation The GETTRPW subroutine issued a FREEMAIN and it failed. The GETTRPW routine performs password extraction. The client cannot extract an encrypted password. The program parameter identifies the program where the failure occurred. If the client program is running interactively, the client prompts the user for a password.
Recommended Action Contact Customer Support.
GETTRPW RETURN CODE = rcExplanation A user invoked client program FTP. An unexpected error occurred in initialization routine GETTRPW and returned the specified return code (rc).
Recommended Action Contact Customer Support. Save the rc return code.
APP option specified, but no application name entered Explanation A user invoked one of the client programs (TCPEEP, FTP, FTP2, or TELNET) utilizing the APP invocation option but no VTAM application name was entered. Client programs TCPEEP, FTP, or FTP2 then terminate. Client program TELNET uses the default VTAM application name.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the TCPEEP command. A user can issue the APPLID command under Client Telnet to change the VTAM application name.
APP name is longer than 8 characters vtam_app_name Explanation A user invoked one of the client programs (TCPEEP, FTP, FTP2, or TELNET) utilizing the APP invocation option, but the VTAM application name (vtam_app_name) was longer than eight characters. Client programs TCPEEP, FTP, or FTP2 then terminate. Client program TELNET uses the default VTAM application name.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the TCPEEP command. A user can use the APPLID command under Client Telnet to change the VTAM application name.
APP and SYS options specified, SYS option ignored Explanation A user invoked a client program (TCPEEP, FTP, FTP2, or TELNET) utilizing both the APP and SYS invocation options. The client program ignored the SYS option and used the APP option.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the TCPEEP command.
VLT log follows: Explanation Client program FTP or FTP2 was running in batch mode utilizing VLT tracing. This should be the first line in the SYSVLT DD file.
GTF logging invoked Explanation Client program FTP or FTP2 was running interactively utilizing GTF tracing.
Unable to allocate VLTLOGWK, return code from VLTGLGE=rc Explanation An attempt to invoke client program FTP or FTP2 with the VLT invocation option. The clients call to VLTGLGE failed to allocate a VLTLOGWK work structure. VLT cannot trace without a VLTLOGWK work structure. The return code (rc) is the GETMAIN failure return code. VLT tracing stopped; FTP continues.
Recommended Action Save the output of the FTP job. Contact Customer Support.
Line number n stripped off end of lineExplanation Client program FTP or FTP2 was running in batch mode. Line number n was found in columns 73 to 80 of the SYSGET input file line. The line number is ignored from the command stream to be presented to the FTP servers.
Recommended Action The message disappears if the line numbers are removed from the batch FTP SYSGET DD input file.
Explanation This message displays on the user's screen when a Telnet or FTP user attempts to connect to Cisco IOS for S/390 while an SOS condition exists.
Recommended Action Ensure that sufficient storage exists for the Cisco IOS for S/390 address space.
TSO ENVIRONMENT UNABLE TO SUPPORT PUTGET, GETPASS RC=rc Explanation A TSO command called the GETPASS subroutine to prompt for a non-display password. The PUTGET return code is given (rc). The return code determines the environmental problem experienced.
Recommended Action Usually this error occurs when the TSO command is invoked improperly.
These are some reasons the TSO environment may not support PUTGET:
VLTLOGWK pointer corrupted VLT logging turned off, LOGPTR=address Explanation Client program FTP or FTP2 was running utilizing VLT tracing. FTP discovered that the VLTLOGWK control block has been corrupted. VLT tracing stopped; FTP continues.
Recommended Action Save the output of the FTP job. Contact Customer Support.
ACB OPEN FAILED FOR VLT code1, ACB ERROR RC=code2 VLT RC=code3 R15=code4 R0=code5 Explanation The attempt to open a server TELNET session with a VTAM application failed to complete successfully. Register 15 and 0 values are options fields.
These are the possible error codes:
| code1 | VLT applid. |
| code2 | ACB error code. |
| code3 | VLT error code (in hexadecimal):
· 00 - Operation completed successfully · 01 - Normal with chained buffer · 02 - Buffer purged by another entry · 03 - I/O error in PUT operation · 04 - I/O error in GET operation · 05 - There are no applids left or passed applid is bad · 06 - Error in REQSESS request · 07 - Bad BIND image · 08 - Error in SIGNA · 09 - Error in SETLOGON · 0A - Error in OPENSEC · 0B - Error in RESET · 0C - Cannot OPEN ACB: Unknown reason · 0D - Cannot OPEN ACB: Network seems misdefined · 0E - Cannot OPEN ACB: Storage shortage · 0F - Cannot OPEN ACB: VTAM shutting down · 10 - Error in TERMSES · 11 - VQE queueing error · 12 - Contention resolution failed for GET · 14 - OPEN timeout error (2 minutes limit) · 17 - Data has been received for an LU0 device that exceeds the buffer. LU0 does not support RU chaining. Increase the BUFFERSIZE on the TERMPROF statement for the TERMTYPE. |
| code4 | Register 15 after OPEN request. |
| code5 | Register 0 after OPEN request. |
Recommended Action If the ACB error code is nonzero, read the IBM manual VTAM Reference Summary.
RPL ERROR: REQ=code1 R15=code2 R0=code3 RTNCD=code4 SENSE=code5 DEST=code6 VLT RC=code7 Explanation A VLT attempted an RPL based VTAM request but the request failed. Destination applid (code6), register 15 (code2), and 0 (code3) values are option fields.
| code1 | RPL request type. |
| code2 | Register 15 after RPL request. |
| code3 | Register 0 after RPL request. |
| code4 | RPL return code. |
| code5 | RPL sense. |
| code6 | Destination applid. |
| code7 | VLT return code (refer to VLT codes defined in message ACC406I). |
Recommended Action Verify that VTAM is functioning properly. Use the VTAM Reference Summary manual for an explanation of RPL codes.
VLT BIND ERROR: bind VLT RC=vlt Explanation A VTAM BIND was received but failed VLT's bind validity checking. The user session is terminated.
Recommended Action Verify that VTAM is functioning properly. Use the SNA Reference Summary manual for a description of a bind format. Refer to message T01F1071I for an explanation of VLT return codes.
VLT ERROR: VLT RC=vlt Explanation A VLT error was detected.
Recommended Action Verify that VTAM is functioning properly. Refer to message T01F1071I for an explanation of VLT return codes.
FTP RETURNS CC=rc Explanation FTP returns the specified return code (rc).
Programs FTP and FTP2 can terminate and set these return codes:
| 0 | FTP successful. |
| 8 | An error occurred in processing the FTP commands, or a remote host disconnected, or a file transfer failed. Check the SYSPUT data output for the problem. |
| 16 | A file allocation error occurred. Check that the SYSGET and SYSPUT files are in the batch JCL. Also, check to make sure that the FIOS option was entered in the invocation option parameters passed to FTP. When running FTP2 in batch, unless the NOA option is specified, a return code of 16 can be returned when there is no NETRC file. |
Recommended Action If the user is executing FTP or FTP2 in batch, the user must check the SYSPUT and take the appropriate action.
|
|