1 INFO-VAX	Mon, 01 Nov 2004	Volume 2004 : Issue 606       Contents:: SAMBA 2.2.12 - (was: Samba 2.2.8 for OpenVMS, new release)( Re: Samba 2.2.8 for OpenVMS, new release( Re: Samba 2.2.8 for OpenVMS, new release( Re: Samba 2.2.8 for OpenVMS, new release Test of Info-VAX Re: Test of Info-VAX Re: Time Change  VMS newbie with UCX  Re: VMS newbie with UCX  Re: VMS newbie with UCX  Re: VMS newbie with UCX  Re: VMS newbie with UCX   F ----------------------------------------------------------------------  % Date: Sun, 31 Oct 2004 21:12:56 -0500 - From: "John E. Malmberg" <wb8tyw@qsl.network> C Subject: SAMBA 2.2.12 - (was: Samba 2.2.8 for OpenVMS, new release) 1 Message-ID: <yamdnQ6XSKM0BhjcRVn-sQ@adelphia.com>    John Reinhardt wrote:  >> >>E >>For those interested in being more on the bleeding edge, I have now J >>merged in the SAMBA 2.2.12 changes with last source kit that I produced. >>H >>I also fixed the bug that I accidently introduced, and implemented theG >>fsync() on the 1 byte writes to try to improve the large file issues.  >>" >>The source kits can be found at: >>, >> http://encompasserve.org/~malmberg/samba/  ( >> SAMBA_2_2_12-V82-SRC-20041017_BCK.ZIP  ; That kit has some serious bugs, and has been replaced with:   # SAMBA_2_2_12-V82-SRC-20041031.ZIP;1   > In the previous 2.2.12 kit and the 2.2.8 kit that I posted on I Encompasserve, I introduced two major bugs.  One is that it bypassed the  H filename translation code, and as a result also bypassed the stat cache  for performance.  . It also broke the operation of the stat cache.  F This new 2.2.12 kit corrects those bugs, and also incorporates all of A Jean-Yves Collot's (JYC) fixes that have been documented to date.   * In addition, it has several other changes:  I 1. In previous versions of both the JYC and my source kits in the module  E vms_support.c, sections of the item_list structure to the SYS$GETUAI  H call were not initialized.  This could lead to internal data structures 3 being corrupted, or crashes with access violations.   F 2. Attempting to debug at level 5 or higher will result in a infinite ' recursion until the stack is exhausted.   G 3. strcpy was used in several places to move overlapping sections of a  G string.  This is documented as to cause undefined behavior, and showed  H up as causing a corrupted stack during debug.  Replaced all occurrences 1 that I found of this with memmove() instructions.   @ 4. Out of memory conditions from realloc() calls were not being @ detected, resulting in the SMBD process crashing with an access G violation.  Added messages to write the error condition to the log and   then exit the SMBD.   G 5. To prevent memory fragmentation, which can cause premature cases of  I the SMBD process running out of memory, I increased the amount of memory  A chunks allocated for storing a cached list of directory contents.   C 6. The tests for VMS Version were failing for EFT and VMS internal  F builds.  This was used to determine ODS-5 support.  Changed to assume F that any EFT or VMS internal builds that are not on VAX support ODS-5.  E This has not undergone any significant testing, all I did was verify:   + * that the server will transfer some files. < * that new files and directories can be created and renamed.  H I have only done a test build on OpenVMS ALPHA 8.2 EFT at this time.  I G attempted to make this code build on older versions, but as yet I have  # not had time to do any test builds.     F If it is found not to build/work on a release before 8.2 EFT, post on H the SAMBA-VMS mailing list the fix, and I will attempt to incorporate itG into a future source code drop.  My main focus is going to start being  E on Samba 3 and Samba 4 and the build support for them, so I will not  1 have time to either prior version or VAX testing.   7 > Work is also being done on Samba 3.X and 4.X for VMS.   G So far it has been in the investigation stage, I do not know of anyone  G that is attempting a build at this time.  If there is anyone doing so,  * please post in the SAMBA-VMS mailing list.  G Instructions for either joining the list, or using the gmane newsgroup  - mirror are available at http://www.samba.org.    >   John H. Reinhardt  > . > (Apologies to John for reproducing his post)   None needed.  H It is available to the public from either the archives of the SAMBA-VMS 6 mailing list or from the gmane newsgroups that mirror.   -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------  % Date: Sun, 31 Oct 2004 21:44:57 -0500 - From: "John E. Malmberg" <wb8tyw@qsl.network> 1 Subject: Re: Samba 2.2.8 for OpenVMS, new release 1 Message-ID: <loadnbCEp_-3PhjcRVn-vQ@adelphia.com>    David J Dachtera wrote:  > H > Hopefully, the newevr versions will be distributed in a similar formatH > when they appear. The procedure I cooked up was a bear to get to whereJ > it is (still a bit dodgy). I'd hate to have to start all over again, but  > it would definitely be doable.  C Please join up with the Samba-VMS list, as it does not appear that  H Jean-Yves Collot is monitoring this forum.  If you can provide a better H packaging solution, maybe it can be integrated into the build procedure.  H As for SAMBA3/4 anything can happen.  My guess is that the target would : be a PCSI installation for Alpha/I64 OpenVMS distribution.  C There is no shortage of work to be done on either new versions, or  D refinements to the old, including assistance on documentation, code  review or all sorts of testing.    Any skill level can help.   F Even through current OpenVMS versions support LDAP or Kerberos, those 2 options have not been enabled in the SAMBA builds.  H The stress test utilities have not been ported.  Many of them depend on 6 fork(), so need to be converted to a different method.  G A port of the SUBVERSION client is needed, unless there is an easy way   to use the netbeans plug-in.  0    http://www.netbeans.org/catalogue/36-all.html  I A cookbook on how to maintain DOCBOOK style documentation on OpenVMS and  H generate the output would probably be useful.  It looks like everything I needed has already been ported, but how to install and use it by someone  < that only wants to use it for a small task needs to be done.  G See http://www.samba.org to either join the samba-vms mailing list, or  9 to use the newsgroup interface through the gmane servers.    -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------  % Date: Sun, 31 Oct 2004 21:24:15 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>1 Subject: Re: Samba 2.2.8 for OpenVMS, new release + Message-ID: <4185AC5E.D999C15D@comcast.net>    "John E. Malmberg" wrote:  >  > David J Dachtera wrote:  > > J > > Hopefully, the newevr versions will be distributed in a similar formatJ > > when they appear. The procedure I cooked up was a bear to get to whereL > > it is (still a bit dodgy). I'd hate to have to start all over again, but" > > it would definitely be doable. > D > Please join up with the Samba-VMS list, as it does not appear thatI > Jean-Yves Collot is monitoring this forum.  If you can provide a better J > packaging solution, maybe it can be integrated into the build procedure.  G Well, I tend to take my example from Hunter Goatley's InfoZip kits: the F kit contains object libraries and builds the .EXE on the target systemH (sorry, but sites with C compilers remain the exception in VMSland where& in UN*Xland they tend to be the rule).  I > As for SAMBA3/4 anything can happen.  My guess is that the target would < > be a PCSI installation for Alpha/I64 OpenVMS distribution.  E YECCCCHHH!!! Only as a dead-last resort goto .PCSI, unless there is a G valid reason with a great deal of weight behind it. Very messy, and you E tend to be at the mercy of bugs in PCSI (much harder to dissect a kit E and over-ride an installation programming error than with VMSINSTAL), ! errors in the PCSI database, etc.   D What I did was take Jean-Yves's kit and amssage so that it links theG .EXE on the target system directly from the .OLBs in the kit on CD-ROM, 7 and does *NOT* install the object or source by default.   H The thinking is that we need to get more acceptance of freeware and openC source, and a good way to do that is to make it as user-friendly as H possible without destroying its (forgive me) "geek" appeal. Not everyoneD who has need of it will be nuts-and-bolts coders - we need to enable  usage without requiring hacking.  D > There is no shortage of work to be done on either new versions, orE > refinements to the old, including assistance on documentation, code ! > review or all sorts of testing.  >  > Any skill level can help.   < I'd be willing to donate my repackaging code along with someC documentation (mostly caveats). Just tell me how/where. I'm already  subscribed to the list.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 01 Nov 2004 00:47:46 -0500 - From: "John E. Malmberg" <wb8tyw@qsl.network> 1 Subject: Re: Samba 2.2.8 for OpenVMS, new release 1 Message-ID: <ubSdnSB2DbGeUxjcRVn-uQ@adelphia.com>    David J Dachtera wrote:  > "John E. Malmberg" wrote:  <snip>I > Well, I tend to take my example from Hunter Goatley's InfoZip kits: the H > kit contains object libraries and builds the .EXE on the target systemJ > (sorry, but sites with C compilers remain the exception in VMSland where( > in UN*Xland they tend to be the rule).  I Any way that it is done it is likely to require a number of object kits.  H   The object kit must be compiled on the lowest version of OpenVMS that % the resulting executable will run on.   G There have been significant improvements in OpenVMS compatibility with  @ UNIX calls in the various 7.x and 8.x releases, and some of the / improvements have been delivered with ECO kits.   F It will take a bit of work to determine the optimum SAMBA for OpenVMS 3 binary that would match a specific OpenVMS release.   I While in some cases you can link on an older version of OpenVMS than the  F objects were compiled on and get away with it, the rule is that it is I unsupported.  And it would take a bit of work to determine what cases it  1 could be supported on prior versions of OpenVMS,.   I >>As for SAMBA3/4 anything can happen.  My guess is that the target would < >>be a PCSI installation for Alpha/I64 OpenVMS distribution. > G > YECCCCHHH!!! Only as a dead-last resort goto .PCSI, unless there is a I > valid reason with a great deal of weight behind it. Very messy, and you G > tend to be at the mercy of bugs in PCSI (much harder to dissect a kit G > and over-ride an installation programming error than with VMSINSTAL), # > errors in the PCSI database, etc.   H HP has produced in their roadmaps that they are investigating SAMBA for D use as a product on the OpenVMS platform.  As an HP employee in the F OpenVMS group, I have a small part in that investigation.  While I do I not control the result, I would expect that HP would use their supported  C distribution method if they decide to pursue a SAMBA based product.   ' You can see that I have a bias on this.   F > What I did was take Jean-Yves's kit and amssage so that it links theI > .EXE on the target system directly from the .OLBs in the kit on CD-ROM, 9 > and does *NOT* install the object or source by default.   @ As stated before, it is likely that many kits will be needed as G different binaries will be needed for different VMS versions, if it is  F intended to provide binaries that will run on anything other than the  current version of OpenVMS.   I With each release of VMS, better UNIX compatibility has been implemented  ? so object code built older releases may not provide as good of  E functionality for later releases.  It would take a bit of testing to   determine the optimum result.   J > The thinking is that we need to get more acceptance of freeware and openE > source, and a good way to do that is to make it as user-friendly as J > possible without destroying its (forgive me) "geek" appeal. Not everyoneF > who has need of it will be nuts-and-bolts coders - we need to enable" > usage without requiring hacking.  H It would seem that making the installation of freeware to work the same C as products supplied by HP would be the best way to meet that goal.   H It may not be as you view the optimal way to install a product, but you # can see the logic behind that idea.   D >>There is no shortage of work to be done on either new versions, orE >>refinements to the old, including assistance on documentation, code ! >>review or all sorts of testing.  >> >>Any skill level can help.  >   > > I'd be willing to donate my repackaging code along with someE > documentation (mostly caveats). Just tell me how/where. I'm already  > subscribed to the list.   H Introduce your self to the mailing list, and tell them what you want to $ do, and see if you get any feedback.  I With open source, who ever controls the web/ftp space for a distribution  G controls the rules of what goes in it.  They can take suggestions, but  C they have the final control.  It is up to the users to decide what  % distribution that they choose to use.   I I can not tell you what Jean-Yves Collot will or will not accept and put  D on his web page.  On what I post on Encompasserve.org for the SAMBA > 2.2.x stream, I will attempt to make as compatible with JYC's G distribution as I can.  I am hoping that he will use what I have done,  - but it is his decision as to what he will do.   E At this time Jean-Yves is apparently testing what he puts on his web  G site more than I am.  He is using SAMBA for production use.  I am only  G dabbling as a side project.  This implies that Jean-Yves will be doing   more testing than I do.   G I also can not control what changes that the SAMBA team will accept in  I their source code.  I am using their bugzillla based bug tracking system  F to track VMS issues that may require source changes.  You can look up F those issues with from the http://www.samba.org.  If you do look, you F will see that some of the changes to make their code more friendly to A OpenVMS have been implemented in the post 3.0.7 stream.  At this  1 writing, the current UNIX SAMBA release is 3.0.7.   H I have been submitting such changes since my work on the 2.0.6 release. H   There are bugs that are fixed in the UNIX releases of SAMBA that were ) first discovered on the OpenVMS platform.   G Now your input is valuable because you are focused on different issues  
 than I am.  A I am focused mainly on build and testing issues.  To my mindset,  F packaging is part of the build, but one of the end phases.  First you @ need to be able to convert the source code into usable binaries.  I If you do not have the ability to build the source into a usable binary,  G the packaging is meaningless.  But that is just my opinion, so until I  H am able to produce a SAMBA 4.x binary, I am not going to concern myself % on how to produce a distribution kit.   H The 2.2.x stream of SAMBA is basically being shutdown by the UNIX SAMBA I team as of the 2.2.12 release.  Only an emergency issue will cause a new  F release on that stream.  So there my goal is to get an OpenVMS 2.2.12 H release to be current with the last UNIX release in that stream.  There - is no way for me to do this on my own though.     H What I want to do is to be able to always build the current UNIX source D on OpenVMS and produce usable binaries.  So that eventually, when a F future SAMBA release is announced, an OpenVMS release that passes the G same tests will also be available.  I also would like to have a method  E of doing this so that any open source product that OpenVMS users are  2 interested in can also be treated in the same way.    G As for now, I am only going to distribute source code on Encompasserve  H because I do not have the means to do full quality testing on what I am E posting, so anyone that uses it needs to have a least the ability to  J compile it, and hopefully can also diagnose problems in their environment.    I So post what you want to or can contribute to the SAMBA-VMS mailing list  1 or newsgroup, and see what reaction that you get.   I If you ask about what others consider important, you may find some other  H areas where you can help.  It is quite possible that Jean-Yves may have 4 other suggestions as to what would be useful to him.  D Right now, as far as I can determine from postings in the SAMBA-VMS A mailing list or in comp.os.vms, there are only a couple of dozen   SAMBA-VMS sites.  G You may find the DOCBOOK issues to also be something that fits in with  F your talents.  The products to implement it appear to be available on E OpenVMS, but setting them up for use by people who do not want to be  F open source document processing experts does not appear to be trivial  the way they distributed now.    -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------  % Date: Mon, 01 Nov 2004 09:53:50 +1100 1 From: Paddy O'Brien <paddy.o'brien@tg.nsw.gov.au>  Subject: Test of Info-VAX , Message-ID: <41856CFE.5020506@tg.nsw.gov.au>   Regards, Paddy   ------------------------------  % Date: Sun, 31 Oct 2004 21:27:56 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: Test of Info-VAX * Message-ID: <4185AD3C.F1A96BC@comcast.net>   Paddy O'Brien wrote: >  > Regards, Paddy  ' Hope you get this. The group is live...    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 31 Oct 2004 12:51:32 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: Time Change+ Message-ID: <41853434.499DF800@comcast.net>    Dan Foster wrote:  > a > In article <41845947.816F1852@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> wrote:  > > C > > That said, the method I'll be employing tonight goes like this:  > > " > >  1. Disable (Multinet's X)NTP.1 > >  2. DEASSIGN the SYS$TIMEZONE* logical names.  > >  3. Change the system time. . > >  4. Invoke SYS$STARTUP:TDF$UTC_STARTUP.COM% > >  5. Re-enable and restart (X)NTP.  > > J > > 2-4 are done via SYSMAN and happen in rapid succession. 1 can still beL > > part of the automated procedure; however, MULTINET:START_SERVER.COM doesJ > > not run from SYSMAN - SUBMIT 5 to a node-specific batch queue instead. > H > Hm? I don't know what version of Multinet and OpenVMS you have, but on$ > my OpenVMS 7.3-2/Multinet 5.0 box: > - > SYSMAN> do multinet netcontrol ntp shutdown 3 > %SYSMAN-I-OUTPUT, command execution on node DUBHE / > Connected to NETCONTROL server on "LOCALHOST" L > < dubhe.catbert.org Network Control V5.0(10) at Sun 31-Oct-2004 9:33AM-GMT# > < Starting shutdown of NTP server  > < NTP server shutdown  >  > ...and...  > * > SYSMAN> do multinet netcontrol ntp start3 > %SYSMAN-I-OUTPUT, command execution on node DUBHE / > Connected to NETCONTROL server on "LOCALHOST" L > < dubhe.catbert.org Network Control V5.0(10) at Sun 31-Oct-2004 9:33AM-GMT > < Starting NTP server & > < NTP server started, process id 23B > C > Is disabling it for a brief interval entirely really required, as : > opposed to simply stopping and then later restarting it?  F VMS version tends to be less relevant, save that TDF$UTC_STARTUP seems to be V7.3 and later.   F Older versions of Multinet appear to behave differently. Sometimes theD XNTP_SERVER process comes back unprovoked, sometimes it doesn't. The@ Multinet document isn't real clear on this; so, I'll lookup that8 NETCONTROL stuff in the doc.'s for the older version(s).  H Note also that this only works if you wait until after 03:00 CDT to makeA the shift backward (repeat the hour of 02:00 CDT, not 01:00 CDT).   E I'll be refining this further for the "Spring Forward" time change in H April 2005. I may also open an SR with VMS support. My partner found outH that when you set the time back to before 02:00. then reboot, the systemG reverts to CDT on the restart (clock says 31-Oct-2004 at 01:00, and the G timezone rule says that CST doesn't begin until 02:00 on the 5th (last)  Sunday of October).   D I guess we're still looking for a definitive work on this topic, eh?   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Sun, 31 Oct 2004 20:45:08 GMT / From: Adam Stouffer <adam_stouffer@hotmail.com>  Subject: VMS newbie with UCX) Message-ID: <o9chd.1514$BU6.818@trnddc05>   C Well I've gotten OpenVMS 7.3 installed on a VS3100 M76 without any  I problems except having to put the license experation date in the release  G date field. Now I'm having trouble licensing UCX. First of all I'm not  I sure if its currently loaded or not, the install never asked. Heres what  ; I fill in for the license and it doesn't like the checksum.     $                       Issuer:  DECUS6                Authorization:  DECUS-USA-907036-693406"                 Product Name:  UCX"                     Producer:  DEC                         Units:  0                 Release Date:                       Version: *             Termination Date:  31-OCT-2005                 Availability: +                     Activity:  CONSTANT=100                       Options:                         Token: )                  Hardware ID:  AB113009NH 2                     Checksum:  xxxxxxxxxxxxxxxxxxx     Is that correct? [YES]: @ Registering UCX license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...5 %LICENSE-F-BADCHK, checksum does not validate for UCX   ; Please review all entered PAK data, including the checksum.     H Any ideas what I'm doing wrong? If UCX needs loaded from the cd I'm not * sure how thats done. Any help appreciated.     Adam   ------------------------------  # Date: Sun, 31 Oct 2004 21:35:20 GMT 5 From: brad@rabbit.dnsalias.org (Bradford J. Hamilton)   Subject: Re: VMS newbie with UCX. Message-ID: <sUchd.349132$D%.131185@attbi_s51>  [ In article <o9chd.1514$BU6.818@trnddc05>, Adam Stouffer <adam_stouffer@hotmail.com> writes: D !Well I've gotten OpenVMS 7.3 installed on a VS3100 M76 without any J !problems except having to put the license experation date in the release H !date field. Now I'm having trouble licensing UCX. First of all I'm not J !sure if its currently loaded or not, the install never asked. Heres what < !I fill in for the license and it doesn't like the checksum. !  ! % !                      Issuer:  DECUS 7 !               Authorization:  DECUS-USA-907036-693406 # !                Product Name:  UCX # !                    Producer:  DEC ! !                       Units:  0  !                Release Date: !                     Version:+ !            Termination Date:  31-OCT-2005  !                Availability:, !                    Activity:  CONSTANT=100 !                     Options: !                       Token:* !                 Hardware ID:  AB113009NH3 !                    Checksum:  xxxxxxxxxxxxxxxxxxx  !  !  !Is that correct? [YES]:A !Registering UCX license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB... 6 !%LICENSE-F-BADCHK, checksum does not validate for UCX ! < !Please review all entered PAK data, including the checksum. !  ! I !Any ideas what I'm doing wrong? If UCX needs loaded from the cd I'm not  + !sure how thats done. Any help appreciated.  !    Hi Adam,  N I've checked my hobbyist license database, and I see no hardware ID associatedM with the UCX PAK - are you _absolutely_ sure you were issued a UCX PAK with a C HW ID?  Typically, the only PAK that has a HW ID is the "base" PAK   (AKA "VAX/VMS")     !  !Adam   J __________________________________________________________________________A Bradford J. Hamilton                    "All opinions are my own" K bMradAhamiPltSon-at-coMmcAast.nPeSt     "Lose the MAPS, and replace '-at-'  0                                          with @"   ------------------------------  + Date: Sun, 31 Oct 2004 22:02:41 +0000 (UTC) 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)  Subject: Re: VMS newbie with UCX0 Message-ID: <newscache$hzxg6i$23u$1@news.sil.at>  [ In article <o9chd.1514$BU6.818@trnddc05>, Adam Stouffer <adam_stouffer@hotmail.com> writes: 7 >               Authorization:  DECUS-USA-907036-693406 # >                Product Name:  UCX # >                    Producer:  DEC ! >                       Units:  0  >                Release Date:+ >            Termination Date:  31-OCT-2005 * >                 Hardware ID:  AB113009NH3 >                    Checksum:  xxxxxxxxxxxxxxxxxxx  > < >Please review all entered PAK data, including the checksum. > I >Any ideas what I'm doing wrong? If UCX needs loaded from the cd I'm not  + >sure how thats done. Any help appreciated.   K You probably forgot the release date (identical to the termination date)...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 31 Oct 2004 21:27:31 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>  Subject: Re: VMS newbie with UCX+ Message-ID: <4185AD23.E53BB807@comcast.net>    Adam Stouffer wrote: > D > Well I've gotten OpenVMS 7.3 installed on a VS3100 M76 without anyJ > problems except having to put the license experation date in the releaseH > date field. Now I'm having trouble licensing UCX. First of all I'm notJ > sure if its currently loaded or not, the install never asked. Heres what= > I fill in for the license and it doesn't like the checksum.  > & >                       Issuer:  DECUS8 >                Authorization:  DECUS-USA-907036-693406$ >                 Product Name:  UCX$ >                     Producer:  DEC" >                        Units:  0 >                 Release Date:  >                      Version: , >             Termination Date:  31-OCT-2005 >                 Availability: - >                     Activity:  CONSTANT=100  >                      Options:  >                        Token: + >                  Hardware ID:  AB113009NH 4 >                     Checksum:  xxxxxxxxxxxxxxxxxxx >  > Is that correct? [YES]: B > Registering UCX license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...7 > %LICENSE-F-BADCHK, checksum does not validate for UCX  > = > Please review all entered PAK data, including the checksum.  > I > Any ideas what I'm doing wrong? If UCX needs loaded from the cd I'm not , > sure how thats done. Any help appreciated.  B The hobbyist license site sends you a .COM file containing the PAKA replicas. Clean the existing records our of LMF (see HELP LICENSE G DELETE), and use the (apporpriate segemnt of the) DCL code you received A from the hobbyist license site. That should register/load with no  problem.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Mon, 01 Nov 2004 03:50:14 GMT / From: Adam Stouffer <adam_stouffer@hotmail.com>   Subject: Re: VMS newbie with UCX) Message-ID: <Wnihd.1590$BU6.606@trnddc05>      > Hi Adam, > P > I've checked my hobbyist license database, and I see no hardware ID associatedO > with the UCX PAK - are you _absolutely_ sure you were issued a UCX PAK with a E > HW ID?  Typically, the only PAK that has a HW ID is the "base" PAK   > (AKA "VAX/VMS")  >    > !  > !Adam   I That was the problem. I removed the hardware ID and it works. Well now I   know :) Many thanks.     Adam   ------------------------------   End of INFO-VAX 2004.606 ************************