Hal,

Ok.  Let's look at a couple of things

DISPLAY GRS,RES=(SYSZPKT.*)
DISPLAY GRS,RES=(SYSDSN.*) <<= look for anyone using My.PKDS

I can tell you that weird things start to happen if you have something
accessing the PKDS that is not the ICSF task.  The ENQ scheme does not take
non-participants into account.  

The safe thing would be to code SYSPLEXPKDS(YES,FAIL(YES)) and let the
system do the heavy lifting.  

You might try the PKDSLIST program to make sure that your PKDS is indeed
empty.  

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS1903

How many PKDS data sets are in your sysplex now?

Rob Schramm



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Hal Merritt
Sent: Tuesday, March 08, 2011 5:59 PM
To: [email protected]
Subject: Re: ICSF Troubles

 Thanks for the replies so far! 

Rob: Here are my parms:
CKDSN(My.CKDS)     
PKDSN(My.PKDS)    
COMPAT(NO)                
SSM(YES)                  
DOMAIN(2)                 
KEYAUTH(NO)               
CHECKAUTH(NO)             
TRACEENTRY(1000)          
USERPARM(USERPARM)        
COMPENC(DES)              
REASONCODES(ICSF)         
PKDSCACHE(64)     

Allen: The LRECL of the PKDS does not seem to be an issue. It occurs (or
works) with either. 

John: No VM. There is nothing to suggest a real hardware issue. 

We use GRS for sharing. The member in SAMPLIB was used to define the
clusters. The share options are 2,3. 

This was working just fine untill we upgraded from z/os 1.9 to z/os 1.11.  


Again, thanks all!!




        

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of zSeries Systems Programmer
Sent: Thursday, March 03, 2011 10:35 PM
To: [email protected]
Subject: Re: ICSF Troubles

Just a few items

How are you sharing?  GRS?  CA-MIM?  Etc.

Were the files defined with the correct share options?

Was this working before or new configuration?

On Thursday, March 3, 2011, Ward, Mike S <[email protected]> wrote:
> We have one PKDS and one CKDS for all lpars.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Hal Merritt
> Sent: Thursday, March 03, 2011 11:36 AM
> To: [email protected]
> Subject: ICSF Troubles
>
> We are z/os 1.11. We almost never IPL. The last time we IPL'd, we 
> received the following:
>
> 11.47.55 STC00014  CSFM450E UNEXPECTED ERROR PROCESSING PKDS, RETURN 
> CODE = 0000000C, REASON CODE = 00001780.
> 11.47.55 STC00014  CSFM401I CRYPTOGRAPHY - SERVICES ARE NO LONGER 
> AVAILABLE.
> 11.47.55 STC00014  IEF352I ADDRESS SPACE UNAVAILABLE
> 11.47.55 STC00014  $HASP395 CSF      ENDED
>
> We don't use PKI and have no current plans to do so. However, the CSF 
> is critical. With a little experimentation in the testplex, I am 
> currently of the opinion that it is some sort of file sharing issue.
>
> When I allocate a fresh PKDS, CSF on LparA comes up just fine. 
> However, CSF on LparB sometimes fails with the above message. The FM 
> seems to say that the PKDS is not completely initialized until the 
> first key is stowed. Not sure how to do that.
>
> I'm thinking a PMR. But a user error is usually more likely. Right now 
> my workaround is to point each LPAR to its own PKDS. Of course, I'm a 
> bit nervous as I don't want to accidently break CSF. That would be 
> equivalent to a full outage.
>
> What I'd really like to do is to completely shut off PKDS. I've tried 
> starting with no PKDS specified, but CSF refuses to start.
>
> Thoughts?
>
>
> NOTICE: This electronic mail message and any files transmitted with it 
> are intended exclusively for the individual or entity to which it is 
> addressed. The message, together with any attachment, may contain 
> confidential and/or privileged information.
> Any unauthorized review, use, printing, saving, copying, disclosure or 
> distribution is strictly prohibited. If you have received this message 
> in error, please immediately advise the sender by reply email and 
> delete all copies.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: GET IBM-MAIN INFO 
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
> ==========================
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to which they 
> are addressed. If you have received this email in error please notify 
> the system manager. This message contains confidential information and 
> is intended only for the individual named. If you are not the named 
> addressee you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: GET IBM-MAIN INFO 
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [email protected] with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential and/or
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [email protected] with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to