1 1
-
INSTALLATION INSTRUCTIONS FOR NEW INSTALLATIONS
+ ____________ ____________ ___ ___ _____________
0 MTS Distribution 5.1
0 August 1983
- 1. Run DECKGEN to prepare a set of TABLES for your machine.
To load DECKGEN, IPL from the Dump/Restore tape. This will
probably put the machine into wait state (unless you have a
3066, 3270, or 1052-compatable device at address 3A8). To
get the IPLREADER to talk to you, press "request" on a 1052
or "enter" on a 3066 or 3270 (i.e., cause an attention
interrupt). When it asks if you want to run the current
system, reply "NO" and enter the commands:
0 LOAD NAME=*IPL.DECKGEN ADDR=xxx
START
0 where xxx is the device address of a tape drive on which
+ ___
the MTS Utility tape is mounted. See component 1021/12 for
more information about the IPLREADER.
0 See the DECKGEN writeup (comp. 004/8) for information on
how to proceed from here. Since DECKGEN was loaded by the
IPLREADER and therefore is told where the console is, it is
not necessary to give an attention interrupt on the console
to wake it up. It is a good idea to run DECKGEN from a
hardcopy terminal if this is possible. If not, you should
take notes as you go along because you may need to rerun
DECKGEN if you make a mistake and you can save some time if
you keep a record of what you've done. You should include
at least one public volume, MTS001, in these tables. The
tables you produce should be written to tape for use in
steps 2 and 15 below. There is no need to include your
entire configuration in these tables if you intend to use
the tables macros to produce tables for your system (see
section 17F below).
- 2. You are now ready to load MTS itself. Rewind the
Dump/Restore tape and IPL from it again. Reply NO when
asked if you want the current system. This time enter the
commands:
0 LOAD NAME=*IPL.NDSKSYS ADDR=xxx
REPLACE TABLES FROM yyy
(Reply to the prompt for a printer address for a map
or press the cancel key (on a 3066, 3215 or 1052) or
PA2 (on a 3270) if you don't want a map).
START
0 where xxx is the address of the MTS Utility tape and yyy is
+ ___ ___
the address of the tape written by DECKGEN in step 1. The
no disk version of MTS should now be running.
1 2
-
3. Proceed with the start-up procedures described in the MTS
operators' manual (comp. 592). Some additional points not
mentioned in the operators' manual are:
0 A. The prompt for the time and date will occur only if
the TOD clock is not set. For example, entering the
time and date as
0 2 41 pm 5 23 81 EDT
0 will set the time and date to 14:41 Eastern Daylight
Time on 23 May 1981. The timezone need not be given
if you gave the correct timezone when you ran DECKGEN,
i.e., MTS will use that one by default.
0 B. MTS keeps GMT in the TOD clock. Although this agrees
with the standard set by IBM for the use of the TOD
clock, some IBM systems do not do this. This means
that even if the clock has been set by another system,
it may be off by several hours and you will want to
reply "NO" when asked if the time is correct. You can
then enter the correct local time, which MTS will use
+ _____
to load the TOD clock with GMT.
- 4. At this point you will be told that MTS001 (or whatever
name(s) you told DECKGEN to use) couldn't be found (which
is reasonable since we haven't restored it yet) and you
should respond by entering CANCEL. This will result in a
fairly serious looking message about an error in catalog
initilization which can be ignored. If you are using a set
of assembled TABLES rather than TABLES produced using
DECKGEN, the message you see at this point will be
different, but the effect is the same.
- 5. Start the job status master job by typing
0 JOBS MAS
0 at the operator's console.
- 6. The following steps can be done from the operator's console
or from a 1052, 3066, 3036, 3277, 3278 or 3279 terminal.
If you are going to work from the operator's console you'll
need to start an MTS job by typing
0 MTS NDSK OPER
0 at the console. If you are going to work from a terminal
you'll need to start an MTS job on that terminal by typing
0 MTS NDSK xxxx
0 at the operator's console, where xxxx is the MTS device
+ ____
1 3
-
name of the terminal to be used. The NDSK parameter tells
MTS to avoid using the file system.
- 7. Next, signon by entering
0 SIGNON ccid
ccid (the password)
0 where ccid is any four character string. If you are
+ ____
working at the operator's console you won't be asked to
enter a password. If you are working from a terminal you
will need to enter a password and because you are using the
no disk system the password will be the same as the ccid
used on the signon command (remember that MTS ccids shorter
than four characters are padded on the right with the
string ".$." and that the pad characters need to be
included in the PW).
- 8. Next attach the MTS Utility tape to your job by entering
0 $SET PROT=OFF
$GET >Txxx
$CONTROL *AFD* VOLUME=MTSUTL
0 where Txxx is the MTS device name of the tape drive where
+ ____
the MTS Utility tape is mounted.
- 9. If you have 2305s or 4305s to use for paging, you must
format them by entering
0 $CONTROL *AFD* POSN=FMT2305
$RUN *AFD*
FFnn
FFnn
.
.
.
$ENDFILE
- 10. If you are going to use an obsolete 2301s for paging,
format them by entering
0 $CONTROL *AFD* POSN=DRUMINIT
$RUN *AFD*
- 11. If you have 2305s, 3805s, 3825s, 4305s or 2301s to use for
paging, start the paging device processor by typing
0 PDP
0 at the operator's console.
1 4
-
12. Next DASDI a paging disk and at least one public volume by
entering
0 $CONTROL *AFD* POSN=DASDI
$RUN *AFD*
Dxxx PAG001 VX PAGING
Dyyy MTS001 VX 1 IPL
. . .
$ENDFILE
0 where Dxxx is the name of the device where the new paging
+ ____
pack is mounted and Dyyy is the name of the device where
+ ____
the new file system volume(s) is mounted. See the General
Notes (comp. 461/19) for instructions on using FILE:DASDI.
- 13. If you started the PDP in step 11, add the paging disk by
typing
0 PGET Dxxx
0 at the operator's console. If you didn't start the PDP
before, start it now by typing
0 PDP
0 at the console.
- 14. Use DISKCOPY to restore the D5.1 system from the
distributed dump/restore tape(s). You should specify the
IPL option, but SLOW and SWAP aren't necessary. See the
General Notes for information on running DISKCOPY.
0 $CONTROL *AFD* POSN=DISKCOPY
$RUN *AFD*
TAPE
>Tnnn
DISK
Dyyy MTS001
IPL
$ENDFILE
0 where >Tnnn is the name of the MTS device on which the D5.1
+ ____
dump/restore tape is mounted and Dyyy is the MTS device
+ ____
name of the disk drive to which the data will be restored.
- 15. Stop your machine, and IPL from the new disk. Again reply
NO when asked if you want to run the current system and
enter the commands:
1 5
-
LOAD NAME=*IPL.D5.1SYS
REPLACE TABLES FROM xxx
(Reply to the prompt for a printer address for a map)
START
0 where xxx is the address of the tape written by DECKGEN in
+ ___
step 1. The D5.1 version of MTS should now be running.
- 16. Proceed with the start-up procedures described in the MTS
Operators' Manual (comp. 592). This time you shouldn't be
told that MTS001 couldn't be found.
0 After initilization is complete you should do the following
from the operator's console or a terminal
0 SIGNON MTS
password (see below)
$RUN RAMROD
CREATE xxxxx FROM D5.1SYS
enter comments if desired
REPLACE TABLES.DUMMY FROM >Tyyy
enter comments if desired
enter null line or date when prompted for version
reply "OK" to confirmation request
DELETE SEG0.NCA.TABLES
reply "OK" to confirmation request
DELETE SEG1.NCA.TABLES
reply "OK" to confirmation request
RENAME TABLES.DUMMY TABLES
reply "OK" to confirmation request
CURRENT
reply "OK" to confirmation request
0 The passwords for most of the userids on the distributed
test pack are the same as the userids, e.g., the password
for MTS is MTS (unlike the NDSKSYS passwords the ccid pad
characters are not part of the password, so the password
for MTS is just MTS). The only userids for which the
passwords are different are the terminal benchmark IDs
(Bnnn) since the passwords for these are irrelevant. (Note
that a password is not required if you are using the
operator's console as your terminal.) The xxxxx on the
+ _____
CREATE command is a name for the new system, which normally
would be the MTS "model number" for the date, e.g., UG153
for August 15, 1983. Tyyy is the MTS device name of the
+ __ __ _ ____
tape drive containing the tape written by DECKGEN.
0 This procedure will cause the "current" system on your
MTS001 pack to correspond to your machine configuration so
that the next time you IPL you can reply "YES" (or enter a
null line) when asked if you want to run the current
system. See the RAMROD (comp. 1019/16) and IPLREADER
(comp. 1021/12) writeups for more information.
1 6
-
17. You now have a working D5.1 version of MTS (presumably).
You can start to run user programs after you've created
some user IDs. To do this, see the description of the
accounting maintenance procedures (104/137) and (104/138),
which you should obtain from the *FS tapes.
0 There are several things that you will probably want to do
to clean up a few loose ends before going much further.
Some of these are:
0 A. Fix HASP for whatever local options you desire. See
the description of these options (comp. 387/26). You
may also want to change some of the commands in
STRT:HSP, the command file for *HSP, which can be used
by the operators to issue the appropriate HASP $START
commands after starting HASP.
0 B. You will also want to change the contents of STRT:LAS,
the command file for *LAS, which can be used by the
operators to start up the terminal lines.
0 C. Fix TSFO (the 2703/1270 MTS Device Support Routine) to
agree with whatever hardware is available. There are
several assembly parameters described in the source.
0 D. Fix up the command statistics directory file
SYS:CMDDIR for the appropriate tapes. If you don't do
this, the system will occasionally mount a tape with
rack number CMDTP (which must be labeled CMD001) to
dump the command statistics data. Eventually this
tape will fill up with command statistics data and the
system will get mad unless you have fixed up
SYS:CMDDIR to give it more tapes to use. A
description of the structure of this file is available
in the Operators' Manual on the *FS tapes (comp. 592).
0 E. Write new versions of the IPLBOOT and IPLREADER
programs to the system pack with the correct device
address for your system console (see the IPLREADER
description, comp. 1021/12).
0 F. In the tables produced by DECKGEN none of the file
system disks are flagged as being under disk manager
control. You can place them under disk manager
control using the DMGRSTAT job program or the *-file
job *DSK. This will need to be done after each IPL
until you code and assemble a version of tables for
your configuration use the tables macros.
0 G. Install ASMH. Once you have a signed and paid
license agreement with IBM for ASMH contact UM for a starter
version of ASMH (ASMH is an IBM program product and as a result
cannot be included on the standard MTS distribution tapes).
1 7
-
18. General things new installations should know.
- A.
How to sign on using the operator's console:
0 1. Enter "MTS OPER" on the operator's console
2. It will come back immediately for input.
3. Enter the signon command.
4. You are now signed on if the ID exists. No
password is required for signon from OPER for "staff"
IDs and SIGFILEs are not processed. Also the "last
signon" message and the "signed on at" message are not
printed.
0 B. An obsolete 2301 drum must have device name DRM1. If
you have a second 2301, it must be named DRM2.
Similarly, 2305s must be named FF00 to FF07 for the
first one, FF08 to FF0F for the second one, FF10 to
FF17 for the third, etc. 3805s and 3825s should be
named FB00, FB08, FB10, ....
0 C. A "privileged" ID is one with X'80' on in the second
byte (byte 1) of the accounting record (set by
accounting maintenance program on request). If the ID
is privileged then no checking for maximum money,
etc., is made. The expiration date and maximum file
space, however, are checked. Also this bit allows the
+ ___
user to run programs with PROT=OFF, and allows
privileged SYSTEMSTATUS commands to be given.
0 D. A "public file privileged" ID is one with X'08' on in
the second byte of the accounting record. This allows
the user to create a public file.
0 E. A user with the ACCPUSE bit on in his accounting
record can also declare a program to be run with
PROT=OFF and can issue privileged SYSTEMSTATUS
commands.
0 F. A user with either ACCTLB or ACCPLB on in his
accounting record can set LSS (Limited-Service State)
off even if the load is too high.
0 G. Certain IDs are used automatically during the start-up
sequence (INIT, SEG2, SYS., STRT). These IDs must be
part of project WOPN on the test pack system so that
they can signon even if the "in use" bit in the
accounting record is set. The project number used for
this test in your production system may be changed by
using a different project or project substring (or set
of them) on the &IPLPROJ SETC symbol in
COPY:GLOBALSETS and reassembling MTS.
0 H. MTS makes certain checks to be sure that only IDs that
belong to individuals that work for the computing
1 8
-
installation can perform certain "privileged"
operations. This check is made by checking the
project number associated with the ID. At UM only
projects that start with "W" are assumed to belong to
installation staff. This may be changed by altering
the setting of the SETC symbol &SYSPROJ in
COPY:GLOBALSETS and assembling and installing a new
version of MTS.
0 I. The distributed system contains a dummy version of
the rate number subroutine (RNBR) which gives zero rates. You
will almost certainly want to replace this routine with a
version that calculates rate numbers according to the rules of
your installation and also update the file *RATEFILE to include
your MTS rates.