1 INFO-VAX	Wed, 31 Oct 2001	Volume 2001 : Issue 605       Contents:  Any news on the fix for the XFC? Re: BCC support in VMSMAIL Re: C programming.. , Re: CLD & error handling from within program Re: Compaq blasts HP Re: Compaq financial humour !  Re: Compaq financial humour !  DEC C and DECUS  Re: DEC C and DECUS . DECwindows Motif Server Mandatory Update Patch2 Re: DECwindows Motif Server Mandatory Update Patch3 Re:  DECwindows Motif Server Mandatory Update Patch ! Re: Delta time between two date's ! Re: Delta time between two date's # Re: Equivalent of /etc/hosts in vms $ Re: Equivalent of /etc/hosts in vms. FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: FTP over SSL Re: GBLPAGES in VMS V7.3% Re: half off fire sale on windows xp! % Re: half off fire sale on windows xp! A Re: How to redirect output&error into a single file in sys$creprc : Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX- Re: OT - HP's MPE-IX - and VMS (cross-posted) - Re: OT - HP's MPE-IX - and VMS (cross-posted) - Re: OT - HP's MPE-IX - and VMS (cross-posted)  Re: Printing to NLA0:?& Re: Promotion at Channel Support Group9 Re: Request for help with ANALYZE/ERROR disk error report ! Re: savesets,  CDs and attributes ! Re: savesets,  CDs and attributes % Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM  Re: Unix-based, VMS-based? Re: Unix-based, VMS-based? Re: VMSMail APIs?  Re: VMSMail APIs?  Re: VMSMail APIs?  VT520 Setup  Re: VT520 Setup  Re: VT520 Setup  Weird Hobbyist PAK behavior  Re: Weird Hobbyist PAK behavior  Re: Weird Hobbyist PAK behavior  Re: Weird Hobbyist PAK behavior  Re: Weird Hobbyist PAK behavior . Re: [AMDS V7.3A] Problem on OpenVMS VAX V7.3 ?  F ----------------------------------------------------------------------  # Date: Wed, 31 Oct 2001 03:02:44 GMT $ From: Scott Vieth <svieth@wi.rr.com>) Subject: Any news on the fix for the XFC? & Message-ID: <3BDF6A7C.20901@wi.rr.com>   Hi:   D I'm gettin' ready for the trip from 7.2-1 to 7.3 (Alpha, of course).C Has anyone heard anything on a fix for the XFC?  I searched DSNlink J tonight and didn't find anything new.  The one XFC patch is still on-hold.  C I've got a beautiful new ES40 with oodles of RAM on order and I was E really looking forward to letting the XFC do its thing.  But it looks 3 like I'll be stuck with the stinky old VIOC.... ;^)    -Scott Vieth :^)   ------------------------------  % Date: Tue, 30 Oct 2001 15:25:45 -0500 ; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com> # Subject: Re: BCC support in VMSMAIL $ Message-ID: <3bdf0cc9$1@news.si.com>  H >Well majority have spoken we will have BCC support soon. As soon as the development 4 >work is over I will post a note in this conference.  F Make sure in include OpenVMS VAX as well as Alphas.  Despite what FredK Kleinsorge says, some of us VAX customers want improvements.  After all, we * pay for them with our maintenance dollars. --A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Tue, 30 Oct 2001 14:00:37 -0500 ; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>  Subject: Re: C programming.." Message-ID: <3bdef8d6@news.si.com>  6 >my brain is fried... I need a quick example of how to > E >1) start a program written in C that accepts 1 command line argument    See SYS$EXAMPLES:*.C --  A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Tue, 30 Oct 2001 21:13:45 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 5 Subject: Re: CLD & error handling from within program ' Message-ID: <3BDF6C68.65A217DE@fsi.net>    Michael Zarlenga wrote:  > 2 > David J. Dachtera <djesys.nospam@fsi.net> wrote:D > :> I must be getting forgetful, because as I remember CLD/CLI, badF > :> keywords were trapped by the CLI and the program never sees them. > I > : I suppose that should be true; however, there needs to be some signal I > : passed back so the program knows it should not attempt to process any L > : further and should take appropriate action: either exit or prompt again. > A > In C, as I recall, the image is not even activated when the CLI C > determines there is a problem with the command, such as an unrec- # > ognized qualifier or bad keyword.   G That would be true if the program were defined as anew DCL command (SET G COMMAND ...). I took his query to mean that he was using a compiled CLD / in his image. I may have been wrong about that.    1 > Oh well, no matter.  The poster has a solution.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 30 Oct 2001 15:51:58 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: Compaq blasts HP 3 Message-ID: <MtTxxczQRLCg@eisner.encompasserve.org>   h In article <d7791aa1.0110290937.5509e792@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes:  H > forget emulators ... you will kill roughly half of the cpu ... i had a   Learn to capitalize.   ------------------------------  % Date: Tue, 30 Oct 2001 21:17:45 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> & Subject: Re: Compaq financial humour !' Message-ID: <3BDF6D59.EFAFB948@fsi.net>    "Terry C. Shannon" wrote:  > > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message# > news:3BDE299F.B351F761@fsi.net...  > > "Terry C. Shannon" wrote:  >  > > > > > L > > > Yet another reason to buy a few shares of CPQ while the stock price is > inJ > > > the cellar. One share will get you the coveted ducat that guarantees > accessJ > > > to stockholder meetings. What's more, said ownership will make you aM > > > potential party to any class-action litigation that might rear its head  > > > sometime down the road...  > > 8 > > Hhmmm... is that a hint or possibly a suggestion...? > N > Suggestion only. If I was gonna mount a class action lawsuit, I can think ofL > more deserving targets than Compaq. Cross Country Bank and its vile credit' > card billing practices comes to mind.   F Try MCI/Worldcomm and their despicable telemarketing practices. ArturoH may have stopped it for me through mail we exchanged off-line. Too bad -C a judge would likely have thrown the book at them, had he/she heard F tapes of the MCI arguing with me about their "right to telemarket" (asH opposed to practices which may very well constitute telephone harassment in most states.    K > But ya never know... SOMEONE might see fit to hire a lawyer and start the N > ball rolling. Alternatively, HP might successfully assimilate Compaq. EitherN > way, ten bucks is a cheap price to pay for a seat at the Annual Shareholders
 > Meeting.  @ I'd very likely get either thrown out or arrested (or both!) for) creating a disturbance (inciting a riot).    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Wed, 31 Oct 2001 03:38:36 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>& Subject: Re: Compaq financial humour != Message-ID: <0nKD7.25828$f6.12522933@typhoon.ne.mediaone.net>   < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3BDF6D59.EFAFB948@fsi.net...  > "Terry C. Shannon" wrote:  > > @ > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message% > > news:3BDE299F.B351F761@fsi.net...  > > > "Terry C. Shannon" wrote:  > >  > > > > > > K > > > > Yet another reason to buy a few shares of CPQ while the stock price  is > > inL > > > > the cellar. One share will get you the coveted ducat that guarantees
 > > accessL > > > > to stockholder meetings. What's more, said ownership will make you aJ > > > > potential party to any class-action litigation that might rear its head! > > > > sometime down the road...  > > > : > > > Hhmmm... is that a hint or possibly a suggestion...? > > G > > Suggestion only. If I was gonna mount a class action lawsuit, I can  think ofG > > more deserving targets than Compaq. Cross Country Bank and its vile  credit) > > card billing practices comes to mind.  > H > Try MCI/Worldcomm and their despicable telemarketing practices. ArturoJ > may have stopped it for me through mail we exchanged off-line. Too bad -E > a judge would likely have thrown the book at them, had he/she heard H > tapes of the MCI arguing with me about their "right to telemarket" (asJ > opposed to practices which may very well constitute telephone harassment > in most states.  > I > > But ya never know... SOMEONE might see fit to hire a lawyer and start  the I > > ball rolling. Alternatively, HP might successfully assimilate Compaq.  EitherC > > way, ten bucks is a cheap price to pay for a seat at the Annual  Shareholders > > Meeting. > B > I'd very likely get either thrown out or arrested (or both!) for+ > creating a disturbance (inciting a riot).  > I Could be. ;-} They tried to throw me out last year... claimed I wasn't on I the Approved Press List. Fortunately my Proof of Stock Ownership overrode  the edict of the Door Police.    ------------------------------  % Date: Tue, 30 Oct 2001 15:08:04 -0700 ) From: "DigiDemon" <digidemon@hotmail.com>  Subject: DEC C and DECUS9 Message-ID: <20011030.150804.1605908235.2494@hotmail.com>    Afternoon people.   F First off, thanks for the help with the startup logging....runs like aF champ now :)  Second, 2 questions....I've been trying to to snag a lilC proggie called findlocks.com from DECUS, but to no avail...is there H something up with the site?  Also, i'd like to see what it would take toF do some compiling and linking...I've hit the faqs and sites to try andG find Gnu-C and Gnu-C++ for Alpha: ftp://ftp.progis.de/pub/vms/gcc/, but H that site is dead as well.  Any directions would be just great...thanks!   James    ------------------------------  # Date: Tue, 30 Oct 2001 23:33:38 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: DEC C and DECUS3 Message-ID: <mNGD7.1128$RL6.16439@news.cpqcorp.net>   e In article <20011030.150804.1605908235.2494@hotmail.com>, "DigiDemon" <digidemon@hotmail.com> writes:   = :... Second, 2 questions....I've been trying to to snag a lil D :proggie called findlocks.com from DECUS, but to no avail...is there :something up with the site?    D   Um, what are you up to?  AMDS and Availability Manager and recent E   versions of SDA are all quite good at tracking locks.  Though AMDS  C   and Availability Manager are separately installed kits, they are     licensed with OpenVMS.  , :Also, i'd like to see what it would take to2 :do some compiling and linking...I've hit the faqs  I   If you find errors or dead URLs in the OpenVMS FAQ, please let the FAQ     maintainer know.  Thanks!   C   The vms.gnu.org progis mirror and the pointers at levitte.org are    clearly busted.        According to:   :     http://gcc.gnu.org/onlinedocs/gcc-3.0/gcc_4.html#SEC63  C   and some other discussions, the GNU GCC kit already includes the  D   OpenVMS bits -- what Progis was contributed back into the GCC kit.$   You might download GCC and look...     Also see: 6     http://www.tmk.com/ftp/vms-freeware/gcc-for-alpha/;     http://www.ctrl-c.liu.se/ftp/WKU/VMS/GCC-FOR-ALPHA/7_1/   F   If somebody finds better pointers, please also let the maintainer(s)F   of http://www.levitte.org/~ava/vms_gnu.htmlx know, too.  (I've pokedH   around for new pointers for inclusion into the OpenVMS FAQ, but don't G   see anything useful.  If GCC kit DOES include OpenVMS, please let me  4   know and I'll toss that detail into the next FAQ.)  H :                                                   and sites to try andH :find Gnu-C and Gnu-C++ for Alpha: ftp://ftp.progis.de/pub/vms/gcc/, butI :that site is dead as well.  Any directions would be just great...thanks!   H   If this is a hobbyist system, please enroll into the hobbyist program.G   The hobbyist program gets you Compaq C V6.4.  Please see the OpenVMS     FAQ for details.       N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Wed, 31 Oct 2001 00:24:33 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)7 Subject: DECwindows Motif Server Mandatory Update Patch 3 Message-ID: <5xHD7.1129$RL6.16455@news.cpqcorp.net>   C   There has been a report of a security problem with the DECwindows B   Motif server on various configurations received and identified, 9   and an ECO kit to resolve this has been made available.   F   The work on the associated CERT announcement is in progress -- that ;   and other details should be available circa 1-Nov-2001.     '   The ECO (MUP) kits are available now: 0     ftp://ftp.service.digital.com/public/vms/...  C   And before somebody asks, AFAIK,  OpenVMS VAX Version 5.5-2H4 is     (also) not affected...  G   The attached has been edited slightly, for width and for readability.   N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com     	--   6 OpenVMS DECwindows Motif Server Mandatory Update Patch Frequently Asked Questions 29-October-2001     H Q.  Why is Compaq issuing this Mandatory Update Patch (MUP) for OpenVMS?  = 	This Mandatory Update Patch is being issued in response to a D recent problem report on systems running OpenVMS Alpha, OpenVMS VAX,D SEVMS VAX or SEVMS Alpha with the DECwindows Motif Server installed.C These systems have a potential security vulnerability that could be H exploited to allow existing users unauthorized access to data and system
 resources.  * Q.  What versions of OpenVMS are impacted?  @ 	All supported versions of OpenVMS Alpha, OpenVMS VAX, SEVMS VAXH or SEVMS Alpha have been examined for this vulnerability.  All supportedG versions with the exception of OpenVMS VAX Version V5.5-2 are impacted.    	Supported Versions Impacted: 0 		*	OpenVMS Alpha Version 6.2 and all associatedJ                           hardware releases (for example, Version 6.2-1H1) 		*	OpenVMS Alpha Version 7.1-2 ! 		*	OpenVMS Alpha Version 7.2-1H1  		*	OpenVMS Alpha Version 7.2-2  		*	OpenVMS Alpha Version 7.3  		*	OpenVMS VAX Version 6.2  		*	OpenVMS VAX Version 7.1  		*	OpenVMS VAX Version 7.2  		*	OpenVMS VAX Version 7.3  		*	SEVMS Alpha Version 6.2  		*	SEVMS VAX Version 6.2   ! 	Supported Versions NOT Impacted:  		*	OpenVMS VAX Version 5.5-2   F Q.  Do I still need the patch if I am not running the DECwindows Motif Server on my system?  9 	No.  This patch is only required for systems running the H DECwindows Motif Server.  Installation of the DECwindows Motif Server isF optional during the installation of the OpenVMS Operating System.  YouE may be running the DECwindows Motif Server on your system even if you 5 are not running the DECwindows Motif layered product.   F Q.  How can I tell if I am running the DECwindows Server on my system?  > 	You can verify whether or not the DECwindows Motif Server has= been installed on your system by using the following command:   0 	             $ DIRECTORY SYS$LIBRARY:DECW$*.EXE  7 	If no DECW$*.EXE files are present on your system, thetF DECwindows Motif Server is not installed on your system and you do not$ need to apply this mandatory update.  = Q.  How can I get the patch I need for my version of OpenVMS?t  3 	There are three ways to get copies of the patches.   A 	1) If you have a service contract that provides media updates toeA the OpenVMS Operating System or if you have purchased a media kitmC containing the OpenVMS Operating System from Compaq in the past sixSB months, a CD-ROM containing patches for all impacted versions will2 automatically be shipped to you in early November.  ? 	2) You may download the patches from the World Wide Web at theo following address:  5 	             <http://www.support.compaq.com/patches>f  @ 	At the web site listed above, use the FTP access option, selectE VMS then either the VAX or AXP directory, then choose the appropriatePH version directory and download the patch as identified in the applicable .HTML file accordingly.H  ? 	Note: Please review the README file(s) for each patch prior to'
 installation.T   	The patch filenames are:    		*	OpenVMS ALPHA   . 				o DEC-AXPVMS-VMS73_DW_MOT_MUP-V0100-4.PCSI/ 				o DEC-AXPVMS-VMS722_DW_MOT_MUP-V0100-4.PCSI-1 				o DEC-AXPVMS-VMS721H1_DW_MOT_MUP-V0100-4.PCSId/ 				o DEC-AXPVMS-VMS721_DW_MOT_MUP-V0100-4.PCSI / 				o DEC-AXPVMS-VMS712_DW_MOT_MUP-V0100-4.PCSIo 				o ALPDWMOTMUP01_062.Ai   		*	OpenVMS VAXe   				o VAXDWMOTMUP01_073.Ae 				o VAXDWMOTMUP01_072.Aa 				o VAXDWMOTMUP01_071.AS 				o VAXDWMOTMUP01_062.A   	 		*	SEVMSM   				o SE_VAXDWMOTMUP01_062.A 				o SE_ALPDWMOTMUP01_062.A    ; 	3) Customers who do not automatically receive a CD-ROM and G cannot access the web site kits should contact their local Compaq SalesbE Office to order a CD-ROM containing the patches.  The part number forvB the CD-ROM is QA-MT3AA-T8. There will be a charge for shipping and	 handling.   A Q.  How can I tell if this patch has already been installed on my- system?-  : 	For PSCI kits, use the PRODUCT SHOW HISTORY command.  For example:  2 	$ PRODUCT SHOW HISTORY VMS***_MOT_MUP/VERSION=1.0  0 	--------------------------------------------...0 	PRODUCT                                     ...0 	--------------------------------------------...0 	DEC AXPVMS VMS721H1_DW_MOT_MUP V1.0 Patch   ...0 	--------------------------------------------...  ; 	For VMSINSTAL kits (.A savesets) search for a .TXT file inoE SYS$COMMON:[SYSUPD] that has the same name as the kit.   For example:i  * 	$ DIR SYS$COMMON:[SYSUPD]*DWMOTMUP01*.TXT   	Directory SYS$COMMON:[SYSUPD]   	ALPDWMOTMUP01_62.TXT;1-  ; Q.	Do I need to reboot my system after I install the patch?r  < 	After you apply this update, you must reboot your system inG order for the changes to take effect.   If you have other nodes in your G OpenVMS cluster, they must also be rebooted in order to make use of the E new images.  If it is not possible or convenient to reboot the entireaF cluster at this time, a rolling reboot may be performed.  However, dueD to the nature of the problem that this kit corrects, Compaq stronglyD recommends a rolling reboot be performed immediately on each cluster node.   : 	Q.	Do I need to reapply the patch if I upgrade my version& of the operating system in the future?  ? 	Yes.  If you upgrade to any of the impacted versions, you mustvG apply the patch appropriate to the new version of the operating system.    ------------------------------  % Date: Tue, 30 Oct 2001 21:03:50 -0500-- From: JF Mezei <jfmezei.spamnot@videotron.ca>0; Subject: Re: DECwindows Motif Server Mandatory Update Patchm, Message-ID: <3BDF5C05.45D92D89@videotron.ca>   Hoff Hoffman wrote: H > Q.  How can I tell if I am running the DECwindows Server on my system? > G >         You can verify whether or not the DECwindows Motif Server hasS? > been installed on your system by using the following command:a > 9 >                      $ DIRECTORY SYS$LIBRARY:DECW$*.EXE   N Don't some DECW$ files get installed with VMS  without the DECwindows server ?  E I have had some DECW$ files on my all mighty microvax II ever since I L installed the CDA converter library which required a few of the DECW files..  N Also, when installing VMS, insn't one give the oppportunity to install some ofI the DECwindows support files without installing the whole motif support ?g   ------------------------------    Date: 30 Oct 2001 19:10:46 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett) < Subject: Re:  DECwindows Motif Server Mandatory Update Patch, Message-ID: <AIsJ6zPwZfYA@malvm6.mala.bc.ca>  4 In article <5xHD7.1129$RL6.16455@news.cpqcorp.net>, 7    hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:    > H > Q.  Do I still need the patch if I am not running the DECwindows Motif > Server on my system? > ; > 	No.  This patch is only required for systems running therJ > DECwindows Motif Server.  Installation of the DECwindows Motif Server isH > optional during the installation of the OpenVMS Operating System.  YouG > may be running the DECwindows Motif Server on your system even if youc7 > are not running the DECwindows Motif layered product.  >   ?      What if the files are installed but you aren't running the  server, e.g. you have:  " $ASSIGN "Y" DECW$IGNORE_DECWINDOWS     in SYSTARTUP_VMS.COM.   >     Is it safe to assume this vulnerability is only exposed if  the server is currently running?   ------------------------------  # Date: Wed, 31 Oct 2001 00:05:06 GMT0) From: martin.hunt@inl.co.nz (Martin Hunt)e* Subject: Re: Delta time between two date's7 Message-ID: <3bdf3f48.97822010@news.wlg.netlink.net.nz>o  B On 24 Oct 2001 20:59 CDT, carl@gerg.tamu.edu (Carl Perkins) wrote:    E >Time since last boot (I didn't know this would work until now - it'sl) >pretty spiffy that this actually works):  >e >$ @timediff "boottime"- >0024-04:41:33 >-B New one on me, but I just tried DIR/SINCE=BOOT and guess what - itD shows files created since the last boot. HELP SPECIFY DATE documentsE TODAY and TOMORROW, but BOTTIME is not there. Another thing to add toe4 the list of undocumented commands/keywords, I think.   ------------------------------  % Date: Tue, 30 Oct 2001 21:19:27 -0600o1 From: "David J. Dachtera" <djesys.nospam@fsi.net>n* Subject: Re: Delta time between two date's' Message-ID: <3BDF6DBF.DFA0DF96@fsi.net>r   Martin Hunt wrote: > D > On 24 Oct 2001 20:59 CDT, carl@gerg.tamu.edu (Carl Perkins) wrote: > G > >Time since last boot (I didn't know this would work until now - it'st+ > >pretty spiffy that this actually works):  > >e > >$ @timediff "boottime"  > >0024-04:41:33 > >aD > New one on me, but I just tried DIR/SINCE=BOOT and guess what - it+ > shows files created since the last boot.     What version are you running?    > HELP SPECIFY DATE documentssG > TODAY and TOMORROW, but BOTTIME is not there. Another thing to add tom6 > the list of undocumented commands/keywords, I think.  6 Wouldn't be the first case of undocumented behavior...   -- o David J. Dachteral dba DJE Systemso http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------   Date: 31 Oct 2001 01:24:37 GMT- From: forkosh@panix1.panix.com (John Forkosh)n, Subject: Re: Equivalent of /etc/hosts in vms) Message-ID: <9rnjsl$6cl$2@news.panix.com>n  . Larry Kilgallen (Kilgallen@SpamCop.net) wrote:1 : Vasu Kulkarni <vasukulkarni@imahal.com> writes:r : > Hi,tJ : >       i want to know the equivalent of /etc/hosts file  in vms7.3. or 0 : > help me where to post such simple questions.  B : There is none in VMS.  That file is used for IP.  It would be in? : any TCP/IP package that is installed on your machine.  If you:> : indicate what TCP/IP package you are using, someone would be : able to help.,  > I recently had sone problems that brought up the same question@ while running net$configure for 7.2.  Assuming they're the same,8 then  sys$system:net$local_name_database.dat  is roughly equivalent to Unix's /etc/hostsf@      The license paks with the layered products hobbyist license9 include dvnetend (and not dvnetrtg), so you can set up ane< end node.  Reply  LOCAL  to net$configure when it asks which0 services to configure (or words to that effect).:      Then, you'll need to run  decnet_register  to add the8 name-to-address translations to local_name_database.dat.9 It's not a text file, so you can't administer it by hand.u4      Someone kindly emailed me these useful tidbits.5 I hadn't found much mention at all of decnet_registero: in the compaq or montagar documentation, though it appears: to be crucial to set up a local lan without dns (which you) can't run anyway due to pak limitations).g John (forkosh@panix.com)   ------------------------------  # Date: Tue, 30 Oct 2001 22:36:34 GMTf+ From: Jeff Campbell <jcampbell@ins-msi.com>s- Subject: Re: Equivalent of /etc/hosts in vms.b+ Message-ID: <3BDF2360.D2BC194A@ins-msi.com>C  ? For Compaq's TCPIP stack - SYS$MANAGER:ETC.HOSTS. See the TCPIP * documentation or $TCPIP HELP CONVERT /VMS.  
 Jeff Campbell. n8wxs@arrl.net   Vasu Kulkarni wrote: >  > Hi,b > G >       i want to know the equivalent of /etc/hosts file  in vms7.3. orr. > help me where to post such simple questions. >  > Thanx and Regardsn	 > --vasu.e   ------------------------------  % Date: Tue, 30 Oct 2001 11:13:09 -0800m% From: Dean Woodward <deanw@rdrop.com>  Subject: FTP over SSLg( Message-ID: <3BDEFBC5.80316AE@rdrop.com>  F Anyone dealt with transmitting files via FTP over SSL, directly from aF VMS box?  I've got a customer that wants to do this.  (Read: needs to, wants a non-windoze solution.)   ------------------------------  # Date: Tue, 30 Oct 2001 19:30:50 GMT L From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr") Subject: Re: FTP over SSLy8 Message-ID: <00A044BE.CA557701@SSRL04.SLAC.STANFORD.EDU>  P In article <3BDEFBC5.80316AE@rdrop.com>, Dean Woodward <deanw@rdrop.com> writes:  G >Anyone dealt with transmitting files via FTP over SSL, directly from a G >VMS box?  I've got a customer that wants to do this.  (Read: needs to,e >wants a non-windoze solution.)h  M I haven't dealt with this, but have heard about it.  There are two protocols,.M SCP (secure copy) and SFTP.  The next release of Multinet is supposed to havebF SCP in it; it is _not_ supposed to have SFTP.  Does the customer need H FTP in specific, or is the actual requirement 'encrypted file transfer'?  H If he needs non-windows SFTP right now, I think he has to go with a Unix system./   -- Alanu    O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056uM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210 O ===============================================================================m   ------------------------------   Date: 30 Oct 2001 20:44:58 GMT0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz) Subject: Re: FTP over SSLv5 Message-ID: <9rn3ga$1e3$1@newsmaster.cc.columbia.edu>   ( In article <3BDEFBC5.80316AE@rdrop.com>,' Dean Woodward  <deanw@rdrop.com> wrote: H : Anyone dealt with transmitting files via FTP over SSL, directly from aH : VMS box?  I've got a customer that wants to do this.  (Read: needs to,  : wants a non-windoze solution.) :t Server side:  *   http://www.columbia.edu/kermit/ftpd.html   Client side...  C Well, if this was Unix and not VMS, I could recommend C-Kermit 8.0:r  *   http://www.columbia.edu/kermit/ck80.html  D which includes an SSL FTP client, and a scriptable one at that.  ButF unfortunately neither the SSL nor the FTP code has been ported to VMS. It does work in Unix, however.   - Frank    ------------------------------   Date: 30 Oct 2001 20:53:46 GMT0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz) Subject: Re: FTP over SSLl5 Message-ID: <9rn40q$1rn$1@newsmaster.cc.columbia.edu>o  8 In article <00A044BE.CA557701@ssrl04.slac.stanford.edu>,K Alan Winston - SSRL Admin Cmptg Mgr <winston@SSRL.SLAC.STANFORD.EDU> wrote:i* : In article <3BDEFBC5.80316AE@rdrop.com>,* :  Dean Woodward <deanw@rdrop.com> writes:I : >Anyone dealt with transmitting files via FTP over SSL, directly from atI : >VMS box?  I've got a customer that wants to do this.  (Read: needs to,I! : >wants a non-windoze solution.)F : E : I haven't dealt with this, but have heard about it.  There are two y* : protocols, SCP (secure copy) and SFTP... :fD I don't think these are the same as SSL.  You can have a regular FTPF connection secured by SSL, but SCP is something else -- in fact it's aF semi-secure variation of Unix RCP.  SCP does not take into account theL differences among file systems (e.g. Unix, VMS, Windows) and copies everyingD in binary mode, which is not going to be very useful between VMS andJ anything else, or probably not even between two VMS's, unless the protocolJ is modified to send along file attributes or raw disk and directory blocks or somesuch.  > This subject came up earlier today on a different newsgroup...  2   From: fdc@watsun.cc.columbia.edu (Frank da Cruz)9   Newsgroups: comp.sys.hp.hpux,comp.protocols.kermit.miscn8   Subject: Re: transfering files securely (encryption ?)    Date: 30 Oct 2001 13:55:35 GMT#   Organization: Columbia Universityt  C   In article <slrn9tsp4e.4ki.Ralf.Hildebrandt@postamt1.charite.de>,w7   Ralf Hildebrandt <Ralf.Hildebrandt@charite.de> wrote:     : On 29 Oct 2001 19:47:11 GMT,:   : Jeffrey Altman <jaltman@watsun.cc.columbia.edu> wrote:   : H   : >Cygwin on Windows does allow OpenSSH to be used there.  But it doesF   : >not address the lack of support in the SFTP protocol for handlingH   : >the differences between Stream-Binary, Stream-ASCII, Stream-EBCDIC,J   : >Stream-Unicode, and various Record based file formats used on variousJ   : >operating systems.  SFTP treats everything as Stream-Binary no matter   : >what.     : K   : This restriction was never a problem for me. I just write the stuff the +   : way it should appear on the target box..	   : YMMV.p   :mF   It might indeed.  Lots of tools work for simple cases but not in theL   general case.  There is a good reason that FTP distinguishes between text-F   and binary-mode transfer.  FTP was designed in the days of computingL   diversity, to interoperate between any pair of computers (the n*n problem);   no matter how their internal file representations differ.i  J   If you only use platforms whose file semantics are all the same, then ofJ   course scp "meets your needs".  But from that we can not infer that scp    meets everybody's needs.  H   Let's look at what happens when you transfer all files in binary mode:  J    . Sending C source code from DOS or Windows to Unix.  You can't compileH      it any more because most C compilers do not like CRLF's.  Silly and0      stupid, we can all agree, but still a fact.  D    . Sending any text file from Unix to DOS or Windows.  You get the5      stairstep effect, e.g. when viewing or printing.V  J   These are trivial problems, yet nevertheless so many of today's computerI   users are baffled by them that they flood the newsgroups with cries fora4   help.  But let's look at some nontrivial examples:  K    . Transferring a Unix ASCII text file to an IBM mainframe, which doesn't.J      use ASCII.  It becomes total, incomprehensible garbage.  Ditto in the      reverse direction.	  I    . Transferring a text file between a record-oriented file system and aoK      stream-oriented file system.  The record boundaries are lost or turned	      into garbage characters..  I    . Transferring text in (say) German from DOS or Windows to Unix.  The o      Umlaute become garbage.  I    . Transferring text in (say) Russian from DOS or Windows to Unix.  Thel!      entire text becomes garbage.e  H   Good tools handle not only trivial cases but the general case as well.H   Good file-transfer tools follow well-established principals of networkH   citizenship by not putting proprietary formats on the wire but rather,J   always converting to a common intermediate representation for transport.D   This includes, for text-mode file transfer, both record format and   character set.  H   Of course it is easy to say that IBM mainframes, VMS, and so on "don'tK   matter".  This is a dangerous attitude.  Monopolies are bad; diversity isrN   good.  Safety and robustness spring from diversity.  If you need convincing,:   look at the current situation with security and viruses.  	   - Frankt   (end quote)t   ------------------------------  % Date: Tue, 30 Oct 2001 13:07:42 -0800a% From: Dean Woodward <deanw@rdrop.com>  Subject: Re: FTP over SSL ) Message-ID: <3BDF169E.9FB4BE15@rdrop.com>i   [snip happens]   Frank da Cruz wrote: > @ > This subject came up earlier today on a different newsgroup... > 4 >   From: fdc@watsun.cc.columbia.edu (Frank da Cruz) > E >   In article <slrn9tsp4e.4ki.Ralf.Hildebrandt@postamt1.charite.de>,h9 >   Ralf Hildebrandt <Ralf.Hildebrandt@charite.de> wrote:." >   : On 29 Oct 2001 19:47:11 GMT,< >   : Jeffrey Altman <jaltman@watsun.cc.columbia.edu> wrote: >tM >    . Transferring a Unix ASCII text file to an IBM mainframe, which doesn'tnL >      use ASCII.  It becomes total, incomprehensible garbage.  Ditto in the >      reverse direction.e   [just snip it]  J >   Of course it is easy to say that IBM mainframes, VMS, and so on "don't+ >   matter".  This is a dangerous attitude._  D Worse than dangerous; I am, in fact, trying to get a file from a VMS system to an IBM system...  G Thanks for the input.  It may be that my solution is to script C-Kermit C on a FreeBSD box to pick up the file from VMS and deliver it to theiG IBM.  The only way this could get more complicated is if I used Samba /7F Pathworks / SMB to read the original file.  (Which, if they don't wantE to pay the integration fee to do, is exactly what will happen because3E they'll be going from VMS to IBM via windoze... by hand, every time.)s   ------------------------------    Date: 30 Oct 2001 18:29:04 -0800( From: bob@instantwhip.com (Bob Ceculski) Subject: Re: FTP over SSLD= Message-ID: <d7791aa1.0110301829.7436e1da@posting.google.com>a   winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr") wrote in message news:<00A044BE.CA557701@SSRL04.SLAC.STANFORD.EDU>...R > In article <3BDEFBC5.80316AE@rdrop.com>, Dean Woodward <deanw@rdrop.com> writes: > I > >Anyone dealt with transmitting files via FTP over SSL, directly from a I > >VMS box?  I've got a customer that wants to do this.  (Read: needs to,7! > >wants a non-windoze solution.)- > O > I haven't dealt with this, but have heard about it.  There are two protocols,eO > SCP (secure copy) and SFTP.  The next release of Multinet is supposed to have H > SCP in it; it is _not_ supposed to have SFTP.  Does the customer need J > FTP in specific, or is the actual requirement 'encrypted file transfer'? > J > If he needs non-windows SFTP right now, I think he has to go with a Unix	 > system.s > 	 > -- Alan  >   H there is no such thing as secure ftp ... multinet and soon after tcpwareD will offer a feature called secure copy ... i think it is due out by
 years end ...o   ------------------------------  # Date: Wed, 31 Oct 2001 02:37:27 GMToL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr") Subject: Re: FTP over SSL 8 Message-ID: <00A044FA.63A664DE@SSRL04.SLAC.STANFORD.EDU>  h In article <d7791aa1.0110301829.7436e1da@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes: >winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr") wrote in message news:<00A044BE.CA557701@SSRL04.SLAC.STANFORD.EDU>...hS >> In article <3BDEFBC5.80316AE@rdrop.com>, Dean Woodward <deanw@rdrop.com> writes:3 >> 0J >> >Anyone dealt with transmitting files via FTP over SSL, directly from aJ >> >VMS box?  I've got a customer that wants to do this.  (Read: needs to," >> >wants a non-windoze solution.) >> oP >> I haven't dealt with this, but have heard about it.  There are two protocols,P >> SCP (secure copy) and SFTP.  The next release of Multinet is supposed to haveI >> SCP in it; it is _not_ supposed to have SFTP.  Does the customer need DK >> FTP in specific, or is the actual requirement 'encrypted file transfer'?  >> wK >> If he needs non-windows SFTP right now, I think he has to go with a Unixy
 >> system. >>  
 >> -- Alan >> e >hI >there is no such thing as secure ftp ... multinet and soon after tcpwarehE >will offer a feature called secure copy ... i think it is due out by  >years end ...  L There is FTP over SSL, and they call it SFTP, honest.  It just doesn't existL on VMS, like I said in the part of the post you quoted but apparently didn'tM read.   (Actually, that part would be all of it, since the rest of your post PK adds little new information to my saying SCP will be in the next release ofR
 Multinet.)   -- Alane  O ===============================================================================i0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056yM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210MO ===============================================================================m   ------------------------------    Date: 30 Oct 2001 18:46:35 -0800( From: bob@instantwhip.com (Bob Ceculski) Subject: Re: FTP over SSL = Message-ID: <d7791aa1.0110301846.757adbd8@posting.google.com>n  U Dean Woodward <deanw@rdrop.com> wrote in message news:<3BDEFBC5.80316AE@rdrop.com>...SH > Anyone dealt with transmitting files via FTP over SSL, directly from aH > VMS box?  I've got a customer that wants to do this.  (Read: needs to,  > wants a non-windoze solution.)  G there is no such thing as secure ftp ... process will release a feature D by the end of the year i believe called secure copy using ssh ... ifH this is a vms to vms transfer, dec had a product called dec encrypt thatD is still available, otherwise wait for tcpware especially if this isH for use over the public internet ... unix is not unhackable like vms is!   ------------------------------  % Date: Tue, 30 Oct 2001 22:01:52 -0500e) From: John Johnstone <jj_usenet@mail.com> ! Subject: Re: GBLPAGES in VMS V7.3n( Message-ID: <3BDF2350.5B62F431@mail.com>  I Having one less SYSGEN parameter to worry about is certainly a good thing K in my opinion so I'm quite glad to see the change.  It would have been nice E if this improvement was mentioned in the release notes, but if having:K improvements undocumented increases the number of them, that's a good thinga too.     Hoff Hoffman wrote:c > V > In article <3BCC82F4.3BB4FA46@mail.com>, John Johnstone <jj_usenet@mail.com> writes:M > :I've been looking at a system running VMS V7.3 and it looks like the valuel( > :of GBLPAGES has taken quite a jump...6 > :Does anyone know why there was such a large change? > H >   We were asked to make OpenVMS easier to manage, and this is a (very)' >   small part of that (on-going) work.  > H >   The setting of GBLPAGES determines the size of the Global Page TableI >   (GPT), and it is now initially sized to support larger RMS caches ands( >   other (large) users of global pages. > D >   Now for some details on the cost of this change, in terms of theI >   new physical memory requirements: the cost of sizing the GPT is threewF >   memory pages (assuming an eight kilobyte page size) for every fourG >   million pages (well, actually, every 4,194,304 pages) configured injG >   the system.  In other words, the overhead of the new higher settingpG >   is viewed as very low, and the value derived from easily increasingaG >   the available global pages and particularly in easily increasing inwB >   the available RMS caching are viewed as reasonable trade-offs.  	 [snipped]h   ------------------------------  # Date: Wed, 31 Oct 2001 03:03:03 GMT   From: cjt <cheljuba@prodigy.net>. Subject: Re: half off fire sale on windows xp!+ Message-ID: <3BDF694D.21777A83@prodigy.net>    "Terry C. Shannon" wrote:e ><snip>  > J > Stranger things have happened. A small consulting firm which will remainI > nameless actually bragged about the fact that they had Internet-enabledn- > peecees in the bathrooms of their office...x  
 With WebCams?    ------------------------------  # Date: Wed, 31 Oct 2001 03:53:03 GMTv4 From: "Terry C. Shannon" <terryshannon@mediaone.net>. Subject: Re: half off fire sale on windows xp!= Message-ID: <zAKD7.25872$f6.12528583@typhoon.ne.mediaone.net>   - "cjt" <cheljuba@prodigy.net> wrote in messaged% news:3BDF694D.21777A83@prodigy.net...o > "Terry C. Shannon" wrote:n	 > ><snip>i > >oL > > Stranger things have happened. A small consulting firm which will remainK > > nameless actually bragged about the fact that they had Internet-enabledm/ > > peecees in the bathrooms of their office...  >b > With WebCams?u  I Umm, no. Fact of the matter is, they were dead serious about their Unique) Differentiator!@   ------------------------------    Date: 30 Oct 2001 13:58:31 -0800, From: ezharkov@yahoo.com (Eugene A. Zharkov)J Subject: Re: How to redirect output&error into a single file in sys$creprc= Message-ID: <af0b5c61.0110301358.2496c02b@posting.google.com>S  Y briggs@encompasserve.org wrote in message news:<9z3P1MF5XA0e@eisner.encompasserve.org>...bn > In article <af0b5c61.0110231245.5771adeb@posting.google.com>, ezharkov@yahoo.com (Eugene A. Zharkov) writes:D > > The following example creates two versions of the test.log file.: > > Is there an easy way to tell creprc to make just one ? > D > $CREPRC doesn't make the two versions.  Your program (or the C RTL > living underneath it) does.F > H > All $CREPRC is going to do with the input, output and error parametersD > is to pass them as predefined values for the SYS$INPUT, SYS$OUTPUTC > and SYS$ERROR logical names.  It will not pre-open them as files.d > G > From the point of view of your program, the SYS$INPUT, SYS$OUTPUT and:B > SYS$ERROR logical names are pure text.  That they are most oftenD > associated with the file names for standard input, standard outputD > and standard error is merely a matter of convention.  Your program& > is free to interpret them otherwise. > B > In the case at hand, your program is using STDIO to do output onC > standard output and standard error.  It is depending on the C run ? > time library to open up the standard output and error streams  > automatically as needed. > 2 > You have at least the following ways to proceed: > C > 1.  Check the SYS$OUTPUT and SYS$ERROR logical names yourself andi* > reopen the appropriate streams to taste. > E > 2.  Use SYS$SYSTEM:LOGINOUT.EXE as the launched image.  Its defaultd: > behavior is to open SYS$INPUT as a DCL command procedureA > and to open SYS$OUTPUT as a process permanent file and set both=< > SYS$OUTPUT and SYS$ERROR to point to this pre-opened file. > ! > 3.  Use LIB$SPAWN() or SYSTEM()S >  > 	John Briggs  A This all looks a bit more complicated than I wanted. I don't want0> to use loginout. I don't think that I can use lib$spawn/system? (because I need to specify priority/privileges/quotas). I think=) I will just use dup2(1,2) in the child...    Thanks anyway for your answer.   ------------------------------  % Date: Tue, 30 Oct 2001 22:49:28 -0500a+ From: "Reece R. Pollack" <bogus@public.com>DC Subject: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB8( Message-ID: <3bdf755d_6@vienna7.his.com>  J "j.lance wilkinson, (814) 865-1818" <jlw@psulias.psu.edu> wrote in message% news:9qpr2c$uoc@r02n01.cac.psu.edu...c   > Any chance that somebody's >aK > 1) Implemented MOD_AUTH_KERB for OpenVMS already and is willing to share?wG > 2) Got the full KRB5 include set at least translated for OpenVMS so In couldn > possibly get (1) going here?  I I ported the full Kerberos V5 package, clients and servers, to VMS when ISL worked for Wollongong. Anyone running the last Attachmate version of PathWayI for OpenVMS has full Kerberos V4 and V5 capabilities, including shareable L libraries and header files. Alas, Attachmate didn't understand anything thatD didn't run under a Microsloth operating system and connect to an IBM' mainframe, and they killed the product.a   -- Reece R. Pollack Senior Software Engineer   ------------------------------  % Date: Tue, 30 Oct 2001 21:37:28 +0100t" From: "Hans Vlems" <hvlems@iae.nl> Subject: Re: OT - HP's MPE-IXr( Message-ID: <9rn32r$kpe$1@news.IAEhv.nl>  F If I read the MPE newsgroup correctly they are thinking along the same lines.G They want to move those poor VMS users to a proper operating system....e   Hans  ) <lroduner@americhem.com> wrote in message = news:OF830EA9D3.8598F247-ON85256AF5.0063BF0A@americhem.com...oL > Just curious - I know almost nothing about HP's MPE-IX.  I do know that itJ > is a non-UNIX OS developed by HP in the late 1970's to 1980s as a 16-bit OSL > called MPE, then ported to 32-bits as MPE-IX; and that it is not receivingK > a lot of work from HP now.  It does have a file system and database built 
 > in also. >pI > How difficult would it be to move enough of the MPE-IX system functionsV anddI > RTL's to VMS so that the existing MPE-IX applications could be "easily"lI > ported to VMS?  Those applications would then gain the stability of VMSsJ > along with the best-in-class clustering and growth offered by VMS.  PlusH > additional applications and customers certainly could only enhance theK > visibility of VMS within CHomPaq, and give those MPE-IX users a future onsH > the best OS in the world instead of withering on the vine, as they are > doing now. >s   ------------------------------  % Date: Tue, 30 Oct 2001 12:44:46 -0800w( From: "Greg Cagle" <gregc@gregcagle.com> Subject: Re: OT - HP's MPE-IX / Message-ID: <ttu49lq9qmg00a@corp.supernews.com>a  9 Crossposting to comp.sys.hp.mpe and the 3000-L. Comments?e   --
 Greg Cagle gregc at gregcagle dot com  g <lroduner@americhem.com> wrote in message news:OF830EA9D3.8598F247-ON85256AF5.0063BF0A@americhem.com...aL > Just curious - I know almost nothing about HP's MPE-IX.  I do know that itM > is a non-UNIX OS developed by HP in the late 1970's to 1980s as a 16-bit OSyL > called MPE, then ported to 32-bits as MPE-IX; and that it is not receivingK > a lot of work from HP now.  It does have a file system and database builtr
 > in also. >bM > How difficult would it be to move enough of the MPE-IX system functions and I > RTL's to VMS so that the existing MPE-IX applications could be "easily"hI > ported to VMS?  Those applications would then gain the stability of VMS J > along with the best-in-class clustering and growth offered by VMS.  PlusH > additional applications and customers certainly could only enhance theK > visibility of VMS within CHomPaq, and give those MPE-IX users a future on H > the best OS in the world instead of withering on the vine, as they are > doing now. >r   ------------------------------  % Date: Tue, 30 Oct 2001 21:57:50 -0000i% From: gavin@allegro.com (Gavin Scott)  Subject: Re: OT - HP's MPE-IXx/ Message-ID: <ttu8iumi1mto73@news.supernews.com>s  K Just curious - I know almost nothing about Compaq's VMS.  I do know that ittL is a non-UNIX OS developed by Dec in the late 1970's to 1980s as a 16-bit OSL called RSTS/E, then ported to 32-bits as VMS; and that it is not receiving a9 lot of work from Compaq now.  It does have a file system.p  H How difficult would it be to move enough of the VMS system functions andL Intrinsics to MPE/iX so that the existing VMS applications could be "easily"J ported to MPE?  Those applications would then gain the stability of MPE/iXJ along with the best-in-class clustering and growth offered by the HP-3000.K Plus additional applications and customers certainly could only enhance thesJ visibility of MPE within CHomPaq, and give those VMS users a future on theH best OS in the world instead of withering on the vine, as they are doing now.   G.    (and so the battle is joined :-)   ------------------------------  % Date: Tue, 30 Oct 2001 22:20:34 -0000r% From: gavin@allegro.com (Gavin Scott)e Subject: Re: OT - HP's MPE-IX / Message-ID: <ttu9ti12pq4occ@news.supernews.com>e   I wrote:" > (and so the battle is joined :-)  C On a more serious note, it would be interesting to see what sort ofpD opportunities there might be for the VMS and MPE communities to workF together toward some common goals in the face of the impending merger.  B You don't have to get too high in the air before MPE and VMS look D pretty much identical these days, and both seem to be suffering fromF the same relative neglect in the face of the Windows/Unix world.  BothD are (I believe) being ported to IA-64, both are widely seen as "cashB cows", have problems attracting new development, have wildly loyal customer bases, etc.   G.   ------------------------------  # Date: Tue, 30 Oct 2001 22:27:23 GMT * From: "Andy Stoffel" <acs@fcgnetworks.net> Subject: Re: OT - HP's MPE-IXFA Message-ID: <fPFD7.70915$W87.4676566@bin4.nnrp.aus1.giganews.com>a  2 "Gavin Scott" <gavin@allegro.com> wrote in message) news:ttu8iumi1mto73@news.supernews.com....M > Just curious - I know almost nothing about Compaq's VMS.  I do know that iteN > is a non-UNIX OS developed by Dec in the late 1970's to 1980s as a 16-bit OS/ > called RSTS/E, then ported to 32-bits as VMS;   I I'm new here (only been using VMS since 1985) and I didn't know this :-).   F > and that it is not receiving a lot of work from Compaq now.  It does > have a file system.   " > (and so the battle is joined :-)  4 [I know your answer was tongue-in-cheek but :-)....]  ? The best place to start BEFORE asking these questions would be:m  "     http://www.openvms.compaq.com/   and then on to:   5 http://www.openvms.compaq.com/wizard/openvms_faq.htmlc  	 which, ifg  : http://www.openvms.compaq.com/wizard/openvms_faq.html#VMS1  4 isn't enough, will point you to a history of VMS at:  8   http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  ' and the entire VMS docuemnation set at:o  # http://www.openvms.compaq.com:8000/a   -Andy-   ------------------------------  % Date: Tue, 30 Oct 2001 14:35:04 -0800y( From: "Greg Cagle" <gregc@gregcagle.com> Subject: OT - HP's MPE-IXy/ Message-ID: <ttuaogcqftrr38@corp.supernews.com>n  F From Greg Stigers Gregory.Stigers@cgiusa.com, on the HP-3000-L mailing list:-  . ----------------------------------------------   X-no-Archive:yesJ I have to appreciate the spirit in which it is intended. It seems apparentJ that the author knows a bit of MPE's history, and a couple of its featuresI (are there extant OSs without a file system?), but has no experience with< it.B  K I assume the author has sympathy for us, knowing and enjoying some years ofeK very positive experience with a great and robust system, which has receivedII less attention than it deserves. The author probably sees his system as anK safe haven for those whose fortunes at the hands of other operating systemstF has been less than desirable, and whose future is in doubt. The authorL probably has concerns about how the newly merged organization will treat itsL heretofore marginalized customers, and would like to see the visibility of a. wonderful, venerable product greatly enhanced.  F I think many of us can recognize the perspective from which the authorJ writes, and sympathize. But I am unwilling to suggest that his compatriotsK jump ship, and question the wisdom of treating potential allies as refugeestL with the offer of safe haven. Rather, I hope that both sides can find allies
 in the other.:  K I know almost exactly nothing of the openness of OpenVMS. But I assume thatpG our own successes in porting open source software to our platform could0F offer some small common ground. Perhaps together, we can challenge theL several definitions of openness that seem to mean leaving my platform to useI your "open" one, thereby offending free men with promises of independence0K and liberty. Perhaps MPE/iX and OpenVMS can be named together in one breathAJ in the company of the OSS communities. Perhaps we can thereby and togetherK raise the visibility of both within Hewlett-Com-Packard, strengthening both'H together rather than weakening both by either attempting to stand on theH other's corpse. And perhaps there are other opportunities for fraternity  that I have not even considered.   Greg Stigers http://www.cgiusa.come/ you have my permission to cross-post this back.P     --
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Tue, 30 Oct 2001 23:16:17 +0000r* From: Roy Brown <roy@acanthus.demon.co.uk> Subject: Re: OT - HP's MPE-IXt3 Message-ID: <OWpyhgXBTz37Ew9n@acanthus.demon.co.uk>-  8 n message <9rn80b015k1@enews2.newsguy.com>, Gavin Scott  <gavin@ALLEGRO.COM> writes< >> Crossposting to comp.sys.hp.mpe and the 3000-L. Comments? >dL >Just curious - I know almost nothing about Compaq's VMS.  I do know that itM >is a non-UNIX OS developed by Dec in the late 1970's to 1980s as a 16-bit OSuM >called RSTS/E, then ported to 32-bits as VMS; and that it is not receiving an: >lot of work from Compaq now.  It does have a file system. >aI >How difficult would it be to move enough of the VMS system functions and=M >Intrinsics to MPE/iX so that the existing VMS applications could be "easily" K >ported to MPE?  Those applications would then gain the stability of MPE/iXeK >along with the best-in-class clustering and growth offered by the HP-3000. L >Plus additional applications and customers certainly could only enhance theK >visibility of MPE within CHomPaq, and give those VMS users a future on the-I >best OS in the world instead of withering on the vine, as they are doingC >now.) >u >G.: >:! >(and so the battle is joined :-)a  < Terrific. Tweedledum and Tweedledee decide to have a battle.  E When what they *both* should be worrying about is the Queen of HeartsnB running around shouting 'Off with their heads'.... (or its modern ) equivalent, 'Reduce the headcount'..... )s  - It's a Looking-Glass world all right..... :-(d   -- uH Roy Brown        'Have nothing in your houses that you do not know to beE Kelmscott Ltd     useful, or believe to be beautiful'  William Morris    ------------------------------  % Date: Tue, 30 Oct 2001 18:41:31 -0500  From: lroduner@americhem.com Subject: Re: OT - HP's MPE-IXlC Message-ID: <OF1D818C85.0ADBBB2F-ON85256AF5.007D0CA3@americhem.com>a  K I want to thank all of you for your responses.  You are quite right, I am a:K long-time and loyal user of VMS.  I just asked the question out of a desireEH to see an excellent OS survive well into the future, and thought that ifH the number of users and applications could be increased, this would helpJ ensure that future.  I don't want to contemplate trying to have to move toE something else - which would probably end up being some Windoze crap!n  H The only exposure I have had to MPE was 15 years ago when my employer atJ that time was looking for a new computer for our research lab, and we wereG looking mainly at DEC / VMS and HP / MPE.  We ended up choosing the DECr> system as it had more of the programs we desired at that time.  A I made the comment about a "file system" in the sense of RMS - aneH operating-system-native service which can provide record-structured ISAMK access, available from the system itself and accessible to any language viaf= standard interfaces, unlike the UNIX world with its basicallyTG stream-oriented bytes of data.  I know that there are some ISAM-capabletI file-manager programs available on the various UNIX's, but that is not int) the same mode as RMS or MPE's (AllBase?).h  I Coming from the VMS world, I have never seen MPE-iX mentioned as having apJ strong clustering capability.  The only OS's mentioned in various articlesE talk about IBM mainframes with SYSPLEX, various UNIX versions such asmF Solaris, True64, and Linux, and of course Micros**t's weak attempts toH build clustering into the various versions of Windoze.  Also, all I haveI read has said that HP has done very little development on MPE-iX over theaI past few years, whereas I knew that VMS was still receiving (some) active-F development - such as the Galaxy partitioning and the DII-COE port andC certification.  I was not attempting to denigrate in any manner thesF capabilities of MPE, I was just under the impression that MPE was lessG active.  I had not seen any mention that MPE-iX would be ported to IPF,nK whereas VMS has a major project (and have added additional personnel) to doy@ this - brought on, of course, by the decision to stop any future8 development of the Alpha chip beyond the EV7 generation.  E I believe that Compaq claims that there are 400,000+ VMS systems withaI 10,000,000 users world-wide (these figures are likely inflated).  What is- the user base for MPE-iX?3  K In the end, this is really a question for the VMS and MPE-iX managers - caneJ these 2 OS's, each of which have such a die-hard following, be joined intoI a new system that is better than either one individually as a part of thewE port to IFS, in the same way that HP-UX and True64 are supposed to beIG joined into a new common Unix OS?  Is there anything in the VMS DII-COE & work which would help in this joining?        f                                                                                                       f                     "Greg Cagle"                                                                      f                     <gregc@gregcag       To:     Info-VAX@Mvb.Saic.Com                                f                     le.com>              cc:                                                          f                                          Subject:     OT - HP's MPE-IX                                f                     10/30/01 05:35                                                                    f                     PM                                                                                f                     Please respond                                                                    f                     to "Greg                                                                          f                     Cagle"                                                                            f                                                                                                       f                                                                                                               F From Greg Stigers Gregory.Stigers@cgiusa.com, on the HP-3000-L mailing list:u  . ----------------------------------------------   X-no-Archive:yesJ I have to appreciate the spirit in which it is intended. It seems apparentJ that the author knows a bit of MPE's history, and a couple of its featuresI (are there extant OSs without a file system?), but has no experience withS it.R  K I assume the author has sympathy for us, knowing and enjoying some years of K very positive experience with a great and robust system, which has receivedaI less attention than it deserves. The author probably sees his system as aPK safe haven for those whose fortunes at the hands of other operating systemsoF has been less than desirable, and whose future is in doubt. The authorH probably has concerns about how the newly merged organization will treat itstJ heretofore marginalized customers, and would like to see the visibility of ae. wonderful, venerable product greatly enhanced.  F I think many of us can recognize the perspective from which the authorJ writes, and sympathize. But I am unwilling to suggest that his compatriotsK jump ship, and question the wisdom of treating potential allies as refugeeseE with the offer of safe haven. Rather, I hope that both sides can find5 allies
 in the other.   K I know almost exactly nothing of the openness of OpenVMS. But I assume thatsG our own successes in porting open source software to our platform could F offer some small common ground. Perhaps together, we can challenge theH several definitions of openness that seem to mean leaving my platform to useoI your "open" one, thereby offending free men with promises of independencegK and liberty. Perhaps MPE/iX and OpenVMS can be named together in one breath J in the company of the OSS communities. Perhaps we can thereby and togetherK raise the visibility of both within Hewlett-Com-Packard, strengthening bothaH together rather than weakening both by either attempting to stand on theH other's corpse. And perhaps there are other opportunities for fraternity  that I have not even considered.   Greg Stigers http://www.cgiusa.com-/ you have my permission to cross-post this back.0     --
 Greg Cagle gregc at gregcagle dot com   ------------------------------  # Date: Wed, 31 Oct 2001 00:19:41 GMTI4 From: "Terry C. Shannon" <terryshannon@mediaone.net> Subject: Re: OT - HP's MPE-IX > Message-ID: <xsHD7.161981$vq.39998738@typhoon.ne.mediaone.net>  ) <lroduner@americhem.com> wrote in messagee= news:OF1D818C85.0ADBBB2F-ON85256AF5.007D0CA3@americhem.com...c   >oG > I believe that Compaq claims that there are 400,000+ VMS systems withaK > 10,000,000 users world-wide (these figures are likely inflated).  What isb > the user base for MPE-iX?r >   D I can't comment on the MPE-iX user base, but you are correct in yourH assumption that the VMS installed base numbers are inflated. Word has itK that the numbers will be "rightsized" in the near future. Whatever, the VMSnF franchise remains profitable, which is more than can be said for CPQ's Wintel business these days.s   ------------------------------    Date: 30 Oct 2001 18:50:03 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: OT - HP's MPE-IXa3 Message-ID: <4sONkBNb7rJ1@eisner.encompasserve.org>   b In article <OF1D818C85.0ADBBB2F-ON85256AF5.007D0CA3@americhem.com>, lroduner@americhem.com writes:  K > Coming from the VMS world, I have never seen MPE-iX mentioned as having a-L > strong clustering capability.  The only OS's mentioned in various articlesG > talk about IBM mainframes with SYSPLEX, various UNIX versions such astH > Solaris, True64, and Linux, and of course Micros**t's weak attempts toJ > build clustering into the various versions of Windoze.  Also, all I haveK > read has said that HP has done very little development on MPE-iX over the3K > past few years, whereas I knew that VMS was still receiving (some) active-H > development - such as the Galaxy partitioning and the DII-COE port and > certification.  @ Coming from the VMS world, I try to avoid making judgement aboutD operating system capabilities based on publicity from the vendor :-)   ------------------------------    Date: 30 Oct 2001 18:52:58 -0800( From: bob@instantwhip.com (Bob Ceculski) Subject: Re: OT - HP's MPE-IX = Message-ID: <d7791aa1.0110301852.4350eb14@posting.google.com>t  g lroduner@americhem.com wrote in message news:<OF830EA9D3.8598F247-ON85256AF5.0063BF0A@americhem.com>...rL > Just curious - I know almost nothing about HP's MPE-IX.  I do know that itM > is a non-UNIX OS developed by HP in the late 1970's to 1980s as a 16-bit OStL > called MPE, then ported to 32-bits as MPE-IX; and that it is not receivingK > a lot of work from HP now.  It does have a file system and database built-
 > in also. > M > How difficult would it be to move enough of the MPE-IX system functions and:I > RTL's to VMS so that the existing MPE-IX applications could be "easily"tI > ported to VMS?  Those applications would then gain the stability of VMSsJ > along with the best-in-class clustering and growth offered by VMS.  PlusH > additional applications and customers certainly could only enhance theK > visibility of VMS within CHomPaq, and give those MPE-IX users a future onlH > the best OS in the world instead of withering on the vine, as they are > doing now.  M don't waste your brain cells on this crowd ... maybe carly really understandstH the high end unlike capellas and palmer, but i doubt it ... the pc crowdH only understand IIS and blue screens and 80% of your time spent applying, patches ... we will have to wait and see ...   ------------------------------  % Date: Tue, 30 Oct 2001 22:25:34 -0500n% From: "John Vottero" <John@mvpsi.com>i Subject: Re: OT - HP's MPE-IXe/ Message-ID: <tturpf8l3d9v10@news.supernews.com>d  ? "Terry C. Shannon" <terryshannon@mediaone.net> wrote in message:8 news:xsHD7.161981$vq.39998738@typhoon.ne.mediaone.net... >:+ > <lroduner@americhem.com> wrote in messagep? > news:OF1D818C85.0ADBBB2F-ON85256AF5.007D0CA3@americhem.com...o >d > > I > > I believe that Compaq claims that there are 400,000+ VMS systems withoJ > > 10,000,000 users world-wide (these figures are likely inflated).  What is > > the user base for MPE-iX?  > >e >pF > I can't comment on the MPE-iX user base, but you are correct in yourJ > assumption that the VMS installed base numbers are inflated. Word has itI > that the numbers will be "rightsized" in the near future. Whatever, theo VMSrH > franchise remains profitable, which is more than can be said for CPQ's > Wintel business these days.e >o  H They just finished a recount and the new numbers are 410,000 systems andF 10,000,000 users. Slightly less than 200,000 of the systems are VAXen.   ------------------------------  # Date: Wed, 31 Oct 2001 04:01:34 GMT74 From: "Terry C. Shannon" <terryshannon@mediaone.net> Subject: Re: OT - HP's MPE-IX = Message-ID: <yIKD7.25899$f6.12531635@typhoon.ne.mediaone.net>   0 "John Vottero" <John@mvpsi.com> wrote in message) news:tturpf8l3d9v10@news.supernews.com...SA > "Terry C. Shannon" <terryshannon@mediaone.net> wrote in messagel: > news:xsHD7.161981$vq.39998738@typhoon.ne.mediaone.net... > >b- > > <lroduner@americhem.com> wrote in messagesA > > news:OF1D818C85.0ADBBB2F-ON85256AF5.007D0CA3@americhem.com...n > >I > > > K > > > I believe that Compaq claims that there are 400,000+ VMS systems withaL > > > 10,000,000 users world-wide (these figures are likely inflated).  What > is > > > the user base for MPE-iX?p > > >o > >sH > > I can't comment on the MPE-iX user base, but you are correct in yourL > > assumption that the VMS installed base numbers are inflated. Word has itK > > that the numbers will be "rightsized" in the near future. Whatever, thet > VMSwJ > > franchise remains profitable, which is more than can be said for CPQ's > > Wintel business these days.s > >a >oJ > They just finished a recount and the new numbers are 410,000 systems andH > 10,000,000 users. Slightly less than 200,000 of the systems are VAXen. >P  @ That's a higher number than I would expect, but it's interestingL nevertheless. Given an Alpha installed base of ~600K systems in January 1999L (internal figure) and extrapolating forward, there probably are ~800K Alphas# out there. Only 25 percent run VMS.i   ------------------------------  % Date: Tue, 30 Oct 2001 21:01:52 -0800n( From: "Greg Cagle" <gregc@gregcagle.com> Subject: Re: OT - HP's MPE-IX,/ Message-ID: <ttv1du5g9jvq18@corp.supernews.com>e  m "Bob Ceculski" <bob@instantwhip.com> wrote in message news:d7791aa1.0110301852.4350eb14@posting.google.com...ti > lroduner@americhem.com wrote in message news:<OF830EA9D3.8598F247-ON85256AF5.0063BF0A@americhem.com>...aN > > Just curious - I know almost nothing about HP's MPE-IX.  I do know that itO > > is a non-UNIX OS developed by HP in the late 1970's to 1980s as a 16-bit OScN > > called MPE, then ported to 32-bits as MPE-IX; and that it is not receivingM > > a lot of work from HP now.  It does have a file system and database builtb > > in also. > >eO > > How difficult would it be to move enough of the MPE-IX system functions andrK > > RTL's to VMS so that the existing MPE-IX applications could be "easily" K > > ported to VMS?  Those applications would then gain the stability of VMS L > > along with the best-in-class clustering and growth offered by VMS.  PlusJ > > additional applications and customers certainly could only enhance theM > > visibility of VMS within CHomPaq, and give those MPE-IX users a future onaJ > > the best OS in the world instead of withering on the vine, as they are > > doing now. >eO > don't waste your brain cells on this crowd ... maybe carly really understandsnJ > the high end unlike capellas and palmer, but i doubt it ... the pc crowdJ > only understand IIS and blue screens and 80% of your time spent applying. > patches ... we will have to wait and see ...  + Are you implying HP is only the "pc crowd?"t   --
 Greg Cagle gregc at gregcagle dot com   ------------------------------  # Date: Wed, 31 Oct 2001 05:44:05 GMT * From: "Bill Todd" <billtodd@metrocast.net> Subject: Re: OT - HP's MPE-IXh@ Message-ID: <FcMD7.11121$tb2.736307@bin2.nnrp.aus1.giganews.com>  = Terry C. Shannon <terryshannon@mediaone.net> wrote in messager7 news:yIKD7.25899$f6.12531635@typhoon.ne.mediaone.net...-   ...-  @ > Given an Alpha installed base of ~600K systems in January 1999G > (internal figure) and extrapolating forward, there probably are ~800Kh Alphas% > out there. Only 25 percent run VMS.   K Hmmm.  A while ago a reference was made to a March (2001) presentation thatCH indicated annual VMS system revenues of $4b and Tru64 system revenues ofJ $3b.  Either one hell of a lot of Linux Alphas are being sold, or each VMSJ system is a great deal more expensive (possibly just due to size) than the4 average Tru64 system, or those numbers were garbage.   - bill   ------------------------------    Date: 30 Oct 2001 17:57:33 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)f6 Subject: Re: OT - HP's MPE-IX - and VMS (cross-posted)3 Message-ID: <3pju0InhRyVb@eisner.encompasserve.org>   W In article <ttu8iumi1mto73@news.supernews.com>, gavin@allegro.com (Gavin Scott) writes: M > Just curious - I know almost nothing about Compaq's VMS.  I do know that itnN > is a non-UNIX OS developed by Dec in the late 1970's to 1980s as a 16-bit OSN > called RSTS/E, then ported to 32-bits as VMS; and that it is not receiving a; > lot of work from Compaq now.  It does have a file system.w  E Actually, it was subsequently ported from 32-bit VAX to 64-bit Alpha,dE and work has recently started to port it to IA64.  But you knew a lotu% more about VMS than I know about MPE.a  J > How difficult would it be to move enough of the VMS system functions andN > Intrinsics to MPE/iX so that the existing VMS applications could be "easily"L > ported to MPE?  Those applications would then gain the stability of MPE/iXL > along with the best-in-class clustering and growth offered by the HP-3000.M > Plus additional applications and customers certainly could only enhance the0L > visibility of MPE within CHomPaq, and give those VMS users a future on theJ > best OS in the world instead of withering on the vine, as they are doing > now.  H As a bold experiment, I have cross-posted this entry between comp.os.vmsG and comp.sys.hp.mpe, hoping that people in the two newsgroups can carrynH on a dignified discussion without any "My OS can beat up your OS" stuff.  @ Describing all of VMS would be a bit complex, but let me try twoB features that are probably more difficult that most for porting toB another environment (certainly not impossible - bits is bits). AndA to keep this techincal rather than political, let's leave out anyoC discussion of what might be required to motivate HP to do one thing, or another.   $ Asynchronous System Transfers (ASTs)$ ====================================  H This is a subroutine a program may provide to be called by the operatingE system when a particular event occurs, such as completion of IO, non-nA completion of IO (timeout), expiration of a timer or interprocessi= communication events.  The AST is executed as an interruptionfF to the program underway, so it is said to be executing at "AST level".A This means that instead of the four modes available to a program: F user/supervisor/executive/kernel (the last three requiring privilege),H there are four other levels interspersed -- the AST level for each mode.> Other than RSX, which you pointed out as an ancestor of VMS, I? have not heard of another operating system with this mechanism.a   Lock Manager ============  F This is a synchronizing service useful as a primitive for implementingE a database, an indexed file system or a myriad of other features. The B lock manager has 6 different modes in which a lock can be held, as
 described at:d  H http://www.openvms.compaq.com:8000/73final/4527/4527pro_036.html#jun_227  4 For more details on how that interface is used, see:  T http://www.openvms.compaq.com:8000/73final/5841/5841pro_021.html#synch_accs_res_chap  ; Note in particular the blocking AST mechanism described at:n  Q http://www.openvms.compaq.com:8000/73final/5841/5841pro_023.html#157_blockingasts   B which shows one of the complex fashions in which ASTs can be used.  D Adding more complexity to the lock manager is the fact that it worksF in a VMS cluster and has for the past 15 years or so, leading to a lot4 of existing software that depends on those features.   ---------------s  C So perhaps someone with knowledge of MPE innards can comment on howl3 difficult it would be to add those features to MPE.e  B In return, perhaps someone could outline some of the more esotericB features of MPE and we could take a stab at seeing how those might be implemented on VMS.  C Again, remember that this topic is cross-posted between comp.os.vmsFD and comp.sys.hp.mpe, so no matter what angle you come from, there is3 _somebody_ who doesn't have the same background :-)M   ------------------------------  % Date: Wed, 31 Oct 2001 01:36:27 -0000 % From: gavin@allegro.com (Gavin Scott) 6 Subject: Re: OT - HP's MPE-IX - and VMS (cross-posted)/ Message-ID: <ttulcroh8m0039@news.supernews.com>   = In comp.os.vms Larry Kilgallen <Kilgallen@spamcop.net> wrote: E > So perhaps someone with knowledge of MPE innards can comment on how 5 > difficult it would be to add those features to MPE.:  D I kind of have the feeling that many of the esoteric features of MPE@ and VMS are tantalizingly similar, yet built on top of low-levelC frameworks that are different enough that merging features between  A the two OSes probably wouldn't be much easier than merging either  one into any other OS.  C Though both are free of Unix's irritating "everything's got to look A like a stream of bytes with no structure other than maybe in-band  record separators" philosophy.  B I suspect that either environment could be somehow merged into theC other, but it would be a heck of a lot of work if you're trying for D something that's a simple "migration" target rather than a "porting"C target.  That is, if people have to make any significant changes to C source code (or even recompile in many cases) then they'll probably  not be interested.  < I'm not sure if a merged OS (or even a halfway decent set of= compatibility fetures) would be any less costly overall than g. continuing to support both systems seperately.  C MPE is pretty mature these days so that most of what we want out ofh< HP is continuing support for new hardware (they've recently C rewritten the MPE I/O subsystem to support the PCI hardware in HP'sSH more recent Unix platform offerings) and peripherals (we're expecting to. finally get native FiberChannel soon I think).  C HP announced their intention to migrate MPE to IA-64 a couple yearssA ago, and reports are that this work is in progress, but it may beo@ a few more before it comes to fruition.  We have an advantage in> that IA-64 is mostly an HP-designed architecture that supportsD efficient runtime translation of PA-RISC code, so we could do fairly@ well with just a good "translated" environment.  The current MPEA versions are object code compatible with everything going back tot> the early 16-bit machines of the 70's and 80's so people will = expect this to continue on IA-64 and it's not clear how many h@ people will be interested in migrating to yet-another-even-more-6 native-mode if "compatibility mode" works well enough.  D > In return, perhaps someone could outline some of the more esotericD > features of MPE and we could take a stab at seeing how those might > be implemented on VMS.  G I don't know about esoteric particularly, but like any good proprietarye@ OS we have lots of complex things that applications depend on to@ behave in a particular way.  File types ASCII, binary, fixed andE variable records, KSAM (indexed) files, bytestream files (and a wholenD associated Posix environment that's fully integrated), Message filesE (basically persistent FIFOs with more bells and whistles than a swiss F army knife, including asynchronous callbacks), The TurboImage databaseC system with its associated Allbase SQL interface (which is the datatI repository used by virtually all significant MPE applications), spooling,tD batch scheduling, the Command Interpreter language that all "JCL" isB written in, various obscure programming languages, a really whizzo) go-everywhere system-level debugger, etc.n  E > Again, remember that this topic is cross-posted between comp.os.vmsmF > and comp.sys.hp.mpe, so no matter what angle you come from, there is5 > _somebody_ who doesn't have the same background :-)>  D I think the majority of comp.sys.hp.mpe readers get messages via theB HP3000-L mailing list (info and archives at http://raven.utc.edu/)B so they'll all see crossposts to comp.sys.hp.mpe, but replies will@ only get gatewayed back to comp.sys.hp.mpe, so the vms crowd may( miss some of the discussion as a result.   G.   ------------------------------    Date: 30 Oct 2001 21:06:52 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)s6 Subject: Re: OT - HP's MPE-IX - and VMS (cross-posted)3 Message-ID: <3aqvaY4wsklr@eisner.encompasserve.org>t  W In article <ttulcroh8m0039@news.supernews.com>, gavin@allegro.com (Gavin Scott) writes: ? > In comp.os.vms Larry Kilgallen <Kilgallen@spamcop.net> wrote:nF >> So perhaps someone with knowledge of MPE innards can comment on how6 >> difficult it would be to add those features to MPE.  D > I suspect that either environment could be somehow merged into theE > other, but it would be a heck of a lot of work if you're trying for0F > something that's a simple "migration" target rather than a "porting"E > target.  That is, if people have to make any significant changes touE > source code (or even recompile in many cases) then they'll probablyk > not be interested.  3 Certainly the goal is to avoid source code changes.,B I think the major advantage is for third parties who might want to? sell onto both customer bases.  For end users, the availability / of additional applications is often desireable.e  I > I don't know about esoteric particularly, but like any good proprietaryaB > OS we have lots of complex things that applications depend on toB > behave in a particular way.  File types ASCII, binary, fixed andG > variable records, KSAM (indexed) files, bytestream files (and a wholemF > associated Posix environment that's fully integrated), Message filesG > (basically persistent FIFOs with more bells and whistles than a swiss.H > army knife, including asynchronous callbacks), The TurboImage databaseE > system with its associated Allbase SQL interface (which is the dataeK > repository used by virtually all significant MPE applications), spooling, F > batch scheduling, the Command Interpreter language that all "JCL" isD > written in, various obscure programming languages, a really whizzo+ > go-everywhere system-level debugger, etc.3  B Those are all familiar VMS concepts with the following exceptions:  B The VMS database situation is quite different.  After developing aC Codasyl database and a Relational database with the same underlyingcD engine, DEC for a brief time bundled the Relational version with theE operating system, but then they unbundled it and sold both to Oracle.tA Thus you will find VMS applications using the indexed file system @ as a matter of course, but not the relational database except in& certain database-centric applications.  C Ah, yes, "JCL".  The "DCL" use on VMS is the same language for botho interactive and batch jobs.d  F >> Again, remember that this topic is cross-posted between comp.os.vmsG >> and comp.sys.hp.mpe, so no matter what angle you come from, there is 6 >> _somebody_ who doesn't have the same background :-) > F > I think the majority of comp.sys.hp.mpe readers get messages via theD > HP3000-L mailing list (info and archives at http://raven.utc.edu/)D > so they'll all see crossposts to comp.sys.hp.mpe, but replies willB > only get gatewayed back to comp.sys.hp.mpe, so the vms crowd may* > miss some of the discussion as a result.    Thanks for the heads-up on that.   ------------------------------  % Date: Tue, 30 Oct 2001 22:36:12 +0000e1 From: Steve Reece <SYSTEM@ipl.demon.co.nospam.uk>o Subject: Re: Printing to NLA0:?.6 Message-ID: <3BDF2B5C.4E9C79B9@ipl.demon.co.nospam.uk>   Michael Moroney wrote: <trim> > L > The device characteristics of the null device (sharable) aren't appropiateF > to a printer device (allocatable to a symbiont) which is why you see > this.p >  <trim>  F I would disagree on this for short life queues (like those used in theF product installation tests for DCPS which do print to queues on the NL device IIRC......) -- sG "A shadow fell over her face; clear, as if the composure were rent liketE a veil.  And her lips parted, but only with a short intake of breath. A Then she said, 'Well, then you are right.  Indeed, we are even.'"4% 		Louis, "Interview with the Vampire"l   ------------------------------  % Date: Tue, 30 Oct 2001 22:12:02 -0500-) From: John Johnstone <jj_usenet@mail.com> / Subject: Re: Promotion at Channel Support Groupa( Message-ID: <3BDF25B2.5E6F1716@mail.com>  I How about forwarding a copy of the e-mail to the guy's ISP as seen by therJ mail headers?  I got one from smp-server.smp-corp.com ([208.34.84.202]) soH I forwarded it to abuse@netacc.net since netacc.net was shown by an ARIN lookup on 208.34.84.202.     Paul Sture wrote:n > V > In article <1050382847.1004102452328.JavaMail.administrator@lp1>, Andy O'Mara wrote: > [a load of unwanted html]m > Q > Has this guy spammed the whole newsgroup via private mail? I certainly got one.s > ___w > Paul Sture
 > Switzerlandw   ------------------------------    Date: 30 Oct 2001 18:58:23 -0800( From: bob@instantwhip.com (Bob Ceculski)B Subject: Re: Request for help with ANALYZE/ERROR disk error report= Message-ID: <d7791aa1.0110301858.57dfa6ee@posting.google.com>e  s SPAMSINK2001@YAHOO.COM (Alan E. Feldman) wrote in message news:<343f30ae.0110300526.10f16d53@posting.google.com>...a > Hello, > B > Can anyone please help me interpret this disk error report? What@ > happened and how serious is it? What do "TRACK FOLLOWING ERROR; > OCCURRED" and "WRITE EXTENDED" mean? Does the presence ofsG > "%SYSTEM-S-NORMAL, NORMAL SUCCESSFUL COMPLETION" always imply a "softaC > error" not generally worth worrying about except perhaps in largei
 > numbers? > H > TIA;  Disclaimer: JMHO;  Alan E. Feldman;  afeldman atski gfigroup.com > replace atski with at-sign.h >  u > $ TYPE DISKERR.POSTtH >  V A X / V M S        SYSTEM ERROR REPORT         COMPILED 29-OCT-2001
 > 03:48:52G >                                                                      , > PAGE   1.  >  d1 >  ******************************* ENTRY    1288.o! > ******************************* H >  ERROR SEQUENCE 17830.                           LOGGED ON:        SID
 > 13000202H >  DATE/TIME 29-OCT-2001 00:09:38.05                            SYS_TYPE
 > 03260901" >  SYSTEM UPTIME: 38 DAYS 08:51:24H >  SCS NODE: XXXXX                                               VAX/VMS > V6.1 >  1A >  DEVICE ERROR KA51  CPU Microcode Rev # 2.  CONSOLE FW REV# 2.6iB >                       Standard Microcode Patch    Patch Rev # 1. >  .' >  RZ28 SUB-SYSTEM, UNIT _IDS09$DKA100:  >  b! >        HW REVISION     43313444c; >                                        HW REVISION = D41C ! >        ERROR TYPE            05eE >                                        EXTENDED SENSE DATA RECEIVEDs! >        SCSI ID               01s5 >                                        SCSI ID = 1.t! >        SCSI LUN              00l6 >                                        SCSI LUN = 0.! >        SCSI SUBLUN           00i9 >                                        SCSI SUBLUN = 0.u! >        PORT STATUS     00000001dA >                                        %SYSTEM-S-NORMAL, NORMAL  > SUCCESSFUL4 >                                         COMPLETION! >        SCSI CMD        3C00002A ! >                        000081A2 ! >                            0078 7 >                                        WRITE EXTENDED ! >        SCSI STATUS           02a8 >                                        CHECK CONDITION >  - >  EXTENDED SENSE DATA >  g! >        EXTENDED SENSE  000300F0-! >                        0AB2A23C0! >                        00620000l! >                        00020009O! >                            000075 >                                        MEDIUM ERROR G >                                        TRACK FOLLOWING ERROR OCCURRED9! >        UCB$B_ERTCNT          04t= >                                        4. RETRIES REMAININGs! >        UCB$B_ERTMAX          00e= >                                        0. RETRIES ALLOWABLE ! >        ORB$L_OWNER     00010004S< >                                        OWNER UIC [001,004]! >        UCB$L_CHAR      1C4D4008u= >                                        DIRECTORY STRUCTURED.6 >                                        FILE ORIENTED1 >                                        SHARABLEv2 >                                        AVAILABLE0 >                                        MOUNTED6 >                                        ERROR LOGGING9 >                                        CAPABLE OF INPUTn: >                                        CAPABLE OF OUTPUT6 >                                        RANDOM ACCESS >  tH >  V A X / V M S        SYSTEM ERROR REPORT         COMPILED 29-OCT-2001
 > 03:48:52G >                                                                      i > PAGE   2.n >   ! >        UCB$W_STS           00000! >        UCB$L_OPCNT     000D435Ed@ >                                        869214. QIO'S THIS UNIT! >        UCB$W_ERRCNT        0001.< >                                        1. ERRORS THIS UNIT! >        IRP$W_BCNT          8000AE >                                        TRANSFER SIZE 32768. BYTE(S) ! >        IRP$W_BOFF          0000a> >                                        TRANSFER PAGE ALIGNED! >        IRP$L_PID       004C002Di8 >                                        REQUESTOR "PID"! >        IRP$Q_IOSB      00000001 E >                        00DF0000        IOSB, 0. BYTE(S) TRANSFERREDbC > ANAL/ERROR/INCL=DISK/SINC=28-OCT-2001 00:00:00.00/OUT=DISKERR.LISd > $a  H normally on extended data errors you will see a follow up status postingG saying "successful" ... if not i would call software support ... if theOD extended data errors continue to mount, then it may be time to buy aC new disk or controller ... also check your connections and for dirtcA and dust problems or a fan problem as heat can cause problems ...g   ------------------------------  # Date: Tue, 30 Oct 2001 19:53:13 GMTp' From: Don Sykes <anonymous@pacbell.net> * Subject: Re: savesets,  CDs and attributes+ Message-ID: <3BDF0672.F02E9117@pacbell.net>t  < I use the VMS exchange command when doing such things. e.g.:+ 1)  $ anal/rms/fdl/out=ASD.FDL  ASD.saveSetc* 2)  ftp your save set (using binary), thenB 3)  $ exchange/net/trans=BLOCK/fdl=ASD.FDL ASD.saveSet ASD.saveSet, Your file will be back to its original form. Don    Michael Worsley wrote: >  > Hi,= > M > Our company is looking at distributing the VAX version of our product on CD  > instead of TK50. > J > Unfortunately, FTPing our saveset from the CD back to the VAX resets the > record length to 512bytes. > J > I have looked at RESET_BACKUP_SAVESET_ATTRIBUTES.COM but, unfortunately,D > some of our customers use VAX/VMS 5.5-2, which doesn't support theC > /ATTRIBUTES  qualifier to SET FILE that is used to reset the files
 > attributes.t > 6 > Any suggestions of another approach I could look at? >  > --	 > Michaele   ------------------------------  % Date: Tue, 30 Oct 2001 21:22:43 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>t* Subject: Re: savesets,  CDs and attributes' Message-ID: <3BDF6E83.E055C1CA@fsi.net>    Jan-Erik Sderholm wrote:a > 9 > Why not just use $COPY to copy from the CD to the VAX ?t   If the CD is ISO-9660, ...   --   David J. Dachtera6 dba DJE Systemsi http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/7   ------------------------------  % Date: Tue, 30 Oct 2001 22:01:01 -0500:% From: "John Vottero" <John@mvpsi.com>7. Subject: Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM/ Message-ID: <ttuqbfmrkjgn1b@news.supernews.com>   F For me, the V7.3 DAYLIGHT_SAVINGS.COM didn't work at all.  It wound upL executing UTC$CONFIGURE_TDF.COM which just displays a message saying that itI is an obsolete command procedure and I should be using UTC$TIME_SETUP.COMt  E "Charlie Hammond" <hammond@not@peek.ppb.cpqcorp.net> wrote in messaged- news:qxiD7.1078$RL6.14936@news.cpqcorp.net... D > In article <3bd87ee1$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes:5 > >In article <nDYB7.968$RL6.10436@news.cpqcorp.net>,f: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond) writes:4 > >>The official patch for this is VMS73_DTSS-V0100.7 > >>As stated below, this applies ONLY to OpenVMS V7.3.o > >> > >>The kit is available at: > >> >cL >>http://ftp1.support.compaq.com/public/vms/axp/v7.3/vms73_dtss-v0100.README > >c) > >Does the problem only exist on Alpha ?h > K > The procedure is common to Alpha and VAX, but it has various architecturecK > specific code.  I do not know if this problem will be encountered on VAX.O > K > It should be safe to extract the file from the Alpha kit and copy it ontoeE > an OpenVMS VAX system.  Of you can make the correction I previouslye posted.p >a. > I will ask that a VAX kit be made available. >t > --I >     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FLe USAfJ >        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)L >       All opinions expressed are my own and not necessarily my employer's. >    ------------------------------    Date: 30 Oct 2001 14:01:18 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen).# Subject: Re: Unix-based, VMS-based?r3 Message-ID: <OvoLEUMhJjf8@eisner.encompasserve.org>b  w In article <NKBD7.2950$tb2.211364@bin2.nnrp.aus1.giganews.com>, "John Gemignani, Jr." <john@REMOVETHISossc.net> writes: L > I'm getting curious.  I am seeing a lot about "Unix-based" and "VMS-based" > references in here lately. > N > What is "unix-based" software and "vms-based" software?  That is, aside fromI > the obvious suggestion that one was developed on a particular platform.e  E Unix-based software, for one thing, leaves all parsing of the commandeH line up to the application, feeding it a giant expansion of the command.> Its interaction with the operating system is likely limited toA routines in the C runtime library, even if the program is writteno in a language other than C.P  > VMS-based software may use ASTs.  It may call system services.   ------------------------------    Date: 30 Oct 2001 18:20:50 -0800( From: bob@instantwhip.com (Bob Ceculski)# Subject: Re: Unix-based, VMS-based? = Message-ID: <d7791aa1.0110301820.42b00fba@posting.google.com>i  | "John Gemignani, Jr." <john@REMOVETHISossc.net> wrote in message news:<NKBD7.2950$tb2.211364@bin2.nnrp.aus1.giganews.com>...L > I'm getting curious.  I am seeing a lot about "Unix-based" and "VMS-based" > references in here lately. > N > What is "unix-based" software and "vms-based" software?  That is, aside fromI > the obvious suggestion that one was developed on a particular platform.c > I > With the Unix-based code probably written in C, and the VMS-based stufftN > (TCPWARE) written in Macro-32 (i.e. VAX), what else would be the difference? > I > Performance has to be measured in some way. The direct performance of arN > network kernel is usually not cited.  It's usually FTP, or NFS, or whatever.N > If a product with a Unix-based kernel is running VMS-based applications, howN > is it characterized?  If the VMS application yields bad performance numbers,) > is that because of a Unix-based kernel?y >  > -Johnt >e  I we are talking about apps written using either the vms or unix kernel ... D the people who wrote tcpware used the vms kernel as their base, theyB were former dec engineers and knew vms well, and people at processI software today will tell you today how good the vms kernel really is, andiH how good of a vms ip stack tcpware is ... if your os kernel is that goodF then i imagine any well written app that uses that kernel as its basisF will outperform similar apps based on other kernels ... this is common sense, not rocket science!   ------------------------------  % Date: Tue, 30 Oct 2001 21:50:18 +0000a1 From: Steve Reece <SYSTEM@ipl.demon.co.nospam.uk>r Subject: Re: VMSMail APIs?6 Message-ID: <3BDF209A.17B97403@ipl.demon.co.nospam.uk>  C I'm not sure if this response relates to the initial query but.....   H One thing that I find strange about VMS mail and the APIs for it is thatA although there are calls for sending mail out from a higher levelaH language, no such APIs (or, as we used to call them, Run Time Libraries)G exist for RECEIVING mail.  So, for example, SMTP mail receipt on VMS iss& effectively a kludge from what I hear.   Steve.     david20@alpha2.mdx.ac.uk wrote:  > q > In article <b2faac46.0110090442.79f92342@posting.google.com>, on_the_move4ever@yahoo.com (Rick Nickles) writes:2F > >You'll have to log a call with support.  All this information isn't" > >readily available to customers. > >s > >eV > >paul@wren.cc.kux.edu wrote in message news:<3bc1e63f.18304210@news.cc.ukans.edu>...A > >> Where, in manuals, or on-line can one find the VMSMail APIs?c > >> > >> Thanks! > N > Look at chapter 14 in the OpenVMS Utility Routines manual which is available > online see :-n > Z > http://www.openvms.compaq.com:8000/73final/4493/4493pro_contents_002.html#toc_chapter_14 >  > David Webb > VMS and Unix team leader > CCSS > Middlesex University   --  G "A shadow fell over her face; clear, as if the composure were rent liketE a veil.  And her lips parted, but only with a short intake of breath.yA Then she said, 'Well, then you are right.  Indeed, we are even.'"c% 		Louis, "Interview with the Vampire"i   ------------------------------  % Date: Tue, 30 Oct 2001 17:08:17 -0500 4 From: John Malmberg <Malmberg@dskwld.zko.dec.compaq> Subject: Re: VMSMail APIs?4 Message-ID: <3BDF24D1.3000706@dskwld.zko.dec.compaq>   Steve Reece wrote:  E > I'm not sure if this response relates to the initial query but.....a > J > One thing that I find strange about VMS mail and the APIs for it is thatC > although there are calls for sending mail out from a higher levelxJ > language, no such APIs (or, as we used to call them, Run Time Libraries)I > exist for RECEIVING mail.  So, for example, SMTP mail receipt on VMS iss( > effectively a kludge from what I hear.    E Receiving MAIL requires an agent.  VMSMAIL knows about DECNET and VMSb+ has an agent registered as a DECNET object.   I For receiving SMTP, you have a TCP/IP service that acts as the agent.  I yH do not know, but I would assume that it would call the existing VMS MAIL1 API instead of having to duplicate the functions.   G If you are looking for notification when a VMS mail message arrives for F a user, you must either periodically check for new mail using the API,F or if the MAIL$SYSTEM_FLAGS are set, you could intercept the broadcast messages with a program.  0 But tell us what you are really trying to solve.   -John  Malmberg@dskwld.zko.dec.compaq Personal Opinion Onlyl   ------------------------------  + Date: Wed, 31 Oct 2001 00:02:16 +0000 (UTC)a From: david20@alpha1.mdx.ac.uk Subject: Re: VMSMail APIs?+ Message-ID: <9rnf28$1m6$1@aquila.mdx.ac.uk>   j In article <3BDF209A.17B97403@ipl.demon.co.nospam.uk>, Steve Reece <SYSTEM@ipl.demon.co.nospam.uk> writes:D >I'm not sure if this response relates to the initial query but..... >aI >One thing that I find strange about VMS mail and the APIs for it is thatmB >although there are calls for sending mail out from a higher levelI >language, no such APIs (or, as we used to call them, Run Time Libraries) H >exist for RECEIVING mail.  So, for example, SMTP mail receipt on VMS is' >effectively a kludge from what I hear.a >t >Steve.n >c  9 What sort of an API do you want for receiving SMTP mail ?uN Like in any SMTP mail system you have a daemon (detached process) listening onN port 25 which deals with receiving the mail and then passes it on for delivery, to user's mailboxes or forwarding elsewhere.  0 Can you explain more fully what you want to do ?  
 David Webb VMS and Unix team leader CCSS Middlesex University     >-  >david20@alpha2.mdx.ac.uk wrote: >> pr >> In article <b2faac46.0110090442.79f92342@posting.google.com>, on_the_move4ever@yahoo.com (Rick Nickles) writes:G >> >You'll have to log a call with support.  All this information isn'tu# >> >readily available to customers.  >> > >> >W >> >paul@wren.cc.kux.edu wrote in message news:<3bc1e63f.18304210@news.cc.ukans.edu>...hB >> >> Where, in manuals, or on-line can one find the VMSMail APIs? >> >>o
 >> >> Thanks!l >> aO >> Look at chapter 14 in the OpenVMS Utility Routines manual which is available  >> online see :- >>  [ >> http://www.openvms.compaq.com:8000/73final/4493/4493pro_contents_002.html#toc_chapter_14h >> V
 >> David Webb- >> VMS and Unix team leader  >> CCSS, >> Middlesex University0 >  >-- H >"A shadow fell over her face; clear, as if the composure were rent likeF >a veil.  And her lips parted, but only with a short intake of breath.B >Then she said, 'Well, then you are right.  Indeed, we are even.'"& >		Louis, "Interview with the Vampire"   ------------------------------    Date: 30 Oct 2001 16:38:50 -0800$ From: smgcircle@home.com (smgcircle) Subject: VT520 Setup= Message-ID: <20eea475.0110301638.704f96b1@posting.google.com>3  C Does anyone know if it is possible to disable the setup key and theeF setup functions on a VT520? We're lookiing for a way to stop the users from making changes.   Thanks for your help.    == Steve ==    ------------------------------  % Date: Tue, 30 Oct 2001 23:36:32 -0500 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: VT520 SetupL Message-ID: <rdeininger-3010012336320001@user-2ive7ad.dialup.mindspring.com>  = In article <20eea475.0110301638.704f96b1@posting.google.com>,e% smgcircle@home.com (smgcircle) wrote:3  E > Does anyone know if it is possible to disable the setup key and thep > setup functions on a VT520?   , > We're lookiing for a way to stop the users > from making changes.   Permanently, or temporarily?  ' If the latter, amputation is Right Out.A   :-)A  J I dunno.  I've never used a VT520.  But in dire straights, you could breakJ the contacts on the setup key.  Keep an undamaged keyboard to plug in whenI YOU need to change the setup, but only let the meddling users have brokena
 keyboards.  J Or, modify the keyboard so the setup key still works, but applies about 75I volts to anyone who presses it.  You could call this a user-training aid.   J I'm not really in the mood for pesky users right now, so I better skip any further suggestions...   -- * Robert Deininger rdeininger@mindspring.comE   ------------------------------  % Date: Wed, 31 Oct 2001 05:42:52 +0100D2 From: martin@radiogaga.harz.de (Martin Vorlaender) Subject: Re: VT520 Setup; Message-ID: <3bdf814c.524144494f47414741@radiogaga.harz.de>   % smgcircle (smgcircle@home.com) wrote: E > Does anyone know if it is possible to disable the setup key and theOH > setup functions on a VT520? We're lookiing for a way to stop the users > from making changes.  H One of our customers physically disconnected the F3 key in the keyboard.B There, you have to have an "admin keyboard" to change the terminal settings :-)   cu,    Martin --  D                        |  Martin Vorlaender  |  VMS & WNT programmer1   OpenVMS: When you    |  work: mv@pdv-systeme.de E   KNOW where you want  |     http://www.pdv-systeme.de/users/martinv/l8   to go today.         |  home: martin@radiogaga.harz.de   ------------------------------  # Date: Tue, 30 Oct 2001 22:56:11 GMT  From: webtrading@schwab.com $ Subject: Weird Hobbyist PAK behavior8 Message-ID: <3bdf2e4c.31068912@news.scrmnt1.ca.home.com>  B I just got a new pak from Montague for my new 3100/40s and enteredC them by hand at the end of the O/S load and got an invalid checksum F message.  I tried it about 5-6 times, carefully checking the auth. andD checksum and always got an error. I went out and got another PAK andC had the same problem. I then created a .com file and it worked just  fine.   F I have entered PAKS on VAXEN by hand LOTS of times and never had this,F and I have also done it with .com files and except for the usual typosB and fat-fingering, not had any problems. I have done this with VMS since they went to PAKS.    Any ideas?   E BTW, my e-mail address is in the .sig and its broken up for the usualE reason. * ------------------------------------------< NO, John Mee3 at home dot com (remove the spaces and do the # obvious with the "dot" and the "at"    ------------------------------  # Date: Tue, 30 Oct 2001 23:05:47 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)( Subject: Re: Weird Hobbyist PAK behavior3 Message-ID: <fnGD7.1127$RL6.16169@news.cpqcorp.net>U  V In article <3bdf2e4c.31068912@news.scrmnt1.ca.home.com>, webtrading@schwab.com writes:C :I just got a new pak from Montague for my new 3100/40s and enteredLD :them by hand at the end of the O/S load and got an invalid checksumG :message.  I tried it about 5-6 times, carefully checking the auth. and # :checksum and always got an error.    E   Check *elsewhere* in what you entered.  The checksum might be fine, E   and this failure can arise if the checksum doesn't match something R"   else that was entered elsewhere.  G :I have entered PAKS on VAXEN by hand LOTS of times and never had this, G :and I have also done it with .com files and except for the usual typos C :and fat-fingering, not had any problems. I have done this with VMS  :since they went to PAKS.  :  : Any ideas?  M   The VMSLICENSE tool is usually a simple and effective option when entering  I   license PAKs, but I usually use the LICENSE REGISTER command directly. T  L   Without seeing the specifics of the PAKs and the commands involved -- and J   please don't post the checksums -- there was very likely a subtle error A   in what you were entering.  I've stared at these errors myself.   J   I've been talking to some of the Montagar-related folks about providing D   the PAKs in command procedures, and some other PAK-related issues.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Wed, 31 Oct 2001 02:20:09 GMT  From: webtrading@schwab.com-( Subject: Re: Weird Hobbyist PAK behavior8 Message-ID: <3bdf5e07.43289635@news.scrmnt1.ca.home.com>  E On Tue, 30 Oct 2001 23:05:47 GMT, hoffman@xdelta.zko.dec.nospam (Hoff  Hoffman) wrote:x  W >In article <3bdf2e4c.31068912@news.scrmnt1.ca.home.com>, webtrading@schwab.com writes: D >:I just got a new pak from Montague for my new 3100/40s and enteredE >:them by hand at the end of the O/S load and got an invalid checksum H >:message.  I tried it about 5-6 times, carefully checking the auth. and$ >:checksum and always got an error.  >rF >  Check *elsewhere* in what you entered.  The checksum might be fine,F >  and this failure can arise if the checksum doesn't match something # >  else that was entered elsewhere.R >TH >:I have entered PAKS on VAXEN by hand LOTS of times and never had this,H >:and I have also done it with .com files and except for the usual typosD >:and fat-fingering, not had any problems. I have done this with VMS >:since they went to PAKS. >:
 >: Any ideas?? > N >  The VMSLICENSE tool is usually a simple and effective option when entering J >  license PAKs, but I usually use the LICENSE REGISTER command directly. D Usually I use the VMSLICENSE tool myself, interestingly the MontagarA command procedure had a "/date" parameter that VMS License didn'tt@ have. That may have been the problem. When I generated a commandF procedure and used the /date parameter, not the "product release date"4 that was in the VMSLICENSE tool part of the startup.  M >  Without seeing the specifics of the PAKs and the commands involved -- and :K >  please don't post the checksums -- there was very likely a subtle error EB >  in what you were entering.  I've stared at these errors myself.F I went over each command very carefully. Interestingly enough that PAK/ /date parameter that may have been the problem.t  K >  I've been talking to some of the Montagar-related folks about providing lE >  the PAKs in command procedures, and some other PAK-related issues.p  F I notice that this one did come as a command procedure. Of course thatC meant I would have to transfer it to tape on a running VAX and then B load it from there.  Easier just to fire up EVE and create it that way.  ; On the second machine, I was able to type it in just fine. w  	 Oh, well.h   Thanks.p  * ------------------------------------------< NO, John Mee3 at home dot com (remove the spaces and do the # obvious with the "dot" and the "at"p   ------------------------------  % Date: Tue, 30 Oct 2001 22:28:38 -0500c% From: "John Vottero" <John@mvpsi.com>h( Subject: Re: Weird Hobbyist PAK behavior/ Message-ID: <tturv7evrc5649@news.supernews.com>p  ( <webtrading@schwab.com> wrote in message2 news:3bdf5e07.43289635@news.scrmnt1.ca.home.com...G > On Tue, 30 Oct 2001 23:05:47 GMT, hoffman@xdelta.zko.dec.nospam (HoffV > Hoffman) wrote:c >m; > >In article <3bdf2e4c.31068912@news.scrmnt1.ca.home.com>,t webtrading@schwab.com writes:.F > >:I just got a new pak from Montague for my new 3100/40s and enteredG > >:them by hand at the end of the O/S load and got an invalid checksumeJ > >:message.  I tried it about 5-6 times, carefully checking the auth. and% > >:checksum and always got an error.- > >-H > >  Check *elsewhere* in what you entered.  The checksum might be fine,G > >  and this failure can arise if the checksum doesn't match something-% > >  else that was entered elsewhere.o > > J > >:I have entered PAKS on VAXEN by hand LOTS of times and never had this,J > >:and I have also done it with .com files and except for the usual typosF > >:and fat-fingering, not had any problems. I have done this with VMS > >:since they went to PAKS. > >: > >: Any ideas?b > > F > >  The VMSLICENSE tool is usually a simple and effective option when enteringK > >  license PAKs, but I usually use the LICENSE REGISTER command directly.rF > Usually I use the VMSLICENSE tool myself, interestingly the MontagarC > command procedure had a "/date" parameter that VMS License didn'tlB > have. That may have been the problem. When I generated a commandH > procedure and used the /date parameter, not the "product release date"6 > that was in the VMSLICENSE tool part of the startup. >-J > >  Without seeing the specifics of the PAKs and the commands involved -- andCL > >  please don't post the checksums -- there was very likely a subtle errorD > >  in what you were entering.  I've stared at these errors myself.H > I went over each command very carefully. Interestingly enough that PAK1 > /date parameter that may have been the problem.n >   > The "/DATE=" qualifier is called the "Key Termination Date" in VMSLICENSE.COM.    ------------------------------  # Date: Wed, 31 Oct 2001 03:50:28 GMTh From: webtrading@schwab.com ( Subject: Re: Weird Hobbyist PAK behavior8 Message-ID: <3bdf7483.49045762@news.scrmnt1.ca.home.com>  C On Tue, 30 Oct 2001 22:28:38 -0500, "John Vottero" <John@mvpsi.com>e wrote:  ) ><webtrading@schwab.com> wrote in messageo  ? >The "/DATE=" qualifier is called the "Key Termination Date" ine >VMSLICENSE.COM.  B That's what I surmised, and tried it that way, but it didn't work.D It's easier just to put it into a license register .com file anyway.* ------------------------------------------< NO, John Mee3 at home dot com (remove the spaces and do the # obvious with the "dot" and the "at"l   ------------------------------  % Date: Tue, 30 Oct 2001 21:50:18 -0500e) From: John Johnstone <jj_usenet@mail.com>h7 Subject: Re: [AMDS V7.3A] Problem on OpenVMS VAX V7.3 ?l( Message-ID: <3BDF209A.6613F8D8@mail.com>  H This is probably stating the obvious but but I'll mention it anyway.  DoG you have the AMDS V7.3 .lib files (sys$common:[amds]amds$vmsaxp-v73.libaE and/or amds$vmsvax-v73.lib) on your system(s) that are generating the  error?       Peter LANGSTOEGER wrote:I > I installed AMDS V7.3 a couple of months ago on my OpenVMS VAX V7.2 and-< > OpenVMS Alpha V7.2-1 systems. All was working as expected. > G > But after upgrading OpenVMS VAX to V7.3, every AMDS Console could notDL > connect to the AMDS Collector (RMDRIVER) on this system. The error message > on the console isy > N > %AMDS-W-BADPARAM, bad parameter for program RMCONFIG request for node ......1 > %TRACE-W-TRACEBACK, symbolic stack dump followsrN > module name     routine name                     line       rel PC    abs PC > O > COMM_UTILITY    AMDS$CheckIosbStatus            65934      000003D1  000538F9sO > COMM_UTILITY    ConfigDone                      66413      0000008E  00053E92wO > ECL_ROUTINES    ecl$send                        62953      0000015D  00058EB5eO > COMM_UTILITY    greetings                       67220      000003A4  00054790uO > DECAMDS         rcv_from_comm                   63058      00000196  000511D6eO > DECAMDS         AMDS$check_message              62917      00000010  00051020eO >                                                            001B095C  001B095C O >                                                            001B0C2B  001B0C2BcO >                                                            001AFFC5  001AFFC5lO >                                                            001AFFA1  001AFFA1tO > DECAMDS         main                            62292      000008CC  00050644  >  > L > So, I thought I need to reinstall AMDS because of a change in kernel (haveF > been seen by me with AMDS on Alpha but so far not on VAX). Bad luck.E > AMDS on OpenVMS Alpha V7.3 does run, but on VAX still the BADPARAM.- >  > Am I alone ? >  > -- a> > Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651= > Network and OpenVMS system manager  Fax.    +43 1 81111-888-> > <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netJ > A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------   End of INFO-VAX 2001.605 ************************