home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 18 REXX
/
18-REXX.zip
/
remcmd.zip
/
REMCMD.DOC
next >
Wrap
Text File
|
1993-05-13
|
3KB
|
69 lines
This collection of Rexx programs constitutes a "remote command" utility
which can be used to execute commands remotely on another OS/2 machine
while viewing the results at your monitor. The transport between the
local and remote machines is APPC. The total package relies on some
Rexx external function packages which can be found in CompuServe.
These are:
RXU.ZIP - OS2DF1 - OS/2 Developer Forum #1
Rexx/Other Languages
ACSUTI.ZIP - OS2DF2 - OS/2 Developer Forum #2
Communications Manager
RXAPPC.ZIP - APPC - APPC Info Exchange Forum
Tools/Utilities
It also requires a program called PMPRINTF.EXE, or any equivalent
program which takes data off an OS/2 queue (DosReadQueue) and puts
it in a PM window of some sort (MLE, etc.). PMPRINTF.EXE itself
can be found in the OS2BBS through IIN/IBMLink. It may be available
elsewhere too.
Just to make things more clear, here are some defintions:
Local Machine - Where you run the program "REMCMDC1.CMD", which is
also where PMPRINTF.EXE runs (where you view the
output of commands executing on the remote machine ...
Remote Machine - Where your commands actually execute (i.e. where
the program REMCMDC3.CMD executes).
The remote machine must be LU6.2 addressable from the local machine
(either by an explicit partner-lu definition, a Connection Network,
or via APPN routing).
Communications Manager at the remote machine must be configured either
to support implicit inbound TP requests, or have an explicit TP
definition for the tp "REMCMDC3". The purpose of the program
"REMCMDC3.EXE" is so that implicit inbound TP support will find him
and execute him (i.e. program name = TPname.EXE). REMCMDC3.EXE is
just a passthrough program which calls a Rexx program of the same
name. In fact, if you rename him, he will call a Rexx program of that
new name (e.g. rename him to "foo.exe" and he'll call a Rexx program
called "foo.cmd").
As far as security is concerned, you can choose whether or not to
have the tp REMCMDC3 require conversation security. REMCMDC3 has some
code in it which attempts a UPM process-level local logon at the
remote machine with a userid/password supplied by you at the local
machine. This userid/password must have Admin authority at the
remote machine or the remote command session is terminated. Of course,
you could change or delete this feature. The programs also practice
a sort of crude encryption while passing data twixt themselves. This
is just so a userid/password isn't sent totally naked across a network.
The functions of the RXU function package which are used in this
collection of programs are:
RxCreateRexxThread
RxKillThread
RxStartSession
RxPmPrintf
RxSi2h
RxSoSe2h
RxCreatePipe
RxDestroyPipe
RxUpm
I'm sure I've left something out of this .DOC file. Feel free to fire
me a note if you have questions, etc.