Creating a library with a *test vs. *prod parameters
Specifies the type of library being created.
*PROD
This is a production library. Database files in production libraries cannot be opened for updating if a user is in debug mode and he requested that production libraries be protected. A user can protect all database files in production libraries by specifying UPDPROD(*NO) on the Start Debug (STRDBG) command to begin testing. However, this protection does not prevent the program from deleting database files or from changing other objects (such as data areas) in the library.
*TEST
This is a test library. All objects in a test library can be updated during testing, even if special protection is requested for production libraries.
I use BRMS/400 software for our backup and recovery processes. One of the special values BRMS will look at when processing libraries for backup is the library *TYPE. What I've done is set all my "development" libraries as *TEST libraries and my production libraries as *PROD. I've also instructed our developers to create all their development libraries as type *TEST. This allows me to create a very simple BRMS control group for backing up ALL the development libraries on the system!
It doesn't get much simpler than this. The following statement instructs BRMS to backup my entire development environment:
Auxiliary Weekly Retain Save SWA Backup List Storage Activity Object While Message Seq Items Type Pool Device SMTWTFS Detail Active Queue 10 *ALLTEST *SYSBAS *DFTACT *YES *NO==================================
MORE INFORMATION ON THIS TOPIC
==================================The Best Web Links: tips, tutorials and more.
Ask your OS/400 questions -- or help out your peers by answering them -- in our live OS/400 discussion forums.
Ask the Experts yourself: Our OS/400 gurus are waiting to answer your questions.
Check out this Search400.com Featured Topic: 20 ways to ensure a smooth OS upgrade