×
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.
What would you suggest the change to OVRSCOPE be?
Never have used this and after eading the help, not sure how.
William Moore
California Fine Wire
805-489-5144
wjmoore@xxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, March 03, 2011 10:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Program not updating file from User Profile sign-in.
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.