× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I was excited to use V6R1's STRJRNLIB command--it's really helped us get
all files added to the production environment journaled as we want.

I am wondering if there is any way to use STRJRNLIB or QDFTJRN to prevent
journaled objects being restored or copied to test environments to not be
journaled. We refresh our Integrated Test and QA environments from
production on a scheduled basis. While it's easy enough to add ENDJRNOBJ
*ALLLIB to those restoration routines, it's much harder to find all the
instances where programmers have restored a file into another environment.
We tend to forget to take off the journaling in those instances.

I tried creating an OMIT rule for all objects on my own library, but this
does not prevent the restored object (in a new library) from being
journaled to the original file's journal. Is there a way to do this?






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.