You'd code a REXX exit and ask for execution via a DTCPARMS file.
Create a SYSTEM DTCPARMS file on TCPMAINT 198.
Here's my entry for SMTP, with an EXIT
:nick.smtp:type.class
:name.SMTP daemon
:command.SMTP
:runtime.Pascal
:diskwarn.YES
On Thursday, 01/29/2009 at 08:18 EST, Hughes, Jim
jim.hug...@doit.nh.gov wrote:
Can the active Telnet Session Connect Exit(SCEXIT EXEC) be changed
without
stopping and restarting the tcpip stack? If so, how??
I think it was z/VM 5.3 where we changed the stack to automatically
reaccess
The changes to dynamically reload a Telnet connection (or TN3270E printer
management) exit without requiring a stack restart were introduced in Lev
el
520. The dynamic reload is accomplished via OBEYFILE processing of an
INTERNALCLIENTPARMS update. See the Usage Notes for the INTERNALCLIENTPA
On Friday, 01/30/2009 at 10:04 EST, Mark Cibula/Endicott/i...@ibmus wrote:
The changes to dynamically reload a Telnet connection (or TN3270E
printer
management) exit without requiring a stack restart were introduced in
Level
520. The dynamic reload is accomplished via OBEYFILE processing of
Can the active Telnet Session Connect Exit(SCEXIT EXEC) be changed
without stopping and restarting the tcpip stack? If so, how??
The TCPIP programmers guide mentions you should EXECLOAD this rexx exec
for performance. Where would be the appropriate place to add the
EXECLOAD statement?
