Re: C version of ADDLC on very long variables

[Dave McKenzie <davemck@xxxxxxxxxxxxx>]

It's not the version of the save file, because it's been x3000 for RISC
save files at all releases (it's x1100 for CISC save files).  My guess
is it's something like "version of the save file spec" or "version of
the SLIC code that wrote this."

Notice in the table below x3000 is the code for V3R6.

Here's a table of various version fields in save files (and tapes):

       CodeA  CodeB  CodeC  CodeD
V3R6M0  3000   3000   35
V3R7M0  3201   3205   3A
V4R1M0  3305   3305   3B
V4R1M4  3350   3350   3D
V4R2M0  3400   3400   3C
V4R3M0  3500   3500   3E
V4R4M0  3600   3600   3F     AB
V4R5M0  3700   3700   40     AC
V5R1M0  3800   3800   41     AD
V5R2M0  3903   3900   42     AE
V5R3M0  4000   4000   43     AF
V5R4M0  4100   4105   44     B0

CodeA and CodeB appear in the "QSRDSSPC.1" records at offsets x52 and
x54 respectively.

CodeA and CodeB can vary somewhat, depending on whether the save file is
written on the native OS release, or a later release using TGTRLS (and
maybe even on PTF level).

CodeC appears at offset 1 in the structure that contains the CPU
serial number (record 25 in V5R3) for SAVOBJ & SAVLIB.  CodeD is used
for SAV.

I think CodeC/D is the one that DSPSAVF uses to calculate "Release level."

--Dave

Gene_Gaunt@xxxxxxxxxxxxxxx wrote:
> What does the x"30003000" at offset 12-15 in a save file (first record)
> signify?  Is it the version/release level of the save file?