Visara Master Console Center Installation User Manual

Page 14

Visara Master Console Center

Telnet/RS232 Consoles:

1. Identify non-mainframe hosts you want to monitor/control (e.g.,

UNIX servers, AS-400s, etc.). (This was done with the completion
of the Quotation Form.)

2. Specify the method of desired communication between the MCC

and each non-mainframe host (RS232 or TELNET).

3. For each TELNET access, supply the IP address required for

access.

4. Verify that network connectivity exists between telnet hosts & the

MCC.

5. For each TELNET access, supply a user-account so the MCC can

“log in”. This information must be available for Visara personnel

at installation.

6. If you want terminal emulation available at the Thin Client /

workstation(s), please indicate the number and type (s) of
terminals required.

General (all consoles):

1. Identify “new automation” procedures you would like performed.

2. Supply Visara with a list of “trial objectives” so we can be sure

your trial runs smoothly (e.g., “we are interested only in console

consolidation”, “we’d like to see console consolidation, IPL, some
level of automation”, etc.)

3. Supply Visara with a list of trial USERIDs. These IDs should be

from four to eight characters in length, and you should indicate

whether each user is allowed to:

“VIEW ONLY” just see, not alter. For example, no MVS

COMMAND authority, etc.)),

“OPERATE” (see and alter. For example, issue MVS Commands,

“OPERATE and ADMINISTER”. An administrator can add
additional GROUPS and USERIDs within those groups. GROUPS

control access authority levels. USERIDs control access to the

system - each userid is associated with one or more groups.

4. Decide on “production” requirements. For example, do you want

the MCC network separated from your normal network traffic? Do

you need additional bandwidth and/or facilities? Do you have a

backup plan? When will you need training?