RE: Library explicit references in programs (Was Re: OVRDBF problem ...)

Hi Darrell,

Well I would say that any program that is specifically designed to delete *ALL 
of something or other must be very strictly controlled, as to when/who 
can/where from it can be run, so it can also be designed to use the correct 
library list and not explicitly hard coded libraries. However bad practice, 
like many things, is not strictly black and white, so those little grey areas 
are there for the piece of mind of many a computer professional. :-)

Steve

-----Oorspronkelijk bericht-----
Van: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]Namens Darrell A Martin
Verzonden: donderdag 13 juli 2006 15:20
Aan: Midrange Systems Technical Discussion
Onderwerp: Library explicit references in programs (Was Re: OVRDBF
problem ...)


Hi, Steve:

Whether it is bad practice to explicitly refer to a library in a program 
depends on context.

In our setup, it is very important that library lists are honored. That is 
almost always how we differentiate among three environments:  production, 
development, and automated "versions" of usually interactive processes. 
Often, the calling CL does an OVRDBF to *LIBL/filename SECURE(*YES) just 
to make sure. (I don't think that's bulletproof, but you get the point.)

On the other hand, we have programs that are designed to affect data ONLY 
in one of the three environments -- usually data used in development, for 
example, "delete all product testing transactions." These programs have to 
identify the data by library explicitly, or they are disasters waiting to 
happen.

Darrell

Darrell A. Martin  -  754-2187
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx

Steve Raby wrote on 07/13/2006 01:09:23 AM:

Yeah has the IT manager that said that actually any experience with 
iSeries? Does he know what one is? 

Actually, I have always thought it bad practice to explicitly refer 
to a library in a program, but maybe thats just me.

This e-mail, including attachments, may contain information that is 
confidential and/or proprietary, and may only be used by the person to 
whom this email is addressed. If the recipient of this e-mail is not the 
intended recipient or an authorized agent, the reader is hereby notified 
that any dissemination, distribution, or copying of this e-mail is 
prohibited. If this e-mail has been delivered to you in error, please 
notify the sender by replying to this message and deleting this e-mail 
immediately.