For that practice run:
You use NECx2.irp
You set the device to 7.7 (which I think is the default value already there in the .irp file).
You run MakeHex in the usual way.
You use the OBC number from JP1 as the function number to select which Pronto hex string to copy from the NECx2.hex file (or which button to use in the CCF file created by IrPanels).
You ignore the JP1 HEX CMD and EFC. They have no meaning for Pronto Hex.

For the real thing, you'll need to see what you get. Mostly it works just as I described above. The decoded protocol name is usually the .irp file name. The decoded device number is usually either the whole makehex device number or the first part of the makehex device number. The decoded subdevice number is usually blank. If it isn't blank you usually put a dot between the device and subdevice numbers to form the makehex device number. The OBC number is almost always the makehex function number. The JP1 hex and EFC never mean anything in Pronto Hex.