1 INFO-VAX	Tue, 05 Apr 2005	Volume 2005 : Issue 190       Contents:; Re: ANN: PWAIT$SDA and MBU freeware updates from Ian Miller  Broken vax4000, Different behaviour of HP C on Alpha and VAX0 Re: Different behaviour of HP C on Alpha and VAX0 Re: Different behaviour of HP C on Alpha and VAX% DS15 - RADEON - VMS732 GRAPHICS V 3.0 5 Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1? * Re: problem with router---NAT and caching? Remote printing woes.  Re: VMS Command language.  Re: VMS Command language.  Re: VMS Command language.  Re: VMS Command language.   F ----------------------------------------------------------------------   Date: 5 Apr 2005 07:26:19 -0700   From: "Ian Miller" <ijm@uk2.net>D Subject: Re: ANN: PWAIT$SDA and MBU freeware updates from Ian MillerC Message-ID: <1112711179.371939.144000@z14g2000cwz.googlegroups.com>   D note that MBU V1.5 seems to have problems on Alpha V8.2 and I've not tried it on I64 V8.2.   E The SHOW MAILBOX command appears to work differently parhaps due to a D change in behaviour of $DEVICE_SCAN and the VIEW command can lead to your process hanging.    I'm looking at these problems.  . Send feedback to the email address in the kit.   ------------------------------  % Date: Tue, 05 Apr 2005 12:20:02 -0600 " From: GreyCloud <cumulus@mist.com> Subject: Broken vax4000 ( Message-ID: <4252D6D2.68F70223@mist.com>  : My vax just died...  I notice that the router box has only7 one light lit instead of two.  The Full/Col light isn't < lit.  The o/s doesn't boot up.  So I installed a spare drive with a spare o/s on it.  No go.  Any ideas as to the next step??    ------------------------------   Date: 5 Apr 2005 02:03:02 -0700 1 From: ralf.gaertner@t-systems.com (Ralf Gaertner) 5 Subject: Different behaviour of HP C on Alpha and VAX = Message-ID: <e1b5cbf1.0504050103.4df3235d@posting.google.com>   E I have a program which generates different messages on Alpha and VAX.   + - VAXstation 4000 , VMS 7.2 , DEC C 6.4-005   E   CC/DECC/OBJ=DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.VAX_OBJ_V72      /DEFINE=(OPENVMS) 2 DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.C/LIST  ( - DS10 , VMS 7.2-1 , DEC C 6.4-005-46B10  C   CC/OBJ=DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.AXP_OBJ_V721 -      /DEFINE=(OPENVMS) 2 DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.C/LIST  B On the VAX the compiler does it's job without any messages, on the Alpha I get * a "informational message" and a "warning":   3122 extern int strlen();  ...........1> %CC-I-INTRINSICINT, (1) In this statement, the return type for	 intrinsic 1 "strlen" is being changed from "size_t" to "int".   A 3383 strcpy(collate+1," \1\2\3\4\5\6\7\10\11\12\13\14\15\16\17"); = .......1                                                      E %CC-W-PTRMISMATCH1, (1) In this statement, the referenced type of the  pointer B value "collate+1" is "unsigned char", which is not compatible with "char"1 because they differ by signed/unsigned attribute.   ? The warning is correct, since the array "collate" is defined as  "unsigned char" E and strcpy wants "char". But why is this only recognized on the Alpha  and not on the VAX ?  E P.S. I am attending the german DECUS symposium so I don't need a fast  explanation.   ------------------------------  # Date: Tue, 05 Apr 2005 13:23:43 GMT 5 From: "Ed Vogel" <edward.vogel_stop_the_spam.@hp.com> 9 Subject: Re: Different behaviour of HP C on Alpha and VAX 1 Message-ID: <zjw4e.2970$Bm.2752@news.cpqcorp.net>   L "Ralf Gaertner" <ralf.gaertner@t-systems.com> wrote in message > The warning3 is correct, since the array "collate" is defined as  > "unsigned char" G > and strcpy wants "char". But why is this only recognized on the Alpha  > and not on the VAX ?  B     As you have not included a full reproducer, I'm guessing about     what is going on....  H     First, I expect you are declaring the library functions strlen() and@     strcpy locally rather than including <string.h> which is the=     recommended way to do things.  If you used <string.h> you 2     would see the PTRMISMATCH1 message but not the      INTRINSICINT message on VAX.  >     Now...getting back to your program.  On Alpha the compilerB     has an optimization we call intrinsic processing.  This is notC     available on VAX.  An intrinsic is a function that the compiler ;     has special knowledge about.  This knowledge will allow <     the compiler to do extra optimizations.  Both strlen and@     strcpy are intrinsics.  For example, consider the statement:         a = strlen("HELLO");5     on VAX this will cause a call to DECC$STRLEN, but :     on Alpha, becuase strlen is an intrinsic, the compiler8     knows what the function does, and the generated code4     simply assigns the value of 5 to the variable a.  >     When a function is an intrinisic, the compiler has its own<     internal declarations for the functions.  These internal:     declarations contain all the type information.  So, on>     Alpha, even though you declarared strcpy with no parameter<     information, the internal compiler declarations have the4     parameters as char * so you see the PTRMISMATCH1:     warning.  Also, when strlen is invoked, the compiler's@     internal definition says that strlen should return a size_t.>     It sees that the user-supplied definition is different, so'     the INTRINSICINT message is output.   9     As you note, the messages are valid.  They are output 3     on Alpha only because Alpha has this additional ;     functionality.  If you disable the intrinsic processing 3     (by using /OPT=NOINTRINSICS) the Alpha compiler 2     will compile the program without diagnositics.       Hope this helps,       Ed Vogel#     DEC/Compaq/HP C/C++ Engineering    ------------------------------  # Date: Tue, 05 Apr 2005 16:35:58 GMT # From: hoff@hp.nospam (Hoff Hoffman) 9 Subject: Re: Different behaviour of HP C on Alpha and VAX 1 Message-ID: <O7z4e.2987$vH.2888@news.cpqcorp.net>   q In article <e1b5cbf1.0504050103.4df3235d@posting.google.com>, ralf.gaertner@t-systems.com (Ralf Gaertner) writes: F :I have a program which generates different messages on Alpha and VAX. : , :- VAXstation 4000 , VMS 7.2 , DEC C 6.4-005 : F :  CC/DECC/OBJ=DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.VAX_OBJ_V72 :    /DEFINE=(OPENVMS)3 :DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.C/LIST  : ) :- DS10 , VMS 7.2-1 , DEC C 6.4-005-46B10  : D :  CC/OBJ=DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.AXP_OBJ_V721 - :    /DEFINE=(OPENVMS)3 :DSA1:[TEXMF2003.SOURCE.CWEB-3-64.VMS]CWEAVE.C/LIST  : C :On the VAX the compiler does it's job without any messages, on the 7 :Alpha I get a "informational message" and a "warning":  :  :3122 extern int strlen();
 :...........1 ? :%CC-I-INTRINSICINT, (1) In this statement, the return type for < :intrinsic "strlen" is being changed from "size_t" to "int". : B :3383 strcpy(collate+1," \1\2\3\4\5\6\7\10\11\12\13\14\15\16\17");> :.......1                                                     F :%CC-W-PTRMISMATCH1, (1) In this statement, the referenced type of theF :pointer value "collate+1" is "unsigned char", which is not compatible> :with "char" because they differ by signed/unsigned attribute. : @ :The warning is correct, since the array "collate" is defined as? :"unsigned char" and strcpy wants "char". But why is this only  - :recognized on the Alpha and not on the VAX ?   I   For some background, the Alpha compiler is newer, and is based on a far    newer code generator.   E   I would look for any local symbols, such as CC.  I do know that the H   more recent C compilers are better at spotting calling-related errors,%   and that may well be the case here.   K   I'd get rid of the extern declaration in the code -- that's busted -- and K   I'd use an include of string.h.  Redefining a standard library routine in H   local code perilous practice at best, and should generally be avoided.  J   If this is an old port, I've found various "creative" porting techniquesJ   in such code and in older ports, and have spent time expurgating the oldF   code -- older ports tend to have work-arounds for routines that wereG   wrong, missing or broken in OpenVMS, and newer libraries tend to have K   better and more compatible libraries, and less need for the work-arounds. D   Some of the work-arounds have caused problems -- I've occasionallyI   presented sessions at various events around porting code and around the F   problems I've seen.  Re-mapping standard library functions to local J   functions is among the more common sources of problems -- local routinesG   should have local names, and not language-defined names.  (Having two I   or more routines with the same name is a technique I've seen used, and  J   it is completely dependent on exactly how the link and the libraries andD   the definition files are implemented on each particular platform.)  J   I've some modules of #defines that I use to temporarily remap the returnK   status codes for some common library functions -- I use these to allow me M   to select more aggressive diagnostics within the C compiler.  That written, J   there are a number of standard C library calls that should have a returnK   status coded, and it is common for programmers to ignore this for some of K   the calls -- the appropriate fix is to code the return status appropriate #   for the function call, of course.   I   I'd also use the compiler-provided __VMS and not the /DEFINE=(OPENVMS), !   but that's personal preference.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------   Date: 5 Apr 2005 17:41:23 +0100 K From: pmoreau@ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.68.40) . Subject: DS15 - RADEON - VMS732 GRAPHICS V 3.0! Message-ID: <oZcR+NorxPbV@sinead>    Hi all,   M Good news, the patch VMS732_GRAPHICS-V0300 is available via ITRC and it seems ; to correct the problems I had wirh a Radeon 7500 on a DS15:   G - No more problems without OPEN3D pack with complete systems hang when  .   playing a bit to much with Dectem scrollbars  & - No problems with Open3D pack with XV  N Hard config: A DS15 audio card in the upper slot, the Radeon in the next slot.  J Thanks for the patch, I will be able to sawpp soon my XP900 for a DS15 (at
 work). Cool.    
 Best regards,    Patrick  --O =============================================================================== N pmoreau@ath.cena.fr  (CENA/SDER) ______      ___   _          (Patrick MOREAU)4 moreau_p@decus.fr (DECUS)       / /   /     / /|  /|J CENA/SDER/Athis-Mons France    / /___/     / / | / |   __   __   __   __  N BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  |N 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__|N http://www.ath.cena.fr/~pmoreau/              http://membres.lycos.fr/pmoreau/O ===============================================================================    ------------------------------  # Date: Tue, 05 Apr 2005 16:23:27 GMT # From: hoff@hp.nospam (Hoff Hoffman) > Subject: Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1?1 Message-ID: <3Yy4e.2985$vH.1818@news.cpqcorp.net>   h In article <pcp351l431r7t45sid50gudu4ehk3htkl2@4ax.com>, Jake Hamby <jhamby IS AT pobox DOT com> writes:  F :I'm a programmer who used VMS back in college and thought it'd be funE :to set up this *old* Alpha that I bought five years ago on eBay with 6 :the latest version from the OpenVMS Hobbyist program.  D   You're off in a comparatively rare OEM board-level platform, whichB   will potentially provide you with additional, um, "fun" in your F   on-going quest for, um, "fun".  Your idea of "fun" is known locally I   as "confiuration, integration and test", and it can be, um, "fun".  :-)   E   It is true that this can be "fun", but it can also be expensive and F   painful and can lead to writing drivers and such -- depending on theE   particular local requirements and around the tolerance for software F   engineering in support of the device integration.  (Sometimes it allD   just works, and sometimes it doesn't -- and device integration and<   testing can range from the trivial to the traumatic to the   intractable.)   G   Another option for "fun" here is running OpenVMS using emulation, and 4   there are VAX emulators listed in the OpenVMS FAQ.  D :The machine is an EB64+ motherboard in a generic tower case, 266MHzE :21064A CPU, 64MB RAM, 2MB cache, with onboard NCR 53C810 SCSI and an E :ISA video card (WDC chipset).  At one point I had a Trio64 PCI video A :card installed but I removed it and can't find it at the moment. C :While I was waiting for the hobbyist CD to arrive, I tried and and F :failed to install Linux (neither 2.4 nor 2.6 kernel supports the SCSIB :controller properly so it hangs in a loop resetting sym0), NetBSDC :(kernel panics immediately), and finally FreeBSD 4.11 installs and 0 :runs (FreeBSD 5.3 installs but isn't reliable).5 :Clearly this old box is not well supported any more!   H   That's one possibility, though we do test all non-retired systems withI   each new OpenVMS release.  I'd also look for a misconfiguration of some G   sort -- these Evaluation Boards were intended for OEMs to integrate,  H   configure and test, and thus the hardware one can find attached can beH   quite wide-open.  One of the biggest requirements -- and unfortunatelyG   one of the most easily overlooked -- is to match up the hardware with G   the supported hardware list.  This is a general requirement for Alpha H   systems and for these, um, "creatively-custom-configured" systems, andD   is a general requirement with these OEM boards as these OEM boardsF   can have most anything connected -- different operating systems have#   different I/O support, obviously.   G :Anyway, I can't get past the "Configuring devices..." prompt no matter # :what I try.  The typical error is:  :  :    Configuring devices... % :%EWA0, Autosense mode set by console / :%EWA0, Half Duplex 10BaseT connection selected  : C :  Improperly handled condition, bad stack or no handler specified. 2 :    Signal arguments:   Number = 00000000000000052 :                        Name   = 000000000000000C2 :                                 00000000000100002 :                                 00000000000030082 :                                 00000000000030082 :                                 0000000000000012  I   I'd look for a non-supported network controller, or other non-supported I   hardware -- I'm assuming the 10BaseT here is the on-board, but I do not F   know that.   And that ISA graphics card is a potential problem, too.  I   The FAQ has details on some bit-flags that can be set during bootstrap, F   and that will enable additional progress-related bootstrap messages.=   These might help identify the particular hardware involved.   E :Now the EB64+ is unfortunately not ROM-upgradeable so I'm stuck with  :an old EPROM.   :>>>show version) :version			X4.1-1299 Jun  1 1995 11:59:08  :>>>show pal2 :pal			VMS PALcode X5.48-102, OSF PALcode X1.35-69 : D :Am I totally out of luck or is there some secret fix I can perform?  C   Confirm the hardware configuration, and check for newer firmware. A   (AFAIK, all supported Alpha systems have (re)loadable firmware. B   Given the age of the system, I'd expect to see the firmware onlyC   on older distributions -- I'd not expect to find recent updates.)   > :Or could it be the ISA video card that's causing the problem?  A   Yes, or any other unsupported hardware.  AFAIK, there were few  A   (one?) supported ISA video card, and AFAIK it was not supported =   on this platform.  You will have fun with this box as it is <   old enough that it lacks support for the more current and A   more widely-available graphics controllers -- a PowerStorm 3D30 C   or 4D20 will *probably* work here, but some of the newer graphics D   controllers require EV6-class processors and non-swizzled bus I/O.  E :I'm going to try to bid on a cheap DEC Personal Workstation 600AU on C :eBay this week, of which there are several for sale at the moment.   A   I would personally aim for an AlphaStation series, including an @   XP900, XP1000 or equivalent box.  I would not acquire an AlphaA   system with less than an EV56 processor, and I would prefer and 4   would look for an EV6-class processor, or better.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  * Date: Tue, 5 Apr 2005 10:01:05 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)3 Subject: Re: problem with router---NAT and caching? $ Message-ID: <d2tnl1$iab$1@online.de>  D In article <d2sc22$3ki$2@online.de>, helbig@astro.multiCLOTHESvax.de3 (Phillip Helbig---remove CLOTHES to reply) writes:     > The giveaway is H > that only port 6000 is affected.  Probably tomorrow morning I'll test K > JF's suggestion that it is some security feature in DECwindows, i.e. the  K > problem should go away if I restart DECwindows.  Maybe the IP address is  3 > cached somewhere in DECwindows when it starts up.   / OK, I just restarted DECwindows.  Same problem.   C Can anyone else (with a Zyxel or some other router) reproduce this:   G    o  change the IP address on a VMS system (TCPIP SET INTERFACE/HOST=)   H    o  tell the router to forward incoming connections to the new address  @    o  log in somewhere remote and launch an applications such asB       SYS$SYSTEM:DECW$CLOCK which displays locally (of course, theF       DISPLAY has to be appropriately defined and the local DECwindowsG       has to accept the connection---try this out first before changing        the address)  E    o  verify that the "can't open display" message is produced on the F       remote system, but that all other incoming connections (TELNET,        FTP etc) work   0    o  extra credit: explain what is going on :-)  H I just noticed something.  Changing the IP address as above (ifconfig -a< shows that it is picked up) does NOT change the logical nameF TCPIP$INET_HOSTADDR.  I have to go to work now, but will try changing D this as well tonight or tomorrow morning and see if that solves the 8 problem.  It might be that DECwindows uses this logical.  C (By the way, I noticed that changing the IP address does not sever  D existing connections, but I guess that is because the connection is 0 really to a MAC address, which I didn't change.)   ------------------------------  % Date: Tue, 05 Apr 2005 17:40:57 +0100 % From: David Gray <police@spamcop.net>  Subject: Remote printing woes.8 Message-ID: <ete551p2mqgshg70vlb4ihs39rl2n5gjgv@4ax.com>   Hi all,    	* OpenVMS 7.3-2  < 	* HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 1 	* Ricoh 1060 printer (PCL6)    D Getting the following error message when trying to print to a remoteE printer via LPD.  The host system is in the UK and the remote printer  is in New Jersey.     A %TCPIP-E-LPD_REQREJECT, print request rejected by !AS (queue !AS) C %SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed   C Both firewalls have telnet and also ports 9100,23 & 515 enabled.  I D cannot verify whether the printer can be seen on the LAN here in theF UK as the firewall administrators in the US cant or wont enabled ping.. That said I can tracert without any problems.   B The printer queue is defined as follows and I also tried using the6 TCPIP symbiont, getting no errors but also no prints.    $ show queue  mercury1/full A Server queue MERCURY1, idle, on TOM::"mercury1:515", mounted form  WORD11$FORM ?   /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=WORD11$FORM) /LIBRARY=HP 2 Lowercase /OWNER=[SYSTEM] /PROCESSOR=TCPIP$LPD_SMB-   /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR  /SEPARATE=(RESET=(HP_RESET))  ) Also tried using port 9100 - same error.     Any thoughts?    Regards  	Dave.    
 Queue log:     6 XPS_TOM> type  $1$DGA8:[SYS0.TCPIP$LPD...]mercury1.log   & $1$DGA8:[SYS0.TCPIP$LPD]MERCURY1.LOG;4      D %%%%%%%%%%%%                    5-APR-2005 17:37:34.49  %%%%%%%%%%%%   # %TCPIP-I-LPD_LOGSUC, using log file # TCPIP$LPD_ROOT:[000000]MERCURY1.LOG       D %%%%%%%%%%%%                    5-APR-2005 17:37:34.50  %%%%%%%%%%%%   < %TCPIP-I-LPD_SYMBRUN, symbiont is running the queue MERCURY1       TCPIP LPD configuration data: 7 LPD Spooler Directory         : TCPIP$LPD_ROOT:[000000] - Retry-Interval                : 0 00:05:00.00 - Retry-Maximum                 : 0 01:00:00.00 - Idle-Timeout                  : 0 00:05:00.00 ! Inbound-Queues-Per-Node       : 1 ! Utility-Queues-Per-Node       : 0 ! Receiver-Debug                : 0 ! Symbiont-Debug                : 0 ! Utilities-Debug               : 0 ! Loop-Max                      : 0 ! Droptime                      : 0 ! Probetime                     : 0 # PS-Extensions                 : LPS % Stream-Passall                : FALSE % VMS-Flagpages                 : FALSE % Persistent-Server             : FALSE % Keepalive                     : FALSE $ Synchronize-All-Jobs          : TRUE% Setup-NoLF                    : FALSE % 1st-VFC-Prefix-Special        : FALSE     PCB for printer  LP: MERCURY1 RM: MERCURY1 RP: TEXT SD: /TCPIP$LPD_ROOT/MERCURY1' LF: /TCPIP$LPD_ROOT/000000/MERCURY1.LOG  BP: MERCURY1	 PA: FALSE 	 ND: FALSE 	 CR: FALSE 	 SN: FALSE    ' lpd$ast_handler save_entry_number = 997    D %%%%%%%%%%%%                    5-APR-2005 17:37:49.99  %%%%%%%%%%%%   A %TCPIP-E-LPD_REQREJECT, print request rejected by MERCURY1 (queue  TEXT)                 ------------------------------  % Date: Tue, 05 Apr 2005 07:38:22 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>" Subject: Re: VMS Command language.. Message-ID: <4252406E.12270.42684CB@localhost>  ) On 4 Apr 2005 at 17:27, Tom Linden wrote: ( > Was there ever any alternative to DCL?  D The GNV tools include the bash shell.  It's not set up to be a CLI, A but it's easy to write a short LOGIN.COM that drops them into it   without any way out...  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com   ------------------------------   Date: 5 Apr 2005 15:47:25 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)" Subject: Re: VMS Command language., Message-ID: <3bfq8dF6ioie6U1@individual.net>  6 In article <slrnd53vs0.e75.usenet@gaia.roc2.gblx.net>,( 	Dan Foster <usenet@evilphb.org> writes:H > DEC also had a POSIX CLI available as well, IIRC. I don't think it was > used much, if at all.  >   D It's been a long time since I tried, so my memory may be a bit foggyB but, I seem to remember there was an option at one time (and maybe7 still!) that let you set an optional CLI at login time.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  # Date: Tue, 05 Apr 2005 15:56:40 GMT # From: hoff@hp.nospam (Hoff Hoffman) " Subject: Re: VMS Command language.0 Message-ID: <Yyy4e.2980$vH.871@news.cpqcorp.net>  N In article <opsoqgwjxpzgicya@hyrrokkin>, "Tom Linden" <tom@kednos.com> writes:0 :On mainframes there are different possibilites,D :JCL, Rexx, CMS and in Unix a number of shells, csh, ksh, bash, rexx0 :regina.  Was there ever any alternative to DCL?     Yes.  E   MCR has been previously mentioned, and there was DEC/shell.  There  A   were a few other CLIs around, though not in as wide-spread use.   D   There are and were application-level interpreters around, as well.@   bash is certainly around, and IIRC the Eunice environment had >   something similar here.  tcl/tsh and others are around, too.B   Regina (a portable interpreter similar to rexx) is available for'   various platforms, including OpenVMS.   D   Off-hand, I do not recall if the POSIX shell was implemented as a 0   CLI or if as an application-level interpreter.   	--   A   And regarding the inevitable question: CLIs can and usually do  B   connect into and support applications calling the (undocumented)C   system service, and typically operate in supervisor mode.  There  C   is no formal documentation of this API, so CLIs are comparatively    rare.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Tue, 05 Apr 2005 12:27:45 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>" Subject: Re: VMS Command language.- Message-ID: <42528441.4280.52F70BC@localhost>   . On 5 Apr 2005 at 15:47, Bill Gunshannon wrote:F > It's been a long time since I tried, so my memory may be a bit foggyD > but, I seem to remember there was an option at one time (and maybe9 > still!) that let you set an optional CLI at login time.   F It's still there.  However, since there is no public documentation on B how to write a CLI, it's a trifle difficult to actually implement  one.  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com   ------------------------------   End of INFO-VAX 2005.190 ************************