RE: Prevent creation of a logical over a physical

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

And DSPDBR gives you a list of the files that are dependent on a file, so
you could run that against each file in the main library. To an outfile.

I had thought you would need to run it against logicals, if they are
SQLtype VIEW, since views can be built over views, not just tables. But it
turns out that views over views get listed under the final base physical.

BTW, views can be created over views but not over normal logical files.

Regards

Vern

At 11:20 PM 12/13/02 -0600, you wrote:
> At 18:12 12/13/2002, Walden H Leverich wrote:
> > Here's the bigger issue, the physicals we're concerned with are in a test
> > environment. The programmers need access to the environment to review test
> > data when there is a problem. However, they have a (nasty) habit of building
> > logicals in their private library over the physical in the test library, so
> > when we go to clear that lib to refresh from production we have to find all
> > the cross-library logicals and delete them first. We were hoping for a
> > simple authority-fix to prevent them from creating the logical.
> I don't remember exactly, but I used to run a query over outfiles created
> by a combination of dspfd and dspobjd in order to get a list of files that
> had dependents in other libraries. It shouldn't be too difficult to figure
> out. I'd think a combination of that and gentle persuasion (with a big
> nasty stick) should, at least, make the problem manageable.
>
>
> Pete Hall
> pbhall@ameritech.net
> http://www.pbhall.us/