Re: RPGIV: RE: IGNDECERR info

[Barbara Morris <bmorris@xxxxxxxxxx>]

Bob cozzi wrote:
> 
> Thanks to everyone who replied.
> 
> We do have the debug method and were looking for a way to check the
> thousands of OPM RPGIII programs for the INGDECERR(*YES) attribute before
> moving some of them to RPGIV.
> Thanks again.
> 

Bob, when you do ADDBKP, you can add a breakpoint handling program -
BKPPGM parameter.  In that program, you could do a DSPPGMVAR
OUTPUT(*PRINT).

Since the breakpoint handling program can't stop the program from
continuing (at least I don't think it can), maybe the best way to handle
this would be to set a breakpoint on line '/1' of all the programs and
have the breakpoint handler update a database and remove the breakpoint
when it got called.  Then keep running the applications until enough of
the programs have got called that it's a small problem to do the rest by
hand.  (Hmm, if I recall correctly, there's a limit to how many programs
can be in the debugger at once, so the program would have gradually set
breakpoints on sets of programs until it got them all.)

Something like this, untested, (although I did something like this
once):

    read file
    do while not eof 
         and num-in-debugger not too many for the debugger to handle
      if not &haveinfo
        addpgm &pgmname
        addbkp pgm(&pgmname) bkppgm(handler)
        add 1 to num-in-debugger
      endif
      read file
    enddo

handler: 
    chain &pgmname file
    dsppgmvar ZIGNDECD output(*print)
    read the print file and set &ignerr
    set &haveinfo
    update file
    rmvbkp '/1' &pgmname