There are other licences/products available, but are not applicable to our environment.

Note

For full UniVision support, SCO OPEN SERVER ENTERPRISE system must be installed.

A typical "SCO Media Box" will contain :-

- SCO boot diskette version 5.xx

- CDROM containing SCO OPEN SERVER

- Licence certificate(s)

Licence certificates are supplied to enable various software features to be loaded or enabled.

The following will be required to perform a base load :-

Licence Number :-A unique number identifying each SCO product

Licence Code :-A licence code which activates the product

Licence Data :-Additional licence data needed to activate some products.

This field is not always present on the Certificate of Licence and Authenticity and is not required for licencing in all cases.

Note

Once SCO OPEN SERVER has been installed, or if additional licences are installed, warning messages are periodically displayed requesting that you register the product with SCO.

Each time SCO is installed a unique ID is generated and is used to identify that installation.

If the system is re-installed using the base media set, then it must be re-registered.

The SCO Registration Centre will supply a Registration key for each licence installed. Once these have been "keyed in", the warning messages are disabled.

As an image of the installed Operating System is created as a part of this load procedure, the above should not become an issue except during an upgrade to the Operating System.

Production will be responsible for providing Registration keys.

Installing SCO OPEN SERVER HOST/ENTERPRISE SYSTEM Base

Insert the SCO OPEN SERVER boot diskette into the floppy drive and boot the system from this floppy.

At the "Boot:" prompt enter (CR)

Note

If it ever became necessary to install boot time loaders, then these would be loaded here. Additional information will be released if this becomes necessary.

The system will test to see what hardware is installed and if any hardware errors can be detected. You will see letters ranging from D to M displayed. See the appendix headed "Kernel Initialization Letters" for an explanation.

The system will prompt you to specify your installation media type. In all cases this will be the cdrom. The SCSI ID will be recorded in the "On-Site Document".

To display a list of options press the space bar.

The system will prompt for the keyboard type. Use the space bar to display the options and select UK English with standard English as the language.

The system will prompt for the Licence Number and Authenticity Code.

Enter the data contained on the SCO OPEN SERVER Certificate.

The system will prompt :-

Enter Installation type

Select FRESH

The system will prompt :-

System Name : enter the system name

Domain Name : UUCP.com (default)

Security Profile : Traditional

Time Zone : Use the space bar to display

options

Geographical Area : Europe

Daylight Saving : No

European Time Zone: GMT

Accept the above selection.

The system will prompt for an interactive/fdisk/Divvy or default installation.

Select the option for an interactive/fdisk/Divvy installation by entering spacebar at "Hard Disk setup". At the submenu select "Partitions and Filing Systems".

The system will prompt for :-

The root password

Enter sysbml (CR)

The system will display the fdisk menu. As systems will ship with only SCO Unix loaded :-

Select option 2. Use entire disk for Unix

Select option 5 to Activate Partition

Enter q to quit

(After fdisk the drive is designated hd0a)

The system will display the "DIVVY" menu.

DIVVY is used to divide drives into divisions in the same way that disks are sliced under SVR4.

The default division for a 2.3GB disk drive is shown on the next page.

Note

Selecting this interactive option causes 'badtrk' to be run automatically. 'badtrk' is the SCO disk maintenance utility. For purposes of installing SCO OPEN SERVER take the exit option from 'badtrk', unless the drive you intend to load SCO onto requires formatting.

Divvy options are :-

Name-This is used to identify a division. For the root drive

use the ones displayed.

If a Unispooler filing system is to be created, then this division should be called 'unis'. This division is then accessed by using /dev/unis.

Create -This option brings the division into use.

Type -Select the filing system type of a division.

Support types are :-

HTFS max size 512Gb

DTFS max size 1 terabyte

NON FS for a swap area equal to 2 times

memory (See later)

Not used - not used

Note

For division unis use HTFS.

Prevent -Prevents a filing system from being created.

Start -Defines where a division starts.

2088450 1K blocks for divisions. 8001 1K blocks for the system

NAME TYPE NEW FS # 1ST BLOCK LAST BLOCK

boot EAFS NO 0 0 15359

swap NON FS NO 1 15360 211967

root HTFS NO 2 211968 2088438

Not used NO 3 - -

Not used NO 4 - -

Not used NO 5 - -

hd0a whole disk NO 7 0 2096450

Default DIVVY Table for a 2.0GB drive

