Our system programmer has requested a Mod 40 to keep on a single
residence volume for z/OS 2.2.
Might want to get Mod 54s.  Or a device that can expand existing volumes.

On Fri, Apr 22, 2016 at 12:32 PM, Jesse 1 Robinson
<[email protected]> wrote:
> After living in close quarters for some time with a single Mod-9 sysres, we 
> seem to have finally outgrown our britches for the next 2.1 RSU. Multiple 
> sysres volumes would require changes to our venerable system migration 
> process, which is used to populate seven different sysplexes from the SMP/E 
> target packs. So we're trying to procure Mod-27s in order not to have to 
> touch the migration mechanism. As Jerry indicates, multiple sysres volumes 
> would require a culture change in addition to a technical one. Bioware is the 
> most difficult area to manage. ;-)
>
> BTW the largest allocation on the sysres volume is SCUNTBL, a whopping 2769 
> cylinders, far larger than distant second SCEERUN2. We could probably stay on 
> a Mod-9 if we treated SCUNTBL as we do ZFS files, which we migrate and manage 
> separately by DSN. Still the simplest solution is a bigger volume.
>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> [email protected]
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Jerry Whitteridge
> Sent: Thursday, April 21, 2016 9:02 AM
> To: [email protected]
> Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge
>
> We use &SYSR1 through &SYSR5 to have a 5 pack resvol set (note these include 
> OMVS related HFS/ZFS - hence the number/sizes) and have no issues. Biggest 
> problem I have is folks inadvertently recataloging the datasets from their 
> indirect values while doing maintenance so we locked down the Master Cat such 
> that even the Sysprogs have restrictions on what they can change.
>
> Jerry Whitteridge
> Manager Mainframe Systems & Storage
> Albertsons - Safeway Inc.
> 925 738 9443
> Corporate Tieline - 89443
>
> If you feel in control
> you just aren't going fast enough.
>
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Lucas Rosalen
> Sent: Thursday, April 21, 2016 2:14 AM
> To: [email protected]
> Subject: EXTERNAL: Re: Respack Volume Size Challenge
>
> As far as I have seen, it's quite simple: create a &SYSR2 symbol (using
> &SYSR1 and changing last char from 1 to 2, for example) and update MCAT 
> accordingly.
> Once I've worked for a client that had 3-volumes respack. It indeed worked.
> We used to keep datasets like LINKLIB, MACLIB, NUCLEUS, etc in 1st volumes 
> though...
>
> -------------------------------------------------------------------------------------------------------------------------------
> *Lucas Rosalen*
> Emails: [email protected] / *[email protected]
> <[email protected]>*
> LinkedIn: http://br.linkedin.com/in/lrosalen
> Phone: +48 (71) 792 809 198
>
>
> 2016-04-21 10:45 GMT+02:00 Jake Anderson <[email protected]>:
>
>> Hello,
>>
>> From the z/OS 2.1, I have started using Mod-27 as the Load
>> address(Respack) for IPLing the z/OS 2.1 LPAR. I am curious how the
>> other Shops are managing when they do not options of using Mod-27 and
>> they have to survive with Mod-9. I believe the Extended Indirect cataloging 
>> is one Options.
>>
>> What kind of challenges are there when the Respack is divided into two
>> Volumes ?
>>
>> Jake
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Reply via email to