| Part 1 | Part 2 | Part 3 | TOC |
Archive-name: dec-faq/vms/part3
Posting-Frequency: bi-monthly
Last-modified: December 22, 1997
Overview
========
This is part 3/3 of the Frequently Asked Questions (FAQ) posting for the
comp.os.vms and vmsnet.misc newsgroups. (comp.os.vms is
bidirectionally-gatewayed to the INFO-VAX mailing list - see INTRO3 in part 1
for further details.) It contains answers to frequently asked questions about
Digital's OpenVMS operating system and the computer systems on which it runs.
This FAQ is archived in the following locations:
comp.answers and news.answers newsgroups
ftp://ftp.digital.com/pub/Digital/dec-faq/vms
ftp://rtfm.mit.edu/pub/usenet/news.answers/dec-faq/vms
CompuServe VAXFORUM, Library 0, VMSFAQ.TXT
To make suggestions for changes or additions to this Frequently Asked
Questions list, send mail to the editor at Steve.Lionel@digital.com.
Answers are especially appreciated.
------------------------------------------------------------
DECW1. How do I let someone else display something on my workstation?
Table of Contents
On a workstation, you go into "Customize" menu of the session manager utility
and select "Security". When the pop-up box appears, you can put
node/user/tranport to allow who can launch an application to the display on
that workstation.
[raspuzzi@mrlat.enet.dec.com]
> Yah, but this doesn't seem to work with non-VMS systems. What do I put in
> for the transport? I tried "TCPIP" just for kicks, but it didn't work.
You need a checklist of sorts:
1) Make sure that you've specified the X-windows "display"
correctly on the remote side. For DECNET it's something
like NODE::0.0, for TCP/IP it's Node.Domain:0.0, etc. On a
unix system, define the DISPLAY environment variable so:
# setenv DISPLAY myvax.domain:0.0
2) If you've verified 1) and things still aren't working, make
sure the Security settings on the VMS side will allow the
connection: Pull down the "Options" menu in the Session
Manager, select "Security..." near the bottom. If you
don't find your host (and username) listed on the left
under "Authorized Users", go to the right side of the menu
and fill in the three fields, "Node", "Username",
"Transport". Then click on the Add botton, then the Apply
and OK buttons to add the new host to the security
database.
a) There are various transports: LOCAL, DECNET, LAT,
TCPIP, etc. Select the one appropriate to the
client machine's connection to the VMS machine.
b) If the connection is DECNET, do *NOT* add :: to the
node name!
c) If the connection is TCPIP, "Username" _must_ be an
asterisk (*) because the TCP/IP protocol used does
not provide the remote username.
d) If the connection is TCPIP, it's best to use a full
domain name, e.g., Node.Subd.Domain. However, you
_may_ have to use the IP address itself, rather
than the domain name (EWS requires this). I
generally add two entries for each TPCIP host, the
first using the domain name, the second the IP
address.
e) There are a various 3rd party vendors who supply
TCP/IP packages for VMS, including but not limited
to TGV (Multinet) and Wollongong (Pathway ?).
Multinet (and DEC's own UCX) call the transport
"TCPIP", Wollongong, at least in some incarnations,
uses "WINTCP". You need to use the appropriate
vendor's package transport name in the "Transport"
field.
3) If things _still_ aren't working, make sure the transport
you want has been activated for DECwindows. This is a
system manager job, but you can do the ground work yourself
before bothering the sysmgr. Do the following:
$ DIR SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
If that file exists, then do:
$ SEARCH SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM -
$_ DECW$SERVER_TRANSPORTS
You sould find something like:
$ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"
If the transport you want, e.g., TCPIP, isn't listed, have
your system manager make the appropriate changes and
restart DECwindows. If the file doesn't exist, the sysmgr
will have to create it by copying the corresponding
.TEMPLATE file to .COM and uncommenting the line that
defines decw$server_transports.
a) If you're wanting to use TCP/IP to connect, make
sure TCP/IP is available on the VMS host. TCP/IP
is _not_ native to VMS. You need to be running
either Digital's UCX or a 3rd party vendor's TCP/IP
product. If you're not, none of the above will
help.
[Fairfield@Slac.Stanford.Edu]
There is a log file created in SYS$MANAGER which tells you which transports
are loaded, and also tell you what connect attempts were rejected, including
showing what the presented credentials were. This file is
SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number if
you have multiple servers on the workstation. I have found this file to be
very useful for tracking down what needs to be put in the Session Manager
Security entries.
[rabinowitz@bear.com]
------------------------------------------------------------
DECW2. How do I create a display on another workstation?
Table of Contents
$ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node
for LAT the command might look like this:
$ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=REMOTE_NODE
for DECnet:
$ SET DISPLAY /CREATE /TRANSPORT=DECNET /NODE=NODE
for TCP/IP
$ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=128.12.4.122
Note that LAT is typically used for X terminals but can be used from
OpenVMS to OpenVMS systems on OpenVMS Alpha V6.1 (if you have setup the X
server to allow the LAT transport - check the docs). LAT will be supported
on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX
release.
[raspuzzi@mrlat.enet.dec.com]
There is a log file created in SYS$MANAGER which tells you which transports
are loaded, and also tell you what connect attempts were rejected, including
showing what the presented credentials were. This file is
SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number if
you have multiple servers on the workstation. I have found this file to be
very useful for tracking down what needs to be put in the Session Manager
Security entries.
[rabinowitz@bear.com]
------------------------------------------------------------
DECW3. How can I get the information from SHOW DISPLAY into a symbol?
Table of Contents
Use the undocumented SHOW DISPLAY/SYMBOL, and then reference the symbols
DECW$DISPLAY_NODE, DECW$DISPLAY_SCREEN, DECW$DISPLAY_SERVER and/or
DECW$DISPLAY_TRANSPORT.
[Fairfield@Slac.Stanford.Edu]
------------------------------------------------------------
DECW4. How do I get a log of a DECterm session?
Table of Contents
If you are working from a Decterm, you can use the AutoPrint feature. Choose
the "Printer..." menu item from the "Options" menu, set the printing
destination to the name of the file you want, and set "Auto Print Mode".
You are now free to continue.
It should be noted that ALL the characters and escape sequences are captured,
but if you display the log file on a DECterm you will get EXACTLY what you had.
[fenster@star.enet.dec.com]
------------------------------------------------------------
DECW5. Problem - the DELETE key deletes forward instead of backward!
Table of Contents
This has to do with Motif's virtual bindings. When a Motif application starts
up, it looks at the vendor string returned in the display connection
information and attempts to match the string to a table of virtual bindings.
You can override the default bindings in your decw$xdefaults.dat file. Here is
the entry you would make to get the default VMS bindings.
*defaultVirtualBindings:\
osfCancel : <Key>F11 \n\
osfLeft : <Key>Left \n\
osfUp : <Key>Up \n\
osfRight : <Key>Right \n\
osfDown : <Key>Down \n\
osfEndLine :Alt <Key>Right \n\
osfBeginLine :Alt <Key>Left \n\
osfPageUp : <Key>Prior \n\
osfPageDown : <Key>Next \n\
osfDelete :Shift <Key>Delete \n\
osfUndo :Alt <Key>Delete \n\
osfBackSpace : <Key>Delete \n\
osfAddMode :Shift <Key>F8 \n\
osfHelp : <Key>Help \n\
osfMenu : <Key>F4 \n\
osfMenuBar : <Key>F10 \n\
osfSelect : <Key>Select \n\
osfActivate : <Key>KP_Enter \n\
osfCopy :Shift <Key>DRemove \n\
osfCut : <Key>DRemove \n\
osfPaste : <Key>Insert
To merge:
$ xrdb :== $decw$utils:xrdb.exe
$ xrdb -nocpp -merge decw$xdefaults.dat
[kleinsorge@star.enet.dec.com]
------------------------------------------------------------
DECW6. Problem - On a DEC2000-300, Motif doesn't start
Table of Contents
Check for a GQ device by doing a SHOW DEVICE G at the DCL prompt. If there is
no GQA0 device:
a) VMS failed to find the appropriate IRQ information for the Compaq QVision
and did not autoconfigure it. Run the correct ECU (for OSF and VMS) and
reboot.
b) You do not have a Compaq QVision video card. This card should have Compaq
printed on it, and identifies itself as a CPQ3011 or a CPQ3111. If it is
not one of these 2 devices (as of 7/1/94 and version 6.1) then VMS does not
support it.
If there is a GQA0 device:
a) There may have been a severe error in the DECwindows startup. Type the
contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information on
errors starting the server.
b) The sysgen parameter WINDOW_SYSTEM is not set to 1. This is a common way
used by system managers to disable server startup.
c) You may not have a valid Motif license. To check for the Motif license,
type LICENSE LIST DW-MOTIF/FULL and examine the information displayed.
Make sure that it is present, valid and active.
[kleinsorge@star.enet.dec.com]
------------------------------------------------------------
DECW7. Problem - My LK401 keyboard unexpectedly autorepeats
Table of Contents
There are several modes of failure:
a) Pressing 2 and 3 keys at the same time causes one key to autorepeat when
released. Check the hardware revision level printed on the bottom of the
keyboard. If the revision level is C01, the keyboard firmware is broken.
Call field service to replace the keyboard with any revision level other
than C01.
b) Pressing certain keys is always broken. Typical sympypoms are: delete
always causes a autorepeat, return needs to be pressed twice, etc. This is
frequently caused by having keys depressed while the keyboard is being
initialized. Pressing ^F2 several times or unplugging and replugging the
keyboard frequently fix this problem. There is a patch available to fix
this problem [contact the CSC for information - a CSCPAT number will be
included here when available. - Ed.]
c) A key that was working spontaneously stops working correctly. This may be
either (a) or (b) or it may be bad firmware. Ensure that you have the most
recent firmware installed on your CPU. An old version of the DEC 3000
firmware had a bug that could cause this symptom.
[kleinsorge@star.enet.dec.com]
------------------------------------------------------------
DECW8. Problem - My LK411 sends the wrong keycodes or some keys are dead
Table of Contents
Check the firmware revision on the keyboard. Hardware revision B01 introduced
an incompatability with the device driver which causes the keyboard to not be
recognized correctly. There is a patch available to fix this problem:
[AXPDRIV06_061] - the fix is also included in OpenVMS V6.2. The rev A01
keyboard, and the LK450 should work without problems.
[kleinsorge@star.enet.dec.com]
[inazu_k@ewbv21.enet.dec.com]
------------------------------------------------------------
DECW9. How do I set the title on a DECterm window?
Table of Contents
If you are creating a new DECterm window, check
HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES.
If you want to change the title of an existing window, use the following
control sequences, where <esc> is the ANSI escape code, value decimal 27, and
<text> is what you want to display:
To set the DECterm title, send <esc>]21;<text><esc>\
To set the icon label, send <esc>]2L;<text><esc>\
For example, DCL to display "My DECterm" in title bar:
$ ESC[0,8]=27
$ WRITE SYS$OUTPUT "``ESC`]21;My DECterm``ESC`\"
[p_lee@decus.ch]
You can also change the title and the icon using the Options-Window...
menu.
------------------------------------------------------------
DECW10. How do I customize DECwindows, including the login screen?
Table of Contents
To customize various DECwindows Motif characteristics including the defaults
used by the SET DISPLAY command, the DECwindows login screen background logo
used (the default is the Digital logo), various keymaps, the FileView
defaults, session manager defaults, the DECwindows login processing,
DECwindows log file processing, and various other DECwindows attributes, see
the example file:
SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE
This example template file is typically copied over to the filename
SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meet
site-specific requirements.
Additionally, various X tools such as xsetroot, bitmap and xrdb -- some these
can be useful in customizing the appearance of an application or of the
DECwindows Motif display -- are provided in the DECW$UTILS: area.
[Steve Hoffman]
------------------------------------------------------------
MISC1. What is the pinout for the DECconnect DEC-423 MMJ connector?
Table of Contents
DECconnect DEC-423 MMJ pinout:
1 Data Terminal Ready (DTR)
2 Transmit
3 Transmit Ground
4 Receive Ground
5 Receive
6 Data Set Ready (DSR)
DECconnect MMJ adapters:
Part: Converts BC16E MMJ male to fit into:
H8575-A EIA232 25 pin female (common)
H8575-B EIA232 9 pin male (MicroVAX II console)
H8571-D EIA232 25 pin male (modem-wired)
H8571-J PC/AT 9 pin male (PC serial port)
H8572-0 0BC16E MMJ male (MMJ extender)
BC16E-** MMJ cable, available in various lengths
Numerous additional adapters and cables are available from the _OPEN
DECconnect Building Wiring Components and Applications Catalog_, as well as
descriptions of the above-listed parts.
[Steve Hoffman]
------------------------------------------------------------
MISC2. What are the escape sequences for the VTxxx function keys?
Table of Contents
In the following, <CSI> is decimal code 155 and can be replaced by the
sequence "<ESC>[" (without the quotes), SS3 is decimal code 143 and can be
replaced by "<ESC>O". VT1xx terminals don't accept <CSI> and <SS3>.
PF1=<SS3>P PF2=<SS3>Q PF3=<SS3>R PF4=<SS3>S
KP0=<SS3>p KP1=<SS3>q KP2=<SS3>r KP3=<SS3>s KP4=<SS3>t KP5=<SS3>u
KP6=<SS3>v KP7=<SS3>w KP8=<SS3>x KP9=<SS3>y KPCOMMA=<SS3>l KPMINUS=<SS3>m
KPPERIOD=<SS3>n ENTER=<SS3>M DNARROW=<CSI>B UPARROW=<CSI>A LFARROW=<CSI>D
RTARROW=<CSI>C FIND=<CSI>1~ INSERT=<CSI>2~ REMOVE=<CSI>3~ SELECT=<CSI>4~
PREV=<CSI>5~ NEXT=<CSI>6~ F6=<CSI>17~ F7=<CSI>18~ F8=<CSI>19~ F9=<CSI>20~
F10=<CSI>21~ F11=<CSI>23~ F12=<CSI>24~ F13=<CSI>25~ F14=<CSI>26~
HELP=<CSI>28~ DO=<CSI>29~ F17=<CSI>31~ F18=<CSI>32~ F19=<CSI>33~ F20=<CSI>34~
These and other control sequences can be found in SYS$SYSTEM:SMGTERMS.TXT
------------------------------------------------------------
MISC3. Can I reuse old keyboards, mice and monitors with a PC?
Table of Contents
Older DIGITAL keyboards (with RJ modular jacks), older DIGITAL mice (with RJ
modular jacks, or with a DIN connector with pins in a configuration other than
the PC-standard DIN connector pin orientation), and older video monitors (with
RGB synch-on-green video signaling) all use signaling formats and/or
communications protocols that differ from the PC standards, and are neither
interchangable nor compatible with typical PC peripheral device controllers.
LK201, LK401, VSXXX, VR260, VR290, etc., are incompatible with most PC
systems.
Newer DIGITAL keyboards (with DIN plugs), newer DIGITAL mice (with PC-pin DIN
plugs), and newer video monitors (multi-synch) are often interchangeable with
`industry standard' PC systems, and can often be used with most PC peripheral
device controllers. LK461, LK471, PC7XS-CA, VRC16, VRC21, etc., are compatible
with most PC systems.
Rule of thumb: if the peripheral device component was sold for use with the
DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, or
more recent system, it will probably work with a PC peripheral controller.
If the peripheral device component was sold for use with an VT420 or older
terminal, most VAX, most VAXstation, and most Alpha systems with names in the
format `DEC <four-digit-number>', it probably won't work on a PC.
Note that the above is a general guideline, and should not be read to indicate
that any particular peripheral device will or will not work in any particular
configuration, save for those specific configurations the device is explicitly
supported in.
[Steve Hoffman]
------------------------------------------------------------
MISC4. What is the pinout for the MicroVAX DB9 connector?
Table of Contents
The MicroVAX DB9 console connector pinout predates the PC-style DB9
pinout, and uses a then-common (older) standard pinout, and uses the
following EIA-232-standard signals:
1: Protective Ground
2: Transmited Data
3: Received Data
4: Request To Send
5: Data Terminal Ready
6: Data Set Ready
7: Signal Ground
8: Shorted to pin 9 on 2000 series, otherwise floating
9: Shorted to pin 8 on 2000 series, otherwise floating
The H8571-B converts the (non-2000-series) MicroVAX DB9 to MMJ
DECconnect. The MicroVAX 2000 and VAXstation 2000 requires a
BCC08 cable (which has the 8-9 short) and the H8571-D for use
with DECconnect.
More recent DIGITAL systems use either the DECconnect MMJ or
the PC DB9 pinout.
The PC DB9 connector is the H8571-J.
[Steve Hoffman]
------------------------------------------------------------
SOFT1. Where can I find lots of free software for OpenVMS?
Table of Contents
An OpenVMS Freeware CD was distributed at US DECUS in
May and December 1995 - this CD will also be included with future versions of
the OpenVMS binaries CD-ROM distribution and the Software Product
Library CD-ROMs)for VAX and Alpha systems. The OpenVMS Freeware CD is
available online at:
http://www.openvms.digital.com/openvms/freeware/cd.html
ftp://ftp.montagar.com/
http://www.montagar.com/dfwlug/
ftp://flash.acornsw.com/
gopher://gopher.acornsw.com/
http://www.acornsw.com/
ftp://ftp.tay.ac.uk/
It may also be ordered from DECUS (http://www.decus.org) as VS0185.
This CD contains a large assortment of freeware and is a good starting
point if looking for utilities. Many of the packages listed below are also
on the Freeware CD. Some of the most often requested tools on the
Freeware CD are: ZIP/UNZIP, MMK (make), PINE, PERL, TAR, UUENCODE/UUDECODE
and XV.
The montagar.com server, belonging to the DECUS Dallas/Fort Worth LUG, also
provides "Almost 350,000 blocks of white papers, OpenVMS rebuttals, good
articles, engineering information, and other assorted OpenVMS Positive
'Stuff'." You can also telnet to dfwlug.decus.org and log in as Info
to access an "OpenVMS BBS" system there.
Digital has a WWW page with pointers to freeware (mostly derived from
this FAQ) but which also contains useful information on archive tools needed
for extracting freeware kits. The URL is:
http://www.digital.com/info/vms-freeware.html
Hunter Goatley runs a VMS freeware fileserver at Western Kentucky
University. If you're using a WWW browser, the URL is:
http://www.wku.edu/www/fileserv/fileserv.html
The FILESERV packages are also available via anonymous FTP from:
ftp.wku.edu, under [.VMS.FILESERV].
ftp.spc.edu, under [.MACRO32.SAVESETS] and [.MX].
ftp.vms.stacken.kth.se, under [.MIRRORS..WKU.VMS.FILESERV].
ftp.shsu.edu, under pub/vms/mx and pub/vms/utilities.
nic.switch.ch, under /mirror/vms/spc.
ftp.technion.ac.il, under /pub/unsupported/vms/spc.
ftp.riken.go.jp
or via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the commands HELP and
DIR ALL in the body of a mail message for more information.
If you get the packages via WWW or FTP, they're in ZIP format which requires
the UNZIP (note: this is not Gnu gunzip!) tool to unpack. You can get this
from:
ftp://ftp.wku.edu/vms/unzip.exe ! VAX
ftp://ftp.wku.edu/vms/unzip.alpha_exe ! Alpha
or you can request the FILESERV_TOOLS package from the e-mail server.
Another source of free software is the vmsnet.sources newsgroup (and the
corresponding vmsnet.sources.d discussion group). See the monthly posting
"vmsnet.sources archives" for a list of sites which archive submissions
to vmsnet.sources.
CompuServe users should check out the libraries of the VAXFORUM forum.
Arne Vajhøj runs an OpenVMS WWW page, with software and other pointers, at:
http://www.hhs.dk/vms/
Kermit is available at:
http://www.columbia.edu/kermit/ or
ftp://kermit.columbia.edu/
ZMODEM is available at:
ftp://ftp.cs.pdx.edu/pub/zmodem
See the FILES file in that directory for further details.
Note that this freeware version of ZMODEM will interoperate only with
ZMODEM software that is licensed from Omen Technology.
(Also on Freeware CD)
[Steve Lionel]
A good source of software for DEC boxes (and anything else pretty much)
is the DECUS library. online catalogs are available as well as some
software via ftp.decus.org; there's a gopher server
gopher://gopher.decus.org/
an FTP server:
ftp://ftp.decus.org/
and a WWW server:
http://www.decus.org/
Some DECUS library CD-ROMs are available online at:
http://www.acornsw.com/www/acorn/cdrom-via-www.html or
gopher://gopher.acornsw.com/
[munroe@dmc.com]
Phone for orders is 508 841 3502. Lots of good stuff from lots of good
folks, and copies on media (tapes, CDs) are cheap.
[Everhart@Arisia.gce.com]
MPJZ's Hyper-Software-List for OpenVMS is Martin P.J. Zinser's list of
additional software.
http://axp616.gsi.de:8080/www/vms/sw.html
Chris Higgins's VMS Software List II
http://csvax1.ucc.ie/www/vms_sw_list/sw_list.html
DECUS SIG Tape collections are available on Mark Berryman's system,
ftp://mvb.saic.com
David Jones's DECthreads-based HTTP_SERVER World-Wide Web server for VMS.
http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html
[goathunter@WKUVX1.WKU.EDU]
DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX. V1.2-4
will include Spyglass Enhanced Mosaic which supports many
"Netscape" enhancements.
A port of Mosaic 2.7-4 which supports UCX,
Multinet and SOCKETSHR/NETLIB is available from:
ftp://wvnvms.wvnet.edu/mosaic/
Lynx (a character-cell World-Wide-Web reader) is available from
ftp://ftp2.cc.ukans.edu/pub/lynx
[Steve Lionel]
Netscape Navigator will be available as part of the OpenVMS Internet Product
Suite. For further details, see:
http://www.openvms.digital.com/openvms/products/ips/index.html
PGP (Phil Zimmerman's "Pretty Good Privacy") is available from the standard
distribution sites as listed in the PGP FAQ. Information on compiling
PGP for OpenVMS can be found at http://zifi.genetics.utah.edu/
An archive of DECwindows and Xwindows software can be found at the following
sites:
ftp://axp.psl.ku.dk/decwindows
ftp://ftp2.cnam.fr/decwindows
ftp://ftp.et.tudelft.nl/decwindows
ftp://ftp.ctrl-c.liu.se/decwindows
http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html
(See also Freeware CD)
[pmoreau@cena.dgac.fr]
ImageMagick is an X11 package for display and interactive manipulation of
images. The package includes tools for image conversion, annotation,
compositing, animation, and creating montages. ImageMagick can read and write
many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, Photo CD,
etc.).
ftp://ftp.x.org/contrib/vms/ImageMagick/ImageMagick-3.3.zip
(Also on Freeware CD)
[cristy@dupont.com]
XV 3.10 is available from:
ftp://ftp.cis.upenn.edu/pub/xv
ftp://ftp.digital.com/pub/graphics/xv
(Also on Freeware CD)
GHOSTSCRIPT and GHOSTVIEW are available from:
ftp://ftp.digital.com/pub/VMS/ghostview
Version 2.3 of GhostView-VMS is now available from:
ftp://iphthf.physik.uni-mainz.de/pub/vms/
[plass@dipmza.physik.uni-mainz.de]
XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:
http://www.contrib.andrew.cmu.edu/usr/dn0o/xpdf/xpdf.html
The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at
ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readme
ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip
[pmoreau@ad.cena.dgac.fr]
Good news: ada.cenaath.cena.dgac.fr anonymous ftp server is reopen. However, we
always have a rather slow Internet link, but some mirror sites are available
(they are listed in AAA_MIRROR_SITES.TXT file):
List of FTP Mirror Sites for the DECWINDOWS archive:
===================================================
AXP.PSL.KU.DK (Multinet) Mirror of CENA DECW archive
FTP.ET.TUDELFT.NL (MadGoat) Mirror of CENA DECW archive
FTP2.CNAM.FR (MadGoat) Mirror of CENA DECW archive
ftp.x.org (in /contrib/vms) not really a mirror, but I try to put all my
new ports at this site.
List of HTTP Mirror Sites for the DECWINDOWS archive:
====================================================
http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html
Some X clients from the OpenVMS Freeware CDROM are located in
[.DECWINDOWS.CDFREEWARE] directory.
[pmoreau@cena.dgac.fr]
I have written and installed on INFO.CS.PUB.RO an 'Archie' clone for VMS
software. Telnet to that machine, and login as VMSARCI.
It contains now listings for over 30 ftp servers with >14 GB of VMS software.
The most useful commands are LIST, which generates a list of scanned ftp
servers, and FIND <string>, whichs looks for a file containing "string"
in the name; the search modes are only "substring" [default] and "exact",
and regex search is not supported (so FIND EMACS will work, but FIND *EMACS*
or FIND *EMACS*.* will not). The search is case-insensitive.
Those of you that know other ftp servers with VMS software that I haven't
found, please let me know. (The program that build the databases can
recursively scan whole servers- as FTP.WKU.EDU, or just some directories-
as NIC.SWITCH.CH /pub/vms)
Sorry, this service is VERY SLOW [by Western standards], because it runs
on a quite-busy oldie-but-goodie VAXStation 3400 with 20Mb and a RF71, and
the Internet link is only 256 Kpbs (sometimes unavailable).
[stfp@roipb.cs.ipb.ro]
Perl 5 (object oriented, blah blah) is available for VMS.
The primary development ftp site is:
ftp://genetics.upenn.edu/perl5/
But this site is mirrored by more than 47 CPAN sites around the world. Each
CPAN site is accesible via a cgi-bin script at the perl homesite:
http://www.perl.com/CPAN/
(PERL can also be found on the OpenVMS Freeware CD)
Charles Lane maintains a web page on how to write cgi-bin scripts in perl 5 for
VMS at:
http://duphy4.physics.drexel.edu/duphy4/cgi_info.html
and I maintain a web page on how to obtain and compile perl5 for VMS at:
http://w4.lns.cornell.edu/~pvhp/perl/VMS.html
[pvhp@lns62.lns.cornell.edu]
------------------------------------------------------------
SOFT2. Where can I find the UNIX <whatever> tool for OpenVMS?
Table of Contents
POSIX:
POSIX-compliant, Digital-supported versions of POSIX routines and
utilities:
lex, yacc, grep, tar, uuencode, uudecode, rcs, man, cpio, make,
awk, ar, mail, etc., the POSIX shell, the POSIX C programming
interface, etc.
POSIX utilities can be used from within the POSIX shell, and
via the DCL `POSIX/RUN POSIX$BIN:tool.' command.
POSIX is a separately-installed package, and is licensed with
OpenVMS V5.5 later. The POSIX installation kit is included
on the consolidated distribution CD-ROM kit, and installation
kits are also available separately.
C:
Common C system and library routines are present in the DEC C run-time
library, which is available for V5.5 and later, and is shipped in V6.1
and later. DEC C is the upgrade for VAX C, DEC C and VAX C can coexist
on the same system OpenVMS VAX system, and both compilers can be enabled
via the "C" license PAK.
Also see SYS$EXAMPLES:, and (if either is installed) the DECW$EXAMPLES:
and UCX$EXAMPLES: areas.
X Windows:
Various Digital-supported X Windows utilities:
xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc.
In DECW$UTILS: in DECwindows Motif V1.2-3 and later. Also see
DECW$EXAMPLES: for example X and C programs.
Miscellaneous tools and examples:
Various unsupported OpenVMS tools and code examples:
DWAUTH (X Windows SYSUAF authorize-like tool), various versions
of grep, fgrep, yacc, vmstar, uuencode, gawk, etc. html tools,
the mx SMTP mail exchange package, X windows flight simulator,
the mxrn X windows news reader, the OSU HTTPD WWW server, a WWW
gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.
IP tools:
DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp,
rcp, nfs, tnfs, etc. OpenVMS V6.2 and UCX V3.3 and later can be used
together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270
qualifiers on various DCL commands.
Also see the various C examples in UCX$EXAMPLES:
[Steve Hoffman]
vi clones
Both vile and elvis (vi clones) run on OpenVms.
The current version of vile is 7.1
It's available at
http://www.clark.net/pub/dickey/vile/vile.html
ftp://ftp.clark.net/pub/dickey/vile
ftp://id.wing.net/pub/pgf/vile
[Thomas Dickey]
GNU tools:
Information on the GNU on VMS Project, which aims to port GNU software
to VMS, is available at:
http://vms.gnu.ai.mit.edu/
ftp://vms.gnu.ai.mit.edu/gnu-vms/
Software info:
http://vms.gnu.ai.mit.edu/software/
Software archive:
ftp://vms.gnu.ai.mit.edu/gnu-vms/software/
GCC:
The Progis company in Germany has ported GCC (GNU C) to OpenVMS Alpha.
http://www.progis.de/
The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1
from Pat Rankin's site.
ftp://ftp.caltech.edu/pub/rankin/
[otis@magna.com.au]
[End of Part 3/3]
| Part 1 | Part 2 | Part 3 | TOC |
Comments to: Martin P.J. Zinser