n(ame)Name or rename a division

c(reate)Create a new filing system in a division

t(ype)Select or change the filing system type in a new FS

p(revent)Prevent a new filing system from being created

s(tart)Start a division on a different block

e(nd)End a division on a different block

r(estore)Restore the original table

enter choice or q to quit

end - defines where a division ends

restore - restore a default table

All systems are shipping with a separate root drive and a number of data drives.

Root will be reserved for the Operating System, swap and unispooler, if applicable.

Current systems are the 3259 and the S40.

To make future memory upgrades simpler, swap will be set to :-

3259 - 256MB (Max sys memory is 128MB)

(262144 1K Blocks)

S40 - 1GB (Max memory is 768MBs but

this will support upto

512MB RAM)

The root division will be reduced to 700MBs.

Sample root drive division tables for the S40 and the 3259 are shown below.

Use divvy options to resize the default divisions in accordance with the relevant divvy table.

NAME TYPE NEW FS # 1ST BLOCK LAST BLOCK

boot EAFS NO 0 0 15359

swap NON FS NO 1 15360 277503

root HTFS YES 2 277504 994304

unis HTFS YES 3 994305 1199105

4

5

recover NON FS NO 6 2088439 2088448

whole

disk NO NO 7 0 2096450

NCR 3259 DIVVY TABLE

NAME TYPE NEW FS # 1ST BLOCK LAST BLOCK

boot EAFS NO 0 0 15359

swap NON FS NO 1 15360 1024000

root HTFS YES 2 1024001 1740801

unis HTFS YES 3 1740802 1945602

4

5

6

hd0a whole disk NO 7 0 2096450

NCR S40 DIVVY TABLE

Once the table is correctly configured, then enter 'q' to quit.

The system will display :-

i(nstall)

r(eturn)

e(xit)

Select as applicable.

The system will display the 'badtrk' menu. Exit from 'badtrk' without

making any changes.

The system will display the software packages which are about to be installed :-

Operating System Services - all are selected

Graphical Environment - all selected

Connectivity - all except LanMan,

Netware and PCint

Documentation

Language Support

Accept the above.

The system will prompt to configure :-

Network Card - select deferred

Network Address - no card configured

Video and Graphics - IBM/VGA

Mouse - Low Resolution

keyboard mouse

email - mmdf

The system will prompt :-

Setting root password enter sysbml (CR)

Re-enter to confirm

The system will now load the packages selected earlier. (On a 3259 this takes around 1 hour.)

Once the load is completed the kernel will be automatically rebuilt and the system rebooted.

It will halt at boot: enter (CR)

The boot sequence will halt a second time at

"enter cntl d for normal boot"

enter cntl d

The system should boot up and display the SCO login prompt.

End of the base load.

To access the SCO Desktop, (always tty02), enter root (CR) followed by the password.

To access a non graphical virtual screen press

cntl/alt together and either F1, F3, F4, etc.

To Add Additional Licences or Users

Access a non graphical virtual terminal.

At the # prompt enter :

#scoadmin (CR)

From the displayed options highlight Licence Manager using the arrow keys and enter (CR)

Use the tab key to move into the product listing area.

Select SCO Open Server (CR)

Press tab to access the top menu bar

Select Licence from the top menu bar

Select the appropriate options from the pull down menu bar and enter the licencing information as appropriate.

When licencing activities are completed then tab to the menu bar and exit from the utility.

Note

Some licences force re-tuning to take place.

Tuning a SCO Open Server System

The following parameters require tuning on a SCO Open Server System regardless of whether it is to support UniVision or Charisma :-

NCALL128

MAXUP50 + 2 x number of Users

NPROC50 + 2 x number of Users + 10%

The above parameters can be added to the stune table by entering:-

#/etc/conf/bin/idtune -m [parameters] [value] (CR)

Once all parameters have been tuned, then rebuild the kernel by entering :-

#/etc/conf/bin/idbuild (CR)

The system will prompt :

Do you wish the kernel to boot by default?

Enter 'Y'

The system will prompt :

Do you want the kernel environment rebuilt?

Enter 'Y'

Note 1

Answering 'Y' to the first question causes SCO to copy the existing kernel to Unix.old and to install the new kernel as Unix.

Answering 'Y' to the second question will make any necessary changes to /etc/inittab and to the device node files.

To cause the changes to have effect, reboot the system.

Configuring Tapes and Disks

