|
I believe backups can now save spool files to tape just like otherfiles.
from
From:
Alan Shore <AlanShore@xxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
10/19/2009 12:52 PM
Subject:
Replicating spool files from one AS/400 to another
Sent by:
<midrange-l-bounces@xxxxxxxxxxxx>
Hi everyone
Due to a system crash, we are now working off our DR system and we are
looking to go back to using the production system this weekend.
Its been many winters have passed since I last replicated spool files
one AS/400 to anotherleast
The procedure that I last used was as follows (with thanks to Tim
Granatir,
Search400.com expert):-
On AS/400 that contains the spool file:
Step 1. Create a physical file that is at
1JOB
character bigger than the size of the spool
file
you wish to replicate.
Step 2. Copy the spool file into your
database
file. Make sure you specify *FCFC for the
control
character parameter.
Step 3. Transfer this database file to
your
target AS/400 using whatever method you
choose
(FTP, File Transfer, etc.).
On AS/400 that you wish to print:
Step 4. Override print file to specify
control
character *FCFC.
Step 5. Copy your database file to the
spool
file.
Your print file is now duplicated on your
target
AS/400.
Example Commands:
CRTPF FILE(MYLIB/FILE133) RCDLEN(133)
CPYSPLF FILE(MYSPLF) TOFILE(MYLIB/FILE133)
(123456/*N/QPADEV0032) CTLCHAR(*FCFC)list
Transfer FILE133 in library MYLIB to your
target
AS/400
OVRPRTF FILE(QSYSPRT) CTLCHAR(*FCFC)
CPYF FROMFILE(MYLIB/FILE133) TOFILE(QSYSPRT)
However, we may have a LARGE number of these spoolf files to migrate
We are presently on V5r4.
Is there a simpler and/or more automated method to achieve this?
Or do I have to cut and paste the spool file attributes (Job, User,
Number,
File and Number) of each and every spool file that needs to be migrated
Thanks in advance
Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.