On 09-Jan-2014 13:15 -0800, Bakutis, Becky wrote:
The JOBD I originally looked at was tied to the user profile used
for ADDSVRAUTE which was qgpl/qdftjobd. Those settings were fine. The
JOBD mentioned in the document you sent a link for was qgpl/qdftsvr.
This JOBD on my system had the settings set as 4 0 *SECLVL with CL
Logging *YES. This has stopped a large number of spool files which
was my original concern.

Ah. Then merely as an FYI:

To determine the Job Description for the PreStart job requires reviewing the Prestart Job Entry information. For the job from the OP, that was a *N/QUSER/QRWTSRVR job. From a request to Display the Subsystem Description using DSPSBSD QUSRWRK, the option 10="Prestart job entries" and then 5="Display details" on the entry for program QRWTSRVR [library QSYS and user QUSER] would present the "Display Prestart Job Entry Detail" panel which includes the Job Description used to start that work. The Change Prestart Job Entry would enable customizing that JOBD and other settings, with regard to how those jobs start, reuse, and end. Note: such customizations should be added to the System Change Management tracking to ensure changes are re-applied as necessary [to prevent loss of the customization; e.g. per an upgrade to a new release]. Customizations may be desirable, because as with a change to the default /user/ job description (QDFTJOBD), the effects may be widespread, beyond what is desirable, such that changes need to be more specific to a particular subset of Work Management; e.g. the intent may be changing the effects only for QRWTSRVR, rather than every other server that also uses the default /server/ job description (QDFTSVR).

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].