Re: Identify a savefile downloaded to a PC?

On 05-Nov-2015 09:46 -0600, rob wrote:

On 11/05/2015 10:32 AM David Gibbs wrote:

On 11/4/2015 10:39 AM, Vernon Hamberg wrote:

SAVFs have some signature stuff at the head - of course, they are
in EBCDIC - but there should be some commonality amongst them - I
look at them in Textpad in hex format sometimes.

I looked at 4 of them and find at position x1085 this string -
QSRDSSPC <<SNIP>>

<<SNIP>>
The 'magic' database that the file command uses also indicates that
the QSRDSSPC is prefixed by 0x19 & 0xDB.

I wasn't 100% sure that the offset of the prefix & QSRDSSPC text
was static, so I just loaded the first 16k of the file and search
for that sequence. For my purposes, this is sufficient.

Did you try various compression?

Data compression
*DEV *NO *YES *LOW *MEDIUM *HIGH

I doubt those are of any concern; probably they are applicable only to the _data portion_ of the objects that were saved\dumped to the Dump Space; i.e. the Data Compression (DTACPR) likely does not apply to the layouts of the Save\Restore Descriptor information itself, which is what the /QSRDSSPC/ stuff is.

What would be more likely to be of concern, is if the "Save command" associated with the Save File (SAVF) changed from what was expected to remain the same; see the "Display Save Header - Save File" or "Display Saved Objects - Save File" Display Save File (DSPSAVF). For example, what Vern described, seems to match the effects of a typical Save Object (SAVOBJ, SAVCHGOBJ, or SAV) request or Save Library (SAVLIB), but not necessarily that of a PTF Save File [Save Command = 'QSYS' perhaps?] or other save commands such as SAVCFG, SAVDLO, SAVSECDTA, and [if even supported] SAVSYS. Note, besides PTF SAVF, there may be other /save files/ "created by the operating system using a function other than" the typical SAVxxx commands; again, the question is, "Are those all going to use the QSRDSSPC with x/19DB?", though for the OP, that may not even be a concern.