× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IIRC, a Save File has a record length of 528. It can be read by a program on the i5-- we have a pair of programs that reads a save file on one system and re-creates it (as a save file) on another. Save something on one system, send, and restore on the other. Faster than SNDNETF because our command doesn't have all that nasty error checking that IBM's commands have!

If you really wanted to, I suppose you could use CPYF and copy from tape to disk (but I think you'd have to create the SAVF on disk by hand before you started).

Speaking of how a save file works-- I've always thought that a SAVF was written using the same interfaces that tape files use-- that's why there's a SAVFWAIT state during save/restore to a save file. But that lets you specify device type *SAVF instead of *TAPE, and use all of the same functions that you can with tape. And IBM didn't have to re-write any save/restore programs, just make a SAVF pretend it was a tape device!.

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.