Creating a version record

The version record must be the first non-comment record in each install message file, and have the format shown in Table 1. If you are translating MVS™ messages, you can use the contents of the version record fields for informational purposes. If you are creating messages for an application program, you need only to supply input to columns 1 through 6. Columns 7 through 38 can be blanks.

Table 1. Format of Version Record Fields
Columns	Contents and Description
1 & 2	".V" Identifies this record as a version record.
3-5	Three-character language code of the messages.
6	Character field containing a Y or N, indicating whether this language contains a double-byte character set (DBCS).
7-14	Field maintenance identifier (FMID) applicable to the messages within the member, padded on the right with blanks.
15-22	Product identifier applicable to the messages within the member, padded on the right with blanks.
23-38	Service level applicable to the member, padded on the right with blanks.

The following is an example of a version record.

   .VENUNJBB44N1 5695-047005

Table 2 explains the previous example of the version record.

Table 2. Version Record Example
Columns	Example	Description
1 & 2	.V	Version record
3-5	ENU	Three-character language code
6	N	DBCS indicator
7-14	JBB44N1␢	FMID
15-22	5695-047	Product identifier
23-38	005	Service level information