Don't bother with the TCPRUNXT SAMPEXEC on the 591 disk - it's probably compiled REXX anyway!! :-) (sorry Chuckie, I couldn't pass up the opportunity)
HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Alan Altmark Sent: Thursday, March 19, 2009 2:25 PM To: [email protected] Subject: Re: New CMS based SSLSERV problem... DTCSSL300E On Thursday, 03/19/2009 at 04:23 EDT, "O'Brien, Dennis L" <dennis.l.o'[email protected]> wrote: > Mark C, > Thanks. I implemented your suggestion, and it works fine. Am I correct > that whatever file I end up putting the :parms. tag in, I need to put > all the parameters of :parms. there? We have about 20 systems to > support. Ideally, I'd like to specify the EXEMPT parameter in SYSTEM > DTCPARMS, which would be common to all nodes, and specify MAXSESSIONS in > a node-specific file. Is there a way to do this? Remember that you can use the server exit facility (:Exit tag or TCPRUNXT EXEC) to generate tags at runtime. See Ch. 5. Look at TCPRUNXT SAMPEXEC on the 591 disk. You could use an exit that returns the correct :parms. whenever it starts a server of class "ssl". Alan Altmark z/VM Development IBM Endicott
