You're at base Java 7.0. Mine is at SR3 FP1. It says so in many places
in the -version display.
Mark Jacobs
Mark Pace <mailto:[email protected]>
October 2, 2015 at 9:55 AM
# /usr/lpp/java/J7.0_64/bin/java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pmz6470-20110827_01)
IBM J9 VM (build 2.6, JRE 1.7.0 z/OS s390x-64 20110810_88604 (JIT enabled,
AOT enabled)
J9VM - R26_Java726_GA_20110810_1208_B88592
JIT - r11_20110810_20466
GC - R26_Java726_GA_20110810_1208_B88592
J9CL - 20110810_88604)
JCL - 20110809_01 based on Oracle 7b147
I can't tell which SR level I have from this. I'm Java ignorant, so I'll
have to try to figure what these Java overrides you speak of.
--
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
Please be alert for any emails that may ask you for login information
or directs you to login via a link. If you believe this message is a
phish or aren't sure whether this message is trustworthy, please send
the original message as an attachment to '[email protected]'.
Donald J. <mailto:[email protected]>
October 2, 2015 at 9:50 AM
The return code 12 / 11060 is because your Java provider list includes
com.ibm.crypto.hdwrCCA.provider.IBMJCECCA
zOSMF uses Java SSL, not System SSL.
Java 7 SR3 is minimum requirement for zOSMF.
You probably need some Java overrides to eliminate attempt
to use hardware crypto.
--
Donald J.
[email protected]
On Wed, Sep 30, 2015, at 12:54 PM, Mark Pace wrote:
Trying to start OSMF for the first time. It appeared that all the setup
ran cleanly.
file:/SYSTEM/etc/zosmf/servers/zosmfServer/server.xml, Hardware error from
call CSNDDSV returnCode 12 reasonCode 11060.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
http://www.fastmail.com - Choose from over 50 domains or use your own
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
Please be alert for any emails that may ask you for login information or
directs you to login via a link. If you believe this message is a phish or
aren't sure whether this message is trustworthy, please send the original
message as an attachment to '[email protected]'.
Mark Pace <mailto:[email protected]>
September 30, 2015 at 3:54 PM
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
Please be alert for any emails that may ask you for login information
or directs you to login via a link. If you believe this message is a
phish or aren't sure whether this message is trustworthy, please send
the original message as an attachment to '[email protected]'.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
