Re: Sequel to: I'm giving up computers if this is the future.

From: Chuck Chopp (ChuckChopp_at_rtfmcsi.com)
Date: 09/14/04 

Date: Tue, 14 Sep 2004 14:09:25 -0400

VAXman- @SendSpamHere.ORG wrote:

> OK...
>
> This Reflection thing sends a command to the VMS session: RUN ALPHALK2
>
> I want to experiment and define a logical and then run the program. I
> have created a ALPHALK2.COM file with $ DEFINE... and $ RUN ALPHALK2
>
> I've looked all throughout this Reflection Weedoze bastardized PeeCee
> *** setup toilet and can only find a reference to RUN VAXLINK2. Is
> there a translation that is automatically applied to change VAXLI to
> ALPHA? It seems to ignore when I change the command to @ALPHALK2 or
> @VAXLINK2 regardless.
>
> Is it any wonder I've been shortening my work time and lengthening my
> Guinness time.
>
> Can anybody here what works with this horked up *** lend a hand?

I'm working with Reflection v10.0 here. I haven't played with these file
transfer programs in ages... not since I started demanding that FTP and
TCP/IP be installed on all of the OpenVMS systems that I work with. Still,
there's been a few cases where all I had was an asynch console connection to
a remote system and I absolutely had to use these tools to upload some files
so they were of benefit to have available.

In Reflections, do the following:

On the menu, choose Setup -> File Transfer...

On the Protocol tab, select "WRQ/Reflection" as your protocol and use the
preset configuration "To OpenVMS".

On the WRQ tab, in the "Host system options" grouping of controls, there is
an edit box labeled "Startup command:". By default, it says "RUN VAXLINK2".
  You can change this to be "RUN ALPHALK2".

If you don't have ALPHALK2.EXE in your default directory in your host
session then it won't be found, so defining a logical name ALPHALK2 in one
of your logical name tables is beneficial.

If you want to use a command procedure then change the startup command to
run the command procedure. Just be sure to fiddle properly with SYS$INPUT
before running ALPHALK2.EXE from within your command procedure so that it
gets its input properly. You know, the old $DEFINE/USER SYS$INPUT....

A note... do you have the correct versions of the VAXLINK2.EXE and
ALPHALK2.EXE programs? Are they damaged at all? If you want, I can email
them to you... just email me directly and I'll fire them off to you.

HTH,

Chuck 

-- 
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com
RTFM Consulting Services Inc.     864 801 2795 voice & voicemail
103 Autumn Hill Road              864 801 2774 fax
Greer, SC  29651
Do not send me unsolicited commercial email.
Loading