Re: *SQLPKG object maintenance -- MIDRANGE-L

Subject: Re: *SQLPKG object maintenance
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Thu, 05 Jan 2012 12:09:43 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 05-Jan-2012 05:52 , Mike Cunningham wrote:

We have an *SQLPKG object that has reached its maximum size <<SNIP>>

Not knowing any details of the failure... some search kwds FWiW:
SQL0904 RC7
QAQQINI option SQL_INCREASE_PKG_LIMIT
msgSQL0904

For the last, as the "symptom string keyword" for the resource limit condition encountered [i.e. described as "maximum size"], seems the RC# [Return Code or Reason Code standard symptom string keyword form] is [incorrectly] referred to by numerous\inconsistent variations like "type #" "rctype#" "type#" "type/#" [or perhaps omitted completely] on the IBM service\support pages.

Some "recent" APAR\PTF text include a "type 7" resource limit.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

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.