---
It may work for you, but I'd rather not have your (potential)
maintenance issues! (8-{[}
--
Never had a problem. Perhaps because we kept SYS1.IPL0 on th
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Rick Fochtman
>
>
--
>
> >>This poor practice was something instilled in the Tata contractors
we have employed.
> >>
> >>
> >
> >Simple answer to that: d
Rick,
Like you we had issues with spool size especially after we converted to
3800-3's. What I did say every month or so spin through sys logs. For a
month and graph out spool utilization and added spool volumes if I saw any
general up swing. I also cya'd email production and management. This
Ted,
I thought long and hard about this ages ago. I have a smpe proc with symbolic
volsers with a default pointing to my install volume I don't reall trust
the smpe dialogs ( and I never will) this also as a side benefit if anyone else
ever does an install while I am on vacation they will not
>I seldom have multiple SYSRES volumes. I use dsnames of SYS9 instead of SYS1,
>renaming when I install the resvol.
>If I'm forced to back it out, then I'm forced to leave the datasets
>uncataloged.
So, you do have (inexcusable) uncatalogued datasets, occasionally. (8-{]}
>The active SYSRES is
I catalog them as a single multi-volume dataset. I've always been
overly generous with spool space and thus have seldom needed to add
spool space.
I've never done it that way. And while one could do it that way and it would
-
I catalog them as a single multi-volume dataset. I've always been overly
generous with spool space and thus have seldom needed to add spool space.
What would happen when you reach the practical limit of 59 volumes?
>> >I catalog them as a single multi-volume dataset. I've always been overly
>> >generous with spool space and thus have seldom needed to add spool space.
>
>>What would happen when you reach the practical limit of 59 volumes?
Why do you say this?
>Up to 253 volumes can be designated as spool
Ted,
Technicality here if the dataset is cataloged with asterisks it is technically
cataloged.
Ed
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-
On Sat, 27 Aug 2011 10:28:13 -0500, Rick Fochtman wrote:
>I catalog them as a single multi-volume dataset. I've always been
>overly generous with spool space and thus have seldom needed to add
>spool space.
>
I've never done it that way. And while one could do it that way and it would
functi
On Sat, 2011-08-27 at 16:58 +, Ted MacNEIL wrote:
> >I catalog them as a single multi-volume dataset. I've always been overly
> >generous with spool space and thus have seldom needed to add spool space.
>
> What would happen when you reach the practical limit of 59 volumes?
Why do you say t
>I catalog them as a single multi-volume dataset. I've always been overly
>generous with spool space and thus have seldom needed to add spool space.
What would happen when you reach the practical limit of 59 volumes?
Also, what do you do with multiple sysres?
Multiple parm/lpa/load libs?
Since
---
You catalogue SPOOL?
And, secondary copies of LPA/LNK libs?
SPOOL space is cataloged as a single multi-volume dataset. Secondary
copies of LPA/LNK libs all have unique names.
Ri
andle multiple JES2 HASPACE datasets.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Rick Fochtman
Sent: Friday, August 26, 2011 4:05 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: JCL Changes and SMS and Not Cataloged Dat
>You're free to disagree, Ted, but I maintain that there's no excuse for ANY
>uncataloged datasets.
You catalogue SPOOL?
And, secondary copies of LPA/LNK libs?
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAI
I wonder how you handle multiple JES2 HASPACE datasets.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Rick Fochtman
> Sent: Friday, August 26, 2011 4:05 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: JCL Chang
In <995242624f0873419e71e8ce2105c5e5e070f91...@exmail01.scwf.nsc.com>,
on 08/26/2011
at 01:43 PM, "Donnelly, John P" said:
>This poor practice was something instilled in the Tata contractors we
>have employed.
Talk to your lawyers; if your outsource company is incompetent then
the not catalog
--
This poor practice was something instilled in the Tata contractors we have
employed.
Simple answer to that: don't hire them again.
Long before SMS, in 1981 (when I started), we had utilities to automatically
delete unca
I did not see if the author indicated if the Datasets in question were
GDG's or nt. If so could it be the noscratc issue?
Ed
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu
nal Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Scott Rowe
> Sent: Friday, August 26, 2011 2:36 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: JCL Changes and SMS and Not Cataloged Datasets
>
> How are they uncataloging SMS datas
How are they uncataloging SMS datasets? I could have sworn a normal user
could not accomplish that without special privileges. Since I no longer
have a system, I can't verify this, but I thought a DELETE NOSCRATCH for an
SMS dataset failed unless you had proper authorization.
On Fri, Aug 26, 201
>This poor practice was something instilled in the Tata contractors we have
>employed.
Simple answer to that: don't hire them again.
Long before SMS, in 1981 (when I started), we had utilities to automatically
delete uncatalogued datasets.
There has been no reason, aside from SYSRES, JES SPOOL
This poor practice was something instilled in the Tata contractors we have
employed.
We change one and another crops up...
We are looking to change of change control management software to capture...
Thankyou all...
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MA
23 matches
Mail list logo
