• Subject: CPI96C0 message
  • From: "Marty" <keech@xxxxxxxxxxxx>
  • Date: Wed, 21 Jan 98 14:46:15 CST

You are right, CPI96C0 omits the user profile, as does the CPF1269
message.  I don't think there is any real reason for the omission.
On the other hand, I don't think anyone has ever asked for it before.

Generally, if a user has trouble signing on with Client Access (the
only user of QACSOTP), they would call up the operator, who would find
the CPI96C0 and CPF1269 messages, the reason codes, and would ask them
what user profile they were trying to use.

I'm not sure if security auditing would audit attempts to sign on
with a disabled profile.

Sorry I don't have a better answer.

Marty Keech * APPC team leader

>Hi Folks !
>We get the following message logged to QSYSMSG:
>CPI96C0 - Protected password could not be validated.
>The detail on this shows the Reason code as 726 which is User profile
>Doing F9=Display message details will identify the from job which
>fingers the device, but no information as to the user profile is logged
>anywhere that I can see.
>There are four possible reason codes for this message and the user
>profile information would be INVALUABLE.
>Am I missing something here and does anyone else see a problem with this
>Thanks in advance.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].