Re: Jobs don't show in Qinter

Thank you for the reply.

Comments below...
On 1 Aug 2010 at 10:32, Simon (Simon Coulter <midrange-l@xxxxxxxxxxxx>) commented
about Re: Jobs don't show in Qinter:

On 01/08/2010, at 8:58 AM, Gary Kuznitz wrote:

Interactive jobs aren't showing up in Qinter on the Wrkactjob display.

I had a system crash last night. I ran RCLSTG.
I can start a Client Access job. It does start. I get a signon
screen.

What subsystem name is shown on the sign-on screen?

Qintr is showing

The jobs are showing in QCTL or any other subsystem.

What do you mean by this? Are they showing in QCTL or another
subsystem or are they NOT showing up at all?

I'm sorry. That was supposed to read:
The jobs are NOT showing in QCTL or any other subsystem.

Does pressing F14 make a
difference to the list of displayed jobs?

It makes a difference but the display jobs still don't show up anyplace.

Does pressing F16 make a
difference to the list of displayed jobs?

It makes a difference but the display jobs still don't show up anyplace.

Does pressing F20 and
setting *SBS *ALL *NONE *NONE *ALL make a difference?

It makes a difference but the display jobs still don't show up anyplace.

I have never seen that screen before. Very interesting.

Before the crash all interactive jobs showed in Qinter.
If I run DSPSBSD Qinter, option 4
Nothing is there
in option 5 I have:
*CONS
*All

The workstation type (or name) entries are less important than the
detail in those entries. Specifically whether the workstation is
allocated at *SIGNON or *ENTER.

By default all workstation entries will likely be *SIGNON which means
the last subsystem to start will allocate all the matching and
available devices.

Ideally, you would change the allocation to *ENTER (or remove the WSE)
for all devices you don't want allocated by a given subsystem. For
example QCTL should get *CONS at *SIGNON but *ALL at *ENTER. QINTER
should get *CONS at *ENTER but *ALL at *SIGNON.

Does anyone have any idea why the jobs wouldn't show in qinter?

Because they're not running in QINTER. Not meant to be facetious.
WRKACTJOB is most likely showing the jobs correctly thus the problem
is likely with device allocation.

Perhaps your subsystems did not start in the order you expect?

Perhaps you're not running the instance of QINTER you expect (i.e.,
QSYS vs. QGPL vs. some other copy)?

Perhaps QCTL was delayed (i.e., took longer to start than usual) and
thus grabbed the devices from QINTER before anyone signed on?

Perhaps you have a damaged object that is causing this effect (i.e.,
jobs start but cannot be found). Does the QINTER job log show any
error messages? Does the job log of the job in which you run WRKACTJOB
show any related error messages?


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------

Thank you,

Gary