Use these tools to manage database console-related information and activities. Console management tools include capabilities that will allow you to view what is happening on a database machine, as well as feed input directly to the database console, if required.
Full understanding of the capabilities of the tools included in this chapter is essential knowledge for those persons designated as Control Center database administrators or Control Center administrators.
Use the View Message Log tool to display database console messages that are recorded and maintained by the product. Console messages for all database console activities such as archiving, adding/deleting dbextents, and cold logging are logged by the product for all databases. In addition, any communication messages the product issued to the databases are logged.
This tool will allow you to display console messages for a given period of time for a single database machine. Use this tool when you need to review database console messages for problem determination, database activity (archive, recovery) verification, monitoring current console activities, and so on.
Use of the View Log tool requires Control Center database user, operator, or greater level of authorization.
All communications between a Control Center support machine and a database virtual machine are captured through the Single Console Image Facility (SCIF) and are recorded by the product, in a log file on the machine's 191 A-disk. Refer to the DB2 Server for VM Control Center Program Directory. A new log file is created each day and is used to record a day's worth of database console messages. The product will keep as many log files as specified during the product installation process.
Each daily log file has a filename of SQLMSTR and a filetype in the format LOGyyddd, where yy is the current year and ddd is the day of the year (1 - 365). Entries are made to the SQLMSTR LOGyyddd file in a chronological order as the database console messages occur. Each entry in the log will be preceded with the date and time that the entry was made. The type of message will be indicated for each entry, such as RDR (reader file received by the product machine), MSG (message received by the product machine), or SCIF (Single Console Image Facility message received from a database machine).
When multiple database machines are managed by a single product virtual machine, the SQLMSTR LOG file will contain entries in chronological order regardless of which database is being communicated with. This causes messages from different databases to be interspersed throughout the log file, making it difficult to view all communications between the product and a single database. The View Message Log tool will filter the log file and display all messages relating to a single database machine.
Figure 238 shows the View Message Log panel, which is reached using Option V on the Control Center Main Menu.
Figure 238. View Message Log Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | |*----------------------------- View Message Log -----------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || | | || Message Lines ===> 100 ( Number of message lines to display ) | | || Log File Date ===> 97075 ( Julian Date of Message Log, today = 97075 ) | | || | | || Enter the number of lines of the Message Log file that you wish to | | || view. The lines displayed will be the most recent information within | | || the log file. | | || | | || Separate Log files are maintained for each day's communications between | | || the CTRLCTR virtual machine and the database. You may view messages | | || from a previous Message Log file by specifying the Julian date of the | | || day that you want displayed. For example, 91044 would be specified | | || to view information for the 44th day of 1991. Only a finite number of | | || log files are kept at any given time, which will limit how far back | | || you may specify for your search. | | || | | || | | |*---------------------------------------------------------------SQMLOGVW-----* | | PF: 1 HELP 3 End | | | +--------------------------------------------------------------------------------+
Figure 239 is an example of a View Message Log file. Each message in the file is preceded by the date and time that it was recorded by the product.
The example Message Log file covers the startup of the SQLDBA database. All database messages from the database are shown as message type SCIF. Other messages with message type MSG are sent to the product machine with the CP MSG command. The messages with message type CP are messages generated by VM/CP. The last message in this log listing is a product command sent from a user who requested to view the Message Log.
Userid: MSTRSRV1 Date: 03/15/97
At Node: VMSYSTM1 Time: 13:54:18
COMMAND EXECUTED: QUERY LAST 50 MESSAGES of LOG 97075
DISPLAYED: Last 50 messages between MSTRSRV and database SQLDBA on 97075
10:11:59 MSG VMSYSTM1 MSTRSRV1 LABELDEF ISSUED FOR SQLDBA: 300
10:11:59 MSG VMSYSTM1 SQLDBA SQMSTATU C SQLDBA STARTUP LOG LABELDEF
10:12:00 MSG VMSYSTM1 SQLDBA SQMSTATU C SQLDBA STARTUP TRACE LABELDEF
10:12:00 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DMSLBD441R ENTER VOLID INFORMATION:
10:12:02 CP VMSYSTM1 MSTRSRV1 HCPQCS150A USER SQLDBA HAS ISSUED A VM READ
10:12:02 MSG VMSYSTM1 SQMTAPEU SQLDBA NEW_STATUS FILDEF 200 TRACE DATA A 191
10:12:04 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0717I START SQLSTART: 03/15/97 10:12 EST.
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0320I THE DEFAULT DATABASE NAME IS SQLDBA.
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0663I FILEDEFS IN EFFECT ARE:
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: Z DISK DMSNAM LOADLIB *
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARIARCH TAP1 SL 00001 VOLID QU1405
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARILARC TAP3 SL 00001
10:12:05 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARITRAC DISK TRACE DATA A1
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARISQLLD DISK ARISQLLD LOADLIB Q1
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: BDISK DISK 300
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: LOGDSK1 DISK 201
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: LOGDSK2 DISK 202
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK1 DISK 200
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK2 DISK 204
10:12:06 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK3 DISK 220
10:12:07 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK4 DISK 221
10:12:07 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK5 DISK 222
10:12:07 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK6 DISK 223
10:12:07 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK7 DISK 224
10:12:08 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: DDSK8 DISK 225
10:12:08 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARIUSRDD DISK USERLIB LOADLIB *
10:12:09 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0025I PROGRAM ARISQLDS IS LOADED AT 856000.
10:12:09 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0025I PROGRAM ARIXRDS IS LOADED AT 6FF000.
10:12:09 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0025I PROGRAM ARIXSXR IS LOADED AT 957000.
10:12:09 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0025I PROGRAM ARICMOD IS LOADED AT 95B000.
10:12:10 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I ACCOUNT PARAMETER VALUE IS N.
10:12:10 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I DUMPTYPE PARAMETER VALUE IS P.
10:12:10 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I LOGMODE PARAMETER VALUE IS L.
10:12:11 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I STARTUP PARAMETER VALUE IS W.
10:12:11 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I SYSMODE PARAMETER VALUE IS M.
10:12:11 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I EXTEND PARAMETER VALUE IS N.
10:12:12 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I CHARNAME PARAMETER VALUE IS ENGLISH.
10:12:12 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I DBNAME PARAMETER VALUE IS SQLDBA.
10:12:12 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I PARMID PARAMETER VALUE IS SQLDBA.
10:12:13 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I TRACDSC PARAMETER VALUE IS 00.
10:12:13 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0015I TRACRDS PARAMETER VALUE IS 0000000.
10:12:13 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I ARCHPCT PARAMETER VALUE IS 79.
10:12:14 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I CHKINTVL PARAMETER VALUE IS 10.
10:12:14 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NCSCANS PARAMETER VALUE IS 30.
10:12:14 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NCUSERS PARAMETER VALUE IS 5.
10:12:15 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NDIRBUF PARAMETER VALUE IS 50.
10:12:15 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NLRBS PARAMETER VALUE IS 2520.
10:12:15 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NLRBU PARAMETER VALUE IS 1000.
10:12:16 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I NPAGBUF PARAMETER VALUE IS 100.
10:12:16 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I SLOGCUSH PARAMETER VALUE IS 90.
10:12:16 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I SOSLEVEL PARAMETER VALUE IS 10.
10:12:16 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0016I DISPBIAS PARAMETER VALUE IS 7.
10:12:17 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0283I LOG ANALYSIS IS COMPLETE.
10:12:17 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0282I LUW UNDO IS COMPLETED.
10:12:17 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0281I LUW REDO IS COMPLETED.
10:12:17 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0060I DATABASE INITIALIZATION COMPLETE.
10:12:17 SCIF VMSYSTM1 MSTRSRV1 SQLDBA: ARI0045I READY FOR OPERATOR COMMUNICATIONS.
13:54:17 MSG MSTRUSR SQMSFILE SQLDBA SQMSFILE SQLDBA MESSAGES 100 92009
|
The Issue Database Commands tool will allow you to enter any line command directly to the database machine's console, as if you were logged onto the database machine itself. Obviously, this is a very powerful and flexible capability providing direct access to your database machine's console, and should therefore be used with extreme care.
Use this tool when you need to invoke any CP or CMS commands on the database virtual machine. By using this tool, you will not need to log onto the database machine and therefore, the SCIF (Secondary Console Image Facility) link between the product and the database machine will not be broken.
Only those persons with Control Center database Administration-level or greater authorization can use this tool.
The product manages database consoles by using the Secondary Console Image Facility (SCIF). Refer to the DB2 Server for VM Control Center Program Directory. This facility gives the product control of the database virtual machine's virtual console and virtual keyboard. The Issue Database Commands tool allows authorized users to utilize this relationship.
The Issue Database Commands entry panel shown in Figure 240 is displayed when Option CO on the Database Utility Functions panel is selected. Authorized users can send any line command to the database machine through this panel.
Figure 240. Issue Database Commands Entry Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | |*----------------------------- Database Command -----------------------------* | || Option ===> CTRLID: MSTRSRV1 | | || Database ===> SQLDBA NODE: VMSYSTM1 | | || | | || | | || I IMMEDIATE COMMAND Immediately issue command | | || | | || S SCHEDULE COMMAND Schedule later command | | || | | || | | || Enter OPTION followed by the COMMAND to be executed, then | | || press ENTER to process | | || | | || NOTE: You may execute CP commands while the database is | | || running if you begin the command with CP | | || | | || EXAMPLE: I CP DETACH 181 would detach a tape, even while | | || the database is active | | || | | || | | |*---------------------------------------------------------------SQMDBCMD-----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
When the database is running the database, then CMS commands will not be allowed to process on the database virtual machine. CP commands can be executed on the database machine while the database is running if they are preceded with CP. For example, to immediately execute a detach command for the archive tape drive while the database is running, this command could be entered on the Database Command panel: I CP DETACH 181. The I instructs the product to execute the command immediately and the CP instructs the product to submit the command to the database as a CP command.
Commands can also be scheduled, which will allow dependencies to be established, such as requiring the target database to be in an up or down state before the command is to be issued. For example, this command schedules a message to be sent to user ID: OPERATOR on node VMSYSTM2 when the database is down:
S TELL OPERATOR AT VMSYSTM2 Please start database SQLDBA at VMSYSTM1
Use this tool to list all the product's database files for a specified database. All files maintained by it for a given database will be listed. From this list you are able to browse and update any of the files.
Use of the tool display option (view only) requires Control Center database User, Operator, or greater authorization. Use of the tool update options (modify or delete) requires database Administration or greater level of authorization.
The List Control Center VM Database Files tool is invoked by selecting Option L on the Database Utility Functions panel. All files with filenames matching the database machine name will be listed. Files in this list may then be displayed, modified, or deleted.
Figure 241 shows the List Files panel, with files listed for database machine SQLDBA.
Figure 241. Database Filelist Screen
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | |*----------------------------- Database Filelist ----------------------------* | || CTRLID: MSTRSRV1 | | || NODE: VMSYSTM1 | | ||Command ===> | | || Database ===> SQLDBA | | || _ SQLDBA ADBEXHIS _ SQLDBA ADBEXLOG _ SQLDBA ADBSPH | | || _ SQLDBA ADDPOOL _ SQLDBA ADDSPLOG _ SQLDBA ADEXTENT | | || _ SQLDBA ADNLPOOL _ SQLDBA ARCHHIST _ SQLDBA ARCHLOG | | || _ SQLDBA COLDLOG _ SQLDBA CONSOLE _ SQLDBA CONTROL | | || _ SQLDBA CURRENT _ SQLDBA DBEXTMAP _ SQLDBA INDXMAIN | | || _ SQLDBA LINKPWDS _ SQLDBA LOGMODE _ SQLDBA PARMS | | || _ SQLDBA MONITORS _ SQLDBA OPARMS _ SQLDBA RECOVCL | | || _ SQLDBA PSPRODCO _ SQLDBA PSPRODUL _ SQLDBA RUNINDX | | || _ SQLDBA RECOVLOG _ SQLDBA RESTORE _ SQLDBA SQLSTART | | || _ SQLDBA SQLADBSP _ SQLDBA SQLCIREO _ SQLDBA SQMREORG | | || _ SQLDBA TAPES _ SQLDBA VERSION | | || | | || | | || | | || Select: V = View, M = Modify, D = Delete | | || Page 1 of 1 | | |*---------------------------------------------------------------SQMDBLST----* | | PF: 1 Help 3 End | +--------------------------------------------------------------------------------+
Select options can be invoked against listed files.
| Note: |
|---|
|
Updating database files can be dangerous! Files such as the PARMS file and TAPES file have separate update functions within the product panel interface that perform validation on all changes. Using the Modify option to update files should be avoided whenever possible to prevent typing mistakes which can cause the product functions to fail. |
| Note: |
|---|
|
Use extreme caution when deleting files to avoid the possible deletion of a file required for the product operation. |
The files listed in Figure 241 are typical files kept by the managing Control Center service machine for any given database. A brief description of each file listed in this example is given below.
Use this tool to display the DBEXTENT/STORPOOL mapping report for a specified database. The information contained in the report provides valuable information relating to a database's dbextents.
To use this tool you will need Control Center database User, Operator, or greater authorization.
Mapping information is gathered each time the database is started and is kept in a file on the Control Center service machine's 191 A-disk. The filetype is DBEXTMAP and the filename matches the database machine name.
The product first determines all virtual addresses for each database minidisk by reviewing the database's SQLFDEF (refer to the DB2 Server for VM System Administration manual). After gathering virtual addresses, the product then reads the database's directory minidisk (BDISK) to determine the mapping of dbextents to database storage pools.
You can display the DBEXTENTS/STORPOOL Mapping report by selecting option QE on the Database Utility Functions panel. Figure 242 shows an example of the DBEXTENT/STORPOOL Mapping report. Information in the report is presented in both dbextent and storage pool sequences.
Figure 242. Example DBEXTENT/STORPOOL Mapping Report
DBEXTENT/STORPOOL Mapping
07/24/1998
******** Dbextent Sequence ********
Virtual Blocks/ DASD Real
Dbextent Storpool Address Pages Cylinders Type Volid Address
-------- -------- ------- ----- --------- ------ ------ -------
BDISK 200 100 CYL 3380 USM0M8 113E
LOGDSK1 201 75 CYL 3380 USM0M8 113E
LOGDSK2 220 75 CYL 3380 USM0HG 1125
1 1 202 14934 100 CYL 3380 USM0M8 113E
2 8 209 14934 100 CYL 3380 USM0M9 113F
3 1 20A 14934 100 CYL 3380 USM0M9 113F
4 1 20F 15561 104 CYL 3380 USM0M4 113A
5 6 20E 20064 134 CYL 3380 USM0ME 1144
6 2 210 7467 50 CYL 3380 USM0OA 1156
7 6 212 3534 20 CYL 3390 USM0L0 11D2
8 6 215 3534 20 CYL 3390 USM0L1 11D3
9 -3 204 4446 25 CYL 3390 USM0JG 11C5
********* Pool Sequence *********
Virtual Blocks/ DASD Real
Storpool Dbextent Address Pages Cylinders Type Volid Address
-------- -------- ------- ----- --------- ------ ------ -------
1 1 202 14934 100 CYL 3380 USM0M8 113E
3 20A 14934 100 CYL 3380 USM0M9 113F
4 20F 15561 104 CYL 3380 USM0M4 113A
2 6 210 7467 50 CYL 3380 USM0OA 1156
-3 9 204 4446 25 CYL 3390 USM0JG 11C5
6 5 20E 20064 134 CYL 3380 USM0ME 1144
7 212 3534 20 CYL 3390 USM0L0 11D2
8 215 3534 20 CYL 3390 USM0L1 11D3
8 2 209 14934 100 CYL 3380 USM0M9 113F
|