Skip to main content

SYSTEM CALL.............


System calls:

                                  System calls provide the interface between a process and the operating system. These calls are generally available as assembly-language instructions, and they are usually listed in the various manuals used by the assembly-language programmers. Certain system allow system calls to be made directly from a higher level language program, in which case the calls normally resemble predefined function or subroutine calls. They may generate a call to a special run-time routine that makes the system call, or the system call may be generated directly in line.
             How system calls are used, consider writing a simple program to read data from one file (input file) and to copy them to another file (output file). In an interactive system, this approach requires a sequence of system calls. First system call is to write a prompting message on the screen, then to read from the keyboard the characters that define the two files. Once the two file names are obtained, the program must open input file and create output file. Each of these operations require another system call. 
Various type of system calls are following:
  • Process control
  • File management
  • Device management
  • Information maintenance
  • Communications

Function of process control:
  • Process control performs abort or end of program.
  • It executes and loads the program.
  • The process should be created and terminated by the process control.
  • Process control system calls set and get process attributes.
  • Process control perform wait and signal event function.
  • Process control perform wait for time function and allocate the memory to program.

Function performs by file management:
  • File management performs read, write and repositioning of the program.
  • The creation and deletion of file function should be performed by the file management.
  • Set and get process attributes function also performed by the file management.
  • Open and close of the program/file function occurred by file management.
Function performs by device management:
  • Device logically attachment and detachment function performed under device management.
  • The request and release of device function performs by the device management.
  • Device management performs the set and get device attributes function.
  • Read, write and reposition of the devices should be performs by device management.

Function of communication:
  • Communication system calls perform creation and deletion communication connection.
  • Send and receive massages function performed by the communication system calls.
  • Transfer status information and attach or detach remote devices function performed by the communication system calls.

Function of information maintenance:
  • Information maintenance system calls perform set or get time or date.
  • System date should be set or get by the information maintenance system calls.
  • The attributes of the process, file and device are set and get by the information maintenances.

Comments

Popular posts from this blog

Standard and Formatted Input / Output in C++

The C++ standard libraries provide an extensive set of input/output capabilities which we will see in subsequent chapters. This chapter will discuss very basic and most common I/O operations required for C++ programming. C++ I/O occurs in streams, which are sequences of bytes. If bytes flow from a device like a keyboard, a disk drive, or a network connection etc. to main memory, this is called   input operation   and if bytes flow from main memory to a device like a display screen, a printer, a disk drive, or a network connection, etc., this is called   output operation . Standard Input and Output in C++ is done through the use of  streams . Streams are generic places to send or receive data. In C++, I/O is done through classes and objects defined in the header file  <iostream> .  iostream  stands for standard input-output stream. This header file contains definitions to objects like  cin ,  cout , etc. /O Library Header Files There are...

locking

DBMS Locking Part I (DBMS only) TECHNICAL ARTICLES -> PERFORMANCE ARTICLES [  Back  ] [  Next  ] DBMS is often criticized for excessive locking – resulting in poor database performance when sharing data among multiple concurrent processes. Is this criticism justified, or is DBMS being unfairly blamed for application design and implementation shortfalls? To evaluate this question, we need to understand more about DBMS locking protocols. In this article, we examine how, why, what and when DBMS locks and unlocks database resources. Future articles will address how to minimize the impact of database locking. THE NEED FOR LOCKING In an ideal concurrent environment, many processes can simultaneously access data in a DBMS database, each having the appearance that they have exclusive access to the database. In practice, this environment is closely approximated by careful use of locking protocols. Locking is necessary in a concurrent environment to as...

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE Customers exploring the field of business intelligence for the first time often lead with: What is the difference between a data warehouse and a data mart? The next question follows as predictably as night follows day: which one does my company need? Let me start by saying that the two terms are often confused. Indeed, some people in the industry use them virtually interchangeably, which is unfortunate, because they do reflect a valuable hierarchical difference. The Data Warehouse A "data warehouse" will typically contain the full range of business intelligence available to a company from all sources. That data consists of transaction-processing records, corporate and marketing data, and other business operations information; for example, a bank might include loans, credit card statements, and demand deposits data, along with basic customer information. This internal data is frequently combined with statistica...