On Sat, Jul 12, 2014 at 8:23 AM, CRPence wrote:
> On 11-Jul-2014 14:22 -0500, John McKee wrote:
<<SNIP>> Is there a process that is supposed to be run to detach
these receivers, or is that just done manually?
Each journal environment for which those [system] receivers are
established, should include the Manage Receivers (MNGRCV) setting
of *SYSTEM and the Delete Receivers (DLTRCV) setting of *YES; refer
to the Work With Journal Attributes for the *JRN associated with
each of the noted\named Journal Receiver (*JRNRCV) objects. Thus
there should be only one journal receiver object that is
active\attached per journal object. The maximum size of the journal
receiver before deletion will be determined by the Receiver Size
Options of the journal and the Threshold attribute of the journal
receiver; see the Display Journal Receiver Attributes (DSPJRNA) for
the threshold and the associated Journal object.
With the default journal environment, the request to Change Journal
(CHGJRN) to request attaching a new generated-name or an explicitly
named journal receiver will enable reducing the current storage for
a[n at least partially] full receiver to the storage of an empty
receiver. For example, the request to CHGJRN QSYS2/QSQJRN
JRNRCV(*GEN) would effect a new empty receiver with the next
receiver name and the previously attached receiver would be
detached and deleted.
I presented insufficient information. I thought the question was so
common that details would have been tedious.
Attach date: 07/12/06
Size (K): 286884
No detach or save date.
Manage receivers: *SYSTEM
Delete receivers: *YES
What drew my attention was that the journal receiver was 0001.
Something is odd. Is there a system value that is potentially wrong?
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact