I do this regularly.  When you do the DSPJRN you need to make sure you
specify the beginning and ending receiver and that they do not go over a
break in the chain.  You can't just do *CURCHAIN or *CURRENT and get
these because there is a break in the chain due to the receivers being

                                Attach                        Save      
Receiver    Library     Number  Date      Status              Date      
COJRCV0305  RCVLIB      00001   06/30/03  SAVED               07/01/03
this is not part of the current chain
but your can DSPJRN on it.
COJRCV1446  JRNLIB      01001   03/04/04  SAVED               03/11/04  
COJRCV1447  JRNLIB      01002   03/05/04  SAVED               03/11/04  
COJRCV1448  JRNLIB      01003   03/08/04  SAVED               03/11/04  
COJRCV1449  JRNLIB      01004   03/09/04  SAVED               03/12/04  
COJRCV1450  JRNLIB      01005   03/12/04  ATTACHED            03/12/04  

---------original message 
date: Mon, 15 Mar 2004 17:23:36 +0000
from: "Mike savino" <mikejsavino@xxxxxxxxxxx>
subject: Restoring Journal Receivers

First, Thanks for everyones suggestions about the Format Id Question.  I
some usefull ideas.

But I've got another one....  I'm trying to restore my Production
and Recievers to a Development machine to run a performance test.
they restore fine, I'm having a problem with the Receiver Chain.  It
that it's broken and I can't figure out how to fix it.  Thought I
the directions in the manual but after the first few failed attempts I
have done more harm than good.  Has anyone out there done this?  And if
did following the instructions in the Backup/Recovery Guide work?  Any

Marty Winkler
517-546-5400 ext 1387

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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