On 3/3/11 9:32 AM, Willie J. Moore wrote:
I have the following CL that is ran when I sign on. It is in the
'Initial program to call' on the user profile.

MONMSG MSGID(CPF2103)
CHGJOB LOG(4 0 *SECLVL) LOGCLPGM(*YES)
CALL PGM(WJMWORK/CLKSIGNINCL)
ADDLIBLE LIB(ALSOURCE) POSITION(*LAST)
ADDLIBLE LIB(AMFLIB) POSITION(*LAST)
ADDLIBLE LIB(FEUPRO) POSITION(*LAST)
ADDLIBLE LIB(TAATOOL) POSITION(*LAST)
ADDLIBLE LIB(AFDWWWOBJ) POSITION(*LAST)

CLKSIGNINCL:
OVRDBF FILE(EMPMAS) TOFILE(AMFLIB/EMPMAS)
OVRDBF FILE(ZZUSER2) TOFILE(AMTLIB/ZZUSER2) +
FRCRATIO(1)
CALL PGM(WJMWORK/CLKLUNCH)

Then this runs at sign-in time the libraries are added and the call
program is called, but the job does not update the sign-in file. 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.

Of course a review of the TRCJOB activated before and after the CALL in the InlPgm could assist in debug, as well as actual debug [though acknowledging possibility that difficulties that might exist to effect the latter, and modifying the source may not be desirable in the former]. However a trace can be activated against a job that is not yet started, without any change to the source of the InlPgm, by naming *all/UserName/DevDspName for the JOB() parameter of STRTRC, knowing what UserName will be used to signon at the display device they have awaiting at the sign-on; ENDTRC to stop the trace and generate the output, IIRC optionally spooled.

Regards, Chuck

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.