Re: ICSF First-time Startup



John,

Based on the CSFM506I message, it looks like your LPAR does not have any
crypto hardware as part of its configuration or there is no domain assigned to
your LPAR for master key processing. Check the configuration of your LPAR from
the HMC/SE for your CEC and the activation profile for your LPAR.

You might be right Raymond.
John, do a "D M=CPU" command and see if a "+" sign is under the CR column. If
true then you CE used the disk enablement process to enable the crypto
co-processors and that you did a POR right after that.

RESPONSE=SYSA
IEE174I 14.22.25 DISPLAY M 054
PROCESSOR STATUS
ID CPU CR SERIAL
00 + + 01xxxxxxxx
01 + + 11xxxxxxxx

George Fogg




HITACHI
 DATA SYSTEMS
Raymond E. Noal
Senior Technical Engineer
Office: (408) 970 - 7978

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On Behalf Of
Chase, John
Sent: Tuesday, November 27, 2007 1:08 PM
To: IBM-MAIN@xxxxxxxxxxx
Subject: ICSF First-time Startup

Hi, All,

We got the CPACF activated on our z9s this past weekend, and now I'm "in
the midst" of "initializing" ICSF. So far, I've completed all the steps
outlined in the ICSF Sysprog Guide and have the started task running.
SYSLOG messages are correct for first-time startup in our configuration
with empty CKDS and PKDS, and the related ISPF panels are accessible.

S CSF
$HASP100 CSF ON STCINRDR
IEF695I START CSF WITH JOBNAME CSF IS ASSIGNED TO USER STCCSF
, GROUP STC
$HASP373 CSF STARTED
IEF403I CSF - STARTED - TIME=14.01.05
CSFM101E PKA KEY DATA SET, SYS1.CSF.CSFPKDS IS NOT INITIALIZED.
CSFM506I CRYPTOGRAPHY - THERE IS NO ACCESS TO ANY CRYPTOGRAPHIC
COPROCESSORS OR ACCELERATORS.
CSFM001I ICSF INITIALIZATION COMPLETE
CSFM400I CRYPTOGRAPHY - SERVICES ARE NOW AVAILABLE.

Next step, according to the ICSF Admin Guide, is to initialize the CKDS
with a master key. The manual says to invoke the PPINIT utility for
this, but instead of the "next panel" shown in the manual, I get "OPTION
NOT ACTIVE" in the message area. I've retraced all the steps I took to
get to "here", and cannot see that I missed any.

Any ideas how to proceed from "here"? Running z/OS 1.7, BTW.

TIA,

-jc-


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx 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 listserv@xxxxxxxxxxx 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 listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.



Relevant Pages

  • Re: ICSF First-time Startup
    ... I should have mentioned in my last post that you need to define the CRYPTO ... environment for the LPAR in the HMC CRYPTO window to define the DOMAIN ... all the steps necessary to get ICSF up and running. ... $HASP100 CSF ON STCINRDR ...
    (bit.listserv.ibm-main)
  • Re: ICSF on z890?
    ... Subject: ICSF on z890? ... Application Migration & Crypto Hardware on z990 ... zSeries Crypto Hardware and Applications ...
    (bit.listserv.ibm-main)
  • Re: z9 Crypto Express2 usage
    ... the crypto coprocessors may not show as 'online' ... While setting up ICSF may be trivial, ... I reviewed the archives and found a pointer to Red Book SG24-7123 z9-109 ... I also am reviewing several ICSF manuals. ...
    (bit.listserv.ibm-main)
  • RE: z9 crypto express 2
    ... Are you going to have any crypto co-processors online to TEST? ... Is the lpar CF1 a coupling facility? ... Useage Domain 1, control domain 1,0. ...
    (bit.listserv.ibm-main)
  • Re: Im back
    ... Since you mentioned your favorite subjects Crypto and TOMCAT, ... The lpar where they did work was not running crypto, ... Now that the failing lpar is running z/os 1.9, ...
    (bit.listserv.ibm-main)