Thanks for the information. I am going to install the PTF's, change it to
70% and create a watch session with a simple program to call to clear
qezjoblog outq and see how that goes.

On Tue, Dec 25, 2012 at 11:38 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 24 Dec 2012 18:27, Jack Kingsley wrote:
I found some hits on this with PTFs for 6.1 and 5.4, is this
standard on 7.1 where you can create the new threshold value
via the data area QMAXJOBPCT. <<SNIP>>

The function provided by that data area provides nothing more than an
override to the percentage at which the message is first issued and the
effect of continued warning for the condition. Prior to that feature
addition, the percentage was notified at the hard-coded value of 90%,
notified "each time the job tables are extended after 90% of the maximum
has been reached". With the request to CRTDTAARA
DTAARA(QSYS/QMAXJOBPCT) TYPE(*DEC) LEN(2 0) VALUE(70) AUT(*EXCLUDE) the
notification could begin instead at 70%, or similarly using CHGDTAARA
DTAARA(QSYS/QMAXJOBPCT) VALUE(80) [if the data area already exists] to
cause notification to begin at 80%... after activation, either by a
PwrDwn\IPL or issuing CHGSYSVAL QMAXJOB [¿to effect a modified value;
i.e. presumably, other than *SAME?].

When a feature is implemented via a *DTAARA [or similar means in a
disconnected or non-integrated fashion], introduced as a PTF to an
existing release, the general [and mostly safe] assumption is that the
feature will continue to function unchanged until such time that a
replacement feature has been provided via an /integrated/ function,
perhaps as an API, command, and\or menu interfaces [perhaps a system
value, modifiable via such interface(s)]. The replacement would be
expected to be documented in the Memo to Users (MTU) and include the
Data Area name as a token such that a search on the token QMAXJOBPCT
within that document would enable anyone to locate the information about
the replacement. Similarly a web search on that token should assist to
verify [in an MTU or elsewhere]; e.g.:

_i IBM i Job Structures i_ January 11, 2011
http://ibmsystemsmag.blogs.com/i_can/2011/01/ibm-i-job-structures.html
"... the capability to customize the percentage at which this message
<ed: CPF1468> is sent. PTFs for 5.4 (SI29585) and 6.1 (SI30171) provide
this support (no PTFs are needed for 7.1 as this support is part of the
operating system). You create a data area named QMAXJOBPCT in QSYS to
control the percentage at which you want the warning message to be sent.
See the PTF cover letters or the redpaper..."

IBM APAR doc reference#: 862573FC004200BD
_i SE31539 - OSP-MSGCPI1468 EARLY WARNING FOR JOB TABLE FULL i_

http://www.ibm.com/support/docview.wss?uid=nas21ed39e77adc12946862573fc004200bd

_i Best Practices for Managing IBM i Jobs and Output i_
http://www.redbooks.ibm.com/redpapers/pdfs/redp4454.pdf

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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