× 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.



As a guess, instead of debugging, either *CALLLVL or *JOB should work if the origin of the problem is from using [the default of] OVRSCOPE(*ACTGRPDFN) on the OVRDBF. Overriding with a job scope might be excessive, and likely a DLTOVR LVL(*JOB) request would then be desired or required after the CALL completes.

Perhaps instead of debug why the invocation does not work at signon, perhaps debug why the program *does work* when called "outside" the signon. Determine for example, what "outside" means with regard to the ACTGRP() of the program from which the CALL is being made. Review the DSPOVR and WRKJOB OPTION(*FILOVR), correlating to the active program on WRKJOB OPTION(*PGMSTK) and its activation group.

Regards, Chuck

On 3/3/11 11:17 AM, Willie J. Moore wrote:
What would you suggest the change to OVRSCOPE be?
Never have used this and after eading the help, not sure how.

CRPence on Thursday, March 03, 2011 10:24 AM wrote:

On 3/3/11 9:32 AM, Willie J. Moore wrote:
<<SNIP>> If I call this CL outside of the user profile sign-in
it updates the file. Does anyone have any ideals why this is not
updating the file from the 'Initial program to call'?


My first guess is always the missing [thus defaulted value for the]
OVRSCOPE parameter of the OVRDBF command.

<<SNIP alluding to using trace [or debug]>>



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.