|
Advanced VMS hacking
NOTICE: TO ALL CONCERNED Certain text files and messages contained on this site deal with activities and devices which would be in violation of various Federal, State, and local laws if actually carried out or constructed. The webmasters of this site do not advocate the breaking of any law. Our text files and message bases are for informational purposes only. We recommend that you contact your local law enforcement officials before undertaking any project based upon any information obtained from this or any other web site. We do not guarantee that any of the information contained on this system is correct, workable, or factual. We are not responsible for, nor do we assume any liability for, damages resulting from the use of any information on this site.
_____________________________
/_____________________________\
/ \
| Inside Vax/Vms |
| Using Command Procedures |
| |
| By |
| Master Blaster |
\_____________________________/
Advanced Telecommunications Inc.
Note: The following is geared for the more advanvced hacker.
Part 1: Using Command Procedures.
----- ------- ----------
You can use command procedures to automate sequences of
commands that you use quite often. For example, if you always
use the DIRECTORY command after you move to a Sub-Directory
where work files are kept, you can write a simple command
procedure to issue the SET DEFAULT and DIRECTORY commands for you.
The following example, GO_DIR.COM, contains two commands:
$ Set Default [perry.accounts]
$ directory
Instead of using each command alone, you can execute GO_DIR.COM
with the @ command:
$ @Go_Dir
This command tells the DCL command interpreter to read the file
GO_DIR.COM and executes the commands in the file. So the command
interpreter sets your default directory to[PERRY.ACCOUNTS] and
issues the DIRECTORY command.
Note: DCL means Digital Command Language. (sorry)
Formatting Command Procedures
---------- ------- ----------
Use the DCL command CREATE to create and format a command
procedure. When you name the command procedure, use the default
file type COM. If you use this default, you don't have to use the
file type when you execute the procedure with the @ command.
Command procedures contain DCL commands that you want the DCL
command intepreter to execute and data lines that are used by
these commands. Commands must begin with a dollar sign. You can
start the command string just after the dollar sign.
Data lines do not start with a dollar sign.h|Data lines are used
as input data for commands. Data lines are used ba7*UU Vs[_2c!.VV 1e %MMU
=55 995RjRD following examle shows command and data lines in a command
procedure.
$ mail
SEND
THOMAS
MY MEMO
Did you get my memo?
$
$ Show users thomas
The first 0%9 is a command and must start with a "$". The next
lines are data lines that are used by the mail function; these
lines must not start with "$".
Using Multiple Lines for One Command
----- -------- %jjjj jjj jjj jjjjjjjj2 H$ R $.+R.9HV--ZkR $,+++K W,=HZ7,-]ZY>$[X7~Pqua
you can make the command procedure more readable by listing the
qualifers on seperate lines rather than runni> them together. To
do this, use the hyphen as a continuation character. Don't start
the continued line with "$". For example:
$ print test.out -
/after=18:00 -
/copies=10 -
z
UUubA AZj2Td(H(H(
UQ%9 =55 9 I=
UIM5Rjjjjjjjjj jjjjjjj jjjjjjjjjjj2
T++RV,(WV,W R,+++F .k&V^V $:
WW*k *V7(Z +V,,-ZW PL(J
|
|
