Yeah, I thought of that also, but still had to contend with the ENQ / LNKLST 
issue.

Thanks,

S. Veryl Ellis 

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

another option is to override SMP DDDEF in job JCL to the newly allocated & 
populated dataset. at end, you can do the renames, unallocation of lla, etc.

ITschak

On Tue, Jun 11, 2019 at 10:49 PM Carmen Vitullo <[email protected]> wrote:

> One of my first contracting jobs was working for state gov'mt, y2k, 
> and my first task was to apply maint to the current OS, the SMP/E 
> environment was pointing to a live sandbox system, I pointed this out 
> to my boss, and he said yeah, we do this all the time, :( so I 
> understand where David is coming from.
>
>
>
> Carmen Vitullo
>
> ----- Original Message -----
>
> From: "Veryl Ellis" <[email protected]>
> To: [email protected]
> Sent: Tuesday, June 11, 2019 2:42:57 PM
> Subject: Re: SYS1.MIGLIB and LNKLST
>
> Applying maintenance to a target SYSRES volume.
> I never apply maintenance to a running system.
>
> S. Veryl
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On 
> Behalf Of Jousma, David
> Sent: Tuesday, June 11, 2019 3:32 PM
> To: [email protected]
> Subject: Re: SYS1.MIGLIB and LNKLST
>
> Veryl,
>
>
> You are getting a lot of feedback that I consider a bit scary. Can you 
> clarify something? Are you trying to apply maintenance to your running 
> SYSRES? Or a copy of it, and are dealing with that type of enqueuer? 
> If the latter, then yes, allocate a .NEW version of MIGLIB, copy the 
> contents from the old to the new, and using appropriate tools, do the renames.
>
> If you are contemplating doing these activities on your running 
> system, well then, let me pop up a bowl of popcorn, and pour a 
> cocktail for this show.
>
> ______________________________________________________________________
> _______________________________
>
> 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 Veryl Ellis
> Sent: Tuesday, June 11, 2019 2:59 PM
> To: [email protected]
> Subject: SYS1.MIGLIB and LNKLST
>
> **CAUTION EXTERNAL EMAIL**
>
> **DO NOT open attachments or click on links from unknown senders or 
> unexpected emails**
>
> I'm applying maintenance to my target SYSRES and the target 
> SYS1.MIGLIB ran out of space (S/D37).
> Can anyone tell me how to get SYS1.MIGLIB out of the running Link List 
> concatenation, so I can delete and reallocate a larger target SYS1.MIGLIB?
> The standard SETPROG LNKLST stuff to delete a DSN from the link list 
> doesn't work on SYS1.MIGLIB.
>
> Thanks for any assist.
>
>
>
> S. Veryl Ellis
>
>
> ----------------------------------------------------------------------
> 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
>
> ----------------------------------------------------------------------
> 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
>


--
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for 
Legacy **|  *

----------------------------------------------------------------------
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