You could install and use Mozilla (CSWB is the name of the download from the HP web site) on the OpenVMS box? Log your information and access ITRC from there. This assumes the OpenVMS box can access the Internet.
Alternatively, zip the pieces, and place them at an FTP download site somewhere. It is possible to transfer files through Windows, though it requires some care around the file formats.
Do consider a call for formal assistance for operating OpenVMS here, too. If file transfers between OpenVMS and Windows are unfamiliar and are stymieing progress, it would be more expedient to either get formal help, or to acquire training in this area.
This all without intending offense. We each have our own unique areas of expertise, and vast areas beyond our expertise. OpenVMS and Windows networking is a comparatively arcane area.
Since you're probably not going to call in help, the basics are as follows.
I'll assume IP is configured on OpenVMS, and that the OpenVMS box has Internet access.
Get to your login directory. Show your login device and directory -- you'll need this later -- as subsequent commands assume this:
SET DEFAULT SYS$LOGIN:
SHOW LOGICAL SYS$LOGIN
Get zip from the Freeware distro. Copies of the Freeware are shipped with OpenVMS, and Freeware V8 has the most current bits. If you don't have an OpenVMS distro, look here:
http://mvb.saic.com/freeware/freewarev80/The core tools are in 000TOOLS directory. Fetch the contents of the 000TOOLS area and the Alpha subdirectory, for this case.
You can use FTP on OpenVMS to download these from
ftp://mvb.saic.com/freewarev80.The rough sequence (on OpenVMS) is as follows:
ftp mvb.saic.com
anonymous
email
bin
cd [.freewarev80]
get filename
get otherfilename
...
^Z
I'd usually suggest using the DCL command COPY /FTP here, but the OpenVMS version here may or may not have that capability. (In computing years, OpenVMS Alpha V6.2-1H3 is ancient.) Your OpenVMS does, but your IP stack may or may not; OpenVMS V6.2 and its associated IP stacks do have COPY/FTP. Older OpenVMS and older IP stacks do not.
Create a subdirectory under your login area. CREATE/DIRECTORY [.ITRC]
COPY the files of interest into this subdirectory. COPY SYS$STARTUP:SYSTARTUP_VMS.COM [.ITRC]
Whatever other files.
Set up the zip symbol:
zip :== $ddcu:[login.ITRC]zip.exe
The "ddcu:[login" comes from your login device and login directory.
Invoke Zip:
zip "-V" sys$login:itrc.zip [.ITRC]*.*
Switch boxes. From the Microsoft Windows Command prompt, transfer the zip archive to the Windows box.
ftp openvms.ip.host.spec
username
password
bin
get itrc.zip
You now have the ITRC zip in your local directory.
You can now clean up, if desired. Delete the [.ITRC] files and the SYS$LOGIN:ITRC.DIR subdirectory on OpenVMS.
Have at on Windows. Post to ITRC, or (better) transfer the zip somewhere where it can be downloaded from remote sites. To a company FTP server or site. If you do choose to unpack the zip on Windows and try to read OpenVMS files, do not use Notepad tool to read them. Use Wordpad. Do recognize that .COM is an executable on Windows, and you can need to rename the .COM files to .TXT files. Then use Wordpad.
(As a general note, I'd suggest not posting the Microsoft Office and Microsoft proprietary formats as ITRC OpenVMS forum attachments. Some of us non-Windows users can read most of them, and some can't. I'd stick to what Windows calls "MS-DOS text files" or some such, or to the OpenVMS native formats.)
And again, do consider getting yourself either some formal help here, or some training in OpenVMS, or somebody you can escalate these questions to. (No offense is intended. We all have our areas of experience and knowledge. But a broken MOUNT command is trivial to resolve. Maybe two to five minutes of my or any other experienced OpenVMS folks' time, in most of the cases I've seen over the years), and this thread has been going for most of a week.
It's taken me (far) longer to describe how to perform this sequence than it would have taken for me to log into the host and examine and to fix the MOUNT problem. There are a collection of other issues here, such as the antiquity of this AlphaServer 2000 and its components; this is old gear. Old systems and old disks do fail. There are other reasons to formally review this system and this environment, too.
Stephen Hoffman
HoffmanLabs LLC
