RE: Library attribute TEST or PROD -- MIDRANGE-L

× 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.

Subject: RE: Library attribute TEST or PROD
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Thu, 30 Apr 2009 16:14:24 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : jeudi 30 avril 2009 15:43
À : Midrange Systems Technical Discussion
Objet : RE: Library attribute TEST or PROD

Has the value *PROD any other use than protection in mode debug?

Not that I see.

So where's the harm in changing the program libraries from TEST to PROD? After all, they ARE production libraries.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Library attribute TEST or PROD , Jim Essinger

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.