Re: Respack Volume Size Challenge

[ronjhawk...@sbcglobal.net]

Jesse,
That's exactly the sort of testing we do. Truecopy, HUR, Flashcopy, 
Shadowimage, FCSE...
Setting up target volumes on the primary, local and remote controllers is 
equally easy. Especially when we use scripts to provision tens of thousands of 
volumes in a single hit. The same script runs against each controller.
Even using a GUI I can create 20,000 volumes with a mix of 10 cylinder. 
3390-3/27/54/250/1GB sized volumes in about two hours starting with just the 
unformatted parity groups installed. I'm sure the other vendor's interfaces are 
equally fast and easy to use.
Ron


Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone 
Original message From: Jesse 1 Robinson <jesse1.robin...@sce.com> Date: 
5/18/2016  15:45  (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: 
[IBM-MAIN] Respack Volume Size Challenge 
There's one wrinkle that you may not see in a lab. We mirror all production 
DASD to our DR site. If I create an oddball volume in production, it requires 
creation of two more identical ones at the recovery site: one for direct 
mirroring and another one to flash to for running a system. This complicates 
volume mapping. I've been told by storage managers that 'wasted space' is a 
smaller problem for them than trying to manage odd-sized volumes. My few odd 
sizes are, for example, to contain sysplex couple data sets or JES2 checkpoint. 
Very small volumes for data sets that do not party well with others. 

.
.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ron Hawkins
Sent: Wednesday, May 18, 2016 2:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Respack Volume Size Challenge

All,

It's hard to imagine that any customer is limited to specific volume size 
nowadays.

For a decade or so now all the storage vendors have delivered the ability to 
make right-sized volumes, usually only limited to what z/OS supported around 
the time the controller model was introduced.

With virtual volumes now (HDS call it HDP) creating a right-sized volume is a 
piece of cake. Being in a lab this has made life extraordinarily easy to 
provision a range of volume sizes with a couple of mouse clicks, or some 
scripts. Alternatively, with thin provisioning offered by all three vendors you 
could make your SYSRES a 3390-54 and just use the space required for the one 
pack SYSRES. If you just use 20,000 CYLs then that's all you use from the pool 
- a bit like Iceberg revisited.

Ron

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ted MacNEIL
Sent: Sunday, May 15, 2016 6:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Respack Volume Size Challenge

Years ago (pre-9) respacks had ‎to be 'split up'. Now, we ask the risk!

-teD
  Original Message
From: Lucas Rosalen
Sent: Thursday, April 21, 2016 05:14
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, se

Re: Respack Volume Size Challenge

[Jesse 1 Robinson]

There's one wrinkle that you may not see in a lab. We mirror all production 
DASD to our DR site. If I create an oddball volume in production, it requires 
creation of two more identical ones at the recovery site: one for direct 
mirroring and another one to flash to for running a system. This complicates 
volume mapping. I've been told by storage managers that 'wasted space' is a 
smaller problem for them than trying to manage odd-sized volumes. My few odd 
sizes are, for example, to contain sysplex couple data sets or JES2 checkpoint. 
Very small volumes for data sets that do not party well with others. 

.
.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ron Hawkins
Sent: Wednesday, May 18, 2016 2:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Respack Volume Size Challenge

All,

It's hard to imagine that any customer is limited to specific volume size 
nowadays.

For a decade or so now all the storage vendors have delivered the ability to 
make right-sized volumes, usually only limited to what z/OS supported around 
the time the controller model was introduced.

With virtual volumes now (HDS call it HDP) creating a right-sized volume is a 
piece of cake. Being in a lab this has made life extraordinarily easy to 
provision a range of volume sizes with a couple of mouse clicks, or some 
scripts. Alternatively, with thin provisioning offered by all three vendors you 
could make your SYSRES a 3390-54 and just use the space required for the one 
pack SYSRES. If you just use 20,000 CYLs then that's all you use from the pool 
- a bit like Iceberg revisited.

Ron

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ted MacNEIL
Sent: Sunday, May 15, 2016 6:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Respack Volume Size Challenge

Years ago (pre-9) respacks had ‎to be 'split up'. Now, we ask the risk!

-teD
  Original Message
From: Lucas Rosalen
Sent: Thursday, April 21, 2016 05:14
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Ron Hawkins]

All,

It's hard to imagine that any customer is limited to specific volume size 
nowadays.

For a decade or so now all the storage vendors have delivered the ability to 
make right-sized volumes, usually only limited to what z/OS supported around 
the time the controller model was introduced.

