Edward Gould wrote:
>At the time we were a medium to large DC in Chicago. If memory serves me 8
>sysprog types having said that we also had very low turnover (1 or 2 in the 10
>years I was there). One of my varied duties was creating TSO id’s . None
>(maybe 2 others) of the others (except the s
> On Dec 14, 2016, at 5:59 PM, John Eells wrote:
>
> Password protection of catalogs has not been supported for some time now.
> The current AMS book says:
>
> "Passwords are no longer honored for protecting a catalog, or data sets
> contained in a catalog. If they are specified, they will be
> On Dec 14, 2016, at 1:13 PM, Elardus Engelbrecht
> wrote:
>
> Warning! Edward and I am now hijacking this thread to discuss something very
> odd/fishy... ;-D
>
> :-D *-D ;-D
>
> Edward Gould wrote:
>
>> Thirty + years ago (pre-RACF) we put update password on the mastercats.
>> Worked l
On Wed, 14 Dec 2016 18:59:22 -0500, John Eells wrote:
>
>"Passwords are no longer honored for protecting a catalog, or data sets
>contained in a catalog. If they are specified, they will be ignored and
>no message will be issued. Previously, passwords were ignored only for
>SMS-managed data sets.
Password protection of catalogs has not been supported for some time
now. The current AMS book says:
"Passwords are no longer honored for protecting a catalog, or data sets
contained in a catalog. If they are specified, they will be ignored and
no message will be issued. Previously, password
> On Dec 14, 2016, at 9:05 AM, Edward Gould wrote:
>
> Thirty + years ago (pre-RACF) we put update password on the mastercats.
> Worked like a charm for us.
>
> Ed
>> On Dec 14, 2016, at 1:16 AM, Elardus Engelbrecht
>> wrote:
>>
>> Jesse Robinson wrote:
>>
>>> And once you have all protectio
Warning! Edward and I am now hijacking this thread to discuss something very
odd/fishy... ;-D
:-D *-D ;-D
Edward Gould wrote:
>Thirty + years ago (pre-RACF) we put update password on the mastercats.
>Worked like a charm for us.
Passwords? Hmmm, my very first boss (now dead) used that, but
Thirty + years ago (pre-RACF) we put update password on the mastercats.
Worked like a charm for us.
Ed
> On Dec 14, 2016, at 1:16 AM, Elardus Engelbrecht
> wrote:
>
> Jesse Robinson wrote:
>
>> And once you have all protections in place, remember that someone has to
>> have the key to master
Jesse Robinson wrote:
>And once you have all protections in place, remember that someone has to have
>the key to master catalog. Whoever that is--including you--may occasionally
>get caught by a missing alias. At every shop I've worked in, userids are
>defined and managed by a non-sysprog depar
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Way, Richard
Sent: Tuesday, December 13, 2016 10:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Prevent allocation of unknown-HLQ data sets?
Realize this is a pretty basic question, but my Google-fu isn't working out
today Can someone te
bject: (External):Re: Prevent allocation of unknown-HLQ data sets?
Way, Richard wrote:
>Realize this is a pretty basic question, but my Google-fu isn't working out
>today Can someone tell me the most common / easiest way to prevent
>allocating a data set that doesn't have
Way, Richard wrote:
>Realize this is a pretty basic question, but my Google-fu isn't working out
>today Can someone tell me the most common / easiest way to prevent
>allocating a data set that doesn't have a catalog alias defined yet? We're
>hitting situations where someone creates a data s
Protect the master catalog
Sent from my iPhone
> On Dec 13, 2016, at 1:57 PM, Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
>> On Tue, 13 Dec 2016 18:55:21 +, Way, Richard wrote:
>>
>> Realize this is a pretty basic question, but my Google-fu isn't working out
2:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Prevent allocation of unknown-HLQ data sets?
Realize this is a pretty basic question, but my Google-fu isn't working out
today Can someone tell me the most common / easiest way to prevent
allocating a data set that doesn't have a catal
Your Welcome, I have those moments more now...
Carmen
- Original Message -
From: "Richard Way"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, December 13, 2016 1:07:29 PM
Subject: Re: Prevent allocation of unknown-HLQ data sets?
D'oh Thanks!!!
Rich Way
-O
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Carmen Vitullo
Sent: Tuesday, December 13, 2016 1:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Prevent allocation of unknown-HLQ data sets?
What I've done in 2 shops was to protect the master cata
D'oh Thanks!!!
Rich Way
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Carmen Vitullo
Sent: Tuesday, December 13, 2016 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Prevent allocation of unknown-HLQ data sets?
What
: Prevent allocation of unknown-HLQ data sets?
Realize this is a pretty basic question, but my Google-fu isn't working out
today Can someone tell me the most common / easiest way to prevent
allocating a data set that doesn't have a catalog alias defined yet? We're
hitting situ
On Tue, 13 Dec 2016 18:55:21 +, Way, Richard wrote:
>Realize this is a pretty basic question, but my Google-fu isn't working out
>today Can someone tell me the most common / easiest way to prevent
>allocating a data set that doesn't have a catalog alias defined yet? We're
>hitting situa
Realize this is a pretty basic question, but my Google-fu isn't working out
today Can someone tell me the most common / easiest way to prevent
allocating a data set that doesn't have a catalog alias defined yet? We're
hitting situations where someone creates a data set by the HLQ of "TEST",
20 matches
Mail list logo
