QZDASOINIT logs

[Guest.Visitor]

If they're ending with "completed normally", then you may need to change the job description they use, QSYS/QZBSJOBD. Its message logging may be set so that it produces a joblog no matter what. Ours is set to LOG(4 00 *NOLIST) LOGCLPGM(*NO) It's also used by most/all prestart jobs in sbs QUSRWRK, so changing it would affect them also. To isolate it to the QZDASOINIT jobs, you'd need to create a new jobd with the logging you want, and change subsystem attributes so QZDASOINIT would use the new jobd.

[Guest.Visitor]

Hi, That jobd already has those settings.

[Guest.Visitor]

if the job is an ODBC connection, check the ODBC setup. On the diagnostic tab is a checkbox for "print joblog at disconnect".

[Guest.Visitor]

Hi, does anyone know of a way to STOP these from being produced? we have an application that creates literally thousands of these daily - and they all reside in QEZJOBLOG. It makes finding real failing jobs difficult and is a nuisance! Thanks Carl

[Guest.Visitor]

Verify the jobd they using when executing. On our sys they run under userid QUSER which uses the QDFTJOBD jobd. It is set to *seclvl which basically means write me a joblog. As others have said, set to *nolist to avoid joblog at normal end.