Hello All,
Sorry for delay in response. This problem has been resolved
by removing all SMS related parameter and by just keeping HFS as DSN type.
Now I am able to allocate this bigger space of FS for unzipping purpose.
But my unzip still getting failed, with below error. I tried enough ways by
having larger size but same issue.
Unzip JCL,
//UNZIPRSU JOB 'MAINFRAME',CLASS=A,MSGCLASS=A,NOTIFY=&SYSUID
//UNZIP EXEC PGM=GIMUNZIP,PARM='HASH=NO'
//SYSUT3 DD UNIT=3390,SPACE=(CYL,(400,100))
//SYSUT4 DD UNIT=3390,SPACE=(CYL,(400,100))
//SMPOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SMPDIR DD PATH='/u/SLE/RSU1410/',
// PATHDISP=KEEP
//SMPWKDIR DD PATH='/u/SLE/RSU1410/temp',
// PATHDISP=KEEP
//SYSIN DD DATA,DLM=$$
<GIMUNZIP>
<ARCHDEF
name="SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z"
volume="TEMP01"
newname="SMPE.ZOS21.RSU.S2654213.SMPMCS"
replace="yes">
</ARCHDEF>
<ARCHDEF
name="SMPHOLD/S0002.SHOPZ.S2654213.SMPHOLD.pax.Z"
volume="TEMP01"
newname="SMPE.ZOS21.RSU.S2654213.SMPHOLD"
replace="yes">
</ARCHDEF>
</GIMUNZIP>
$$
Size of RSU and other related datasets are
. . . . . . . . . . . . . . . . . . . . . . . . .
. .
Data Set Information
Command ===>
More:
+
Data Set Name . . . . : SMPE.ZOS21.RSU.S2654213.SMPMCS
General Data Current Allocation
Management class . . : **None** Allocated cylinders : 4,300
Storage class . . . : **None** Allocated extents . : 1
Volume serial . . . : TEMP01
Device type . . . . : 3390
Data class . . . . . : **None**
Organization . . . : PS Current Utilization
Record format . . . : FB Used cylinders . . : 0
Record length . . . : 80 Used extents . . . : 0
Block size . . . . : 27920
1st extent cylinders: 4300
Secondary cylinders : 0 Dates
Data set name type : Creation date . . . : 2014/12/04
SMS Compressible. . : NO Referenced date . . : ***None***
Expiration date . . : ***None***
# df -Pk /u/SLE/RSU1410/
Filesystem 1024-blocks Used Available Capacity Mounted on
OMVS.SYS5.RSU.SAURABH 3072048 2696780 375152 88%
/u/SLE/RSU1410
# df -Pk /u/SLE/RSU1410/temp
Filesystem 1024-blocks Used Available Capacity Mounted on
OMVS.SYS5.RSU.TEMP 7168032 4966228 2201700 70%
/u/SLE/RSU1410/temp
Error, I am getting is,
********************************* TOP OF DATA
**********************************
-------------------------------------------------------------------------------
DATE 12/04/14 TIME 06:19:15 SMP/E
36.13
UNIX COMMAND OUTPUT
> /bin/pax -zvrf /u/SLE/RSU1410/SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z
> ./GIMFAF.XML
./GIMFAF.XML
-------------------------------------------------------------------------------
DATE 12/04/14 TIME 06:22:33 SMP/E
36.13
UNIX COMMAND OUTPUT
> /bin/pax -zvrf /u/SLE/RSU1410/SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z
./GIMFAF.XML
./SMPPTFIN
pax: FSUM6260 write error on file "./SMPPTFIN": EDC5133I No space left on
device
******************************** BOTTOM OF DATA
********************************
----------<GIMUNZIP>
----------<ARCHDEF
----------name="SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z"
----------volume="TEMP01"
----------newname="SMPE.ZOS21.RSU.S2654213.SMPMCS"
----------replace="yes">
----------</ARCHDEF>
----------<ARCHDEF
----------name="SMPHOLD/S0002.SHOPZ.S2654213.SMPHOLD.pax.Z"
----------volume="TEMP01"
----------newname="SMPE.ZOS21.RSU.S2654213.SMPHOLD"
----------replace="yes">
----------</ARCHDEF>
----------</GIMUNZIP>
GIM68200E ** PROCESSING FAILED FOR THE /bin/pax UNIX SYSTEM SERVICE COMMAND.
GIM47800S ** AN ERROR OCCURRED WHILE GIMUNZIP WAS PROCESSING ARCHIVE
/u/SLE/RSU1410/SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z.
GIM20501I GIMUNZIP PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS
12.
IGD104I HFS FILE WAS RETAINED, DDNAME IS (SMP00001)
FILENAME IS (/u/SLE/RSU1410/temp/smpe2014338061915982269/GIMFAF.XML)
IEF142I UNZIPRSU UNZIP - STEP WAS EXECUTED - COND CODE 0012
IEF285I SYS14338.T061915.RA000.UNZIPRSU.R0109899 DELETED
IEF285I VOL SER NOS= STO500.
I am not getting any clue to solve this issue. how much more space I will
have to allocate or some other way to resolve this.
On Thu, Dec 4, 2014 at 7:16 PM, Doug Henry <[email protected]> wrote:
> You still didn't provide the D SMS commands oupput. However I also notice
> that on Ispf allocate screen you had specified storage class TESTSC but
> the sms error message ICG17290I had storage classs TESTSG.
>
> Storage class . . . . TESTSC
>
> IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1
> >> > WERE ELIGIBLE FOR VOLUME SELECTION.
> >> > THE CANDIDATE STORAGE GROUPS WERE:TESTSG
>
> When I do your allocation I get 96001 tracks on the first volume and the
> second volume marked as a canadidate.
>
> Partial output of listc ent(myid.x.hfs) all
>
> VOLSER------------TEST22
>
> VOLSER-----------------*
>
> Doug
>
>
> On Thu, 4 Dec 2014 13:24:43 +0530, Mainframe Mainframe <
> [email protected]> wrote:
>
> >Yes. Both volume are part of same storage group . Also I am allocating HFS
> >dataset, so aggrgrow= on parameter doesn't matter here.
> >
> >Any other clue to define HFS dataset with bigger space more then 4000MB.
> >
> >
> >On Wed, Dec 3, 2014 at 10:09 PM, Doug Henry <[email protected]>
> wrote:
> >
> >> Are you sure that the volumes you used in the list are sms managed and
> in
> >> the TESTSC storage class ?
> >>
> >> Issue D SMS,VOL(ABL056) and D SMS,VOL(ABL057) and show us the results.
> >>
> >> Doug
> >>
> >> On Wed, 3 Dec 2014 14:27:36 +0530, Mainframe Mainframe <
> >> [email protected]> wrote:
> >>
> >> >Hello All, Thanks for reply .I tried creating multi volume HFS
> dataset, as
> >> >I wanted space more then 4000MB but I was getting the issue which I
> >> >mentioned before.
> >> >
> >> > . . . . . . . . . . . . . . . . . . . . . . .
> . .
> >> > . .
> >> > Menu RefList Utilities Help
> >> >
> >>
> ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
> >> > Allocate New Data Set
> >> > Command ===>
> >> >
> More:
> >> > +
> >> > Data Set Name . . . : OMVS.SYS5.RSU.TEMP
> >> >
> >> > Management class . . . TESTMC (Blank for default management
> >> class)
> >> > Storage class . . . . TESTSC (Blank for default storage
> class)
> >> > Volume serial . . . . (Blank for system default
> volume)
> >> **
> >> > Device type . . . . . (Generic unit or device
> address) **
> >> > Data class . . . . . . TESTDC (Blank for default data class)
> >> > Space units . . . . . MEGABYTE (BLKS, TRKS, CYLS, KB, MB, BYTES
> >> > or RECORDS)
> >> > Average record unit (M, K, or U)
> >> > Primary quantity . . 4500 (In above units)
> >> > Secondary quantity 0 (In above units)
> >> > Directory blocks . . 0 (Zero for sequential data set) *
> >> > Record format . . . . U
> >> > Record length . . . . 0
> >> > Block size . . . . .
> >> > Data set name type HFS (LIBRARY, HFS, PDS, LARGE,
> BASIC, *
> >> > EXTREQ, EXTPREF or blank)
> >> >
> >> > . . . . . . . . . . . . . . . . . . . . . . .
> . .
> >> > . .
> >> > Menu RefList Utilities Help
> >> > Ä ÚÄÄÄÄÄÄÄÄÄÄÄÄ Multivolume Allocation ÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
> >> >ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
> >> > ³ ³
> >> > C ³ Command ===> ³
> >> > ³ ³
> More:
> >> >- +
> >> > D ³ Enter the number of volumes to allocate or ³ lt data class)
> >> > ³ the names of one or more volumes and ³ S, KB, MB, BYTES
> >> > ³ press Enter to allocate or enter Cancel ³
> >> > ³ command to exit. If a number is entered, ³
> >> > ³ any volume names will be ignored. ³
> >> > ³ More: + ³
> >> > ³ Number of volumes to allocate: ³ tial data set) *
> >> > ³ ³
> >> > ³ Volume names: ³
> >> > ³ 1. ABL056 2. ABL057 3. 4. ³
> >> > ³ 5. 6. 7. 8. ³ DS, LARGE,
> BASIC, *
> >> > ³ 9. 10. 11. 12. ³ or blank)
> >> > ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ k)
> >> > Expiration date . . . (YY/MM/DD, YYYY/MM/DD
> >> > Enter "/" to select option YY.DDD, YYYY.DDD in Julian form
> >> > / Allocate Multiple Volumes DDDD for retention period in
> days
> >> > or blank)
> >> >
> >> >
> >> >
> >> >
> >> > IKJ56893I DATA SET OMVS.SYS5.RSU.TEMP NOT ALLOCATED+
> >> > IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET
> >> > OMVS.SYS5.RSU.TEMP
> >> > IGD17277I THERE ARE (8) CANDIDATE VOLUMES OF WHICH (8) ARE ENABLED OR
> >> >QUIESCED
> >> > IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1
> >> > WERE ELIGIBLE FOR VOLUME SELECTION.
> >> > THE CANDIDATE STORAGE GROUPS WERE:TESTSG
> >> > IGD17279I 7 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT
> >> >SPACE (0
> >> >41A041D)
> >> >
> >> >
> >> > Space on these volumes are
> >> >
> >> >. . . . . . . . . . . . . . . . . . . . . . .
> . .
> >> > . .
> >> > Menu RefList RefMode Utilities Help
> >> >ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ VTOC Summary Information
> >> >ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
> >> > Volume . : ABL056
> >> > ³
> >> > Command ===>
> >> > ³
> >> >
> >> > ³
> >> > Unit . . : 3390
> >> > ³
> >> >
> >> > ³
> >> > Volume Data VTOC Data Free Space Tracks
> >> > Cyls ³
> >> > Tracks . : 150,255 Tracks . : 60 Size . . : 95,344
> >> >6,356 ³
> >> > %Used . : 36 %Used . . : 1 Largest . : 95,340
> >> >6,356 ³
> >> > Trks/Cyls: 15 Free DSCBS: 2,995 Free
> >> > ³
> >> > Extents . : 2
> >> > ³
> >> >
> >> > ³
> >> >
> >> > ³
> >>
> >>
> >ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
> >> >
> >> >
> >> > . . . . . . . . . . . . . . . . . . . . . . .
> . .
> >> > . .
> >> > Menu RefList RefMode Utilities Help
> >> >ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ VTOC Summary Information
> >> >ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
> >> >³ Volume . : ABL057
> >> > ³
> >> >³ Command ===>
> >> > ³
> >> >³
> >> > ³
> >> >³ Unit . . : 3390
> >> > ³
> >> >³
> >> > ³
> >> >³ Volume Data VTOC Data Free Space Tracks
> >> > Cyls ³
> >> >³ Tracks . : 450,765 Tracks . : 60 Size . . : 450,644
> >> > 30,042 ³
> >> >³ %Used . : 0 %Used . . : 1 Largest . : 450,644
> >> > 30,042 ³
> >> >³ Trks/Cyls: 15 Free DSCBS: 2,997 Free
> >> > ³
> >> >³ Extents . : 1
> >> > ³
> >> >³
> >> > ³
> >> >³
> >> > ³
> >>
> >>
> >ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
> >> >
> >> >
> >> >Is there any other way creating this multi volume dataset with space of
> >> >4500 + MB size.
> >> >
> >>
> >> ----------------------------------------------------------------------
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to [email protected] with the message: INFO IBM-MAIN
> >>
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
