Example of an FMH-5

As an example, suppose that an FMH-5 header needs to be built for a transaction program named TP1. This FMH-5 includes access security subfields specifying an identifier of PROG1, a password of SAMPLPW, and appended PIP data of TEST. The conversation type is basic and the synchronization level is confirm. There is no LUW or conversation correlator.

In EBCDIC, TP1, PROG1, SAMPLPW, and TEST have the following values:

TP1: X'E3D7F1'
PROG1: X'D7D9D6C7F1'
SAMPLPW: X'E2C1D4D7D3D7E6'
TEST: X'E3C5E2E3'

Therefore, the access security subfield information is a hex string of:

100801E2C1D4D7D3D7E60602D7D9D6C7F1

The PIP parameter is a hex string of:

000C12F5000812E2E3C5E2E3

The length of the entire FMH-5, including the access information, but not including the PIP data, is 32 bytes (X'20'). The entire FMH-5, including appended PIP data, is a hex string of:

200502FF 0803D000 4003E3D7 F1100801 E2C1D4D7 D3D7E606
02D7D9D6 C7F10000 000C12F5 000812E2 E3C5E2E3

Figure 1 shows the final FMH-5 broken down into its various fields. The FMH-5 length field does not include the PIP data, but byte 4 must be set to X'08' to indicate that the PIP data is there.

Figure 1. Sample FMH-5 divided into its component fields

Diagram that shows the final FMH-5 which is broken down into its various fields.