IBM E02HRLL-G Administration Guide - Page 215

Invalid Data for Data, Invalid Document

Page 215 highlights

Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity BCGEDIUP0038 Missing Record Delimiter End of record reached without record delimiter detected. Record delimiter expected was {0}. Record number was {1}. Record name was {2}. Byte offset was {3} Error BCGEDIUP0039 Character Conversion Failed An attempt to convert data to Unicode characters failed. The input data was {0}, and the data length was {1}. Error received: {2} Error BCGEDIUP0040 Invalid Data for Data Type Invalid data found attempting to convert {0} type data. Invalid data was {1} Error BCGEDIUP0041 Unsupported Character Set The character set used for the ROD (flat file) data is not supported. The character set was {0} Error BCGEDIUP0042 Unsupported Record Found An unsupported record was found processing C and D records. The character C, D, or Z was expected in the first position. {0} was received. Byte offset was {1} Error BCGEDIUP0052 Unexpected Serialization Exception An unexpected exception occurred while serializing the document. Exception text is: {0} Error BCGEDIUP0053 Parser or Serializer Creation Failed No parser or serializer Error could be created for syntax {0} BCGEDIUP0055 Empty Document for The document could not be Error Serialization serialized because it is empty BCGEDIUP0057 Invalid Document for The document could not be Error Serialization serialized because its internal structure is invalid BCGEDIUP0099 No Recognized Input Parser found no Data recognizable input data. Parser component {0} Error Extended description Appendix B - failed events 209

  • 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

Table 44. EDI event codes and messages (continued)
EDI Event code
Event name
Internal description
Severity
Extended description
BCGEDIUP0038
Missing Record
Delimiter
End of record reached
without record delimiter
detected. Record delimiter
expected was {0}. Record
number was {1}. Record
name was {2}. Byte offset
was {3}
Error
BCGEDIUP0039
Character Conversion
Failed
An attempt to convert data
to Unicode characters
failed. The input data was
{0}, and the data length
was {1}. Error received: {2}
Error
BCGEDIUP0040
Invalid Data for Data
Type
Invalid data found
attempting to convert {0}
type data. Invalid data was
{1}
Error
BCGEDIUP0041
Unsupported
Character Set
The character set used for
the ROD (flat file) data is
not supported. The
character set was {0}
Error
BCGEDIUP0042
Unsupported Record
Found
An unsupported record
was found processing C
and D records. The
character C, D, or Z was
expected in the first
position. {0} was received.
Byte offset was {1}
Error
BCGEDIUP0052
Unexpected
Serialization
Exception
An unexpected exception
occurred while serializing
the document. Exception
text is: {0}
Error
BCGEDIUP0053
Parser or Serializer
Creation Failed
No parser or serializer
could be created for syntax
{0}
Error
BCGEDIUP0055
Empty Document for
Serialization
The document could not be
serialized because it is
empty
Error
BCGEDIUP0057
Invalid Document for
Serialization
The document could not be
serialized because its
internal structure is invalid
Error
BCGEDIUP0099
No Recognized Input
Data
Parser found no
recognizable input data.
Parser component {0}
Error
Appendix B - failed events
209