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



Dave,

You are right on the mark.  By selecting user as a column, it matches
WRKACTJOB.  The Current User column is very handy for the QZDASOINIT jobs.
I can see the actual user vs. QUSER.

Thanks for responding.  That answers my questions.

Regards,

Mike Shaw

----- Original Message -----
From: "Dave Novey" <novey@us.ibm.com>
To: <mhshaw@worldnet.att.net>
Sent: Thursday, September 05, 2002 10:09 AM
Subject: Re: Difference Between What Ops Nav and WRKACTJOB Is Reporting


> Mike,
>
> You posted the following to the Midrange-L mailing list:
>
>    Message: 4
>    From: "Mike Shaw" <mhshaw@worldnet.att.net>
>    To: <midrange-l@midrange.com>
>    Subject: Differences Between What Ops Nav and WRKACTJOB Is Reporting
>    Date: Wed, 4 Sep 2002 11:10:02 -0700
>    Reply-To: midrange-l@midrange.com
>
>    Greetings All,
>
>    Had a strange experience yesterday in resolving some OneWorld issues.
>    If I
>    used WRKACTJOB to see the jobs running under the sbs JDEB7333 it told
me
>    that all active jobs in the subsystem were under the user id ONEWORLD.
>    When
>    in Ops Nav Active Subsystems, it would show me that there were several
>    different user ids for the active jobs, one of them being JDEOE which
>    were
>    causing the problems for us yesterday.  Ops Navigator is V5R1 with
>    Service
>    Pack SI02795 applied.
>
>    Has anyone else noticed this?  Any ideas as to what the difference is
>    and
>    why?
>
>    Regards,
>
>    Mike Shaw
>    iSeries Operations Manager
>    Kendall - Jackson Enterprises
>    Santa Rosa, CA
>
> The difference you are seeing might be caused by the fact that Ops Nav
> supports both a Current User column and a User column.  The Current User
> column shows the user profile that the job is currently running under,
> while the User column shows the user portion of a qualified job name,
which
> is the user profile the job started with.  The list of active jobs from
the
> active subsystems window shows the Current User by default, so you would
> have to modify the columns that are displayed in order to see the User
> column.  The WRKACTJOB display always shows the user portion of the
> qualified job name (which is the User column in Ops Nav).  As an example,
> suppose a job starts running under user ONEWORLD and then switches to run
> under JDEOE.  The WRKACTJOB display will show ONEWORLD in the User column
> and the User column of Ops Nav will show ONEWORLD, but the Current User
> column of Ops Nav will show JDEOE.
>
> We chose to make the Current User a default column rather than User
because
> this column shows the user profile that the job is currently doing work
as.
> This becomes more useful when dealing with server jobs that do work for
> multiple users.  They will usually start under a single profile, such as
> QUSER, and then switch to run under each profile that they are doing work
> for.
>
> If this answers your questions, could you please post this information to
> Midrange-L for me.  Thank you.
>
> Dave Novey
> OS/400 Work Management
> Rochester, MN
> Email: novey@us.ibm.com
>
>
>
>
>




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.