× 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.



On Mon, 31 Dec 2001, Jay 'Eraserhead' Felice wrote:
> >
> > What you REALLY want to know is what command was used to populate the save
> > file, and what format that command writes data in.   If the save file was
> > created using the SAVLIB command or SAVOBJ command, then you'll want to
> > know the format of data created with those commands.  And that format is
> > release-specific, and AFIAK undocumented.
>
> How can it be release specific if people are posting save files for Open
> Source AS/400 stuff on the web?  Maybe it's backwards compatible, with new
> releases having new features that are ignored by older versions, but that's
> fine with me--tar is like that.
>

Because you specify a target release when you do the save.  Something
like:
   SAVLIB LIB(OPNSRC) DEV(*SAVF) SAVF(QGPL/MYSAVF) TGTRLS(V3R2M0)

You save it to the earliest target release that your code will work on...
At least that's what I do.   (I'm one of those people who has open source
AS/400 stuff on the web, in save file format...)





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.