AIX

• To login in:

Login id: <username>

Password: <the password does not appear>

• To log out:

$ <ctrl+d> (or)

$ <exit> (or)

$ logout

• AIX is designed as a multiuser system, a level of security is implemented to control access. Each user of the system has a user name and associated password (optional).

• If the user ID requires a password, the system will prompt for the password in a similar manner. While the user is typing a password, it does not appear on the screen.

• To terminate the session the user may either enter the exit or logout command, or press the key combination <Ctrl-d> (holding down the Ctrl key while pressing the d key.) logout only works if you are in your login shell.

SMIT is the System Management Interface Tool for AIX. It allows a user to navigate a menu hierarchy of commands, rather than using the command line. Invocation is typically achieved with the command smit. Experienced system administrators make use of the F6 function key which generates the command line that SMIT will invoke to complete the proposed task. SMIT also generates a log of commands that are performed in the smit.script file. The smit.script file automatically records the commands with the command flags and parameters used. The smit.script file can be used as an executable shell script to rerun system configuration tasks. SMIT also creates the smit.log file, which contains additional detailed information that can be used by programmers in extending the SMIT system.

The following are some unique system management features of AIX.

☛ Logical Volume Manager :- The Logical Volume Manager (LVM) maintains the hierarchy of logical structures that manage disk storage.

☛ System Resource Controller:- The System Resource Controller (SRC) provides a set of commands and subroutines for creating and controlling subsystems and is designed to minimize the need for human intervention in system processing.

☛ Object Data Manager :- The Object Data Manager (ODM) is a data manager intended for the storage of system data.

☛ Software Vital Product Data:- Certain information about software products and their installable options is maintained in the Software Vital Product Data (SWVPD) database.

☛ Workload management :- Workload Manager (WLM) is designed to provide the system administrator with increased control over how the scheduler virtual memory manager (VMM) and the disk I/O subsystem allocate resources to processes. You can use WLM to prevent different classes of jobs from interfering with each other and to allocate resources based on the requirements of different groups of users.

☛ Operating system updates:- The operating system package is divided into file-sets, where each file-set contains a group of logically related customer deliverable files. Each file-set can be individually installed and updated.

A file is a collection of data, stream of characters or a byte stream. No structure is imposed on the file by OS. The various file types are as follows:

• Ordinary (text or code data)

• Directory (table of contents, that stores a list of files within that directory)

• Special files(representing hardware or logical devices)

An ordinary file can contain either text or code data. Text files are readable by a user and

can be displayed or printed. Code data, also known as a binary file is readable by the

computer. Binary files may be executable. Directories contain information the system needs to access all types of files, but they do not contain the actual data. Each directory entry represents either a file or a subdirectory.Special files usually represent devices used by the system.

The man command will look in the on-line manual for information on the commands, subroutines and files with the name title. This information will be presented on the screen one page at a time for the user to browse.

The information consists of:

PURPOSE : The title and a one-line description of the command

SYNTAX : The syntax of the command

DESCRIPTION : Many pages of information about the function and usage of the

command with examples

FLAGS : Description of available options

FILES : Any system files associated with the command

RELATED INFO : The names of any related commands

BUGS : Any information about the behavior/performance of the command in unusual circumstances

$ man <command for which you want the information>

There are two methods for configuring a read/write optical drive. The read/write optical drive must be connected to the system and powered on.

☛ Method 1:-Method one is the faster of the two methods. It only configures the read/write optical drive specified. To use this method, you must provide the following information:

Subclass Defines how the drive is attached.

Type Specifies the type of read/write optical drive.

Parent Name Specifies the system attachment the drive is connected to.

Where Connected Specifies the logical address of the drive.

Enter the following command to configure the read/write optical drive:

mkdev -c rwoptical -s Subclass -t Type -p ParentName -w WhereConnected

The following is an example of a read/write optical drive that has a SCSI ID of 6, a logical unit number of zero, and is connected to the third (scsi3) SCSI bus:

mkdev -c rwoptical -s scsi -t osomd -p scsi3 -w 6,0 -a pv=yes

Method of Configuration Manager, searching the current configuration, detecting any new devices, and automatically configuring the devices. This method is used when little information is known about the read/write optical drive.

a)Use the configuration manager to configure all newly detected devices on the system (including the read/write optical drive) by typing:

cfgmgr

b)Type the following command to list the names, location codes, and types of all currently configured read/write optical drives:

lsdev -C -c rwoptical

c)Determine the name of the newly configured read/write optical drive using the location code that matches the location of the drive being added.