How 2 Know
If you can't Google it, You Can Knowing it.

Archive for the ‘Information Management’ Category

Volume Group Characteristics

Friday, February 13th, 2015

You can find below the meaning of each parameter on Volume Group Characteristics (the output from lsvg vg command):

 

  1. Volume Group: Name of Volume Group.
  2. VG State: active/partial. Partial indicates that some of the Physical Volumes in the Volume Group are not active.
  3. VG Permission: It indicates if the volume group is read-only or read-write.
  4. Max LVs: Maximum number of Logical Volumes allowed in Volume Group.
  5. LVs: Total number of Logical Volumes at present in Volume Group.
  6. Open LVs: Number of LVs open at present in the Volume Group for any Read Write operation.
  7. Total PVs: Total number of Physical Volumes present in Volume Group.
  8. Stale PVs: How many stale Physical Volumes are there in Volume Group. The stale Physical Volumes are those ones on which I/O operations are not possible.
  9. Active PVs: Total number of Physical Volumes which are active in Volume Group.
  10. Max PPs per VG: Maximum no. of Physical Partitions which can be there in the Volume Group.
  11. Max PPs per PV: Maximum number of Physical Partitions which can be there in Physical Volume.
  12. VG Identifier: The very long string to identify Volume Group.
  13. PP Size: The size of Physical Partition used in every Physical Volume of Volume Group.
  14. Total PPs: Total number of Physical Partitions in Volume Group.
  15. Free PPs: Total number of free Physical Partitions with in Volume Group.
  16. Used PPs: Total number of Physical Partitions in use in Volume Group.
  17. Quorum: Whether the quorum is on or not in Volume Group.
  18. VG Descriptors: Number of Volume Group Descriptor Areas(VGDA) in Volume Group.
  19. Stale PPs: How many Physical Partitions are stale or unable to perform I/O operations.
  20. Auto On: Whether the Volume Group will varyon on system startup or not.
  21. Max PVs: Maximum number of Physical Volumes allowed in this Volume Group.
  22. Auto Sync: Whether this Volume Group should sync automatically or not.
  23. BB Policy: Its bad block relocation policy. So, this value here is relocatable, that means we are allowed to relocate bad blocks in this Volume Group if need be.

Continue Reading…

Error: 1601, Severity: 17-Sybase

Thursday, May 16th, 2013

Error Explanation

There are not enough ‘user connections’ available to start a new process. Retry when there are fewer active users

Recommended Solution

1. Determine the current number of user connections configured: by using the following command
Continue Reading…

How to increase size of Sybase database on UNIX platforms ?

Tuesday, March 26th, 2013

Issue 

I have problem in size of database because the free space of the database is less than specific percentage of total space.

Cause

Users used to update in the database and that lead to increase used space of this database
Continue Reading…

Common Error Codes in DB2 for Z/OS

Sunday, March 24th, 2013

When DB2 executes SQL statements, it returns the results of the operation into the SQLCODE and SQLSTATE fields in the SQLCA. SQLCODE provides key information about the success or failure of SQL statement execution.

Continue Reading…

VSAM for z/OS

Saturday, March 23rd, 2013

Do you ever think to compress VSAM dataset?

Do you know how to enable SMS on your z/OS system?

Do you know how to start SMSVSAM Server?

How convert non-sms volume to sms managed volumes?

Do you know how to enable VSAM RLS on your SYSPLEX system?

Continue Reading…

DB2 for z/OS Common Rules

Saturday, March 23rd, 2013

Rule 1:  Don’t Grant any DB2 Object for PUBLIC, you don’t know who will use this authority and get access to your DB2 subsystem.

Rule 2: Grant access to DB2 objects according to need to know concept, don’t give extra authority unless it is business need.

Continue Reading…