Figure 1 shows an example response to incorrect data being
entered.
Figure 1. Response to incorrect
data formatPEM_OK
GDS LLID
00 0F 12 21
Sign-on Reply LLID
00 0B FF 02
Sign-on Completion Status Subfield
03 00 06
Sign-on Request Formatting Error Subfield
04 01 00 0F
The first three lines of hexadecimal user data returned to the PEM client
show the following required values, as described in
Table 1:
- 000F
- Length of entire GDS data, including this 2-byte length value
- 1221
- Data ID for sign-on data
- 000B
- Length of this second (nested) data structure (length, data ID, and
data), including this 2-byte length value
- FF02
- Data ID for sign-on reply data
- 03
- Length of subfield for sign-on completion status, including this 1-byte
length value
- 00
- Data ID of subfield for sign-on completion status
- 06
- Sign-on completion status 06 indicating incorrect data format (see Table 1 for a list of signon completion status values.)
The last line of hexadecimal user data returned to the PEM client shows
the following
optional values, which are returned only
if there is an error. (The optional values are described in
Table 1.)
- 04
- Length of subfield for sign-on request formatting error, including this
1-byte length value
- 01
- Data ID of subfield for sign-on request formatting error
- 000F
- Sign-on request formatting error, indicating "data value out of range" (see Table 1 for a description of other possible formatting
errors).