Re: QDFTSVR job description question.

As shipped by IBM, the QDFTSVR job description has LOG(4 00 *NOLIST), LOGCLPGM(*NO), and ENDSEV(30), and in general, the QDFTSVR job description should not be changed from these settings. The QDFTSVR job description settings were carefully selected by IBM for optimal system performance and health characteristics for prestart jobs. These settings allow for all messages to be logged to the job log while it is running; if the job ends with a severity of 30 or greater, the job log will be created. If the job ends normally, then no jog log is created.

It sounds like changing QDFTSVR back to the shipped settings is what you want to do.



When logging is turned on for a prestart job, a job log will be created every time a user profile swap occurs in one of those jobs.

I want to emphasize that point - a job log will be created every time a user profile swap occurs.

Since the database server prestart jobs can be reused up to 200 times, and database connections can be frequent, this can result in a very large number of job logs. In addition, the QDFTSVR job description is specified in several prestart job entries, so change the job description impacts all the prestart jobs that use that job description. I worked with a client that started hitting the maximum number of spooled files in the system ASP - which is 2.6 million - because of LOG(4 00 *NOLIST) on QDFTSVR. You do not want that to happen to you!


If you need logging enabled in order to do troubleshooting, you should not change the QDFTSVR job description. Rather, you should create a duplicate of it and change the settings you need to modify. Then, change the prestart job entry of ONLY the jobs you are troubleshooting to use the new job description. You can change the prestart job entry without ending the prestart jobs; if that is done, active prestart jobs at the time of the change continue to run with the job description used when the job was started. The new job description gets picked up as new prestart jobs are started over time. To have the job description change take effect immediately, end and restart the prestart jobs (END/STRPJ commands).

When logging is turned on for prestart jobs, you need to carefully watch the job logs on your system so ensure you don’t start to get near the limit of the maximum number of spooled files.

When you are done troubleshooting, you should change the prestart job entry back to use the QDFTSVR job description.


Dawn

On Feb 8, 2023, at 3:56 PM, K Crawford <kscx3ksc@xxxxxxxxx> wrote:

We have many QZDASOINIT and QRWTSRVR jobs by user QUSER using job
description QGPL/QDFTSVR. These create many many QPJOBLOG spool files each
day. Vary few of them have any true errors in them. I only want spool
files if something happens.
Would I be better off changing that job description or copying it and
changing the jobs/users to use the new one? Will be a lot easier to change
it. Being in QGPL I think it would be safe during our next upgrade.

I want a log if it fails but nothing if no errors.

It is currently set up like this.
Message logging:
Level . . . . . . . . . . . . . . . . . . . . : 4
Severity . . . . . . . . . . . . . . . . . . . : 0
Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL
Log CL program commands . . . . . . . . . . . . : *YES

Thinking of changing to this. Main reason I do get some level 40 saying
library already in library list.
Message logging:
Level . . . . . . . . . . . . . . . . . . . . : 4
Severity . . . . . . . . . . . . . . . . . . . : 41
Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL
Log CL program commands . . . . . . . . . . . . : *YES

Thanks
--
KCrawford
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.