Once the system load is completed and the system is tuned, then additional disks and any tape units must be manually added. SCO Unix does not configure them automatically.

To Configure Additional Disk Drives and Create Filing System

Prior to configuring additional disk drives you should make a note of :-

BUS ID to which the SCSI is installed

SCSI host adapter ID

SCSI ID of the disk drive

LUN (always 0)

At the root # prompt enter :

#mkdev hd (CR)

Select option 2 to add a SCSI drive to a SCSI controller.

The system will prompt for the SCSI controller device driver.

Typically this will be 'alad'. (default)

The system will prompt :

Which alad SCSI adapter supports this device? 0 or 1

Refer to the information recorded at the beginning of this section.

The system will prompt :

What SCSI bus is this device attached to?

Refer to the information recorded at the beginning of the section.

The system will prompt :

LUN?

Enter 0 (CR)

The system will prompt :

Update SCSI configuration Y/N

Enter Y (CR)

The system will prompt :

Relink kernel Y/N

Enter Y if you have added all additional drives or N if you wish to add more.

Once the kernel has been relinked reboot the system.

The above actions add the SCSI drive to the device tables. To install and set up the drive divisions :-

#mkdev hd (CR)

Repeat the above to identify the drive to be prepared. This time instead of prompting to relink the kernel the system will invoke fdisk.

From the fdisk menu select option 2 to partition the entire disk to be used by Unix.

Then select option 5 to make the partition the active partition.

Then exit from fdisk.

The system will now invoke badtrk.

badtrk reserves a table for bad SCSI logical blocks to be recorded. It does not allow you to scan the disk for defects. To scan for defects you must invoke badtrk from the command line.

Exit from badtrk without invoking any of its options.

The system will now invoke divvy.

Refer to the section which describes divvy at the beginning of this document.

If this is a UniVision system then modify the division sizes so that you create one division which is the size of the drive.

If this is a Charisma system and this is the only data drive or the last data drive then create one division which is 300MB in size and a second division which is the size of the remaining free space.

Note

All filing systems will be HTFS. The maximum filing system size for HTFS is 512GB.

Set 'type' to be HTFS, set new FS to NO and calculate the first and last blocks accordingly. (Note 1 block = 1KB).

For a UniVision system use uni1, 2, 3 etc as the name.

For a Charisma system use char1, 2, 3 etc as the name.

Name the 300MB division 'chart'.

Note

The name is used to reference the division, i.e. /dev/uni1 or /dev/char1.

Once the division information is entered then enter q to quit followed by i to install.

Note

Division 6 is reserved for use by FSCK.

To create filing systems on newly created divisions at # enter :

#mkdev fs (CR)

Select the option to Add a New Filing system to system (CR)

Enter the division onto which you wish to create the filing system

i.e. :

/dev/uni1 or /dev/char1

You will be prompted to enter a mount point, (directory name).

For Charisma systems use /charisma1, 2, 3 etc.

For the test division use /chartest.

For a UniVision system use /unistore1, 2, 3 etc.

The system will prompt to know whether the filing system should be mounted when entering multiuser mode.

Enter 1. Always mount [name] (CR)

The system will prompt Do you want to allow User to mount this filing system?

Enter Y (CR)

Note

This is essential otherwise Charisma's SAVEFILES will fail as it mounts and unmounts filing systems.

To create and mount the filing system enter (CR)

Repeat to divide additional drives and to make and mount filing systems.

Once all drives have been installed, divided and have filing systems mounted then enter df (CR) and ensure that all filing systems are correctly mounted and are of the correct size.

To configure a tape drive

At the root # prompt enter :

#mkdev tape (CR)

Select configure a SCSI tape from the displayed options.

Select to Install a SCSI tape drive.

Enter the SCSI Adapter device drive (for example alad) (this will be the default). Enter the device ID of the SCSI host adapter. Enter the SCSI ID of the tape unit. Enter the LUN of the tape unit; always 0.

When prompted to modify the vendor specific ID string accept the defaults.

When prompted select the appropriate tape type from the displayed list.

The system will prompt for you to modify the default boot string setting for the tape drive. Accept the defaults.

Once the tape configuration is completed then relink the kernel and reboot.

Test the tape drive for proper functionality.

Configuring the parallel printer port and com 1/2 ports

Note

Some products such as the Smartmon require ports to be configured differently from the instructions below.

If installing such products then refer to the Information Release associated with these products.

To configure com 1 & 2

At the root # prompt enter :-

#mkdev serial (CR)

Select i to install a new serial board (CR)

Select 1 for a standard tty device (CR)

Select 1 for a port card (CR)

Select 1 or 2 to configure com 1 or 2 as appropriate (CR)

Select 1 or 2 for IBM - com 1 or 2 as appropriate (CR)

Select ? (CR) for choices (CR)

Select the appropriate tty label (CR)

Note

The installation of additional I/O controllers is documented in the Information Release issued for specific devices.

If all devices are installed then relink the kernel and reboot the system.

Test the com ports as appropriate.

To configure a parallel port

At the root # prompt enter :-

#mkdev parallel (CR)

Select add a parallel port (CR)

Select parallel port address 378 - 37RF (CR)

Select the default interrupt - Interrupt 7 (CR)

If no other devices are to be configured then relink the kernel, reboot and test the parallel port.

To modify /etc/gettydefs file tp prevent autobauding

The gettydefs file is the equivalent of the ttydefs file in NCR SVR4. It defines the ports characteristics.

Typical entries are shown below :-

n # B2400 HUPCL # B2400 CS8 SANE HUPCL

TAB 3 ECHOE IXANY #\r\n@!login # m

m # B4800 HUPCL # B4800 CS8 SANE HUPCL

TAB 3 ECHOE IXANY \r\n@!login # n

The getty process that causes login to be displayed can cycle through the entries in the gettydefs file moving from one baud rate to the next.

The label for each entry is shown at the left hand side of the entry. In the examples above this is 'n' and 'm'.

The label that will be tried next is shown at the extreme right hand side of the entry.

In the example above if the getty is unsuccessful with label m it will autobaud to label n and if it is unsuccessful with label n it will autobaud to label m.

To prevent this label at both ends of each gettydef entry must be the same.

These should already be correctly configured, but, if they are not, use vi to modify them as required.

To install a Network Card

Login to root (CR)

#custom (CR) (enters Software Manager in scoadmin)

Insert the network driver diskette into the floppy drive or load from the cdrom.

From Software Manager : arrow right to change from Host to

Software (CR)

Arrow to select Install new (CR)

System will ask From what host machine?

Check that the (system name) is asterisked (change with arrow) TAB.

With Continue highlighted press (CR)

System prompts to insert Media and select media Device

Select Floppy Disk Drive 0 TAB to Continue press (CR)

The system will examine media, and display reminder to use netconfig to configure the installed driver. (CR) to OK

System will then load network drivers.

When completed, exit Software Manager and at #-

Enter # netconfig (CR)

With Hardware highlighted press (CR)

Select Add LAN adapter press (CR)

System will display the type of controller found for example

SMC Etherpower 8432e PCI bus# 0 device 17 Function 0 (CR)

System will then display the Add Protocol screen and ask which protocol you require adding to this adapter.

Arrow to SCO TCP/IP (CR)

System will then display Protocol Configuration screen. Select as follows

Local host:(System user name)TAB

IP Address:128.0.0.1TAB (use DEL to delete if reqd.)

Net mask :255.255.255.0TAB

Broadcast address:128.0.255.255TAB

Domain :(leave blank)TAB

TCP connects:256TAB

TAB again to highlight advanced options (CR)

Check Gateways *NO TAB through other options to OK (CR)

TAB again down to OK (CR)

If it is necessary to modify the defaults for the controller then system will display Modify HArdware Screen, use TAB to set as follows :

PCI Bus: 0 TAB

Device : 10 (use arrow up to give options,CR to select)TAB

Function: 0 TAB

TAB again to Advanced options (CR)

Use arrow up to give options, select BNC (CR) OK (CR)

TAB to OK in Modify Hardware Screen (CR)

TAB to highlight Hardware (CR) x to exit

Relink kernel when prompted and reboot

Test card with #ping 128.0.0.1 (CR) after reboot

Creating an Emergency Boot Floppy disk set

The emergency boot floppy disk set allows you to recover a system in the event of a catastrophic system failure without having to completely reinstall the system.

These, together with a complete system CPIO, will allow systems to be recovered with the minimum of downtime.

The emergency boot floppy set and CPIO backup is to be created :-

(1)By Production after the initial O/S installation

(2)By Installation personnel once all peripherals have been properly configured

(3)By whomever after modification to any part of the systems configuration

To create the emergency diskettes :-

At the root # prompt enter :

#mkdev fd (CR)

From the menu select 2 (CR)

Create emergency boot floppy disks

Select the appropriate floppy drive type and density,

normally 2 (CR)

When prompted for the type of file system enter 1 (CR)

to create the root floppy disk.

Follow screen prompts until the root drive is created.

If you are prompted to create a shell enter n

Set the floppy to write protected and label it :

"Emergency root" [Date].

Press (CR) to return to the Select Filesystems menu.

Enter 2 (CR) to create the emergency boot floppy diskette.

Once the boot diskette has been created then write protect the floppy and label it :

"Emergency Boot" [Date]

To create a full cpio backup install a tape into the default tape unit and enter

cpio find . -print | cpio -ocvB -O /dev/rct0

To list the contents of the tape enter

cpio -itvcB -I /dev/rct0 (CR)

Installing Charisma

Base load by Production staff

Install BML Termcap, Terminfo and File transfer programs

Insert BML Termcap diskette into drive 0.

At the # prompt enter :-

'tar xvt6'(CR)

tar will extract termcap.bml,terminfo.bml,topc,frpc,rz and sz.

'cd /etc'(CR)

'cp termcap termcap.old'(CR)

'cp termcap.bml termcap'(CR)

'cd /usr/lib/terminfo'(CR)

'tic terminfo.bml'(CR)

Install Micro Focus Cobol OSX

Login as 'root'

Password system

At the # prompt enter :-

'mkdir /usr/lib/cobol'(CR)

'cd /usr/lib/cobol'(CR)

If extracting from 3.5 inch diskette :_

'tar xvt6'(CR)

Repeat for all disks.

If extracting from a cartridge tape :-

'tar xvt8'(CR)

Remove media from relevant device.

At the # prompt enter :-

#sh ./install (CR)

Cobol will be installed. You will be prompted for

Continue Installation? Enter Y (CR)

Default location for driver programs? Enter /usr/bin (CR)

Once the # prompt returns then enter :-

# cd bin(CR)

# ./adiscf (CR)

The Cobol configuration menu will be displayed.

EnterF2 to alter the configuration

F3 to accept/display option

F3 to display individual options

From the displayed options

Select 14 Accepts into non edited numeric fields

Select 3 for processed free format

Exit back to the main menu by entering Esc, Esc, Esc.

EnterF4 to save the configuration

F3 to overwrite the existing configuration

1 to make this the default configuration

Esc to exit back to #.

Editing System Files for Terminal Configuration

Until recently SCO Charisma systems did not make use of 'qterm' to identify terminal emulation. Instead entries were made in the /etc/ttytype file for each port configured onto the system.

Network processes cannot make use of the file as it is not possible to tie a network process to a specific driver. Therefore all SCO systems shipped as of the release of this document will use qterm to identify terminal types as they log into Charisma.

For completeness however instructions on how to configure the ttytype file are included.

The ttytype file

File is in location /etc/ttytype

Using the vi editor terminal types should be entered for tty1A, tty2A and ttya??.

Termcap entries for bml used terminals are :-

tlwWyse 120 in vt100 mode

tlTexas Instruments 924

xlTexas Instruments 928

t9Texas Instruments 931

vt220BML MC5C (link terminal in vt220-7

mode)

See FILE EXAMPLES for example of ttytype file.

The /etc/inittab file

The /etc/inittab file contains entries for all serial ports. It is used to assign a device driver and gettydefs label to each port. Examples of an inittab entry is shown below :-

ao1:23:off:/etc/getty tty1a m

ao2:234:respawn:/etc/getty tty2a m

The first example is for device tty1a.

The 'off' statement says it is disabled and the 'm' statement corresponds with the label 'm' in the /etc/gettydefs.

This port will never display a login prompt.

To enable this device enter :-

#enable tty1a (CR)

This will alter off to 'respawn' and create a 'getty' process which will cause login to be displayed.

The second example shows an entry for device tty2a which is enabled for use with a gettydefs label of m.

Examples of gettydefs label are :-

i 1200bds

k 2400bds

m 9600bds

n19200bds

To check that a getty is running on a port enter :-

#ps -t ttyname (CR)

If any changes are made to the /etc/inittab file using the editor then a corresponding change must be made to /etc/conf/init.d/sio.

The reason being that each time the kernel is relinked so the /etc/inittab file is recreated from /etc/conf/init.d/sio.

Once all devices have been added to the inittab file, then ensure they are enabled by displaying the inittab file. If any entries need to be enabled then enter :-

#enable [ttyname] (CR)

Creating a User

Login as 'root'

Password sysbml

At the # prompt enter :-

'scoadmin' (CR)

Select Account Manager from list of utilities and press (CR).

Select User from the top menu bar and

press (CR)

Select Add New User and press (CR).

Enter the following :-

Login:bml

User ID:200

Comment:

Password:<*> Set password now

Login Shell:sh

Home Directory:/charisma1/bml

Login Group:group

Select OK and press (CR)

<*>Remove password

[ ] Force password change at next login

Select OK and press (CR)

Select Host from the top menu bar and

press (CR)

'x' (to exit)

TAB to the top menu bar

Select File from the top menu bar and

press (CR).

'x' (to exit)

When prompted set up the password as 'bml 8000'.

Loading Charisma software

Login as 'bml'

Password

Insert Charisma Data Directories Tape into cartridge tape drive.

At the $ prompt enter :-

'tar xvt8'(CR)

This will extract the Data Directories from the tape.

Insert Charisma Programs Tape into cartridge tape drive.

At the $ prompt enter :-

'tar xvt8'(CR)

This will extract the Charisma Program files from the tape.

Press CTRL D to logout.

Login as 'bml'

Password bml 8000

bm1 .profile

Unix uses .profile files to initialize variables either on a system wide basis or on a user basis.

In Charisma the file / charisma1/bm1/.profile is executed as users login to bm1 from the Unix login prompt.

Variables used by Charisma are defined in this file which are then "exported" so that Unix processes can use lookup tables to find out what device a variable, (label), represents or where to go to find a particular set of code or data.

For example You have seen that Charisma uses printer labels of LP01, LP02, etc. Using the Unix spooler does not require any further action. However, Charisma has a direct print feature, which most users seem to want to use, which allows print jobs to be outputted without having to use SPOOL feature.

So that Charisma can issue the various commands to Unix to enable jobs to output "directly", it is necessary to define that LP01 is actually a device with the link file /dev/LP01.

The .profile which is shipped with all SCO/Charisma configurations includes entries which :

(1)Define the emulation for the system console

(2)Turn on the console virtual terminal manager

Whilst Users should not use the console to execute Charisma applications, if they do it is useful to still be able to access Unix from the console.

(3)Use the response from qterm to automatically set up the correct emulation for each terminal in the system.

(4)Set up the paths for IQ & Ufax.

(5)Set up the User licence for Charisma.

(6)Configure the default tape device for savefiles, etc.

Configure the default printer to print out savefiles information.

(7)Set up the Cobol environment.

(8)Define printers.

(9)Identify where the various Charisma directories are.

(10)Define ULIMIT as 4000,000. This controls the maximum file size that can be opened by a BML User.

Most of these parameters will never need modification.

The next section identifies those parameters which are "site specific" and must be modified if the system is undergoing installation. A typical .profile is included at the end of this section.

Before altering .profile you should copy it, as fallback should things go wrong.

login as bm1, (password bm18000)

Enter

cp .profile .profile.date (CR)

Where date is todays date

To access .profile

login as bm1, (passport bm18000)

To display the .profile enter

pg .profile (CR)

To edit the .profile enter

vi .profile (CR)

To print the .profile enter

lp -d [printername] .profile (CR)

1.User Licence

This is controlled by an entry in the .profile

Note Well

This is company confidential information. If licences are increased without proper authorisation, or if Users are advised on how to illegally increase their Charisma licence, then EDP Group Employees involved may be subjected to disciplianry action.

Identify the line

if test 'who bm1 wc-1' -gt xx

xx will be a number which is the maximum number of concurrent bm1 Users allowed to be logged in. This is the licence that the User purchases.

xx is to be modified to the exact number of Charisma Users that the User has purchased. This is defined on the RFS which is raised from the Customer's order.

Customer Service Supervisors are to ensure that Installation

Engineers are properly briefed on what the value should be.

2.Savefiles Variables

To edit in the default savefiles tape device and printer, find the section headed -

#-------------------savefiles variables

If necessary, replace the tape device name with the correct tape device name.

If necessary, replace the printer label with the printer label of the printer the User wishes to use for savefiles information.

Return to Index