I guess I still don’t understand all the hubbub....  If you aren’t applying 
maintenance to running system, then "fixing" sys1.miglib on another volume is a 
piece of cake, and does NOT involve any LLA unallocate commands etc....

When I go to rename SYS1.MIGLIB on my maintenance SYSRES RSM02A, I get:

IEC614I RENAME FAILED - RC 008, DIAGNOSTIC INFORMATION IS (040B0446),     
 IKJACCNT,RSM02A,SYS1.MIGLIB                                               
 DATA SET NAME IS IN USE BUT YOU HAVE AUTHORITY TO OVERRIDE THIS TEST      

And then I press enter...

                          Rename Data Set In Use                           
Command ===>                                                               
                                                                           
Data Set Name . : SYS1.MIGLIB                                              
Volume  . . . . : RSM02A                                                   
                                                                           
  The system detected that a data set with the above name is in use        
  (possibly on another system) but it cannot determine whether it is the   
  data set you wish to rename. If it is the same data set and any program  
  has it open, renaming it could cause serious system and data integrity   
  problems.                                                                
                                                                           
  You have the extra security authority to rename the data set even though 
  its name is in use. Refer to the DFSMS documentation on the RENAME macro 
  for further information.                                                 
                                                                           
Instructions:                                                              
  Press ENTER to override data set name protection and rename the data     
  set.                                                                     
  Enter CANCEL or EXIT to cancel the rename request.                       
                                                                           
Am I missing something?   As for size, no need to hog wild on freespace *if* 
the only time it is an issue is applying to non-running sysres volume.
_____________________________________________________________________________________________________
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717


-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Kurt Quackenbush
Sent: Wednesday, June 12, 2019 11:18 AM
To: [email protected]
Subject: Re: SYS1.MIGLIB and LNKLST

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

On 6/12/2019 9:06 AM, Carmen Vitullo wrote:
> Just as an aside, the underlying issue is LPALIB, LINKLIB and MIGLIB 
> are underallocated in the ServerPac dialog, I've opened a case with 
> the serverpac folks years ago and alway "TRY" to remember to change 
> the allocation of these libraries prior to them being allocated. the 
> libraries are allocated with just enough space to install the OS from 
> the ServerPac, no room for maint in most cases.

Not to hijack the thread, but... I thought ServerPac already automatically adds 
20% (25?) free space, but I could be wrong.  In any case, how much free space 
should be allocated by ServerPac?  I saw 50% mentioned.  Is that enough?  
Should it be the same for every data set, or just the three you mention?  Is it 
possible to get any kind of consensus on this topic?

Kurt Quackenbush -- IBM, SMP/E Development Chuck Norris never uses CHECK when 
he applies PTFs.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL 
EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to