transfer library from AS400

[frenk]

I have an old as400 with V5R2M0 with 92% of 70gb used and I have to transfer a 20gb library on another as400.
The tape is not compatible and with V5R2M0 I cannot use the image catalog and virtual device(the second as400 is configured as NFS server and in the first as400 I have mounted an exported directory from the server)...
can anyone help me
Thanks

[Peter Zich]

In article <a177971c-84b0-44ae...@googlegroups.com>,
fren...@hotmail.com says...

If you have a ftp-connection, you can do it this way:

CRTSAVF FILE(QGPL/yyy) (on both AS/400 !)
SAVLIB LIB(xxx) DEV(*SAVF) SAVF(QGPL/yyy) DTACPR(*YES) (on the old
AS/400)
FTP new-AS/400 (from the old one)
LCD QGPL
CD QGPL
B
PUT yyy

RSTLIB SAVLIB(xxx) DEV(*SAVF) SAVF(yyy) (on the new AS/400)


Don?t forget to delete the Save-Files !

Good luck !

-- Peter

[frenk]

I can not act in this way:
the savf of library exceeds the capacity of the disk

[CRPence]

The necessary save activity likely could be achieved to the disk,
with some planning. First, there is likely some amount of reclaimable
storage that could be recovered from the system before trying to effect
any large saves to save files; submit a request to RTVDSKINF, and after
the completion review variations of the PRTDSKINF reporting. There may
be evidence that a RCLSTG SELECT(*ALL) might assist, or if QRPLOBJ,
QRCL, or QSYS [for QHST* files] might have objects that can be dealt
with A request to RCLSTG SELECT(*DBXREF) might also reclaim some
storage; review the DSPFD QSYS/QADB* TYPE(*MBR) FILEATR(*PF) for
row\storage statistics. Second, the *LIB object is merely a container
of other object types; i.e. SAVLIB is optional, and dividing the save
activity into groups of objects by type and generic names with SAVOBJ
can limit the size of any one save file. At the cost of CPU upon
restore, the ACCPTH(*NO) will prevent saving the logical file keyed
access paths, thus reducing the storage for the saved data. Also...

SAVRSTLIB might be able to accomplish the activity, but likely only
after some good cleanup. Similar to division of the save\restore
activity with SAVOBJ, the SAVRSTOBJ can similarly group objects by type
and generic name to limit the storage requirements. These tools require
installing the option for ObjectConnect and the underlying
communications definitions.

How to best handle the situation with the least impacts to the source
and target systems, if significant storage can not be reclaimed,
requires a closer examination of the library mostly for its database
files for relations and sizes.

--
Regards, Chuck

[ga]

Chuck is correct, you could save parts of the library and move the
sub-parts individually using ftp as was suggested.

Another thought, back up some other libraries to your tape and remove
them from the disk temporarily so that you do have enough space to do
create the savf, ftp them across, then restore the libraries you saved
off to tape to create room. I'd make two copies though, just to be
safe!

I know I rented an external tape drive that could be attached (not
sure what model you have of an as/400 or whether that is an option)
but I was able to rent an external drive and save libraries off to a
tape that was compatible with newer iseries. Again, you might have
some limitations with your old OS...

I don't know what model as/400 you have but is there any option to add
dasd to it?? Lots of cheap stuff out there if you could do that...

ga
nos...@nospam.fmctc.com

[xyzzy]

Assuming both AS400s are on the same network, could you not configure a SNADS connection between both systems and simply copy files and objects across using DDMF. It's a technique I've used in the past to transfer files from a V4R2 system to one at V6R1. It wasn't the quickest approach, but it worked.

[CRPence]

SNA/DS is unrelated to DDM Files; that reply seems to muddle the two
distinct features.? DDM can not copy /objects/ only data; e.g. data of
database source-members and data-members can be copied with the Copy
File (CPYF), whereas a "display file" can not be transported via DDM for
lack of an object-copy vs data-copy utility. The CRTFILE(*YES) of the
CPYF could be argued as offering support for an effective /copy/ of a
database file object, but very primitive, and unlikely to effect a
desirable outcome as compared with saves, minimally, per the lack of
capability to /copy/ logical file definitions; i.e. as a data-copy
feature, the utility would create a like-definition physical file into
which the data would be copied, instead of creating the like-definition
logical file at the target. The SNA Distribution Services can be used,
as could FTP, to transport objects [and data] that was previously saved
to a save file; however in my experience, abutting a storage threshold
is more cumbersome to deal with for SNA/DS than for FTP, because the
SNA/DS effectively requires two copies of the data at both the source
[sending] and target [receiving]. Copying save-file records over DDM is
possible, but the OS-provided CPYF utility offers no support; i.e. a
program would need to move the data, if DDM were utilized. Given the OP
indicates that a NFS setup is already available, does not that imply
that the two systems can be considered to be "on the same network" via
TCP/IP.? FWiW, the DDM has long been available directly over TCP/IP.
However, SNA over TCP/IP is available only via either of the AnyNet or
the Enterprise Extenders. The ObjectConnect feature referred-to in my
prior reply, requires a SNA configuration.

--
Regards, Chuck

[Obelix]

Last time i had a similar problem, i just wrote a quick CLLE that list
object into a file and then do a SAVRSTOBJ() by single object.

Not fast, but requires a minimal space.

[CRPence]

On 08 Oct 2013 08:01, Obelix wrote:
> Il 03/10/2013 15:08, frenk ha scritto:
>> I have an old as400 with V5R2M0 with 92% of 70gb used and I have
>> to transfer a 20gb library on another as400.
>> The tape is not compatible and with V5R2M0 I cannot use the image
>> catalog and virtual device(the second as400 is configured as NFS
>> server and in the first as400 I have mounted an exported directory
>> from the server)...
>> can anyone help me
>

> Last time I had a similar problem, I just wrote a quick CLLE that

> list object into a file and then do a SAVRSTOBJ() by single object.
>
> Not fast, but requires a minimal space.

Consider... when doing that... Database relations, and access paths,
become a potential issue. The former can be resolved by ordering the
save\restore activity, the latter can not, because all relations need to
be saved in the same save request and [effectively also restored on the
same] restore request to avoid the cost of rebuilding the access paths
on the target system. Thus why I had added the earlier comment that

"How to best handle the situation with the least impacts to the source

and target systems" would require "a closer examination of the library
mostly for its database files for relations and sizes." The deferral of
access path processing to the target requires potentially very
significant CPU there [and if not ordered saves and restores, possibly
much greater storage at the target than the source, per less sharing
than the database save\restore would effect if the DB network were saved
and restore each on one request].

--
Regards, Chuck