How to send or receive documentation for AD Tools Products

Technote (FAQ)


Question

What are the instructions for sending or receiving documentation using FTP to IBM Level 2 Technical Support for Application Development products?

Cause

Instructions for uploading (putting files on the server) and downloading (getting files from the server) are shown below.

Answer

Files placed on the EMEA Centralized Customer Data Repository FTP server will be deleted after 7 business days.

Send additional problem details (i.e. screen prints or email from user) to the ecurep email repository at: techsupport@ecurep.ibm.com. You must add PMR xxxxx,bbb,ccc in the subject line of your email where xxxxx is your pmr number, bbb is your branch office and ccc is your IBM country code. Go to this link for more details.

*** See Special Instructions for PDSE ***


Putting files on the FTP Server

All datasets delivered electronically to IBM must be in a compressed format. MVS customers must first use the TRSMAIN program to compress their file [with the PACK parameter]. As of z/OS 1.9 TRSMAIN is shipped as AMATERSE.The TRSMAIN program and instructions can be obtained from this IBM web site:


When you create the tersed dataset, use of the following mandatory naming convention allows the support tools to move the documentation automatically to the proper directories and update the PMR to indicate that the file is available.

If the files cannot be associated with an existing PMR, they will be tagged as lost and eventually deleted.

Files must follow the following naming convention:


    xxxxx.bbb.ccc.yyy.TRS[.CRY | .CRY64]

Where:
    xxxxx PMR Number
    bbb Branch Office
    ccc IBM Country Code
    yyy A short description for the file (not limited to 3 chars)
    TRS Mandatory for a tersed file
    CRY Optional additional Identifier for non-DES encrypted file (FTPENCR module is used)
    CRY64 Optional additional Identifier for 64-bit DES encrypted file (FTPENCRD module is used)

Example
    34143.055.000.dump.TRS (for PMR 34143, branch 055, country 000)

  • Use the BINARY option for transfer.
  • Place tersed files on the toibm/mvs directory.

Some additional remarks:

To reduce reaction time, inform us about the transferred files. The material will be automatically deleted after 7 days. The FTP get and ls options are intentionally disabled.

Failure to use the file naming convention will delay resolution of the problem you are experiencing. If you need help understanding how to create a compressed terse archive, contact the support representative who is working on your problem.

Please read the ServiceUse Agreement Link. By submitting your testcase to IBM you are agreeing to comply with the "statement on confidentiality" within this agreement. If you do not agree, do not use this service.

After preparing and tersing the data, you should deliver the data to our ftp server. You may use any FTP process you like, however one recommended method is shown below in the examples.


PDSE Instructions

Unlike sequential files, you cannot terse PDSE's that include Program Objects with TRSMAIN. First, you must XMIT them into a FB, LRECL=80 format. While optional, we also recommend this for PDS’s.

Prior to tersing the file(s) use this syntax:


    XMIT X.Y DS( 'data.set(member)') OUTDSN( xmitname)

X.Y is a required placeholder for system.userid (but is ignored) and may be coded as-is (the letter X then a dot then the letter Y). The member name is optional. If omitted, the entire PDSE is used as input.

This will convert your PDSE into a sequential file. The output file, "xmitname" will be RECFM=FB, LRECL=80, BLKSIZE=3120. You can then terse your OUTDSN data set. We do the RECEIVE at our end after untersing the file.

Getting Files from the FTP Server

You can find file(s) we make available to you on our FTP Server in the following directory:


You may logon directly to the site ftp.emea.ibm.com from your MVS system and use 'anonymous' as the UserID and your email ID as the password. (e.g. UserID= anonymous, PW= your_email_ID@location). If receiving a tersed or xmitted file they were placed there in binary format so you must issue "type binary" prior to any get.

If the file was Tersed, specify the ftp command:

    locsite recfm=fb lrecl=1024 blksize=6144

If the file was XMITed (as with a PDSE), specify:
    locsite recfm=fb lrecl=80 blksize=3120
Then issue "get file.name 'your.received.dataset name' " to download the file to your MVS system. You can then use the RECEIVE command from TSO to put it back into it’s original format using:

    RECEIVE INDSN(‘ your.received.dataset.name’)

