Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Master Catalog Protection

28 views
Skip to first unread message

Alvaro Quintupray B.

unread,
Oct 5, 2006, 4:24:27 PM10/5/06
to
Hi.

I have protected the Master Catalog, but when a TSO user from menu (ISPF
3.4) tries to visualize a group of archives, it obtains the following
message.

MASTER.CATALOG.ZOS16 CL(DATASET ) VOL(NEXCAT)
WARNING: INSUFFICIENT AUTHORITY - TEMPORARY ACCESS ALLOWED
FROM MASTER.CATALOG.** (G)
ACCESS INTENT(ALTER ) ACCESS ALLOWED(READ )


This user ( TSO1 ) has a defined the alias TSO1 ASSOCIATIONS
whith USERCAT--CATALOG.PROD.TSOUSERS


are there temporary files ..?

what's going on ... ?

why I getting that message ...?

Thanks

Alvaro.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

McKown, John

unread,
Oct 5, 2006, 4:49:41 PM10/5/06
to
> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:IBM-...@BAMA.UA.EDU] On Behalf Of Alvaro Quintupray B.
> Sent: Thursday, October 05, 2006 3:24 PM
> To: IBM-...@BAMA.UA.EDU
> Subject: Master Catalog Protection
>
>
> Hi.
>
> I have protected the Master Catalog, but when a TSO user from
> menu (ISPF
> 3.4) tries to visualize a group of archives, it obtains the
> following
> message.
>
> MASTER.CATALOG.ZOS16 CL(DATASET ) VOL(NEXCAT)
> WARNING: INSUFFICIENT AUTHORITY - TEMPORARY ACCESS ALLOWED
> FROM MASTER.CATALOG.** (G)
> ACCESS INTENT(ALTER ) ACCESS ALLOWED(READ )
>
>
> This user ( TSO1 ) has a defined the alias TSO1 ASSOCIATIONS
> whith USERCAT--CATALOG.PROD.TSOUSERS
>
>
> are there temporary files ..?
>
> what's going on ... ?
>
> why I getting that message ...?
>
> Thanks
>
> Alvaro.

Your profile is in WARNING mode.

This is a "known problem" with WARNING mode on a dataset profile which
covers a catalog. The reason is that DFSMSdfp attempts various access
modes (even if not really required) and takes some different paths if
the access is allowed or not. That is, even if READ access is all that
is needed, DFSMSdfp will first attempt an ALTER. As an example, I think
this is because DFSMSdfp will allow a person to DELETE a dataset if they
have ALTER access to the catalog, even if they do not have ALTER access
to the dataset itself. I.e. ALTER acces to the catalog "trumps" lack of
ALTER access to the dataset.

This will "go away" when you take the profile out of WARNING mode. There
is no fix. This is a WAD (or BAD as the case may be).

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.

Mark Zelden

unread,
Oct 5, 2006, 4:50:54 PM10/5/06
to
On Thu, 5 Oct 2006 15:24:17 -0500, Alvaro Quintupray B.
<aquin...@NEXUSSA.CL> wrote:

>Hi.
>
>I have protected the Master Catalog, but when a TSO user from menu (ISPF
>3.4) tries to visualize a group of archives, it obtains the following
>message.
>
> MASTER.CATALOG.ZOS16 CL(DATASET ) VOL(NEXCAT)
> WARNING: INSUFFICIENT AUTHORITY - TEMPORARY ACCESS ALLOWED
> FROM MASTER.CATALOG.** (G)
> ACCESS INTENT(ALTER ) ACCESS ALLOWED(READ )
>
>
> This user ( TSO1 ) has a defined the alias TSO1 ASSOCIATIONS
>whith USERCAT--CATALOG.PROD.TSOUSERS
>
>
>are there temporary files ..?
>
>what's going on ... ?
>
>why I getting that message ...?
>

Because you have warning on and the way 3.4 works. Basically,
catalog management checks for alter first because that gives you
authority to display more (like catalog passwords). Not an issue
for ISPF 3.4, but it causes those "bogus" messages.

Bottom line: Turn of warning for catalogs.

BTW, the archives are your friend. I'm sure this has been covered
on more than one occasion.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group
mailto: mark....@zurichna.com
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

Alvaro Quintupray

unread,
Oct 5, 2006, 7:00:37 PM10/5/06
to
Great ..!! Monsters...!! Gurus..!!

The problem now not exists ..!!

Thank to John and Mark


Atte.
Alvaro Quintupray B.
Ingeniero de Sistemas
Nexus S.A. Chile
Fon : 420 8149
Fax : 420 8508

-----Mensaje original-----
De: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU] En nombre de
McKown, John
Enviado el: Jueves, 05 de Octubre de 2006 16:50
Para: IBM-...@BAMA.UA.EDU
Asunto: Re: Master Catalog Protection

0 new messages