With virtual volumes now (HDS call it HDP) creating a right-sized volume is a 
piece of cake. Being in a lab this has made life extraordinarily easy to 
provision a range of volume sizes with a couple of mouse clicks, or some 
scripts. Alternatively, with thin provisioning offered by all three vendors you 
could make your SYSRES a 3390-54 and just use the space required for the one 
pack SYSRES. If you just use 20,000 CYLs then that's all you use from the pool 
- a bit like Iceberg revisited.

Ron

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ted MacNEIL
Sent: Sunday, May 15, 2016 6:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Respack Volume Size Challenge

Years ago (pre-9) respacks had ‎to be 'split up'. Now, we ask the risk!

-teD
  Original Message
From: Lucas Rosalen
Sent: Thursday, April 21, 2016 05:14
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Ted MacNEIL]

Years ago (pre-9) respacks had ‎to be 'split up'. Now, we ask the risk!

-teD
  Original Message  
From: Lucas Rosalen
Sent: Thursday, April 21, 2016 05:14
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[John Eells]

Tom Marchant wrote:

On Sun, 24 Apr 2016 11:31:42 -0500, Mike Schwab wrote:


Once a volume exceeds 64K cylinders, the allocations must be a
multiple of 21 cylinders, and the volume must be a multiple of 1113
cylinders.  That is the z/OS requirements for EAV volumes.


More precisely, allocations from the Cylinder-managed space on an EAV
are rounded up to the next multiple of 21 cylinders. Allocations from the
track-managed space area up to cylinder 65520 continue to be allocated
as before. The boundary between them is cylinder 65520.

I don't know if there are any restrictions for using an EAV for an IPL volume.


Data sets that are accessed early in IPL must be below the line on an 
EAV, as must those which have their own access methods and have not been 
rewritten to support doing I/O to the cylinder-managed space.  The 
latter are probably most important for a one-pack system.


The (probably incomplete) list I have for system data sets has not been 
updated since z/OS V1.13, but I think these still cannot be above the line:


- Imbed and Keyrange attributes, incompatible CA sizes for VSAM
- NUCLEUS
- SVCLIB
- LOGREC
- VTOC & VTOCIX
- RACF databases
- Page data sets
- HFS data sets
- Parmlib concatenation data sets
- XRC Control, Master, or Cluster non-VSAM data sets

This should *not* be read to mean or imply that everything that is not 
listed here is supported above the line.  It's just the list of things I 
know about that don't work.


--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Jousma, David]

+1 on the mod-54's.We are all mod-54 for SYSRES.  When the dust settled, I 
am at 27% freespace.  Root filesystem alone on my 2.2 systems is 83K tracks.

_
Dave Jousma
Assistant Vice President, Manager, Mainframe Engineering
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Schwab
Sent: Friday, April 22, 2016 2:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Respack Volume Size Challenge

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 <jesse1.robin...@sce.com> 
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
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jerry Whitteridge
> Sent: Thursday, April 21, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge
>
> We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lucas Rosalen
> Sent: Thursday, April 21, 2016 2:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: EXTERNAL: Re: Respack Volume Size Challenge
>
> As far as I have seen, it's quite simple: create a  symbol 
> (using
>  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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
> <lrosa...@br.ibm.com>*
> LinkedIn: http://br.linkedin.com/in/lrosalen
> Phone: +48 (71) 792 809 198
>
>
> 2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:
>
>> 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 lists...@listserv.ua.edu 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 

Re: Respack Volume Size Challenge

[Tom Marchant]

On Sun, 24 Apr 2016 11:31:42 -0500, Mike Schwab wrote:

>Once a volume exceeds 64K cylinders, the allocations must be a
>multiple of 21 cylinders, and the volume must be a multiple of 1113
>cylinders.  That is the z/OS requirements for EAV volumes.

More precisely, allocations from the Cylinder-managed space on an EAV 
are rounded up to the next multiple of 21 cylinders. Allocations from the 
track-managed space area up to cylinder 65520 continue to be allocated 
as before. The boundary between them is cylinder 65520.

I don't know if there are any restrictions for using an EAV for an IPL volume.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Mike Schwab]

Once a volume exceeds 64K cylinders, the allocations must be a
multiple of 21 cylinders, and the volume must be a multiple of 1113
cylinders.  That is the z/OS requirements for EAV volumes.

On Sun, Apr 24, 2016 at 10:41 AM, R.S.  wrote:
> W dniu 2016-04-23 o 20:46, Mike Schwab pisze:
>>
>> [...]
>> Some vendors support 1 cylinder increments.  EAVs (Mod 59+) must be
>> incremented by 1113 cylinders.
>
>
> I'm curious about 1113 cyl increment.
> Is it requirement of EAV in z/OS or rather implementation specific feature
> of DS8000 disk system?
> I don't rmemeber a requierement the size of EAV (or EAS) to be integer
> multple of 1113 cyl.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
>
> --
> Treść tej wiadomości może zawierać informacje prawnie chronione Banku
> przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być
> jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś
> adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej
> przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie,
> rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie
> zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo,
> prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale
> usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub
> zapisane na dysku.
>
> This e-mail may contain legally privileged information of the Bank and is
> intended solely for business use of the addressee. This e-mail may only be
> received by the addressee and may not be disclosed to any third parties. If
> you are not the intended addressee of this e-mail or the employee authorized
> to forward it to the addressee, be advised that any dissemination, copying,
> distribution or any other similar activity is legally prohibited and may be
> punishable. If you received this e-mail by mistake please advise the sender
> immediately by using the reply facility in your e-mail software and delete
> permanently this e-mail including any copies of it either printed or saved
> to hard drive.
>
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl
> Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru
> Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88.
> Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości
> wpłacony) wynosi 168.955.696 złotych.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[R.S.]

