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

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 userConsider below Table :
Create Table SAMP_TABSN CHAR (10) SNAME CHAR (10) STATUS CHAR (2) NOT NULL BY DEFAULTCITY CHAR (10) NOT NULL
Note :: Unless you specify NOT NULL, the default is to allow for NULLIn 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 Program as

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 valueTake the Offset Value 000003C0Got 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 shotsThis 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 This 045 pints to the Move statement 1526, this is the exact line in the programCheck 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 explain one ca…

DB2 Utilities and Commands (helpful for DB2 Certification)

• Utilities
– Image Copy
– CDB SuperCopy
– Quiesce
– Load
– CDB SuperLoad
– Check
– BSCTIAUL
– CDB SuperUnload
– Recover
– CDB SuperRestore
– Reorg
– CDB SuperReorg
– Runstats
– Report Recovery
– Repair

• Commands
– Display/Stop/Start Database
– Display/Term Utility


DB2 Logging

• DB2 Logs
– A ‘journal’ of all activity for a subsystem
– Undo/redo records for table updates
– Each event in the log is identified by its RBA(relative byte address)
– RBA denotes a point in time: the greater the RBA, the later in time the event occurred
– Data Sharing - LRSNs along with RBAs

– Some events:
• Full image copy
• Quiesce
• Load


Data Sharing

• Benefits of Data Sharing
– High availability
– Workload balancing
– Sysplex parallelism
– Better use of resources


Backing Up Tables

• Image Copy
– Backup for DB2 table spaces
– Can also copy index spaces
– Can perform full (all data) or incremental (changed data) copies
– Can prevent or allow updates by others during copy
– SAMPLIB: DB2COPY

• CDB SuperCopy
– Faster method of creating stan…