DB2 Commands.ppt

© 2003 IBM Corporation
Introduction to DB2
Utilities
Mmanish kumar
Rajarshi Das / S.N.
Moitra
Santosh Patel
28th June 2017

DB2 Command
DB2 ZOS Commands are user to execute database administration functions. Db2
Supports several different types of commands –
• The DSN commands and its subcommands -
DSN is the DB2 command processor and executes as a
TSO command processor.
• DB2 Commands –
You can use DB2 commands to control most of the
operational environment.
• IMS Commands –
You can use IMS commands to control IMS connections
as well as to start and stop connections to DB2 and
display activity on the connections.
• CICS Attachment facility commands
You can use CICS commands to control CICS
connections as well as to start and stop connections to
DB2 and display activity on the connections.

The DSN command and its subcommands
Environment: All of the DSN subcommands, except SPUFI, run under DSN in
either the foreground or background, and all, except END, also run under DB2
Interactive (DB2I). SPUFI runs only in the foreground under ISPF.
BIND PACKAGE (DSN) The DSN subcommand BIND PACKAGE builds an
application package. DB2 records the description of the
package in the catalog tables and saves the prepared
package in the directory.
BIND PLAN (DSN) The DSN subcommand BIND PLAN builds an application
plan. All DB2 programs require an application plan to
allocate DB2 resources and support SQL requests made at
run time.
DSN (TSO) The TSO command DSN starts a DSN session.
END (DSN) The DSN subcommand END is used to end the DSN
session and return to TSO.

DB2 commands
Environment: The command START DB2 can be issued only from a z/OS
console.
All other DB2 commands can be issued from the following environments:
• A z/OS console or application program
• A DSN session
• A DB2I panel
• An IMS terminal
• A CICS terminal
• An application program, using the DB2 instrumentation facility interface
(IFI)
DB2 commands that are issued from a logged-on z/OS console or TSO
SDSF can
be checked by DB2 authorization using primary and secondary authorization
IDs.

DB2 command parsing
All of the DB2 and related commands have a similar structure that is
necessary to execute valid commands.
The following figure illustrates the pattern of DB2 commands.
-DISPLAY DATABASE(J64DBASE),SPACENAM(PROJ32)
Recognition character - (-)
Command -- DISPLAY
Primary keyword-- DATABASE
Value - J64DBASE
Value -- PROJ32
Keyword - SPACENAM
Separators -- (,)

Scope of DB2 and related
commands
All commands have one of the following scopes:
Member or Local
Many commands used in a data sharing environment have member (or
local) scope because they affect only the DB2 subsystem for which they are
issued. For example, a CANCEL THREAD command cancels the specified
threads for the member that is identified by the command prefix.
Group
Other commands have group scope because they affect an object in such a
Way that affects all members of the group. For example, a STOP
DATABASE command issued from any member of the group stops that
database for all members of the group.

Scope of DB2 Commands Cont..-
The following commands have group scope:
ALTER GROUPBUFFERPOOL (DB2)
BIND PACKAGE (DSN)
BIND PLAN (DSN)
DCLGEN (DSN)
DISPLAY DATABASE (DB2)
DISPLAY GROUP (DB2)
DISPLAY GROUPBUFFERPOOL (DB2)
FREE PACKAGE (DSN)
FREE PLAN (DSN)
MODIFY irlmproc,DIAG (z/OS IRLM)
REBIND PACKAGE (DSN)
REBIND PLAN (DSN)
REBIND TRIGGER PACKAGE (DSN)
START DATABASE (DB2)
STOP DATABASE (DB2)

The following commands have either group or member scope, depending on
which options you specify with them:
ARCHIVE LOG (DB2)
DISPLAY FUNCTION SPECIFIC (DB2)
DISPLAY PROCEDURE (DB2)
DISPLAY THREAD (DB2)
DISPLAY TRACE (DB2)
DISPLAY UTILITY (DB2)
MODIFY irlmproc,SET (z/OS IRLM)
MODIFY irlmproc,STATUS (z/OS IRLM)
START FUNCTION SPECIFIC (DB2)
START PROCEDURE (DB2)
START TRACE (DB2)
STOP FUNCTION SPECIFIC (DB2)
STOP PROCEDURE (DB2)
STOP TRACE (DB2)
TERM UTILITY (DB2)
Scope of DB2 Commands Cont …-

Business Unit or Product Name
Presentation Title | Presentation Subtitle | Confidential © 2002 IBM Corporation
9

10
Login using IBMUSER and SYS1

11
How to check – DB2 up and running

12

13
Select DB9G

14
These Jobs shows that Db2 is up and running

15
How to execute Db2 Commands

16
Check for SSID

17
SSID should be DB9G

18
Change DB8G to DB9G, hit enter twice

19
Now SSID would be DB9G

20
DB2 Command Line

21
This is DB2 Command Line processor

22
Access Command

23
Normal Completion

24
Non group buffer pool dependent MODE(ngbpdep)

25
Alter Bufferpool Command

26
Successful Completion

27
Alter GBP

28

29
Archive Log

30
Archive Log offload

31

32

33
Display Archive

34
Display Archive Log

35
Display bufferpool

36
Display Bufferpool

37
Display * will show all inactive BP as well

38
Display GBPOOL

39
Only valid for Data sharing

40
Display Database

41

42
Display a particular database

43

44
Display Claimers Information

45

46
Display Claimers of a Tablespace

47

48
Display DDF ( Distributed Data Facilities )

49

50
Deisplay DDF detailed report

51

52
Display Function Specific

53
Display Group

54

55
Display Location

56

57
DISPLAY LOG

58

59
Display Proc

60

61
Display Thread

62

63
Display utility

64

65
Recover INDOUBT thread

66

67
Recover Postponed

68

69
Set Archive

70
Set Archive

71
Set Log

72
Set Log

73
Set Sysparm

74

75
Stop Database

76

77
Start Database

78
Start Database

79
Start Db2

80
Start Db2

81
Stop Db2

DB2 Commands.ppt

More Related Content

Similar to DB2 Commands.ppt (20)

Recently uploaded (20)

DB2 Commands.ppt