After some help off list from Mark Waterbury (thanks Mark!) I set up a
command exit program for QIBM_QCA_RTV_COMMAND. I have it sending messages
to me when PRTSQLINF is run.

The messages I'm getting are like this:

PRTSQLINF run from user QUSER from job QSQSRVR/171549. The command
executed is: PRTSQLINF OBJ(*JOB).


The joblog for the above referenced job shows this:

Additional Message Information



Message ID . . . . . . : CPF9898

Date sent . . . . . . : 10/28/21 Time sent . . . . . . :
15:05:53


Message . . . . : SERVER MODE CONNECTING JOB IS
963939/QLWISVR/QNAVMNSRV.


Cause . . . . . : This message is used by application programs as a
general
escape message.


And if I go to job 963939/QLWISVR/QNAVMNSRV and view the joblog I see this:

Additional Message Information



Message ID . . . . . . : SQL7908

Date sent . . . . . . : 10/28/21 Time sent . . . . . . :
15:05:53


Message . . . . : Job 171549/QUSER/QSQSRVR used for SQL server mode

processing.



Cause . . . . . : A Structured Query Language (SQL) statement was
executed
while running in SQL server mode. SQL statements for this connection or

thread will be processed in job 171549/QUSER/QSQSRVR.

Technical description . . . . . . . . : SQL server mode was requested by

either setting the SQL server mode job attribute, or by setting the
server
mode environment attribute via the SQL Call Level Interface. When
running
in this mode, SQL statements are processed by a separate job, which runs

under the user profile specified for the connection. The thread
identifier
is 2 and the connection is to Relational Database DILGARD. If the

Relational Database name is *N, this means that all connections for the

thread will use the same job.

So - QNAVMNSRV is, I think, the new Navigator. Is it possible IBM stuck a
PRTSQLINF in there somewhere for troubleshooting and did not remove it
before a PTF release?

Yea, I'm guessing wildly here.


On Wed, Oct 13, 2021 at 4:10 PM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

All,

V7R3

Since applying the latest cume and all groups last Friday, we've been
getting 30-50 pages daily of "Print SQL Information" spool file pages
printing daily. Each is either 1 or 2 pages in length and happen all hours
of the day and night. No job number info in the printed pages.

Any idea what is creating these? Anyone else seeing this?

Thanks.


--


*Jeff Crosby*
Senior Vice President
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.




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