APAR status
INTRAN
Error description
Updated: 09/29/2006 Siva Sreeraman & Tsegai Tecleab newupdt: 11/30/2006 newupdt: 02/26/2010 Tsegai Tecleab newupdt: 06/06/2011 Tim McAllister --------------------------------------------------------------- The preferred method for sending in documentation for DB2 for z/OS is via the IBM z/OS Problem Documentation Upload Utility. See Info APAR II11945 for additional information. --------------------------------------------------------------- There are several methods that customer's can FTP diagnostic file for DB2 z/OS and related products to IBM. Here the are couple of options. >>>>>>>>>>>>>>>>>>>> OPTION I <<<<<<<<<<<<<<<<<<<<<<< ****************************************************** *** Section 0 - Introduction *** ****************************************************** ATTENTION: THE FTP SERVER IS CASE SENSITIVE STARTING SEPTEMBER 29th 2006, DIRECTORY CHANGES AND FILE NAMING CONVENTION CHANGES HAVE BEEN MADE TO THE TESTCASE SERVER. PLEASE FOLLOW THE INSTRUCTIONS BELOW CAREFULLY. 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 FTP files B. TERSE - techsupport.services.ibm.com/390/trsmain.html C. Naming Conventions for New Directory 3. Common Mistakes ****************************************************** *** Section 1 - Receiving a file from FTP *** ****************************************************** IBM DB2 will put UserMods and APAR Fixes onto an FTP Site for download by customers. The information needed to download these UserMods and APAR Fixes follows: FTP Site = testcase.software.ibm.com Directory = /fromibm/im FileName = This will be fix specific Mode = binary From TSO ready mode: Type: ftp testcase.software.ibm.com - you will be prompted for the following information NAME: anonymous /* lower case */ PASSWORD: ENTER complete e-mail address - you should now be connected to the FTP site /* case sensitive to directory */ Type: cd /fromibm/im /* change to binary mode */ Type: binary Type: locsite CY PRI=10 SEC=10 REC=FB LR=80 BLK=32720 Type: get hdbNN10.aqxxxxx.aparfix (NN=66,77, 88 etc) You should see that the transfer was completed. /* exit FTP: Site dependent. see your help */ Type: quit ****************************************************** *** Section 2 - Sending a file to TESTCASE *** ****************************************************** ATTENTION: THE FTP SERVER IS CASE SENSITIVE. It is recommended that every file be TERSED prior to it being FTP'ed to the IBM FTP Site. The TERSE'ing of files and sending them in 'binary' mode is to reduce transmission and download errors, not simply to reduce the number of bytes being transmitted. Even small files should be TERSED. See Section 2.B for TERSE instructions. ****************************************************** *** Section 2.A - How to FTP your files *** ****************************************************** 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.software.ibm.com If you receive a response back from the PING command you now have the ability to connect to the server. Enter: ftp testcase.software.ibm.com You will log on using the following information: USER: anonymous PASSWORD: your complete e-mail address /* case sensitive to directory */ Type: cd /toibm/im NOTE: The /toibm/im directory is the recommended directory that should be used to FTP documentation to IBM. Putting diagnostic documentation into any other directory may significantly delay analysis and could result in the doc being purged before it can be successfully downloaded. At this point you are now attached to the IBM FTP site and located in the proper directory in which to place your files. Here is a sample of how to place a file on the site. >>> assume you are now connected to the site cd /toibm/im (case sensitive) binary /* set mode <----- */ put input.dataset xxxxx.bbb.ccc.yyy.yyy.[TRS][.CRY|.CRY64] quit For details on the new file naming convention, please refer to Section 2.C in this document. ****************************************************** *** Section 2.B - TERSE *** ****************************************************** Reference this IBM Website for TERSE instructions : http://techsupport.services.ibm.com/390/trsmain.html It is highly recommended that you TERSE your files using TRSMAIN and send them in BINARY mode. ****************************************************** * Section 2.C Naming Conventions For New Directory * * Structure as of September 29, 2006 * ****************************************************** xxxxx.bbb.ccc.yyy.yyy.[TRS][.CRY | .CRY64] Field Explanation Sample ----- ----------- ------ xxxxx PMR Number 34143 bbb Branch Office 055 ccc IBM Country Code 000 yyy.yyy A short description for the file dump type TRS Mandatory Identifier 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) **************************************************************** If file is encrypted by using FTPENCR or FTPENCRD, please update PMR with keyword "ENCRKEY=PASSWORD" where PASSWORD is the encyption KEY **************************************************************** Example 34143.055.724.dump.TRS.CRY (PMR_#.branch_office_#.country_code.dump.TRS.CRY) Take care to use the binary option before transfer. Some additional remarks: * To reduce reaction time, inform your IBM software support about the transfered files. * The material will be automatically deleted after 7 days. * The FTP GET and LS options are intentionally disabled. * We strongly recommend to transfer files in a tersed format (using TRSMAIN). * If file is encrypted, please use keyword "ENCRKEY=PASSWORD" in pmr text to indicate the correct password. ****************************************************** *** Section 3 - Common Mistakes *** ****************************************************** Reference the following website for additional information and restrictions : http://techsupport.services.ibm.com/390/trsmain.html 1) Naming convention not followed. 2) Doc is FTP'ed to a different directory than /toibm/im. This will result in a significant delay and could result in the doc being purged before it can be downloaded. 3) Special characters that are allowed on the FTP site are used but these characters are not allowed on MVS. 4) TRSMAIN does not support Tape. Tape Datasets should be IEBGENER'ed to DASD then Tersed with TRSMAIN. 5) If the large files are not TERSED, the customers site will time out during a transmission. Make sure you you define your FTP to wait up to 10 minutes prior to timing out. 6) Not specifing TERSE when file is tersed. ****************************************************** *** Section 4 - Sample TERSE and FTP JCL *** ****************************************************** //PREPSTEP EXEC PGM=IEFBR14 //DD1 DD DISP=(MOD,DELETE,DELETE), // SPACE=(CYL,(1,1),RLSE), // DSN=HLQ.tersed.dataset.you.need.2send //* //TERSE EXEC PGM=TRSMAIN,PARM=PACK //SYSPRINT DD SYSOUT=* //INFILE DD DISP=SHR,DSN=HLQ.untersed.dataset.you.need.2send //OUTFILE DD DISP=(NEW,CATLG,DELETE), // DCB=(LRECL=1024,BLKSIZE=6144,RECFM=FB), // SPACE=(CYL,(1,1),RLSE), // UNIT=(SYSDA,1), // DSN=HLQ.tersed.dataset.you.need.2send //* //FTPPUT EXEC PGM=FTP,REGION=12288K, // PARM='testcase.software.ibm.com' //STEPLIB DD DISP=SHR,DSN=SYS1.TCPIP.LINKLIB //SYSUDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //OUTPUT DD SYSOUT=* //INPUT DD * anonymous your.email@complete.address.com cd /toibm/im lcd 'HLQ' <<=== Can be multiple levels... 'HLQ.HLQ2' binary put tersed.dataset.you.need.2send xxxxx.bbb.ccc.yyy.yyy.TRS quit /* where HLQ = High Level Qualifier. In the above JCL: The dataset names on the DSN of //DD1 in PREPSTEP and //OUTFILE in TERSE should be the same. This is also the same dataset being sent on the 'put' statement in the FTPPUT step. The 'lcd' <localsite change directory) allows you to specify HLQ which will shorten the length of the file name required on the 'put' command. i.e. from above: lcd 'HLQ' binary put tersed.dataset.you.need.2send xxxxx.bbb.ccc.yyy.yyy.TRS You can also change the dataset name as follows: lcd 'HLQ.tersed.dataset' binary put you.need.2send xxxxx.bbb.ccc.yyy.yyy.TRS will both result in dataset HLQ.tersed.dataset.you.need.2send to be put out to the FTP Site as xxxxx.bbb.ccc.yyy.yyy.TRS >>>>>>>>>>>>>>>>>>>> OPTION II <<<<<<<<<<<<<<<<<<<<<<< http://www-05.ibm.com/de/support/ecurep/index.html
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II14631
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-03
Closed date
Last modified date
2011-06-03
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":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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 June 2011