Re: [MI400] matpg, odv, oes encoding

["Leif Svalgaard" <leif@xxxxxxxx>]

From: Steve Richter <srichter@AutoCoder.com>
Are the encoding schemes of the ODV and OES entries in the MATPG template
known?

===> the short answer is yes. The S/38 functional reference manual section 8
explains the precise structure of a program template.

I dont have a pressing need for this right now, but you can enhance the
MATINAT and QTERTVPV api if the data defn of an ODVN can be materialized.

What do we call the 2 byte index into the ODV that, when expressed in hex
external form, is used to identify data objects in the MI pgm. On the AddBkp
cmd, the system refers to it as "machine-interface
object-definition-table-vector (MI ODV) number". ODVN? ODTN?

===> The template has three pieces:
1) the template definition containing things like name, version, authority,
...
2) the instruction stream
3) the Object Definition Table (ODT).

The ODT in turn consists of
a) the Object Directory Vector (ODV)
b) the Object Entry Strings (OES)

The index into the ODV is called the ODT Reference Number.

Some of this has undoubtedly evolved with time.