Digital ring information for user IZUSVR:
Ring:
>IZUKeyring.IZUDFLT<
Certificate Label Name Cert Owner USAGE DEFAULT
-------------------------------- ------------ -------- -------
DefaultzOSMFCert.IZUDFLT ID(IZUSVR) PERSONAL YES
zOSMFCA CERTAUTH CERTAUTH NO
***
I'll have to check to see if I have an LPAR Site certificate and its root
certs.
On Thu, Oct 1, 2015 at 1:23 PM, Donald J. <[email protected]> wrote:
> What does this command list:
> RACDCERT ID(IZUSERV) LISTRING(IZUKeyring.IZUDFLT)
> Add your LPAR Site certificate and its root certs to that ring.
>
> Check Chapter 10:
>
> z/OSMF creates digital certificates that are used for secure
> communications between the user's web
> browser and the z/OSMF server, and between instances of z/OSMF servers.
> The z/OSMF keyring name is generated during the configuration phase. The
> keyring name format is
> IZUKeyring.<IZU_SAF_PROFILE_PREFIX>. By default, the keyring name is
> IZUKeyring.IZUDFLT.
> In most cases, the default z/OSMF keyring name should be sufficient for
> your installation.
>
> --
> Donald J.
> [email protected]
>
> On Wed, Sep 30, 2015, at 01:06 PM, Mark Pace wrote:
> > One last piece of information - this system runs as a guest of z/VM.
> >
> > On Wed, Sep 30, 2015 at 3:59 PM, Mark Pace <[email protected]>
> wrote:
> >
> > > One other piece of information - the reasonCode
> > > 2B34 (11060) The service could not be performed because the required
> > > PCICC, PCIXCC, CEX2C, or CEX3C was not active, or did not have a
> master key
> > > set.
> > >
> > > *User action*: If the service required a specific PCICC, PCIXCC, CEX2C,
> > > or CEX3C, verify that the value specified is correct. Reissue the
> request
> > > when the required PCICC, PCIXCC, CEX2C, or CEX3C is available, and has
> the
> > > master key set.
> > > No idea what any of this means.
> > >
> > > On Wed, Sep 30, 2015 at 3:54 PM, Mark Pace <[email protected]>
> wrote:
> > >
> > >> Trying to start OSMF for the first time. It appeared that all the
> setup
> > >> ran cleanly.
> > >>
> > >> The first task starts up.
> > >> CWWKB0056I INITIALIZATION COMPLETE FOR ANGEL
> > >>
> > >> But the IZUSVR1 dies
> > >>
> > >> Launching zosmfServer
> > >> (wlp-1.0.2.cl0220130714-1602/websphere-kernel_1.0.2) on IBM J9 VM,
> version
> > >> pmz6470-20110827_01 (en_US)
> > >> AUDIT ¨ CWWKE0001I: The server zosmfServer has been
> > >> launched.
> > >>
> > >> AUDIT ¨ CWWKG0010I: The server zosmfServer is shutting down because
> of
> > >> a previous initialization error.
> > >> AUDIT ¨ CWWKE0036I: The server zosmfServer stopped after 2.443
> > >> seconds.
> > >> ERROR ¨ CWWKG0047E: An error occurred while attempting to verify a
> > >> configuration document:
> > >> file:/SYSTEM/etc/zosmf/servers/zosmfServer/server.xml, Hardware error
> from
> > >> call CSNDDSV returnCode 12 reasonCode 11060.
> > >>
> > >> FATAL ¨ CWWKG0044E: Server shutdown because a configuration document
> > >> does not contain a valid signature:
> > >> file:/SYSTEM/etc/zosmf/servers/zosmfServer/server.xml
> > >>
> > >> The documentation basically says something did work, fix it. During
> the
> > >> configuration I replied that I wanted a CA to be created. Has anyone
> seen
> > >> this error and point in the right direction?
> > >> I also don't get this Hardware error.
> > >> CWWKG0044E: Server shutdown because a configuration document does not
> > >> contain a valid signature: {0}. *Explanation* The designated
> > >> configuration document does not contain a valid signature, or a
> portion of
> > >> the document that is protected by the signature has been modified.
> This
> > >> message is preceded by an error message that provides more
> information on
> > >> the specific error in the document. *Action* Correct the error in the
> > >> configuration document that was identified in the preceding error
> message.
> > >> CWWKG0047E: An error occurred while attempting to verify a
> configuration
> > >> document: {0}, {1}. *Explanation* An exception was thrown while
> > >> attempting to verify that the designated configuration document
> contains a
> > >> valid signature. *Action* Correct the error in the configuration
> > >> document that is causing the exception to be thrown and then retry
> starting
> > >> the server.
> > >>
> > >> --
> > >> The postings on this site are my own and don’t necessarily represent
> > >> Mainline’s positions or opinions
> > >>
> > >> Mark D Pace
> > >> Senior Systems Engineer
> > >> Mainline Information Systems
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > > --
> > > The postings on this site are my own and don’t necessarily represent
> > > Mainline’s positions or opinions
> > >
> > > Mark D Pace
> > > Senior Systems Engineer
> > > Mainline Information Systems
> > >
> > >
> > >
> > >
> >
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> --
> http://www.fastmail.com - Access all of your messages and folders
> wherever you are
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
