Examples of using GIMUNZIP

In this first example, suppose a GIMZIP package contains a set of archive files and you want to extract the data sets and files from those archive files. In addition, you want to verify the integrity of the archive files and rename the destination data sets and files in the process. The following job stream can be used to perform such an operation.

Figure 1. GIMUNZIP example 1

//JOBx     JOB …
//STEP1    EXEC PGM=GIMUNZIP,PARM="HASH=YES"
//SMPDIR   DD PATH='/u/smpe/ORDER123/',PATHDISP=KEEP
//SMPCPATH DD PATH='/usr/lpp/smp/classes/',PATHDISP=KEEP
//SMPJHOME DD PATH='/usr/lpp/java/J6.0/',PATHDISP=KEEP
//SMPOUT   DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(50,10))
//SYSUT4   DD UNIT=SYSALLDA,SPACE=(CYL,(25,5))
//SYSIN    DD *
<GIMUNZIP>

  <ARCHDEF archid="SMPMCS"
           replace="YES"
           preserveid="YES"
           newname="/userid/IBM/DO000029/SMPMCS">
  </ARCHDEF>

  <ARCHDEF archid="FMID001.F1"
           newname="userid.IBM.FMID001.F1">
  </ARCHDEF>

  <ARCHDEF archid="FMID002.F2"
           newname="userid.IBM.FMID002.F2">
  </ARCHDEF>

  <ARCHDEF archid="GLOBAL"
           prefix="userid.IBM">
  </ARCHDEF>

  <ARCHDEF name="S0006.2003030335435443234.pax.Z"
           replace="YES"
           newname="/userid/IBM/DO000029/RootHFS/">
  </ARCHDEF>

</GIMUNZIP>
/*

Note: Blank lines and spaces have been added to the package control tags for clarity, but are not required.

This second example of the GIMUNZIP operation uses the new storclas and catalog attributes:

Figure 2. GIMUNZIP example 2

//jobname JOB ...
//UNZIP EXEC PGM=GIMUNZIP,PARM=“HASH=NO”
//SMPDIR DD PATH='/u/zosmf/swiExport/',PATHDISP=KEEP
//SMPCPATH DD PATH='/usr/lpp/smp/classes/',PATHDISP=KEEP
//SMPJHOME DD PATH='/usr/lpp/java/J6.0/',PATHDISP=KEEP
//SMPOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(50,10))
//SYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(25,5))
//SYSIN DD *
<GIMUNZIP>
  <TEMPDS unit=“SYSALLDA”> </TEMPDS>
  <ARCHDEF archid="LV1022.SYS1.MIGLIB"         
           newname="SYS1.MIGLIB"                    
           volume=“STG833”
           catalog=“NO” >
  </ARCHDEF>
  <ARCHDEF archid="ML5443.SYS1.AOS12"          
           newname="AOS.AOS12"
           storclas=“STANDARD”
           catalog=“YES” >
  </ARCHDEF>
</GIMUNZIP>
/*

In this example, the <TEMPDS> tag indicates the device unit type SYSALLDA will be used when allocating temporary work data sets. If the target MIGLIB data set does not already exist on volume STG833, then it will be allocated on that volume and will not be cataloged. In addition, if the target AOS12 data set does not already exist, it will be allocated using storage class STANDARD and will be cataloged.