RE: Danger! Danger! using IGNDECERR and FIXNBR

I would like to jump in and add a couple of cents here; (IMHO)

First, LVLCHK(*NO) - in "most" cases, I agree do not use, however; in a
small shop, short on staff, and long on work, this is a good solution for
adding (TO THE END *ONLY*) of a file a field or fields that are needed for
say 2-4 programs, but you know you have 100s accessing the file, and no time
or tools to really find all the programs; which brings up a great
tool(Hawkeye) to find and re-compile these for you.  But do not let a junior
programmer make the call on this, the IS manager will have to support you on
this, or you tell him that adding a field for this one program will be a six
month long project, his choice.... I like to pad.   ;)

As for RCLACTGRP ACTGRP(*ELIGIBLE); in a production environment - no.
However; as you are testing, recompiling, testing some more, the command
saves many gray hairs as it is possible to modify a program, compile it, yet
the old one stays in memory until the execution of the command RCLACTGRP;
So in conclusion, WHILE you are testing, USE the command first, re-try your
test, then if your results are not what you want, it is time to use debug.
I have seen many programmers going crazy because they "know" that the change
they just made is not executing, but they where still running an old copy of
the ILE program.





RCLACTGRP ACTGRP(*ELIGIBLE) sure jumps to mind.

Bruce

>
>Lets see
>IGNDECERR(*YES),
>LVLCHK(*NO),
>RCLRSC(*CALLER),
>CRTPF   A   CONTIG(*YES),
>Penny's in the fuse box,
>
>What other things are out there that we really shouldn't be using all that
>often.
>
>John
>





Mark A. Manske
[mailto:mmanske@minter-weisman.com]
Sr. Project Lead
Minter-Weisman

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