|
> Chris wrote: > Look at system values: > qjobmsgqfl - full > qjobmsgqmx - max size > qjobmsgqsz - initial size > qjobmsgqtl - max initial size > > The first being what you want to change to *wrap or *prtwrap Job logs can > be very large so be careful with the prtwrap option. You might also want to review the logging levels that are being used for the interactive users. This is set by either the JOBD associated with the user profile or by the CHGJOB command. Unless there is some special reason (like programs bombing), it is usually satisfactory for normal users' logging level to be set as LOG(2 00 *NOLIST) LOGCLPGM(*NO) to minimize the number of entries created in the job log. HOWEVER, this logging level inhibits the ability to press F9 and retrieve previously executed commands from a command line. A developer or a power user that has command line authority would probably need to be left at a logging level level of 3 or higher to be able to retrieve previous commands. Also, developers may want their logging as LOG(4 00 *SECLVL) LOGCLPGM(*YES) for times when they are debugging programs and need to see the low-level messages that get sent to the job log. HTH Steve Landess Austin, Texas (512) 423-0935
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.