1 INFO-VAX	Wed, 03 Nov 2004	Volume 2004 : Issue 611       Contents:$ Re: 3of9 Barcoding libraries for VMS$ Re: 3of9 Barcoding libraries for VMS$ Re: 3of9 Barcoding libraries for VMS! Re: LNM$SYSCLUSTER_TABLE question  LPD Retrying failed job:+ Re: MSL5026 Tape lib with OpenVMS & Windows + Re: OpenVMS on OSNews - leave your comments ( Re: Samba 2.2.8 for OpenVMS, new release2 Re: Seeking ancient DTR, FMS distros for VMS 5.5-12 Re: Seeking ancient DTR, FMS distros for VMS 5.5-12 Re: Seeking ancient DTR, FMS distros for VMS 5.5-12 Re: Seeking ancient DTR, FMS distros for VMS 5.5-1 Re: Time Change  Re: Time Change  Re: Time Change  Re: Time Change  Re: Time Change ( Re: Undocumented (?) PCSI error messages( Re: Undocumented (?) PCSI error messages  F ----------------------------------------------------------------------  % Date: Wed, 03 Nov 2004 11:19:19 +0100 9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> - Subject: Re: 3of9 Barcoding libraries for VMS ' Message-ID: <4188B0A7.F62BAA12@aaa.com>   2 I once used the JetForm suite of products for VMS.4 Mainly "JetForm Merge" that "merged" forms (designed3 with "JetFrom Designer" on Windows) with plain text , data files (transfered from an IBM mainframe8 application). The forms could include a lot of different8 bar code types. The output was printed on 20+ LaserJets.   Worked lik a dream... 6 Don't know if the JetForm products are still available for VMS (or at all...).   	 Jan-Erik.    "Barry Treahy, Jr." wrote: > I > Does anyone know of any open-source libraries that would run on VMS for E > producing 3of9 barcoding ?  I need to modify some of our systems to G > produce embedded barcoding on our documents and I suspect that if any J > commercial products existed in the past, they are probably gone or owned. > my CA and CA would want 6 figures for it.... >  > Barry  >  > -- > > > Barry Treahy, Jr                     E-mail: Treahy@MMaz.com> > Midwest Microwave, Inc.                  Phone: 480/314-1320> > Vice President & CIO                      FAX:  480/661-7028 > 1 >                        ... but it's a DRY HEAT!    ------------------------------  # Date: Wed, 03 Nov 2004 11:59:49 GMT " From:   VAXman-  @SendSpamHere.ORG- Subject: Re: 3of9 Barcoding libraries for VMS 0 Message-ID: <00A3A4FB.3A9E3D8B@SendSpamHere.ORG>  U In article <4188070F.7020708@MMaz.com>, "Barry Treahy, Jr." <Treahy@MMaz.com> writes: I >Does anyone know of any open-source libraries that would run on VMS for  E >producing 3of9 barcoding ?  I need to modify some of our systems to  G >produce embedded barcoding on our documents and I suspect that if any  J >commercial products existed in the past, they are probably gone or owned - >my CA and CA would want 6 figures for it....   F I wrote my own postscript "font" for 3/9 barcode.  If you are printing> your documents on a postscrip printer, these might be useable. you    --  < http://www.ProvN.com  for the *best* OpenVMS system security=                       solutions that others only claim to be.  --  , Cyber-Terrorism (si'-ber tayr'-or-iz-em) n.:M   The release of, the sale of, or the use of any Micro$oft software product!   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM    ------------------------------  $ Date: Wed, 3 Nov 2004 10:01:10 -0500 From: norm.raphael@metso.com- Subject: Re: 3of9 Barcoding libraries for VMS Q Message-ID: <OF0471334C.D95C9C54-ON85256F41.0051EEA0-85256F41.00528830@metso.com>   < I do not know if there is a "Jetforms" product for 'VMS, butE I can tell you that Jetforms changed its name to Accelio and was soon D after acquired by Adobe, who continue to support that product suite.  6 Also, we use a product from Integrated Software Design http://www.isdweb.com , called OnTap VMS.  I know not about pricing.  - [Disclaimer:  No beneficial interest in any.]   C Jan-Erik S=F6derholm <aaa@aaa.com> wrote on 11/03/2004 05:19:19 AM:   4 > I once used the JetForm suite of products for VMS.6 > Mainly "JetForm Merge" that "merged" forms (designed5 > with "JetFrom Designer" on Windows) with plain text . > data files (transfered from an IBM mainframe: > application). The forms could include a lot of different: > bar code types. The output was printed on 20+ LaserJets. >  > Worked lik a dream... 8 > Don't know if the JetForm products are still available > for VMS (or at all...).  >  > Jan-Erik.  >  > "Barry Treahy, Jr." wrote: > > H > > Does anyone know of any open-source libraries that would run on VMS=  forH > > producing 3of9 barcoding ?  I need to modify some of our systems to=  H > > produce embedded barcoding on our documents and I suspect that if a= nyF > > commercial products existed in the past, they are probably gone or owned 0 > > my CA and CA would want 6 figures for it.... > > 	 > > Barry  > >  > > -- > > @ > > Barry Treahy, Jr                     E-mail: Treahy@MMaz.com@ > > Midwest Microwave, Inc.                  Phone: 480/314-1320@ > > Vice President & CIO                      FAX:  480/661-7028 > > 4 > >                        ... but it's a DRY HEAT!=   ------------------------------   Date: 3 Nov 2004 07:46:16 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) * Subject: Re: LNM$SYSCLUSTER_TABLE question3 Message-ID: <ECqaxiBee8Z3@eisner.encompasserve.org>   _ In article <9fyzdpKIMBTe@cuebid.zko.dec.com>, brooks@cuebid.zko.dec.nospam (Rob Brooks) writes:    > $ def/clus clusname equiv_str  > $ sho log/ful clusnameH >    "CLUSNAME" [super,clusterwide] = "EQUIV_STR" (LNM$SYSCLUSTER_TABLE) > # > You can thank Guy Peleg for that!       Rah!    ------------------------------   Date: 3 Nov 2004 08:41:52 -0800 . From: norbert.hanowski@dillinger.biz (Norbert)! Subject: LPD Retrying failed job: = Message-ID: <77ba41db.0411030841.4c0475c7@posting.google.com>    Hi, > 1. I change my printjobs under LN03 with LAT to TCPIP and PCL.D In the beginning it worked fine. Only sometimes it got "LPD RetryingA failed job:...". But now i get this message every printjob and my * printer prints the job 4 minutes later....  - My queue: $INIT/QUEU/START/PROC=TCPIP$LPD_SMB " L_Test/DEF=(NOFEED)/Retain=ERROR -  /default=(nofeed,noflag,noburst)      F 2. With every print, i get a flag page with User, host, class and job. How can i cancel this?    	 Thank you    ------------------------------   Date: 3 Nov 2004 00:50:06 -0800 % From: Bart.Zorn@xs4all.nl (Bart Zorn) 4 Subject: Re: MSL5026 Tape lib with OpenVMS & Windows= Message-ID: <a98cd882.0411030050.25703289@posting.google.com>   1 As far as I know, you still can download MRU from B ftp://ftp.support.compaq.com/private/sms/mru/robot_sav-dcx_axp.exe  E I can't verify that right now, because our firewall doesn't allow it.    Regards,  	 Bart Zorn   t gartmann@non.immunbio.mpg.de.sens (Christoph Gartmann) wrote in message news:<cm8l6n$idt$1@n.ruf.uni-freiburg.de>...n > In article <2NOV04.10180042@thuria.waisman.wisc.edu>, karcher@thuria.waisman.wisc.edu (Carl Karcher) writes:: > >In a previous article, <ksrich<at>bellsouth.net> wrote: > > ? > >->You can use MRU which should have come with the Library.    > > K > >Not anymore. The MSL 5026 we received in Feb 2004 didn't come with it. I F > >had to get a copy from someone who's MSL drive arrived in May 2003.E > >HP wants you to use "HP StorageWorks Library and Tape Tools". It's E > >available for VMS but when I tried it a few months back, I thought E > >it was the worst hack job I've ever used on VMS (beats CA/WEBES by 
 > >miles). > $ > You could give my program a try at: >    http://www.immunbio.mpg.de/groups/gartmann/loader.zip > 
 > Regards, >    Christoph Gartmann    ------------------------------  $ Date: Wed, 3 Nov 2004 17:45:23 +0100  From: "Dr. Dweeb" <dr@dweeb.com>4 Subject: Re: OpenVMS on OSNews - leave your comments- Message-ID: <cmb1v3$1ll6$1@news.cybercity.dk>   H It seems like it turned into a "Linux scales to "n" processors" v "no it, doesn't" slinging match after about 2 posts.( I laughed at the put down of DCL though.  	 Dr. Dweeb   A "Kenneth Farmer" <kfarmer@NOSPAM.spyderbyte.com> wrote in message 8 news:eyZhd.43080$hr3.1423664@twister.southeast.rr.com...K > I posted a link to the ComputerWorld OpenVMS article on OSNews (50K+ hits  a I > day).  Many Linux, IBM and Solaris folks tearing it down.  Get in there  and  > educate these children.  :)  > 0 > http://www.osnews.com/comment.php?news_id=8744 >  >  > Ken  > 
 > OpenVMS.org ' > _____________________________________ $ > Kenneth R. Farmer <>< 336-736-7376' > SpyderByte: http://www.SpyderByte.com  >  >  >  >    ------------------------------   Date: 3 Nov 2004 11:34:25 -0600 + From: wb8tyw@qsl.network (John E. Malmberg) 1 Subject: Re: Samba 2.2.8 for OpenVMS, new release 3 Message-ID: <BJQuOXiB6$U3@eisner.encompasserve.org>   + In article <418859C7.BDCAC0D2@comcast.net>, 6   David J Dachtera <djesys.nospam@comcast.net> writes: > "John E. Malmberg" wrote:  >> >> David J Dachtera wrote: >> > "John E. Malmberg" wrote: >>M >> >>Any way that it is done it is likely to require a number of object kits. L >> >>  The object kit must be compiled on the lowest version of OpenVMS that* >> >>the resulting executable will run on. >> >D >> > Please elucidate. How does the o.s. version effect compilation? >>C >> The compiler uses information obtained from the operating system = >> supplied data files to determine how to compile a program.  > E > Sound to me like another case of "if the kit needs it, the kit must F > supply it unless it is guaranteed to be present in the environment".  G For what is supported, it is supplied.  For changing what is supported, < that would require convincing the product management people.  C > The machine works for me, not the other way around. If I needed a I > specific library/version, I'd make sure the compiler could find it. The = > environment does not control me, I control the environment.   C This section of the discussions was about binary distributions, not  source kit.   B And it is getting to be the same points being stated and restated.  ? Compiling on newer, linking on older may have unknown problems.   F Setting up a build environment where you can compile on newer and thenJ distribute binaries on older has not been documented and is not supported.  I And even if you were to do so, you still have the same issue, the objects N that result for the older release of VMS, and may not be optimal for the newerN version of VMS.  Newer features and performance enhancements would be missing.  # So the choice ends up being one of:   F   * having one kit with mulitple binaries for each tested VMS version,*     and having it get very large over time  E   * having one kit that is built for the lowest version, and thus not E     able to take advantage of the new features.  There are some cases F     where a just link on a newer version will generate an improvement,8     and these have been documented in the release notes.  C   * Having separate object kits that are tuned for the environment.   H >> With the C compiler, these are known as the header files, and are not@ >> actually supplied as individual files, but in a text library. > H > Here again, if a specific SYS$LIB_C.TLB version is needed, it would be0 > *MY* job to supply, not the environment's job.  G The specific TLB version that is required depends on the target for the G binary, as stated above.  If you use the unsupported tricks to build an H object targeted at an older version of OpenVMS, the resulting binary may9 also not take advantage of features in the newer version.   H >> Other compilers have their own definition libraries, including Macro. > F > ...and some of those are only present AFTER the compiler product has > been installed.   H Look again at the installion instructions for those products.  TypicallyK the installation procedure for the product reads in source definition files C from the OpenVMS Operating System, and then generates it's specific  set of definition files.  J This is why the OpenVMS installation manuals and the Compiler installation; manuals typically state to reinstall them after an upgrade.   G >> New objects will may set extra flags which may not be handled by the B >> older shared images.  And this may not be visible to a program. > I > That would be a case of the software product requiring specific support I > from the system RTL - i.e., an o.s. version requirement, not a language  > version requirement.  H Correct.  To use the enhanced features you need the newer version of theF operating system.  The lowest operating system supported is determinedO at the compilation time for the objects, and the link time for the executables, G with the objects needed to be be built for a version less than or equal   to the version being linked for.  J >> These are all hypothetical issues, as such configurations have not beenJ >> tested, there is no way to predict what will work and what will not, or# >> how visible such issues will be.  > J > Again, I think its just a matter of providing a suitable environemnt forA > the compiler to match the requirements of the source code. It's - > developer's job, not the environment's job.   G At this time OpenVMS does not document or support how to build on newer J versions to run on older versions.  Hoff has posted on that subject in the past.   9 >> > ... or is upward-compatibility no longer maintained?  >>F >> Upward compatible means that a non-privileged object compiled on anK >> older version of OpenVMS can link and run on a newer one.  And generally 2 >> a best effort is attempted for privileged code. >>I >> It does not mean that code compiled on a newer version of OpenVMS will D >> run correctly or predictably on an older version.  As that is not= >> tested, there is no listing of what will or will not work.  > A > To date, this has yet to be an issue for me in other languages.   F Understood.  But the issue still remains is that it is unsupported and not likely to be supported.   I What you are discussing is what you have found that you can get away with  and what is supported.  D >> Would you want to limit the performance of a program on a currentJ >> version of VMS so that it can share the same binary as a older version? > E > Limit? No. Provide a default behavior when "optimal support" is not  > available? Yes.   C But that is likely to be determined at compile time, not link time. F By it self, the compiler will not generate code that will fall back toE a default behavior, and unless you do some special tricks, the Linker  will not do it either.  K >> Hoff has posted about this many times before.  In one case before I took J >> my current job, I was proposing to compile on current versions and link >> on older versions.  > H > As long as system RTL calls are consistent across versions, should not > be an issue.  E Newer calls and parameters are added all the time.  There may also be D dormant and undocumented/unsupported routines in the older versions.   Here is a hypothetical example:   J The routine SYS$FOO_64() may be invoked by the compiler as an optimizationO when it sees that information in the current operating system definition files. H Instead of generating the code that references SYS$FOO_32 which was whatA the compiler did based on older operating system defintion files.   E There may be an almost functional implementation of SYS$FOO_64 in the F older release, so the link will work.  Until the exact failure case ofF the unsupported SYS$FOO_64() is found, the problem may not be noticed.  F Take a look at the assembly generated by the compiler for a reasonablyH complex module, and you will see that in many cases, there are operatingE system and rtl library calls present that are not in the source code.  Especially on Alpha and I64.  L You may also see that some calls in the source to standard language specificE routines, like in the CRTL, are not present because the compiler knew : how to generate the code for them that was more efficient.  I >> Right now, a lot of SAMBA functionality is disabled on the VMS port of  >> the 2.2.x stream. >  > Such as ... ?    The highlights:   M   These are features availble on SAMBA for UNIX, and have been for some time.   E    winbind - Translates Microsoft/Unix/? usenames and groups into the E              host OS security model.  Probably a requirement for both E              external authentication and other very usuable features.   E    LDAP - Lightweight Directory Access Protocol.  Most likely related            to the above.   M    Kerberos - Used for replacing LANMAN authentication in an Active Directory                environment.  @    Asynchronous NMDB - Performance optimization disabled on VMS.      Support for ACLs.      Full support for Quotas.   8    Support for Operating System based locking for speed.5      [Currently available for LINUX and a few others]       Support for Acccounting.   /    Support for incoming "Net Message" routines.   "    Test and Verification routines.  = >> Future builds may end up using GNU make for compatibility.  > E > Again, if the kit requires it, the kit must providie it. *DO* *NOT* I > assume it to present in the target environment, or you doom the product 
 > to failure.   H Why should one source kit totally include a distribution kit for anotherG product?  Are you suggesting that a C compiler also be distributed with * a source kit?  Where do you draw the line?  E > Those sound like development tools. Should not be needed for simple  > compiles.   I They are.  But the case of what is needed for simple compiles, is that it J is a lot of work to maintain a command file to build a product like SAMBA,E which already has a large number of people maintaining the makefiles. G And there are a lot of modules.  Using either MAKE or MMS/MMK is almost 8 a requirement for development of a project of this size.  G So having one build procedure for development and one for quick compile ; is not something that I would want to try to also maintain.   F > Hhmmm... Probably stick to plain text for now and fancy it up later,B > time permitting. Plain text is the "universal" language (on VMS,; > Stream_LF text files are more universal than non-stream).   F On RSYNC port in progress, I am currently building .RNH files directlyF from the supplied UNIX documentation.  I expect to be able to do so on SAMBA.  H The DocBOOK support allows OpenVMS specific information to be exposed toF the users of the other operating systems through common documentation.3 You can certainly see the advantages of doing that.   F > We've still got folks out there with LA50s, LA75s, LA100s, and such, > anyway...   L And it looks like the support for them is there in the OpenSource componentsG of Docbook that have been ported to VMS.  The modules may not have been  built of tested for a while.   -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------   Date: 3 Nov 2004 07:47:28 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ; Subject: Re: Seeking ancient DTR, FMS distros for VMS 5.5-1 3 Message-ID: <pHeJb3iSzWL9@eisner.encompasserve.org>   [ In article <f486c91c.0411021747.67842061@posting.google.com>, alegend@mail.com (Al) writes: 	 > Hi All,  > H > I am looking for DATATRIEVE and FMS distributions that would run on myC > resurrected MicroVAX II. I'm running VMS 5.5-1, and I believe the : > versions I'm after would be dated between 1990 and 1993. > 5 > No license needed as I am using a hobbyist license.   D    It's not clear that DATARIEVE is covered by the hobbyist license.:    I'm pretty sure that if it wasm I would have loaded it.   ------------------------------  % Date: Wed, 03 Nov 2004 14:24:29 +0000 - From: David B Sneddon <dbsneddon@bigpond.com> ; Subject: Re: Seeking ancient DTR, FMS distros for VMS 5.5-1 * Message-ID: <4188EA1D.3020904@bigpond.com>  ! Bob Koehler was overheard to say: ] > In article <f486c91c.0411021747.67842061@posting.google.com>, alegend@mail.com (Al) writes:  > 	 >>Hi All,  >>H >>I am looking for DATATRIEVE and FMS distributions that would run on myC >>resurrected MicroVAX II. I'm running VMS 5.5-1, and I believe the : >>versions I'm after would be dated between 1990 and 1993. >>5 >>No license needed as I am using a hobbyist license.  >  > F >    It's not clear that DATARIEVE is covered by the hobbyist license.< >    I'm pretty sure that if it wasm I would have loaded it.  @ The DTR license PAK is with the hobbyist layered products bundle   Regards, Dave.  --  I David B Sneddon (dbs)    VMS Systems Programmer     dbsneddon@bigpond.com I Sneddo's quick guide ...          http://www.users.bigpond.com/dbsneddon/ I DBS freeware at ...   http://www.users.bigpond.com/dbsneddon/software.htm I "Life is what happens to you while you're busy making other plans" Lennon    ------------------------------   Date: 3 Nov 2004 11:48:35 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ; Subject: Re: Seeking ancient DTR, FMS distros for VMS 5.5-1 3 Message-ID: <5A2V+oReGvf5@eisner.encompasserve.org>   Z In article <4188EA1D.3020904@bigpond.com>, David B Sneddon <dbsneddon@bigpond.com> writes: > B > The DTR license PAK is with the hobbyist layered products bundle > 
 > Regards, > Dave.   *    Me thinks I'll install it tonight.  8-)   ------------------------------  % Date: Thu, 04 Nov 2004 00:32:09 +0800  From: prep@prep.synonet.com ; Subject: Re: Seeking ancient DTR, FMS distros for VMS 5.5-1 - Message-ID: <87zn1y99me.fsf@prep.synonet.com>   / JF Mezei <jfmezei.spamnot@teksavvy.com> writes:    > Al wrote: I >> I am looking for DATATRIEVE and FMS distributions that would run on my D >> resurrected MicroVAX II. I'm running VMS 5.5-1, and I believe the; >> versions I'm after would be dated between 1990 and 1993.   H > FMS hasn't changed since then, and I assume DTR hasn't changed either.  F Yes it did! It was about then that DTR was fitted with CDD/supository!C Getting DTR to start on a 9MB uVII was a near miracle! Use an early F pre-CDD version, or a much later one post RDB selloff with the ability to run DTR standalone.  H You REALLY don't want to fire up DTR/CDD/RDB in less that 64 or more MB!   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   Date: 3 Nov 2004 07:32:21 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: Time Change3 Message-ID: <H+0aZM2mXrLE@eisner.encompasserve.org>   X In article <ReShd.2156$Of7.1059@news.cpqcorp.net>, hoff@hp.nospam (Hoff Hoffman) writes: > K >   As Charlie says, I too would not expect to see the system parameter and I >   the integrated TDF support appear on any OpenVMS VAX release, but the J >   underlying time-change mechanism used in recent OpenVMS Alpha versionsM >   is itself an integrated version of DECnet-Plus DTSS support -- and AFAIK, M >   DTSS DST/daylight support can and does exist for OpenVMS VAX, if enabled.   "    Is anybody actually using DTSS?   ------------------------------   Date: 3 Nov 2004 07:33:51 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: Time Change3 Message-ID: <TzsI3lVjPV7I@eisner.encompasserve.org>   U In article <4187A6B3.8050800@MMaz.com>, "Barry Treahy, Jr." <Treahy@MMaz.com> writes:   J > The irony is that NTP has been around for eons, and UCX isn't exactly a G > spring-chicken either, so one would have expected that some of these  J > more basic TCP functions to have been ironed out by now in a product of D > UCX's age.  Seriously, how often has a NTP client really required H > modification over the years, especially the past five?  Very little I  > suspect...  J    I think the change over from NTP to what Multinet called XNTP was about    5 years ago.   D    But everybody still supports the older version, too.  Well, maybe    except UCX.   ------------------------------   Date: 3 NOV 2004 09:52:52 GMT 4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher) Subject: Re: Time Change5 Message-ID: <3NOV04.09525252@thuria.waisman.wisc.edu>   / In a previous article, (Larry Kilgallen) wrote:   B ->So those who have disabled the annoying DTSS Opcom messages with1 ->logical name NET$DISABLE_DTSS are out of luck ?   = No. In the operator log on 10/31 at 02:00 you will still see:   ! Message from user SYSTEM on VRENT i %TDF-I-TDFSET, Summer time or standard time changeover - new SYS$TIMEZONE_DIFFERENTIAL=-21600/old=-18000.    --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 4 --                 karcher.nospma@waisman.wisc.edu     ------------------------------   Date: 3 Nov 2004 11:58:14 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: Time Change3 Message-ID: <1pVEL4PlfPGb@eisner.encompasserve.org>   l In article <3NOV04.09525252@thuria.waisman.wisc.edu>, karcher@thuria.waisman.wisc.edu (Carl Karcher) writes:1 > In a previous article, (Larry Kilgallen) wrote:  > D > ->So those who have disabled the annoying DTSS Opcom messages with3 > ->logical name NET$DISABLE_DTSS are out of luck ?  > ? > No. In the operator log on 10/31 at 02:00 you will still see:  > # > Message from user SYSTEM on VRENT k > %TDF-I-TDFSET, Summer time or standard time changeover - new SYS$TIMEZONE_DIFFERENTIAL=-21600/old=-18000.   C The cluster in question does not use OPERATOR.LOG, it does have the 2 system parameter set, but the time did not change.   ------------------------------  % Date: Thu, 04 Nov 2004 00:24:25 +0800  From: prep@prep.synonet.com  Subject: Re: Time Change- Message-ID: <874qk6aojq.fsf@prep.synonet.com>   4 David J Dachtera <djesys.nospam@comcast.net> writes:  D > Well, I discovered that XNTP differs from NTP; however, the latest0 > versions have again been renamed NTP (no "X").   > Dub-dub-dub-dub-dub...  G XNTP uses ntp V3, NTP is V4. IF you want to complain to Jim Mills et al  about V3 then tough!    J The main loop code and the like have been completly overhauled for ntp V4,  they are very different animals.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   Date: 3 Nov 2004 08:26:44 -0800 / From: kenneth.randell@verizon.net (Ken Randell) 1 Subject: Re: Undocumented (?) PCSI error messages = Message-ID: <79de9693.0411030826.2896e4ab@posting.google.com>    Thanks for your reply.   > L > The OpenVMS engineers responsible for the POLYCENTER Software InstallationD > (PCSI) utility have taken a look at this and responded as follows: > L > 1.  We do not understand what the customer is trying to do.  However, it's3 >     probably not relevant to the error situation.   < This is answered below, but this is correct...I can get thisE PCSI-E-PEV error by simply trying to re-install the VMS731_PCSI-V0200  kit.  F > 2.  The messages about losing recovery data should not appear if theI >     VMS731_PCSI remedial kit was re-installed with /SAVE_RECOVERY_DATA. L >     However, if this operation specifies a full product kit along with the0 >     patch kit, then this warning would appear. >   E The VMS731_PCSI-V0200 kit was already installed on this machine using < the /SAVE switch.  TCP/IP 5.4 ECO 1 was installed BEFORE the1 VMS731_PCSI-V0200 kit so it has no recovery data.     The following is what happens...  - $ product install vms731_pcsi /source=[]/save   ( The following product has been selected:E     DEC AXPVMS VMS731_PCSI V2.0            Patch (maintenance update)    Do you want to continue? [YES]    Configuration phase starting ...  F You will be asked to choose options, if any, for each selected product and for A any products that may be installed to satisfy software dependency 
 requirements.   5 DEC AXPVMS VMS731_PCSI V2.0: OpenVMS V7.3-1 PCSI V2.0   > Recovery data will be saved which will allow you to un-install= this kit.  In the past, kit installations provided some level 8 of recovery capability by renaming all replaced files to= file_name.ext_OLD.  If you wish, you can continue to do this.   6 Note that this will triple the disk space required for: this kit - one for the installed files, once for the saved7 recovery data and once for the file_name.ext_OLD files.   * Do you wish to have replaced files renamed to file_name.ext_OLD [NO] ?:   Files will not be renamed   7 * This product does not have any configuration options.        << System Disk Backup >>    9     This kit will make functional changes to your system. 7     Before installing this kit you should make a backup 8     copy of your system disk.  If you do not make a copy7     of your system disk you will not be able to restore 0     your system to a pre-kit installation state.    "     Do you want to continue? [YES]   Execution phase starting ...? %PCSI-E-NOPEV, product DEC AXPVMS TCPIP_ECO V5.4-151 is missing  version equivale ncy class representative   Portion done: 0%" %PCSI-E-S_OPFAIL, operation failed" %PCSI-E-S_OPFAIL, operation failedC %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error 	 condition   J > 3.  The %PCSI-E-NOPEV indicates that certain piece of data is missing inI >     the product database. The cause of this data omission is not known.  >    OK   > J >     The code change in the PCSI utility to address this problem has beenJ >     included in field test 1 of OpenVMS V8.2.  We expect to release PCSIL >     remedial kits that contain this fix for supported V7.3x systems in the9 >     next 2-3 months (though a date has not be set yet).   B This is good news but still doesn't explain WHY this sort of errorC information is not in HELP/MESSAGE or something like that.  PCSI is A becoming a critical utility for folks distributing software.  Its B functionality & capabilities are documented reasonably well in the; manual, but I can't find ANY information on error messages.    > M >     The best and least risky solution is to reinstall the patch kit that is ( >     identified in the error message.    & This did not work, a la the following:  , $ product install tcpip_eco /source=[] /save  ( The following product has been selected:E     DEC AXPVMS TCPIP_ECO V5.4-151          Patch (maintenance update)    Do you want to continue? [YES]    Configuration phase starting ...  F You will be asked to choose options, if any, for each selected product and for A any products that may be installed to satisfy software dependency 
 requirements.   B DEC AXPVMS TCPIP_ECO V5.4-151: Compaq TCP/IP Services for OpenVMS.  >     (c) Compaq Computer Corporation 2004. All Rights Reserved.       Compaq Computer Corporation   F     COMPAQ TCP/IP Services for OpenVMS offers several license options.  7 * This product does not have any configuration options.    Execution phase starting ...? %PCSI-E-NOPEV, product DEC AXPVMS TCPIP_ECO V5.4-151 is missing  version equivale ncy class representative   Portion done: 0%" %PCSI-E-S_OPFAIL, operation failed" %PCSI-E-S_OPFAIL, operation failedC %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error 	 condition   ) >     If this should fail, try installing M >     the other patch or product kits one-by-one from a source directory that , >     contains only the kit being installed.  ? This worked(?)...installing the TCP/IP ECO 5.4 ECO kit 1 from a  directory by itself produces:   , $ product install tcpip_eco /source=[] /save  ( The following product has been selected:E     DEC AXPVMS TCPIP_ECO V5.4-151          Patch (maintenance update)    Do you want to continue? [YES]    Configuration phase starting ...  F You will be asked to choose options, if any, for each selected product and for A any products that may be installed to satisfy software dependency 
 requirements.   B DEC AXPVMS TCPIP_ECO V5.4-151: Compaq TCP/IP Services for OpenVMS.  >     (c) Compaq Computer Corporation 2004. All Rights Reserved.       Compaq Computer Corporation   F     COMPAQ TCP/IP Services for OpenVMS offers several license options.  7 * This product does not have any configuration options.    Execution phase starting ...     Portion done: 0%...100%V  , But I'm not sure it actually did anything.    @ In any case, why does the number of kits in the source directory2 matter when I'm explictly specifying the kit name?  ? Re-installing the VMS731_PCSI-V0200 kit after the 5.4 ECO 1 kit:B install still fails as before with the PCSI-E-NOPEV error message.  - I am open to other ideas/interpretations/etc.n   ------------------------------  # Date: Wed, 03 Nov 2004 18:08:30 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond)e1 Subject: Re: Undocumented (?) PCSI error messagese1 Message-ID: <y89id.2233$0A.1033@news.cpqcorp.net>i  o In article <79de9693.0411030826.2896e4ab@posting.google.com>, kenneth.randell@verizon.net (Ken Randell) writes:  >Thanks for your reply.d   You are welcome.  N >>     The best and least risky solution is to reinstall the patch kit that is' >>     identified in the error message.r  0 I may have miss-quoted the enineer.  He replies:  6 Actually, the prior message actually stated following:  H "The best and least risky solution is to reinstall the patch kit that isF missing the critical pointer in PDB using my fix dated July 1st 2004."E                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^r  J Without that fix the reinstallation of the failing patch kit won't correctF the problem.  One can only rebuild the PDB or get by while waiting forH the fix by installing patch kits after placing them "solo" in the source. directory (and this is strongly discouraged ).     --J       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------   End of INFO-VAX 2004.611 ************************