Examples of PEM client and CICS PEM server user data

Data is passed between the PEM client and the CICS® PEM server by using GDS variables.

You can use the following examples to help you check the data being sent by your PEM client:
These examples are produced by the sample PEM client program shown in the library CICSTS56.CICS.SDFHSAMP. This program uses the following values:
partner_LU_alias
hostcics
LU_alias
ps2lua
mode_name
lu62ss

When you write your own PEM client program, use the values defined in your communications manager configuration.

Example: Sign-on with new password

The following is an example of a successful sign-on using a new password. 
    PEM hostcics ps2lua lu62ss sec2r01 drtnnom hursley

A userid, password, and new password are correctly entered.

The PEM client sends the following hexadecimal user data to the CICS PEM server: 
    0231221001FFF010901E2C5C3F2D9F0F10902C4D9E3D5D5D6D40906C8E4D9E2D3C5E8
This contains the following values, as described in Table 1:
0023
Length of entire GDS variable, including this 2-byte length value
1221
Data ID for sign-on
001F
Length of this second (nested) data structure (length, data ID, and data), including this 2-byte length value
FF01
Data ID for sign-on and change password request data
09
Length of subfield for userid, including this 1-byte length value
01
ID of subfield for userid
E2C5C3F2D9F0F1
Userid (SEC2R01) in EBCDIC
09
Length of subfield for password, including this 1-byte length value
02
ID of subfield for password
C4D9E3D5D5D6D4
Password (DRTNNOM) in EBCDIC
09
Length of subfield for new password, including this 1-byte length value
06
ID of subfield for new password
C8E4D9E2D3C5E8
New password (HURSLEY) in EBCDIC

Example: Response to correct sign-on data

Figure 1 shows an example of the response to the correct sign-on data being entered.
Figure 1. Response to correct sign-on data
PEM_OK
GDS LLID
00 2d 12 21
Sign-on Reply LLID
00 29 ff 02
Sign-on Completion Status Subfield
03 00 00
Date & Time of Current Successful Sign-on Subfield
0a 02 07 ca 01 14 0d 24 31 62
Date & Time of Last Successful Sign-on Subfield
0a 03 07 ca 01 11 16 1b 23 3e
Date & Time Password Will Expire Subfield
0a 04 07 ca 02 03 00 00 00 00
Revoke Count Subfield
04 05 00 00
The first three lines of hexadecimal user data returned to the PEM client show the following required values, as described in Table 1.
002d
Total length of the GDS variable, including this 2-byte length value
1221
Data ID for sign-on data
0029
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 for sign-on completion status
00
Sign-on completion status. 00 indicates that the userid and password were valid, and the password had not expired. (See Table 1 for a list of sign-on completion status values.)
In Figure 1, the last four lines of hexadecimal user data returned to the PEM client show the following optional values, as described in Table 1. (Note that the formatting error subfields shown in Table 1 are not included, indicating that there are no errors.)
0A
Length of subfield for date and time of current successful sign-on including this 1-byte length value
02
Data ID for date and time of current successful sign-on
Date and time of current successful sign-on, as described in Table 1:
07CA
Year (1994)
01
Month (January)
14
Day (20)
0D
Hour (13)
24
Minutes (36)
31
Seconds (49)
62
Hundredths of a second (98)
0A
Length of subfield for date and time of previous successful sign-on,
03
Data ID for date and time of previous successful sign-on
Date and time of previous successful sign-on, as described in Table 1:
07CA
Year (1994)
01
Month (January)
11
Day (17)
16
Hour (22)
1B
Minutes (27)
23
Seconds (35)
3E
Hundredths of a second (62)
0a
Length of subfield for date and time password will expire (including this 1-byte length value)
04
Length of subfield for data ID for date and time password will expire
Date and time password will expire, as described in Table 1:
07ca
Year (1994)
02
Month (February)
03
Day (14)
00
Hour (00)
00
Minutes (00)
00
Seconds 00)
00
Hundredths of a second (00)
04
Length of subfield for revoke count, including this 1-byte length value
05
Data ID of subfield for revoke count
0000
Revoke count. (0000 means that there have been no unsuccessful sign-on attempts since the last successful sign-on with this userid.)

Example: Response to incorrect data format

Figure 2 shows an example response to incorrect data being entered.
Figure 2. Response to incorrect data format
PEM_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).