IBM Support

II14108: HOW TO SEND CUSTOMER DOCUMENTATION FOR TDS FOR Z/OS PMRS TO ECUREP FTP SITE (COMPID 569510100)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • Documentation may be sent via FTP or EMAIL.  FTP is preferred.
    The FTP site is ftp.emea.ibm.com.
    Use the following instructions to send documentation to the
    FTP site:
    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
       (This tells the system to do all transfers in BINARY mode,
       and is necessary to correctly process TERSED, TAR, or ZIP
       files).
    put yourfile.bin YOUR.FTPSITE.DSN
    At the Command: prompt, enter: quit
    .
    .
    where yourfile.bin is the file that you wish to send and
    YOUR.FTPSITE.DSN must follow following naming conventions:
    .
    xxxxx.bbb.ccc.yyy.yyy.EEE
    Field  Explanation     Sample
    xxxxx  PMR Number       00111
    bbb    Branch Office    L6Q
    ccc    IBM Country Code 000
    
    .
     yyy.yyy A short description for the file type dump
    .
     EEE file extension -
         should be TRS if file is TERSED with TRSMAIN
         should be TAR if file is from tar or pax backup
         should be ZIP for a ZIP file
    
    .
    NOTE:  The automatic process will attempt to unterse all
           files regardless of the file extension.  All files
           should be tersed except for TAR or ZIP files.
           For any file sent untersed, the PMR will be updated
           with this message:
          Your Action is required: Untersing problems with file:
    
    
           The same mesage will be issued if there are actual
           problems untersing a file (for example if the tersed
           file was sent in ASCII mode instead of BINARY mode
    
    .
    The PMR will automatically be updated when the file(s) is
    received on the FTP site.
    Email documentation may be sent as attachments to:
    mvs_support@mainz.ibm.com
    The SUBJECT field of the email must be the PMR number (i.e.
    PMR<pmr>,<branch>,<country>
    For example, if your PMR number is:
    00123 , branch office is GWA, country code is 001
    Use following subject for your mail:
    PMR00123,GWA,001
    or
    PMR 00123 GWA 001
    If tersed files are sent they will be automatically
    untersed and stored (as is also done for the FTP site).
    The PMR will be updated and a call generated to alert
    support that the email has been received.
    You will also receive a REPLY EMAIL from
    no_reply@mainz.ibm.com  which will tell you
    if the email was received OK or if there were
    any problems.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • Closing for customer view
    

APAR Information

  • APAR number

    II14108

  • 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

    2005-11-04

  • Closed date

    2006-08-04

  • Last modified date

    2014-04-04

  • 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:
04 April 2014