IBM BJ0NJML Integration Guide - Page 115

If the external systems do not correctly manage the inbound TRANSID counters

Page 115 highlights

Format of Interface Tables For example, assume that you create a purchase order with one line item. This transaction uses the predefined MXPOInterface, and it increments the TRANSID value that is associated with the MXOUT_INTER_TRANS queue table to 1065. The transaction produces the following records: T One entry in the MXOUT_INTER_TRANS queue table, with the IFACENAME value equal to the MXPOInterface value, and the TRANSID value equal to 1065. T One entry in the MXPO_IFACE interface table, with the TRANSID value equal to 1065. If the same purchase order has three line items, the transaction produces the following records: T One entry in the MXOUT_INTER_TRANS queue table, with the IFACENAME value equal to the MXPOInterface value, and the TRANSID value equal to 1065. T Three entries in the MXPO_IFACE interface table, each with the TRANSID value equal to 1065. In this case, each entry with the TRANSID value equal to 1065 has a unique secondary sequence number. If a transaction writes to multiple interface tables, the interface queue table contains a separate record with a unique TRANSID value for each interface table. Each interface queue table maintains its own TRANSID counter. The outbound TRANSID value is initialized when the interface queue table records are generated. You must create and maintain the TRANSID counters that populate the inbound queue tables and the interface table records. If the external systems do not correctly manage the inbound TRANSID counters, sequential processing is not guaranteed. Ensure that the TRANSID values that the external system generates does not duplicate the TRANSID value that is generated. Errors occur if duplicate TRANSID values exist and when you process the same object structure in both an inbound and an outbound direction by using a single interface table. Each endpoint has its own set of interface queue tables and its own outbound TRANSID counter. The following diagram shows an example of the relationship between the interface queue tables and the interface table records. The interface tables contain both inbound and outbound transactions. Interface Tables 101

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Format of Interface Tables
Interface Tables
101
For example, assume that you create a purchase order with one line item. This
transaction uses the predefined MXPOInterface, and it increments the TRANSID
value that is associated with the MXOUT_INTER_TRANS queue table to 1065.
The transaction produces the following records:
One entry in the MXOUT_INTER_TRANS queue table, with the
IFACENAME value equal to the MXPOInterface value, and the TRANSID
value equal to 1065.
One entry in the MXPO_IFACE interface table, with the TRANSID value
equal to 1065.
If the same purchase order has three line items, the transaction produces the
following records:
One entry in the MXOUT_INTER_TRANS queue table, with the
IFACENAME value equal to the MXPOInterface value, and the TRANSID
value equal to 1065.
Three entries in the MXPO_IFACE interface table, each with the TRANSID
value equal to 1065.
In this case, each entry with the TRANSID value equal to 1065 has a
unique secondary sequence number.
If a transaction writes to multiple interface tables, the interface queue table
contains a separate record with a unique TRANSID value for each interface table.
Each interface queue table maintains its own TRANSID counter. The outbound
TRANSID value is initialized when the interface queue table records are
generated. You must create and maintain the TRANSID counters that populate
the inbound queue tables and the interface table records.
If the external systems do not correctly manage the inbound TRANSID counters,
sequential processing is not guaranteed. Ensure that the TRANSID values that the
external system generates does not duplicate the TRANSID value that is
generated. Errors occur if duplicate TRANSID values exist and when you process
the same object structure in both an inbound and an outbound direction by using
a single interface table.
Each endpoint has its own set of interface queue tables and its own outbound
TRANSID counter.
The following diagram shows an example of the relationship between the
interface queue tables and the interface table records. The interface tables contain
both inbound and outbound transactions.