Skip to main content

Why DB2 and why not VSAM (DB2 Vs VSAM)?

Why DB2 and why not VSAM (DB2 Vs VSAM)?



This is the common query raised by the programmers, whether to go with DB2/VSAM, hope below information helps.


VSAM

DB2

Definition

Database with file Concepts

Database built on File management storage system-DBMS concepts




Security levels

Provides at Dataset level only

Provides Good security levels at various levels (like table, table space etc.,)




Data Maintenance

It’s difficult compared to DB2.

Data retrieval or insertion or updates etc, is a bit difficult (puts more burden on programmer to achieve this).

Simply speaking Query interface is not supported

It’s easy to maintain data by using SQL

Data retrieval or insertion or updates etc, is far easier using SQl .

Query interface is supported




Referential Integrity

Again it programmers responsibility to design it accordingly

It’s one of the feature of DB2




Recovery

Recoverable only from Backup file

Auto recovery is not possible

Recoverable from DB2 log/ Backup

Auto recovery is possible




Backup

Incremental backup is not supported.

Incremental backup is supported




Performance

Performance is better than DB2, when small amount of data is used by the transaction

DB2 has good performance over VSAM, when high volume of data is used by the transactions




Accessible

Mainframes only

Can be shared with Distributed systems

Comments

Post a Comment

Popular posts from this blog

NULL VALUES and NULL INDICATORS in DB2

In DB2, the columns defined as NULL needs to be handled carefully else it will throw null exception error, in order to over come this error data type can be handled by using null indicator . NULL is stored using a special one-byte null indicator that is "attached" to every nullable column. If the column is set to NULL, then the indicator field is used to record this. Using NULL will never save space in a DB2 database design - in fact, it will always add an extra byte for every column that can be NULL. The byte is used whether or not the column is actually set to NULL. The indicator variable is transparent to an end user Consider below Table : Create Table SAMP_TAB SN CHAR (10) SNAME CHAR (10) STATUS CHAR (2) NOT NULL BY DEFAULT CITY CHAR (10) NOT NULL Note :: Unless you specify NOT NULL, the default is to allow for NULL In above table SN and SNAME columns holds null values by default, in order to handle these null variables we need to have NULL-INDICATORS declares in the Pro
15 comments
Read more

Mainframe Written test @ Accenture

1. What r the 2 function we can get by using INSPECT verb? (c) A. file handling, error handling B. opening a file, closing a file. C. char counting, replacing. D. none of the above 2. Indicate which of the following is not true about the formal parameters in a subroutine? (c) A. every formal parameter must appear in the linkage section of the subroutine B. every formal parameter must appear in the using phrase of the procedure division header of the subroutine C. A formal parameter name can appear more than once in the using phrases of the procedure division header of the subroutine. D. A formal parameter can not be declared with value clause in a subroutine 3. What is the value of A? (B) 01 A pic 9(3). Move 100 to A. Perform 1000-para thru 1000-exit. Display the value of a=A Stop run. 1000-para. If A=100 Perform 1000-exit Else Move 150 to A End-if. Move 200 to A. 1000-exit. Exit. a.100 b.200 c.150 d. none of the above is correct. 4. What is the value of B? (A) Move 1 to A Evaluate tr
2 comments
Read more

How to Solve SOC7 Abend - with screen shots

Below process helps to find out the statement, caused the SOC7 error. Check the Sysout of RUNJCL . This shows the error statement and lists offset value Take the Offset Value 000003C0 Got to respective Compilation Job listing, check the sysprint Search for the offset value 0003C0 (delete +00 -- initial 3 letters of Offset value and search for it) check below 2 screen shots This Offset value is listed under line no 0045 – which refers to Move statement. Take this no. 045 and find for it in same sysprint. This points to the exact statement, caused SOC7 T his 045 pints to the Move statement 1526, this is the exact line in the program Check for the above line no. In source program . This points to the statement highlighted below . Check the statement, variable check-4, which is added to check-6. These are having different Picture clause. check-4 is alfhanumaric, holding some junk data, when this data is moved to Chcek-6 variable(of comp-3) creates SOC7 error. This is just an example to e
16 comments
Read more