W dniu 2016-04-23 o 20:46, Mike Schwab pisze:

[...]
Some vendors support 1 cylinder increments.  EAVs (Mod 59+) must be
incremented by 1113 cylinders.


I'm curious about 1113 cyl increment.
Is it requirement of EAV in z/OS or rather implementation specific 
feature of DS8000 disk system?
I don't rmemeber a requierement the size of EAV (or EAS) to be integer 
multple of 1113 cyl.


--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Mike Schwab]

Requires software and hardware that supports it.  Varies BY Vendor,
and WITHIN Vendor.
ICKDSF V 16+ has a REFRESH to pick up a new volume size, once changed
in the hardware.
Some vendors support 1 cylinder increments.  EAVs (Mod 59+) must be
incremented by 1113 cylinders.

On Fri, Apr 22, 2016 at 12:55 PM, Nims,Alva John (Al) <ajn...@ufl.edu> wrote:
> Wow,  I guess I have that to look forward to when going to 2.2.  My current 
> z/OS 1.13 SCUNTBL is only 64 CYL, ouch, one more nail for me to use to 
> convince my storage guy to give me a few Mod 27's.
>
> I do have a question and YES IT IS A DUMB ONE, I freely admit it, the more I 
> get back into z/OS, the more I do not know anymore, but I thought I had heard 
> of a way, could be my mind playing tricks, it does that a lot, but I thought 
> that there is a way to convert a Mod 9 to a Mod 27 in-place?  Could be a 
> hardware option or at a z/OS level, or both, maybe?
>
> Al Nims
> Systems Admin/Programmer 3
> UFIT
> University of Florida
> (352) 273-1298
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Jesse 1 Robinson
> Sent: Friday, April 22, 2016 1:32 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Respack Volume Size Challenge
>
> 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
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Jerry Whitteridge
> Sent: Thursday, April 21, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge
>
> We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Lucas Rosalen
> Sent: Thursday, April 21, 2016 2:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: EXTERNAL: Re: Respack Volume Size Challenge
>
> As far as I have seen, it's quite simple: create a  symbol (using
>  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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
> <lrosa...@br.ibm.com>*
> LinkedIn: http://br.linkedin.com/in/lrosalen
> Phone: +48 (71) 792 809 198
>
>
> 2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:
>
>> 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 ?
>>
>&

Re: Respack Volume Size Challenge

[Jesse 1 Robinson]

My R13 version of SCUNTBL is 127 cylinders. 2.1 was a huge increase. I'll leave 
the 'in-place' volume conversion to the hardware gurus. 

.
.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Nims,Alva John (Al)
Sent: Friday, April 22, 2016 10:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Respack Volume Size Challenge

Wow,  I guess I have that to look forward to when going to 2.2.  My current 
z/OS 1.13 SCUNTBL is only 64 CYL, ouch, one more nail for me to use to convince 
my storage guy to give me a few Mod 27's.

I do have a question and YES IT IS A DUMB ONE, I freely admit it, the more I 
get back into z/OS, the more I do not know anymore, but I thought I had heard 
of a way, could be my mind playing tricks, it does that a lot, but I thought 
that there is a way to convert a Mod 9 to a Mod 27 in-place?  Could be a 
hardware option or at a z/OS level, or both, maybe?

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, April 22, 2016 1:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Respack Volume Size Challenge

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jerry Whitteridge
Sent: Thursday, April 21, 2016 9:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge

