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

Reply via email to