Anyone else seen this?


______________________________ Forward Header __________________________________
Subject: Level Check on DDM file 
Author:  <MIDRANGE-L@midrange.com> at INET_WACO
Date:    11/5/99 8:45 AM


     
     In testing yesterday, I noticed that a DDM file that I was accessing 
     should have caused my app to blow up, as the remote object had a 
     different format level ID than the file the program was compiled with. 
     
     The DDM object was defined LVLCHK *RMTFILE and the remote file was 
     LVLCHK *YES. The program was compiled against a new version of the 
     file that included a new field at the end of the record format. I'm at 
     a loss to say why the system did not detect the level check and report 
     the error. 
     
     Local machine (dev) is 170 @ V4R3. Remote machine (prod) is 510 @ 
     V4R3. Anyone else ever see this type of behavior for DDM files?
     
     eric.delong@pmsi-services.com
     
     
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. 
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner/operator: david@midrange.com 
+---
     


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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-2019 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].