We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lucas Rosalen
Sent: Thursday, April 21, 2016 2:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Nims,Alva John (Al)]

Wow,  I guess I have that to look forward to when going to 2.2.  My current 
z/OS 1.13 SCUNTBL is only 64 CYL, ouch, one more nail for me to use to convince 
my storage guy to give me a few Mod 27's.

I do have a question and YES IT IS A DUMB ONE, I freely admit it, the more I 
get back into z/OS, the more I do not know anymore, but I thought I had heard 
of a way, could be my mind playing tricks, it does that a lot, but I thought 
that there is a way to convert a Mod 9 to a Mod 27 in-place?  Could be a 
hardware option or at a z/OS level, or both, maybe?

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, April 22, 2016 1:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Respack Volume Size Challenge

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jerry Whitteridge
Sent: Thursday, April 21, 2016 9:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge

We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lucas Rosalen
Sent: Thursday, April 21, 2016 2:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Mike Schwab]

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
<jesse1.robin...@sce.com> 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
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Jerry Whitteridge
> Sent: Thursday, April 21, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge
>
> We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Lucas Rosalen
> Sent: Thursday, April 21, 2016 2:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: EXTERNAL: Re: Respack Volume Size Challenge
>
> As far as I have seen, it's quite simple: create a  symbol (using
>  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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
> <lrosa...@br.ibm.com>*
> LinkedIn: http://br.linkedin.com/in/lrosalen
> Phone: +48 (71) 792 809 198
>
>
> 2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:
>
>> 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: EXTERNAL: Re: Respack Volume Size Challenge

[Jerry Whitteridge]

To expand a bit more on our multi volume respack environment (as Skip points 
out the biggest challenges were with the wetware and not the technical side). 
We long ago decided to have minimal entries in the MCAT except for what ware 
required to be in there OR were on the resvol sets. EVERYTHING on the Resvol 
sets are cataloged with a symbolic or on 2 specific other packs.

Our maintenance design is to do SMP work in a sandbox environment to the 
target/dlib datasets which are given Non Mcat Names and exist only in the 
Maintenance environment (Actually there are 3 sets of these names to reflect 
the 3 Maintenance environments (Sandbox/Dev/Prod)). From these target libs the 
running system resvol sets are built using DFDSS doing dataset renames as 
needed for the include/exclude process. Once IPL'd and tested the active resvol 
set is then dumped and sent to the next Sysplex for pack builds (as all catalog 
entries are symbolics no catalog changes are needed). When the resvol set is 
active in the new Sysplex then the smp target & dlibs are also updated in the 
original sandbox Maint environment to reflect the running set etc. etc.

This allows us to have maint environments that can a) be cloned, b)  have 3 
concurrent level  of any particular set of software at the same time c) apply a 
PTF to any specific environment as needed without disturbing the other 
environments.

But the real key is to the whole kit & kaboodle that the MCATS only contain 
symbolics  or aliases & then are locked down. Adding new volumes to the set is 
easy - add a new symbolic.


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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, April 22, 2016 10:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: Respack Volume Size Challenge

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jerry Whitteridge
Sent: Thursday, April 21, 2016 9:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge

We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lucas Rosalen
Sent: Thursday, April 21, 2016 2:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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

Re: FW: Respack Volume Size Challenge

[John Eells]

That makes perfect sense, thanks; it's just terminology.  (I always call 
the target and DLIB data sets "SMP/E-managed data sets" but that does 
not mean everyone has to!)  I'm less confused now.  ;-)



From: Nims,Alva John (Al)
Sent: Thursday, April 21, 2016 3:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RE: Respack Volume Size Challenge

We used multiple CSI's because a lot of the products were moved to their own 
set of CSI's (ZONEINDEX was used heavily), also ALL the TARGET and DLIB data 
sets (which I consider part of the SMPe data sets), SMPPTSx (multiple) and 
other SMP data sets.




--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Respack Volume Size Challenge

[Lucas Rosalen]

Not that I consider 3-volumes respack crazy, just wanted to point out that
it works even with more than 2 volumes :)
By the way, we used FILTERs in ADRDSSU job to fit each product in 1 volume
the best we could - for example, our Netview was entirely in volume #2 at
that time.

