Saving and restoring D3 accounts from win to linux

[Rick Weiser]

Hi all,

I need to save 3 accounts (pseudo floppy) from a D3 windows server and restore them on a D3 linux server (both v10.2x).  Are there and special switches I need when saving or restoring?

Thanks,

Rick

[Scott Ballinger]

Hi Rick,

The "(a" option creates saves that are compatible with pre v7.0 versions of D3, and the "(c" option creates R83 compatible saves (not sure this is still supported). Since you are dealing with current releases on both ends the documented compatibility switches don't apply.

The current docs do state that Incremental saves won't work on FSI accounts, so as long as you have "full" file saves on the Windows server you should be OK.

/Scott Ballinger

Pareto Corporation

Edmonds WA USA

206 713 6006 cell

[Rick Weiser]

I just tried to load a file save tape from a D3 windows server onto Linux and when doing the account-restore, it tried to load the account into the FSI and gives me errors:

1  > SX 0,101

'SX'  is not a file name

1  > SX > TEMP 0,7

'TEMP'  is not a file name

1  > SX > TEMP > TEMP 0,111

'TEMP'  is not a file name

1  > SX > SALE.ITEM.TEMP 0,13

'SALE.ITEM.TEMP'  is not a file name

1  > SX > SALE.ITEM.TEMP > SALE.ITEM.TEMP 0,313

'SALE.ITEM.TEMP'  is not a file name

When I look at the system file for this account:

001 QS

002 FSI:SX

D3 Linux does not use FSI, right?  How do I restore this account onto Linux that is in the FSI on windows?

[Tony Gravagno]

The account must be saved in the non-FSI format with the A option as Scott noted.
An account cannot be saved to Linux if it was saved without the A option.

[Rick Weiser]

The a option worked.  FYI, Scott noted that these switches were not needed in current releases.

Thanks,

Rick

[Tony Gravagno]

I saw Scott's note. There are two concepts here. The first is cross-release compatibility. The second is cross-platform compatibility. The D3 Windows FSI is not based on traditional frame allocation from overflow. The pointers are different from the D3 Linux VME. As you've seen, the MDS pointers in the FSI are "remote" Q-pointers into the underlying OS file system. The Linux VME still uses standard D-pointers. I believe the A switch is/was required for saving v7 to v9+, and/or v9+ to v7. That's where in this case the switch is "not needed", since you're at v10 on both sides. But the A switch is still required for operations cross-platform.

Side note: the C option isn't just to support R83 and thus D3 to other MV platforms. The C option forces conformity with R83 where item sizes were 32k, indexes didn't exist, frame sizes were 512bytes (for mod/sep calculation), and other nuances.

Best,
T