Physical Transmission Flow Persistence API
The physical transmission wrapper also has the responsibility to provide some protocol-specific information to the physical transmission flow for use when logging the transmission. This is not required for MQ inputs unless the wrapper flow intends to override the MQ defaults.
The following table shows what may be specified under Environment.PMP.Variables.LogPT.DBRecord:
| Data Record | Default Value |
|---|---|
| OBJ.UID | MQMD.MsgId |
| OBJ.CID | NULL |
| OBJ.SUBTYPE | Channel.PT_TYPE |
| OBJ.PARTY_ID | Channel.PARTY_ID |
| OBJ.OWNER_ID | NULL |
| TRANSMISSION.CCSID | InputProperties.CodedCharSetId |
| TRANSMISSION.ENCODING | InputProperties.Encoding |
| TRANSMISSION.FILENAME | NULL |
| TRANSMISSION.FILEADDRESS | NULL |
A similar API exists for transmission fragments. Fragmentation is discussed fully in Design for large files.
The following table shows what may be specified under Environment.PMP.Variables.LogFRAG.DBRecord:
| Data Record | Default Value |
|---|---|
| OBJ.UID | MQMD.MsgId |
| OBJ.CID | FragInfo.fragmentCustomerRef |
| OBJ.SUBTYPE | Channel.PT_TYPE |
| OBJ.PARTY_ID | Channel.PARTY_ID |
| OBJ.OWNER_ID | NULL |
| FRAGMENT.CCSID | InputProperties.CodedCharSetId |
| FRAGMENT.ENCODING | InputProperties.Encoding |
| FRAGMENT.SEQUENCE | FragInfo.sequence |
| FRAGMENT.BYTE_OFFSET | FragInfo.byteoffset |
| FRAGMENT.FIRST_BAT_SEQ | FragInfo.firstBatSeq |
| FRAGMENT.FIRST_BAT_SPAN | FragInfo.firstBatSpan |
| FRAGMENT.LAST_BAT_SEQ | FragInfo.lastBatSeq |
| FRAGMENT.LAST_BAT_COMPLETE | FragInfo.lastBatComplete |
| FRAGMENT.TXN_SEQ_OFFSET | FragInfo.firstBatInitialTxnSeq |
Note: FragInfo is a reference to MQRFH2.usr.ibmepp.fraginfo.
|
|