I am working as UID 0 with all required authority. I don't see any issue
with it. Still can you please suggest the authority required,So that I can
cross verify.

Regards
Venkat

On Wed, Jul 22, 2015 at 7:59 PM, Blake, Daniel J [CTR] <[email protected]>
wrote:

> I get a screen that will allow me to override the in-use message.  Perhaps
> you don't have the authority you need.
>
>
> Dan Blake
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of venkat kulkarni
> Sent: Wednesday, July 22, 2015 10:26 AM
> To: [email protected]
> Subject: Re: Library out of space issue while APPLY RSU
>
> Hello Dan,
>               This solution wont work because we are running system from
> primary RES volume and applying Maintenence on Alt RES volume and DDDEF
> also pointing to Alt RES volume dataset.
>
> Now, When I tried renaming Alt volume dataset with .old extension, I am
> getting below error.
>
>
>  
> ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
>  DSLIST - Data Sets on volume RESALT Data set in use
>
>  Command - Enter "/" to select action                  Message
> Volume
>
>  
> -------------------------------------------------------------------------------
>  R        SYS1.SASMMOD1
>  RESALT
>  ***************************** End of Data Set list
> ****************************
>
>
>
> ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
> ³ Data set 'SYS1.SASMMOD1' in use by another user, try later or enter HELP
> for ³ ³ a list of jobs and users allocated to 'SYS1.SASMMOD1'.
>     ³
>
> Regards
> Venkat
>
> On Wed, Jul 22, 2015 at 7:31 PM, Blake, Daniel J [CTR] <[email protected]>
> wrote:
>
> > Been there, done that.  Yes the system has a reserve on the dataset
> > names.  However if you have the proper authority you can:
> >
> > 1.      Rename the files using IDCAMS or ISPF 3.4.  Make sure you rename,
> > not delete them.
> > 2.      Then allocate new, larger ones using *.NEW or something that fits
> > your naming conventions as the LLQ.
> > 3.      Uncatalog the *.NEW data sets.
> > 4.      Rename the uncataloged data sets dropping the .NEW LLQ.
> > 5.      Rerun your SMP/E jobs.
> > 6.      Some point in time delete the old data sets from step 1.
> >
> > Note: I am assuming that SMP/E is pointing to your maintenance volume,
> > not your IPL volume.
> >
> >
> > Dan
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]]
> > On Behalf Of venkat kulkarni
> > Sent: Wednesday, July 22, 2015 9:41 AM
> > To: [email protected]
> > Subject: Re: Library out of space issue while APPLY RSU
> >
> > Hello,
> >         Thanks for reply. Yes, I am applying Maintenance not on
> > production system. Can you please  suggest on the issue I discussed
> before.
> >
> >
> > Regards
> > Venkat.
> >
> >
> >
> > On Wed, Jul 22, 2015 at 4:29 PM, Paul Gillis <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > > Please do not tell me that you are applying maintenance to a running
> > > system. Because if you are then you have probably just destroyed
> > > your IPL volume.
> > >
> > > Cheers,
> > > Paul Gillis
> > >
> > > -----Original Message-----
> > > From: IBM Mainframe Discussion List
> > > [mailto:[email protected]] On Behalf Of venkat kulkarni
> > > Sent: Wednesday, 22 July 2015 7:11 PM
> > > To: [email protected]<mailto:[email protected]>
> > > Subject: Library out of space issue while APPLY RSU
> > >
> > > Hello Group,
> > >                   I am applying RSU on z/OS 1.13 system and
> > > encountered
> > > D37-04 and E37-04 for various datasets like
> > >
> > > D37-04  SYS1.SASMMOD1  ---  is used by XCFAS , LLA,
> > > D37-04  SYS1.SISPLOAD   ---  is used by XCFAS , LLA,
> > > D37-04  SYS1.SGIMLMD0  ---  is used by XCFAS , LLA,
> > > D37-04  SYS1.NUCLEUS   ---
> > > D37-04  SYS1.LINKLIB       ---  is used by XCFAS , LLA,
> > > E37-04  SYS1.CNMLINK   ---  is used by XCFAS , LLA, NETVIEW
> > >
> > >
> > > Now, renaming the dataset to .old and then  create new dataset big
> > > big
> > size
> > > and then using ISPF option 3.3 for copy,   we have only option left is
> > >
> > > 1) Unallocate linkist (SETPROG LNKLST,UNALLOCATE) and then stop LLA
> > > ( P
> > > LLA)
> > >
> > > 2) For CNMLINK dataset, I will have to stop NETVIEW as well along
> > > with Unallocate linkist (SETPROG LNKLST,UNALLOCATE) and then stop
> > > LLA ( P
> > > LLA)
> > >
> > >
> > > 3) But for NUCLEUS dataset, I will have to bring down alll system in
> > > sysplex and then do remaining and creating bigger dataet and then
> > > copy content using ISP 3.3
> > >
> > >
> > >
> > > Do we have any other way to overcome this issue rather then copping
> > > LLA and XCFAS etc.
> > >
> > >
> > > Regards
> > > Venkat
> > >
> > > --------------------------------------------------------------------
> > > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to
> > > [email protected]<mailto:[email protected]> with
> > the message: INFO IBM-MAIN
> > >
> > > --------------------------------------------------------------------
> > > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to
> > > [email protected]<mailto:[email protected]> with
> > the message: INFO IBM-MAIN
> > >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to [email protected]<mailto:[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

Reply via email to