I probably should have pointed out that if you have multiple machines then you can make one responsible for using this procedure and all others acquiring their updates from that updated machine. Just change the "MIM" in the procedure to your local machine that was updated using MIM. Distributed is *the* way to go here. No need to beat on MIM. MIM has been very good to all of us! -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE on behalf of Sampsa Laine Sent: Fri 6/4/2010 10:52 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Network nodename database procedure available I say we all run it at EXACTLY the same time, see if we can crash MIM on a weekly basis too :) Sampsa On 4 Jun 2010, at 15:48, Steve Davidson wrote: I have written a quick (and dirty) little procedure to update the network database on VMS platforms. This procedure (a batch job), will acquire the latest database from MIM:: on a weekly basis. The procedure is located at MIM::[DECNET]NETUPDATE.COM (thanks Johnny). I will update it from time-to-time as necessary and re- post that fact here. I would store this procedure in a "common" place (ie SYS$COMMON: [SYSMGR]) or if you have it, a dedicated area that you already store command/batch job procedures (files). Pick a time and then run it as a normal command procedure. It is self-submitting so it will happily re-submit as part of the procedure. The procedure makes two assumptions: First that the batch queue you will be using is SYS $BATCH, and second that you want the update to occur on a weekly basis. You are of course free to change either. As always, please review any file that is submitted before committing to execute it, and if you have questions just ask. Regards, -Steve