SunSystems SunAccount Version 426 UNIX Oracle Platforms 8

SunSystems 4
UNIX Oracle Platforms

SunSystems UNIX Oracle Platforms Manual
Issue 10, November 2004 (based on software version 4.2.6)
Copyright © 1982-2004 Systems Union Holdings Ltd
All rights reserved
The copyright of this manual and the computer software described herein and
provided herewith are the property of Systems Union Holdings Ltd. No part of
this publication or the computer software may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any human or computer
language, in any form or by any means without the express written permission of
Systems Union Holdings Ltd.
Systems Union Holdings Ltd

Systems Union House
1 Lakeside Road
Aerospace Centre
Farnborough
Hampshire
GU14 6XP
England
Phone: +44 (0) 1252 556000
All trademarks mentioned are the products of their owners

Contents
User Assistance ........................................................................ 1
Introduction ............................................................................... 4
Preparation
Hardware and Software Requirements ..................................... 5
Server Memory .................................................................... 5
Server Disk Space ............................................................... 5
Printer .................................................................................. 5
Oracle Software ................................................................... 6
Preparing the Environment ....................................................... 7
Installation
Installing SunSystems ............................................................... 8
Running the Installation Script ............................................. 8
Amending Scripts for Oracle 8.1.7.2 or Higher ................... 12
Amending Scripts for Oracle 9.2.0.3 or Higher ................... 14
Tablespace Independence for SunSystems Databases .......... 17

Installing a Single SunSystems Schema ............................ 19
Creating Additional Schemas ............................................. 19
Migrating Existing Installations to Use Independent
Tablespaces ............................................................ 19
Login and Configuration ..................................................... 20
Upgrading SunSystems .......................................................... 21

Before You Upgrade .......................................................... 21
Installing the New Version of SunSystems ......................... 23
Restoring SunSystems Data Tables .................................. 24
Files and Directories ............................................................... 29

Program Files .................................................................... 29
Other Files ......................................................................... 29
Using SUN.INI ......................................................................... 33
Contents
Administration
Running SunSystems .............................................................. 34
Specifying the Location of Print, Work and Backup Files ... 36
Configuring the Terminal Display ....................................... 37
Configuring the Keyboard .................................................. 38
Logging in to SunSystems ...................................................... 41
File Permissions and Ownership ............................................. 44
SunSystems Graphical Client ................................................. 45

Client Hardware Requirements .......................................... 45
Client Software Requirements ........................................... 45
Preparing the Host Environment ........................................ 46
Installing SunSystems Graphical Client ............................. 46
Running SunSystems Graphical Client .............................. 47
Troubleshooting Guide ....................................................... 48
Printing from SunSystems ....................................................... 50

Displaying Stored Reports ................................................. 50
Printing from UNIX ............................................................. 50
LaserJet Printer Setup ....................................................... 52
Example Control Sequences for HP LaserJet Printers ....... 54
Oracle Administration and Maintenance Tasks ....................... 58

Backup Routine .................................................................. 58
Monitoring Database Size .................................................. 58
Improving Performance ...................................................... 59
Appendices
Appendix A: SunAccount Transfer File ................................... 64
Appendix B: File and Table Names ......................................... 68
Appendix C: Error Messages .................................................. 84
Appendix D: Database Overview .......................................... 100
Appendix E: Machine Variations ........................................... 102
Appendix F: terminfo ............................................................. 104
Appendix G: Enabling Business Analyser ............................. 106
Appendix H: Cobol Run-time Licensing ................................. 108
SunSystems UNIX Oracle Platforms Manual Version 4.2.6

User Assistance
OVERVIEW
This section outlines the manuals you can use to find out more about SunSystems.
It also covers the other ways in which you can investigate SunSystems and its
functionality.
THE SUNSYSTEMS PLATFORM MANUALS
The SunSystems Platform Manuals have been written to help you install and run
SunSystems in a variety of environments. They contain technical information
and advice and are critical to a successful implementation. The platform manuals
detail SunSystems upgrade procedures for new sites.
The SunSystems Platform Manual is divided into four sections:
Preparation, Installation, Administration and the Appendices.
THE REFERENCE MANUAL
Each SunSystems and SunAccount or SunBusiness function is presented in

alphabetical order. These include Ledger Accounting, the Fixed Asset Register,
Corporate Allocations, Sales Order Processing, Inventory Control and Purchase
Order Processing. Each section provides an overview of a function, followed by
descriptions of the boxes on the screen.
Where you see the text Conversion Module, this indicates that the option described
is only operational if you have a license for multi-currency processing.
Where you see the text Multi-Lingual Module, this indicates that the option
described is only operational if you have a license for the multi-lingual facility.
The Reference Manual also covers the SunSystems tools and shortcuts, such as
FREEFORMAT and CALCULATOR.
User Assistance 1
THE APPRECIATION GUIDE
The Appreciation Guide describes the scope of SunAccount or SunBusiness. It is

aimed at the manager responsible for implementing SunSystems, and for controlling
business procedures.
There is a section describing the user definable reports and documents available
within SunSystems.
THE DEMONSTRATION DATABASE
Three demonstration databases are provided with each system: DEM, DM1, and
DM2. Each is a fully operational database, which includes examples of all aspects
of SunSystems, SunAccount and SunBusiness. You can use them to familiarise
yourself with the system, before using your live database(s).
THE TECHNICAL REFERENCE MANUAL
The Technical Reference Manual is geared to the more technical user of

SunSystems. It includes information about the programming language, the structure
of the programs, naming conventions, user hooks and translating SunSystems into
other languages. The appendices outline the layouts of all SunSystems files.
HELP
Within SunSystems you can access full information about SunSystems by selecting
Help, Contents and Index from the menu. This enables you to use the online
manual’s text searching facilities.
Each box in SunSystems is help enabled. If you need to find out what a box does
whilst you are using SunSystems, place your cursor in the box and press F1. See
the section SunSystems Tools, Buttons, and Keystrokes in the Reference Manuals
for further information.
2 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

ELECTRONIC MANUALS
All of the SunSystems manuals are available on the CD in PDF format. These can
be viewed and printed using Adobe Acrobat Reader, which is available from
Adobe's web site. If you decide to install the electronic manuals permanently they
are then easily accessible from the SunSystems Program Menu.
The most up-to-date manuals for the latest version of SunSystems can also be
found on the SunSystems web site at:
www.sunsystems.com
User Assistance 3
Introduction
This manual covers versions of SunSystems for Oracle 8.1.7.2 and above, or Oracle
9.2.0.3.0 or above, and has been written to assist the system administrator with the
installation of SunSystems with an Oracle database. It covers installation on a
variety of UNIX-based systems and includes installing and operating Graphical
Client for UNIX.
The appendices contain additional useful information such as: table and filenames,
the transfer file layout, and error messages.
Regardless of whether you are installing SunSystems for the first time, or upgrading
to the latest version of the software, the installation procedures are the same. The
same steps also apply to a demonstration system or a live issue of SunSystems.
F Note: There is a separate manual for those who wish to use an ISAM
database.
THE ISSUE MEDIA
SunSystems for UNIX Oracle is supplied on CD only.

The demonstration databases DEM, DM1 and DM2, are supplied with the
SunSystems issue media. These databases are used in conjunction with the
Appreciation Guides; you are strongly recommended to load them.
Manuals
See the previous section User Assistance for a full description of information
provided in each manual. Where necessary, Addenda, Errata and User Notes are
included with the manuals. These must be read carefully.
IMPORTANT NOTE
When you are installing SunSystems you are strongly advised to use all
recommended settings. If you wish to use a configuration that does not include
the settings recommended in this manual, you should contact your supplier to
ensure that the configuration you wish to use is supported.

Hardware and Software
Requirements
This section describes the hardware and software configuration required to run
SunSystems.
When the system is operated in multi-user mode, the number of terminals which
may be used is subject to the configuration supplied, and any restrictions of the
computer itself. Each screen must be cursor addressable and have a minimum of
25 lines of 80 characters each.
SERVER MEMORY
The amount of memory required for SunSystems varies depending on how the
system is used by each of the concurrent users. Approximately 12Mb is needed
for the first user, and up to 10Mb for subsequent users. These figures do not
include memory used for the operating system or other software packages. The
actual memory requirements vary depending on the way data is accessed and the
performance criteria you require.
SERVER DISK SPACE
The files are stored on the issue media in compressed format. Make sure you have
at least 350Mb of free disk space before beginning the installation.
To establish the amount of disk space available on your file systems, you should
use the df UNIX command. Consult your UNIX documentation for further
information about using df on your machine.
PRINTER
The printer must be capable of printing 132 characters per line. If you use a
printer which prints on A4 or American quarto size paper, you have to print in
compressed mode for certain SunSystems reports. If the wide column feature is
used in the reporting functions, up to 256 characters per line may be required.
Hardware and Software Requirements 5

ORACLE SOFTWARE
SunSystems can be installed only when Oracle server and Procedural SQL have
already been configured on your system.
F Note: The hard disk space and memory requirements for Oracle software
itself depend on the type and number of Oracle components installed on
your system. This depends on the type of UNIX server and you should
consult your Oracle installation documentation for further details.

Preparing the Environment
Preparing the environment is essential to both the installation and the day to day
running of SunSystems.
It is important that you read this section carefully.
Operating System Setup

Before installing SunSystems you must set up the operating system environment.
The installation should be performed by the super user (root) or system
administrator. This user should create a directory to contain the working copy of
the system. Any directory name can be used, but you are advised to create a
directory called sun426 beneath the user applications directory (usually called
/u, /opt, or /home). This new directory should allow access by all system
users, for example:
mkdir /home/sun426
chmod 777 /home/sun426
The directory name chosen is referred to as $SUNDIR throughout this document.
UNIX Shells
SunSystems runs interactively using the Bourne or Korn shell. However, if you
are running SunSystems using FREEFORMAT in background mode, only the Bourne
shell is supported. The C shell is not supported at all with SunSystems.
Preparing the Environment 7

Installing SunSystems
If you are already running a version of SunSystems, you should read the section
Upgrading SunSystems before following the instructions below.
This section describes copying the files from the issue media and installing
SunSystems. The installation of all SunSystems modules is performed by the
install.sun script. This script is interactive and informs you of each step it
performs. These steps are described in detail below. (See the subsection Running
the Installation Script).
A log file called suninstall.log is created when the script has completed
successfully. It logs the version of SunSystems, the date of installation, and all
languages installed.
Having completed the installation, read the manuals located in the docs
subdirectory for any further information.
RUNNING THE INSTALLATION SCRIPT
The installation script is used to install SunSystems. In the example below it is

assumed that SunSystems version 4.2.6 is being installed in the directory /home/
sun426.
1 Log in as user Oracle and ensure the environment variables ORACLE_HOME
and ORACLE_SID are defined and exported. For example:
ORACLE_HOME=/home/oracle; export ORACLE_HOME
ORACLE_SID=SUNSYS; export ORACLE_SID
F Note: If these environment variables are not set the installation script will
prompt you for them as it is essential that they are correctly set.
2 Use su to become super user (root).

3 Mount the CD, using the appropriate command:
AIX mount -v cdrfs -o ro /dev/<CD-DEVICE> /cdrom
Digital mount -t cdfs -o noversion /dev/<CD-DEVICE> /cdrom
HP mount -F cdfs -o cdcase /dev/dsk/<CD-DEVICE> /cdrom
UnixWare mount -F cdfs -r -o fperm=0500 /dev/<CD-DEVICE> /cdrom
F Note: The CD device name <CD-DEVICE> should be replaced with the

appropriate device for the target machine.
On Solaris the CD mounts automatically on /cdrom/cdrom0.
4 Change directory to the CD mount point, for example:
cd /cdrom
5 To execute the installation script, type:
sh ./install.sun
6 Depending on the SunSystems release you are installing, some or all of the
following options are available from this CD:
Install SunSystems for the first time
Install an additional language
Install Service Pack
Install Option Pack
Quit
F Note: If you choose to install an additional language you are offered the
selection of languages as described in the subsection Language Selection,
but without the facility to select a BASE language.
Installing SunSystems 9
Language Selection
All the languages available for each release are displayed:
Enter required languages.
NOTE that the first language selected will be the BASE
language.
Select from
C Chinese Simplified
D Dutch
E English
F French
G German
I Italian
J Japanese
P Portugese
S Spanish
T Chinese Traditional
Enter the initial letter(s) of the language(s) required:
If a language is not displayed, it may not be available for this release. Contact
your supplier for more information.
If you intend to use a live (i.e. a non-demonstration) version of SunSystems, make
sure the base language entered here matches the base language specified in your
serialisation details.
F Note: Although you can install any language version, you can use only the
languages for which you are serialised. If in doubt, consult your serialisation
details. If, however, you wish to install a demonstration system, you can
use up to four language versions.
The Demonstration Database

It is recommended that you install the demonstration database DEM to train new
users. This database also allows you to test report formats and journal definitions
before going live, and to experiment with a demonstration copy of the software.
The install script prompts you with the following:
Do you wish to install the Demonstration Database for
your BASE language in directory /home/sun426/back ?
Selection ? (y/n)
Type y to install the demonstration database. The files are copied into $SUNDIR/back
and can be restored using FB=File Backup/Restore within SunSystems.

