APAR status
Closed as canceled.
Error description
This information apar provides instructions for gathering documentation for the FTP server and client. ================================================================ Documentation to collect ================================================================ D1. Description of problem D1.1 Identify if this an FTP client or FTP server related problem? D1.2 Always provide copy of any FTP client output since the FTP session was started. D1.3 If any error message is prefixed by 3 digits as in 550 Data set SYS1.TCPPARMS not found this is an error being reported by the FTP server. Provide documentation as documented for server problems. D1.4 Provide a copy of the FTP.DATA file for the failing applicaton (client or server). note: As an alternative, use following FTP commands form the FTP client QUOTE STAT ; for z/OS FTP server variables LOCSTAT ; if client is a z/OS Client for z/OS FTP client variables D1.5 Review console log around time of error and supply console output for any FTP messages D1.6 NOTE: Small text output can be emailed as follows: TO: TCPDOC@US.IBM.COM SUBJECT: pmrno,branch,country Update PMR on retain if you have emailed doc. D1.7 Provide a packet trace if - Problem being reported concerns a timeout - Problem being reported involves FTP commands being sent to a z/OS FTP server via a browser Note: Refer to information apar II12014 for instructions on obtaining a packet trace. ================================================================ Documentation for FTP server problems ================================================================ D2. USER abends (ie, U40xx) For user abends, check for an existing CEEDUMP on your system. Information on CEEDUMPs can be found in the Language Environment Programming Reference. If the Level2 support team decides the CEEDUMP is insufficient, an SVC dump trapping the original abend may be required. In this case, the following actions should be taken: (a) Code the following in the PARM specification of the FTPD cataloged procedure: TRAP(ON,NOSPIE) TERMTHDACT(UAIMM) (b) Set a SLIP to trap the original abend. Typically, the original abend code can be found in message IEF450I. If unable to determine abend code, contact level2 support. D3. FTP server traces D3.1 Server Trace output: The trace output will go to a file in the HFS as defined by the syslogd configuration file (/etc/syslog.conf). For additional information regarding syslogd, refer to informational apar II12021 NOTE: If syslogd is not configured for FTP on your system, the trace output will be written to the console. This is *NOT* recommended and can result in the console being flooded. Output that is sent to the console is also difficult to read and may delay problem diagnosis. Code the following statements in the Server's FTP.DATA file to allow FTP clients to selectively activate traces. Recycle the server to activate this support. DEBUGONSITE TRUE DEBUGONSITE TRUE D3.2 Common server trace options (a) SSL/TLS issues: SOC(3),SEC,CMD,FLO (b) logon issues: ACC,CMD,FLO (c) timeout issues: FLO,FSC(3),CMD (d) transfer issues: INT,FSC(3),UTL,FLO,SOC(3) (e) JES issues: JES,FLO,FSC(3) D3.3 Common server dump options (a) File Service Codes: FSC (b) Network Service Codes: SOC Data Connection: 52 Control Connection: 54 (c) JES issues: JES (d) SQL issues: SQL (e) Changing translate tables: 81 (f) User Exit: 82 and 87 (g) Socks: 84 and 85 D3.4 Using Modify commands to set trace/debug options (a) MODIFY ftp_server_jobname,DEBUG=(xxx) where xxx can be multiple server trace options as shown above. MODIFY ftp_server_jobname,DEBUG=(NONE) disables tracing MODIFY ftp_server_jobname,DEBUG=(?) displayes current trace settings (b) TRACE statement in FTP.DATA. Note: TRACE is equivalent to DEBUG BAS. (c) DEBUG statement in FTP.DATA. Note: A DEBUG statement must be coded for each debug option. D3.5 Using FTP Client to set trace/debug options in server (a) QUOTE SITE DEBUG=oooooooo QUOTE SITE DUMP=oooooooo where 00000000 is a single debug or dump option. Specify a separate SITE command for each. (b) QUOTE SITE DEBUG=? ; Lists server debug options QUOTE SITE DUMP=? ; Lists server dump options (c) QUOTE SITE DEBUG=NONE ; Turns off server debug QUOTE SITE DUMP=NONE ; Turns off server dump D3.6 Setting debug and dump options in the FTP.DATA file DEBUG 00000000 or DUMP 00000000 statement can be added to the FTP.DATA file. One option per statement. CAUTION: It is not recommended that this be done for the server as every client that FTP's into the mainframe will be traced. This is also true for the client. Every client using the FTP.DATA file will be traced. ================================================================ Documentation for FTP client problems ================================================================ D4. FTP client traces D4.1 Activating tracing when FTP is initiated (a) From TSO, FTP foreign_host (trace Note: trace is equivalent to DEBUG BAS. (b) From z/OS UNIX environment, one of the following: ftp foreign_host -d ftp foreigh_host / (trace Note: -d and trace are equivalent to DEBUG BAS. D4.2 Setting trace/debug options for the client note: All trace output goes to terminal when running interactive and to //SYSOUT DD statement when running in batch (a) Use TRACE (MVS) or-d (OMVS) when FTP is invoked (b) Activate trace with DEBUG command DEBUG oooooooo oooooooo oooooooo Activate dump with DUMP command DUMP 00000000 0000000 00000000 where: 0000000 is a valid debug or dump option (c) FTP subcommand (once in session): DEBUG xxx where xxx can be one of multiple client trace options as shown below. Note: A DEBUG statement must be coded for each debug option. (d) TRACE statement in FTP.DATA. Note: TRACE is equivalent to DEBUG BAS. (e) DEBUG statement in FTP.DATA. Note: A DEBUG statement must be coded for each debug option. D4.3 Common client trace options (a) SSL/TLS issues: SOC(3),SEC,CMD,FLO (b) logon issues: see D4.5 below (c) timeout issues: FLO,FSC(3),CMD (d) transfer issues: INT,FSC(3),UTL,FLO,SOC(3) (e) JES issues: INT,FSC(3),UTL,FLO,SOC(3) D4.4 Common Client dump options (a) File Service Codes: FSC (b) Network Service Codes: SOC Data Connection: 52 Control Connection: 54 (c) JES none for client (d) SQL issues: SQL (e) Changing translate tables: 81 (f) User Exit: 82 and 87 (g) Socks: 84 and 85 D4.5 Logon issues Add to FTP.DATA file for client following DEBUG ACC DEBUG CMD DEBUG FLO When running FTP in batch, this can be accomplised via jcl by concatenation to the //SYSFTPD DD statment pointing to the Clients FTP.DATA file. ex: //SYSFTPD DD DISP=SHR,DSN=SYS1.TCPPARMS(FTPDATA) // DD * DEBUG ACC DEBUG CMD DEBUG FLO /* ================================================================ Sending Documentation to IBM ================================================================ Reference the following technote (link) for sending documentatino to the z/OS level2 support team. http://www.ibm.com/support/docview.wss?rs=852&uid=swg21298465 ================================================================ To the customer: if you have suggestions to improve this informational APAR, please submit a problem record to TCPIP level 2 using component ID 5655HAL00. WE APPRECIATE YOUR SUGGESTIONS.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
infoapar
APAR Information
APAR number
II12925
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2001-06-28
Closed date
2002-11-07
Last modified date
2008-09-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
15 September 2008