Re: Library attribute TEST or PROD

2009/4/30 David FOXWELL <David.FOXWELL@xxxxxxxxx>:

Hi,

I wanted to run some SQL on a table of libraries that I generated. Basically, our libraries contain either data files or compiled objects.

Eg for an application you might see a library calle APPLI containing source files and program objects, etc and there'd be the library APPLIF containing database files specific to that application.

I see that all libraries containing the programs have the attribute TEST and those containing the data PROD. Then there are temporary developer's libraries that are PROD or TEST.

I'd like to be able to change all the program libraries to PROD, and the development libraries to TEST.

Anyone know of a reason why I couldn't or shouldn't do that, and why would the program libraries be of type TEST in the first place?

Hi David

The main difference that I'm aware of is when using debug: if
UPDPROD(*NO) is specified then files in PROD libraries can't be opened
for update. I find that handy when setting up parallel environments to
make sure I'm not picking up any live files by mistake. I don't think
it makes any difference to programs - just the database files.

Regards, Martin