Alan,
I had heard that one could save spool files beginning with V5R4 but, since I've never used it, it didn't occur to me. My needs, so far, have always been porting a listing from dev (which has no attached printers) to production so I just do one-at-a-time stuff. For larger volumes, like you have, the save/restore route does make better sense.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Monday, October 19, 2009 2:02 PM
To: Midrange Systems Technical Discussion
Subject: RE: Replicating spool files from one AS/400 to another
Thanks for your reply Jerry
I just found out that you can save spoolfiles in the following manner SAVOBJ OBJ(outqname) LIB(libname) DEV(*SAVF) SAVF(library/savefile) SPLFDT
(*ALL)
ftp'ing the save file to the other system and then use the command RSTOBJ OBJ(outqname) LIB(libname) DEV(*SAVF) SAVF(library/savefile) SPLFDTA (*NEW )
will ADD the spool files into the outq
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
Jerry Adams
<Jerry@bwwholesal
e.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
10/19/2009 02:56 Subject
PM RE: Replicating spool files from
one AS/400 to another
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Alan,
Have you tried to SNDTCPSPLF command? You would probably want to front-end it with an API (don't know which one off the top of my head) in order to get the spool file, etc., for the parameters. I use JWSPLF command, but can't remember where I got it.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Monday, October 19, 2009 12:48 PM
To: Midrange Systems Technical Discussion
Subject: Replicating spool files from one AS/400 to another
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 from one AS/400 to another 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 least 1
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) JOB
(123456/*N/QPADEV0032) CTLCHAR(*FCFC)
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 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.
midrange.com
