×
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.
There isn't (to my knowledge) a means of prefixing a file name with the
system name like you can with the VAX, but you can create a DDM file on one
box that points to a remote file on another box.
For example, if you have FILEA in LIBA on SYS1 you could have a library, say
DDMLIB2 with a file FILEA in pointing to the remote file on SYS2. You would
create the DDM file using the CRTDDMF command:
There are third party packages, such as DataMirror and Vision that will
replicate data on the fly to secondary systems as part of a high
availability process. I believe they achieve this using a combination of
database journals and data queues between the systems to identify the
changed data and to transfer and apply it.
All the best
Jonathan
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wenzloff
Sent: 22 August 2007 13:53
To: midrange-l@xxxxxxxxxxxx
Subject: Multi-computer techniques
I'm sure those of you who work with multiple systems will find this
question elementary but I have worked on a single AS400 for 17 years and
never had to think about another system.
Soon we will be getting two new machines and will have to keep files
consistent between them.
So if I update a file on SYS1 what is a good technique to get SYS2
updated?
I know I could use FTP but that seems archaic. In the late 1980s I
worked on VAX systems and we simply prefixed a file name with the system
name and the operating system took care of the details. Like copy
SYS1::LIB/FILE to SYS2::LIB/FILE.
Is there anything like that on our beloved computer?
Thanks,
Greg
As an Amazon Associate we earn from qualifying purchases.
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.