Ftp Error Code = 00012
Contents |
DATA IN UPPER CASE z/OS Subscribe You can track all active APARs for this component. APAR status Closed as user error. ftp error codes Error description FTP RETURN CODE 99000 is seen when reading in a
Mainframe Ftp Return Codes
NETRC file that has upper cased data and works fine when in MIXED or LOWER case. This problem only
Eza1735i
occurs when going to the name server and works fine when the IP address is used. Local fix Problem summary Problem conclusion Temporary fix Comments This APAR is being closed as a USER error. - - - The customer invoked an FTP batch job to run an EXEC that invokes FTP. The job contained a DD statement for a NETRC.DATA file. The NETRC.DATA file contained an entry for the host that FTP was to connect to. This entry in the NETRC.DATA file contained the userid and the password to be used for the FTP login. - - - The customer also provided the userid and password as input to FTP via the stack. - - - FTP used the NETRC.DATA information to log the user on. It then attempted to use the stacked userid as a command. This resulted in the "Unknown command: ..." message. Since the "(EXIT" parameter was specified, FTP then exited with a return code of 99000. - - - If the NETRC.DATA file is used to provide information for automated FTP operation, the data provided by the NETRC.DATA file can not be additionally provided via the stack or any other input stream that FTP might use. APAR Information APAR numberPQ02284 Reported component nameTCP/IP V3 MVS Reported component ID5655HAL00 Reported release310 StatusCLOSED USE PENoPE HIPERNoHIPER Special AttentionNoSpecatt Submitted date1997-03-12 Closed date1997-03-27 Last modified date1997-03-27 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Publications Referenced SC31713601 Fix information Applicable component levels Document information More support for: z/OS family Software version: 310 Operating system(s): z/OS Reference #: PQ02284 Modified d
CORRESPONDING EZA1735I MSG TO EXPLAIN THE FTP RETURN CODE. z/OS A fix is available Obtain the fix for this APAR. Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description Batch FTP with EXIT coded does not issue EZA1735I FTP Return Code message with the FTP return code when it detects that there is an UNKNOWN subcommand. The batch job exits with a condition code 696 without any indication of what the FTP return code is. The following is a sample batch job what would cause this condition. - normal login sequence. - some command such as get or put - QUOTE QUIT The above transfer completes http://www.ibm.com/support/docview.wss?uid=isg1PQ02284 successfully. But the QUOTE QUIT causes FTP to be in an UNKNOWN command state. So when the job finishes, the UNKNOWN command return code of 99000 is returned to the job as 696. But there is no trace entry that the FTP Return Code = 99000. . Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of MVS TCP/IP FTP client. * **************************************************************** * PROBLEM DESCRIPTION: QUOTE QUIT command passed in the batch * * job http://www.ibm.com/support/docview.wss?uid=isg1PN89012 does not produce EZA1735I msg when * * (EXIT is set. * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer submitted FTP job in batch mode. The client was invoked with (EXIT parameter and with the following JCL: normal login sequence PUT XX.YY AA.BB QUOTE QUIT When the job ran, the PUT and QUOTE QUIT command finished successfully. However, the customer noticed IEF142I message in the JES system log output with condition code of 0696, indicating something went wrong. When FTP client processed the QUOTE command, QUIT is passed to the server. When server receives the QUIT command, the connection is closed per the quit request. Then a reply is given back to the client, acknowledging that quit was processed. The Client then tried to process the next input but since there is none, QUIT command was generated due to unexpected EOF sequence. The QUIT command is sent to the server but server does not respond due to closed connection. Since client did not receive any reply back, connection is terminated via SysHalt. The above sequence is correct except before calling SysHalt, (EXIT flag needs to be checked and then issue EZA1735I if true. Problem conclusion GetChar in FTUTIL / EZABB01K is changed to check for ExitFlag and issue EZA1735I FTP Return Code = 99000. 99000 in this case is used as a catch all return code. Temporary fix Comments APAR
Sybase ASE Visual Expert for MS SQL Server Enable for http://appeon.novalys.net/appeon-powerbuilder-web-development-documentation/appeon-troubleshooting-guide/error00012.htm PowerBuilder Deploy PB apps on the web Other Solutions Impact Analysis Source Code Documentation Knowledge Transfer Code Exploration Code Review Authorizations Authentication Audit & Reporting Localization / Translation SQL Extraction Source Change from Runtime PB Code Protection Download a free trial Request a demo Price Request About Novalys About Appeon Corp Success ftp error Stories Troubleshooting Appeon Troubleshooting Guide Troubleshooting Appeon Install InstallShield errors Error 1607 or 1628 Error 1155 "DLL function call crashed" error when launching an Appeon Setup program Install Appeon Server EAServer cannot be started after Appeon Server install Cannot connect to EAServer Manager Install Appeon Server Web Component Third-party Web Server problems ftp error code with the Sybase redirector plug-in Upgrade installation "Upgrading AppeonDB failed" error "Bad interpreter: No such file or directory" error Uninstall issues "Failed to remove aprpmnt.dll" error Frequently Asked Questions Troubleshooting Appeon Developer Operating Appeon Developer toolbar "ADT is already running" error Exiting Appeon Developer completely after an error Windows XP SP2 critical update makes Appeon Developer not start Appeon Developer Configuration Testing connection fails during DB Type Profile configuration "Error launching LoadConfig" Feature Analysis "The XML page cannot be displayed" when opening a UFA report "Error loading ADTObjectList.xml" "Error loading command string" Feature analysis or deployment comes to a standstill "Fail to load PBTempl.xml" error "This application has requested the Runtime to terminate it in an unusual way" error, when you deploy or analyze an application "Error opening DLL Library adtxml.dll for external function" Error Appeon Debugger "Script Debugger Component Not Found" error "Component Not Registered" error "Script Debugger Disabled" error Troubleshooting Web De