Editing the Script Files
The script files used to access SunSystems are shipped with the SUNDIR variable
set to SUNSYS_HOME. They are automatically edited to reflect your particular
choice of directory. The files affected are szrun, ssls.sh and bin/*su*
and bin/SUN. The ORACLE_HOME and ORACLE_SID environment variables
are written to the bin/SUN script.
Copying the SUN File to /usr/bin

The installation procedure asks you if you wish to copy the SUN file to /usr/bin.
If you do not want to use /usr/bin, type n and remember to add $SUNDIR/bin
to the path of each user.
Starting Communication Processes CCITCP2 and SSMASTER

The installation procedure asks if you want the communications processes
(CCITCP2 and SSMASTER) to be started automatically when the server is
rebooted. If you answer y then the script to start this process is copied to the
appropriate directory. This varies depending on which UNIX you are running,
but it is normally the rc2.d directory, found in either /etc or /sbin.
F Note: These communication processes are only required if you are using
Graphical Client.
Installing Service Packs

Select item 4 from the available installation options to apply the current service
pack to an existing SunSystems release.
The service pack option does not install a complete edition of SunSystems.
However, if this is required, select option 1 which installs SunSystems and then
applies the relevant service pack.
Service packs are cumulative, so installing the latest edition includes all prior
fixes from previous service packs.
Please refer to your SunSystems supplier to verify the correct prerequisite software
version that is required to apply the service pack.
AMENDING SCRIPTS FOR ORACLE 8.1.7.2 OR HIGHER
You must install Oracle Server Manager to be able to run the SunSystems Oracle
scripts. The scripts are located in the admin/<ORACLE_SID>/create
directory, and these automate the process of creating an Oracle database. They
define the configuration of your Oracle instance and database. They are supplied
with a default configuration which may not suit your installation, so you must
modify them according to the requirements at your site. This ensures the smooth
running and optimum performance of your database.
The scripts comply with the Oracle Optimal Flexible Architecture (OFA) set of
file naming and placement guidelines for Oracle software and databases. Although
using OFA is not a requirement, Oracle Corporation recommends that you use it if
your database is likely to grow in size, or if you plan to have multiple databases.
OFA is designed to provide significant benefits in the following areas:
• Ease maintaining Oracle software and databases through standard file
organisation
• Reliability through data spanning multiple physical drives
• Performance through decreased I/O contention for disks
F Note: Distributing I/O across disks can produce significant performance

gains. In particular, proper distribution of redo log files and data files
when creating an instance can aid performance. This may affect the paths
you specify in replacing the above text strings. See the Oracle Server
administrator’s documentation for information on how to distribute I/O
via the placement of these files. For more information about OFA consult
your Oracle documentation.
Below is a list of the scripts supplied with SunSystems which you should modify.
No other scripts should be modified in any way.
Oracle Scripts Supplied with SunSystems
F Note: In the scripts below the examples refer to <ORACLE_SID>. This is

the Oracle instance name.
admin/<ORACLE_SID>/pfile/init<ORACLE_SID>.ora
Instance parameter file. This contains configuration and tuning parameters for
creating your Oracle instance. You should edit it to suit your requirements. It is
based on the init.ora file, which is supplied with Oracle software. See the
Oracle Server administrator’s documentation for information on optimising
performance using this file.

It is advisable to place at least one of the control files on a separate disk device to
the others. This ensures the database is not lost if the disk containing the control
files should fail.
This file will automatically be linked to the default Oracle parameter file directory
($ORACLE_HOME/dbs) to enable the Oracle utilities to be used. See your Oracle
documentation for more details.
It is essential that you configure the parameters in this file correctly for your
requirements to ensure your database performs optimally.
admin/<ORACLE_SID>/create/<ORACLE_SID>run.sh
Starts an idle Oracle instance and creates the Oracle database. The
create database command specifies the location, size and maximum number
of redo log file groups. If a particular character set is required, edit this file. See
the Oracle Server administrator’s documentation for further information on the
create database statement.
admin/<ORACLE_SID>/create/<ORACLE_SID>run1.sh
Calls Oracle scripts to create the Oracle data dictionary. Creates tablespaces and
rollback segments required for SunSystems. You should edit this script to apply
default storage parameters to the create tablespace and create rollback segment
statements. See the Oracle Server administrator’s documentation for information
on how to calculate appropriate storage parameters and to determine how to
configure your rollback segments. This can have an impact on the performance of
your system.
admin/<ORACLE_SID>/create/<ORACLE_SID>run2.sh
Calls further Oracle scripts for the Oracle data dictionary.
admin/<ORACLE_SID>/create/<ORACLE_SID>altertablespace.sh
Alters the system users default tablespace and temporary tablespace.
admin/<ORACLE_SID>/create/dbusers.sh
Creates default users and roles within Oracle.
Running the Oracle Scripts

Log in as the Oracle user, change directory to:
$SUNDIR/admin/<ORACLE_SID>/create
Run the following script:
<ORACLE_SID>.sh
This script calls the scripts supplied with SunSystems one by one.
Checking the Oracle Log Files for Errors
You must check the log file alert<ORACLE_SID>.log in the directory
$SUNDIR/admin/<ORACLE_SID>/bdump/
You must also check any log file in the directory $SUNDIR/admin/
<ORACLE_SID>/create/
AMENDING SCRIPTS FOR ORACLE 9.2.0.3.0 OR HIGHER
The Oracle scripts, which are located in the install directory beneath the
program directory, automate the process of creating an Oracle Instance / Database.
These scripts should be modified, according to the requirements at your site, as
they are supplied with a default configuration. The scripts comply with the Oracle
Optimal Flexible Architecture (OFA) for file placement and also use the Oracle
Managed Files (OMF) feature for file naming. Although using OFA and OMF is
not a requirement, Oracle Corporation recommends that you use both features.
F Note: SunSystems does not support versions of Oracle 9i prior to Oracle

9.2.0.3.0.
F Note: For more information on OFA and OMF please consult your Oracle
documentation.
OFA-Compliant Directory Tree of Sample SunSystems Database

The following lists the contents of the install directory and shows the directory
structure of the OFA-compliant SunSystems Database.
$SUNDIR
/install
/CreateDatabase.sh
/initTemplate.ora
/CreateDB.sql
/CreateDBFiles.sql
/CreateDBCatalog.sql
/PostDBCreation.sql
/CreateUsers.sql
/sundbs
/admin
/sun
/bdump
/cdump
/pfile
/scripts
/udump

/oradata
/sun
Assumptions:
• $SUNDIR is the directory where SunSystems is installed.
• OFA-compliant directory structure created under the sundbs directory is
located in $SUNDIR.
• ORACLE_HOME is set to the value supplied during installation.
F Note: Distributing I/O across disks can give significant performance gains.
In particular, distributing Redo Log files and Data files when creating an
Oracle Instance can aid performance. See Oracle documentation for more
detailed information on performance issues.
Oracle Database Creation Scripts

This section describes the function of the Oracle Instance/Database creation scripts
located in the install directory. These scripts should be modified to suit your
sites requirements before the CreateDatabase.sh file is executed.
CreateDatabase.sh
This batch file controls the creation of the Oracle Instance/Database. It performs
the following tasks:
• Creates OFA directory structure under the sundbs directory.
• Creates the init${ORACLE_SID}.ora parameter file in its correct OFA
location.
• Creates the Oracle Instance, Password file, Database and SPFILE.
• Creates default SunSystems Oracle Users and Roles.
• Assumes that the following environment variables are defined:
SUNDIR - SunSystems home directory
ORACLE_HOME - Oracle installation directory
ORACLE_SID - name of database to be created
F Note: The Oracle password file is created with default Oracle passwords.
• SYS / CHANGE_ON_INSTALL
• SYSTEM / MANAGER
These should be changed after the Oracle Instance/Database has been created for
security.
initTemplate.ora
This file contains the Oracle Instance configuration and tuning parameters. See
Oracle Database Reference manual. This file contains variables that are replaced
when the parameter file is created in the current OFA location.
CreateDB.sql
This script connects to the Oracle Instance and creates the Oracle Database. See
Oracle SQL Reference manual.
CreateDBFiles.sql
This script connects to the Oracle Instance and creates additional Tablespaces.
See the Oracle SQL Reference manual.
CreateDBCatalog.sql
This script connects to the Oracle Instance and runs the following Oracle scripts
in order to create Oracle Data Dictionary structures.
$ORACLE_HOME/rdbms/admin/catalog.sql
$ORACLE_HOME/rdbms/admin/catexp7.sql
$ORACLE_HOME/rdbms/admin/catblock.sql
$ORACLE_HOME/rdbms/admin/catproc.sql
$ORACLE_HOME/rdbms/admin/catoctk.sql
$ORACLE_HOME/rdbms/admin/owminst.plb
$ORACLE_HOME/sqlplus/admin/pupbld.sql
PostDBCreation.sql
This script connects to the Oracle Instance and compiles any invalid PL/SQL
modules. Also creates an Oracle SPFILE and restarts the Instance.
CreateUsers.sql
This script connects to the Oracle Instance and creates default SunSystems Oracle
Users and Roles.

Tablespace Independence for
SunSystems Databases
This section is intended for qualified Oracle Database Administrators only, and
explains how it is possible to use independent and secure schemas in a single
SunSystems Oracle instance.
OVERVIEW
Although SuperUser SUN is adequate in most cases, you may require greater
flexibility in how the Oracle database is used. You can have separate database
tables, including an independent installation table within each personal tablespace.
This allows multiple SunSystems schemas to be held within one Oracle instance.
For security, each schema can only access its own identified set of tables. This
configuration has the additional advantage that both identical and multiple
SunSystems database codes can be user defined within each schema, providing
greater flexibility and simpler management. For example, each tablespace could
include a demonstration SunSystems database called DEM.
Tablespace Independence for SunSystems Databases 17

EXAMPLE
The following example shows two independent tablespaces held within one
database:
File System (Program Directory)

/Company1/SunSystems /Company2/SunSystems
Tablespace: SUNCOMP1 Tablespace: SUNCOMP2

Owner: US1 Owner: US2
SALFLDGEM SALFMSC SALFLDGEM SALFMSC
SSINSTAL SSINSTAL
VSSINSTAL VSSINSTAL
Key
owner access only
owner and SSA access
Oracle Users
User Name Password Default Tablespace Roles
US1 ??????? SUNCOMP1 SUNROLE

US2 ??????? SUNCOMP2 SUNROLE
SSA SUNSSP irrelevant SSAROLE

New View: VSSINSTAL
The Oracle user SSA has select and update privileges. This is required for
operations such as confirming login identity and maintaining user counts. The
view is as restrictive as the requirements of SunSystems allow.
INSTALLING A SINGLE SUNSYSTEMS SCHEMA
To create a single SunSystems schema within a multi-user Oracle environment,

you need to add another user tablespace and an Oracle user. You must also edit
the SUN.INI file.
SUN.INI Entries
In SUN.INI, enter the line sunuser= followed by your user name. For example:
sunuser=US1
This entry must be changed whenever you wish to access an alternative tablespace.
If you decide to use SuperUser SUN at a later stage, the sunuser entry should
be removed.
CREATING ADDITIONAL SCHEMAS
You can create additional schemas through the Oracle Schema Manager. You
must also use the command grant unlimited tablespace to user,
but with a different user name.
MIGRATING EXISTING INSTALLATIONS TO USE INDEPENDENT

TABLESPACES
To migrate existing installations to use independent tablespaces, complete the

following steps:
1 You must remove any public synonyms that exist for SunSystems tables through
the Schema Manager once the specified number of tablespaces have been
created.
2 Use FB=File Backup/Restore to back up each SunSystems database.
3 Back up the installation, report definition and data dictionary files.
4 Create the required number of SunSystems super users in Oracle with individual
default tablespaces.
Tablespace Independence for SunSystems Databases 19

5 Log in as each super user and create an OD=Operator Definition for that super
user, then restore the required database backup files.
6 Restore previously shared data, i.e. the installation table (SSINSTAL) and
remove any entries that are no longer needed.
F Note: You can transfer data using an Oracle database rather than FB=File
Backup/Restore. However, you should only do this if you are a qualified
DBA.
LOGIN AND CONFIGURATION
When you run SunSystems in a multiple tablespace environment, you need to use
slightly different procedures. Specifically, you should avoid using SuperUser
SUN.
If you log in using SuperUser SUN, the error message ‘INVALID’ appears at the
bottom left corner of the screen. You must use the sunuser name designated in
SUN.INI and the password defined in the Oracle database.
After using DB=Database Definition, and FB=File Backup/Restore to restore your
data, select OD=Operator Definitions. In OD=Operator Definitions, create an
operator with the name you specified as sunuser in SUN.INI, and the
corresponding password. You can alter the password later if you wish.
If you are using multiple tablespaces, you should avoid amending the definition
for SuperUser SUN in OD=Operator Definitions.

Upgrading SunSystems
This section covers the installation procedure when a previous version of

SunSystems is currently loaded. There are many circumstances in which an upgrade
is necessary:
• Loading a new version
• Loading a new release of the same version
• Extending your licence to use SunSystems.
Installing a new version of SunSystems allows you to access numerous new features
and changes to the functionality of the software. This is indicated by the first and/
or second digit(s) of the release number being increased, for example moving
from version 3.5.4 to 4.2.6.
Installing a later release of the same version of SunSystems may involve relatively
minor amendments to the software; in this case only the third digit release number
of SunSystems is changed, e.g. moving from 4.2.1 to 4.2.6.
Extending your licence could be changing the number of users, or changing the
number of modules that you can access. For example, adding four more users, or
the Multi-Currency module, or an extra language.
Whatever the reasons for your upgrade, the procedure remains the same. See
Appendix H for cobol runtime licensing of upgraded systems and multiple
SunSystems installations.
F Note: The SunSystems version number is printed on the labels of the issue
media. It is also displayed on the SunSystems main screen.
BEFORE YOU UPGRADE

In preparation for your upgrade, you should carry out the following procedures:
1 Carefully read any User Notes supplied with your upgrade to establish whether
any special procedures are required.
2 Post or Hold any current journals in Ledger Accounting.
3 Import and post all outstanding SunBusiness transactions using the SunAccount
function JI=Journal Import.
Upgrading SunSystems 21
4 If possible, try to co-ordinate the upgrade with a PC=Period Cleardown, so
that your table sizes are minimised.
5 If you want to retain the demonstration databases supplied with version 4.1 or
previous versions of SunSystems, you must rename DEM, DM1, and DM2
before upgrading.
6 Take a full security copy of your current SunSystems program files with a full
operating system backup.
7 Take a full security copy of your current database using Oracle backup facilities.
8 Use the SunSystems FB=File Backup/Restore option to make a separate backup
of all your current SunSystems data files (see the subsection File Backup/Restore
for full instructions).
9 Drop all objects in the SUN schema. If you want to retain your existing database
configuration, do not run the createdb.sh script, but run the script dbuser.sql
using Server Manager, after appropriately editing it. You may, however, wish
to take the opportunity to reconfigure your database. In this case you should
delete the entire SunSystems database and use the createdb.sh script to
rebuild it from scratch.
You must edit the script files run by createdb.sh before executing them. See
the section Installing SunSystems.
F Note: Make sure that the network user who performs the SunSystems restore
in FB=File Backup/Restore has sufficient privilege to read the backup files.
Log in as the same user, or amend the permissions on the backup directory.
File Backup/Restore
Apart from your own security backup of SunSystems files, you must use the
SunSystems FB=File Backup/Restore function to make a separate backup of your
data tables. This converts the data tables to text files, which can be upgraded
when you restore them. You need to complete the following steps:
1 With the old version of the software, use FB=File Backup/Restore to backup
all tables for each database code. Remember to backup all budget, archive,
and install tables, plus the report format and document format files. The last
three are offered if you enter spaces when prompted for a database code.
F Note: You only need to backup the SSFORMAT and SSREPORT files if you
have created your own formats with Document Definition or Report
Definition. If you use the standard document and report formats supplied
with the system, you can use the SSFORMAT and SSREPORT files provided
with version 4.2.

2 To save the formats you have created, you may prefer to use the Transfer Out
option in the old version of DD=Document Definition or RD=Report Definition.
This saves your formats as .FMT or .REP files. Once the new version of the
software is loaded you can use Transfer In to import your formats.
F Note: Document formats which have been programmed specially for you
(bespoke formatters) are not held in the document format file and must be
recompiled before you can upgrade. Contact your supplier for further
details.
3 Save any of the supplied programs which you have tailored yourself (e.g.
sunspool). Refer to your supplier for more information.
4 Delete all the old program files from your program directory. If you are updating
SunSystems, make sure you have taken copies of any .MDF files containing
FREEFORMAT macros, and .TLF files for transfer layouts used in LX=Ledger
Export. However, the upgrade may require some alterations to your macros
before they perform correctly.
F Note: It is not possible to restore from backups made using the multi-volume
backup function BM in older versions of the software. You must make a
single volume backup of each file. Refer to your supplier.
INSTALLING THE NEW VERSION OF SUNSYSTEMS
You are now ready to load the new SunSystems 4.2.6 program files. It is advisable
to install version 4.2.6 into a new directory and to delete all the old program files
from the previous SunSystems program directory.
If you specify the same program directory as your previous version the installation
procedure overwrites all the files of the same name.
The installation process is fully automated, as detailed in the section Installing
SunSystems. You are strongly recommended to load the demonstration databases
when prompted, as these have been rewritten for version 4.2.6 and are designed to
help you familiarise yourself with the new functionality.
As tables may have changed between versions, all objects in the existing
SunSystems database must be deleted. The simplest way to do this is to drop all
objects in the USERS tablespace, then restore them using the instructions in the
subsection Restoring Data Tables.
F Note: If you want to convert ledger export, bank reconciliation or verification

rules data to the process manager formats, you must use BC=Business
Conversion. For more details see SunSystems User Note Version 4.2.6.
Warning: Decimal and Thousand Separators in JP=Journal Presets
If the following conditions apply, you should read the instructions in this subsection
carefully:
• You are upgrading from version 4.1.2b or 4.1.4
• You are using ‘.’ full stop/period as a thousand separator and ‘,’ comma as a
decimal separator in JP=Journal Presets.
Having followed the upgrade procedure, you must perform the following steps
before you restore your data files:
1 Using FB=File Backup/Restore, select Restore and leave the Database Code
box blank. Enter Y-Yes to restore the installation file, report format file and
data dictionary file. You must now exit and restart SunSystems.
2 If you have the Multi-Lingual module, choose LD=Language Definitions and
Examine the Language Code associated with this operator. You can check
OD=Operator Definitions if you are uncertain which language to view. Make
a note of the entries in the Decimal and Thousand Separator boxes, and Amend
both boxes to blank.
3 In DB=Database Definitions, Examine each Database Code. Make a note of
the entries in the Decimal and Thousand Separator boxes, then Amend the
Decimal Separator to ‘.’ full stop/period, and the Thousand Separator to ‘,’
comma.
4 You can now return to FB=File Backup/Restore and continue restoring your
data files. When they are all restored, use DB=Database Definitions and
LD=Language Definitions and return the Decimal and Thousand Separator
boxes to their original settings.
RESTORING SUNSYSTEMS DATA TABLES
Once version 4.2.6 is loaded and you have created the SunSystems Oracle database
(or dropped all objects in the SUN schema if you are retaining your database
configuration), you can begin to restore your data. Because of the changes in
version 4.2.6, there are several considerations concerning the demonstration
databases and your report and document formats. You need to complete the
following steps:
1 Log in to SunSystems version 4.2.6 as SuperUser SUN. A warning message is
displayed. Refer to the instructions in the section Logging in to SunSystems to
create a default installation table.
2 In DB=Database Definitions amend the default database definition record (this
has a blank database code) so that it points to your old backup directory.

3 Go to FB=File Backup/Restore. Leave the database code blank and Restore
your install file.
4 Exit SunSystems and log in again as your usual operator Id.
5 Go to FB=File Backup/Restore. Leave the database code blank and Restore
your report format file.
6 Go to FB=File Backup/Restore. Enter your first database code and Restore
your reference table.
7 Go to FB=File Backup/Restore. Enter your first database code and Restore the
remaining tables.
Repeat steps 6 and 7 until all your databases are restored.
Multi-Lingual users: When restoring from foreign language databases, the base
language of the operator Id who runs the restore procedure must be the same as
the language held in the database. In other words, if you are restoring French
database files, the base language of the operator Id running the restore must also
be French.
Restoring the Installation Table

The installation table contains all the new SunSystems version 4.2.6 reference
data such as operator records, permissions, printer setups, and database definitions.
From version 4.2.6 you can use the Transfer option to copy some of the SunSystems
reference records. Before you restore your own installation table, you must install
the demonstration installation table as this contains the user hooks required for
Process Manager and additional functionality such as Standard Descriptions in
Ledger Accounting. Then use Restore Append to restore your original SSINSTAL
table.
The DB=Database Definitions settings are particularly important, since these
records point to the directories where the backup files are stored. You must amend
the default database definition record to identify where your own SSINSTAL.BAK
is held.
When you restore your copy of the installation table the analysis category lengths
previously located in your database definition records are written to the new data
dictionary file SSDDICTY. The data dictionary file is used by RD=Report
Definition. This is only applicable if upgrading from version 4.1 to 4.2.
You should be aware that the analysis lengths for the version 4.2.6 demonstration
databases overwrite any previous records you may have for databases called DEM,
DM1, and DM2. If you want to retain your previous version of the databases
DEM, DM1, or DM2, you have to rename them before upgrading.
If you are upgrading from a version prior to version 4.0 then your old ID=Installation
Data records are used to create the default DB=Database Definitions and
OD=Operator Definitions records.
See the Reference Manuals for further information about SunSystems reference
functions.
Restoring the Report Format File

From version 4.2.6 the DD=Document Definition function has been absorbed into
the RD=Report Definition function. To save the document formats you have
previously created you should retain your backed up SSFORMAT and SSREPORT
files and restore them once the new version is installed. The functionality provided
by DD=Document Definition is available through RD=Report Definition.
When you restore your report format file into version 4.2.6 you have the option to
include and convert your old document formats as well. The system first checks
for an SSREPORT.BAK file in 4.1 format, and also an SSFORMAT.BAK file.
Assuming you previously used the document formats to produce SunAccount or
SunBusiness documents, you should confirm that you want to include them.
The SSREPORT file supplied with version 4.2.6 provides a range of example
report and document formats. These provide more efficient formats for standard
reports such as JL=Journal Listing, as well as examples of the new reports available
via RD=Report Definition.
Document formats which have been programmed specially for you (bespoke
formatters) are not held in the document format file and must be amended before
you can upgrade. Please refer to your supplier.
Budget Tables
The budget tables are not offered for restoration until the reference data for that
database has been restored. If you have upgraded from a version prior to version
2.4.4, you must create a BD=Budget Definitions record before you can restore
your budget tables.
F Note: If you use the Transfer option in reference functions, to import or

export reference records to or from other software, you should note that
the record layouts have changed with version 4.2. Further details can be
obtained from your supplier.
Journal Hold Table

If you are upgrading from a version prior to version 3.5, you must use FC=File
Creation to create a journal hold table, before you can use any of your restored
data.
FreeFormat Macros
FREEFORMAT macros, held in .MDF files, are not necessarily upwards compatible.
The commands required to carry out a function automatically may change as new
options are added to SunSystems. You should check your macros when upgrading
and edit them as necessary.
A copy of the file SSISSUE.MDF is supplied SunSystems. This file contains
FREEFORMAT macros designed to work with the 4.2.6 demonstration databases,
including the macros linked to OB=Operator Buttons. When you access
FREEFORMAT, SunSystems searches for a file called STANDARD.MDF; if none is
found then the contents of SSISSUE.MDF are copied into a new STANDARD.MDF.
When you are upgrading, your existing STANDARD.MDF is not overwritten. Should
you wish to use the latest macros in SSISSUE.MDF you must manually append
the contents to your STANDARD.MDF.
For further information about the FREEFORMAT macro tool see the SunSystems
Reference Manuals.
Operator Permissions
In SunSystems version 4.2, the function OP=Operator Permissions has changed
considerably from versions prior to 4.1. Each operator Id now belongs to an
Operator Group. SunSystems is issued with a default group defined as ‘ ’ space.
This group has no restrictions, so members of this group can access all functions
and all types of data.
Operator Ids who have no previous restrictions are automatically added to the
default permissions group. Their Operator Group is set to ‘ ’ space. These operators
still have no restrictions.
Operator Ids which did have permissions defined are handled as follows:
The operator Id is added to an Operator Group with the same three character code
as the operator Id. This new Operator Group is created automatically. The new
Operator Group retains the same permissions and includes all the databases to
which that operator previously had access.
In version 4.2 operator permissions previously applied to DD=Document Definition
are transferred to RD=Report Definition. If an operator did not have permission
to use DD=Document Definition, he will not be permitted to access RD=Report
Definition after the upgrade.
F Note: New functions in version 4.2 have no access restrictions imposed.

For more information about OP=Operator Permissions, please refer to the sections
Operator Permissions and Data Access Groups in the SunSystems Reference
Manuals.
Chart of Accounts and Item Records
When you upgrade from version 4.0.1 or earlier, you have the option to move the
data stored as Comments to two new boxes. This affects the function CA=Chart
of Accounts where data can be moved to the Tax Code box. A similar feature is
available in SunBusiness. The previous entry in IR=Item Records in the Comments
Box can be moved to Commodity Code.
When you use FB=File Backup/Restore to restore your reference tables, a message
appears, for example:
UPDATE CHART OF ACCOUNTS TAX CODE FROM EXISTING COMMENTS FIELD (Y/N)?
Enter Y-Yes to move your data or N-No to leave the records as they are.
Report Definition
In SunSystems 4.2, Report Definition now processes Ledger Transaction Financial
and Other Amounts as signed numeric values for all Report Types and in all
circumstances, therefore debits will be negative. You should review any upgraded
Report Formats and amend them to cater for this change, although this is only
necessary where dealing with Ledger Transaction Financial and Other Amounts
as subjects of comparative statements.

Files and Directories
This section describes the main files which comprise SunSystems, and where they
should be located. See Appendix B: Filenames for a full listing of files and their
descriptions.
PROGRAM FILES
SunSystems program files are loaded into a single directory known as the
SunSystems program directory. Before starting the installation you must decide
on the location of the program directory. Throughout this manual the program
directory is referred to as $SUNDIR.
OTHER FILES
System File
The system file SSSYSTEM.DAT must be located in the SunSystems program
directory. It contains information regarding the following:
• The SunSystems serial number assigned to your company
• The modules you are licensed to use
• The number of users who can simultaneously log in to SunSystems
• Your company name
• The operating system you are running on.
Dictionary and Report Files

The report format files are called SSREPORT and SSREPORT.idx; the data
dictionary files are called SSDDICTY and SSDDICTY.idx. Both pairs of files
are used by the function RD=Report Definition. The data dictionary files also
contain your NL=Analysis Length records.
Files and Directories 29

All of these files are, by default, held in the $SUNDIR directory. If you want to
keep them elsewhere, edit the SUN.INI file and add your chosen directory after
the sysdata entry. An example of SUN.INI is provided in the section Using
SUN.INI.
Data Tables
Reference Data
The reference tables contain the chart of accounts, asset details, item records,
analysis codes, conversion records, and other information entered from the reference
functions. A full list of reference functions is provided in the section Actions in
the SunSystems Reference Manuals.
Ledger Data
The ledger table contains the active SunAccount transactions (i.e. transactions
which have not been cleared down). Other SunAccount data is also stored in the
journal hold table, the budget tables and archive tables. The ledger table is used
by all three SunAccount modules: Ledger Accounting, the Fixed Asset Register,
and Corporate Allocations.
Sales Order Data

The sales order and sales order history tables contain all the transactions entered
in the Sales Order Processing module in SunBusiness.
Purchase Order Data

The purchase order and purchase order history tables contain all the transactions
entered in the Purchase Order Processing module in SunBusiness.
Inventory Control Data

Inventory movements and stock take details in SunBusiness are held in the
movement table.
Backup Files
SunSystems has its own FB=File Backup/Restore function. This option allows
you to take a backup copy of the data tables. The SunSystems FB=File Backup/
Restore facility creates an ASCII text file which can be examined with a word
processor or text editor.

FB=File Backup/Restore is often used in non-SQL versions of SunSystems for
day-to-day backup of data files. In SQL versions it is used only for upgrading to
a new version of SunSystems. It must be used when upgrading. See the section
Upgrading SunSystems.
For a regular backup strategy the Oracle and UNIX backup facilities are more
appropriate and much faster than using the SunSystems FB=File Backup/Restore
function. See your Oracle documentation for more information on backing up
your database.
The backup files should be located in an exclusive directory, so that they can be
distinguished from other files.
Stored Report Files

Whenever you choose to print a report in SunSystems, you are offered the option
to Print Report or Store on Disk. When a report is stored on disk, a print file is
written to the directory/drive specified in OD=Operator Definitions and/or
DB=Database Definitions. Reports can also be spooled, and the spooled files are
also written to this directory.
Having stored a report on disk, several options are available for displaying or
printing it later. These are described in the section Printing from SunSystems.
The print files should be located in an exclusive directory. This makes it easier to
monitor the age, number, and size of print files.
Work Files
Work files are, by definition, temporary files which are deleted and re-created as
necessary. Certain work files are deleted when the application terminates or when
a similar file is required again. If, for any reason, SunSystems shuts down
abnormally, you are advised to delete all the work files.
The work files should be located in an exclusive directory because they are then
easier to monitor; the default is $SUNDIR/work. Before upgrading to a new
version of SunSystems you must delete all remaining work files. The SunSystems
function OD=Operator Definitions allows you to specify individual work file
directories for each of your operators.
Other work files are created when an operator logs in, and are subsequently deleted
when they log out. These are used by FREEFORMAT macros (SSWM files), and also
the QUERY tool (SSWN files) in SunSystems. These work files are stored by default
in the program directory.
Files and Directories 31

If your users do not have delete permissions, you may find these work files
accumulate, and have to be deleted by the system administrator. To avoid this,
you can specify a separate directory for these types of work files using SUN.INI.
See the section Using SUN.INI for further information.
Changing Locations of Directories

You may consider having separate locations for sensitive databases to enhance
database security. See the section Security in the Appreciation Guides.
The installation script install.sun creates work, print and backup directories.
The path names therefore are:
$SUNDIR/work
$SUNDIR/print
$SUNDIR/back
You can change these path names, but these divisions are recommended for ease
of maintenance. See the subsection Specifying the Location of Print, Work, and
Backup Files in the section Running SunSystems for further information.

Using SUN.INI
You are advised to make use of a SUN.INI file which is located in the program
directory. The following extract is taken from the SUN.INI supplied with
SunSystems:
[SUNSYSTEMS INITIALISATION]
sysdata=
syswork=
Please note the following:
• Data in [ ] square brackets is for information only
• The sysdata line indicates where the report format file SSREPORT and the
data dictionary file SSDDICTY are held
• The syswork line indicates where the temporary work files SSWM-xxx and
SSWN-xxx (where xxx is the operator Id) are held. These files are used by
the FREEFORMAT and QUERY facility
• The directory path names can be a maximum of ten characters in length.
Example:
From the $SUNDIR directory, type:
mkdir sysdata syswork
chmod 777 sysdata syswork
Then edit SUN.INI to read:
sysdata=./sysdata/
syswork=./syswork/
Using SUN.INI 33
Running SunSystems
SunSystems is started by typing the following command:

SUN
This is a short shell script which was optionally placed by the install.sun
script in /usr/bin. You can edit it if necessary using an editor such as vi.
Assuming directory /home/sun426 is used, its contents will be:
NLS_SORT=BINARY # Do NOT change this!
# Set ONE of the following, depending on your installation:
Oracle 8.1.7.2 or above
Note 1
# NLS_LANG="ENGLISH_UNITED KINGDOM.WE8ISO8859P1"
# NLS_LANG=DANISH_DENMARK.WE8ISO8859P1
# NLS_LANG=DUTCH_THE NETHERLANDS.WE8ISO8859P1
# NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
# NLS_LANG=FINNISH_FINLAND.WE8ISO8859P1
# NLS_LANG=FRENCH_FRANCE.WE8ISO8859P1
# NLS_LANG=GERMAN_GERMANY.WE8ISO8859P1
# NLS_LANG=ITALIAN_ITALY.WE8ISO8859P1
# NLS_LANG=NORWEGIAN_NORWAY.WE8ISO8859P1
# NLS_LANG=PORTUGUESE_PORTUGAL.WE8ISO8859P1
# NLS_LANG=SPANISH_SPAIN.WE8ISO8859P1
# NLS_LANG=SWEDISH_SWEDEN.WE8ISO8859P1
# NLS_LANG=JAPANESE_JAPAN.JA16SJIS
Oracle 9.2.0.3.0 or above
#NLS_LANG="ENGLISH_UNITED KINGDOM.WE8MSWIN1252" Note 1
# NLS_LANG=DANISH_DENMARK.WE8MSWIN1252
# NLS_LANG="DUTCH_THE NETHERLANDS.WE8MSWIN1252"
# NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
# NLS_LANG=FINNISH_FINLAND.WE8MSWIN1252
# NLS_LANG=FRENCH_FRANCE.WE8MSWIN1252
# NLS_LANG=GERMAN_GERMANY.WE8MSWIN1252
# NLS_LANG=ITALIAN_ITALY.WE8MSWIN1252
# NLS_LANG=NORWEGIAN_NORWAY.WE8MSWIN1252
# NLS_LANG=PORTUGUESE_PORTUGAL.WE8MSWIN1252
# NLS_LANG=SPANISH_SPAIN.WE8MSWIN1252
# NLS_LANG=SWEDISH_SWEDEN.WE8MSWIN1252
# NLS_LANG=JAPANESE_JAPAN.JA16SJIS
# NLS_LANG="SIMPLIFIED CHINESE_CHINA.ZHS16GBK"
# NLS_LANG="TRADITIONAL CHINESE_CHINA.ZHT16BIG5"

stty cs8 -istrip
ORACLE_HOME=/home/oracle
ORACLE_SID=SUNSYS
SUNDIR=/home/sun426
Note 2
COBDIR=$SUNDIR/lib/cobol
LD_LIBRARY_PATH=$COBDIR Note 3
Note 10
LD_LIBRARY_PATH_64=$COBDIR/lib
LIBPATH=$COBDIR/lib Note 3
SHLIB_PATH=$COBDIR/lib Note 3
COBTERMINFO=$SUNDIR/lib/terminfo Note 4
COBSW=-iFl0+B Note 5
dd_lp=”>/usr/bin/lp -s” Note 6
dd_ls=”<$SUNDIR/ssls.sh” Note 7
dd_data=$SUNDIR/data/ Note 8
dd_work=$SUNDIR/work/
dd_back=$SUNDIR/back/dd_print=$SUNDIR/print/
export NLS_SORT NLS_LANG ORACLE_HOME ORACLE_SID

SUNDIR COBSW COBDIR LD_LIBRARY_COBTERMINFO dd_lp
dd_ls dd_data dd_work dd_back dd_print
umask 000 Note 9
cd $SUNDIR
./SSMM $*
Note 1: NLS is Oracle National Language Support. See your Oracle
documentation for more information on this.
Note 2: The environment variable COBDIR tells the COBOL Run Time
System (RTS) where to find screen configuration files (COBOL ADIS files)
and the cobkeymp it needs for mapping the terminal and keyboard.
Note 3: LD_LIBRARY PATH is only required for SCOUNIX or SVR4-
based platforms. LIBPATH is only required for AIX. SHLIB_PATH is
only required for HP-UX.
Note 4: Information about the COBTERMINFO variable is provided in the
subsection Configuring the Terminal Display.
Note 5: The COBSW (COBOL Switch) environment variable controls the
COBOL programs as follows: -i stops keyboard interrupts; -F allows
intermediate code compatibility; l0 frees memory when exiting a program;
and + B allows non-database records to be read even if they are
simultaneously being updated.
Running SunSystems 35
Note 6: The lp command and dd_lp variable are covered in the section
Printing from SunSystems.
Note 7: The ssls.sh script is called whenever an ‘*’ asterisk is entered
in VR=View Stored Report.
Note 8: This dd_ method of accessing data directories allows path names
of more than 10 characters in length and is set up automatically on loading
the system.
Note 9: Recommended file permissions are provided in the section File
Permissions and Ownership.
Note 10: LD_LIBRARY_PATH_64 is required for 64-bit SUR4-based
platforms used for Oracle 9i releases of SunSystems.
SPECIFYING THE LOCATION OF PRINT, WORK AND BACKUP

FILES
When you install SunSystems, the directories print, work and back are created
beneath the $SUNDIR. These are the default directories for print files, work files
and backup files respectively. However, if you anticipate having large files in any
of these directories, you may want to divide them between different UNIX
partitions. The locations for the backup files can be entered in DB=Database
Definitions, and the locations for the print and work files can be entered in
OD=Operator Definitions with SunSystems.
In both these functions, you must enter the directory path either as an absolute
pathname or as a relative pathname. SunSystems limits you to a ten character
specification.
Mapping Directories Using dd_

Rather than entering the UNIX path within SunSystems, it is possible to define a
variable which can then be added to the sun script with a dd_ prefix. This allows
you an eighteen character specification.
This method is the same for print, work and backup files.
Example
The work files for user U1 are to be stored in /home1/sunwork and the work
files for user U2 are to be stored in /home2/sunwork.
Within the SunSystems function OP=Operator Definitions for operator U1 enter:
Work File Drive <wrk1/ >

and for operator U2 enter
Work File Drive <wrk2/ >
Then edit the sun script and include the lines:
dd_wrk1=/home1/sunwork/
export dd_wrk1
dd_wrk2=/home2/sunwork/
export dd_wrk2
The ‘/’ at the end of the specification is essential.
The same procedure can be used for mapping print file drives with OD=Operator
Definitions and backup file drives within DB=Database Definitions.
Any identifier can be used for the dd_ variable, except ls, which already exists
for use within VR=View Stored Report. Also make sure that the identifiers do not
clash with those used for printing; see the section Printing from SunSystems.
CONFIGURING THE TERMINAL DISPLAY
This subsection describes the process of configuring the system so that it gives the
correct instructions to display data on the screen.
The COBOL Run Time System (RTS) must recognise the particular CRT (video
screen) being used. The RTS must be able to use terminal capabilities such as
cursor addressing and highlighting, the terminal control strings for which vary
greatly from one terminal type to another.
The RTS has been written so that it may be used with a minimum of special action
to interface with the specific terminal being used. The terminal type is established
from the TERM environment variable, which in turn should be established by the
shell during the login process.
Screen Configuration
A terminfo database directory is supplied with SunSystems. $SUNDIR/lib/
terminfo is accessed via the COBTERMINFO variable in the $SUNDIR/bin/
SUN script. The structure is the same as the UNIX /usr/lib/terminfo, but
the entries it contains have been specially compiled to work with SunSystems
graphical interface. To change the TERM environment variable, type:
TERM=vt100
export TERM
This causes SunSystems to look for an entry:
$SUNDIR/lib/terminfo/v/vt100
Appendix F: terminfo provides further information on building terminfo
emulation files, and lists the entries needed for a SunSystems interface. In addition,
the file $SUNDIR/lib/terminfo/terminfo.sun contains the source listing
for each supplied entry.
The SunSystems function TD=Terminal Definitions allows you to mix colour and
monochrome terminals and also to use terminals of different line and column
lengths. The number of lines displayed for the default terminal is 24 (the default
terminal code is set to ‘ ’ space). Setting the number of lines to 25 displays messages
to the terminal without overwriting the selection text and is therefore recommended
for terminals which can support this feature.
Whichever you choose, it is important that the following three variables coincide:
• Number of lines in the terminal setup (usually altered by pressing the SETUP
key or the SHIFT and SELECT keys)
• The lines# field in the compiled terminfo entry (which must be either lines#24
or lines#25). Appendix F: terminfo gives more information on how to alter
terminfo files
• The entry you make in the box lines (24/25) within TD=Terminal Definitions.
If these do not coincide, you may find that your terminal display constantly omits
the top line and the screen text becomes garbled.
CONFIGURING THE KEYBOARD
The values sent by keyboard function keys differ depending on the personality or
emulation of the terminal. A selection of the most commonly used terminal
emulations and the associated function key values is provided with SunSystems
and SunQuery. However, if a function key is not responding within either package,
the following information will help you with the configuration.
Some function keys are preset by the hardware and used by the operating system.
These keys cannot be used by SunSystems. Other keys have no value strings
attached to them and similarly can not be used by a software package. If you are
using a PC emulation package to connect to UNIX, consult your emulation
documentation to ensure the keyboard is configured correctly.
Before trying to map a function key for use within SunSystems, make sure it
sends out an escape sequence at the UNIX prompt. This normally begins with a
^[ escape sequence followed by a string. For example, when using an ANSI
emulation, pressing F1 ENTER should result in the message:
^[[M: not found

Mapping System Function Keys
COBOL provides a facility, keybcf, which allows user function keys to be
configured. This is accessed by running the file $SUNDIR/bin/keybcf.sun
provided with SunSystems.
The following table lists SunSystems special characters, their meanings, and the
function key value within keybcf.
SunSystems Usage Key Number keybcf Function Default Key Used
Escape 0 Esc
Help? 1 F1
Lookup = 2 F2
Duplicate. 3 F3
FreeFormat\ 4 F4
Query& 5 F5
Shorthand~ 6 F6
Duplicate to end: 7 F7
Calculator@ 8 F8
Context 9 F9
Action bar 10 F10
Down line/null accept 13 DownArrow
Backtab 14 UpArrow
Left arrow 15 LeftArrow
Right arrow 16 RightArrow
Page up 17 PageUp
Page down 18 PageDown
Insert Turn On Insert Mode
at screen level
Ctrl-T Toggle between Insert
and Overstrike at
the screen level
Running keybcf.sun
When you use keybcf.sun, you are presented with the keyboard configuration
menu. The keybcf.sun menu screen shows you:
The file which holds the keyboard mapping is:
/home/sun426/lib/cobol/cobkeymp
You are provided with the following options:
Amend the existing keyboard mapping file
Create a new keyboard mapping file
Retrieve and amend the issue keyboard mapping file
Enter number of option required (1-3) or x to exit:
Option 1: Amend the existing keyboard mapping file

This option allows you to amend the current $SUNDIR/lib/cobol/cobkeymp
file. Before amending it, a copy is saved as cobkeymp.iss, if such a file does
not exist.
Option 2: Create a new keyboard mapping file

This option moves the current $SUNDIR/lib/cobol/cobkeymp file to
cobkeymp.iss (unless it already exists). A new cobkeymp file is created
when save is requested from within keybcf.
Option 3: Retrieve and amend the issue keyboard mapping file

This option copies the file $SUNDIR/lib/cobol/cobkeymp.iss to
$SUNDIR/lib/cobol/cobkeymp. This option should be chosen only after
option 1 or 2.

Logging in to SunSystems
When you access SunSystems, the login screen is displayed.

You are asked for some, or all, of the following:
• Your operator Id and password.
• The date.
The first time you log in to SunSystems, you must log in as SuperUser SUN with
the password you defined when editing the dbbuild.sql script, and then create
the installation table.
1 Create the Installation table. At the bottom of the screen, the following message
appears:
DEFAULT DATABASE RECORD NOT FOUND
2 Press ENTER and the following message is displayed:
PRESS ENTER TO RETRY OR CANCEL TO EXIT SYSTEM.
3 Enter Z at the next prompt followed by Y to create the installation table.
4 Create an OD=Operator Definitions record for the operator SUN with a
password of your choice.
F Note: If you are upgrading and have not run the createdb.sh script as
described in the section Upgrading SunSystems, then manually create the
SUN operator with the same password used in your SunSystems database.
5 Create the SunSystems database DEM using FC=File Creation.
You can now create your own SunSystems databases using the FC=File Creation
function within SunSystems.
SunSystems creates files as Oracle tables with default storage parameters. If you
need to customise these tables based on your data volume before using R-Restore
in the SunSystems FB=File Backup/Restore function, follow the instructions below:
svrmgrl
connect sun/sunsys
select * from user_tables;
Logging in to SunSystems 41
Check the sizes; you can change the storage parameters of the tables to suit your
requirements. See the section Installing SunSystems, subsection Runnning Oracle
Scripts for more information on changing storage parameters.
F Note: Although you can use Restore to create tables, if you do not first
create the reference tables using FC=File Creation, then the SunBusiness
transfer tables are not created.
See the section Running SunSystems for information on configuring your display
and keyboard.
You should read the following sections of the Reference Manuals for information
on important areas involved in the initial setup of SunSystems:
• Operator Definitions. Describes how to set up OD=Operator Definitions, their
passwords, location of print and work files, etc.
• File Creation. Enables you to create the necessary data tables for a new database
• Terminal Definitions. Enables you to define your terminal type, the colours
you wish to use, etc.
• Printer Definitions. Enables you to define the printer configurations you use.
This option is associated with CS=Control Sequence Definitions
• Operator Permissions. Enables you to apply various levels of security to your
databases, in conjunction with DA=Data Access Groups.
Serialisation
If you are installing SunSystems for the first time, you need to serialise the software
in order to access each of the SunSystems modules. If your system has not been
serialised, the function FB=File Backup/Restore is limited. Only the reference
file is offered for processing.
You may not need to serialise if you have only requested a demonstration copy of
SunSystems. This allows you to experiment with all modules, but restricts the
dates you can enter and prohibits you from creating new databases. If you are
licensed to use SunSystems, you will have full access to those SunSystems modules
that you ordered, as well as the demonstration database.
The instructions for serialisation are provided with the issue media. Having typed
SUN from the appropriate directory, you are prompted for an operator Id. Type
sun to log in as SuperUser SUN with the password specified in the script file
dbbuild.sql, accept the default date by pressing ENTER, and then type ZS
followed by ENTER.

This takes you to the serialisation screen, which is reproduced in your serialisation
details. Enter the codes in the corresponding boxes. You should take care with
upper and lower case.
If the serialisation is successful you are prompted to exit and re-enter SunSystems.
If not, contact your supplier for further advice.
Logging in to SunSystems 43
File Permissions and
Ownership
The SunSystems installation script gives full permissions (chmod 777) to all
files and subdirectories beneath the $SUNDIR directory. This does not include
the program files (.so) which should remain read only. Individual file permissions,
their owners and groups can be changed to reflect your own system security and
user structure.
All files need read permission for each UNIX user who intends to use SunSystems;
the files SSMM and ssls.sh need execute permission, and the following files
and directories need write permission:
SSREPORT
SSREPORT.idx
SSSYSTEM.DAT
*.MDF (FREEFORMAT macros)
$SUNDIR/work
$SUNDIR/print
$SUNDIR/back
all database files (held by default in $SUNDIR/oradata/dbs)
The data dictionary files SSDDICTY and SSDDICTY.idx should remain read
only.
The installation script also contains the command umask 000. This ensures that
files created which may be needed by others users (transfer files, for example), are
given write permission.
However, some work files are indexed sequentially and can only be created with
the permissions rw-rw-r--. This is a restriction of the C-ISAM used by the
UNIX operating system to create indexed sequential files.
For this reason, we recommend that all SunSystems users are a member of the
same UNIX group.
For general information on the creation of user and group accounts and privileges,
and on altering file permissions, consult your UNIX documentation.

SunSystems Graphical Client
SunSystems Graphical Client provides an MS Windows graphical user interface

(GUI) for SunSystems running on a UNIX host.
The Graphical Client uses the TCP/IP and Micro Focus CCI protocols. These
protocols allow the presentation layer on your PC to connect to the application
and database layers on your host UNIX machine.
SunSystems can be accessed simultaneously by character-based terminals as well
as PCs running the Graphical Client software. This allows a choice of interface.
F Note: If you intend using the Business Analyser facility you must use
Graphical Client as it does not work on character-based terminals.
Before You Begin

Before you install the SunSystems Graphical Client, you must ensure that
SunSystems has been installed on the UNIX host, and is fully operational. See the
section Installing SunSystems for full details.
CLIENT HARDWARE REQUIREMENTS
You need approximately 5Mb of free disk space and at least an additional 8Mb of
RAM on each PC.
CLIENT SOFTWARE REQUIREMENTS
Your PC can be running Windows NT Workstation 4.0, or Windows9x, and should

have TCP/IP connected to a UNIX machine. Check this by accessing the host via
the telnet or ping command.
On Windows NT 4.0 and Windows 9x, Microsoft TCP/IP-32 is recommended.
F Note: Your PC must have Internet Explorer 4.0 (or later) installed if you
want to use Business Analyser.
SunSystems Graphical Client 45

PREPARING THE HOST ENVIRONMENT
Before you can install SunSystems Graphical Client you must ensure that the
UNIX host has been configured to enable communications between the PC and
the host.
The Systems Administrator must perform the following tasks:
• Check that the /etc/services file includes the line
mfcobol 86/udp
F Note: This line should have been inserted automatically by the installation
script, if it was not already present.
• Run the script $SUNDIR/bin/suncci. This loads the files ccitcp2 and
SSMASTER into memory as background processes using the nohup command.
F Note: The installation script can set this to run automatically whenever the
machine is rebooted.
F Note: All files created on the host via the Graphical Client take their
ownership from SSMASTER, which is the Oracle user by default.
INSTALLING SUNSYSTEMS GRAPHICAL CLIENT
This section describes the installation procedures for Windows NT, and Windows
9x.
First, you must ensure that the IP address of the UNIX host and its name are
defined in the HOSTS file on your PC. This file is located in the TCP/IP home
directory.
A typical entry would read:
unixbox 129.153.162.16
Alternatively, you must ensure that the host name can be resolved by your particular
method of names resolution, for example DNS.
Running the Installation Program

If you are using Windows 9x or NT 4.0 the installation process should begin
automatically. If it does not then, from the taskbar, click Start, and Run, and enter
the following command:
d:\setup
(where d is the drive letter of the CD drive) and click OK.

You are asked to specify the directory into which the programs will be installed.
The directory is created if it does not already exist.
You are prompted to install the online help files. If you choose Yes the files are
copied to the SunSystems program directory.
Once the files have been copied onto the PC, you are asked to enter the host name
and your name, as defined in the UNIX /etc/hosts file.
The entries are written to a file called CCI.INI in your Windows directory,
usually C:\WINDOWS or C:\WINNT
F Note: Refer to Appendix G: Enabling Business Analyser for details on

configuring Graphical Client for use with Business Analyser.
RUNNING SUNSYSTEMS GRAPHICAL CLIENT
Edit the file SUN.INI in your graphical client directory and add the line
sun=</directory name>/SUN
where directory name is the equivalent of $SUNDIR/bin. For example:
sun=/home/sun426/bin/SUN
If you chose to copy the sun script to /usr/bin the path name should be
sun=/usr/bin/SUN
When complete, you can test that your installation has been successful by loading
and running SunSystems.
Once the software is installed, click the SunSystems icon, or select it from the
taskbar in Windows. There may be a delay of a few seconds while the connection
is made.
Running Multi-Sessions
A maximum of nine sessions of SunSystems Graphical Client can be run
concurrently on each PC.
F Note: The number of concurrent sessions is restricted by memory usage

and licence numbers.
Printing
All SunSystems files created via the Graphical Client are placed on the host. For
this reason, all .PRN files requested for printing are sent to the UNIX spooler and
not to a printer attached to the PC. See the section Printing from SunSystems.

FreeFormat
Any FREEFORMAT macros are written to a .MDF file on the PC. Since the interfaces
are different, FREEFORMAT macros created on the PC may not work via the character-
based version and vice versa.
TROUBLESHOOTING GUIDE
This subsection is designed to help you find solutions to problems you may
encounter with SunSystems Graphical Client.
Is the network responding?
Use telnet or ping to test connection to the host.
Are the daemons SSMASTER and CCITCP2 loaded on the host?
To make sure, at the UNIX prompt use the following command:
$SUNDIR/bin/suwho
The two filenames should be returned, for example:
# suwho
UID PID PPID C STIME TTY TIME CMD
root 11115 1 0 Feb 22 ? 0:03 ./ccitcp2
oracle 11121 11119 0 Feb 22 ? 0:00 ./
SSMASTER
Does the /etc/hosts file include your PC address and name?
To make sure, at the UNIX prompt use the following command:
pg /etc/hosts
Check that it has been edited correctly.
Does the CCI.INI file on the PC contain the correct host name and address?
This file is placed in the directory C:\WINDOWS. Here is an example of CCI.INI:
[ccitcp-base]
CCITCP2=unixbox
name=John Smith
Does the SUN.INI file contain the correct path for the sun script?
There is an option to write to log files on the PC and/or the UNIX host. Edit
SUN.INI and create SSMASTER.INI on the PC and UNIX machine respectively,
to include the following line:

comms-log=Y
Any diagnostic messages are then written to SSMASTER.LOG (on UNIX) and
SUNCLI.LOG (on the PC). Note that this option is designed as a single-user
diagnostic only.
Which users are executing SunSystems via a graphical client?
You can use the following command:
$SUNDIR/bin/suwho
This returns the name and the session number of each instance of SSMM. For
example:
Oracle 13975 13974 0 16:51:35 ttyp3 0:00 ./SSMM JohnSmith-001,Z
If the PC is halted while a session is still in progress it will be necessary to kill the
session on the UNIX machine.
In the above example, the process id 13975 would be killed using the kill
command. Your systems administrator can provide more information about this
command.
When you next enter SunSystems, you must use the hidden function ZC to clear
the operator login. ZC can be selected only from the SunSystems module, and
can be accessed only with the correct OP=Operator Permissions.
Does the client program fail to connect?
Make sure the name of the machine in the /etc/hosts file is the same as the
node name. To check this type:
uname -n
The machine name returned should be the same as in the hosts file.
If you were able to log in previously but now fail to do so, it may be because the
maximum number of processes for the UNIX user has been exceeded. Each
Graphical Client user requires three processes in addition to other processes run
on the UNIX machine by the same user. Consult your systems administrator and
check that the MAXUPROC parameter value is large enough to allow all Graphical
Client users to establish connection.

Printing from SunSystems
This section details the procedures you must follow in order to produce hard copies
of various listing and reports, as well as documents such as invoices, cheques and
statements from SunSystems.
F Note: You should use a PCL printer for producing output from SunSystems.
If you attempt to print to a postscript printer, the output may be truncated.
DISPLAYING STORED REPORTS
SunSystems allows you to store reports using store on disk. This produces a file
rather than sending the report directly to the printer. The method of storing reports
is described in the Reference Manuals section Actions.
The purpose of storing reports is to allow you to display them on the screen before
printing, to check that they are as required, and to allow you to print them later if
the printer is currently in use. You can also edit the reports with a UNIX editor or
a word processing program before printing, thereby including, for example,
footnotes or additional page headings.
Within SunSystems you can view and print stored reports. However, you cannot
change them. Full details of the VR=View Stored Reports function are given in
the Reference Manuals. Other methods of displaying and printing the reports
outside SunSystems are described in the following sections.
PRINTING FROM UNIX
Stored reports are already formatted by the system with page headings and correct
page length. To print them directly use the UNIX spooler lp. It is important to
use this in a multi-user environment since it forms a queue of reports to be printed
when more than one request is made.
lp CAJLP1.PRN
If the print file CAJLP1.PRN is no longer required the command rm CAJLP1.PRN
must be used. Semi-automatic printing can be achieved by editing the SUN file,
and adding this as the last line:
lp print/*.PRN &

When a user logs out of SunSystems all stored reports are printed. The system
may be re-entered immediately, prior to printing the reports, in order to perform
other processing. The reports are printed when the printer is available but the
print files will not be deleted.
See the section Running SunSystems for more information on the SUN file.
For the purpose of these examples, it is assumed that two printers have been
configured within UNIX: a LaserJet printer with the system default known to
UNIX as lp0 and a dot matrix printer known to UNIX as lp1. Within SunSystems
these are known as LA and DM respectively.
The COBOL RTS (Run Time System) looks at a UNIX environment variable to
set up a pipe using the SunSystems printer device name, created in Printer
Definitions. In this case, the written output is piped to the UNIX spooler lp.
In the above example, therefore, the following lines would be entered in the file
$SUNDIR/bin/SUN
dd_la=”>/usr/bin/lp -s”
dd_dm=”>/usr/bin/lp -dlp1 -s”
export dd_la
export dd_dm
The arguments to the lp command used above are -s to suppress printer messages
and -d to specify a printer other than the default. The lp command is usually in
/usr/bin but may be found in a different directory, so consult your UNIX
manuals if in any doubt.
To complete the linking process, within PD=Printer Definitions in SunSystems,
set:
Printer Code < >
Printer Device Name <:la>
This becomes the system default.
Also within Printer Definitions in SunSystems:
Printer Code <dm >
Printer Device Name <:dm>
Note that the printer device names must be preceded by a colon. Also any identifier
can be used for the dd_ variable, except ls (which already exists for use within
VR=View Stored Reports). You should also make sure that they do not clash with
those used for the location of files.
Printing from SunSystems 51

LASERJET PRINTER SETUP
Creating Control Sequences

Printer Command Language (PCL), commonly known as escape sequences, is a
language used to instruct the printer how you want to print (e.g. orientation, fonts,
character spacing, etc.). Many software applications like SunSystems allow you
to specify how you want print.
Note the following typical printer command (to specify landscape orientation):
EC & l # O Printer commands always start with the escape character EC
Printer commands are case sensitive and end with an upper case character, except
when combined. A command received by the printer stays in effect until changed
by a subsequent command.
You define a printer command in SunSystems using the PD=Printer Definitions
and CS=Control Sequence Definitions functions. The control sequences are entered
as a string of numbers. For example, each of the characters in the above example
will be represented by a three digit number:
027 038 108 049 079
F Note: SunSystems 4.2.6 uses the ISO 8859P1 character set so the printer
must also be configured to use this character set, otherwise reports may
not print correctly. See examples below.
By default the printer will treat a Carriage Return (CR) as literally a carriage
return, and a Line Feed (LF) as literally a line feed. This is not how UNIX operates.
In UNIX LF actually means CR+LF so the printer need to be set up accordingly.
See “Correct Line Termination for UNIX” in the examples below.
Combining Printer Commands

There are three steps to combine printer commands and create escape sequences:
1 The first two characters after the EC escape character (represented in
SunSystems as 027) must be the same in all commands that need combining.
2 When combining commands, the representation of the last character in a
command, usually an upper case letter, becomes a lower case letter. The very
last character of a command that ends a sequence is, however, upper case so
the printer recognises that the sequence has ended.
3 Printer commands take effect from left to right so sequences should be
constructed in the order in which the commands should be performed.

This example of a combination of printer commands is taken from the printer
manual:
1. 027 069 Reset
2. 027 038 108 048 079 (111) Orientation Portrait
3. 027 038 108 048 076 (108) Disable Perforation Skip
4. 027 038 108 054 068 (100) 6 Lines per Inch
5. 027 038 108 048 069 (101) 0 Lines Top Margin
6. 027 038 108 054 054 080 (112) 66 Lines per Page
7. 027 038 107 048 083 (115) 10 cpi Courier Typeface
The numbers in brackets are the lower case decimal representations of the character
preceding them. See step number 2 above. Using the same example the escape
sequence is as follows, although there are really three escape sequences here, all
of which start with EC 027.
027 note 1 reset
069
027 note 1 need to start a new one because the second character is not common
(see step 1 above)
038 note 4 these characters are common to all printer commands, so do not
have to be repeated
108 note 4 these characters are common to all printer commands, so do not
have to be repeated
048
111 note 5 the lower case representations are used as we are in mid-escape
sequence
048
sequence
054
sequence
048
sequence

054
054
080 note 6 the upper case representation is used as we are concluding the
sequence for note 2
027 note 3 need to start a new one because note2 was ended with an upper
case character (see note 6)
038
107
048
083 note 6 the upper case representation is used as we are concluding the
sequence for note 2
EXAMPLE CONTROL SEQUENCES FOR HP LASERJET

PRINTERS
These example control sequences are also supplied with the demonstration database
DEM.
The control sequences have not been combined. This makes it easier to change
them within the CS=Control Sequence Definitions screen. They can be combined
if you need to add additional sequences.
F Note: The order in which the sequences are entered on the Control Sequence
Definitions screen is important, as a particular escape sequence may depend
on a previous one.
The Lines per Page box in the Printer Definitions screen specifies how many lines
are printed before SunSystems prints its heading lines. The lines per page specified
by the escape sequences in CS=Control Sequence Definitions determines how
many actual physical lines are printed on a sheet of paper before a page throw
occurs. In order to have the heading lines coincide with the page throw (in other
words, to avoid page slippage) the number of lines specified in PD=Printer
Definitions must correspond to the number of lines specified in the associated
escape sequences.

Portrait Normal
027 069 Reset
027 038 107 050 071 Correct Line Termination for UNIX
027 040 048 078 ISO 8859 P1 Character Set
027 038 108 048 079 Orientation Portrait027 038 108 055 046
055 055 052 053 067 Set VMI (7.7745)
027 038 108 054 054 070 Text Length (66 Lines)
Enter these numbers in the CS=Control Sequence Definitions screen exactly in
the order specified. There is no need to leave a gap or input the sequences on
different lines. Also make sure that the PD=Printer Definitions screen that uses
this CS=Control Sequence Definitions has Lines per Page set to 66 as explained
earlier.
Portrait Compressed
027 069 Reset
027 038 108 048 079 Orientation Portrait
027 038 107 050 083 16.67 Typeface
027 038 107 055 072 7/120" HMI
027 038 108 055 046 055 055 052 053 067 Set VMI (7.7745)
Again ensure the PD=Printer Definitions Lines per Page box is set to 66.
Landscape Normal
027 069 Reset
027 038 108 049 079 Orientation Landscape
027 038 108 055 046 055 055 052 053 067 Set VMI (7.7745)
Ensure PD=Printer Definitions Lines per Page box is set to 42.

Landscape Compressed
027 069 Reset
027 038 107 052 083 Elite 12.0 Font
027 038 108 053 046 052 057 055 049 067 Set VMI (5.4971)
Landscape Super Compressed

027 069 Reset
027 038 107 050 083 16.67 Typeface
027 038 108 053 046 052 057 055 049 067 Set VMI (5.4971)
F Note: These control sequences determine the number of lines printed before
a page throw. If you want to change this parameter you will have to
substitute the relevant Text Length escape sequence (this information is in
your printer manual) and change the Lines per Page box in PD=Printer
Definitions.
F Note: The VMI specifies the gap between the lines. If there is a conflict
between the VMI and the Text Length, the Text Length will be ignored. In
this case, you will also have to adjust the VMI. Refer to your printer manual
or printer supplier in order to do this.

US Paper Sizes
The following control sequences have been created for US letter sized stationery:
US Portrait Normal Letter

027 038 108 048 079 027 040 115 049 048 072
US Portrait Compressed Letter

027 038 108 048 079 027 040 115 049 054 046 054 054 072
US Landscape Normal Letter

027 038 108 049 079 027 040 115 049 048 072
US Landscape Compressed Letter

027 038 108 049 079 027 040 115 049 048 072

Oracle Administration and
Maintenance Tasks
It is the role of the database/system administrator to ensure the smooth running

and efficient performance of Oracle. After a database has been created and all
objects and data have been added and are in use, there are times when administration
and maintenance must be performed. For example, it is important to back up the
database regularly. You may also need to create some new indexes to improve
performance.
In addition to the administrative duties outlined in the Oracle documentation, there
are some specific tasks relating to the running of SunSystems.
BACKUP ROUTINE
An Oracle database backup should be taken, ideally, every day. This is the
recommended method to backup your SunSystems data. The SunSystems function
FB=File Backup/Restore takes much longer than the database backup and is used
primarily for backing up data prior to an upgrade or for transferring SunSystems
data to a different database or operating system. It should not be used for every
day backing up.
Database backups should be stored on a separate drive to that of the database, so
in the event of a disk failure, both are not lost. Database backups should also be
included in your regular operating system backup schedule.
See your Oracle documentation for more information on database backups.
MONITORING DATABASE SIZE
The size of the SunSystems database (in USERS tablespace) should be checked
regularly. If the amount of free space falls below 20% of the total size, you must
plan for immediate expansion.

Updating Statistics and Recompiling Stored Procedures
The speed at which data is retrieved by Oracle is dependent on the data access
plan selected by the database optimiser. The optimiser makes its access plan
selection based on a number of criteria, including statistics regarding the distribution
of data within a given table. The statistics data is held within the Oracle data
dictionary tables, but has to be updated manually. As the statistical information
gets out of date when data is added or amended in the database, performance
drops as the optimiser may not be selecting the most efficient data access plan. To
ensure optimal performance the statistics should be updated regularly using the
ANALYZE command with the STATISTICS option, for example ANALYZE
TABLE SALFLDGDEM COMPUTE STATISTICS.
Stored procedures provide improved performance by being precompiled. This
avoids certain overheads associated with executing SQL statements. However,
the compilation of a stored procedure creates an access plan based, among other
things, on the statistics. If the statistics are out of date, or have been updated, then
the access plan of the stored procedure may be inefficient or even invalid. This
can result in degrading performance. Therefore stored procedures should be
recompiled on a regular basis, after updating the statistics. To recompile stored
procedures use the command ALTER PROCEDURE COMPILE.
You should update statistics weekly for each SunSystems table and then recompile
all stored procedures.
IMPROVING PERFORMANCE
There are many ways of improving the performance of SunSystems in an Oracle

environment. Each will have varying effects depending on the specific
configuration and data volumes and distribution at your site. Performance and
tuning information is best obtained from the Oracle Server administrator’s
documentation and the Oracle Server tuning manual. However, there are a number
of factors specifically related to SunSystems which should be considered in
optimising your system for performance. They are not arranged in any order of
priority. Take each factor in turn, monitoring the effect of changes for each one.
Device Management
There are a number of ways of improving performance through device management:
• Manually distributing I/O across disks
• Hardware-based RAID disk striping
• Disk mirroring.
Oracle Administration and Maintenance Tasks 59

Manually Distributing I/O Across Disks
Distributing data files, log files and rollback files across different physical disks
can have significant performance benefits. See the Oracle manuals for more
information.
Hardware Disk Striping

Disk striping involves the distribution of data across drives. Depending on the
level selected, there can be performance improvements and/or fault tolerance
benefits. For further information consult your hardware supplier.
Disk Mirroring
This is a method of providing fault tolerance whereby data is duplicated by writing
it to two mirrored disks. If one fails then the other one is used so that the system
can continue. This can have a beneficial effect on read performance as data can
be read from both disks. However, write performance can suffer and also this
method uses a lot of disk space since it is only 50% utilised.
Server Hardware Configuration

In general, performance is limited by the slowest part of your system, which
becomes a bottleneck. This may be the server CPU, memory, disk I/O, the server
processor bus architecture or one of a number of other components. Performance
is best improved by identifying the major bottleneck in your system and addressing
it so it is no longer a bottleneck. There will always be some part of a system which
is slower than the rest, so removal of a bottleneck will inevitably result in the
appearance of another. Each bottleneck should be addressed in turn. There will
come a point where no further improvement is possible given the cost constraints.
You should attempt to determine potential bottlenecks before purchasing your
hardware as this will determine the equipment you need. However, if the hardware
is already in place and performance requires tuning, then the following are ways
to address this.
Memory
This can have a major impact on the performance of Oracle applications. One of
the major time consumers is disk I/O. Oracle keeps data that has already been
read in memory for as long as possible until the memory is required for another
process. If the data is still in memory, then any subsequent access to the data will
not require a physical I/O from disk, only a logical I/O from memory which is
much faster. It therefore follows that, whilst memory is a bottleneck, the more
memory you have available to Oracle, the better performance you will achieve.

The Oracle instance parameter files described in the subsection Running Oracle
Scripts in the section Installing SunSystems contain parameters which affect how
memory is allocated to Oracle processes.
See the Oracle Server administrator’s documentation and the Oracle Server Tuning
manual for further information on configuring memory.
Server CPU/SMP
The processor on the server has to handle all the processing work Oracle does.
The faster your processor, the better the system will perform. Use of SMP with
multiple processors also has a very beneficial effect on performance, as Oracle is
able to multi-thread.
You should be able to identify whether the CPU is a bottleneck by monitoring
your system and thus whether an extra processor or processors would benefit
performance.
Provided you have ample memory, multiple CPUs, and can distribute your database
files across multiple disks, you should consider installing the Oracle Parallel Query
option to further improve performance. See the Oracle documentation for further
information.
Disk System and Interface

There are a variety of disk systems and interfaces available. Given that disk I/O is
a potential major bottleneck, it is recommended that a fast system and interface is
used. Again this can have a major impact on performance. Consult your hardware
supplier for further information.
SunSystems Configuration
Reference Data Setup

It is possible to improve performance dramatically by planning the way SunSystems
is used prior to setting up your data. An advantage of relational databases, such as
Oracle, is the ability to execute a query that retrieves and returns only the required
information. The easier the processing required to do this, the better it will perform.
For SunSystems this means performance can be optimised by grouping information
together as much as possible using identifying codes, e.g. alphabetic account codes
by account type (see example below), and journal definition codes by currency.
Many of the SunSystems functions process or report on data using selection criteria
to limit the information processed or retrieved. Often the selection criteria involve
ranges of data, e.g. account code range from 64001 to 64999. Other ranges may

be less obvious, but implied e.g. “process all debtor and client account types”.
The database will process this retrieval much faster if the codes for these ranges
are contiguous. For example, if you are often going to report on debtor and client
account types together (i.e. cutting out account types such as creditor, profit and
loss etc.), then group these account types together in consecutive account code
ranges. For example make debtor accounts from 60001 to 69999 and client accounts
from 70000 to 79999, with no other account types in between. The demonstration
data supplied with SunSystems is organised in this manner.
In addition, the more selection criteria supplied by the user when running a report
or a process, the faster Oracle can respond. This is because it is more likely to use
an index to speed data retrieval rather than read every record in the table (table
scan) to determine if it is required for the query. Using an index is very much
faster than a table scan where under 15% of the total data for a table is required.
Above this figure it becomes less efficient to use the index. This means that if a
significant amount of the data in a table is to be retrieved, it will be much faster to
do it in discrete, smaller runs, using appropriate selection criteria, than to do it in
one large run.
The more selection criteria supplied, by user entry or layout records, when running
an inquiry, report or procedure, the faster Oracle can respond. The more
appropriately your data is structured, the greater the effect.
Adding Extra Indexes

An index on an Oracle table is simply a method of speeding data retrieval. Up to
255 indexes can be added to a table. SunSystems data tables are created with
default indexes. These correspond to the way in which much of the data is accessed,
to optimise performance. Specifying a range of selection criteria for the first
column of the index is the main factor in the database deciding to use that index.
For example, there is an index on the ledger table for which the first column is
ACCNT_CODE representing the account code. Within SunAccount, the majority
of data access is via the account code, so this index speeds performance.
If you commonly access data via columns which are not the first column in an
index, e.g. ledger T-Codes, then you could consider adding an extra index on the
T-Code or codes most commonly used. This should speed the data retrieval;
however, any additional index will decrease the performance of data updates to a
certain extent as the index also has to be updated, so a balance must be struck.
Given all the other factors involved, the only realistic method for determining the
benefit of adding an index is to try it and see. If performance is not significantly
improved, or data entry performance is degraded to an unsatisfactory level, then
the index can simply be dropped again.

F Note: Do not drop the default SunSystems indexes or the performance of
SunSystems will be adversely affected.
Each site will be different in its index requirements, hence it is the responsibility
of the administrator to determine a strategy and implement any indexes required.
Note that these will have to be recreated upon upgrading to a new version of
SunSystems as this process involves dropping and recreating the database.
A specific example of where an index could be added is where a Journal Listing is
run with no selection criteria entered for the Journal Number, but a range of Journal
Sources is entered. The SQL query that is submitted to the database will have no
index to use (indexes are on Account Code and Journal Number), so a poorly
performing table scan will result. Adding an index on the Journal Source column
would speed up this report by a vast amount.
Operator Permissions
Extensive use of Operator Permissions within SunSystems has an impact on
performance due to the additional security information which has to be looked up.
Masking
The facility in SunSystems to use masking when entering selection criteria for
reports is a very useful one. However, in some cases it can result in a less efficient
query being sent to the database which may adversely affect performance.
Audit Control
Extensive use of Audit Control within SunSystems has an impact on performance
due to the additional tracking information which is logged to disk for each audit
controlled element.

Appendix A: SunAccount
Transfer File
This transfer file is used to import transactions into SunAccount, using the
JI=Journal Import function. A table of this format is also generated by SunBusiness
in order to transfer data from SunBusiness to the SunAccount ledgers. JI=Journal
Import can accept transfer files in the formats: SAF, SBF and PCF, from previous
versions of SunSystems.
The transfer table layouts used by SunBusiness are provided in the sections
Movement Import and Sales Import in the SunBusiness Reference Manual.
The same layout is created when you backup the ledger and budget tables in
SunAccount (backup files are created by the FB=File Backup/Restore function).
However, it contains a control record which is not required for JI=Journal Import
files. The filenames of these backup files are given in Appendix B: Filenames.
The SAF format transfer file may be created by any application which is able to
present it in ASCII text format.
This layout should be used for every transaction that is to be imported into Ledger
Accounting, Corporate Allocations and the Fixed Asset Register. Remember
that the debits and credits should balance to zero.
Fields which are not used should be space filled.
F Note: A full list of the maximum values permitted in SunSystems is provided

in Appendix D of the Technical Reference Manual.

Control Record
This is not required for JI=Journal Import, although a warning message appears if
none is found.
Item Start Position Length Comments
Filler 1 32 Space
Record Type 33 1 =C
Highest Journal Number Used 34 7
Last Cleardown Sequence Used 41 5
Filler 46 2 Spaces
Language Id. 48 2
Filler 50 463 Spaces
Accounting Transaction
Account Code 1 10 10 characters

Filler 11 5 Spaces
Accounting Period 16 7 yyyyppp (year number,
period number)
Transaction Date 23 8 yyyymmdd (year,
month, and day
number)
Filler 31 2 Spaces
Record Type 33 1 =M
(Record Types E, T, N
and L can still be read
in version 4.2. If your
records include
analysis codes T0, or
T6 to T9 you must use
Record Type L or M.)
Appendix A: SunAccount Transfer File 65

Journal Number 34 7 Journal Number

(The SunBusiness
transfer file divides
this item into a
SOURCE of 2 chars at
Start Position 34,
followed by the
Journal Number of 5
chars at Start Position
36.)
Line 41 7 Line Number
Amount 48 18 15 integer and 3
decimal
Debit/Credit Marker 66 1 = D or C
Allocation Indicator 67 1
Journal Type 68 5
Journal Source 73 5
Transaction Reference 78 15 15 characters
Description 93 25
Entry Date 118 8 yyyymmdd (Generated
by JI=Journal Import)
Entry Period 126 7 yyyyppp (Generated
by JI=Journal Import)
Due Date 133 8 yyyymmdd
Filler 141 6 Spaces
Payment/Allocation Ref 147 9 9 integer
Payment/Allocation Date 156 8 yyyymmdd
Payment/Allocation Period 164 7 yyyyppp
Asset Indicator 171 1 =V, D, I, or Space
Asset Code 172 10
Asset Sub-code 182 5
Conversion Code 187 5
Conversion Rate 192 18 9 integer and 9 decimal
Other Amount 210 18 15 integer and 3
decimal
Other Amount Dec. Places 228 1

Operator Id 229 3 Leave blank

Next Period Reversal 238 1 Leave blank
Text Linked 239 1 Leave blank
Rough Book Flag 240 1 Leave blank
In Use Flag 241 1 Leave blank
Analysis Code 0 242 15
Posting date 392 8 For rough journals:
date when un-roughed
(Generated by
JI=Journal Import)
Update Order Bal. Ind. 400 1 Leave blank
Filler 401 112 Leave blank
Appendix A: SunAccount Transfer File 67

Appendix B: File and Table
Names
This appendix gives a list of the file and table names used in SunSystems. Note
that nn represents the Language Code element of the names. The SunSystems
application consists of a large number of small programs and files, described in
the following table:
File Type File Suffixes Example Usage
Linked file none SSMM This is the main program.

Compiled .so SSFB Each menu function calls a
programs separate program
Screen blank SSTMPL The screen layouts contain the
definitions .idx prompts and field markers
Help blank SAHELP Help text displayed when you
messages .idx press F1
Program .MSG SBMSSG System messages invoked by the
messages program
Record and .LYT SSRM Reference maintenance,
document SPPP purchase order picking list
layouts
Report blank SAHEAD Headings for standard reports
headings

COMPLETE LIST OF PROGRAM FILES
UNIX COBOL Environment Run Time Program Files
Contained in $SUNDIR/lib/cobol
The exact contents of this directory may change with different releases of the
COBOL. Some systems may have extra subdirectories coblib, dynload, lang
and bin, which are further parts of the COBOL package.
ADISCTRL COBOL Accept/Display program
keybcf.gnt Keyboard Configuration utility
cobver COBOL version file
rts32 COBOL RTS (Run Time System) File
cobkeymp COBOL Keyboard Mapping File
Contained in $SUNDIR/bin
SUN Script for running SunSystems contained in $SUNDIR/bin
keybcf Keyboard configuration interpreter program
keybcf.sun Script for the keyboard configuration program
ccitcp2 The cci daemon for Graphical Client users
suwho A script file to show the Graphical Client processes currently
running
suncci A script file to start Graphical Client daemon processes
sunmaster A script file called by suncci to start the SSMASTER daemon
Contained in $SUNDIR/lib/terminfo
terminfo source files e.g. vt100.src
a,v,w, etc. directories containing compiled terminfo code
The following application programs are loaded by the COBOL run time
environment according to which module you are in and which function you have
selected.
Programs are supplied as callable shared objects with suffix .so
Appendix B: File and Table Names 69

Program Module Mnemonic Description
SAAA LA GA Aged Analysis

SAAL LA AL Account Listing
SAAR LA AQ Account Inquiry
LA AA Account Allocation
AR AQ Asset Inquiry
SAAS LA PS Print Statements
LA PR Print Remittances
SAAT LA CT Creditor Transfer
LA LA, DT Debtor Transfer
SABR LA BR Used to Roll Forward Previous Year
Balances in the Balance Table
SABU LA BU Ledger Balance Table Updates
SACA LA Displays Transactions Present on the
Ledger Table for a Given Code
SACRM LA LA,PR German Remittance Formatter
SADB LA DB Daybook Listing
SAEA LA FA Financial Analysis Extract
SAES LA FS Financial Statement Extract
SAET LA FT Financial Tables Extract
SAFA LA FA Financial Analysis Report
Update Customer & Vendor Details
SAFS LA FS Financial Statement Report
SAFT LA FT Financial Table Report
SAGP LA GP Generate Payments
SAGP LA GD Generate Debits
SAJE LA JE Journal Entry SAJE35-41
SAJESS RE LA User Hook Program for Journal Entry
SAJH LA JE Journal Hold SAJH42
SAJL LA JE/GP/JI/LR Journal Listing
CD/AA and JL
SALR LA LR Ledger Revaluation
SALX LA LX Ledger Export
SAPA LA PA Print Formatted Accounts
SAPC LA PC Period Cleardown

SAPL LA PL Payment Listing

SAPN LA PN Tax Reporting
SAPT LA PT Tax Reporting
SARP LA RP Rough Book Processing
SASO LA FA Financial Analysis Sort Process
SATA LA TA Tax Reporting
SATB LA TB Trial Balance
SATF LA JI Journal Import
SATFITF LA JI International Treasurer System
SATFSSRE LA User Hook Program for Journal Import
SATM LA TM Transaction Matching
SAVP LA VP Void Payments
SBAL IC EI Expired Items Report
SBAS IC AS Assembly Structure Listing
SBCL SO CL Customer Listing
SBIA SO/IC IA Inventory Allocation
SBIE IC IE Inventory Evaluation
SBIL IC IL Inventory Listing
SBIM IC ME Movement Entry
SBIS IC IT Inventory Status
SBIU IC IU Inventory Usage
SBML IC ML Movement Listing
SBPA SO PA Print Acknowledgements
SBPI SO PI Print Invoices
SBPK SO PK Print Statistical Declaration
SBPM SO PI/PS Post Stock Movement
SBPP SO PP Print Picking
SBPS SO PS Print Despatch Notes
SBPV IC PV Print Movements
SBTD SO SE Sales Order Entry (Details)
SBTDEXT SO Sales Order Entry/Import User Hook
SBTDSSRE SO User Hook Program for Sales Order
Detail
SBTE SO SE Sales Order Entry (Header)

SBTESSRE SO User Hook Program for Sales Order

Entry
SBTL SO SL Sales Listing
SBTS SO OS Order Status
SCCR CO CR Maintain Calendar Definitions
SCDR CO DR Allocation Definitions Report
SCGA CO GA Generate Allocations
SFAG AR AG Asset Register
SFAL AR AL Asset Listing
SFAS AR AS Asset Status
SFCD AR CD Calculate Depreciation
SFDI AR DI Asset Disposal
SFMD AR MD Mark Assets for Disposal
SFTL AR TL Depreciation Table Listing
SGBM MM BM Bill of Materials
SMEA IC MA Movement Analysis Extract
SMMA IC MA Movement Analysis Extract Report
SMMI IC MI Movement Import
SMMQ IC MQ Movement Inquiry
SMNQ IC IQ Inventory Inquiry
SMPC IC PC Period Cleardown
SMSC IC SC Stock Take Clearance
SMSI IC SE Stock Take Entry
SQ Stock Take Inquiry
SA Stock Take Approval
SMSL IC SL Stock Take Listing
SMSR IC GS Generate Stock Take
SOBL SO BL Price Book Listing
SOCQ SO CQ Customer Inquiry
SOEA SO SA Sales Analysis Extract
SOIQ SO IQ Item Inquiry
SOPC SO PC Period Cleardown
SOPM SO PM Print Miscellaneous Documents
SOPQ SO PQ Print Quotation

SOQC SO QC Quotation Conversion

SOSA SO SA Sales Analysis Report
SOSI SO SI Sales Order Import
SOSISSRE SO User Hook Program for Sales Order
Import
SOSQ SO SQ Sales Inquiry
SOUP SO UP Update BSP
SPGD PO GM Goods Receipt Matching (Details)
SPGE PO GM Goods Receipt Matching (Header)
SPIP PO VE/VA/
OM/GE Invoice Posting
SPIQ PO IQ Item Inquiry
SPOA PO OA Order Amendment Listing
SPPC PO PC Period Cleardown
SPPD PO PE Purchase Order Entry (Details)
VE Purchase Invoice Entry (Details)
VM Purchase Invoice Matching (Details)
SPPDSSRE PO User Hook Program for Purchase Order
Detail
SPPE PO PE Purchase Order Entry (Header)
VE Purchase Invoice Entry (Header)
VM Purchase Invoice Matching (Header)
SPPESSRE PO User Hook Program for Purchase Order
Entry
SPPI PO PI Purchase Import
SPPISSRE PO User Hook Program for Purchase
Import
SPPL PO PL Purchase Listing
SPPP PO PP Print Purchase Orders
PE Preview Purchase Orders
SPPQ PO PQ Purchase Inquiry
SPPT PO PT Purchase Commitment
SPPU PO PU Purchase Order Status Report
SPSL PO SL Supplier Listing

SPSQ PO SQ Supplier Inquiry

SPTT PO TT Commitment Transfer
SPVA PO VA Invoice Approval SPVA82
SPVG PO VG Invoice Register
SSAM SS AM Analysis Mapping
SSBC SS BC Business Conversion (hidden function)
(applicable to SUN user only)
SSBC2 SS Budget Checking Sub Routine
SSBU SS BU Business Menus (hidden function)
(applicable to SUN user only)
SSBV SS BV Business Views
SSBVLOAD Program for Launching Business
Analyser
SSCCUR SS Logon Security
SSDF All Document Formatter
SSDH Business Rules Data Dictionary
Handler
SSDI SS DI Definable Data Items
SSDT SS DT Data Dictionary Transfer (hidden
function)
SSEP SS EP Event Profiles
SSFB SS FB File Backup/Restore Router
SSFB3 SS FB Restore Data Upgrader
SSFBDD SS FB Backup/Restore Data Dictionary File
SSFBIN SS FB Backup/Restore Installation Data Table
SSFBKF SS FB Backup/Restore Stock Take Table
SSFBPF SS FB Backup/Restore Purchase Order Table
SSFBPF42 SS FB Copies Order Date from POP Order
Header to Given Report
SSFBPFLC SS FB Removes “P” Type Records from POP
Table
SSFBPH SS FB Backup/Restore Purchase History Table
SSFBQF SS FB Backup/Restore Journal Hold Table
SSFBRE SS FB Backs Up Report Format Data Files
SSFBRE SS FB Backup/Restore Report File

SSFBRF SS FB Backup/Restore Reference Table

SSFC SS FC File Create
SSFH SS File-Handler Router
SSFHCR SS File-Handler Common Routines
SSFHIN SS Installation File-Handler
SSFHKF SS Stock Take File-Handler
SSFHLB SS Ledger Balance , File-Handler
SSFHLF SS Ledger File-Handler
SSFHLH SS Archive File-Handler
SSFHLP SS Print File-Handler
SSFHMF SS Movement File-Handler
SSFHDD SS Data Dictionary File-Handler
SSFHOF SS Sales Order File-Handler
SSFHPC SS File handler for Purchase Order Master
Records (Control)
SSFHPF SS Purchase Order File-Handler
SSFHPJ SS File-handler for Purchase Order Master
Records (PO Header)
SSFHPK SS File-handler for Purchase Order Master
Records (Goods Receipt Header)
SSFHPL SS File-handler for Purchase Order Master
Records (Invoice Header)
SSFHPM SS File-handler for Purchase Order Master
Records (Detail Records)
SSFHPO SS File-handler for Purchase Order Master
SSFHPP SS File-handler for Purchase Order Master
SSFHPS SS File-handler for Purchase Order Master
SSFHQF SS Journal Hold File-Handler
SSFHRA SS Reference Audit File-Handler
SSFHRE SS Report File File-Handler
SSFHRF SS Reference File-Handler
SSFHTR SS SunBusiness Transfer File-Handler

SSFHHF SS Sales History File-Handler

SSFHPU SS Purchase History File-Handler
SSLP SS LP Lookup Table Profiles
SSLT SS LT Lookup Tables
SSMM SS Main Menu
SSNL SS NL Analysis Lengths
SSOP SS OP Operator Permissions
SSPA SS Business Conversion, Bank
Reconciliation (hidden function)
SSPX SS PX Parts Explosion
SSRA All RA Reference Audit
SSRC SS RC Reconciliation Accounts
SSRD SS Report Definition
SSRE SS Business Rules Rule Engine (entry)
SSRETM SS Transfer Manager Rule Engine
SSRF All Report Formatter
SSRF33EX All French User Hook for Format Amount
in Words
SSRF34EX All Spanish User Hook for Format Amount
in Words
SSRF49EX All German User Hook To Format Amount
in Words
SSRG SS RG Rule Messages
SSRI SS Business Rules Rule Engine (import)
SSRH All Report-Handler
SSRL SS RL Allows Locking of Records
SSRN SS RN Reconciliation Manager
SSRP SS RP Reconciliation Profiles
SSRR All Reference Reporting
SSRS SS RS Rule Sets
SSRT All Reference Transfer
SSRU SS Operator Buttons
SSRUACB Commitment Inquiry Special Edit
SSRUBCD Budget Check Definition

SSRUCAD Calculation Definition Special Edit

SSRUIAD Item Account Definition Special Edit
SSRUITD Extended Item Description Special Edit
SSRUITM Item Records Layout Special Edit
Routine
SSRUITP Item Records Process Special Edit
Routine
SSRUOTD Sales Order Description Special Edit
SSRUPRB Price Book Maintenance Layout
Routines
SSRUPRD Price Book Definition Special Edit
SSRUPRH Price Book Hierarchy Routine
SSRUQY Reference Maintenance Query Routine
SSRUSFD Sales Format Definition Special Edit
SSSF Various Special Functions
SSSH SS Old Screen-Handler (pre version 3.5)
SSSH35 SS Screen-Handler Routing
SSSHAD SS Screen-Handler Accept/Display
SSSHFF SS FreeFormat Screen-Handler
SSSHFH SS FreeFormat File-Handler
SSHGA SS SunSystems File Handler
SSSHGD SS SunSystems General Definition Screen
Handler
SSSHGL SS GUI Screen Handler (Login)
SSSHGM SS Hypertext Help for GUI Routines
SSSHGRD SS GUI Accept Module for Template
Fields
SSSHMF SS Help and Calculator
SSSHPN SS Panels Screen-Handler
SSSHQY SS Query Windows Screen-Handler
SSSHRX Rule Sets Screen-Handler
SSTD SS TD Terminal Definition
SSTI SS Transfer Manager Import
SSTP SS TP Transfer Profiles

SSTR SS TR Transfer Manager

SSTRIN SS Converts Response Tables
SSTRLF SS Translates Ledger Table Responses
SSTRQF SS Translations of Hold Table Responses
SSTRRF SS Handles Translation of Reference Table
Responses
SSTU SS Menu Template Update Program
SSTX SS Transfer Manager Export
SSUC SS UC Business Conversion (hidden function)
SSVR All VR View Report
SSXC SS Business Conversion, Ledger Export
(hidden function)
SSXF SS XF External File Types
PROGRAM SUPPORT FILES
The following tables provides a key to the lower case letters used in the
filenames:
Lower case code Description
b Budget code B-K

ddd Database code
fffff Format or report code
iii Operator Id
lc Language Code
lllll Layout code
nnn 3-digit number, sequential to avoid overwriting
rr Selection on Menu or internal function mnemonic
ss Subsystem Id (SA=Ledger Accounting, etc.)
ttt Reference table code
xxx Journal number
yy Ledger archive year

The following table provides a key to the file types:
Code File Type
1 Database Table
2 Indexed Sequential File
3 ASCII Text File
Filename Description
BANKREC.NDF Transfer file for Bank Reconciliation conversion (used by

TP=Transfer Profiles)
BCONNECT.EXE Program that enables Business Analyser lookup function
(RDBMS servers only).
BFILES.EXE Program that enables Business Analyser to connect to
Transfer Manager data via FTP. (Thin Client only).
BRlcHEAD Business Rules Report Headings
BRlcMSSG.MSG Message file used by BCONNECT.EXE and BFILES.EXE
BVIEW.EXE Program that enables Business Views function layouts.
SAlcHEAD SunAccount Report Headings
SAlcHELP.DAT SunAccount Help File
SAlcMSSG.MSG SunAccount Screen Messages
SAlcRM.LYT SunAccount Reference Record Layouts
SBlcHEAD SunBusiness Report Headings
SBlcHELP.DAT SunBusiness Help File
SBlcMSSG.MSG SunBusiness Screen Messages
SBlcRM.LYT SunBusiness Reference Record Layouts
SClcHEAD Corporate Allocations Report Headings
SClcHELP.DAT Corporate Allocations Help Files
SClcRM.LYT Corporate Allocations Reference Record Layouts
SFlcHEAD Asset Register Report Headings
SFlcHELP.DAT Asset Register Help Files
SFlcRM.LYT Asset Register Reference Record Layouts
SMlcHELP.DAT Inventory Control Help File
SMlcRM.LYT Inventory Control Reference Record Layouts
SOlcHELP.DAT Sales Order Processing Help File

Filename Description
SOlcRM.LYT Sales Order Processing Reference Record Layouts

SPlcHELP.DAT Purchase Order Processing Help File
SPlcRM.LYT Purchase Order Processing Reference Record Layouts
SSISSUE.MDF Default Command File
SSlcHEAD System Report Headings
SSlcHELP.DAT Help File
SSlcMSSG.MSG System Screen Messages
SSlcRM.LYT System Reference Record Layouts
SSlcTMPL.DAT System Screens
SSTU.SO Menu Template Update Program. Used in conjunction with
Business Menus
SUN.INI SunSystems Initialisation File
SUNWIN.ICO SunSystems Icon
DATA FILES
These hold details of transactions and reference records.
Reference Tables
Filename Type File Description
SSSYSTEM.DAT 3 System Data

SSINSTAL.DAT 1 Installation Table
SSRFttt 1 Reference Table
SSRAREFddd 1 Audit Tables
SSREPORT.DAT 2 Report Format Definitions
SSDDICTY.DAT 2 Data Dictionary used by RD=Report Definition
Ledger Tables
SALFLDGddd 1 Ledger Table
SAbFLDGddd 1 Budget Table
SAPYDDBddd 1 Debit Table used by GD=Generate Debits

SAPYPAYBddd 1 Payment Table used by GP=Generate Payments

SAQFHLDddd 1 Journal Hold Table
SALHARCddd 1 Ledger Archive Table
SBTRTRNddd 1 SunBusiness Transfer Table
Fixed Asset Files
SOMFHDRddd 1 Sales Order Headers Table
SOMFETddd 1 Sales Order Details Table
SOHFOHFddd 1 Sales Order History Table
Purchase Order Files

SPMFORDddd 1 Purchase Order Header Orders Table

SPMFGRNddd 1 Purchase Order Header GRNs Table
SPMFINVddd 1 Purchase Order Header Invoices Table
SPMFDETddd 1 Purchase Order Header Details Table
SPMFDTOddd 1 Purchase Order Header Details (at order stage) Table
SPMFDTGddd 1 Purchase Order Header Details (at GRN stage) Table
SPMFDTIddd 1 Purchase Order Header Details (at invoice stage)
Table
SPHFPHFddd 1 Purchase Order History Table
SPTRTRNddd 1 Purchase Commitment Transfer Table
SMMFMOVddd 1 Inventory Control Table
SMKFHDRddd 1 Stock-Take Headers Table
SMKFDETddd 1 Stock-Take Details Table

BACKUP FILES
SSINSTAL.BAK 3 Installation Backup File

SSRF-ddd.BAK 3 Reference Backup File
SALF-ddd.BAK 3 Ledger Backup File
SAbF-ddd.BAK 3 Budget Backup File
SAyy-ddd.BAK 3 Ledger Archive File
SBTR-ddd.BAK 3 Business Transfer File
SMMF-ddd.BAK 3 Inventory Control Backup File
SMMH-ddd.BAK 3 Inventory Control Archive File
SMKF-ddd.BAK 3 Stock-Take Backup File
SOMF-ddd.BAK 3 Sales Order Backup File
SOHF-ddd.BAK 3 Sales Order History Backup File
SOMH-ddd.BAK 3 Sales Order Archive File
SPMF-ddd.BAK 3 Purchase Order Backup File
SPHF-ddd.BAK 3 Purchase Order History Backup File
SPMH-ddd.BAK 3 Purchase Order Archive File
SSRF-SKL.BAK 3 Skeleton Reference Backup File
PRINT FILES
All print files may be deleted when the operators are logged out of SunSystems,
assuming the reports they contain are no longer required.
rrnnn.PRN 3 Report File

lllllnnn.PRN 3 Report File with a layout
JLxxxxxxx.PRN 3 Forced Journal Listing
SAfilename.TLF 3 Transfer Layout File

You can produce reports in a variety of transfer formats from the following
SunAccount functions:
FA=Financial Analysis
FS=Financial Statements
and FT=Financial Tables.
The table on the next page shows the formats available, and the naming conventions
of these reports:
Format Description Filename
LOTUS Suitable for Lotus 123 FTfffff.PRN

EXCEL Suitable for Microsoft Excel FTfffff.PRN
CDFQ Comma delimited with quotes FTfffff.CDF
2020 Suitable for 2020 FTfffff.CDF
BDF Bar delimited FTfffff.BDF
SYLK Suitable for SYLK FTfffff.SLK
CDF Comma Delimited FTfffff.CDF
FCS Financial Control System DATfffff.ES
LGCfffff.ES
WORK FILES
All work files may be deleted when the operators are logged out of SunSystems.
Normally work files are created and deleted automatically by SunSystems.
ssrr-ddd.iii 2 Transaction Entry work files

2 Sort work files, etc.
ssrr-iii.DAT 2 Report work files
SSWM-nnn.DAT 2 Learn/Execute macros

Appendix C: Error Messages
OPERATING SYSTEM AND COBOL ERRORS
This appendix describes errors which mainly result from the operating system
being unable to perform the process requested from the COBOL run time system.
There are two different forms in which these errors can be reported:
File Status Codes

Errors resulting from the processing of disk files are reported to you on the message
line near the bottom of the screen. A file status code at the end of this line identifies
the specific error which has occurred. The file status code is in the form:
9-mmm
where mmm is an error code. If an operating system error has occurred the first
character of the file status is always nine.
9-255
This is a catch-all code for unexpected database errors. If you receive this error,
add the line ERRORLOG=ON to your SUN.INI file and attempt to reproduce the
error. This setting in SUN.INI will output specific database errors to a log file in
the SunSystems programs directory in the format SQL-xxx.LOG where xxx =
operator Id. This information can, if required, be given to Systems Union support
in order to help identify the problem. Also check the Oracle Server error log to
see if the error has been recorded there.
Run Time System (RTS) Errors

This type of error should rarely occur when using the system.
The run time system is a part of the COBOL language resident in memory when
programs are operating. If it finds an error in the processing requested by the
system it reports it in the form:

aaaa
SEGMENT: 00
ERROR mmmm COBOL PC nnnn
where aaaa is the program name, mmmm is the error code, and nnnn is the address
of the program instruction in error.
The following pages list some run time system error messages and give their
meaning.
001 Insufficient buffer space
You have tried to OPEN a file and while you have not exceeded your system’s file
limit, something within your system is unable to allocate sufficient memory space
for this operation to be carried out successfully.
002 File not open when access attempted
You have tried to access a file without OPENing it first.
003 Serial mode error
The program which you are trying to execute is a device not a program.
004 Illegal file specification
A name which you have supplied contains an illegal character. This could be any
character which is not part of the permitted character set, or it could be the system
dependent delimiter which on most systems is the space.
Attempt the file operation again, ensuring that you use the correct filename.
005 Illegal device specification
Devices to which your COBOL program can WRITE are defined by the operating
system. You have attempted to access a device which is not defined by your
system.
006 Attempt to output to a file opened for input
You have tried to WRITE to a file which is open for INPUT only.
007 Disk space exhausted
There is no room available on your current disk for file operations.
008 Attempt to input from a file opened for output
You have attempted to READ from a file which you opened for OUTPUT only.
009 No room in directory
There is no room available for further file operations in the directory which you
have specified, or the specified directory cannot be found by your program.
Appendix C: Error Messages 85

011 Memory Error (Fatal)
The run-time system has insufficient memory to successfully carry out the attempted
operation.
012 Attempt to open a file which is already open
You have tried to OPEN a file which is already OPEN and so cannot be OPENed
again.
013 File not found
The operating system has been unable to find a file which you have attempted to
access in your program.
014 Too many files open simultaneously
You have tried to exceed the maximum number of files which you can have OPEN
at any one time. This may be a software or an operating system restraint, but you
must not violate it.
015 Too many indexed files open
You have tried to exceed the number of device files which you can have open at
any one time. This may be a software, or an operating system restraint, but you
016 Too many device files open
You have tried to exceed the number of device files which you can have open at
any one time. This may be a software or an operating system restraint, but you
017 Record error: probably zero length
You have probably tried to access a record which has had no value moved into it.
018 Read part record error: end of file before end of record or file open in
wrong mode
A part record has been found at the end of a file. Consequently your run time
system will treat the data file as a record and, not finding a full record, will report
this error.
019 Rewrite error: open mode or access mode wrong
You are attempting to do a REWRITE to a file that has not been opened with the
correct access mode for this operation.
021 File is a directory
You have tried to WRITE to a directory instead of a file.

022 Illegal or impossible access mode for OPEN
The mode in which you are attempting to OPEN a file violates the general rule of
COBOL programming for that type of file. For example, you may have OPENed
a line-sequential file in the I-O mode.
023 Illegal or impossible access mode for CLOSE
The mode in which you are attempting to CLOSE a file is not possible for that
type of file.
024 Disk input-output error
This error could be given if you do a READ after a WRITE, or if there is a
verification failure, or a parity error.
025 Operating system data error
You are trying to set up terminal characteristics for a device which is not a terminal.
026 Block input-output error
An error has occurred while you are attempting to access a disk. This could be the
result of a corrupt disk.
If you have a corrupt disk try to run your program again using your backup copy
of that disk.
027 Device not available
You are attempting to access a device which is either not attached to your machine
or, if attached, is not on line.
Attach the device to your machine and ensure that it is on line. Repeat the file
operation.
028 No space on device
You have attempted to do a file operation such as WRITE for which there is not
sufficient space available on your disk.
When your program has terminated you will have to delete some of the files or
directories on your current logged in disk to make enough room on it for you to
carry out successful file operations.
030 File system is read only
The file system which you are using is READ only, which effectively means that
it is WRITE protected. You have tried to amend the information found within a
file in some way. For example, you may have tried to WRITE to a file, or to
DELETE information found within it. As the file system which you are using is a
READ only, you can only READ the contents of its files. You cannot alter them
in any way.

031 Not owner of file
You are attempting to perform an operation on a file but the file’s owner has not
given you the necessary permission for that operation. You could, for example,
be attempting to alter the access mode for a file, which only the file’s owner can
do.
You will have to abandon your attempted file operation, unless the file’s owner
alters the file’s attributes in such a way as to allow you to perform the operation
you wish to carry out.
032 Too many indexed files or no such process
You have tried to OPEN an indexed file but the number that you currently have
open is the system limit.
Alternatively you could be trying to use a process Id which does not exist, or your
operating system no longer recognises.
033 Physical input-output error
You have a hardware error of some type, perhaps you have failed to place a disk
in the relevant drive or you may have tried to WRITE to a disk but the processor
detected that the hardware interface has failed.
You will have to try to correct the fault in your hardware, for example by placing
a disk in the necessary drive.
034 Incorrect mode or file descriptor
You are either trying to WRITE to a file which is open for READ purposes only,
or READ a file which is open for WRITE purposes only.
035 Attempt to access a file with incorrect permission
You are attempting to do a file operation which you do not have sufficient
permission to achieve, for example you could be trying to WRITE data to a file
which has been set up with the READ attribute only.
036 File already exists
You are attempting an inappropriate operation on an existing file.
037 File access denied
Your attempt to access a file has been denied by the operating system. You may
have tried to WRITE to a WRITE protected file, or you could have attempted to
READ from an OUTPUT device.
Alter the access permission on the relevant file. Access can be READ only if you
just want to read the contents of the file without making any changes, or it can be
READ and WRITE in which case you will be able to change its contents.

038 Disk not compatible
You have tried to load a disk that is incompatible with the current version of your
operating system.
This could be because it was created under a previous version of the system or it
could have been created under a completely different operating system. You would
also receive this error if you tried to load a disk with a name that clashed with a
disk that was already loaded.
039 File not compatible
You are trying to load a file that is not compatible with the structure of files under
the current release of your software. This could be because that file was created
under a different operating system or under a previous version of your current
system.
041 Corrupt indexed file
Your run time system does not recognise the control information for an indexed
file and as the index has been corrupted in some way, the data within the file is no
longer accessible to your system.
You will have to rerun your program using the backup copy of that file. If you
have added a great deal of information to the file since you last took a backup you
may like to rebuild the file using the SunSystems file backup followed by a restore,
using the FB=File Backup/Restore option.
042 Attempt to write on broken pipe
Your program has created a process as a result of DD_logical filename mapping
assignment (for example, the process may be a line printer spooler). The process
was not created properly, or has died prematurely. This error occurs when your
program attempts to write to the process.
043 File information missing for indexed file
You normally receive this error if the system crashed on the program’s previous
run, while the file was OPEN. Information was probably added to the end of that
file, but the directory information was not updated and so that data cannot be
accessed by your system. You can also receive this error if you copied the ISAM
file from one disk to another, but only copied either the .DAT part, or the .IDX.
If it is the result of a faulty copy you should be able to restore the missing part of
the file from the .DAT or .IDX file. Otherwise, you will have to rerun your
program using the backup copy of that file. If you have added a great deal of
information to the file since you last took a backup you may like to rebuild the file
using the SunSystems file backup followed by a restore, using the FB=File Backup/
Restore option.

047 Indexed structure overflow
There is some fault in the structure of your ISAM file. You have probably tried to
put another entry in the index when there is no room for it. This error could also
be given if you have tried to access an old ISAM file, created perhaps using CIS
COBOL.
048 Attempt to divide by zero (fatal)
You are executing a program that is attempting to divide by zero. Contact your
supplier.
065 File locked
You have tried to OPEN a file which has already been locked, or opened for
output by another user. Alternatively you have tried to OPEN a file for output
which another user already has open.
066 Attempt to add duplicate record key to indexed file
You have tried to add a duplicate key for a key which you have not defined as
being able to have duplicates.
067 Indexed file not open
You are attempting to access an indexed file which you have not OPENed.
068 Record locked
You have tried to access a record which is currently locked by another user.
069 Illegal argument to ISAM module
This is the result of an internal system error.
Contact your supplier who will try to help you to discover the cause of your error
and how it can be rectified.
070 Too many indexed files open
You are attempting to OPEN an indexed file, but you have already exhausted the
system limit which specified how many of these files can be opened at any one
time.
071 Bad indexed file format
This error could be given if you are using a file which has been corrupted, otherwise
it is the result of an internal system error.
If the disk you are using is corrupt, re-run your program using your backup copy
of the disk. If this is not the cause of the error then you should contact your
supplier who will try to discover the cause of your error and how it can be rectified.

072 End of indexed file
Contact your supplier, who will try to help you discover the cause of your error
074 No current record in indexed file
Contact your supplier who will try to help you discover the cause of your error
076 Cannot create lock file in /isam directory
For some reason your system is unable to create a lock file in the ISAM directory.
One reason for this could be that in its previous run your program terminated
abnormally, (perhaps due to a power failure) leaving some files locked. When
you try to run this program following its abnormal termination you will receive
this error.
You will have to manually remove all of the files that are still locked from the
ISAM directory before you can successfully re-run your program.
077 Internal ISAM module error
078 Illegal key description in indexed file
081 Key already exists in indexed files
100 Invalid file operation
You have attempted a file operation which violates a general rule of COBOL in
some way. The most likely cause of this error is that you have attempted a
REWRITE on a sequential file opened I-O, or on a relative file with access mode
sequential also opened I-O, without preceding it with a successful READ NEXT.

101 Illegal operation on an indexed file
102 Sequential file with non-integral number of records
This error could be given if you have specified an incorrect record length for a
sequential file; if the sequential file you are attempting to access is corrupt in
some way; or if the file you have specified is not a sequential file.
104 Null file name used in file operation
You have specified a variable name for a filename instead of a literal, and on
attempting to OPEN that file only spaces were found in the variable.
105 Memory allocation error
The run time system is unable to allocate sufficient memory space to successfully
carry out the attempted operation. This error implies that there is no memory
space left on your system.
106 Dictionary error
This could be the result of a READ or WRITE error to file or disk, but it is more
likely to be the result of an internal system error.
and how it may be rectified.
107 Operation not implemented on this run time system
You are attempting to perform an operation which your run time system does not
support.
114 Attempt to access item beyond bounds of memory
Memory access violation has been detected by your operating system.
115 Unexpected signal
A signal the run time system was not expecting has been caught.
116 Cannot allocate memory
For some reason a part of your run time system is unable to allocate you sufficient
memory to enable you to execute your code.
117 Bad collating sequence
This is an internal system error.
Please contact your supplier who will try to help you discover the cause of your
error and how it may be rectified.

138 File closed with lock - cannot be opened
You are attempting to OPEN a file which you previously CLOSEd with lock, and
as such an operation violates one of the general rules of COBOL programming
you have been given this error.
139 Record length or key data inconsistency
There is a discrepancy between the length of a record, or the keys which you have
specified, in your current program and its definition in the program in which it
was first OPENed.
141 File already open - cannot be opened
You have tried to OPEN a file which is already OPEN and so cannot be OPENed
again.
142 File not open - cannot be closed.
You have tried to CLOSE a file which is not OPEN.
143 Rewrite/delete in sequential mode not preceded by successful read
You have to do a successful read on a sequentially accessed file attempting a
REWRITE or DELETE on some of the information contained within that file.
146 No current record defined for sequential read
The current record pointer in your file is undefined owing to a failed READ/
START or INVALID KEY condition. You have tried to read another record in
the file but as the current record is undefined the system cannot find the start of
the record for which you have asked.
147 Wrong open mode or access mode for read/start
You have violated one of the general rules of COBOL programming as you have
tried to carry out a READ or START operation on a file which has not been
OPENed INPUT or I-O, or is not OPEN at all.
148 Wrong open mode or access mode for write
You have tried to WRITE to a file in sequential access mode that you have not
OPENed for OUTPUT or EXTEND, or you have tried to WRITE to a file in
random or dynamic access mode that has not been OPENed INPUT or I-O.
149 Wrong open mode or access mode for rewrite/delete
You have violated one of the general rules of COBOL syntax as you are trying to
do a REWRITE or DELETE on a file that you have not opened for I-O.
151 Random file on sequential file
You have violated one of the general rules of COBOL syntax as you are trying to
do a random READ on a file which has sequential organisation.

152 REWRITE on file not open input-output
You have violated one of the general rules of COBOL syntax as you are only
permitted to carry out a REWRITE on a file that has been OPENed for I-O
operations, but you have attempted a REWRITE on a file that is not OPEN I-O.
153 Subscript out of range
A subscript which you have used in your program is out of the defined range, that
is, it is either zero, or it is greater than the number of occurrences of the item.
154 PERFORM nested too deeply
This error usually results if you have used GO TO to jump out of the range of a
PERFORM rather than to jump to an EXIT statement at the end of its range.
155 Illegal command line
The generic command line interpreter, which must be present if your program is
to be run successfully, is not found on your system.
157 Not enough program memory: object file too large to load
Your program is too large for the available memory space.
159 Malformed line-sequential file
A line-sequential file which you are trying to access is corrupt in some way. Re-
run your program using the backup copy of that file.
161 Illegal intermediate code
The piece of intermediate code which is currently being processed is not a valid
operation. You are probably trying to execute a corrupted file.
162 Arithmetic overflow in numeric field
You have attempted to divide a data-item by zero.
163 Illegal character in numeric field
You have attempted an arithmetic or comparison operation on a numeric item
which contains non-numeric data (for example, space).
164 Run time system subprogram not found
You have attempted to call a subroutine whose entry address has not been set up
in your run time system.
165 Version number incompatibility (intermediate code and RTS
incompatible)
You are using incompatible releases of the compiler and the run time system which
means that the compiler that you are using will generate (or has already generated)
code that your run time system will not be able to execute correctly.

166 Recursive COBOL call is illegal
You have tried to CALL a COBOL module that is already active.
167 Too many USING items
The list of items you have supplied is a CALL....USING statement is longer than
the run time system can handle.
168 Stack overflow (fatal)
You have nested a PERFORM statement or a series of CALL statements too deeply.
171 Japanese operations are illegal with this RTS
You are attempting to do Japanese operations with a non-Japanese RTS, or you
have used a Japanese compiler to compile your program and are now trying to run
your code using a non-Japanese run time system.
173 Called program file not found in drive/directory
You have attempted to call a file which is not present on your current logged-in
drive or directory, or is not pointed to by the COBDIR environment variable.
176 Illegal inter segment reference
Your code contains a segment reference for the forward reference table which is
illegal, or it is corrupted. Contact your supplier who will try to help you discover
the specific cause of this error.
177 Attempt to cancel active program
You have tried to remove a currently executing program or its parents or
grandparents from its memory.
178 Error during save
You cannot save the information which your program has generated. This can be
caused by several different reasons but one of the most common causes is that you
have attempted to BUILD a module that is too large for the memory space.
179 Error during chain (program not found)
You have tried to chain to another program which your system is unable to find.
180 End-of-file marker error
A file-marker used to indicate that the end of file has been reached is missing from
one of your files.
181 Invalid parameter error
A parameter which you have used is not one which is recognised by your system.

182 Console input or console output open in wrong direction
You are either trying to read input from the screen or WRITE to the keyboard.
183 Attempt to open line-sequential file for I-O
You have tried to open a line-sequential file in the input-output open mode, but
this mode is not supported for files with this organisation.
184 ACCEPT/DISPLAY input-output error
You have tried either to read input from the screen or WRITE to the keyboard.
187 Run time system not on COBDIR path
The Run Time System cannot be found on the path you have set up in the COBDIR
environment variable. Check the value of this variable (found in the
AUTOEXEC.BAT) .
188 File name too large
A file name which you have used has more characters than the maximum number
allowed by your operating system (usually eight).
189 Intermediate code load error
You are unable to load a file because it has become corrupt in some way.
190 Too many arguments to CALL
A CALL within your program cannot be successfully executed because of the
number of arguments which you have used with it.
193 Error in variable length count
The piece of intermediate code which is currently being processed is not a valid
operation. You are probably trying to execute a corrupt file or one which has not
been compiled.
194 File size too large
A file which your program is accessing is too large for successful execution to
continue.
195 DELETE/REWRITE not preceded by a READ
Before a DELETE or a REWRITE statement can be successfully executed in
sequential access mode the last input-output statement executed for the associated
file must have been a successful READ. In your code no READ statement precedes
your attempted DELETE or REWRITE.
196 Record number too large in relative or indexed file
The relative record key has exceeded the system limit, that is the file is too large
for the system to handle.

Alternatively the record key which you have specified is too large for the system
to deal with successfully, or the pointer to the record has been corrupted in some
way so that it is either too large or it is not a multiple of the record length.
197 Screen handling initialisation error
This error is caused by one of the following:
Your display adapter is in the wrong mode
Your screen handling interface has not been correctly initialised because your
terminal does not have the required capabilities
Your terminfo file is corrupt
Memory has been allocated incorrectly.
198 Load failure
You have not been able to load the file which you requested perhaps because it is
corrupt.
If the file failed to load because it is corrupt then re-run your program loading
your backup copy of the file. This error often occurs because of insufficient
memory.
199 Operating system error out of defined range
A system call has returned an unexpected error number which is not documented.
Contact your supplier who will try to help you discover the specific cause of this
error.
200 Run time system internal logic error
You can receive this error if the amount of memory available on your machine is
so low that not even the run time system can be fully loaded properly. In this case
you will have to free some memory and then you should be able to re-run your
program successfully.
However the most common cause of this error is that your run time system has
followed a route which it should not have followed. If this is the case you will
need to contact your supplier who will try to help you discover the cause of this
error.
201 Input-output error in paging system
There is no room available in your current directory or file on the floppy disk
which you are using, for the paging file.
When your program has terminated delete some files which you no longer need in
your directory to make room for the paging file.

203 CALL parameter not supplied
You have not supplied your currently executing file with all of the parameters
mentioned in the linkage section of your main program.
206 Reading unwritten data from memory file
You are attempting to read data which has not been written from the core file.
207 Machine does not exist
You have tried to access a machine that is not connected to your network, or the
machine is not switched on.
208 Error in multi-user system
This is normally caused by an unexpected error occurring within the network or
file sharing facilities. A corrupted network message will also return this error.
209 Network communication error
This is normally given if an incorrect checksum has been received in a
communications packet.
210 File is closed with lock
You have tried to open a file which you have previously closed with lock.
212 Malformed assembler subroutine file
You are attempting to access an assembler routine that is not in the specific format
for such a file.
213 Too many locks
You have either tried to exceed the maximum number of record locks per file
which can be in force at any one time or you have exhausted an operating system
or network resources, for example, dynamic memory.
215 Cannot animate a program running COMMUNICATIONS
You have tried to animate a program which makes use of the communications
module. This cannot be done as both animator and the communications module
need full use of the CRT.
216 Cannot initialize the named communications device
A device driver is probably missing.
217 Incompatible host for compiled code file
The .GNT file is not valid for the host processor.

219 Operating system shared file limit exceeded
You have tried to exceed your operating system’s limit on the number of shared
files that you can have OPEN simultaneously. As this figure is operating system
dependent so you will need to consult your operating guide for details of how
many shared files your system permits to be OPEN at any one time.
221 SORT/MERGE error
222
You receive one of these three errors if you attempt to do a SORT/MERGE which
is unsuccessful for some reason. These errors can result from a variety of causes;
for example, you may have too many files OPEN when you are attempting a
SORT/MERGE or the file you are trying to access may be locked.
901 Could not open print device
Your printer may be disconnected or switched off.
902 Bad printer control code given
Check Control Sequences and/or Printer Definitions.
903 Printer device not open
904 Out of memory while printing
The print command is unable to allocate sufficient memory space to successfully
carry out the attempted operation. This error implies that there is no memory
space left on your system.
905 Failed to open file
Print Manager cannot open the file you are attempting to print.
906 Disk full while spooling file
There is insufficient disk space to create the required temporary spool file. Delete
some files or directories on your current drive before trying again.
907 Print job aborted
908 Printer information structure badly constructed
909 No default printer found
Check Printer Manager for a default print device.
910 No commdlg.dll found
Write failure

Appendix D: Database Overview
This appendix provides a brief overview of table layouts and SQL queries.
Table Names
SunSystems allows the user to define multiple companies/ledgers which can be
consolidated in reporting. These companies/ledgers are known as databases in
SunSystems. Each database has its own set of tables, each distinguished by a
three letter alphanumeric code known as the Database Code. The database code is
the last three characters of the table name denoted by ‘ddd’.
So if SALFLDGddd stands for the ledger table, and the demonstration database or
company has the three letter prefix DEM, the ledger table is called SALFLDGDEM.
Likewise the ledger table for database/company 001 is called SALFLDG001.
Column Names
Wherever possible meaningful column names have been used.
Indexed Columns
All SunSystems tables have at least one index, and some have two or three. An
index may be created for a single column or for multiple columns. Indexed columns
are indicated at the end of each table listing.
The SQL indexes may be composed of a number of columns. Multi-column indexes
are called ‘segmented indexes’ or ‘composite keys’.
For most tables index 1 is a unique index, i.e. it allows no duplicates.

Numeric Data in SQL Databases
Numeric columns are generally stored as ‘int’ or ‘numeric’. In the following
example you can see the numeric data types used by SunSystems, and their sizes:
Column Name Sample SQL Server Type Bytes
Payment 1,234,567.89 numeric variable

Turnover 123,456,789 int 4
Age 21 smallint 2
SunSystems dates are all in the format yyyymmdd.

SunSystems accounting periods are always in the format yyyyppp.
Both dates and periods are sometimes held in character columns and sometimes
in numeric columns.
Join Columns
Columns used to join tables are usually given the same name. To join information
from the ledger table and the accounts table would require the SQL clause:
where SSRFACC.ACCNT_CODE = SALFLDGDEM.ACCNT_CODE
and SSRFACC.SUN_DB = ‘DEM’
Joins for analysis codes require the analysis category to be specified. For example,
to find the analysis row corresponding to ANAL_T2 you would have to use the
SQL clause:
where SSRFANV.CODE = SALFLDGDEM.ANAL_T2
and SSRFANV.CATEGORY = ‘T2’
and SSRFANV.SUN_DB = ‘DEM’
Other reference tables may require the combination of more columns to define a
unique reference.
Appendix D: Database Overview 101

Appendix E: Machine Variations
HP9000
Since the COBOL was written primarily for ANSI conforming terminals, HP
terminals will not work properly without a major rewrite of the COBOL interface.
It is therefore strongly recommended that the supported HP terminals be used in
ANSI mode. The following table shows the recommended configuration:
Terminal 2392 700/92

2394 700/94
700/22
TermMode ANSI EM220

TERM= ansi vt220
Function Key ‘N’ N/A
InhHndShk(G) ‘YES’ N/A
Inh DC2(H) ‘YES’ N/A
If error 197 Screen Handling System Initialisation Error occurs when you are
using one of the supported terminals, the terminfo file is missing an entry for
home. Correct this by adding home=\E&aOyOC to the terminfo source file.
Compile that change with the tic command.
To configure a terminal for vt220 emulation, follow the instructions below:
1 Press the user system key.
2 Press F8 (config keys).
3 Press F5 (terminal config).
4 At the menu, move the cursor to TermMode in the bottom right, then press F2
until EM220 is displayed.
5 Press F1 (save config).
6 Press F8 (config keys).

7 Press F6 (ansi Config).
8 At the menu move the cursor to the backspace field in the top right, and press
F2 until Backspace/Del is displayed. This allows the backspace key to work
correctly.
9 Press F1 (save config).
F Note: It is very important to reset the terminal to HP mode before copying

any HP system data from tape. Copying to and from tape using tar is
unaffected.
If you are using the vt220 emulation, it is necessary to press CTRL+SYSTEM before
entering SunSystems; this enables you to use the function keys. Displayed on the
function key labels will be F6-F13, but the keys will correspond to function key 1,
function key 2, and so on.
Appendix E: Machine Variations 103

Appendix F: terminfo
Below is a list of terminfo entries necessary for running SunSystems. The

source code for your particular emulation is usually supplied with your system,
and may be found in $SUNDIR/lib/terminfo.
For example, for a VT100 terminal the source file is:

$SUNDIR/lib/terminfo/vt100.src
For more detailed information on terminfo, see the relevant man pages on
your system.
Compiling and Displaying terminfo Entries

Use the UNIX tic command to compile new terminfo entries. Note that
unless the TERMINFO environment is set, the tic command will compile the
entry by default beneath the usr/lib/terminfo structure. Because
SunSystems uses its own terminfo structure, set the TERMINFO variable to
point to the $SUNDIR/lib/terminfo directory before executing tic.
For example:
TERMINFO=$SUNDIR/lib/terminfo
export TERMINFO
tic -v1 vt100.src
Many versions of UNIX support the infocmp or untic commands which display
terminfo entries to the screen or to a file. Therefore to alter or include a
terminfo entry for an existing emulation, type:
TERMINFO=$SUNDIR/lib/terminfo
export TERMINFO
tic -v1 vt100.src
Make the changes to vt100.src using vi or another text editor, then type:
tic -v1 vt100.src
For further information on tic, infocmp and untic, consult your UNIX
documentation.

AIX users should use the Micro Focus commands mfinfocmp and mftic rather
than the AIX infocmp and tic commands. The files mfintocmp and mftic
can be found in $SUNDIR/lib/cobol/bin.
Using Wyse Terminals

Attributes on Wyse terminals occupy a character position on the screen, so normal
highlighting (reverse, underline, etc.) cannot be used.
Instead, the rev string in terminfo should be set to \E!6\E). This sets the
protect character attribute (which does not occupy a screen position) to reverse
video and turns on the write protect submode on the terminal.
The sgr0 string in terminfo should be set to \E(which turns the write protect
submode off. The sgr and xmc entries should be removed completely from
terminfo.
Appendix F: terminfo 105

Appendix G: Enabling Business
Analyser
If you are serialised for the module Process Manager, you need to enable the
Business Analyser function. This allows you to view data, errors and messages
generated as a result of running the rules which are defined in RS=Rule Sets. See
the SunSystems User Note Version 4.2.6 for more information on the Business
Analyser function.
There is now a new program, BFILES.EXE, which allows the user to define how
work files are to be handled on the network. This program resides, and must be
set up on, each client as follows:
1 Run the BFILES.EXE program. A dialog box appears entitled Work File
Access for Business Analyser.
2 For UNIX, you must select FTP as the Connection Type.
3 Now enter the appropriate information as detailed below:
Server Enter the network name of the UNIX server.
Directory Enter the full pathname for the directory containing
the operator’s work files. For example, /home/
sun426/work .
User Name Enter the UNIX login name, which is used by the
operator to log in to the UNIX server. This is not the
same as the SunSystems operator code.
Password Enter the UNIX login password, which is used by the
operator to log in to the UNIX server. This is not the
same as the SunSystems password.
4 When all the appropriate information has been entered, click the Test button to
ensure that the connection is successful. A message is returned, stating either
Pass or Fail.
5 Use the Clear button if the setup information needs to be amended or removed.
The Clear button actually removes information from the fields allowing it to
be re-entered.

ODBC CONNECTION SETUP
To fully utilise the database lookup features of the Business Analyser tool, the
SunSystems client must have an ODBC data source defined to access the
SunSystems database. To configure this, the system administrator must run the
program BCONNECT.EXE. This program prompts for an ODBC data source name
plus a valid database username and password, and must be run on each client
machine. See Additional Client Software Requirements below for further details.
CONFIGURING BUSINESS ANALYSER
Business Analyser invokes BVIEW.EXE to connect to the server using the above
information. It finds the required file and copies it to the windows temp directory
and uses it from there. When BVIEW.EXE closes, any files updated by it are sent
back to the server. Please note that the program assumes that all file names are in
upper case.
When creating a TP=Transfer Profile for use with Business Analyser, the file
must be output to the work file location specified in:
• The user’s OD=Operator Definitions record
• The directory specified in the BFILES configuration
The directory must be the same in all three programs.
ADDITIONAL CLIENT SOFTWARE REQUIREMENTS
If you are using the ODBC connection as described above, each client requires the
Oracle Net8 client software component with the Microsoft supplied Oracle ODBC
driver. Please refer to your Oracle documentation for further information regarding
the installation and configuration of Net8 networking components.
Appendix G: Enabling Business Analyser 107

Appendix H: Cobol Run-time
Licensing
SunSystems application programs rely upon the COBOL runtime system supplied
with each edition.
This runtime system is licensed automatically by the installation routine,
INSTALL.SUN.
If a new edition of SunSystems 4.2.6 is installed in a new directory, the location of
the software is moved, or a secondary install is required (for development or testing
purposes), then the license database becomes invalid.
This appendix describes how to avoid potential conflicts with the license database
in two possible scenarios:
Installing SunSystems 4.2.6 software in a new location, and installing an additional
version of SunSystems 4.2.6:
When updating SunSystems 4.2.6, it is advised to install it in a new location. The
new install attempts to configure the license database and bind it to the new directory
location. In other words, only one installation directory can be licensed at one
time. The existing license database does not allow overwriting. Therefore, it is
necessary, before running the installation routine, to remove the original license
details and other peripheral files from the system. As the root user, remove the
following directories:
/var/aslmfsem /var/mfaslmf
and the file:
/etc/sundir
Now installation can continue as normal; the license database is automatically
configured to reflect the new location of the SunSystems 4.2.6 software.
To allow multiple SunSystems installations to coexist successfully on a single
system, it is necessary to utilise the same license database for each installation
required. This is achieved by first removing the files described in step 1 above.
F Note: This has an impact on any operating editions of SunSystems. It is

therefore advised to avoid this procedure if any edition is in use.

Next, additional software is installed in the required location(s). Finally, the original
$SUNDIR/bin/SUN script is edited in the following manner:
The line that reads COBDIR= identifies the runtime directory of the original install
e.g. COBDIR=/home/firstsun426.
This entry needs to be updated so that the COBDIR variable is set to identify the
runtime directory of the new SunSystems installation. For example, if the original
install was located in /home/firstsun426, and the new software is found in
/home/new426, the COBDIR value is reset to:
COBDIR=/home/new426/lib/cobol
F Note: This operation is required for every subsequent install on the system.
If the latest edition installed is removed for any reason, then the database becomes
invalid. The SunSystems administrator must reinitialise the database to license
the remaining installations.
Reinitialising the Database

1 Logged in as root, locate the required runtime system. Set COBDIR to point to
this directory. Then run:
$COBDIR/apptrack
2 Select option 4 - License uninstall.
3 Then select option 9 - Quit.
4 Next, set and export the environment variable COBSES.
This is -f$SUNDIR/etc/asadmin.key
$SUNDIR should be replaced with the actual path of the primary SunSystems
install.
5 Run $COBDIR/apptrack again. This automatically installs the license key
and binds it to the current COBDIR directory. Now immediately unset the
COBSES variable. Running apptrack again verifies the new license database
details and the directory it is bound to.
All $SUNDIR/bin/SUN scripts need to be amended to reflect the new COBDIR
value.
Appendix H: Cobol Run-time Licensing 109

Index
Index page numbers shown in bold refer E
to SunSystems functions.
emulation 104
environment variable 35, 37, 51
A error messages 84
escape sequences 39, 52
administrator database 58 exporting 64
ANSI 102
archive files 22 F
ASCII text file(s) 30, 64
file
B names 68
owners 44
backup files 30, 82 status codes 84
base language 10 File Backup/Restore 22, 30
bespoke formatters 23, 26 File Creation 42
BFILES.EXE 106 Fixed Asset Register 30
budget files 22, 26 FreeFormat 27, 31
Business Analyser 106 FTP 106
function keys 38
C
Chart of Accounts 28 G
chmod command 44 groups 44
COBOL 51, 69
Switch 36 H
colour terminals 38
company name 29 hardware requirements 5
configuring highlighting 37
terminals 37, 102 HP9000 102
Corporate Allocations 30
cursor addressing 37 I
D importing transactions 64
installation
data file 25
dictionary 29, 80 script 32
files 80 installing the SunSystems manuals 3
Database Definitions 25 Inventory Control 30
demonstration databases 10, 22 Inventory Control data file 30
disk(s) space 5 issue media 21
Document Definition 22 Item Records 28
documentation 1
J
Journal Hold file 26
Journal Import 64
Index i
K R
keybcf utility 39 reference file 30
keyboard mapping 35 report
definition 28
L format file 26
Report Definition 22, 80
Ledger Accounting 30 root user 7
ledger file 30 run time system errors 84
licensing 21
log files, checking for errors 14 S
login screen 41
Sales Order data file 30
M Sales Order Processing 30
screen handling 102
mapping script(s)
keyboards 40 files 11
terminals and keyboards 35 running 13
memory requirements 5 supplied with SunSystems 12
modules, SunSystems 29 security 22, 32
multi serial number 29
lingual 25, 26 serialisation 29, 42, 43
volume backups 23 Service Packs 11
setting up 7
N shell script 34
number of users 29 spooling 31
SQL clause 101
O SSDDICTY 29, 80
SSFORMAT 22, 26
Online Help 2 SSINSTAL 25, 80
operator SSISSUE.MDF 27
Id 41 SSREPORT 22, 26, 29, 80
password 41 SSSYSTEM 29, 80
permissions 42 SSWM 31
Operator Definitions 42, 46 SSWN 31
Operator Permissions 27 STANDARD.MDF 27
Oracle Start of Session command 11
Scripts, Amending 14 stock take files 30
owners of files 44 stored report files 31
SUN.INI 32, 33
P SunBusiness 21, 64
suninstall script 32
path names 32 SunSpool script 23
PC, UNIX emulation on 38 SunSystems web site 3
performance 58 SuperUser SUN 24, 41, 42
Period Cleardown 22 support files 78
permissions 32, 44 system administrator 7
print file(s) 31, 82 system file 29
Printer Command Language (PCL) 50
Printer Definitions 42, 51, 54
printers 52
Process Manager 106
program files 68, 78
Purchase Order data file 30
Purchase Order Processing 30
ii SunSystems UNIX Oracle Platforms Manual Version 4.2.6

T
temporary files 31
TERM environment variable 37
terminal
control strings 37
emulations 38
mapping 35
Terminal Definitions 38, 42
terminfo file 104
text editor 30
tic command 104
transfer file 64
Transfer In/Out 23
U
umask command 44
UNIX editor 50
upgrading SunSystems 21
V
version of SunSystems 21
W
word processor 30, 50
work file(s) 31, 83
Index iii

SunSystems SunAccount Version 426 UNIX Oracle Platforms 8

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SunSystems SunAccount Version 426 UNIX Oracle Platforms 8

Uploaded by

Copyright:

Available Formats

SunSystems 4

UNIX Oracle Platforms

Systems Union Holdings Ltd

All trademarks mentioned are the products of their owners

Preparing the Environment ....................................................... 7

Tablespace Independence for SunSystems Databases .......... 17

Upgrading SunSystems .......................................................... 21

Files and Directories ............................................................... 29

Using SUN.INI ......................................................................... 33

Logging in to SunSystems ...................................................... 41

File Permissions and Ownership ............................................. 44

SunSystems Graphical Client ................................................. 45

Printing from SunSystems ....................................................... 50

Oracle Administration and Maintenance Tasks ....................... 58

Appendix B: File and Table Names ......................................... 68

Appendix C: Error Messages .................................................. 84

Appendix D: Database Overview .......................................... 100

Appendix E: Machine Variations ........................................... 102

Appendix F: terminfo ............................................................. 104

Appendix G: Enabling Business Analyser ............................. 106

Appendix H: Cobol Run-time Licensing ................................. 108

SunSystems UNIX Oracle Platforms Manual Version 4.2.6

THE SUNSYSTEMS PLATFORM MANUALS

THE REFERENCE MANUAL

Each SunSystems and SunAccount or SunBusiness function is presented in

The Appreciation Guide describes the scope of SunAccount or SunBusiness. It is

THE DEMONSTRATION DATABASE

THE TECHNICAL REFERENCE MANUAL

The Technical Reference Manual is geared to the more technical user of

2 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

THE ISSUE MEDIA

SunSystems for UNIX Oracle is supplied on CD only.

4 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

SERVER DISK SPACE

Hardware and Software Requirements 5

6 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

Operating System Setup

Preparing the Environment 7

RUNNING THE INSTALLATION SCRIPT

The installation script is used to install SunSystems. In the example below it is

8 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

F Note: The CD device name <CD-DEVICE> should be replaced with the

The Demonstration Database

10 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

Copying the SUN File to /usr/bin

Starting Communication Processes CCITCP2 and SSMASTER

Installing Service Packs

F Note: Distributing I/O across disks can produce significant performance

Oracle Scripts Supplied with SunSystems

F Note: In the scripts below the examples refer to <ORACLE_SID>. This is

12 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

Running the Oracle Scripts

AMENDING SCRIPTS FOR ORACLE 9.2.0.3.0 OR HIGHER

F Note: SunSystems does not support versions of Oracle 9i prior to Oracle

OFA-Compliant Directory Tree of Sample SunSystems Database

14 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

Oracle Database Creation Scripts

16 SunSystems UNIX Oracle Platforms Manual Version 4.2.6

Tablespace Independence for SunSystems Databases 17

File System (Program Directory)

Tablespace: SUNCOMP1 Tablespace: SUNCOMP2

SALFLDGEM SALFMSC SALFLDGEM SALFMSC

US1 ??????? SUNCOMP1 SUNROLE

18 SunSystems UNIX Oracle Platforms Manual Version 4.2.6