Re: Joblogs for jobs in jobq: Not sure this is the right group, but if not I am sure Mr Gibbs will point me to the right one.

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 04/18/2017 08:17:35
AM:

----- Message from Danny Hayes <Danny_Hayes@xxxxxxxxx> on Tue, 18
Apr 2017 12:17:18 +0000 -----

To:

"RPG programming on the IBM i (AS/400 and iSeries)"

<rpg400-l@xxxxxxxxxxxx>

Subject:

RE: Joblogs for jobs in jobq: Not sure this is the right group, but
if not I am sure Mr Gibbs will point me to the right one.

Rob,

I tried this:
Tue Apr 18 08:13:54 EDT 2017 ] Run All... SELECT X.JOB_NAME FROM
TABLE(QSYS2.JOB_INFO(JOB_STATUS_FILTER => '*JOBQ', JOB_USER_FILTER
=> '*ALL')) X WHERE JOB_QUEUE_LIBRARY = 'QGPL' AND JOB_QUEUE_NAME =
'RPMOTMULT2'
SQL State: 42704 Vendor Code: -204 Message: [SQL0204] JOB_INFO in
QSYS2 type *N not found. Cause . . . . . : JOB_INFO in QSYS2 type
*N was not found. If the member name is *ALL, the table is not
partitioned. If this is an ALTER TABLE statement and the type is *N,
a constraint or partition was not found. If this is not an ALTER
TABLE statement and the type is *N, a function, procedure, trigger
or sequence object was not found. If a function was not found,
JOB_INFO is the service program that contains the function. The
function will not be found unless the external name and usage name
match exactly. Examine the job log for a message that gives more
details on which function name is being searched for and the name
that did not match. Recovery . . . : Change the name and try the
request again. If the object is a node group, ensure that the DB2
Multisystem product is installed on your system and create a
nodegroup with the CRTNODGRP CL command. If an external function was
not found, be sure that the case of the EXTERNAL NAME on the CREATE
FUNCTION statement exactly matches the case of the name exported by
the service program. Processing ended because the highlighted
statement did not complete successfully Failed statements: 1

If you're on 7.1 you're out of luck. The UDTF JOB_INFO() was introduced in
7.2 Group PTF level 14 and 7.3 Group PTF level 3. Your error would be
consistent with the results on a 7.1 system.

Michael Quigley
Computer Services
The Way International
www.TheWay.org