Sending Files to Communications Server Support
How do I send documentation to the z/OS Communications Server (TCP/IP, VTAM) or ISPF level 2 team?
FTP: USING FTP TO SEND DOCUMENTATION
An FTP Server is available for sending documentation and diagnostic information (associated with a PMR) to IBM. Before delivering documentation using the Internet, you must be instructed to do so by the support representative who is working on your problem. You will need the PMR number and other necessary information which your support representative will discuss with you.
The Problem Documentation Upload Utility or PUTDOC Utility may be used when sending data directly from a z/OS system. The FTP command may be used when sending data from any platform. Use of the Secure Diagnostic Data Upload Utility (SDDUU) is not recommended for z/OS data sets, but may be used for relevant data from other platforms.
Using the Problem Documentation Upload Utility (MTFTPS)
- Uppercase or lower-case A-Z
- Numbers 0-9
- Period (.)
- Underscore (_)
- Hyphen (-)
This utility provides an alternative interface to FTP that integrates the TERSE function and (optional) file encryption. But the main benefit is for larger files (such as Stand-Alone Dumps) in that it will break up the original file into multiple pieces that are processed in parallel. This can result in a significantly reduced elapsed time when transferring data to z/OS support, which may be an important consideration when dealing with critical outages.
If the system is running z/OS 1.13, see the MVS Diagnosis: Tools and Service Aids manual for directions on how to use this utility. For earlier releases, see the IBM z/OS Problem Documentation Upload Utility page for directions to install and use this utility.
Using the PUTDOC Utility
The PUTDOC utility may be used for the placement of documentation on the server. The latest version can be obtained using the
z/OS Support and Downloads site. Select
PUTDOC under the Tools and Utilities column. The minimum level recommended is version 3, which was available September, 2003; the most recent version is 5.21 from April, 2008. Please specify TO(EMEA), which is the preferred location.
If not using the PUTDOC or MTFTPS tool, the following procedure should be followed.
Preparing the files
We strongly recommend that all files originating from a z/OS system be tersed, regardless of size. Not only does this reduce the amount of network traffic, it also ensures that the structure inherent in the original files is not lost during transmission. Non-text RECFM V or U data sets
MUST be tersed 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 data sets be tersed on the originating system/LPAR before any transfers to other systems.
For z/OS 1.9 and above (plus 1.7 and 1.8 with the PTF for OA19194 applied), use the AMATERSE service aid to terse the files. For earlier systems, the TRSMAIN utility available by way of the z/OS Support and Downloads site should be used.
Files from other platforms (such as network analyzer (Sniffer) traces, network diagrams and spreadsheets) should be placed in a ZIP file before uploading.
ECuRep (IBM EMEA Centralized Customer Data Repository) is the preferred FTP server to be used. Files placed on this server must use the following format for the target file name. Not using the complete PMR identification in the file name will cause delays in processing.
|bbb||PMR branch number|
|ccc||PMR country number. For example; 000 for United States of America, 706 for France, ... Do not use a country abbreviation for this field.|
|yyy||Short description for the file (can be multiple qualifiers)|
|type||TRS||File is tersed|
|CRY||File is tersed and encrypted1|
|CRY64||File is tersed and encrypted with 64bitDES1|
|ZIP||File is zipped|
|other||Use an appropriate name. Supply the original data set attributes in the PMR.|
|(1)||Files encrypted with the eGarda encryption tool (FTPENCR or FTPENCRD) are still accepted but are not recommended. Use Secure FTP (FTP/TLS or SFTP) or the encryption option of the Problem Documentation Upload Utility instead.|
For example: A dump collected for PMR 12345,49R,000 could be uploaded using the name
For file names, only use the following characters:
The server name ftp.ecurep.ibm.com should be used if possible. If external DNS services are not available on your system, the IP address 126.96.36.199 can be used; but note that this address is subject to change without notice.
Files from the z/OS system should be placed in the
/toibm/mvsdirectory. Files from a workstation (such as a zipped sniffer trace) should be placed in the
/toibm/windowsdirectory. All files (with the exception of simple readable text) should use the BINARY transfer mode. An example session run while logged into TSO is included at the end of this page.
NOTE: All directory names must be in lower case. Using an upper case name will cause the transfer to fail with a
550 xxxx: No such file or directoryerror. If using the ISPF Editor to prepare a batch job for the transfer, enter
CAPS OFFon the command line.
FTP from a workstation would use a similar procedure. Alternatively, use any of a number of available GUI clients. Note that many such clients (and web browsers) attempt to list directory content, which will result in an error condition (such as
450 : Permission denied) since anonymous users are not allowed to list the directory's content..
The following is a sample set of JCL to terse and FTP a CTRACE data set in a single job.
//TERSE EXEC PGM= AMATERSE ,PARM=SPACK,REGION=0M
//* For releases using the downloaded TERSE program:
//*TERSE EXEC PGM=TRSMAIN,PARM=SPACK,REGION=0M
//SYSPRINT DD SYSOUT=*
//INFILE DD DISP=SHR,DCB=(BUFNO=15),
//OUTFILE DD DISP=(NEW,PASS),UNIT=SYSDA,DSN=&&TERSED,
//STEP01 EXEC PGM=FTP,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//OUTPUT DD SYSOUT=*
//MYDATA DD DSN=&&TERSED,DISP=(OLD,DELETE)
//INPUT DD *
ftp.ecurep.ibm.com (timeout 720 exit=12
PUT //DD:MYDATA 12345.49R.000.TCPIP.TRACE.TRS
Send email messages, including attachments, to
email@example.com. Be sure to do the following:
- Specify the full PMR number (xxxxx,bbb,ccc) at the start of the subject line
- Do NOT email SVC dumps
- Size limit for attachments is approximately 10M, however your email system may be even more restrictive (smaller). For larger files, consider zipping the original file and attaching the resultant .zip file. If it is still too large, you must use one of the FTP methods described above.
Alternatively, the firstname.lastname@example.org address may be used. If you chose this option, be sure to update the PMR with an indication that documentation has been sent. Failure to do so may delay processing.
To mail tapes, CDs, or hardcopy listings, obtain the support name and room number from your Level 2 representative and use the following address.
z/OS Communication Server Change Team - Lvl2
Attn: support name PMR: xxxxx,bbb,ccc
IBM - CWCA/B501/room
3039 Cornwallis Rd.
Research Triangle Park, NC 27709-2195
Menu Utilities Compilers Options Status Help
ISPF Primary Option Menu
Option ===> tso ftp ftp.ecurep.ibm.com
0 Settings Terminal and user parameters User ID . : KOHRING
1 View Display source data or listings Time. . . : 12:59
EZY2640I Using 'SYS1.TCPPARMS(FTPDATA)' for local site configuration parameters.
EZA1450I IBM FTP CS V1R7
EZA1554I Connecting to: ftp.ecurep.ibm.com port: 21.
220-FTPD1 IBM FTP CS V1R7 at MCEFTP.ecurep.ibm.com, 18:03:04 on 2008-03-20.
220-Welcome to the IBM Centralized Customer Data Repository (ECuRep)
220-By using this service, you agree to all terms of the
220-Service User Licence Agreement
220-For FAQ/Documentation please see ECuRep - Homepage
220- LOGIN user: anonymous pw: your_email_address
220-please report questions to: email@example.com
220 Connection will close if idle for more than 30 minutes.
EZA1459I NAME (ftp.ecurep.ibm.com:KOHRING):
EZA1701I >>> USER anonymous
331 Send email address as password please.
EZA1701I >>> PASS
230-Here you can deliver/get support material to/from IBM.
230- deliver use command 'cd toibm'
230- get use command 'cd fromibm'
230- for CADCAM/CATIA/VPM/ENOVIA/SMARTEAM use command 'cd cadcam'
230-Please use command 'bin' prior transfer. See special instructions
230-displayed when changing to the sub directory.
230 'ANONYMOUS' logged on. Working directory is "/".
EZA1701I >>> CWD toibm/mvs
250 HFS directory /toibm/mvs is the current working directory.
EZA1701I >>> TYPE I
200 Representation type is Image
EZA1611I Usage of SITE command with PUT is OFF
PUT 'my.full.tersed.dataset.name' 12345.49R.000.TCPIP.DUMP.TRS
EZA1701I >>> PASV
227 Entering Passive Mode (192,109,81,7,254,231)
EZA1701I >>> STOR 12345.49R.000.TCPIP.DUMP.TRS
125 Storing data set /toibm/mvs/12345.49R.000.TCPIP.DUMP.TRS
250 Transfer completed successfully.
EZA1617I 9216 bytes transferred in 0.005 seconds. Transfer rate 1696.00 Kbytes/sec.
EZA1701I >>> QUIT
221 Quit command received. Goodbye.
NOTE: The information presented in this documentation was previously maintained as Information APAR II12030.
|Software Development||Application Time Facility for z/OS||Not Applicable||zSeries||2.8.6, 2.8.7|
More support for:
z/OS Communications Server
Software version: 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, 1.13, 2.1, 2.2, 2.10
Operating system(s): z/OS
Reference #: 1298465
Modified date: 28 December 2010