---
*Lucas Rosalen*
Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-22 16:04 GMT+02:00 Nims,Alva John (Al) <ajn...@ufl.edu>:

> Our email system was having conniption fits yesterday and I do not think
> this one made it through.
>
> Al Nims
> Systems Admin/Programmer 3
> UFIT
> University of Florida
> (352) 273-1298
>
> -Original Message-
> From: Nims,Alva John (Al)
> Sent: Thursday, April 21, 2016 3:35 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: RE: Respack Volume Size Challenge
>
> We used multiple CSI's because a lot of the products were moved to their
> own set of CSI's (ZONEINDEX was used heavily), also ALL the TARGET and DLIB
> data sets (which I consider part of the SMPe data sets), SMPPTSx (multiple)
> and other SMP data sets.
>
> Al Nims
> Systems Admin/Programmer 3
> UFIT
> University of Florida
> (352) 273-1298
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Eells
> Sent: Thursday, April 21, 2016 2:23 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Respack Volume Size Challenge
>
> Nims,Alva John , Al wrote:
> > You think 3 packs was crazy, for a time I worked with up to 10 packs,
> now it did include the entire SMPe data sets, but what we did there was
> include the primary res volume ID as part of the data set name, yep, the
> copy job was huge process.  Eventually the SMPe data sets were converted to
> being SMS managed, so the number of actual res volumes dropped to 3.  The
> zFS data sets used the primary volser in the DSN. So just as Lucas wrote,
> we use system symbols for the volser in the catalog.
> 
>
> I am not sure what you mean by "SMPe data sets."  The SMP/E CSI data sets
> should occupy a small fraction of a volume...nowhere near seven volumes!
> The SMPPTS could grow to be fairly large, depending on your APPLY/ACCEPT
> gap practices, but it's associated with the global zone and not the target
> zone (i.e., it need not be placed on the sysres volume set).
>
> Can you elaborate a bit?
>
> --
> John Eells
> IBM Poughkeepsie
> ee...@us.ibm.com
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

FW: Respack Volume Size Challenge

[Nims,Alva John (Al)]

Our email system was having conniption fits yesterday and I do not think this 
one made it through.

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-Original Message-
From: Nims,Alva John (Al) 
Sent: Thursday, April 21, 2016 3:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RE: Respack Volume Size Challenge

We used multiple CSI's because a lot of the products were moved to their own 
set of CSI's (ZONEINDEX was used heavily), also ALL the TARGET and DLIB data 
sets (which I consider part of the SMPe data sets), SMPPTSx (multiple) and 
other SMP data sets.

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Eells
Sent: Thursday, April 21, 2016 2:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Respack Volume Size Challenge

Nims,Alva John , Al wrote:
> You think 3 packs was crazy, for a time I worked with up to 10 packs, now it 
> did include the entire SMPe data sets, but what we did there was include the 
> primary res volume ID as part of the data set name, yep, the copy job was 
> huge process.  Eventually the SMPe data sets were converted to being SMS 
> managed, so the number of actual res volumes dropped to 3.  The zFS data sets 
> used the primary volser in the DSN. So just as Lucas wrote, we use system 
> symbols for the volser in the catalog.


I am not sure what you mean by "SMPe data sets."  The SMP/E CSI data sets 
should occupy a small fraction of a volume...nowhere near seven volumes!  The 
SMPPTS could grow to be fairly large, depending on your APPLY/ACCEPT gap 
practices, but it's associated with the global zone and not the target zone 
(i.e., it need not be placed on the sysres volume set).

Can you elaborate a bit?

--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[John Eells]

Nims,Alva John , Al wrote:

You think 3 packs was crazy, for a time I worked with up to 10 packs, now it 
did include the entire SMPe data sets, but what we did there was include the 
primary res volume ID as part of the data set name, yep, the copy job was huge 
process.  Eventually the SMPe data sets were converted to being SMS managed, so 
the number of actual res volumes dropped to 3.  The zFS data sets used the 
primary volser in the DSN. So just as Lucas wrote, we use system symbols for 
the volser in the catalog.



I am not sure what you mean by "SMPe data sets."  The SMP/E CSI data 
sets should occupy a small fraction of a volume...nowhere near seven 
volumes!  The SMPPTS could grow to be fairly large, depending on your 
APPLY/ACCEPT gap practices, but it's associated with the global zone and 
not the target zone (i.e., it need not be placed on the sysres volume set).


Can you elaborate a bit?

--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Nims,Alva John (Al)]