If you downloaded the packed version, uncompress your file. You should use the TRSMAIN program to uncompress your file(s) using the UNPACK parameter. You can get the TRSMAIN utility from our webpage at:

Examples: (Combine these jobsteps as needed. Fields specific to your location need to be changed)

XMIT a PDS or PDSE to a sequential file prior to TERSEing

//*_________________________________________________*/
//*
//* Transmit a library to a squential dataset
//* 'YOUR.LIBRARY is the PDS or PDSE you want to send
//*  X.Y is a required placeholder
//*_________________________________________________*/
//*
//TSOXMIT  EXEC
PGM=IKJEFT01,REGION=6144K,DYNAMNBR=999
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
 XMIT X.Y DSN('hlq.pds.to.be.xmitted') -
OUTDSN(TEMPXMIT)

/*

TERSE job to pack a dataset prior to FTPing to IBM:

//STEP EXEC PGM=TRSMAIN,PARM=SPACK
//SYSPRINT DD SYSOUT=*
//INFILE DD DISP=SHR,DSN=hlq.TEMPXMIT
//OUTFILE DD DISP=(NEW,CATLG),UNIT=SYSDA,
// SPACE=(CYL,(200,200),RLSE),
// DSN=hlq.tersed.file.name

MVS batch job to FTP files to IBM:

//FTP EXEC PGM=FTP,PARM='-v (EXIT '
//* Uncomment next line for Secure-FTP
//*FTP EXEC PGM=FTP,PARM='-a TLS -v (EXIT '
//SYSTCPD DD DSN=hlq.TCPPARMS(TCPDATA),DISP=SHR
//SYSFTPD DD DSN=hlq.TCPPARMS(FTPDATA),DISP=SHR
//SYSPRINT DD SYSOUT=*
//*   Please use 192.109.81.7 instead of
//*   ftp.emea.ibm.com if you have problems with
//*   IP name resolution

//INPUT DD *
ftp.emea.ibm.com
anonymous
your@email.address
bin
cd /toibm/mvs
put 'hlq.tersed.filename' ppppp.bbb.ccc.filedesc.TRS
quit
/*

Where:
ppppp is the PMR number
bbb is the branch number
ccc is the country code
filedesc is some kind of file description

FTP Command mode to FTP files to IBM:

1. Please compress your dataset using TRSMAIN which can be downloaded from:

2. Access server from a command prompt by entering:
      ftp ftp.emea.ibm.com
3. When prompted, your userid is anonymous, the password is your complete e-mail address.
4. Change to the correct directory by entering: cd /toibm/mvs
5. Change the FTP transfer type to binary by entering: type binary
6. Put the file on the FTP server with:
      put ’hlq.tersed.file.name’ ppppp.bbb.ccc.filedesc.TRS
7 End your session by entering: quit

MVS batch job to receive files from IBM

//*_________________________________________________*/
//*                                                
//* FTP from  ftp.emea.ibm.com                    
//* xxxxxxx@xxxxxxx is your email address          
//* and yyyy.yyy is the filename support provides  
//*_________________________________________________*/

//*
//* Please use 192.109.81.7 instead of

//*   ftp.emea.ibm.com if you have problems with
//*   IP name resolution

//*_________________________________________________*/
//*
//FTPSTEP  EXEC PGM=FTP,REGION=12288K,
//             PARM='ftp.emea.ibm.com (EXIT'
//SYSUDUMP DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//OUTPUT   DD  SYSOUT=*

//INPUT    DD  *
anonymous
xxxxxxx@xxxxxxxx
cd /fromibm/mvs
binary
locsite CY PRI=10 SEC=20 REC=FB LR=80 BLK=3120
get
yyyy.yyy            TEMPREC
quit
//*


Jobstep to unTERSE a file


//STEP     EXEC PGM=TRSMAIN,PARM=UNPACK
//SYSPRINT DD   SYSOUT=*
//INFILE   DD   DISP=SHR,DSN=
YOURHLQ.TEMPREC 
//OUTFILE  DD   DISP=(NEW,CATLG),UNIT=SYSDA,
//         SPACE=(CYL,(200,200,20),RLSE),

