[prev in list] [next in list] [prev in thread] [next in thread] 

List:       racf-l
Subject:    Re: HCPRPW002E
From:       Dovid Wakser <0000051422d81dd4-dmarc-request () LISTSERV ! UGA ! EDU>
Date:       2017-06-30 13:25:43
Message-ID: 005201d2f1a4$6172a6c0$2457f440$ () com
[Download RAW message or body]

No, Jeff, but I figured it out. I forgot to alter those users to NOPASSWORD
and PASSPHASE. But thanks for the response.

David Wakser

-----Original Message-----
From: RACF Discussion List [mailto:RACF-L@LISTSERV.UGA.EDU] On Behalf Of
Jeff Bengtson
Sent: Friday, June 30, 2017 3:13 PM
To: RACF-L@LISTSERV.UGA.EDU
Subject: Re: HCPRPW002E

I don't think it's RACF giving you issues here.  HCP is the prefix for z/VM
related messages.   Probably have better luck with your post over there.  

Jeff Bengtson
Computing Environment
State Farm Insurance
ph: (616) 887-1608
hrs (all times Eastern): Mon-Thur: 6:30-3:45; Fri: 6:30-10:45

-----Original Message-----
From: RACF Discussion List [mailto:RACF-L@LISTSERV.UGA.EDU] On Behalf Of
Dovid Wakser
Sent: Friday, June 30, 2017 9:03 AM
To: RACF-L@LISTSERV.UGA.EDU
Subject: HCPRPW002E

Cross-posted to RACF & VM lists.

All:

	I have a new employee who is attempting to log on for the first
time. I set up his account with a temporary password. After entering it, he
(properly) gets prompted for a new password. He types in the new password,
and receives message HCPRPW002E Password syntax invalid.

	Figuring he was not entering something properly, I attempted to do
the same thing on one of his new user ids, utilizing passwords that I have
used in the past and fit all of the local "rules" implemented in RACF.
However, I receive the same response! 

Any place in RACF where I can look to see exactly what it things the problem
is? I can't seem to figure this out. It doesn't seem to be user error (since
I know how it needs to be done), but it is possible that when I set up the
user, I didn't set up something properly. Any ideas?

David Wakser
[prev in list] [next in list] [prev in thread] [next in thread]