× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Chuck,
The WRKJRNRCV QRECOVERY/QSQJRN0001 and display attributes shows:
Display Journal Receiver
Attributes


Receiver . . . . . . . : QSQJRN0001 Library . . . . . . . :
QRECOVERY


Journal . . . . . . . : *NONE Library . . . . . . .
:
Threshold (K) . . . . : 100000 Size (K) . . . . . . . :
28
Attach date . . . . . : 00/00/00 Attach time . . . . . :
00:00:00
Detach date . . . . . : 00/00/00 Detach time . . . . . :
00:00:00
Save date . . . . . . : 00/00/00 Save time . . . . . . :
00:00:00
Text . . . . . . . . . :
*BLANK


Auxiliary storage pool . . . . . . . . . . . . . . :
1
*Status . . . . . . . . . . . . . . . . . . . . . . : EMPTY
*

Number of entries . . . . . . . . . . . . . . . . . :
0
Minimized fixed length . . . . . . . . . . . . . . :
YES
Receiver maximums option . . . . . . . . . . . . . :
*NONE
Maximum entry specific data length . . . . . . . . :
0
Maximum null value indicators . . . . . . . . . . . :
0
First sequence number . . . . . . . . . . . . . . . :
0
Last sequence number . . . . . . . . . . . . . . . :
0
Fixed length data . . . . . . . . . . . . . . . . . :
Job name . . . . . . . . . . . . . . . . . . . . : NO
User name . . . . . . . . . . . . . . . . . . . . : NO
Program name . . . . . . . . . . . . . . . . . . : NO
Program library name . . . . . . . . . . . . . . : NO
System sequence number . . . . . . . . . . . . . : NO
Remote address . . . . . . . . . . . . . . . . . : NO
Thread identifier . . . . . . . . . . . . . . . . : NO
Logical unit of work identifier . . . . . . . . . : NO
Transaction identifier . . . . . . . . . . . . . : NO
Pending transactions . . . . . . . . . . . . . . . : NO
Minimize entry data . . . . . . . . . . . . . . . . : *NONE
Remote journal type . . . . . . . . . . . . . . . . : *NONE
Local journal . . . . . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . . . . . . . . :
ASP group . . . . . . . . . . . . . . . . . . . . :
System . . . . . . . . . . . . . . . . . . . . . :
Local journal receiver library . . . . . . . . . . : *NONE
Source journal . . . . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . . . . . . . . :
ASP group . . . . . . . . . . . . . . . . . . . . :
System . . . . . . . . . . . . . . . . . . . . . :
Source journal receiver library . . . . . . . . . . : *NONE
Redirected receiver library . . . . . . . . . . . . : *NONE

As far as I can see from the above, not much important has been set on the
receiver.

"WRKJRNA JRN(QSYS2/QSQJRN)" shows the current Receiver as QSQRRN0248 in Lib
QRECOVERY.

As mentioned an inhouse monitor had picked up the state of the journal and
issued the following warning:
AS/400 system id: S6575D1C has a *stale *journal receiver:
QRECOVERY/QSQJRN0001
This could stop system journaling from working!
Please contact AS/400 support person with these details.

The QSQJRN0001 was created in the middle of systems installation.
Created by user . . . . . . . . . . : QLPINSTALL
I also see the following:
Journaling information:
Currently journaled . . . . . . . . : NO

So the question is, "Do I need to worry about this receive journal?"

Maybe I'll place a call with IBM?

Cheers
Paul



On 28 May 2010 17:43, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 27-May-2010 22:18, PaultinNZ wrote:

We upgraded our i5 to V6R1M0 on Saturday and Sunday 15/16 May.
After the install we see that we have a ‘stranded/stale’ journal
receiver QSQJRN0001 in library QRECOVERY.

DSPOBJD *FULL detail:
Object . : QSQJRN0001 Attribute . . . :
Library . . . . . : QRECOVERY Owner . : QSYS
Library ASP device: *SYSBAS Library ASP group: *SYSBAS
Type : *JRNRCV Primary group . . . : *NONE
User-defined information:
Attribute . . . . . . . . :
Text . . . . . . :
Creation information:
Creation date/time . : 15/05/10 19:06:04
Created by user . . : QLPINSTALL
System created on . : S6575D1C
Object domain . . . : *SYSTEM

Does anyone have any idea why this is hanging around and can we
safely delete it?


From what was the conclusion drawn, that the journal receiver is
"stranded\stale"? If you are mistakenly looking at library
QRECOVERY thinking you are looking at library QRCL, see:
http://archive.midrange.com/midrange-l/200803/msg01307.html

FWiW, the DSPOBJD is not a proper interface to review the status
of a journal receiver; i.e. for possible relationship to an active
journal object. Use instead: WRKJRNRCV QRECOVERY/QSQJRN0001

The Work with Journal Receiver will presumably will show the
receiver is active to the journal QSYS2/QSQJRN; WRKJRNA QSYS2/QSQJRN
then F17=Receiver-Chain should show the receiver in QRECOVERY. The
library QRECOVERY is used for that journal receiver object because
that library is never backed up; reconfigure the journal environment
to associate the journal to a receiver in another library, if
desired to have the receiver for QSYS2/QSQJRN to be part of regular
backup activity.

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 ...

Follow-Ups:
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.