Hi Mark,
I suspect the errors you've encountered stem from somehow referencing a
pre-540 SSL 'class' entry -- one that lacks the :runtime.C , :mount. and
other tags that define values needed for the 540 SSL server. Please chec
k
your SYSTEM DTCPARMS file (or any others you've customized) for a
stale/rogue pre-540 SSL class entry that looks like this one:
:nick.ssl :type.class
:name.SSL daemon
:command.VMSSL
:diskwarn.YES
Also, ensure that a pre-540 level IBM DTCPARMS file is not present in the
CMS search order of the (540) SSL server, and that thePK65850- level IBM
DTCPARMS file *is* available. The class definition from this file is:
:nick.ssl :type.class
:name.SSL daemon
:command.VMSSL
:runtime.C
:diskwarn.YES
:Admin_ID_list.TCPMAINT GSKADMIN
:memory.256M
:mixedcaseparms.YES
:mount. /../VMBFS:VMSYS:ROOT/ / ,
/../VMBFS:VMSYS:SSLSERV/ /tmp ,
/../VMBFS:VMSYS:GSKSSLDB/ /etc/gskadm
:parms.KEYFile /etc/gskadm/Database.kdb
(Note: The 540 GA-level of this file lacks the 'SSLSERV' file space ID fo
r
the '/tmp' mount; commentary in the updated file explains why this needs
to
be included.)
One other customer ran across the errors you cited for this same reason,
but
I've just not had a chance to update the page you had checked to add this
'gotcha'...
Regards, Mark Cibula (z/VM TCP/IP Support)
