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



If the chain is broken (highly likely in this case) then you need to specify the receiver as Gavin has suggested.
Thats why you are not seeing the data in the receiver using defaults.


--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


------ Original Message ------
From tgarvey@xxxxxxxxxx
To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Date 10/11/2024 9:19:13 AM
Subject RE: Restoring Journal Receivers

Yes

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Thomas Burrows
Sent: Thursday, October 10, 2024 8:47 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Restoring Journal Receivers

Is the reason you need the RECEIVERS because you have missing data in the files???

On Thu, Oct 10, 2024 at 2:24 PM Gavin Inman <midrangelist@xxxxxxxxxxxxxx>
wrote:

IF they are not in the chain. . (i.e. break in the sequence), you will
need to specify the receiver range and not use *CURCHAIN.


On 10/9/2024 2:29 PM, tgarvey@xxxxxxxxxx wrote:

Hi,

We have some journal receivers that filled up and were detached from
their journal. They were saved to tape and now restored back into
their original library.

Now, when they get restored to the same original library and journal,
they do not seem to be included in the receiver chain of that journal.
When I do a Work With Receiver Directory I can see them. But, when I
start a RCVJRNE command using the *CURCHAIN value for the Range of
receivers to use, I don't get anything from those non-attached
receivers.



Do I misunderstand how this works?



Kind Regards,



Thomas Garvey




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.