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


  1.  Home
  2. MIDRANGE-L
  3. August 2023

RE: External Re: Journal Receiver Creation Based On Time

Cybernetics.

I am still in the process of learning so I appreciate the guidance.

We are not a high transaction volume type of business so entries should be rather limited.
We are highly integrated with the network side and they have a restriction of the once an hour backup so trying to keep in sync as best I can with them.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, August 25, 2023 3:13 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: External Re: Journal Receiver Creation Based On Time

Before you get too far into this consider the recovery aspects of what you’re trying to do. Clearly the recovery point objective is one hour or less. The real question is in the event you need to restore some/all tables, how are you going to get all the roll forward to work? Roll back might be more interesting if the error is not found prior to the change in the receiver.

Consider using one journal per application, per day. You might have multiple journals that way. Less if the referential integrity between applications is a requirement.

With one journal / day, you can change the journal receiver during the back up (BRMS can do this almost automatically) and then the detached journal will be in the nightly back up. You can save the active journal receiver anytime you want but now you only need the one, so the dedupe/sendremote is smaller Than it would ordinarily be.

What kind of VTL?

--
Jim Oberholtzer
Agile Technology Architects




On Aug 25, 2023, at 3:03 PM, (WalzCraft) Jerry Forss <JForss@xxxxxxxxxxxxx> wrote:

Jim

I was thinking of that as well but thinking that the save to the VTL and replication to the cloud would send everything every time.
The de-dup process would see the receiver as being changed.

Once running I will have to see the bandwidth impact on the different methods.
The network side will be sending to the cloud as well.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jim Oberholtzer
Sent: Friday, August 25, 2023 10:20 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: External Re: Journal Receiver Creation Based On Time

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Creating a new journal every hour is going to make a rollback or recovery a far more interesting (read: difficult) feat.

You can back up active journals, why not just run your backup on an hourly basis? You'll be stacking back up on top of back ups, but hey it's only disk space.

Once the backup is complete, consider getting rid of the previous 24 hours of backups to save space on the VTL.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Fri, Aug 25, 2023 at 8:29 AM Marc Rauzier <marc.rauzier@xxxxxxxxx> wrote:

Le 25/08/2023 à 14:58, (WalzCraft) Jerry Forss a écrit :
Hi All

New to journaling so have some basic questions.

We are getting a VTL and want to save journals every hour, which
will be
replicated to the cloud.

Basically what I want to do is every hour create new receiver and
save
detached receiver to VTL.
I see where I need to have *USER on the Manage receivers but not
seeing
where I specify the length of time.

Do I just create a new receiver every hour and that automatically
detaches the previous one?

Yes, this is the way it works. You can generate a new receiver when
you want. You just have to handle yourself the delete after your backup.

Example:

CHGJRN JRN(DIMARCO2/JRN) JRNRCV(*GEN) Journal receiver JRN0000132
created in library DIMARCO2.
Journal receivers JRN0000131 and *N detached.
Sequence number not reset. First sequence number is 416.

CPF7020 information message contains the name of the detached receiver.
Therefore you can run something like RCVMSG MSGTYPE(*INFO) RMV(*NO)
MSGDTA(&MSGDTA), then substring &MSGDTA to find the receiver name
based on CPF7020 message description.



What is the best practice for accomplishing this?



Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change
specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and
privileged
information that is protected by law. The information contained
herein is transmitted for the sole use of the intended recipient(s) and should "only"
pertain to "WalzCraft" company matters. If you are not the intended
recipient or designated agent of the recipient of such information,
you are hereby notified that any use, dissemination, copying or
retention of this email or the information contained herein is
strictly prohibited and may subject you to penalties under federal
and/or state law. If you received this email in error, please notify
the sender immediately and permanently delete this email. Thank You

WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<http://www.walzcraft.com> Phone: 1-800-237-1326
--
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.




Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and
privileged information that is protected by law. The information
contained herein is transmitted for the sole use of the intended
recipient(s) and should "only" pertain to "WalzCraft" company matters.
If you are not the intended recipient or designated agent of the
recipient of such information, you are hereby notified that any use,
dissemination, copying or retention of this email or the information
contained herein is strictly prohibited and may subject you to
penalties under federal and/or state law. If you received this email
in error, please notify the sender immediately and permanently delete
this email. Thank You

WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<http://www.walzcraft.com> Phone: 1-800-237-1326
--
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.




Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and privileged information that is protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s) and should "only" pertain to "WalzCraft" company matters. If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this email or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this email in error, please notify the sender immediately and permanently delete this email. Thank You

WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<http://www.walzcraft.com> Phone: 1-800-237-1326

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.