//         DSN=YOURHLQ.DOWNREC


Jobstep to RECEIVE an XMITted file
 //*_________________________________________________*/
//*                                                
//* RECEIVE file on your MVS system              
//* PDS will be under your high level qualifier    
//* with TEMP.LIBRARY as an extension              
//* <<CHANGE TEMPREC to TEMPREC2 if TERSED        
//*_________________________________________________*/

//*                                                
//TSOTMP   EXEC PGM=IKJEFT01,REGION=6144K,DYNAMNBR=999
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
RECEIVE INDSN(
DOWNREC)
DSN(
TEMP.LIBRARY)
/*

Jobstep to delete any temporary files created above

//*_________________________________________________*/
//*                                                
//* DELETE your TEMPREC datasets                  
//*_________________________________________________*/

//*                                                
//DEL1 EXEC PGM=IEFBR14,COND=(7,LT)
//TEMP1  DD DSN=
YOURHLQ.TEMPREC,             <<CHANGE
//       DISP=(MOD,DELETE),

//       SPACE=(CYL,(20,20),RLSE)
//TEMP2  DD DSN=
YOURHLQ.DOWNREC,             <<CHANGE
//       DISP=(MOD,DELETE),
//       SPACE=(CYL,(20,20),RLSE)

Reminder: Files placed on the FTP server will be deleted after 7 business days.


FTP is an acronym for File Transfer Protocol. FTP is a client-server TCP/IP application that allows for file transfers between different types of computers connected to computer networks. IBM employees and customers both use FTP client software to access the EMEA Centralized Customer Data Repository FTP server. FTP clients are available for nearly all computing platforms and have both command line and graphical user interfaces. Web browsers such as Netscape Navigator or Microsoft Internet Explorer can also display FTP directory listings and perform FTP file downloads.


Related information

IBM EMEA

Cross reference information
Segment Product Component Platform Version Edition
Software Development File Manager for z/OS Not Applicable OS/390, z/OS All Versions
Software Development DITTO Not Applicable VM/ESA, VSE/ESA, z/OS
Software Development Ad/Cycle C/370 Not Applicable MVS/ESA, OS/390, VM/ESA
Software Development Application Monitor for z/OS Not Applicable OS/390, z/OS
Software Development C for VM/ESA Not Applicable VM/ESA
Software Development COBOL and CICS/VS Command Level Conversion Aid Not Applicable VSE/ESA, z/OS, z/VM
Software Development COBOL for MVS & VM Not Applicable OS/390, VM/ESA, z/OS
Software Development COBOL for OS/390 & VM Not Applicable OS/390, VM/ESA, VSE/ESA, z/OS
Software Development COBOL for VSE/ESA Not Applicable VSE/ESA
Software Development Compiler and Library for REXX on zSeries Not Applicable MVS/ESA, OS/390, VM/ESA, z/OS
Software Development Debug Tool for z/OS Not Applicable OS/390, VM/ESA, z/OS
Software Development Enterprise COBOL for z/OS Not Applicable OS/390, z/OS
Software Development Enterprise PL/I for z/OS and OS/390 Not Applicable OS/390, z/OS
Software Development Fortran Not Applicable MVS/ESA, OS/390, VM, z/OS
Software Development High Level Assembler (HLASM) and Toolkit Feature Not Applicable OS/390, VSE/ESA, z/OS, z/VM
Software Development OS/390 C/C++ Not Applicable OS/390, z/OS
Software Development PL/I for MVS & VM Not Applicable MVS/ESA, OS/390, VM/ESA, z/OS
Software Development WebSphere Studio Asset Analyzer Not Applicable OS/390, z/OS
Software Development WebSphere Studio Workload Simulator for z/OS and OS/390 Not Applicable OS/390, z/OS
Software Development WebSphere Studio Workload Simulator for z/OS and OS/390 Not Applicable z/OS

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Fault Analyzer for z/OS

Software version:

10.1, 11.1, 12.1

Operating system(s):

z/OS

Reference #:

1154524

Modified date:

2005-12-02

Translate my page

Machine Translation

Content navigation