|
Here is my joblog when I used SAVRSTOBJ to another system in my office:
Additional Message Information
Message ID . . . . . . : CPC3723
Date sent . . . . . . : 06/07/06 Time sent . . . . . . :
15:05:26
Message . . . . : 1 objects saved from library QUSRSYS; 0 objects not
included.
Cause . . . . . : 1 objects were saved from library QUSRSYS to save
file
OBCSAVF in library QTEMP at 06/07/06 15:05:07. 0 objects were not
included
in the save operation. The save is formatted for Version 5 Release 1
Modification 0. The objects were not included in the save operation
for the
following reasons:
Here is the target job's open files.
Job . . : xxxxxx User . . : QUSER Number . . . :
003870
Number of open data paths . . . . . . . . . . : 1
Member/ Record File I/O ----Open---
Relative
File Library Device Format Type Count Opt Shr-Nbr
Record
OBCSAVF QTEMP SAV 0 I NO
looks like save files to me.
_____________________________
Bryan Dietz
Aktion Associates
midrange-l-bounces@xxxxxxxxxxxx wrote on 06/07/2006 12:09:48 PM:
-> Bryan Dietz wrote:
-> > Using the SAVRST command is going to accomplish(if you could get
-> working intra-system) the same thing as the save file method
->
-> not quite, actually SAVRST saves to a queue and restores from that
queue
-> while the save operation is still ongoing. this makes sence when you've
-> 2 machines (= 2 sets of disks) because the overall time is shorter.
->
->
-> R.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.