× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hey all,

I've got a question

I've written an app, that kind of mixes OPM style calls with ILE style
calls, and i ran into something that I don't quite understand.

given the following schenario: (all programs are RPGIV - all override
commands are done using callPs to QCMDEXC, in the rpg programs)

call programA  - dftactgrp(*NO) actgrp(*YES)
  ovrdbf file1 tofile(lib1/file1)
  open file1
  close file1
  dltovr file1
  call programb  - dftactgrp(*NO) actgrp(*CALLER)
    ovrdbf file1 tofile(lib1/file1)
    open file1
    close file1
    dltovr file1
    seton lr
    return
  call programc  - - dftactgrp(*NO) actgrp(*CALLER)
    ovrdbf file1 tofile(lib1/file1)
    open file1
    close file1
    seton lr
    return
  cpyf lib1/file1 lib2/file1 mbropt(*add)

notice, programC doesn't delete the override.
I stepped through this in debug, and when I got to the cpyf statement at
the end, it bombed with 'from and to file/member cannot be the same'.

this would indicate that the override is still in effect from when programc
was called, which i guess is caused by it being in the same activation
group (*caller).  Right?  so, even though I seton LR and ended that call
level, the override remained in effect.

but why is it, if just before the cpyf command, I do a shift/sysrequest/3
and display active overrides, none are listed?

Thanks,

Rick



As an Amazon Associate we earn from qualifying purchases.

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.