MIDRANGE-L » February 2013

Re: cl compile severity level

Subject: Re: cl compile severity level
From: rob@xxxxxxxxx
Date: Wed, 20 Feb 2013 10:44:48 -0500
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>

Well, I recreated them. I enrolled them into BRMS, and the compile still
blows up. Apparently now BRMS wants to allocate the <expletive deleted>
device just to compile the program! This is REALLY getting carried away
with validity checking programs!

Rob Berendt

This thread ...

Re: cl compile severity level, (continued)
- Re: cl compile severity level, rob <=

References:
- cl compile severity level , rob

Prev by Author: Re: SSD Best practices
Next by Author: Overriding the defaults of a sql command.
Previous by thread: RE: cl compile severity level
Next by thread: Re: cl compile severity level
Index(es):

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact