AB 150/2 INFORMATION RELEASE

3. Printers

To configure Charisma printers find the section labelled -

#----------------assign printer here---------

As applicable, replace the /dev/xx with the names of the link files that were used when creating the printer sysadm. For example, this will be /dev/LPxx for printer connected to MTS ports or /dev/term/xxx for printers connected to RTC ports.

By default there are eight printers configured - LP01 through LP08.

If more printers are installed then add additional line :-

dd_LPxx = [device name]

Where xx is the next number and device name in the link file used when configuring the printer.

Add dd_LPxx to the entries

export dd_LP01 etc else the printer will not print from within Charisma.

No other variables should be changed unless you are directed to do so by Support or as instructed by a Project Plan.

Installing CHARTEST

CHARTEST is where BML install test data. It is sed for training etc.

CHARTEST will be installed into the filing system /chartest.

Before installing the software, it is necessary to create a User called 'bmltest'.

Refer to the the section entitled 'Creating a User' for information of how to do this.

For Home Directory replace /charisma1/bml with /chartest/bml.

The password will remain as bml 8000.

Once the User has been created then login as bmltest, password bml 8000.

Insert the Charisma Data Directories tape into the cartridge tape.

At the $ prompt enter

tar xvt8 (CR)

This will extract data directories from the tape.

Insert the Charisma programs tape into the cartridge tape drive.

At the $ prompt enter

tar xvt8

This will load Charisma programs.

Once the above have loaded, then exit back to the Unix login prompt.

Login as bml and ensure that the bml console prompt is displayed.

Modify the .profile as applicable.

CHARTEST is now installed.

Installing UniVision

You can now install UniVision in the normal way, except you should not the following :

(1)SCO does not tolerate User names with uppercase characters. For example -

UniV will fail to install properly

whereasuniv will install correctly

(2)On occasions SCO does not install UniVision properly if the home directory does not exist. For example -

If UniVision is installed into /unistore1/univ and the sub directory /unistore1/univ has not been created then the installation may fail.

Create the target directory before commencing the UniVision Installation. For example, from root enter :-

#mkdir /unistore1/univ (CR)

CONFIGURING PRINTERS/VDUS CONNECTED TO SPECIALIX

MTS Terminal Servers

Networked devices do not have permanent Unix process relationships.

Therefore, software has to be configured which will "connect" a Unix printer to a specific terminal server port. This software has to be made to be auto configuring at boot time, so that this connection is permanently made.

There are 4 stages to configuring printers so they are Charisma ready:-

1.MTS installation and configuration

2.mtsd installation and configuration

3.Charisma .profile modification

4.Record Sheet

(1)MTS Installation and Configuration :-

A.The Specialix MTS terminal server is a network node in its own right. This means it has to be assigned a unique name and IP address to make it addressable by the host system.

The actual IP address will be specified by the local CSS as a part of his Project Plan. However, MTS names will be mts1, mts2, etc. Ideally, mts1 will be the terminal server closest to the host system. (In the event of an upgrade, use the name of the nearest MTS with an 'a' added. Do not reconfigure existing MTS devices).

To configure an MTS (see appendix 1).

Connect a VDU to port 8 on the MTS. This is reserved for MTS/mta configuration purposes and should not be used for running applications.

Note

If there are no VDUs being supplied to sites/locations; only P.C.s, then the CSS is to ensure that a comm 1 to MTS cable is supplied. It should be long enough to reach MTS terminal servers in their installed location. This can then be used with the Windows terminal to configure the MTS.

The VDU/comm port should be set for:-

VT100 eumulation, 9600bd, 8 bits, 1 stop bit no parity.

On pressing enter the MTS login prompt will be displayed.

To login enter admin (CR)

The MTS# prompt will be displayed.

Note

At no time during configuration is a password to be set.

To set up the correct screen emulation enter

MTS# set line . termtype vt100 (CR)

To access the menu driven configuration utility enter

MTS# screen (CR)

B.Configure the MTS to recognise the host system :-

Select Network Configuration (CR)

Select Host table (CR)

Select ADD Host (CR)

Enter the host name of the system to which the MTS is connected, followed by (CR). (In the case of multiple hosts this will be to be repeated.)

(You can display this by paging the /etc/hosts files.)

To set the host systems IP address

Select change host (CR)

Highlight the new entered host name. Use the del key to erase the default entry and enter the IP address of the host followed by (CR).

When prompted, save and exit by pressing (CR).

Use the Esc. key to exit back to the Network Configuration Menu.

Use the Esc. key to exit back to the Main Menu.

C.To configure the MTS in the server configuration to recognise its own name and IP address :-

Select Server Configuration (CR)

Enter the name of the MTS

