IBM Support

II12030: MUSTGATHER: INSTRUCTIONS FOR SENDING TCPIP DOCUMENTATION TCPIPINFO

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as canceled.

Error description

  • This information APAR describes the procedures for sending
    Documentation to the Communications Server IP level2 team.
    ****************************************************************
    *                                                              *
    *   Information in this APAR is no longer being updated.       *
    *   Please use the following URL for the latest set of         *
    *   directions:                                                *
    *                                                              *
    * http://www.ibm.com/support/docview.wss?rs=852&uid=swg21298465
    *                                                              *
    ****************************************************************
     ********************************
     * SENDING DOCUMENTATION       *
     *********************************
    There are various ways to send documentation to the
    Communications Server Level2 support team.
    Please see below for additional information.
    NOTE: Please update the PMR when DOC for a particular problem
          has been sent. Also it is helpful to note the method used
          to send the doc (FTP, mail, or email).
    =========================================================
    1.   FTP: USING FTP TO SEND DOCUMENTATION
     Please note: It is recommended that the PUTDOC utility be used
     for the placement of docs on the server.  The latest version
     can be obtained via the following URL (one line):
        http://techsupport.services.ibm.com/server/nav/zSeries/
             putdoc/putdoc.html
     Version 3 (available after September, 2003) supports the
     specification of TO(EMEA), which is the prefered location.
    
     If not using the PUTDOC tool, the following procedure should be
     followed.  The TRSMAIN utility should or must be used
     depending on the type of doc:
     (a) Dumps should be tersed using the TRSMAIN
         utility before placing on the server;
     (b) Non-text RECFM V or U datasets MUST be tersed using the
         TRSMAIN utility before placing on the server.  Examples
         include : ctraces, packet traces, CCW traces, and  GTF
         traces.
         NOTE :  To avoid potential file corruption due to loss of
                 record structure,  it is recommended that datasets
                 are packed using the TRSMAIN utility on the
                 originating system/LPAR before using FTP to send
                 the dataset.
     (c) PC files (especially network traces, such as Sniffer
         traces) should be placed into a ZIP file.
     ** Please refer to the following URL for TRSMAIN: **
        http://techsupport.services.ibm.com/390/trsmain.html
    .
    The ECuRep (IBM EMEA Centralized Customer Data Repository)
    can be reached via several ways :
    - IBM CUSTOMERS should use an FTP Client Software Program to
      place data onto our FTP Server, which can be reached by :
        TCP/IP name    :   ftp.emea.ibm.com
        TCP/IP address :   192.109.81.7
    .
    Use the following instructions to transfer your data to our ftp
    server from the TSO command line.
    Note: The instructions below do not include steps which may be
    necessary to pass through a firewall or proxy server.
    .
    From the TSO READY: prompt enter: ftp ftp.emea.ibm.com
    At the USER: prompt, enter: anonymous
    At the password prompt, enter: your_email_address
    (i.e. your_user_id@company.com)
    At the Command: prompt, enter: cd toibm/mvs
    At the Command: prompt, enter: bin
    At the Command: prompt, enter:
    put trsmain.bin YOUR.LOCAL.DSN [file naming convention]
    At the Command: prompt, enter: quit
    .
      Using a BROWSER is possible, but NOT recommended.
      When you type the URL, you must type :
        ftp://ftp.emea.ibm.com       (NOT http://)
          or
        ftp://192.109.81.7           (NOT http://)
      Be aware that some browsers may automatically issue a
      LIST-command when changing a working directory.
      However, in some subdirectories, this is NOT allowed and
      you may experience error messages (like "Permission Denied")
       ==>  PLEASE ADHERE TO THE FILE NAMING CONVENTIONS
       ==>  MENTIONED BELOW ||
    ================================================================
       IMPORTANT : Naming conventions for files :
    Using the following naming convention will allow the supporting
    tools to move the data from the DFS server to MCEVS1 :
    xxxxx.bbb.ccc.yyy.optional_qualifiers
    xxxxx    PMR-Number
    bbb      Branch Office (if known)
    ccc      Numeric Country code (ie; 000 for USA, 706 for France)
    yyy      Short description for the file
    Optional and additional Qualifiers are :
    .TRS     Data is tersed
    .CRY     Data is crypted
    .CRY64   Data is crypted with 64bitDES
    In case the sent data are not in TERSED format, the
    correct and complete DCB-Parameters (RECFM,LRECL
    and BLKSIZE) have to be supplied
       For filenames, only use the following characters :
        - Uppercase or lowercase A-Z
        - Numbers 0-9
        - Period (.)
        - Underscore (_)
        - Hyphen (-)
       Using other characters may lead to unpredictable results,
       your file may NOT be processed.
    ================================================================
    This FTP Server is available for sending documentatio and
    diagnostic information (associated to PMRs) to IBM.
    Before delivering documentation via the Internet, you must be
    instructed to do so by the support representative who is working
    on your problem.
    For further details please see :
    ==>   https://www.ibm.com/support/pages/node/739283
    By using this service you agree to all terms of the Service Use
    Agreements, which can be found on the web :
    ==>   www.ibm.com/de/support/ecurep/service.html
    ****************************************************************
    MAIL: USING PHYSICAL MEDIA TO MAIL DOCUMENTATION
       MAILING ADDRESS FOR DOCUMENTATION
       z/OS Communication Server Change Team - Lvl2
       IBM -   CWCA/B501/N323
       3039 Cornwallis Rd.
       Research Triangle Park, NC 27709-2195
       Note: Please include PMR number, Branch, and Office with
             any mailed material. Also, include Level2 Rep's name
    =========================================================
       EMAIL: EMAILING DOCUMENTATION
       Use the following email address: TCPDOC@US.IBM.COM
       Guidelines for emailing doc to TCPDOC:
       (a) Specify the PMR number on the subject line
       (b) do NOT email SVC dumps
       (c) Size limit for attachments is approximately 10M,
           however the sender's email system may be even
           more restrictive (smaller).
           - For larger files, consider ziping the source
             and email zip file.
       (d) After doc has been sent, update pmr with an
           indication that documentation has been sent.
    

Local fix

  • COMMENTS: informational purpose only
    
    Other Keywords:
    
    R50A R120 R140 R150 R160 R170 R180 R190 z/OS
    

Problem summary

  • 
    

Problem conclusion

  • 
    

Temporary fix

  • 
    

Comments

  • informational purpose only
    

APAR Information

  • APAR number

    II12030

  • 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

    1999-08-24

  • Closed date

    1999-12-09

  • Last modified date

    2008-09-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:
28 June 2021