Re: Another evil of LVLCHK(*NO)

[Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx]

so missing data is better than corrupt data?  a hard error is a hard 
error...better to keep LVLCHK on and ensure that your programs, etc are 
recompiled to use the changed file than to poke and hope it works...JMO.

add a monitor block or error extender on the write/update opcodes and what 
happens?  no error just the old-fashioned "where the heck is my data" 
problem.  bad practice is bad practice, flawed design is flawed design. 
but i guess i'm just very biased on the subject 8^)


Thanks,
Tommy Holden



From:
rob@xxxxxxxxx
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
09/23/2009 08:51 AM
Subject:
Re: Another evil of LVLCHK(*NO)
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Try defining that file with DDL instead of DDS.  Compile your program. Use 

DDL to add a column at the end that is numeric.  Then see what happens...
> CHGPF FILE(ROB/LVL1) LVLCHK(*NO) 
  File LVL1 in library ROB changed. 
> call lvl1 
  Data mapping error on member LVL1. 
  Data mapping error on member LVL1. 
? C 
  Cancel reply received for message CPF5029. 
  1 records lost when member LVL1 closed. 
  Error message CPF4572 appeared during CLOSE. 
  Function check. RNX1217 unmonitored by LVL1 at statement 0000000009,
    instruction X'0000'. 
  Error message CPF4572 appeared during CLOSE (C G D F). 
  Error message CPF4572 appeared during CLOSE (C G D F). 

Rob Berendt