IBM Support

II06125: DOCUMENTING PROBLEMS OF NETVIEW FTP (NVFTP)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • Hints to provide all necessary and helpful information
    for analysis of a NVFTP VM & VSE V1 and MVS V2 problem:
    
    ----------------------------------------------------------------
    ----------------------------------------------------------------
    Try to copy and paste this picture with the specific information
    into the PMR:
    
     +-----------------------+             +-----------------------+
     | operating system      |             | operating system      |
     | operating system level|    .-------*| operating system level|
     | VTAM level            |     .       | VTAM level            |
     |                       |             |                       |
     | (NV)FTP release/level |      .      | (NV)FTP release/level |
     | LU name               |*------      | LU name               |
     |                       |             |                       |
     |                       |             |                       |
     | requestor             |             | responder             |
     |    or                 |             |    or                 |
     | responder             |             | requestor             |
     |                       |             |                       |
     | sender                |             | receiver              |
     |   or                  |             |   or                  |
     | receiver              |             | sender                |
     |                       |             |                       |
     | which user exits ?    |             | which user exits ?    |
     +-----------------------+             +-----------------------+
    
    NOTE: In the picture above, each box would represent one
          of the Netview FTP server's systems that is involved
          in the transfer. Note that the REQUESTOR is the
          initiator of the request (sometimes referred to as
          the Primary or the Local server). PLEASE use this
          new terminology for problem description and
          clarification.
    ------------------------------------------------------------
      The following is a list of information material,which
      is often missing in the PMRs sent to our Change Team.
      Please select the items, which fit to your problem and
      include in the PMR or send the material to one of the
      following locations:
    -----------------------------------------------------------
    >>>      VNET:   NFTPTEAM  at  ROMEPPC                  <<<
    >              the pmr no. should be part of the fileid   <
    >   or                                                    <
    >>>      FAX: (39) - 6 - 5966 - 2456                    <<<
    >              Please specify on the header page:         <
    >                    PMR Number and                       <
    >                    name of addressee                    <
    -----------------------------------------------------------
    >>>            ** FOR U.S. CUSTOMERS **                 <<<
    >                                                         <
    >  FAX: 1-919-254-3404                                    <
    >                                                         <
    >  Mailing Address:  IBM Corporation                      <
    >                    4205 South Miami Blvd.               <
    >                    bldg 503 / dept BZH                  <
    >                    R.T.P. NC  27709                     <
    > (include the level 2 contact name on envelope Please)   <
    >                                                         <
    >  VNET  Customers:  USIB183M at IBMMAIL                  <
    ------------------------------------------------------------
    >>>        DOCUMENTATION TO BE SENT IN ON TAPE          <<<
    >                                                         <
    >  Please supplY ALL tape documention on STANDARD LABEL   <
    >  3480 or 6250 tapes. Please supply the JCL and output   <
    >  of the copy job                                        <
    >  1. For MVS systems use IEBGENER                        <
    >  2. for VM systems use VMFPLC2                          <
    -----------------------------------------------------------
    >>>      ABEND or ERROR with QUEUE HANDLER              <<<
    >                                                         <
    > 1. The complete Queue Handler Log  (DVGLOG)             <
    > 2. System log (console log) at time of error            <
    > 3. SNAP dump produced by Queue Handler                  <
    >     (verify DVGSNAP dd card in startup JCL)             <
    > 4. System dump if applicable                            <
    >     (code a SYSMDUMP dd card to startup JCL)            <
    -----------------------------------------------------------
    >>>      ERROR in REQUEST QUEUE PROCESSING                <
    >                                                         <
    > 1. If the request is added by the batch interface:      <
    >   -the complete add request batch job with request parms<
    >   -the complete batch job output                        <
    > 2. If the request is added by the interactive interface:<
    >   -save the request added via ISPF panels with a name.  <
    >    To view all request parameters at once, select the   <
    >    View option from the SAVED REQUEST Panel (DVGMEORE)  <
    >    Print this panel for sending in via FAX              <
    > 3. Request Queue Dataset information if needed for      <
    >    specific error situation                             <
    > 4. Queue Handler Log (DVGLOG)                           <
    >---------------------------------------------------------<
    >>>           ERROR WITH PANEL FLOW OR INPUT            <<<
    >                                                         <
    > 1. Turn on PANELID to display panel names               <
    >    (from command line enter PANELID)                    <
    > 2. The screen print of the panel(s) in question         <
    >       with the specific input typing(s)                 <
    >---------------------------------------------------------<
    >>>             ABEND or ERROR in SERVER                <<<
    >                                                         <
    > 1. Complete Server log (DVGLOG)                         <
    > 2. System Log at time of error (console log)            <
    > 3. Server Initialization Parms and APPL definitions     <
    > 4. SNAP dump produced by Server if applicable           <
    >    (verify coding of DVGSNAP DD card in JCL)            <
    > 5. System Abend Dump - if applicable                    <
    >    (verify coding of SYSUDUMP or SYSMDUMP DD card)      <
    >                                                         <
    >    *** IF ERROR IS FILE OR REQUEST SPECIFIC ***         <
    >                                                         <
    > 6. DCB information of both sending/receiving files      <
    > 7. Output of Internal Trace (see Installation manual)   <
    >    -code server init parm TRC='-----H----'              <
    >---------------------------------------------------------<
    >>>           ERROR with USER EXIT ROUTINES             <<<
    >            (select items below that apply)              <
    >                                                         <
    > 1. Short description of User-Exit routine function      <
    > 2. Server internal trace(see installation manual)       <
    >   -code server init parm TRC='-------8--'               <
    > 3. Complete Server Log (DVGLOG)                         <
    > 4. Current request parms (see request Que processing    <
    >   -items above)                                         <
    > 5. SNAP Dump produced by Server (trace output will be   <
    >   -written here: verify DVGSNAP dd card in startup JCL) <
    >---------------------------------------------------------<
    >>>              VTAM RELATED ERRORS                    <<<
    >                                                         <
    > 1. VTAM Definitionns in eddect for both servers:        <
    >   -(APPL definitions and logmode table entries)         <
    > 2. DVGLOG of both Servers (complete context of error    <
    >   -msgs; i.e. DVG065i include ALL return codes)         <
    > 3. SYSTEM log at time of error (note any ISTxxxx msgs)  <
    >>>        *** file transmission errors ***             <<<
    > 4. VTAM Buffer Trace (i.e. for bind failures)           <
    > 5. Server internal trace may be requested: code the     <
    >   -server init parm TRC='----B-----'                    <
    >>>         *** Transmission Hang Condition ***         <<<
    > 6. Dump of the NVFTP Server Address Space by issuing    <
    >   -the MVS DUMP command (DO NOT CANCEL!!) with the      <
    >   -following SDATA options: NUC RGN PSA CSA LPA SUM TRT <
    >---------------------------------------------------------<
    *    For additional information and unique problems       *
    *    with resolutions see INFO APAR II03756               *
    *---------------------------------------------------------*
    For your information and your consideration to migrate to
    the newest release:
    
    Service discontinued       effective December 3, 1992:
       5668-932    FTP Vers. 2.2        for MVS and VSE
       5664-315    FTP Vers. 2.2        for VM
    Service Discontinued       effective August 31, 1994
       5665-487    NvFTP V1(base and AFF)   MVS
    Service Discontinued       effective June 30, 1995
       5685-108    NvFTP V2.1.0         for MVS
    ----------------------------------------------------------------
    

Local fix

Problem summary

Problem conclusion

  • KEYWORDS: 568510801 568404801 ftpinfo doc DOC
    

Temporary fix

Comments

  • 566893201   566431501   566548701   568510801   568404801
     573008201   568601301
    

APAR Information

  • APAR number

    II06125

  • 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

    1992-07-17

  • Closed date

    1992-09-18

  • Last modified date

    1995-08-12

  • 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:
13 December 2020