MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » May 2014

Re: why does DSPOVR show overrides that DSPJOB does not?



fixed

Steve,
I believe that it *is* an activation group issue.
I have seen this same effect when running jobs with programs in activation
groups.
Ex. Job A runs pgm P using activation group XXX. pgm P calls pgm R. Pgm R
uses activation group *CALLER (this uses activation group XXX) and issues
an OVRDBF command. The default scope of the OVRDBF is *ACTGRPDFN which
limits it to the current activation. When you use the DSPJOB command, you
are in the activation group for the JOB which is the DEFAULT ACTIVATION
group. Your override in in activation group XXX, so you do not see it.
It would be nice if IBM gave us the option to specify the activation group
for the display override in the DSP/WRKJOB command, but they have not done
it yet, so I doubt that they will.

Jeff Young
Sr. Programmer Analyst


On Fri, May 16, 2014 at 1:03 PM, Steve Richter via MIDRANGE-L <
midrange-l@xxxxxxxxxxxx> wrote:

Gary,

I posted the code I was running. Pretty basic. I call qcmdexc to run the
OVRDBF command. The call qcmdexc to DSPJOB and the DSPOVR. DSPOVR shows the
override and DSPJOB does not.

I don't think it is an activation group thing because the OVR exists.
DSPOVR sees it. I ask because I was running some code that was not
working. I was questing if the DSPOVR was working or not, then ran DSPJOB
to display the override and it did not display. So then I spent time
looking for why an override did not exist when it actually did exist.




On Fri, May 16, 2014 at 12:21 PM, Gary Thompson via MIDRANGE-L <
midrange-l@xxxxxxxxxxxx> wrote:

Hmm,
You write: " The thing is when the override is OVRSCOPE(*JOB) then DSJOB
will display the override."
And: "I think it has to do with the call level ..."
You lost me there.
I don't have details about your job and program(s) [OPM vs ILE] so I'm
not
sure how
activation group issues apply, but your first statement seems relevant,
no?
I think an activation group can be seen as "a job within a job", so
program A in
activation group AG_A can have FILE1 over-ridden to FILE_A, and program B
in activation group AG_B can have FILE1 over-ridden to FILE_B; both
running in Job_1.
Further, any override with OVRSCOPE(*JOB) "breaks" activation group
"walls" and
applies to programs running in any/all activation groups within that job.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steve Richter via MIDRANGE-L
Sent: Friday, May 16, 2014 9:42 AM
To: Midrange Systems Technical Discussion
Subject: Re: why does DSPOVR show overrides that DSPJOB does not?

The thing is when the override is OVRSCOPE(*JOB) then DSJOB will display
the override.

I think it has to do with the call level of the job. On the DSPJOB
option(*FILOVR) there is a "Call level" display field. But I do not see
a "call level" parm to the DSPJOB command.



On Fri, May 16, 2014 at 11:31 AM, Gary Thompson via MIDRANGE-L <
midrange-l@xxxxxxxxxxxx> wrote:

Total guess:
in the debugger you are "in the debug program activation group"
(different from "from the same job") and the over-ride in question is
not for *job, but another AG ?


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steve Richter via MIDRANGE-L
Sent: Friday, May 16, 2014 9:23 AM
To: Midrange Systems Technical Discussion
Subject: why does DSPOVR show overrides that DSPJOB does not?

When I run OVRDBF from an RPG program, halt the pgm in the debugger
and then run DSPJOB ( from the same job ) the override is not visible.
But when I run DSPOVR I see the override. What is the difference?

thanks,


h option(*srcstmt)

** ------------------------- dshtest4b ----------------------------
ddshtest4b pr extpgm('DSHTEST4B')

** ---------------------- pr_qcmdexc ---------------------------------
dpr_qcmdexc pr extpgm('QCMDEXC')
d InCmds 9999a const options(*VarSize)
d InCmdsLx 15p 5 const

** -------------------------- dshtest4b ----------------------------
ddshtest4b pi

d cmds s 256a varying
d ch80 s 80a
d dec155 s 15p 5

/free
cmds = 'ovrdbf dsmast2 tofile(dtalib09/dsmast2) ' ;
pr_qcmdexc( cmds: %len(cmds)) ;

cmds = 'dspovr ' ;
pr_qcmdexc( cmds: %len(cmds)) ;

cmds = 'dspjob option(*filovr)' ;
pr_qcmdexc( cmds: %len(cmds)) ;

*inlr = '1' ;
return ;
--
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.

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


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

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


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







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact