########################################################################
#                                                                      #
# COMPONENT_NAME: WebSphere MQ Integrator Broker                       #
#                                                                      #
# Program Number 5655I5800                                             #
# (C) COPYRIGHT International Business Machines Corp. 1999, 2001       #
# All Rights Reserved                                                  #
# Licensed Material - Property of IBM                                  #
#                                                                      #
# US Government Users Restricted Rights - Use, duplication or          #
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.    #
#                                                                      #
########################################################################

The following files contain PTFs that equate to CSD09 for WebSphere 
MQ Integrator Broker V2.1 for z/OS:-

UK00028.TRS
UK05695.TRS

They are supplied in packed format.  When transferring to z/OS they must
be downloaded in binary format into sequential datasets with the 
following attributes :-

Organization  . . . : PS   
Record format . . . : FB   
Record length . . . : 1024 
Block size  . . . . : 6144 
1st extent tracks . : 500 
Secondary tracks  . : 50   

You can use the following sample JCL to allocate these datasets:

//* < INSERT A VALID JOBCARD HERE >                                     
//*                                                                     
//ALLOCATE EXEC PGM=IEFBR14                                             
//SYSMOD1  DD  DSN=<YOUR HIGH LEVEL QUALIFIER>.UK00028.TRS,
//             DISP=(NEW,CATLG,DELETE),                                 
//             UNIT=SYSDA,                                              
//             SPACE=(TRK,(500,50),RLSE),                               
//             DSORG=PS,                                                
//             DCB=(RECFM=FB,LRECL=1024,BLKSIZE=6144)                   
//*                                                                     
//SYSMOD2  DD  DSN=<YOUR HIGH LEVEL QUALIFIER>.UK05695.TRS,             
//             DISP=(NEW,CATLG,DELETE),                                 
//             UNIT=SYSDA,                                              
//             SPACE=(TRK,(500,50),RLSE),                               
//             DSORG=PS,                                                
//             DCB=(RECFM=FB,LRECL=1024,BLKSIZE=6144)                   
//*                                                                     

Once you have allocated these datasets:
From an OMVS session on your target system
ftp ftp.software.ibm.com (from an OMVS session on your target system)
bin
cd software/mqseries/fixes/wmqibv21/zOS/CSD09
lcd '<HLQ>.'
mget *.TRS (replace
to download the TERSMAIN packed SYSMODs.

Alternatively, packed files can be downloaded to a distributed platform
and ftp'd as binary with the replace option. e.g.
put UK00028.TRS '<HLQ>.UK00028.TRS' (replace

Once loaded on the target system the datasets should be unpacked using
the TRSMAIN utility program.  This utility is freely available from :-

 http://techsupport.services.ibm.com/390/trsmain.html

The following example JCL can be used to unpack the datasets after the
<INSTALLATION SPECIFIC> changes have been made and a suitable job card
added.

//*****************************************************
//* UNTERSE APAR                                       
//*****************************************************
//UNPACK   EXEC PGM=TRSMAIN,PARM='UNPACK'              
//STEPLIB  DD DISP=SHR,DSN=<TERSE.LOADLIB>
//SYSPRINT DD SYSOUT=*                                 
//INFILE   DD DSN=<YOUR HIGH LEVEL QUALIFIER>.UK00028.TRS,
//         DISP=SHR                                    
//OUTFILE  DD DSN=<HLQ>.UK00028,  
//         DISP=(NEW,CATLG),                           
//         SPACE=(TRK,(1000,100,))                     
/*                                                     

The resulting files can then be applied using normal SMPE procedures.

########################################################################