Unix
Unix
Unix
AIM- Introduction to UNIX Operating system system and its File system.
OBJECTIVE- To understand the concept of UNIX Operating system and its Installation.
THEORY-
Multitasking: A UNIX operating system is a multitasking operating system that allows you to
initiate more than one task from the same terminal so that one task is performed as a foreground
and the other task as a background process.
Multi-user: UNIX operating system supports more than one user to access computer resources
like main memory, hard disk, tape drives, etc. Multiple users can log on to the system from
different terminals and run different jobs that share the resources of a command terminal. It deals
with the principle of time-sharing. Time-sharing is done by a scheduler that divides the CPU
time into several segments also called a time slice, and each segment is assigned to each user on
a scheduled basis. This time slice is tiny. When this time is expired, it passes control to the
following user on the system. Each user executes their set of instructions within their time slice.
Portability: This feature makes the UNIX work on different machines and platforms with the
easy transfer of code to any computer system. Since a significant portion of UNIX is written in C
language, and only a tiny portion is coded in assembly language for specific hardware.
File Security and Protection: Being a multi-user system, UNIX makes special consideration
for file and system security. UNIX has different levels of security using assigning username and
Command Structure: UNIX commands are easy to understand and simple to use. Example:
"cp", mv etc. While working in the UNIX environment, the UNIX commands are case-sensitive
and are entered in lower case.
Open Source: UNIX operating system is open source it means it is freely available to all and is
a community-based development project.
Accounting: UNIX keeps an account of jobs created by the user. This feature enhances the
system performance in terms of CPU monitoring and disk space checking. It allows you to keep
an account of disk space used by each user, and the disk space can be limited by each other. You
can assign every user a different disk quota. The root user can perform these accounting tasks
using various commands such as quota, df, du, etc.
While working with UNIX OS, several layers of this system provide interaction between
the pc hardware and the user. Following is the description of each and every layer
structure in UNIX system:
Layer-2: Kernel -
The core of the operating system that's liable for maintaining the full functionality is
named the kernel. The kernel of UNIX runs on the particular machine hardware and
interacts with the hardware effectively.
It also works as a device manager and performs valuable functions for the processes
which require access to the peripheral devices connected to the computer. The kernel
controls these devices through device drivers.
The kernel also manages the memory. Processes are executed programs that have
owner's humans or systems who initiate their execution.
The system must provide all processes with access to an adequate amount of memory,
and a few processes require a lot of it. To make effective use of main memory and to
allocate a sufficient amount of memory to every process. It uses essential techniques like
paging, swapping, and virtual storage.
It also keeps a history of the list of the commands you have typed in. If you need to
repeat a command you typed it, use the cursor keys to scroll up and down the list or
type history for a list of previous commands. There are various commands like cat, mv,
cat, grep, id, wc, and many more.
o Bourne Shell: This Shell is simply called the Shell. It was the first Shell for UNIX OS. It is
still the most widely available Shell on a UNIX system.
It is the outermost layer that executes the given external applications. UNIX distributions
typically come with several useful applications programs as standard.
For Example: emacs editor, StarOffice, xv image viewer, g++ compiler etc.
Installation on UNIX –
To perform this step, you must be either the user "sag" or a member of the
group "sag" to which the administrator and all users of Software AG products
are assigned. Do not perform this step as the user "root".
Note:
The following descriptions of installation steps assume that the graphical
installation mode is used. The step sequence is the same in character mode.
The setup program is started and guides you through the installation. During
installation you have to provide the license key.
Notes:
Note:
If you run the installation procedure in character mode, at each command
prompt, you must type in the exact wording (for example: "accept" for
"accept", not just "y" or the ENTER key).
In this screen, you can change the value of the $SAG environment variable,
which is the path of the directory tree where all Software AG products are
installed.
In this screen, you can specify the directory of the license file.
Note:
By default, your-current-directory/common/LKey/prd46.xml is displayed.
1. If you do not want to use the displayed license file, specify the path to your
license file.
Or:
Choose the Browse button to select the license file.
This screen, which contains a progress indicator, informs you about the
installation status. Please wait until the selected components have been
installed.
In this screen, you can specify the version of either your Natural ($NATVERS)
or Adabas ($ADADIR/$ADAVERS) environment or specify both.
Notes:
In this screen, you can specify an existing Natural parameter module which will
be used as template for a new Predict parameter module.
1. Select NATPARM from the selection box if you want to use the
NATPARM module without changing FNAT/FUSER settings.
Note:
You can choose the command button displaying a magnifying glass to
display the contents of the currently selected parameter file.
In this screen, you specify whether you are installing Predict for the first time,
or updating an older Predict version already installed on your machine.
Note:
This screen is omitted, if you install Predict for the first time into an
environment where Predict has not been installed before. In this case, the
installation process continues with Step 14.
In this screen, you can specify which steps are performed during
postinstallation.
1. You can specify that the Predict System File shall be created
Or:
You can specify that you want the Predict modules to be installed.
Or:
You can specify both of the above options.
Notes:
In this screen, you can select the database ID (DBID) for your Main FDIC
system file and you can enter the file number (FNR) for your Main FDIC
system file.
Note:
This screen is skipped if the selected parameter module contains an FDIC
specification.
In this screen, you can select the database ID (DBID) for your Coordinator
FDIC system file and you can enter the file number (FNR) for your
Coordinator FDIC system file.
This screen, which contains a progress indicator, informs you about the load
status. Please wait until the Predict modules have been loaded.
In this screen, you can choose to perform or not to perform optional installation
steps. Depending on the installation type, all of the steps displayed below are
performed automatically in the order given.
1. Steps to be performed:
Back up the existing FDIC file (step is performed only when using an
existing FDIC file for the installation).
Convert the FDIC file from Version 4.5 to Version 4.6 (step is
performed during an upgrade installation only).
Update the Predict Metadata.
Define the Coordinator FDIC in the new SYSDIC (step is performed
during a new or partly installation only).
Load the Predict description of the Predict system file.
Load the Predict example data.
Adapt the Text Modules in Library SYSEXT.
In this screen, you can specify whether you want to view the Readme file. By
default, the confirmation box is checked. Uncheck the box if you do not want to
view the Readme file.
VIVA QUESTIONS-