You think 3 packs was crazy, for a time I worked with up to 10 packs, now it 
did include the entire SMPe data sets, but what we did there was include the 
primary res volume ID as part of the data set name, yep, the copy job was huge 
process.  Eventually the SMPe data sets were converted to being SMS managed, so 
the number of actual res volumes dropped to 3.  The zFS data sets used the 
primary volser in the DSN. So just as Lucas wrote, we use system symbols for 
the volser in the catalog.

The symbols can be setup like this,  is assigned by default the volser of 
the volume IPL'd from:
SYSDEF SYMDEF(='(1:4).S(6:1)')
SYSDEF SYMDEF(='(1:4).T(6:1)')

The system I currently work with uses a primary IPL volumes of MVSIP1, MVSIP2, 
MVSIP3
So when we IPl from MVSIP1, then  = MVSIS1 &  = MVSIT1
If IPLd from MVSIP2, then  = MVSIS2 &  = MVSIT2

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Eells
Sent: Thursday, April 21, 2016 7:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Respack Volume Size Challenge

Lucas Rosalen wrote:
> As far as I have seen, it's quite simple: create a  symbol 
> (using
>  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...


That's exactly what it was designed to do, and why we did it at the time.  Note 
that SYS1.NUCLEUS (and IPL text) must be on the first volume, as must the 
SYS1.SVCLIB data set.

Generally, if you can get enough on the volume to IPL, start JES, and log on, 
you are far ahead of the game should you have to recover the system at some 
point (including DR).

ServerPac's Recommended System Layout (RSL) automatic volume assignment process 
will put NUCLEUS and SVCLIB on the first volume and "try" meet the second 
objective too (assuming a local 3270 SNA terminal).

But it's certainly better to get a big enough volume to put all the target data 
sets (yes, the version root and SMP/E target CSI too) on one volume, all 
together.  ServerPac's RSL function will let you play with volume sizes to see 
how large a volume you need very quickly and you can see the effects by 
displaying what's on each volume if you have more than one.

--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: EXTERNAL: Re: Respack Volume Size Challenge

[Jerry Whitteridge]

We use  through  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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lucas Rosalen
Sent: Thursday, April 21, 2016 2:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: Respack Volume Size Challenge

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
<lrosa...@br.ibm.com>*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>:

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

 Warning: All e-mail sent to this address will be received by the corporate 
e-mail system, and is subject to archival and review by someone other than the 
recipient. This e-mail may contain proprietary information and is intended only 
for the use of the intended recipient(s). If the reader of this message is not 
the intended recipient(s), you are notified that you have received this message 
in error and that any review, dissemination, distribution or copying of this 
message is strictly prohibited. If you have received this message in error, 
please notify the sender immediately.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Lizette Koehler]

At one shop I worked at a long time ago, we had a 6 pack Sysres system.  


They were all 3390 Mod9s.  It worked quite well.

Currently our only issue is the OMVS datasets needed.  We have put those on a 
Sysres volume that is a 3390 Mod54 with all other SYSRES volumes being a 3390 
Mod27.  We may need to loo, at using a 3390 Mod-A (The extend volume) to allow 
for the growth of some of the OMVS Files for z/OS we ship on the Sysres volumes.


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jake Anderson
> Sent: Thursday, April 21, 2016 1:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Respack Volume Size Challenge
> 
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[John Eells]

Lucas Rosalen wrote:

As far as I have seen, it's quite simple: create a  symbol (using
 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...



That's exactly what it was designed to do, and why we did it at the 
time.  Note that SYS1.NUCLEUS (and IPL text) must be on the first 
volume, as must the SYS1.SVCLIB data set.


Generally, if you can get enough on the volume to IPL, start JES, and 
log on, you are far ahead of the game should you have to recover the 
system at some point (including DR).


ServerPac's Recommended System Layout (RSL) automatic volume assignment 
process will put NUCLEUS and SVCLIB on the first volume and "try" meet 
the second objective too (assuming a local 3270 SNA terminal).


But it's certainly better to get a big enough volume to put all the 
target data sets (yes, the version root and SMP/E target CSI too) on one 
volume, all together.  ServerPac's RSL function will let you play with 
volume sizes to see how large a volume you need very quickly and you can 
see the effects by displaying what's on each volume if you have more 
than one.


--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Respack Volume Size Challenge

[Lucas Rosalen]

As far as I have seen, it's quite simple: create a  symbol (using
 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: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2016-04-21 10:45 GMT+02:00 Jake Anderson :

> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Respack Volume Size Challenge

[Jake Anderson]

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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN