I have a vague recollection that there are two additional, undocumented, fields in the dynamic array returned by the STATUS statement, and that one of these is the internal version number. Certainly you can recover it with the newer parts of FILEINFO() function, where the file header can be recovered and decoded.
The filepeek command is intended to be used interactively, though you could script it. You need to read the first 4 bytes only - however this is not possible with filepeek, which displays sixteen bytes per line. The following script will return 16 bytes; you can inspect the first four bytes to determine (a) the byte order, (b) the internal revision number, and (c) whether 32-bit or 64-bit addressing is in effect. filepeek filename << EOC sw 10 0 q EOC ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
