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



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/09/2017
11:40:56 AM:
These match between the IBM supplied one and my QROB one.

Object . . . . . . . : QWEBQRYJQ Owner . . . . . . . : QSYS
Library . . . . . : QWEBQRY Primary group . . . : *NONE
Object type . . . . : *JOBQ ASP device . . . . . : *SYSBAS

Object secured by authorization list . . . . . . . . . . . . : *NONE

Object
User Group Authority
*PUBLIC *USE
QSYS *ALL
QSPL *CHANGE


WRKJOBQD
Status:
Subsystem active . . . . . . . . . . : *NO
Subsystem name if active . . . . . . :
Job queue held . . . . . . . . . . . : *NO
Operator controlled . . . . . . . . . : *YES
Authority to check . . . . . . . . . . : *OWNER

OK, then what is really interesting about the jobs that don't show
up is that they are such special jobs that they were submitted with CALL
and the program name prefixed by QSYS. I've never seen that before --
though I know that is a method some use to prevent interference by
site-created tools/objects.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.