Re: Level Check

["Jim Franz" <franz400@xxxxxxxxxxxx>]

have had similar problems, mostly related to CHGPF changes, where file does
not
get a new create date, but programmer added/changed fields in source.
jim
----- Original Message ----- 
From: <rick.baird@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, March 17, 2004 3:56 PM
Subject: RE: Level Check


>
> If the files are identical in fields and attributes, regardless of how or
> when they were created, you will NOT recieve a level check.  are the files
> different?
>
> speaking of weird level checks though, last week, I had a program bomb
with
> a level check.  The program had not been changed or compiled in several
> months (but had been run many times) and the file that caused the level
> check had not been changed in longer than that - it's a file from an
> outside vendor accounting package, so we would have no reason to change
it.
>
> yet, the level check did occur.  I didn't do any research on what might
> have caused it for I was out of the office when it occured and I
instructed
> the operator to recompile.  everything was hunky dorey afterwards.
>
> has that happened to anyone else?
>
> Rick
>
> ------original message----
> I agree that it is wrong.  I am pretty sure that IBM did not misunderstand
> me.  He said definitely a program compiled over testdata will not look at
> the proddata file for a level check AND since I was running it over
> proddata, the program would not even check the file over which it was
> compiled.
>
> But I am here to tell you ... it happened. I did not get a level check and
> I can reproduce it.
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>