1 INFO-VAX	Sun, 06 Oct 2002	Volume 2002 : Issue 552       Contents: Re: 'hobbyist' vms! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) 
 Re: FDL Files 
 Re: FDL Files  Re: Mount ISO Image  Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic+ Re: Originator of detached process from DCL L Re: Proposal: Retirement of some Components of the Compaq C++ Class  LibraryL Re: Proposal: Retirement of some Components of the Compaq C++ Class  Library7 Sony 40/12/48 CD-RW IDE usable wih CDRecord on OpenVMS? % TPU access to DCL symbols or logicals ) Re: TPU access to DCL symbols or logicals  Re: UCX security advisory  Re: UCX security advisory  Re: Version control on OpenVMS! Re: WASD Security Advisory Issued ! Re: WASD Security Advisory Issued + Which UIC to use for a product's username ? / Re: Which UIC to use for a product's username ? / Re: Which UIC to use for a product's username ? / Re: Which UIC to use for a product's username ?   F ----------------------------------------------------------------------  # Date: Sat, 05 Oct 2002 18:32:12 CDT  From: sword7@speakeasy.org Subject: Re: 'hobbyist' vms 6 Message-ID: <MWSdnT8VBLzh6wKgXTWc3Q@News.GigaNews.Com>  0 David J. Dachtera <djesys.nospam@fsi.net> wrote:J > What I don't know is: do any of the current VAX emulators run on *BSD or
 > Solaris?  H Well, my ts10 emulator works so well on FreeBSD operating system.  I didJ tried that without any modification before.   Try that on FreeBSD and let 
 me know that.    -- Tim Stark   --  , Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  % Date: Sun, 06 Oct 2002 10:37:58 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>* Subject: Re: e-mail web client (SilkyMail)) Message-ID: <3D9FF666.5060909@vajhoej.dk>    JF Mezei wrote:    > Arne Vajhj wrote:2 >>BTW, how does VMS MAIL handle the same problem ? > A > The same way because this is a limitation of the POP protocol.     You misunderstood my question.  1 How does VMS MAIL handle the sitituation with two - sessions (f.ex. good old VT320's) reading and $ deleting email at the same account ?   Arne   ------------------------------  % Date: Sun, 06 Oct 2002 10:40:07 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>* Subject: Re: e-mail web client (SilkyMail)' Message-ID: <3D9FF6E7.50209@vajhoej.dk>    Arne Vajhj wrote:  : > There are probably some webmail interface out there that > does not handle it.  > ; > But is is a very common feature - I would expect it to be 7 > used by *millions* of people world-wide. And it seems 
 > to work.  + To elaborate a bit: the reason that this is , usually not a problem is that email accounts- is usually personal. It is probably extremely + rare that two web-sessions would access the  same POP-account.    Arne   ------------------------------   Date: 6 Oct 2002 07:19:41 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen) * Subject: Re: e-mail web client (SilkyMail)3 Message-ID: <J5X7CmkZo9iV@eisner.encompasserve.org>   b In article <3D9FF666.5060909@vajhoej.dk>, Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk> writes: > JF Mezei wrote:  >  >> Arne Vajhj wrote: 3 >>>BTW, how does VMS MAIL handle the same problem ?  >>  B >> The same way because this is a limitation of the POP protocol.  >   > You misunderstood my question. > 3 > How does VMS MAIL handle the sitituation with two / > sessions (f.ex. good old VT320's) reading and & > deleting email at the same account ?  B In general, VMS MAIL relies upon RMS indexed files to allow accessE by simultaneous sessions.  But what exactly needs to be handled about ; "the situation" ?  I was not following the piece about POP.    ------------------------------   Date: 6 Oct 02 15:17:38 +0200 ) From: p_sture@elias.decus.ch (Paul Sture) * Subject: Re: e-mail web client (SilkyMail)) Message-ID: <BixJe+e9vBAP@elias.decus.ch>   b In article <3D9FF666.5060909@vajhoej.dk>, Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk> writes: > JF Mezei wrote:  >  >> Arne Vajhj wrote: 3 >>>BTW, how does VMS MAIL handle the same problem ?  >>  B >> The same way because this is a limitation of the POP protocol.  >   > You misunderstood my question. > 3 > How does VMS MAIL handle the sitituation with two / > sessions (f.ex. good old VT320's) reading and & > deleting email at the same account ? >   : I have seen it get confused when logged in from my laptop.    --  
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 06 Oct 2002 18:30:54 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>* Subject: Re: e-mail web client (SilkyMail)) Message-ID: <3DA0653E.8080602@vajhoej.dk>    Larry Kilgallen wrote:  D > In general, VMS MAIL relies upon RMS indexed files to allow accessG > by simultaneous sessions.  But what exactly needs to be handled about = > "the situation" ?  I was not following the piece about POP.     7 The question is if the two sessions do a varity of DIR, : READ n and DEL n what will happend. The worst case is that= a DEL n delete something else than it should. But there could 7 also be the possibility that READ n read something else  than it should.    Arne   ------------------------------    Date: 06 Oct 2002 00:14:47 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: FDL Files- Message-ID: <87k7kwkglk.fsf@prep.synonet.com>   ; Hein van den Heuvel <hein_netscape@eps.zko.dec.com> writes:   E >     Good thing you posted that code example. As Bart and Christoffe C > replied earlier, we all thought you were talking standard RMS FDL > > files. You now appear to have been referring to some 'formatB > definition language' which is non standard VMS. It might even beC > just a bunch of C macro's. You'll have to poke around in your own @ > development environment as to what to rules are for this tool.  F Wrong FDL, they are `Form Definition Library' files from TDMS I think. (long time, much bitrot...)   A >     At first glance it looks like a locally developed tool, not @ > overly complex.  If you just had to make a report and were notC > overly bound to this FDL tool, then you may want to look at other E > alternatives like plain C, or the perl formatting tools.  Ohterwise 7 > it is time to hit some workers aroudn you for advice.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  # Date: Sun, 06 Oct 2002 10:49:23 GMT $ From: winston@SSRL.SLAC.STANFORD.EDU Subject: Re: FDL Files8 Message-ID: <00A15073.D2589930@SSRL04.SLAC.STANFORD.EDU>  \ In article <87k7kwkglk.fsf@prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:< >Hein van den Heuvel <hein_netscape@eps.zko.dec.com> writes: > F >>     Good thing you posted that code example. As Bart and ChristoffeD >> replied earlier, we all thought you were talking standard RMS FDL? >> files. You now appear to have been referring to some 'format C >> definition language' which is non standard VMS. It might even be D >> just a bunch of C macro's. You'll have to poke around in your ownA >> development environment as to what to rules are for this tool.  > G >Wrong FDL, they are `Form Definition Library' files from TDMS I think.  >(long time, much bitrot...)  G Not TDMS.  TDMS forms are defined with a WYSIWYG character-cell editor.    -- Alan    ------------------------------  % Date: Sat, 05 Oct 2002 21:28:02 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>  Subject: Re: Mount ISO Image' Message-ID: <3D9F9FB2.49E91FB4@fsi.net>    Larry Kilgallen wrote: > \ > In article <3D9F1B89.EDB55A5@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes: > > Larry Kilgallen wrote: > O > >> On earlier versions of VMS one must explicitly specify /MEDIA_FORMAT=CDROM N > >> for mounting an ISO9660 CDROM.  In my experience, one must still add thatN > >> if mounting an ISO-9660 volume other than on a genuine CDROM drive.  ThatL > >> is, when I mount an Infoserver partition on VMS I must specify it, so IO > >> presume the same might be true using the software driver someone mentioned L > >> earlier in this thread for mounting an image without committing it to a > >> CDROM.  >   > > DJAS01::DDACHTERA$ sh dev ld > > I > > Device                  Device           Error    Volume         Free 
 > > Trans Mnt J > >  Name                   Status           Count     Label        Blocks
 > > Count Cnt 2 > > DJAS01$LDA0:            Online               01 > > DJAS01::DDACHTERA$ ld conn hpets2002.iso lda1 ( > > DJAS01::DDACHTERA$ moun/over=id lda1. > > %MOUNT-I-WRITELOCK, volume is write lockedA > > %MOUNT-I-CDROM_ISO, HPETS2002:HPETS2002 (1 of 1) , mounted on  > > _DJAS01$LDA1:  > > DJAS01::DDACHTERA$ > > F > > Sorry 'bout the text wrap. That's kinda ugly in places, ain't it?! > > 3 > > Anyway, that's using LD V6.2 on OpenVMS V7.1-2.  > ; > Hmmm.  Does the LDA0: device tell VMS it is CDROM drive ?   ! DJAS01::DDACHTERA$ sh dev/fu lda0   > Disk DJAS01$LDA0:, device type Foreign disk type 1, is online,
 file-oriented 1     device, shareable, device is a template only.   2     Error count                    0    Operations completed                  0F     Owner process                 ""    Owner UIC                      [SYSTEM];     Owner process ID        00000000    Dev Prot             S:RWPL,O:RWPL,G:R,W 6     Reference count                0    Default buffer size                 512   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  " Date: Sat, 5 Oct 2002 23:16:29 GMT- From: bdc@world.std.com (Brian 'Jarai' Chase) ! Subject: Re: OpenVMS is strategic & Message-ID: <H3J7BH.ACs@world.std.com>  + In article <3D9F4203.982F3E0@videotron.ca>, / JF Mezei  <jfmezei.spamnot@videotron.ca> wrote:  > Bill Todd wrote:  K > > The real beginning happened well before KO's departure in 1992.  It was M > > certainly as early as the 1988 cancellation of the PRISM DECwest project, O > > which I've been told was itself due to continuing internal friction between  > > the VMS and Unix factions. > N > I'd say that the real beginning was when DEC refused to commercialise/marketO > its PDP11-in-a-VT100 as a viable personal computer. Commodore had the vision. I > Apple had the vision, and IBM got the vision (rather late in the game). 2 > Digital had it now, but *chose* not to push it.   E Ah, the PDT-11 series.  Yeah, that was the first time they blew their J chances on the personal computing.  They did it again a few years later byF simultaneously introducing three completely incompatible systems:  TheJ PDP-8 based DECmate and DECmate-II, the PDP-11 based DEC Professional, andH the 8086 based DEC Rainbow.  Had they concentrated on just one of those,I and priced it significantly below IBM's PC, I'd imagine DEC would've have  been much more successful.  H As opposed to looking at the PC market as a dramatic change in computingG philosophy, the indications seem to be that they saw it as just another 5 opportunity to extend their existing product lines.     J The truly sad thing here is that DEC already had everything they needed toA completely dominate the personal computing industry.  They had an J established name, they had great lines of 12-bit and 16-bit CPUs, they hadD OSes like RT-11 which certainly could've competed with MS-DOS.  TheyG practically dominated the educational markets with their larger PDP-11, H PDP-10, and VAX systems.  These would've been good avenues to pursue theB introduction of affordable computing to students and faculty.  DECJ obviously had the ability to adapt their technologies into low-end systems) without investing much additional effort.   J I guess all we can say now is... oops!  I'd much rather today were a worldB based on a some sort of "DEC with business sense" and one of their< processor lines than the world of Microsoft and PCs we have.   -brian.  --  F --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----H This counter is [6,177,399,753] times as pointless as a real one.  -- K.   ------------------------------  $ Date: Sat, 5 Oct 2002 21:12:54 -0400* From: "Bill Todd" <billtodd@metrocast.net>! Subject: Re: OpenVMS is strategic 6 Message-ID: <dtmcnRrulKKVEwKgXTWcow@News.GigaNews.Com>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3D9F8999.4D4B56B0@videotron.ca... > Bill Todd wrote:K > > That couldn't have happened at the time, because DEC simply didn't know  how G > > to build hardware that cheaply:  if it had sold its products at the  price K > > IBM charged for its PC, it would have lost quite a bit of money on each  one " > > (well, maybe not the DECmate). >  > Horse radish.   B I beg your pardon?  I was there at the time, and to the best of myL recollection you were not.  I knew what the manufacturing costs of the boxesL were, and you clearly haven't a clue.  It wasn't a matter of being unwillingL to compromise margins (though there was pressure on that front as well):  asI I already stated, the *cost* to build and sell the boxes was greater than  IBM's sales price.   > L > If IBM was able to compate against Apple and Commodore, there is no reason DEC L > ,which was able to build cheaper hardware than IBM, couldn't have competed- > too. Where there is a will, there is a way.   J Easy for you to say.  IBM didn't use a single IBM component in the PC:  itK out-sourced everything, and merely assembled (and even that separately from I its normal assembly lines).  DEC could have done the same, I suppose, but H the result would then just have been another PC clone (and it's possibleE that might have been a good thing, but it's not what Brian and I were  discussing).   > H > DEC has consistently shown that it was unwilling to compete against itL > competitors, perhaps because it refused to wake-up to the existence of new competitors.  F As is too often the case, JF, you speak emphatically but from completeL ignorance.  DEC made major efforts (and spent about $500 million - which wasF a substantial chunk of money at that time) trying to compete in the PCK space, and was thwarted by its own manufacturing excellence - which was the H prime contributor to a product cost that could not compete directly withJ IBM's.  It took quite a few more years before DEC could even come close toD PC-level box costs, and by that time Rainbow and Pro were long gone.   - bill   ------------------------------  $ Date: Sat, 5 Oct 2002 20:11:58 -0400* From: "Bill Todd" <billtodd@metrocast.net>! Subject: Re: OpenVMS is strategic 6 Message-ID: <71udnQLnx6Zd4gKgXTWcrg@News.GigaNews.Com>  : "Brian 'Jarai' Chase" <bdc@world.std.com> wrote in message  news:H3J7BH.ACs@world.std.com...   ...    > The L > PDP-8 based DECmate and DECmate-II, the PDP-11 based DEC Professional, andJ > the 8086 based DEC Rainbow.  Had they concentrated on just one of those,K > and priced it significantly below IBM's PC, I'd imagine DEC would've have  > been much more successful.  K That couldn't have happened at the time, because DEC simply didn't know how I to build hardware that cheaply:  if it had sold its products at the price K IBM charged for its PC, it would have lost quite a bit of money on each one  (well, maybe not the DECmate).   > J > As opposed to looking at the PC market as a dramatic change in computingI > philosophy, the indications seem to be that they saw it as just another 5 > opportunity to extend their existing product lines.   I Actually, neither.  The PC was clearly something different (a single-user L machine that wasn't dedicated to some specific task, used by a non-technicalJ person), but DEC didn't see it as the major threat to its existing line-upK that it was (though some of us did) and thus tried to make sure that its PC L products didn't compete directly with its traditional products (I don't knowL if that was the first example of the rule that if you don't cannibalize yourJ own products your competition will, but it significantly predated my first exposure to that maxim).   > L > The truly sad thing here is that DEC already had everything they needed toC > completely dominate the personal computing industry.  They had an L > established name, they had great lines of 12-bit and 16-bit CPUs, they hadF > OSes like RT-11 which certainly could've competed with MS-DOS.  TheyI > practically dominated the educational markets with their larger PDP-11, J > PDP-10, and VAX systems.  These would've been good avenues to pursue theD > introduction of affordable computing to students and faculty.  DECL > obviously had the ability to adapt their technologies into low-end systems+ > without investing much additional effort.   K Into low-end systems, yes - but DEC was already doing that to at least some H degree.  PCs were (as noted above) a different proposition, and required4 significant work to make usable by computer novices.  K DEC arguably could have done this in the late '70s and captured the market. J But it lost this opportunity as soon as IBM entered the arena, because theI IBM PC almost immediately became perceived as the standard (regardless of F how pitiful a standard it was) and all subsequent attempts (except forK 'compatibles') immediately became niche products.  It's still arguable that C DEC could have established significant presence in such niches (the C PDP-11-based PRO supported transparent distributed file sharing for J office-style networks - plus traditional DECnet access as well - at a timeI when *any* networking on the IBM PC was something to be marveled at), but K when the products failed to compete directly with the IBM standard DEC then K decided that VAX was the future, even on the desktop (really, really stupid K move, that:  the production economics made it clear that VAX was at least 5 I years away from being able to compete cost-effectively with the 11 on the G desktop, let alone compete with the 386, so the only smart choices were G between dropping the 11 desktop effort and embracing the 386 as a close E member of the family or pursuing a dual PDP-11/386 desktop strategy).    - bill   ------------------------------   Date: 6 Oct 2002 07:13:47 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen) ! Subject: Re: OpenVMS is strategic 3 Message-ID: <mQsUIFGmNTIx@eisner.encompasserve.org>   l In article <3D9749E6.20808@mail.tele.dk>, Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne.vajhoej@mail.tele.dk> writes:  ; > My very subjective feeling is that repeatedly bashing of  7 > Digital/Compaq/HP senior management has absolutely no 7 > effect on the decisions made - and basicly just lower * > the signal to noise ratio in this forum. > 8 > The same JF's post about SMTP logicals is on the other5 > hand very interesting and what actually make people  > read this forum !   A But those of us who have killfiled his posts due to the incessant / drone of politics will hever see the SMTP post.    ------------------------------   Date: 6 Oct 02 10:50:42 +0200 ) From: p_sture@elias.decus.ch (Paul Sture) 4 Subject: Re: Originator of detached process from DCL) Message-ID: <FFp$93nb7Rvo@elias.decus.ch>   P In article <00A14FDE.8708C91E@SendSpamHere.ORG>, system@SendSpamHere.ORG writes:W > In article <Ink5Zcq0ZmCR@elias.decus.ch>, p_sture@elias.decus.ch (Paul Sture) writes: ^ >>In article <3D9DF5EA.9FE73534@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: >>> tironef@yahoo.com wrote:E >>>> I'm trying to determine which process or application created the F >>>> detached process.  This job can be just submitted or created as aK >>>> detached process from a process named ABATEMGR.  If my job is run from 1 >>>> ABATEMGR, I need to do additional procssing.  >>> 	 >>> ouch.  >>> Q >>> Can ABATEMGR be modified ? If so, then ABATEMGR could "pass a message" to the Q >>> detacted process to indicate it should do the extra processing. One way to do $ >>> this is to use the process name. >>>  >> >>But not terribly secure. >>K >>> I.E. when ABATEMGR creates the detached process, it specifies a special N >>> process name. And when the detached process starts , it checks its processM >>> name to see if it is the special keyword and if so, then does the special B >>> processing and then renames itself to a standard process name. >>> N >>> I am not really sure it is possible for a detached process to know who its >>> parent is. >>  >>How about something like this? >>1 >>1. Master process creates the detached process. = >>2. Master then creates a mailbox using the pid of the newly 2 >>   detached process as part of the mailbox name.C >>3. Master places a message in the mailbox indicating the "owner". A >>4. Detached process reads the mailbox to determine the "owner". A >>5. Detached process writes back to the mailbox with status, and  >>   closes it. , >>6. Master reads status and closes mailbox. >> >>--   >>Paul Sture
 >>Switzerland  >  > L > For that matter, assuming the original poster can modify the programs and F > there are sufficient privies to so so, why not do the equivalent of: > N > $ DEFINE/TABLE=LNM$JOB_{detached_JIB_address} PROGENITOR 'F$getjpi("","PID") >  > after creating the process.   I Granted, I did rather assume the original poster can modify the programs.   I But assuming that the creating process has sufficient privs to modify the I job table of the created process, that could be a simpler solution in the F case of the detached process. However, in the case of a submitted job,B in both our suggestions there is the extra loop of translating theE job number into a pid, and potential timing issues for the batch case 0 (batch queue over the job limit or not running).  C Re-reading the first paragraph above leads me to wonder if only the G privileged process is run as detached, with non-privileged ones running > via submit. If this is indeed _always_ the case then a simpler> differentiator is whether F$MODE() returns "OTHER" or "BATCH".   --  
 Paul Sture Switzerland    ------------------------------    Date: 06 Oct 2002 01:20:44 +0800, From: Paul Repacholi <prep@prep.synonet.com>U Subject: Re: Proposal: Retirement of some Components of the Compaq C++ Class  Library - Message-ID: <87fzvkkdjn.fsf@prep.synonet.com>   , krblock@computer.org (Kenneth Block) writes:  E > > Have you considered depreciating the interfaces and removing them : > > from the documentation while leaving them in the code?   C > Absolutely, but to get the cost savings of not having to continue C > qualifing and porting, removal is necessary. Retirement is a long ) > process, deprecation is the first step.   D Cost saving? If there is significant cost saving, it will be becauseA you are not using automated testing... If you have, then you will  possibly save about $10.  D $TRANLOG (?) was retired 20 years ago. It is still there and workingD on Vaxes. So any code that was untouched still worked. Of course, inB the modern world, working customer code is worth nothing at all...     --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 06 Oct 2002 10:45:29 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>U Subject: Re: Proposal: Retirement of some Components of the Compaq C++ Class  Library ) Message-ID: <3D9FF829.5050604@vajhoej.dk>    Paul Repacholi wrote:   F > $TRANLOG (?) was retired 20 years ago. It is still there and workingF > on Vaxes. So any code that was untouched still worked. Of course, inD > the modern world, working customer code is worth nothing at all...  2 $TRNLOG and it is still present on Alpha as well !   Arne   ------------------------------   Date: 6 Oct 2002 10:26:19 -0700 & From: jordan@ccs4vms.com (Rich Jordan)@ Subject: Sony 40/12/48 CD-RW IDE usable wih CDRecord on OpenVMS?= Message-ID: <cc5619f2.0210060926.14896291@posting.google.com>   ? Office Depot has a Sony 40x/12x/48x IDE burner for $39.99 after E multiple rebates.  Has anyone by chance tried one of these in a Alpha F PWS with VMS and a recent version of CDRecord?  My current SCSI YamahaD 6416 is becoming a bottleneck for some things, and I want to replaceF the current IDE CDROM with SCSI (probably on a KZPAA controller ratherA than on the embedded UWSCSI bus), so putting a burner that is not = trying to serve as the system CD reader on IDE would be fine.   F End setup would have disks on the embedded bus, the IDE CD-RW, and theF SCSI CDROM and a tape drive on the KZPAA, assuming the Sony is usable.   Rich Jordan    ------------------------------  % Date: Sun, 06 Oct 2002 05:57:41 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> . Subject: TPU access to DCL symbols or logicals+ Message-ID: <3DA00911.5B1BAFD@videotron.ca>   E Looked in Google, and it seemed that back in the early 1990s, Digital R engineers were aware of a big need to give TPU procedures access to logical names.  Q Current documentation isn't very obvious  if such a feature was added since then.   K So, apart from writing my own TPU$CALL_USER routine that translates symbols L (or logicals), are there other ways for a TPU procedure to access either DCL symbols or logical names ?  F My goal is to setup a bunch of information in DCL, and then invoke TPUK non-interactively to effect changes to a variety of files to help configure M software etc. Doing it this way means that the installation procedure is more ) independant of the format of those files.   K I realise that the DCL could just write a temporary file that would contain K the TPU command to define various symbols, and then the TPU procedure would I just call that file prior to making all the changes to the various files.   4 Just wondering if there are better ways of doing it.   ------------------------------  % Date: Sun, 06 Oct 2002 18:41:50 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>2 Subject: Re: TPU access to DCL symbols or logicals) Message-ID: <3DA067CE.3000603@vajhoej.dk>    JF Mezei wrote:   G > Looked in Google, and it seemed that back in the early 1990s, Digital T > engineers were aware of a big need to give TPU procedures access to logical names. > S > Current documentation isn't very obvious  if such a feature was added since then.  > M > So, apart from writing my own TPU$CALL_USER routine that translates symbols N > (or logicals), are there other ways for a TPU procedure to access either DCL > symbols or logical names ?  0 I still use CALL_USER to translate logicals with in my XEVE.   , SYS$EXAMPLES:EVE$FILE.TPU uses the following hack: '     file_parse (logical, "", "", NAME);   0 If the feature was added then we are some people that missed the announcement !   Arne   ------------------------------   Date: 6 Oct 2002 02:04:02 -0600 B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)" Subject: Re: UCX security advisory3 Message-ID: <ECBuqauTtUa+@eisner.encompasserve.org>   U In article <mr2Def+RygEe@elias.decus.ch>, p_sture@elias.decus.ch (Paul Sture) writes: n > In article <20020930070908.6365.qmail@nym.alias.net>, Doc.Cypher <Use-Author-Address-Header@[127.1]> writes: >>  $ >> Or - as was the case here - http. >>   > 	 > Indeed.  >   ; Erm, people, the POP protocol is not layered on HTTP... :-)    Simon.   --  B Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       + Microsoft: The Lada of the computing world.    ------------------------------   Date: 6 Oct 2002 13:13:29 -0000 4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>" Subject: Re: UCX security advisory5 Message-ID: <20021006131329.1671.qmail@nym.alias.net>   K On 6 Oct 2002, clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)  wrote:G >In article <mr2Def+RygEe@elias.decus.ch>, p_sture@elias.decus.ch (Paul  >Sture) writes: C >> In article <20020930070908.6365.qmail@nym.alias.net>, Doc.Cypher . >> <Use-Author-Address-Header@[127.1]> writes: >>> % >>> Or - as was the case here - http.  >>>  >>  
 >> Indeed. >>   > < >Erm, people, the POP protocol is not layered on HTTP... :-)  K I know, but HTTP was a nice *big* hole in my security. At least the UCX bug < required an attacker to have an account on the system first.     Doc. --  6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.net    ------------------------------   Date: 6 Oct 2002 05:11:52 -0700 # From: dooleys@snowy.net.au (dooley) ' Subject: Re: Version control on OpenVMS = Message-ID: <1ca82fc6.0210060411.68d27f60@posting.google.com>   u "Yong Liu" <fdu9774@rogers.com> wrote in message news:<RBMk9.121200$U_.99583@news04.bloor.is.net.cable.rogers.com>...  > Hi,  > N > WE have codes scattered on OpenVMS, UNIX and OpneVMS. The question is how toL > build a central version control repository. Which version control softwareM > do you use to address this problem? Is the software deal with heterogeneity H > or you have some arangement to deal with it. If so, how did you do it? > ThanksE If you are looking at an open solution and you need to manage a large C code base then have a look at http://research.compaq.com/SRC/vesta/ C I have not used this, but came across it when looking for tools for  "configuration management".  Phil   ------------------------------  # Date: Sun, 06 Oct 2002 01:04:56 GMT $ From: winston@SSRL.SLAC.STANFORD.EDU* Subject: Re: WASD Security Advisory Issued8 Message-ID: <00A15022.2CF3BC0A@SSRL04.SLAC.STANFORD.EDU>  d In article <ano1be$fhqe2$1@ID-135708.news.dfncis.de>, bill@gw5.cs.uofs.edu (Bill Gunshannon) writes:* >In article <2zru26hpTRY4@elias.decus.ch>,- >	p_sture@elias.decus.ch (Paul Sture) writes:  >>  * >> Attack reproduced, on my username file: >>   >> $ dir sysuaf/da/siz=all >>    >> Directory SYS$COMMON:[SYSEXE] >>  @ >> SYSUAF.DAT;2               4/18        5-OCT-2002 10:51:13.20@ >> SYSUAF.DAT;1              54/54       27-OCT-2000 17:35:16.22 >>  " >> Total of 2 files, 58/72 blocks. >> $ set host 0  >>  @ >>  Welcome to OpenVMS (TM) Alpha Operating System, Version V7.3 >>   >> Username: test , >> Error accessing system authorization file >> Invalid record size6 >> %REM-S-END, control returned to node LOCAL:.MYBOX:: >> $ >>  H >> Yes, a denial of service, but easy to fix, as it hasn't destroyed the >> original version. >>   >  >Question. (seriously) > B >UI do not know exactly what this exploit is all about as I don't2 >have a VMS machine available to play with but.... > F >Once the UAF has been overwritten can the exploit be repeated or does9 >it immediately prevent any further access to the system?   G Repeated.  Once you're logged in the process will stay in place without  referring back to the UAF.  I >Assuming it can be repeated, could the attacker not just run the exploit F >a few dozen times in rapid succession until the real UAF file (or anyI >other important system file) ran out of allowed versions and deleted the  >important file.  N That only works if you have version limits set on your important system files, which you typically don't.    K If version limits aren't set, the oldest version doesn't go away by itself; M RMS just declines to create version 32768.  (So you'd have to run the exploit 5 more than a few dozen times to cause that to happen.)    -- Alan    ------------------------------   Date: 6 Oct 02 14:45:34 +0200 ) From: p_sture@elias.decus.ch (Paul Sture) * Subject: Re: WASD Security Advisory Issued) Message-ID: <OL4Sza8oM$Id@elias.decus.ch>   d In article <ano1be$fhqe2$1@ID-135708.news.dfncis.de>, bill@gw5.cs.uofs.edu (Bill Gunshannon) writes:+ > In article <2zru26hpTRY4@elias.decus.ch>, . > 	p_sture@elias.decus.ch (Paul Sture) writes: >>  * >> Attack reproduced, on my username file: >>   >> $ dir sysuaf/da/siz=all >> O  >> Directory SYS$COMMON:[SYSEXE] >> u@ >> SYSUAF.DAT;2               4/18        5-OCT-2002 10:51:13.20@ >> SYSUAF.DAT;1              54/54       27-OCT-2000 17:35:16.22 >>  " >> Total of 2 files, 58/72 blocks. >> $ set host 0  >> l@ >>  Welcome to OpenVMS (TM) Alpha Operating System, Version V7.3 >>   >> Username: test , >> Error accessing system authorization file >> Invalid record size6 >> %REM-S-END, control returned to node LOCAL:.MYBOX:: >> $ >>  H >> Yes, a denial of service, but easy to fix, as it hasn't destroyed the >> original version. >> t >  > Question. (seriously)m > A > I do not know exactly what this exploit is all about as I don'tO3 > have a VMS machine available to play with but....  >   D The problem was that using the -l switch, a logfile could be createdB anywhere on the system, under any name you liked. The fix disables the -l switch.   G > Once the UAF has been overwritten can the exploit be repeated or doesn: > it immediately prevent any further access to the system?J > Assuming it can be repeated, could the attacker not just run the exploitG > a few dozen times in rapid succession until the real UAF file (or any-J > other important system file) ran out of allowed versions and deleted the > important file.c >   < Yes it can be repeated, provided the user remains logged on.C If a privileged user is logged on, they can fix the problem; if nott4 then booting from CD is probably the best way to go.  @ Of course on my home system I have an overnight job which purgesB the whole system back to 10 versions, so I need to review that ...  @ I myself don't like imposing version limits on files, preferringB to have it under my control - for example that overnight batch jobD uses PURGE/LOG so that I have a record of what was deleted and when.  A I'd definitely recommend that the system directories *don't* have  version limits.v   -- h
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 06 Oct 2002 05:00:52 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca>c4 Subject: Which UIC to use for a product's username ?, Message-ID: <3D9FFBBF.FA8C2B7C@videotron.ca>  L Ok, say I am developping a product that requires a username to be created on
 the VMS node.e  K what is the best/politically correct way to determine which UIC and name toaK use ? Should the installation procedure just create a fixed username with aoN fixed UIC, hoping there is no conflict, or should it ask the system manager in+ which UIC he'd like that account created ? g  N Are there "utility" groups that third parties can use for their product ?  AreF there any standards in terms of UIC usage (egL is there a range of UICM reserves for software/servers etc ? or does that vary significantly from siteE	 to site ?h  M Are there guidelines that writers of installation procedures should follow to M provide the software with a username acceptable to the system manager (and too the software) ?b   (this would be with VMSinstal)   ------------------------------  $ Date: Sun, 6 Oct 2002 13:10:43 +0200$ From: Michael Unger <unger@decus.de>8 Subject: Re: Which UIC to use for a product's username ?* Message-ID: <00A150C2.3D399A6C.4@decus.de>  0 "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote:  C > Ok, say I am developping a product that requires a username to bel
 created on > the VMS node.l > E > what is the best/politically correct way to determine which UIC and@ name tocF > use ? Should the installation procedure just create a fixed username with aE > fixed UIC, hoping there is no conflict, or should it ask the system 
 manager in, > which UIC he'd like that account created ?  B I suppose to use usernames of the format "XYZ$username" is "commonA standard" with "XYZ" being the company's/supplier's name. The UICsE group itself should be determined by the system manager, i.e., he hasV to be asked about that.e   >gA > Are there "utility" groups that third parties can use for theirS product ?  AreD > there any standards in terms of UIC usage (egL is there a range of UICdE > reserves for software/servers etc ? or does that vary significantly 	 from site- > to site ?-  / It does vary of course -- significantly ... :-)_   >@E > Are there guidelines that writers of installation procedures should)	 follow toD? > provide the software with a username acceptable to the systemv manager (and to= > the software) ?F >=  > (this would be with VMSinstal)  D Even if the username is pre-determined by the installation procedureF the system manager should be asked for acceptance and given the chance: of changing the username if (s)he feels declined to do so.   Michaelo   ------------------------------   Date: 6 Oct 02 15:26:38 +0200 ) From: p_sture@elias.decus.ch (Paul Sture)e8 Subject: Re: Which UIC to use for a product's username ?) Message-ID: <uX$hcZJ6FkE0@elias.decus.ch>   \ In article <3D9FFBBF.FA8C2B7C@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:N > Ok, say I am developping a product that requires a username to be created on > the VMS node.i > M > what is the best/politically correct way to determine which UIC and name to M > use ? Should the installation procedure just create a fixed username with aaP > fixed UIC, hoping there is no conflict, or should it ask the system manager in- > which UIC he'd like that account created ?   > P > Are there "utility" groups that third parties can use for their product ?  AreH > there any standards in terms of UIC usage (egL is there a range of UICO > reserves for software/servers etc ? or does that vary significantly from siteh > to site ?  >  From the Authorize manual:  
 /UIC=value   ...6  < Compaq reserves group 1 and groups 300--377 for its own use.    O > Are there guidelines that writers of installation procedures should follow tonO > provide the software with a username acceptable to the system manager (and top > the software) ?m >   > (this would be with VMSinstal)  9 I've never seen any guidlines except to avoid 300-377 and = anything up to an including MAXSYSGROUP. I'd avoid [200,*] as 5 well, since that's the default when adding usernames.g   --  
 Paul Sture Switzerlanda   ------------------------------  * Date: Sun, 6 Oct 2002 16:40:42 +0000 (UTC), From: "Richard Maher" <maher_rj@hotmail.c0m>8 Subject: Re: Which UIC to use for a product's username ?/ Message-ID: <anpp28$gu8$1@paris.btinternet.com>t   Hi,   E On a pre-emptive note, I listen intently to almost everything StephenuK Hoffman has to say but when it comes to VMSINSTAL he is completely wrong. IoH doubt that the alternative (polycenter?) will be around much longer. How$ much does support of that crap cost?  J As others have already advised, simply ask the system manager for a uniqueL UIC at instalation time. I used to use [1,4] but all sorts of security toolsD spew up at multiple usernames having this (or any other) system UIC.  G When it comes to registering your facility code the Developers Guide torI VMSINSTAL (which can be found in the obsolete products section of the VMS-G doc set) had an appendix E (iirc) that led me (ok eventually) to a verySI helpful lady who advised me how to register TIER3 as a product and my T3$0K facility code. I won't publish her name here (in case she gets swamped) buta5 if worst comes to worst just open a help log with HP.    Regards Richard Maher.  # PS. Here is an example if it helps.o  L !***************************************************************************	 *********o !* *uI !*         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALL RIGHTS RESERVED.r *  !* * K !*    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED 	 ONLY    * L !*    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH LICENSE AND  WITH THE    *J !*    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE  OR ANY
 OTHER    *K !*    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISE MADE AVAILABLE  TO  ANY    *H !*    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE  SOFTWARE  IS HEREBY    *- !*    TRANSFERRED. *c !* *2L !*    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TO CHANGE WITHOUT NOTICE AND    *D !*    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3 SOFTWARE LTD. *t !* * G !*   8-Feb-1999   RJM   V2-001   Use $persona system services to createa
 servers     *eK !*                               under the required username.  T3$SETENV ise	 now     *p+ !*                               redundant.  *IK !*                               T3$EXESRV.COM now needs world read access.  *-L !*                               TIER3$SERVER now needs DETACH privilege for the    *: !*                               $PERSONA system services. *sG !*                               No privileged images left to register.i *iL !***************************************************************************	 *********S !*+D) !* Facility: TIER3 Installation Procedure  !* $!, $   ON CONTROL_Y THEN VMI$CALLBACK CONTROL_Y  $   ON WARNING THEN EXIT $STATUS $! $!  Find out what we are doing $!; $   IF P1 .EQS. "VMI$_INSTALL"      THEN GOTO TIER3_INSTALL ? $   IF P1 .EQS. "VMI$_POSTINSTALL"  THEN GOTO TIER3_POSTINSTALL07 $   IF P1 .EQS. "VMI$_IVP"          THEN GOTO TIER3_IVP : $   IF P1 .EQS. "HELP_ACCOUNT"      THEN GOTO HELP_ACCOUNT $   EXIT VMI$_UNSUPPORTED0 $! $TIER3_INSTALL:o $!A $!  TIER3 creates a SYSUAF account, so has to be installed on theh1 $!  system disk. ie no alternate root is allowed.! $!B $   IF F$TRNLNM("VMI$ALTERNATE_ROOT") .EQS "" THEN GOTO CHECK_ARCH $   TYPE SYS$INPUT  <             TIER3 V2.0 must be installed on the system disk.  E  You can not specify an alternate root directory when installing this, product.   $   EXIT VMI$_FAILUREa $! $CHECK_ARCH: $!& $!  Make sure we are running on a VAX. $!: $   IF F$GETSYI("ARCH_TYPE") .EQ. 1 THEN GOTO CHECK_VMSVER $   TYPE SYS$INPUT  ?         This installation kit is not compatible with Alpha AXP.c  =           You can only install TIER3 V2.0 on VAX/VMS systems.,   $   EXIT VMI$_FAILURE  $! $CHECK_VMSVER: $!% $!  Check VMS version. We need >= 6.2- $!3 $   VMI$CALLBACK CHECK_VMS_VERSION TIER3$VMSVER 6.2y* $   IF TIER3$VMSVER THEN GOTO CHECK_GBLPAG& $   VMI$CALLBACK MESSAGE E BADVMSVER -A $   "TIER3 V2.0 requires OpenVMS version 6.2 or later to install"9 $   EXIT VMI$_FAILUREt $! $CHECK_GBLPAG: $   TIER3$GBLPAG_FREE == 0E $   VMI$CALLBACK GET_SYSTEM_PARAMETER TIER3$GBLPAG_FREE FREE_GBLPAGES<8 $   IF TIER3$GBLPAG_FREE .GE. 150 THEN GOTO CHECK_GBLSEC& $   VMI$CALLBACK MESSAGE E INSGBLPAG -@     "This version of TIER3 requires 150 global pages to install" $   EXIT VMI$_FAILURE  $! $CHECK_GBLSEC: $   TIER3$GBLSEC_FREE == 0E $   VMI$CALLBACK GET_SYSTEM_PARAMETER TIER3$GBLSEC_FREE FREE_GBLSECTSc7 $   IF TIER3$GBLSEC_FREE .GE. 15 THEN GOTO CHECK_COBRTLx& $   VMI$CALLBACK MESSAGE E INSGBLSEC -B     "This version of TIER3 requires 15 global sections to install" $   EXIT VMI$_FAILUREp $! $CHECK_COBRTL: $!" $!  Check COBRTL is V5.4 or higher $!3 $   VMI$CALLBACK CHECK_PRODUCT_VERSION TIER3$COBRTL)) VMI$ROOT:[SYSLIB]COBRTL.EXE V5.4 "COBRTL"o0 $   IF .NOT. TIER3$COBRTL THEN EXIT VMI$_FAILURE $! $CONFIRM_LICENSE:b $! $   TYPE SYS$INPUT  @       You *MUST NOT* install TIER3 unless you have been licensed@       to use this product on this machine by Tier3 Software Ltd.  5       Do not continue with this installation unless:-C  B       a) Tier3 Software Ltd has issued you with a valid license to#          use TIER3 on this machine. D       b) You accept the terms and conditions of the end user license          agreement.   $ $   VMI$CALLBACK ASK TIER3$LICENSE -:     "Do you want to continue with the installation" NO B -I     "Contact Tier3 Software Ltd if you are unsure of your license status" 1 $   IF .NOT. TIER3$LICENSE THEN EXIT VMI$_FAILUREe $   GOTO CHECK_DISKy $!: $   VMI$CALLBACK CONFIRM_LICENSE TIER3$LIC TIER3 MAHER 2.0 23-AUG-1999:00:00:00.00y( $   IF TIER3$LIC THEN GOTO CHECK_LICENSE $   TYPE SYS$INPUT  I       You must register and load a TIER3 Product Authorization Key beforeh       installing this product.   $   EXIT VMI$_FAILUREk $! $CHECK_LICENSE:  $!; $!  VMI$CALLBACK CHECK_LICENSE TIER3$EXISTS TIER3 MAHER 2.0u 23-AUG-1994:00:00:00.00 Si9 $   VMI$CALLBACK CHECK_LICENSE TIER3$EXISTS COBOL DEC 5.0b 23-AUG-1994:00:00:00.00o( $   IF TIER3$EXISTS THEN GOTO CHECK_DISK $! $   TYPE SYS$INPUT  F         A license for this product has not been registered and loaded.  4                         TIER3 will not be installed.   $   EXIT VMI$_FAILUREn $! $CHECK_DISK: $!) $!  Check that there is enough disk spaceC $!A $   VMI$CALLBACK CHECK_NET_UTILIZATION TIER3$SPACE 5800 2800 3000p/ $   IF .NOT. TIER3$SPACE THEN EXIT VMI$_FAILURE1 $!" $!  Get IVP and purge confirmation $!$ $   VMI$CALLBACK SET IVP         ASK& $   VMI$CALLBACK SET PURGE       ASK H$ $   VMI$CALLBACK SET POSTINSTALL YES $! $!  See if TIER3$SERVER exists.t $!2 $   VMI$CALLBACK RUN_IMAGE "VMI$KWD:T3$CHKACC.EXE" $   IF TIER3$MISSING $   THEN, $           TIER3$ACTION == "CREATE_ACCOUNT" $           GOTO GET_UIC	 $   ENDIFi$ $   TIER3$ACTION == "UPDATE_ACCOUNT" $   TIER3$QUAL = "", $   TYPE SYS$INPUT  E     The username TIER3$SERVER already exists in the SYSUAF file. Thist4     account will be overwritten during installation.  % $   VMI$CALLBACK ASK TIER3$CONTINUE - ;     "Do you want to continue with the installation" YES B -s%     "@VMI$KWD:KITINSTAL HELP_ACCOUNT" 2 $   IF .NOT. TIER3$CONTINUE THEN EXIT VMI$_FAILURE $   GOTO NO_QUESTIONSw $!	 $GET_UIC:a $!  $   VMI$CALLBACK ASK TIER3$UIC -D     "Enter the TIER3 server account UIC code [Group,Member]" "" D  -F     "This UIC is used for TIER3$SERVER, the TIER3 communication server account"+ $   IF TIER3$UIC .EQS. "" THEN GOTO GET_UICb1 $   TIER3$QUAL = "/ADD_IDENTIFIER/UIC="+TIER3$UIC  $! $NO_QUESTIONS: $! $   TYPE SYS$INPUT  =     No more questions will be asked during this installation.c   $!L $!  Create the communication server account. Have to do it in 3 steps due to DCL 255 byte restriction.u $! $   TIER3$NULL = """"""n) $   TIER3$OWNR = """Tier3 Software Ltd"""e $   TIER3$PRIV =L "(SYSNAM,SYSPRV,CMEXEC,CMKRNL,TMPMBX,NETMBX,ALTPRI,DETACH,SECURITY,AUDIT,SYS GBL)"u $   TIER3$QUAL = TIER3$QUAL +eD "/FLAGS=(NODISUSER,NOCAPTIVE,NODISIMAGE,NOPWD_EXPIRED,NORESTRICTED)" $   TIER3$QUAL = TIER3$QUAL +n@ "/ACCOUNT=TIER3/PRIORITY=6/NOACCESS/DEFPRIVILEGES=" + TIER3$PRIV8 $   VMI$CALLBACK 'TIER3$ACTION' TIER3$SERVER 'TIER3$QUALK $   TIER3$QUAL = "/PRIVILEGES=" + TIER3$PRIV + "/NOEXPIRATION/NOPWDEXPIRED"  $   TIER3$QUAL = TIER3$QUAL +r? "/ASTLM=20000/BIOLM=32767/DIOLM=32767/BYTLM=480000/ENQLM=32767"o $   TIER3$QUAL = TIER3$QUAL +e4 "/MAXJOBS=0/MAXACCTJOBS=0/MAXDETACH=0/NOPWDLIFETIME"8 $   VMI$CALLBACK UPDATE_ACCOUNT TIER3$SERVER 'TIER3$QUAL $   TIER3$QUAL =J "/FILLM=16000/PGFLQUOTA=400000/WSDEFAULT=4096/WSEXTENT=16384/WSQUOTA=8192"D $   TIER3$QUAL = TIER3$QUAL + "/OWNER=" + TIER3$OWNR + "/TQELM=5000" $   TIER3$QUAL = TIER3$QUAL +e> "/DEVICE=SYS$SYSROOT:/DIRECTORY=[SYSMGR]/LGICMD=" + TIER3$NULLF $   TIER3$QUAL = TIER3$QUAL + "/CPUTIME=0/CLI=DCL/CLITABLES=DCLTABLES"8 $   VMI$CALLBACK UPDATE_ACCOUNT TIER3$SERVER 'TIER3$QUAL $! $MOVE_FILES: $!0 $!  Set up SYS$SHARE, SYS$LIBRARY and SYS$SYSTEM $!5 $   VMI$CALLBACK PROVIDE_IMAGE "" IMAGES.PROVIDE "" TGF $   VMI$CALLBACK SECURE_FILE TIER3_PRIVATE "" S:RWED,O:RWED,G:RWED,W:ED $   VMI$CALLBACK SECURE_FILE TIER3_COMSRV  "" S:RWED,O:RWED,G:RWED,WD $   VMI$CALLBACK SECURE_FILE TIER3_CONFIG  "" S:RWED,O:RWED,G:RWED,W $!4 $!  Copy over the input files for detached processes $!5 $   VMI$CALLBACK PROVIDE_FILE  "" INPUT.PROVIDE  "" T'D $   VMI$CALLBACK SECURE_FILE TIER3_COMSRV  "" S:RWED,O:RWED,G:RWED,WF $   VMI$CALLBACK SECURE_FILE TIER3_EXESRV  "" S:RWED,O:RWED,G:RWED,W:RF $   VMI$CALLBACK SECURE_FILE TIER3_DBGSRV  "" S:RWED,O:RWED,G:RWED,W:R $!/ $!  Create and populate the examples directory.b $!A $   TIER3$EGDIR = F$SEARCH("VMI$ROOT:[SYSHLP.EXAMPLES]TIER3.DIR")p2 $   IF TIER3$EGDIR .NES. "" THEN GOTO EGDIR_EXISTS> $   VMI$CALLBACK CREATE_DIRECTORY COMMON SYSHLP.EXAMPLES.TIER3 $! $EGDIR_EXISTS:6 $   VMI$CALLBACK PROVIDE_FILE "" EXAMPLES.PROVIDE "" T $! $!  Setup startup procedure  $!J $   VMI$CALLBACK PROVIDE_FILE TIER3_ T3$STARTUP.COM VMI$ROOT:[SYS$STARTUP]+ $   VMI$CALLBACK SET STARTUP T3$STARTUP.COMc $! $!  Setup IVP proceduree $!: $   TIER3$IVPDIR = F$SEARCH("VMI$ROOT:[SYSTEST]TIER3.DIR")4 $   IF TIER3$IVPDIR .NES. "" THEN GOTO IVPDIR_EXISTS6 $   VMI$CALLBACK CREATE_DIRECTORY COMMON SYSTEST.TIER3 $! $IVPDIR_EXISTS:oL $   VMI$CALLBACK PROVIDE_FILE  TIER3_ T3$IVP.COM    VMI$ROOT:[SYSTEST.TIER3]L $   VMI$CALLBACK PROVIDE_IMAGE TIER3_ T3$CHKACC.EXE VMI$ROOT:[SYSTEST.TIER3] $   TYPE SYS$INPUT  7     The IVP has been moved to directory [SYSTEST.TIER3]a  B     To invoke the IVP, enter @SYS$COMMON:[SYSTEST.TIER3]T3$IVP.COM   $! $TIER3_POSTINSTALL:y $!, $!  We don't do anything here at the moment. $! $   EXIT VMI$_SUCCESS  $! $TIER3_IVP:l $!' $   @VMI$ROOT:[SYSTEST.TIER3]T3$IVP.COMi $   EXIT $STATUS $! $HELP_ACCOUNT: $! $   TYPE SYS$INPUT  F     In order to operate correctly, TIER3 requires exclusive use of theH     TIER3$SERVER account. As this account already exists on your system,C     you are being asked to verify that it was created by a previouseG     installation of TIER3 and that you wish to have the account profile '     updated with the latest parameters.u  H     If the TIER3$SERVER account is in use by another application or userF     then you should delay the installation of this product until TIER37     can be guaranteed exclusive access to this account.e   $   exit $!    8 Larry Kilgallen <Kilgallen@SpamCop.net> wrote in message- news:lnmiZ6oPG7M6@eisner.encompasserve.org... K > In article <00A150C2.3D399A6C.4@decus.de>, Michael Unger <unger@decus.de>o writes: 4 > > "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote: > > F > >> Ok, say I am developping a product that requires a username to be > > created on > >> the VMS node. > >>H > >> what is the best/politically correct way to determine which UIC and > > name tolI > >> use ? Should the installation procedure just create a fixed usernamee
 > > with aH > >> fixed UIC, hoping there is no conflict, or should it ask the system > > manager in/ > >> which UIC he'd like that account created ?t > >dF > > I suppose to use usernames of the format "XYZ$username" is "commonE > > standard" with "XYZ" being the company's/supplier's name. The UIChI > > group itself should be determined by the system manager, i.e., he hase > > to be asked about that.o >lE > The XYZ$username is only "legal" if XYZ is a facility name that has / > been registered with HP(nee Compaq(nee DEC)).3 >aH > >> Are there guidelines that writers of installation procedures should
 > > follow toiB > >> provide the software with a username acceptable to the system > > manager (and to@ > >> the software) ? >lE > The registration of facility names is the mechanism for doing this.nC > One problem is that they keep changing the address for doing suchrD > registrations, even faster than they change the company name.  LJKC > Software has the name "LJK" and it is used for multiple products./ >p   ------------------------------   End of INFO-VAX 2002.552 ************************