Re: Stranded journal receiver: QRECOVERY/QSQJRN0001 from V6R1M0 install -- MIDRANGE-L

Hi Paul

Sounds more like the recovery message/advice in the in house monitor
is incorrect. Checking the source for the program that traps the error
might give you a clue as to what error condition the program monitor
is trying to identify - there might even be some program comments that
shed light on whatever was being monitored for.

What's the creation date and time of the troublesome receiver and is
there a good reason for not just deleting ?

I don't really like the fact that the receivers for a system journal
are in library QRECOVERY - I think I'd want to do something about
that, even if it was only forcing a journal change to get the
receivers into a more correct library. Where do these receivers live
on the other systems ?

regards
Evan Harris

On Mon, May 31, 2010 at 4:02 PM, PaultinNZ <paultormey@xxxxxxxxx> wrote:

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