Figure 1 shows the expected flows between
the PEM client and CICS PEM server during a successful sign-on on a PV connection.
Figure 1. Successful sign-on—PV connection.
This is the expected sequence of events: - The session between the PEM client logical unit and the CICS PEM server
logical unit is established.
- The PEM client gathers data, and sends data for the sign-on program request
to the server, requesting a reply. The request flow contains BB, CD, FMH5,
and data.
- The CICS PEM server ignores the security fields in the FMH5. It processes
the data to issue the sign on (or sign on with changed password).
- The server adds the user to the PV signed-on-from list.
- The server sends the reply and deallocates the session. The reply flow
contains CEB and data.
- The client receives and processes the reply.
- The client adds the userid to the signed-onto list.
Note: - All security fields in the FMH-5 (userid, password and UP, AV, PV1 and
PV2 bits) are ignored by the CICS PEM server when it attaches the sign-on
transaction.
- The CICS PEM server adds the userid to its PV signed-on-from list only
if the sign-on and change password request is successful and either ATTACHSEC=MIXIDPE
or ATTACHSEC=PERSISTENT is specified in the CONNECTION definition.
- The PEM client must add the userid to its PV signed on-to list only if
a successful sign-on reply is received from the CICS PEM server. The
userid has been added to the PV signed on from list in the CICS PEM server,
so all subsequent attach requests from this userid can flow as signed on.