Use the downward arrow, highlight the Internet address field and enter the IP address of the terminal server (CR).

When prompted save and exit by pressing (CR)

D.Add the MTS name and IP address to the /etc/hosts file on the main system.

E.To confirm that the system and the MTS recognise each other :-

Press the Esc. key to exit to the main menu. Highlight Command Line mode (CR).

At the MTS# prompt enter reboot (CR)

Answer Y to reboot.

Once rebooted re-login to the MTS# prompt and enter ping system name (CR).

You should see messages being repeated indicating that data is being sent and received. To stop this test press 'del'. If the message is not repeated, then the MTS/Host setup is incorrect.

Re-check the MTS setups. If you are still unsuccessful, contact Support for assistance.

At the Host # prompt enter

#ping MTS name (CR)

You should see similar messages to the above being displayed. If not, re-check the configuration in the /etc/host file. If you are unable to resolve the problem, contact Support for help.

F.To configure ports for VDUs or Printers

Re-display the MTS configuration screen and select

Line configurations (CR)

Line settings (CR)

Using the space bar alter VDU speeds to 19200.

Terminal to vt100 and Page to 1.

Note

Use    control K to move upwards

control J to move downwards

control H to move left

control L to move right

Ports intended to be used by printeres should be left 9600 &dumb.

When reconfiguration is completed press (CR)

When prompted save and exit.

Select Virtual Circuits (CR)

Note

For VDU ports use the space bar to set 'type' to 'dir tel'.

Leave port 8 as 'normal'.

For printers use the space bar to set 'type' to 'rev raw'.

For printers only change the MTS port number and the HOST port number so that:-

1st MTS 21xx where xx = the port number

2nd MTS 22xx where xx = the port number

(Use DEL or PRINT SEND to delete existing port nos.)

When the configuration is complete press (CR)

When prompted save and exit

G.To setup a default user to cause the processrs to log into bm1.

Press the Esc key to return to the main menu.

Select Users (CR)

Select Add User (CR)

Enter bm1 (CR)

Password bm18000 (CR)

Select Set Sessions

Use the space bar to change 'type' to 'rlogin' on session 1 only

Use the space bar to set 'auto' to 'on' on session 1 only

Press (CR)

When prompted save and exit

H.Use the Esc key to return to the Main Menu.

Select Command Line mode (CR)
at the MTS# prompt enter reboot (CR)
Enter Y to reboot (CR)
The MTS will re-initialise using the new configuration.

Configure other MTS as appropriate.

(2)Mtsd Installation and Configuration

mtsd is the software utility supplied by Specialix which 'connects' a print process to an MTS port. It is contained on a single floppy which is shipped with each MTS.

To install the mtsd software:-

Insert the floppy into a suitable drive

# cd /usr/bin (CR)

Enter #tar -xvf /dev/rdsk/f03ht (CR)

Once mtsd is loaded enter

# uncompress amts/* (CR)

# chmod +rwx amts/* (CR)

To check that mtsd is accessible enter

#amts/mtsd.svr4 - help (CR)

The mtsd help utility should be displayed. Press (CR) to exit.

To start mtsd processes which will "connect" /dev/xx to MTS ports enter from root

#/usr/bin/amts/mtsd.svr4 -print -mtsname [mtsname] -mtsport [mosport] -linkfile [device address] -noclose &(CR)

For example for printer LP01 :-

Printer LP01 is device /dev/LP01 connected on mts1 on port 4. Therefore the command line entry to start the amts process will be :-

#/usr/bin/amts/mtsd.svr4 -print-mtsname mts1 -mtsport 2104 -linkfile /dev/LP01& (CR)

If you enter #ps -ef you will see the above process in the process list.

To create printers in Unix use sysadm by :-

sysadm, printers, printers, add.

Note

Use defaults, unless directed otherwise, below.

Fill in the form by entering :-

Printer name - LP01 LP02 etc

Printer type - dumb

Do you want to use standard configurations - No

Device or basic networking address /dev/[printer name] (/dev/LP01)

Use F3 to save the form.

At the next form change :-

Can a User skip the banner page to 'Yes'

Press F3 to save the configuration.

To test the printer enter

# banner test 1p -d LP01 (CR)

Test should be printed on printer LP01

Repeat for all printers.

Once all the printers have been tested using the banner command test, then using

#man vi 1p -d [printer name] (CR)

Checking for correct flow controlling

To create the mtsd process as part of a system boot up :-

#cd / etc/rc2.d (CR)

#vi S99mtsd (CR)

Create an entry for each printer

/usr/bin/amts/mtsd.svr4 -print -mtsname [mtsname] -mtsport [mtsport] -linkfile [device address]&

