RE: Model 40S DASD -- 6502 IOP & *SAVFs for V4R5

Wayne,

I might as well use your item to respond to since you responded to mine.

So, thanks to the others who responded -- looks like I can find a DASD growth 
path with minimal trouble.

As for savefiles...

There are at least two separate general issues. First, the internal structure 
that describes what was saved and how it will restore -- this is very 
version/release-dependent. It's where TGTRLS() becomes important when saving 
objects. And second, the *FILE object itself -- a savefile is, after all, a 
*FILE object with an attribute of SAVF.

I generally use SNADS to send savefiles around here in our network. I range 
from V4R4 to V5R3 nowadays and can't recall having problems. That is, the 
savefiles themselves go where I want them to go without corruption; and as long 
as the receiving system is at a level that supports the saved objects, restores 
have always worked. I often store them on intermediate systems where they 
cannot restore. Sending them later to an appropriate system allows restores to 
work.

I've had similar success with FTP. I've FTP'd V5R2 savefiles to V4R4 systems, 
then sent them via SNADS to V5R2 and they restore fine.

A fundamental point is that the SAVF *FILE object itself always gets created 
according to the VRM of the receiving system no matter if it's FTP or SNA. The 
data that then gets written into that SAVF *FILE by the transfer is the same 
series of bytes that was saved (assuming binary transfer and related stuff). 
So, in my understanding, it's only when a RSTxxx command is run that the data 
inside gets interpreted. Intermediate storage is mostly irrelevant.

Just don't expect to restore objects saved for V5R2 onto a V5R1 or earlier 
system. (But if a proper TGTRLS() was specified and matches the target, all 
should be well.)

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   7. RE: SAVF from V5R3 to V4R5 (Wayne McAlpine)
>
>Thanks to all who replied.  I've run a test by creating a SAVF on the 
>V4R5 system and FTP'ing the SAVF from the V5R3 system.  It appears to 
>have completed successfully.  I'm going to do it with a dummy library 
>and files to be sure that I can go in the opposite direction and do a 
>restore back to the V5R3 system.  If that doesn't work, I'll pursue the 
>IFS solution.
>
>------------------------------
>
>message: 8
>date: Mon, 28 Mar 2005 16:58:20 -0600
>subject: Re: Model 40S DASD -- 6502 IOP
>
>I'm starting to do something similar (see my recent post about save file 
>version compatibility).  My V4R5 box is a 9402-40S with the expansion 
>unit.  The two original drives are 2 gb drives.  The remaining two 
>drives in the system unit and the eight drives in the expansion box are 
>all 4 gb drives.  The combination storage controller in the system unit 
>is a 918B and the controller for the expansion unit is a 6530.  The 
>entire system is mirrored.  If I recall, the 6502 is the RAID controller 
>  and the 6530 is not.  But the point is that the 4 gb drives are 
>supported, and possibly 8 gb as well.

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com


__________________________________________________________________
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp