II13072: OD390 SUPPORT FTP INSTRUCTIONS

APAR status

• INTRAN

Error description

• Content Management OnDemand for OS/390 5655A8800 ftp TESTCASE
  
  INSTRUCTIONS for using the TESTCASE ftp site for transmitting
  documentation to AND receiving files from OD390 Support
  
    ******************************************************
    ***  Section 0 - Introduction                      ***
    ******************************************************
    OD390 Support is providing these instructions for use by our
    customers.
    Specific naming conventions are provided to ensure that the
    filename contains enough information to identify the
    nature of the file contents, as well as the PMR/ETR or the
    program testfix code/PTF/APAR that the file is associated
    with.
    It is important that you read and follow the instructions.
  
    This Informational APAR contains the following sections:
    1. How to Receive a file from TESTCASE
    2. How to Send a file to TESTCASE
       A. How to verify site access
       B. How to FTP files
       C. TRSMAIN - Also see DB2 Informational APAR II12154
       D. Naming conventions
    3. Notes
    4. IBM ftp example in Batch JCL
  
    ******************************************************
    ***  Section 1 - Receiving a file from FTP         ***
    ******************************************************
    IBM OD390 Support may place onto its FTP site files that
    contain executable code, documentation, or examples that are
    made available for customer download.
    Such files should not be downloaded without the express
    recommendation of OD390 Support.
    The files will be placed in a specific directory.
    The following are general directions to reach the ftp site.
    Your procedure may vary based on your installation's
    standards.
    An example of how to use ftp in batch with JCL is given at
    the end of this APAR.
  
     Example from TSO ready prompt:
  
     1. Type: FTP TESTCASE.BOULDER.IBM.COM
  
     2. (You will be prompted for the following information:)
  
        NAME:     (enter 'anonymous' in *lower case*)
        PASSWORD: (supply your complete e-mail address)
  
     3. You should now be connected to the FTP site, and you
        can start entering ftp commands. Ftp commands are case
        sensitive
  
     4. Type: cd /software/fromibm/eas
  
     5. Change to the subdirectory created for you.
        This information is sent to you by OD390 Support.
        Type: cd __________
  
     6. List the contents of your subdirectory.
        Type: dir
  
     7. If there is a README.TXT file in your subdirectory,
        get the README.TXT file by entering the following:
        - Type: ascii
        - Type: get README.TXT 'hlq.mlq.README.TXT'
          ('userid' should be your TSO user ID.)
        - Type: quit
        - Return to ISPF and browse 'hlq.mlq.README.TXT' before
          you continue to step 8.
  
     8. Change to the transfer mode that matches the file type.
        If the file on the ftp site that you will be downloading
        has an extension of '.TRS' or 'XMIT'
        Type: binary
  
     9. Allocate your target OS/390 dataset.
        If the file on the ftp site that you will be downloading
        has an extension of '.TRS'
        Type: locsite TR PRI=60 SEC=60 REC=FB LR=1024 BLK=4096
  
        If the file on the ftp site that you will be downloading
        has an extension of '.XMIT'
        Type: locsite TR PRI=60 SEC=60 REC=FB LR=80 BLK=4000
  
    10. Get the file.
        The file name is sent to you by OD390 Support
  
        Type: get ________.________.TRS
  
                          or
        Type: get ________.________.XMIT
  
         You will get the file to the dataset allocated in
         step 9 and you should see that the transfer was
         completed.
  
         If the file extension was ".TRS", then the dataset
         you transferred the file to is used as input to
         TRSMAIN via the INFILE DD.
  
         If the file extension was ".XMIT", then the dataset
         you transferred the file to is used as input to
         TSO RECEIVE, e.g.:
            "TSO RECEIVE INDSN('whatever.itis.XMIT')"
  
     11. Type: quit
  
    ******************************************************
    ***  Section 2 - Sending a file to TESTCASE        ***
    ******************************************************
    THE FTP SITE IS CaSe sEnSiTiVe.
  
    If you are capturing an 0C4, please send a SYSMDUMP.
    Please issue the following MVS console command first:
    'CD SET,SYSMDUMP=(ALL),ADD'
  
    If you are capturing a SYSMDUMP for us, it must go to a
    dataset, not SYSOUT. The dataset must be FB, LRECL=4160.
  
    Before you transfer a dataset to the ftp site from an OS/390
    system, you must first prepare it for transfer.
    We require that you pack your file first, with TRSMAIN.
    (Also see DB2 Informational APAR II12154.)
    This will ensure that your data is encapsulated and will
    restore to the correct format on our test systems.
    We also require that you ftp your file to the filename and
    directory location requested by OD390 Support.
    If the files that are sent do not conform to our standards,
    we may require you to resend your documentation.
  
    ******************************************************
    ***  Section 2.A - How to verify access            ***
    ******************************************************
    First, verify that your site can initially connect to the
    TESTCASE server.  You can try using the PING command to
    verify that the TESTCASE host server is available to you.
  
    Enter: PING TESTCASE.BOULDER.IBM.COM
  
    If you receive a response back from the PING command you
    now have the ability to connect to the server.
    You may have firewall restrictions at you installation that
    prevent access to foreign hosts. If Necessary, see your
    Network Systems Administrator for the necessary authority
    to get around this.
  
    ******************************************************
    ***  Section 2.B - How to FTP your files           ***
    ******************************************************
    The following are general directions to reach the ftp site.
    Your procedure may vary based on your installation's
    standards.
    An example of how to use ftp in batch with JCL is given at
    the end of this APAR.
  
     Example from TSO ready prompt:
  
     1. Type: FTP TESTCASE.BOULDER.IBM.COM
  
     2. (You will be prompted for the following information:)
  
        NAME:     (enter 'anonymous' in *lower case*)
        PASSWORD: (supply your complete e-mail address)
  
     3. You should now be connected to the FTP site, and you
        can start entering ftp commands. Ftp commands are case
        sensitive
  
     4. Type: cd /software/toibm/eas
  
        NOTE: The /software/toibm/eas is the only directory that
        you will be permitted to use for transferring files to
        OD390 Support.  If you put your files to a different
        directory, you may be required to FTP them to
        /software/toibm/eas.
  
        At this point you are connected to the IBM FTP site,
        within the proper directory.
  
     5. Change to the transfer mode that matches the file type.
  
        Type: binary
  
     6. Put your file to the name requested by OD390 Support.
  
        Generally, we ask for this filename format:
  
              PMR99999.meaningful.TRS
        (See section '2.D - Naming Conventions').
  
        We request that you use upper case in your file names.
  
        Type:  put 'MVS.HOST.FILENAME' PMR99999.meaningful.TRS
  
        You will put the dataset to the file we requested,
        and you should see that the transfer was completed.
  
      7. Type: quit
  
    ******************************************************
    ***  Section 2.C - TRSMAIN (AKA 'TERSE')           ***
    ******************************************************
       Please reference DB2 Informational APAR II12154.
       Contact OD390 Support if you need additional information.
  
    ******************************************************
    *** Section 2.D -  Naming Conventions -            ***
    ***                Customer Files                  ***
    ******************************************************
   All filenames MUST be upper case.  <---- NOTE
  
   The general format:  PMRnnnnn.xxxxxxxz.TRS
  
      'nnnnn' is the PMR number for the problem that you opened.
      'z'     is a number from 1 to 9
  
      xxxxxxxz problem identifier:
  
         Valid identifiers:
           1) JOBLOG   - JES JOBLOG, SYSMSG, etc.
           2) SPUFI    - Output of SPUFI or QMF query
           3) CWBOLOG  - CWBOLOG from CICS region
           4) CICS     - CICS region output or CICS Transaction
                         DUMP
           5) MSGUSR   - MSGUSR log from CICS region
           6) RPTDATA  - Line data report input to IODBSTOR
           7) AFPDATA  - AFP Data input to IODBSTOR
           8) AFPRES   - AFP resource file input to IODBSTOR
           9) ACT      - ACT/AFT definitions
          10) SVCDUMP  - required for all SVC DUMPs
          11) SADMP    - required for any unformatted DUMPs
          12) UFDMP    - required for all SYSMDUMPs, SYSABENDs
                         and SYSUDUMPs
          13) OTHER    - requires that the customer send a
                         description to OD390 Support describing
                         the file contents.
  
     Example of a valid file name:  PMR12334.JOBLOG1.TRS
  
    ******************************************************
    ***  Section 3  - Notes                            ***
    ******************************************************
   1. It is important that you notify OD390 Support when you
      sent a file to the ftp site
   2. Data stays on the ftp site for 3-5 days. We have no
      control over this.
   3. IT IS IMPORTANT THAT YOU UNDERSTAND THAT THE FTP SITE IS:
      ************* CASE SENSITIVE *************
      MVS dataset names must be in upper case.
      ftp commands must generally be lower case.
   4. If you have trouble logging in to the site due to
      'too many users currently logged on', please try again in
      fifteen minutes.
  
    ******************************************************
    ***  Section 4  - Batch JCL Example                ***
    ******************************************************
    The following Batch JCL example is taken from our labs
    It is presented as an example, only.
    You TCP/IP control dataset names will be unique to your
    installation.
  //FTPTEST  JOB (ACCT#),,NOTIFY=&SYSUID,
  //            CLASS=A,MSGCLASS=H
  //PUTTIT   EXEC PGM=FTP,REGION=0M,PARM='(exit'
  //*************************************************************
  //* ISPF EDIT THIS DATASET WITH NUM OFF,CAPS OFF              *
  //* YOU DO NOT WANT NUMBERS IN COLUMNS 73-80 ON STREAM INPUT! *
  //*                                                           *
  //* NOTE: This JCL is an example. Your mileage may vary.      *
  //*************************************************************
  //SYSPRINT DD  SYSOUT=*
  //OUTPUT   DD  SYSOUT=*
  //SYSFTPD  DD  DSN=hlq.TCPIP.CONFIG(R1FTP),DISP=SHR
  //SYSTCPD  DD  DSN=hlq.TCPIP.CONFIG(R1DATA),DISP=SHR
  //INPUT    DD *
  testcase.boulder.ibm.com
  user anonymous
  myid@anywhere.com
  LPWD
  cd software/fromibm/eas
  PWD
  dir
  locsite TR PRI=60 SEC=60 REC=FB LR=1024 BLK=4096
  get PMR12345.DBRMLIB.TRS 'OD390.PMR12345.DBRMLIB.TRS'
  dir
  quit
  /*
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• 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