Reboot the system and test each printer to ensure that they print.

(3)Enabling For Charisma

To enable Charisma to have access to the printer it is necessary to include them into the .profile in the /charisma1/bm1 directory.

Prior to modifying the .profile it should be copied.

Login as bm1 then :-

#cd /charisma1/bm1 (CR)

#cp .profile .profile.old

To add the printers to the .profile

#vi .profile (CR)

In the section entitled "Assign printers here"

for each printer add an entry

dd_[printer label] = [device name]

For example, for printer LP01 the entry would be :-

dd_LP01=/dev/LP01

(4)Recording Action

1.For each MTS complete the attached record sheet

These should be attached to the on-site document.

2.Print the contents of S99mtsd

#cd /etc/rc2.d (CR)

#1p -d [printer name] S99mtsd (CR)

Attach this to the on-site document.

3.Print the .profile

#cd /charisma1/bm1 (CR)

#1p -d [printer name] .profile (CR)

Attach this to the on-site document.

Charisma Installation by Field Service Personnel

As you will have read in the previous section, Production Staff will install Cobol, Charisma and associated utilities using their master software sets. They then create backups which are shipped with the system to be used to recover the system in the event that there is a catastrophic failure.

If you have to recover a system, then use the following procedure :-

You will require the following media :-

Boot floppy which was created in Production
Root floppy " " " " "
System backup tape of /dev/boot filesystem
System backup tape of /dev/root filesystem
Charisma programs backup
Latest Charisma SAVEFILES tape

In the event that the root drive has failed, then load SCO Open Server as described at the beginning of this document.

Stop at the point where you are directed to load additional licences. At this point proceed to 'RESTORING THE SYSTEM'.

If the Operating System is corrupted or some other drive has failed, then proceed to 'RESTORING THE SYSTEM'.

RESTORING THE SYSTEM

Insert the BOOT Diskette into drive 0 and turn on the machine.

At the boot: prompt hit the (CR) key.

When requested insert the ROOT Diskette into drive 0

and hit (CR).

At the # prompt enter :-

mkdir/stand(CR)

mount /dev/boot /stand(CR)

cd /stand(CR)

Insert the /dev/boot filesystem Tape into SCSI tape drive 0.

cpio -iudv -I/dev/rStp0(CR)

The boot filesystem will be extracted.

On completion insert the /dev/root filesystem Tape into SCSI tape drive 0.

umount /stand(CR)

cd ..(CR)

mount /dev/hd0root /mnt(CR)

cd /mnt(CR)

cpio -iudv -I/dev/rStp0(CR)

The root filesystem will be extracted.

On completion enter :-

cd ..(CR)

umount /mnt(CR)

sync;sync;haltsys(CR)

The system will halt and SCO can be booted from the Hard Disk again.

After Restoring the Operating System and rebooting from the Hard Disk :-

Login as 'bml'

Insert the Charisma Programs Backup Tape into SCSI tape drive 0.

At the 'bml ttyxx:' prompt enter :-

tar xvt8(CR)

Charisma programs will be re-installed in the bml home directory.

On completion insert the Charisma data 'savefiles' Tape into SCSI tape drive 0.

cpio -iudv -I/dev/rStp0(CR)

Charisma data will now be restored.

On completion the system restoration is complete.

Check that all printers and terminals are working correctly in case the /dev/root backup was out of date.

SCO Open Server HOST & ENTERPRISE

Pentium and Fast 486 PCI Motherboard with Intel Triton chipset

On some PCI system boards containing Intel Triton chipsets, the system console keyboard will lock and become unusable.

This is because of a timing loop in the kernel's keyboard driver that is not long enough or some faster machines.

In this case it is possible to load the Operating System with no changes to the system but after basic Operating System installation follow the instructions below.

Reboot the machine and enter system bios configuration.

Disable all system cache and set processor speed to low if possible.

Reboot the machine at its new slower speed and load Unix.

Only bring the system up in single user mode by entering the root password at the '.....ctrl d to continue....' prompt.

At the # prompt enter :-

cd/etc/conf/pack.d/cn(CR)

cp Driver.o Driver.rel(CR)

_fst-w Driver.o(CR)

At the * prompt enter :-

rd42dat+0x1e?w 0xe830(CR)

The hex editor should return with :-

rd42dat+0x1e: 0xe80d= 0xe830

At the * prompt enter :-

$q(CR)

At the # prompt enter :-

cd/etc/conf/cf.d(CR)

./link_unix(CR)

This will relink the system kernel with the changes.

Say YES to be the default kernel.

Say NO to rebuild kernel environment.

Reboot the machine and enter system bios configuration.

Reset the bios for optimal performance.

Reboot.

Return to Index