💾 Archived View for gemini.spam.works › mirrors › textfiles › hacking › vmsptuto.txt captured on 2021-12-04 at 18:04:22.
-=-=-=-=-=-=-
====================
THE IBM VMSSP SYSTEM
====================
PART ONE
BY
THE MOTORHEAD
INTRODUCTION
------------
IBM's VMSSP mainframe operating system is for one of the most sophistocated computers available today, the IBM 303x and 308x families of processors. These computers can handle vast quantities of memory, handle hundereds of users logged in at one tim
e, plus access many high-volume hard disks at once. To someone who has only used an Apple, a VMSSP computer would definitely fit the title 'supercomputer'. This series of tutorial text files will attempt to give the reader enough knowledge about the sys
tem to perform some usefulddestructivewwhatever tasks on hishher own.
LOGGING IN
----------
Logging onto the computer is, of course the first and most important step. The first thing you have to find is a valid username. This can be hard to do, because there is, to my knowledge, no way of seeing who is on a system before you have logged in
. Very clever for security, but not too friendly for the average userhhacker. If you need to hack out a username, they are from 1 to 8 characters long, and have a 1-to-8 character password associated with them. Start out by trying such common first and
last names like 'Jones', etc.
The login command on a VMSSP system is, quite simply, LOGIN (or LOGON). You would issue the login command like this:
.LOGIN <username> [<password>]
(The '.' is the prompt, and <password> is optional; if you don't supply a password, the system will prompt you for one.) If the username you have tried isn't valid, you will get the message:
DMKLOG053E <userid> NOT IN CP DIRECTORY
If the password you've tried is wrong, this message will appear:
DMKLOG050E PASSWORD INCORRECT
If there is already somebody logged in on the account you've tried, you will get this message:
DMKLOG054E ALREADY LOGGED ON {LINE|GRAF|LUNAME} raddr
Once you've gotten a correct usernameppassword combination, you will be greeted with this line:
LOGMSG- hh:mm:ss mmdddyyy
This indicates when the system logon message was most recently revised. Then the system logon message will be displayed, and you will be told if you have any files waiting for you in your 'reader' (which will be explained later). This message will look
like this:
FILES: {nnn|NO} RDR, {nnn|NO} PRT, {nnn|NO} PUN
One important thing to look for is one of the following messages:
LOGON AT hh:mm:ss zone weekday mmdddyyy
RECONNECTED AT hh:mm:ss zone weekday mmdddyyy
RECONNECTED means that you have ben re-connected to a session that was stopped using the 'DISC' command instead of just logging out. You should get off this as soon as possible, as the person who disconnected probably will be wanting to get back onto the
ir account.
Now that you know how to log into the system, you are ready for some of the more basic commands of the operating system.
QUERY
-----
The QUERY command is used to get various bits of information about your session on the machine, and various other system statistics. There are many options associated with this command, and only a few of them will be described here. (Note: the QUER
Y command can be abbreviated to just 'Q')
Q TIME - display the current time and date on the screen
Q Reader|PRinter|PUnch - displays on the screen files, if any, in the
reader.
Q DISK [mode] - Gives information about the various 'minidisks' attached
to the session at one time.
Q SEARCH - Similar to Q DISK.
Q USERS - Tell how many users are logged on to the system.
Q NAMES - give the usernames and terminal addresses of all users logged
onto the system.
LISTFILE [<fn> <ft> [<fm>]]
---------------------------
The LISTFILE will give a list of all or some of the files on one of the minidisks attached. The wildcard character '*' can be used to search for groups of files with a certain filenameffiletype.
GIME <label> [<cuu>] [<fm>]
---------------------------
The GIME command will attach another user's (or the system's) disk to your session. <cuu> stands for the 'address' associated with that disk, and <fm> is which 'mode' you want it stuck at. Modes are from A to Z. <label> is the 'name' associated with
the particular disk.
DROP <fm>
---------
The DROP command is the opposite of GIME; that is, it will detach a disk from your session. <fm> is the mode where the disk was GIME'd.
BASIC
-----
This will invoke the IBM BASIC interpreter, which is, if you ask me, severely brain-damaged. I would avoid it.
FORTVS <fn>
-----------
This invokes the IBM VS FORTRAN-77 compiler. The file <fn> should have a filetype of FORTRAN. The compiler will generate a file called <fn> TEXT, which contains the equivalent of an .OBJ file (for you CPMM and MS-DOS users) or a .REL file.
LOAD <fn> (START
----------------
This will load the file <fn> TEXT into memory and begin execution.
TELL <user> <message>
---------------------
This command will send <message> to <user>. Pretty basic. If the user isn't logged on, the operating system will tell you.
LOGOFF
------
Self-explanatory.
DISCONNECT
----------
This command will disconnect your terminal from your session, but still leave the session logged onto the system, in 'DSC' mode. You can re-log on to your session using the 'LOGON' command, and return to the same place you were at when you disconnec
ted. Handy if you have to go off somewhere but don't want to destroy the environment you have set up.
RECEIVE [<id#>]
---------------
The RECEIVE command is used to read files in your 'reader' onto your minidisk. Each file in the reader has an id# associated with it, and this is how you read in the file. If no id# is supplied by the user, the system will just RECEIVE the first fi
le in the reader.
CONCLUSION
==========
That's about it for Part 1, look for Part 2 soon. More system commands will be explored, as well as networking of VMSSP systems and some priveliged commands.