Jacky If you go to the description of the NSINTERADDR statement in the IP Configuration Reference, as with most statements, you will find a section "Steps for modifying". However, unlike most of the statements in the manual with which I am familiar, the information here is just pathetic! All it does is point you to the MODIFY command in the IP System Administrators Commands manual. It really should have gone the extra centimetre and mentioned that the particular flavour of MODIFY was "MODIFY command Resolver address space" since not everyone will know that all these TCPIP.DATA statements fall under a topic called "Resolver".
Under "MODIFY commandResolver address space" you will find the command John suggested described. John has a locally created RESOLVER started task procedure so he can start it with the S RESOLVER command. In case you do not have a locally created RESOLVER started task procedure, you can still stop and start the provided RESOLVER started task. You stop it with the P RESOLVER command, just as John again mentioned, but it all gets a bit subtle when you need to start it again. The command you need is START IEESYSAS.RESOLVER,PROG=EZBREINI,SUB=MSTR Not so very obvious is it? The reason for this command is twofold: 1. You are using only default values for the resolver configuration file so no configuration file DD-statement is needed and, when no DD-statement is needed, the only logical statement which is needed in the started task procedure is // EXEC PGM=EZBREINI 2. z/OS - not Communications Server - very kindly provides a generalised started task procedure with the name IEESYSAS which I think does absolutely nothing - have a look at it, I can't - except to enable some "tricks" permitted by JCL, one of which is to override the value of the PGM operand and another is the ability to change the procedure name - thereby frustrating some who have searched their procedure libraries in vain for a member named RESOLVER! This subtlety is described in the IP Configuration Guide under "Managing the resolver address space". Chris Mason On Tue, 14 Oct 2008 16:09:55 +0100, Jacky Bright <[EMAIL PROTECTED]> wrote: >Is it possible to change NSINTERADDR dynamically without IPL ? How can we >achieve that ? > >I have to change SYS1.TCPPARMS(TCPDATA) NSINTERADDR parm as the DNS server >has crashed. > >JAcky ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
