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.
On Wed, Dec 3, 2014 at 12:16 AM, Lucas Rosalen <[email protected]>
wrote:
> Thanks Doug, I really overlooked that error code.
> In this case, you could try allocating the OMVS dataset as multi-volume I
> guess.
>
>
> -------------------------------------------------------------------------------------------------------------------------------
> *Lucas Rosalen*
> [email protected] / *[email protected] <[email protected]>*
> +55 19 9-8146-7633
>
> 2014-12-02 13:55 GMT-02:00 Doug Henry <[email protected]>:
>
> > Hi Lucus,
> > The dadsm error "DADSM FAILURE (044E0097)" means "requested space
> exceeds
> > 65535 tracks
> > for a data set type that is limited to 65535 tracks per volume. "
> >
> > I would work with the person or group that handles SMS to get the proper
> > allocation request.
> >
> > Doug
> >
> >
> > On Tue, 2 Dec 2014 12:21:14 -0200, Lucas Rosalen <
> [email protected]>
> > wrote:
> >
> > >Well, you'll have to make space on TESTG storage group. This might be
> > >accomplished by either cleaning up (deleting) unused datasets or by
> adding
> > >more volumes to that storage group.
> > >It says that OMVS.SYS5.RSU.SLE is 88% full. Is that before or after
> > running
> > >the unpax job? Maybe you could delete unused files from that filesystem
> to
> > >make room inside it, then you wouldn't have to allocate a new
> filesystem.
> > >
> > >Regards,
> > >
> > >
> >
> >
> >-------------------------------------------------------------------------------------------------------------------------------
> > >*Lucas Rosalen*
> > >[email protected]
> > >+55 19 9-8146-7633
> > >
> > >2014-12-02 8:49 GMT-02:00 Mainframe Mainframe <[email protected]
> >:
> > >
> > >> Hello Group,
> > >> I am in the process of applying RSU1410 but while
> > >> unzipping it I am facing space issue .
> > >>
> > >>
> > >> > /bin/pax -zvrf
> > /u/SLE/RSU1410/SMPPTFIN/S0001.SHOPZ.S2654213.SMPMCS.pax.Z
> > >> > ./GIMFAF.XML
> > >>
> > >> ./GIMFAF.XML
> > >>
> > >>
> >
> -------------------------------------------------------------------------------
> > >> DATE 11/19/14 TIME 22:19:47
> 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
> > >>
> > >>
> > >>
> > >> 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/smpe2014323221642624191/GIMFAF.XML)
> > >> IEF142I UNZIPRSU UNZIP - STEP WAS EXECUTED - COND CODE 0012
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> -------------------------------------------------------------------------------
> > >> # df -Pk /u/SLE/RSU1410/
> > >> Filesystem 1024-blocks Used Available Capacity
> Mounted
> > on
> > >> OMVS.SYS5.RSU.SLE 3072048 2696780 375152 88%
> > /u/SLE/RSU1410
> > >> # exit
> > >>
> > >>
> > >> As RSU size is really big, So I am trying to allocate bigger space of
> > HFS
> > >> dataset with 4000MB and multi volume and which i will be mounting
> at
> > >> /u/SLE/RSU1410//temp but I am getting below issue. I think we have
> > space
> > >> constraint of allocating these dataset.
> > >>
> > >>
> > >>
> > >>
> > >> IKJ56893I DATA SET OMVS.SYS5.RSU.TEMP NOT ALLOCATED+
> > >> IGD17281I ALLOCATION FOR DATA SET
> > >> OMVS.SYS5.RSU.TEMP FAILED,
> > >> VOLUME (ABL056) WAS EXPLICITLY SPECIFIED FOR A GUARANTEED SPACE
> REQUEST
> > >> BUT WAS
> > >> REJECTED
> > >> 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:TESTG
> > >> IGD17279I 6 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ON THE
> INCLUDE
> > >> LIST
> > >> IGD17279I 1 VOLUMES WERE REJECTED BECAUSE OF A DADSM FAILURE
> (044E0097)
> > >> ***
> > >>
> > >> Can anybody help me to come out of this issue.
> > >>
> > >> ----------------------------------------------------------------------
> > >> 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
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
