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...) _______________________________________________ This is the Linux 5250 Development Project (LINUX5250) mailing list To post a message email: [EMAIL PROTECTED] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250 or email: [EMAIL PROTECTED] Before posting, please take a moment to review the archives at http://archive.midrange.com/linux5250.
