Dave, Are you 100% certain that the DTCPARMS files that the server is accessing as its D-disk and E-disk is the one that you are actually updating? See "The DCTPARMS File" section in "z/VM TCP/IP Planning and Customization" for details. I'm using SC24-6125-04, it's on page 39.
I prefer to use the "nodeid DTCPARMS" filename format, so that I have no doubt that it is using *our* file exactly, and not something leftover by an installation, or some mystically, or by some quietly applied service. The "nodeid" is that which matches the one returned by the CMS command "IDENTIFY", which itself reads the 'SYSTEM NETID S' file and matches against the (virtual) CPU serial number in the virtual machine. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Dave Keeton" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 11/24/2010 01:34 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: Question about SSL Service Now it seems to have heartburn with the :For. tag... which is present under the :nick.SSLDCSSM section. DTCRUN1005E Required tag :For. was not found in file(s): SYSTEM DTCPARMS D1, IBM DTCPARMS E1 This log is sent to TCPMAINT immediately after TCPIP's PROFILE EXEC is run. Dave On Wed, 2010-11-24 at 14:18 -0500, James Poirier wrote: Dave, In this case I believe it is. The setup doc for using non pool show it on the nick.tcpip ONLY. Jim P. On 11/24/10 2:20 PM, "Dave Keeton" <[email protected]> wrote: Jim, That is present also. Is it possible that having multiple :DCSS_Parms. entries is a bad thing? On Wed, 2010-11-24 at 14:10 -0500, James Poirier wrote: Dave, This parm :DCSS_Parms.<DEFAULT> goes on :nick.tcpip not on :nick.ssldcssm Jim P. On 11/24/10 2:07 PM, "Dave Keeton" <[email protected]> wrote: :DCSS_Parms.<DEFAULT> -- Dave Keeton Systems Programmer Mainframe Computing Svcs Oregon State Data Center Office: (503) 373-0832 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
