DB2 Table Editor For Multi Platforms
DB2 Table Editor For Multi Platforms
Users Guide
V ersion 4 Release 3
SC27-1616-09
IBM DB2 Table Editor for Multiplatforms, Workgroups, iSeries, and z/OS
Users Guide
V ersion 4 Release 3
SC27-1616-09
Note Before using this information and the products that it supports, read the information in Appendix B, Notices, on page 347.
Tenth Edition (October 2006) This edition applies to the following releases and to all subsequent releases and modifications until otherwise indicated in new editions: v IBM DB2 Table Editor for Multiplatforms, Version 4 Release 3 (program number 5724-B33) v IBM DB2 Table Editor for Workgroups, Version 4 Release 3 (program number 5424-E55) v IBM DB2 Table Editor for iSeries, Version 4 Release 3 (program number 5697-G84) v IBM DB2 Table Editor for z/OS, Version 4 Release 3 (program number 5697-G65) This edition replaces SC27-1616-08. Copyright Rocket Software, 2001, 2006
Contents
About this book . . . . . Who should read this book . . Conventions used in this book How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix ix ix ix
Chapter 1. Overview of IBM DB2 Table Editor . . . . . . . . . Summary of changes . . . . . . . . . . . . . . . . . . . Hardware requirements for DB2 Table Editor on Multiplatforms . . . . Software requirements for DB2 Table Editor on Multiplatforms . . . . Licensing . . . . . . . . . . . . . . . . . . . . . . . DB2 Table Editor connectivity . . . . . . . . . . . . . . . . Configuring your network environment . . . . . . . . . . . . . Configuring your SNA environment . . . . . . . . . . . . . Configuring your TCP/IP environment . . . . . . . . . . . . Configuring your CLI environment . . . . . . . . . . . . . Configuring your ODBC Environment . . . . . . . . . . . . Configuring the iSeries Environment . . . . . . . . . . . . . Setting Server Parameters . . . . . . . . . . . . . . . . Enabling DB2 Table Editor to list iSeries Physical and Logical files . DB2 Table Editor Concepts . . . . . . . . . . . . . . . . Using LookAt to look up message explanations . . . . . . . . .
. 1 . 1 . 1 . 2 . 2 . 3 . 5 . 5 . 6 . 6 . 7 . 8 . 9 . . . . 10 . . . . 11 . . . . 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . file . . . . . . . . . . . . . . 15 15 15 16 19 19 20 21 21 22 23 23 42 42 43 44 45 46 47 48 48 49 49 50 50 51 52 52 53 53 54
Chapter 2. Getting Started with DB2 Table Editor Console component . Servers. . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining packages . . . . . . . . . . . . . . . . . . . . Governing . . . . . . . . . . . . . . . . . . . . . . . . . Sample Tables . . . . . . . . . . . . . . . . . . . . . . . Starting DB2 Table Editor Console . . . . . . . . . . . . . . . . File menu - DB2 Table Editor Console component . . . . . . . . . . Edit menu - DB2 Table Editor Console component . . . . . . . . . . Help menu - DB2 Table Editor Console component . . . . . . . . . Authorities and privileges required for DB2 Table Editor tables . . . . . Configuring DB2 Table Editor. . . . . . . . . . . . . . . . . . Working with server definition files (SDFs) . . . . . . . . . . . . Sample tables . . . . . . . . . . . . . . . . . . . . . . Setting up Governing . . . . . . . . . . . . . . . . . . . Creating Resource Limits Groups . . . . . . . . . . . . . . . Creating a Resource Limits Group Schedule . . . . . . . . . . . Assigning Users to a Resource Limits Group . . . . . . . . . . . Specifying Parameters for a Resource Limits Group Schedule . . . . Assigning Users without a User Profile to a Resource Limits Group . . Creating User Profiles . . . . . . . . . . . . . . . . . . . Managing User Profiles . . . . . . . . . . . . . . . . . . . Selecting a Resource Limits Group for a User Profile . . . . . . . . Creating a New Server Definition File . . . . . . . . . . . . . Creating a new server definition file based on an existing server definition Setting connectivity options . . . . . . . . . . . . . . . . . Enabling Dynamic Definition of ODBC Servers . . . . . . . . . . . Importing DB2 for Windows Databases . . . . . . . . . . . . . . Activating Tracing . . . . . . . . . . . . . . . . . . . . . . Changing your password in DB2 Table Editor . . . . . . . . . . . . Specifying advanced DSN settings . . . . . . . . . . . . . . . Specifying driver-specific keywords . . . . . . . . . . . . . . .
iii
Deleting a Server from the Server Definition File . . . . . . . . . . . . Creating an extended catalog . . . . . . . . . . . . . . . . . . . Editing an extended catalog . . . . . . . . . . . . . . . . . . . . DB2 Table Editor Console window . . . . . . . . . . . . . . . . . . Parameters window overview . . . . . . . . . . . . . . . . . . . Fields and controls information . . . . . . . . . . . . . . . . . . . Resource limits groups at Server window Fields and Controls Information User Profile window Fields and Controls Information . . . . . . . . . New Profile Fields and Controls Information . . . . . . . . . . . . Assign User Profile window Fields and Controls Information . . . . . . Edit / New Resource Limits Group Schedule notebook Fields and Controls Information . . . . . . . . . . . . . . . . . . . . . . . . Editing Resource Limits Groups window Fields and Controls Information New Resource Limits Group window Fields and Controls Information . . . Edit Catalog Fields and Controls Information . . . . . . . . . . . . Add Catalog Fields and Controls Information . . . . . . . . . . . . Bind Options notebook Fields and Controls Information . . . . . . . . Packages Wizard and Procedures Wizard Fields and Controls Information Change Passwords window Fields and Controls Information . . . . . . Set User Information window Fields and Controls Information . . . . . Keyword and Value window Fields and Controls Information . . . . . . Advanced DSN Settings window Fields and Controls Information . . . . Parameters notebook Fields and Controls Information . . . . . . . . Options notebook Fields and Controls Information . . . . . . . . . . Importing DB2 for Windows Databases window Fields and Controls Information . . . . . . . . . . . . . . . . . . . . . . . . DB2 Table Editor Console window Fields and Controls Information . . . . Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3. Getting started with the DB2 Table component . . . . . . . . . . . . . Configuring DB2 Table Editor Developer . . . File Menu . . . . . . . . . . . . . . Edit Menu . . . . . . . . . . . . . . View Menu . . . . . . . . . . . . . . Form Menu . . . . . . . . . . . . . . Layout Menu . . . . . . . . . . . . . Window Menu . . . . . . . . . . . . . Help Menu . . . . . . . . . . . . . . Control Shortcut Menu . . . . . . . . . Form Shortcut Menu . . . . . . . . . . DB2 Table Editor Toolbars . . . . . . . . DB2 Table Editor Object Toolbar . . . . . DB2 Table Editor Status Bar . . . . . . Command Line Parameters . . . . . . . . Working with forms . . . . . . . . . . . Creating new forms . . . . . . . . . . Working with controls on a form . . . . . Opening a form . . . . . . . . . . . Saving a form . . . . . . . . . . . . Printing a form . . . . . . . . . . . Closing a form . . . . . . . . . . . Deleting a form . . . . . . . . . . . Working with validation rules . . . . . . . Creating a validation rule . . . . . . . . Creating a validation group . . . . . . . Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54 54 55 55 55 56 56 56 57 57 58 61 62 63 63 63 71 78 78 79 79 80 89 91 91 92
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
101 101 101 102 103 104 104 106 107 107 108 109 110 111 111 112 112 116 136 137 138 139 139 140 140 141
iv
Users Guide
Deleting a validation rule . . . . . . . . . . . Deleting a validation group . . . . . . . . . . Locking when Editing a Table . . . . . . . . . . Migrating Forms to a Different Environment . . . . . Controls dialog box . . . . . . . . . . . . . . Fields and controls information . . . . . . . . . Control Attributes dialog box (General Tab) . . . . Control Attributes dialog box (Column Tab) . . . . Control Attributes dialog box (Format Tab) . . . . Control Attributes dialog box (Replace Values Tab) . Control Attributes dialog box (Source Tab) . . . . Control Attributes dialog box (Button Action Tab) . . Control Attributes dialog box (Name Tab) . . . . . Control Attributes dialog box (Refresh Frequency Tab) Control Attributes dialog box (Default Result tab) . . Form Attributes dialog box (General Tab) . . . . . Form Attributes dialog box (Tables Tab) . . . . . Form Attributes dialog box (Join Conditions Tab) . . Form Attributes dialog box (Sort Conditions Tab) . . Object List dialog box . . . . . . . . . . . . Add Table dialog box . . . . . . . . . . . . Join dialog box . . . . . . . . . . . . . . Sort dialog box . . . . . . . . . . . . . . Validation Rules dialog box . . . . . . . . . . Action dialog box . . . . . . . . . . . . . Validation Rule Summary dialog box . . . . . . Rule Type dialog box . . . . . . . . . . . . Values dialog box . . . . . . . . . . . . . Control dialog box . . . . . . . . . . . . . Value List dialog box . . . . . . . . . . . . Equality Type dialog box . . . . . . . . . . . Value dialog box . . . . . . . . . . . . . . Select Statement dialog box . . . . . . . . . Error Message dialog box . . . . . . . . . . Logical Connector dialog box . . . . . . . . . Save Form At Server dialog box . . . . . . . . Server dialog box . . . . . . . . . . . . . Object List dialog box . . . . . . . . . . . . DITA . . . . . . . . . . . . . . . . . . Import Panel from DBEDIT dialog box . . . . . . DBEDIT Panels dialog box . . . . . . . . . . Open From Server dialog box . . . . . . . . . Main Window . . . . . . . . . . . . . . . Form Window . . . . . . . . . . . . . . . Tab Order dialog box . . . . . . . . . . . . Grid Settings dialog box . . . . . . . . . . . Bitmap dialog box . . . . . . . . . . . . . Enter Snap Points dialog box . . . . . . . . . Properties dialog box . . . . . . . . . . . . Server dialog box . . . . . . . . . . . . . Tables Dialog Box (Edit Table wizard) . . . . . . Columns dialog box. . . . . . . . . . . . . Actions dialog box . . . . . . . . . . . . . Format dialog box . . . . . . . . . . . . . Select Controls dialog box . . . . . . . . . . Attributes dialog box (Button Action Tab) . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141 142 142 142 144 144 144 145 145 146 147 147 151 151 151 152 152 153 153 154 154 154 155 155 155 156 156 157 157 157 158 158 159 159 160 160 161 161 161 162 163 163 164 164 164 164 165 165 166 171 171 172 172 174 176 176
Contents
Attributes Dialog Box (Advanced Tab) . . . . . . . . Print Preview window . . . . . . . . . . . . . . Package dialog box . . . . . . . . . . . . . . . HTML Parameters dialog box . . . . . . . . . . . Select Column to Link dialog box . . . . . . . . . . Select Control dialog box. . . . . . . . . . . . . Bind Completed dialog box . . . . . . . . . . . . Bind Options dialog box (Identification Tab) . . . . . . Bind Options Dialog Box (Formats Tab) . . . . . . . Bind Options Dialog Box (Statement Performance Tab) . Options dialog box (General Tab). . . . . . . . . . Options dialog box (Network Tab) . . . . . . . . . Options dialog box (LOBs Tab) . . . . . . . . . . Options dialog box (Traces Tab) . . . . . . . . . . Set CURRENT SQLID dialog box . . . . . . . . . Run SQL Statement dialog box . . . . . . . . . . Open Form dialog box . . . . . . . . . . . . . . Link Controls dialog box . . . . . . . . . . . . . Multiple Actions Dialog Box . . . . . . . . . . . . LOB Control Attributes Dialog Box (General Tab) . . . . LOB Control Attributes Dialog Box (Column Tab) . . . . LOB Control Attributes Dialog Box (Format Tab . . . . Launch LOB Application Dialog box (Column Tab) . . . Launch LOB Application Dialog box (Lob Associations Tab) File Extension Mapping Dialog Box . . . . . . . . . Forms Dialog Box . . . . . . . . . . . . . . . Servers Dialog Box . . . . . . . . . . . . . . . Tables Dialog Box . . . . . . . . . . . . . . . Statements Dialog Box . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
182 186 186 187 188 188 188 189 189 190 191 191 192 193 194 194 195 196 196 196 197 197 201 201 202 202 203 203 204
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component . . . . . . . . . . . . . To install DB2 Table Editor: . . . . . . . . . . . . . . . . . . . . Advanced installation . . . . . . . . . . . . . . . . . . . . . Installing DB2 Table Editor Java Player . . . . . . . . . . . . . . . Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases . . . . . . . . . . . . Installing DB2 Table Editor Java Player as an applet when working with DB2 databases . . . . . . . . . . . . . . . . . . . . . . . . Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases . . . . . . . Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases . . . . . . . . . . . . . . . . Command Line Parameters . . . . . . . . . . . . . . . . . . . Opening DB2 Table Editor Windows User component . . . . . . . . . . Opening DB2 Table Editor Java Player component . . . . . . . . . . . Connecting to an Informix Database using the DB2 Table Editor Java Player component . . . . . . . . . . . . . . . . . . . . . . . . . File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Table Layout Edit Popup Menus . . . . . . . . . . . . . . . . . . Working with LOBs (Large Objects) . . . . . . . . . . . . . . . . . Specifying which application will be used to open Large Objects (LOBs) Editing a tables . . . . . . . . . . . . . . . . . . . . . . . .
207 208 209 213 214 215 218 219 221 222 222 222 223 223 224 225 225 227 227 228
vi
Users Guide
To create a new form using the Edit Table feature: Working with primary keys . . . . . . . . . Working with Rows . . . . . . . . . . . . Working with Columns . . . . . . . . . . . Working with Cells . . . . . . . . . . . . Committing changes to the database . . . . . . Opening a form . . . . . . . . . . . . . . Fields and controls information . . . . . . . . Options dialog box . . . . . . . . . . . . Open From Server dialog box . . . . . . . . Main Window . . . . . . . . . . . . . . Form Window . . . . . . . . . . . . . . Set User Information dialog box . . . . . . . Zoom dialog box . . . . . . . . . . . . . Edit table dialog box . . . . . . . . . . . Row Conditions Dialog Box . . . . . . . . . Row Conditions Dialog Box . . . . . . . . . Sort Conditions dialog box . . . . . . . . . Column List dialog box . . . . . . . . . . Server dialog box . . . . . . . . . . . . Edit Table Wizard - Server page . . . . . . . Object List dialog box . . . . . . . . . . . Edit Table Wizard - Object List page . . . . . Object List Dialog Box (Windows User component) Advanced Options dialog box . . . . . . . . Edit Table Wizard - Columns and Buttons page . Sort and Row Conditions dialog box . . . . . Edit Table Wizard - Sort and Row Conditions Page Set CURRENT SQLID dialog box . . . . . . Columns dialog box. . . . . . . . . . . . File Extension Mapping Dialog Box . . . . . . Column LOB Type Associations dialog box . . . Set Database Server Dialog Box . . . . . . . Save Form at Server dialog box . . . . . . . Options Dialog Box (CPI-C Tab) . . . . . . . Options Dialog Box (TCP Tab) . . . . . . . . Options Dialog Box (CLI Tab) . . . . . . . . Options Dialog Box (LOB Tab) . . . . . . . . Options Dialog Box (Traces Tab) . . . . . . . Options Dialog Box (General Tab) . . . . . . Set Formula Dialog Box . . . . . . . . . . Grid Variables Dialog Box . . . . . . . . . Filters Dialog Box . . . . . . . . . . . . Decryption Dialog Box . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
229 230 231 233 233 234 234 235 235 236 236 236 236 237 238 238 239 239 240 240 240 241 242 242 243 244 244 245 246 246 247 247 248 249 249 249 250 250 250 251 251 252 252 253 255 255 255 257 258 260 260 261
Chapter 5. Using DB2 Table Editor with Informix databases . . . . . . Installing DB2 Table Editor when working with Informix Databases . . . . . Configuring your ODBC Environment . . . . . . . . . . . . . . . Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases . . . . . . . Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases . . . . . . . . . . . . . . . . Connecting to an Informix Database using the DB2 Table Editor Java Player component . . . . . . . . . . . . . . . . . . . . . . . . Creating Catalog Objects when working with Informix databases . . . . . . Using the Procedures Wizard to create catalog objects. . . . . . . . .
Contents
vii
Chapter 6. The DB2 Table Editor Control Center Plug-in . . . . . . . . 265 Installing the DB2 Table Editor Control Center Plug-in . . . . . . . . . . 265 Using the DB2 Table Editor Control Center Plug-in . . . . . . . . . . . 267 Chapter 7. The DB2 Table Editor ISPF component . . . . . . . . . . Licensing for the DB2 Table Editor ISPF component . . . . . . . . . . . Customizing DB2 Table Editor for ISPF . . . . . . . . . . . . . . . Customization summary . . . . . . . . . . . . . . . . . . . . Step 1. Create the control file . . . . . . . . . . . . . . . . . . Step 2. Bind the packages . . . . . . . . . . . . . . . . . . . Step 3. Bind the plans . . . . . . . . . . . . . . . . . . . . . Step 4. Bind the packages and plans for all other sub systems to which you want to connect . . . . . . . . . . . . . . . . . . . . . . Step 5. Edit SETISAMP members ETI and ETICLIST . . . . . . . . . Step 6. Optional: Add DB2 Table Editor to the DB2 Administration Tool and Launchpad . . . . . . . . . . . . . . . . . . . . . . . . Completing customization . . . . . . . . . . . . . . . . . . . Permissions . . . . . . . . . . . . . . . . . . . . . . . . Working with DB2 Table Editor for ISPF . . . . . . . . . . . . . . . Invoking DB2 Table Editor from the Administration tool Launch pad . . . . The DB2 Table Editor main panel . . . . . . . . . . . . . . . . Opening a table . . . . . . . . . . . . . . . . . . . . . . . Specifying how a table will be displayed in DB2 Table Editor for viewing or editing . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a table . . . . . . . . . . . . . . . . . . . . . . . . Column display functions . . . . . . . . . . . . . . . . . . . . . Accessing the CSETUP primary option menu . . . . . . . . . . . . Fixing a column . . . . . . . . . . . . . . . . . . . . . . . Repositioning columns . . . . . . . . . . . . . . . . . . . . Resizing columns . . . . . . . . . . . . . . . . . . . . . . Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting CSET customizations . . . . . . . . . . . . . . . . . Removing CSET customizations . . . . . . . . . . . . . . . . . Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . The use of color in DB2 Table Editor ISPF Component . . . . . . . . . . Data Type Abbreviations Used in DB2 Table Editor for ISPF . . . . . . . . DB2 Table Editor ISPF Component Commands . . . . . . . . . . . . 269 269 269 269 270 270 270 270 270 272 272 275 275 275 276 277 280 284 294 294 295 296 298 299 301 301 301 301 302 303
Chapter 8. Accessibility features . . . . . . . . . . . . . . . . . 307 Chapter 9. Troubleshooting . . . . . . . . . . . . . . . . . . . 309 Service updates and support information . . . . . . . . . . . . . . . 311 Where to find information . . . . . . . . . . . . . . . . . . . . . 311 Appendix A. Messages . . Messages for the DB2 Table Messages for the DB2 Table Java Player components . . . Editor Editor . . . . . . . . . . ISPF component . Console, Developer, . . . . . . . . . . . . . . . . . . . . Windows User, . . . . . . . . . 313 . . . 313 and . . . 329
Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . . 347 Other Notices . . . . . . . . . . . . . . . . . . . . . . . . . 349 Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 349 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
viii
Users Guide
ix
v Send your comments by e-mail to [email protected]. Be sure to include the name of the book, the part number of the book, the version of DB2 Table Editor, and, if applicable, the specific location of the text you are commenting on (for example, a page number or table number). v Print and fill out the reader comment form located at the back of this book. You can use the following methods to return the form: Give it to your local IBM branch office or IBM representative. Send it to the address printed on the reader comment form. For customers in the U.S. and Canada, fax it to 1-800-426-7773.
Users Guide
Summary of changes
This section summarizes significant changes that are implemented in this release of DB2 Table Editor. Enhanced functionality when working with Informix Databases No DB2 catalog database required A DB2 database is no longer required when working with Informix data only. Save forms at server Forms can now be saved at the server using the DB2 Table Editor Windows User component, and saved forms can be retrieved from the server using the Windows User and Java Player components.
Licensing
IBM DB2 Table Editor can access DB2 on a variety of platforms depending on which License Use Management (LUM) key that you have. The LUM keys are as follows: 1. Using the Multiplatform LUM key, you can access DB2 Universal Database running on the following platforms: v v v v v v v v v Linux Linux 390 AIX SUN Solaris HP-UX SCO NUMA-Q Windows NT Windows 2000
Users Guide
v Microsoft Windows XP 2. Using the Workgroup LUM key, you can access DB2 Universal Database Workgroup Server running on: v Windows NT v Windows 2000 v Microsoft Windows XP v Linux v AIX 3. Using the iSeries LUM key, you can access DB2 Universal Database running on the following platforms: v AS/400 v iSeries 4. Using the z/OS LUM key, you can access DB2 Universal Database running on the following platforms: v z/OS v os/390 The DB2 Table Editor license is enforced based on the platform to which IBM DB2 Table Editor is connecting (The platform where DB2 resides). You can have more than one License Use Management key installed. This would permit you to connect to DB2 on more than one platform. If you want to add an additional license, the new key must be installed by reinstalling the product using a version that includes the new LUM key in the disk1 directory. This process does the license enrollment as part of the install, but does not overwrite any existing keys. Note: The java code does not use the enrollment process to validate the keys. For the DB2 Table Editor Java player application and applet, copy the *.lic file that you want to add to the appropriate directory. This will activate the key. Related concepts Licensing for the DB2 Table Editor ISPF component on page 269 Related reference Hardware requirements for DB2 Table Editor on Multiplatforms on page 1 Software requirements for DB2 Table Editor on Multiplatforms on page 2
In order for DB2 Table Editor to use CLI to connect to DB2, you must first use DB2 to define your database servers and how to connect to them. This configuration is outside the control of DB2 Table Editor. Once this configuration is complete, however, DB2 Table Editor simply needs the alias that was defined for a particular database in order to connect to it. The primary advantage to using CLI is simplified configuration, in that if a database is already defined in the DB2 Universal Database for Windows client, its alias is the only piece of configuration information needed in DB2 Table Editor. The disadvantages to using CLI are that DB2 Table Editor performance using CLI is generally substantially worse than when using a DRDA connection, and that DB2 Table Editor only supports connecting to workstation, or z/OS or OS/390 databases with CLI (you must use DRDA connections to access iSeries or AS/400 databases).
Communications
One component of DRDA describes the communications protocol that participants in the architecture must use. It specifies that requesters and servers must communicate either via the SNA LU 6.2 architecture, or TCP/IP protocols. Tip: When using CLI to connect to a database, you must perform similar network configuration; however, this configuration is performed as part of the DB2 client configuration, rather than as part of the DB2 Table Editor configuration. The
Users Guide
following discussion on configuring your SNA and TCP/IP environments applies only to DRDA connections.
in detail. You must rely on your in-house SNA networking staff and your SNA software vendors technical support services to implement and support your network configuration. DB2 Table Editor Technical Support cannot provide support for these issues. DB2 Table Editor works with products that provide a Win CPIC-C interface. Note: Make sure that you have the latest corrective service or maintenance for your SNA product. Contact your SNA software vendors technical support services personnel for this information.
Users Guide
v DB2 Universal Database for Sun Solaris (Enterprise Server Edition) v DB2 Universal Database for z/OS and OS/390 v DB2 DataJoiner To connect to DB2 Universal Database for z/OS and OS/390, you must also have DB2 Connect installed locally or as a gateway. Note: Although DB2 Table Editor supports CLI connectivity to DB2 for DB2 for z/OS and OS/390, you are strongly urged to use a DRDA connection for your DB2 for z/OS and OS/390 databases. Related concepts DB2 Table Editor connectivity on page 3 Configuring your network environment on page 5 Configuring your TCP/IP environment on page 6 Configuring your ODBC Environment
large objects (LOBs) as long variable length objects For ODBC servers, DB2 Table Editor does not support: bookmarks interval data types For more information on configuring your Informix database for ODBC connectivity, consult the most recent version of the Informix documentation. When consulting the documentation, search for information on ODBC drivers. Related concepts DB2 Table Editor connectivity on page 3 Configuring your network environment on page 5 Configuring your TCP/IP environment on page 6 Configuring your CLI environment on page 6
Terminology
DB2 Table Editor uses SQL Terminology. The following table (The relationship between iSeries and SQL terminology ) shows the relationship between iSeries system terms and SQL relational database terms.
Table 1. The relationship between iSeries and SQL terminology iSeries Terms Library - Groups related objects and allows you to find the objects by name. SQL Terms Collection - Consists of a library, a journal, a journal receiver, an SQL catalog, and optionally a data dictionary. A collection groups related objects and allows you to find the objects by name. Table - A set of columns and rows. Row - The horizontal part of a table containing a serial set of columns. Column - The vertical part of a table of one data type. View - A subset of columns and rows of one or more tables. Package - An object type that is used to run SQL statements. Authorization name or Authorization ID.
Physical file - A set of records. Record - A set of fields. Field - One or more characters of related information of one data type. Logical file - A subset of fields and records of one or more physical files. SQL Package - An object type that is used to run SQL statements. User Profile
Authorities
v DB2 must be configured to accept the requests from DB2 Table Editor and the users must have the proper authorities specified in DB2 for the requests to be carried out. v The user profile that is used to install DB2 Table Editor must have SECADM authority.
Users Guide
DRDA Port
The DRDA Port must be in Listen state in order for the installation to complete successfully. To verify that the DRDA port is in Listen state: 1. Type NETSTAT on the AS/400 command line. 2. Select Option 3 (Work with TCP/IP connection status). 3. Locate for DRDA under the Local Port column and ensure that the State = Listen. If the State = Listen, go to the next section, if not continue to step 4. 4. If DRDA is not there, DDM TCP/IP services must be started on the AS/400. To start the DDM TCP/IP server: a. Type STRTCPSVR *DDM on the iSeries command line. b. Locate DRDA under the Local Port column and ensure that the State = Listen. If the State = Listen, go to the next section, if not continue to the User Profile CCSID section. Tip: To ensure that the DDM server, which opens the DRDA port, will autostart when the STRTCP command is issued during system startup: 1. Type GO TCPADM at the AS/400 command line. 2. Select Option 2 (Configure TCP/IP Applications) 3. Select Option 5 (Change DDM TCP/IP Attributes) 4. Change the Autostart server prompt to yes.
5. Select the type of network connection that applies to your environment. v If you selected Connect using TCP/IP: a. In the Host Name field, type a host name for the database that you specified in the RDB name field. This can be either the Host Name.Domain Name or the servers TCP/IP address. b. In the Port Number field, Type a port number for the database server to use. The default port for DB2 to listen for DRDA TCP/IP conversations on the AS/400 is 446. Note: There is a possibility that the default port (446) will already be assigned, but not active, or that the port has been changed to another value. If either of these is the case, you will receive the WSAECONNREFUSED error message when DB2 Table Editor attempts to connect to the server. v If you selected Connect using CPI-C, type a symbolic destination name in the Symbolic destination name field. v If you selected Connect using DB2 UDB for Windows CLI, select a database alias from the Database Alias list. 6. Check the Enable load balancing check box if you want load balancing to be enabled. 7. Click Test Connection to test the connection to the server. 8. Click OK.
Enabling DB2 Table Editor to list iSeries Physical and Logical files
The SQL statements that create the DB2 Table Editor database objects by default only allow object types of T (Tables) and V (Views) to be displayed in a list. Any AS/400 file can be accessed using DB2 Table Editor. However, in order for all file types, including Physical and Logical files, to be listed you must modify the SQL script as described in the following steps. 1. From the Create Objects window, scroll down to the following statement:
CREATE VIEW RDBI.TABLE_VIEW2
2. In the CREATE statement, modify the WHERE clause to add P for Physical files and L for Logical files as follows:
WHERE A.TABLE_TYPE IN (T,V,P,L);
3. Click OK. Once the packages have been successfully created, the Bind Packages window will open. 4. Click Next. The Permissions window opens 5. In the User IDs box, type the user IDs to which you want to grant permission to run the packages in DB2 Table Editor. Note: In order to run DB2 Table Editor, a user must have permission to run the user packages in order to use DB2 Table Editor. DB2 Table Editor creates the collection containing these packages on the iSeries with authority PUBLIC * EXCLUDE. You must grant appropriate authority for those users to that Collection/Library on the iSeries. 6. Click Grant. Permissions are granted on the server to the user IDs that you specified. 7. Click Next. The Check Table Authorizations window opens. 8. Select either check or do not check for unassigned tables.
10
Users Guide
Note: Tables with no permissions are not visible to DB2 TableEditor and do not appear in table lists. Once they are located, you can assign permissions to these tables, making them visible in lists. Click Next. If you checked the Check for unassigned tables check box and unassigned tables are found, the Grant Table Authorization window opens. 9. From the Grant Table Authorization window, grant the necessary table authorizations, if necessary. 10. Click Finish.
Database A database is a software application that stores sets of electronically organized information on a computer. It contains a collection of tables, which contain data. DB2 is a database product built by IBM. Forms A form is a vehicle through which you view and change table data. In DB2 Table Editor, forms play different roles depending on the component of DB2 Table Editor that you are using. v In DB2 Table Editor Developer, you create forms for use in the DB2 Table Editor component and the Java Player component. These forms can allow the user to access, search, and edit tables in DB2 databases table to which the form is linked. v In DB2 Table Editor component and the Java Player component, a form is the object that you work with to view and change table data. It is similar to a paper form, in that it contains blank spaces, or fields, for you to fill in. In addition, it allows you to fill in some of the fields and retrieve information, or enter new information and update the database. Note: The forms are built by a developer in DB2 Table Editor Developer. These forms will be highly customized to your organization, your data, and your needs.
Chapter 1. Overview of IBM DB2 Table Editor
11
Full-screen editor A full-screen editor is a special form that presents data from the database as a grid or in a spreadsheet format. This type of form allows edits directly in the grid itself and includes the ability to insert and delete rows, sort columns, and find and replace values. Join A join is a connection between two tables, using a field common to both tables. For example, there could be a table that containing personal information for all the employees of a company (employee numbers, names, addresses, and Social Security numbers for each employee). In the same database there could be another table containing employee numbers and department numbers. In order to avoid repeating the employee personal information in the table containing department numbers, there is a join from the employee number in the personal information table, to the employee number in the department table; this allows the information to be linked, but not repeated.
Primary Table The primary table is the table that is designated by the form developer as the updateable table. For each form there is only one primary table, but there can be a number of secondary tables, which are usually related to the primary table by join conditions. Insert, Update and Delete buttons on a form operate only on the primary table and perform the appropriate database modifications for the action (insert, update and delete) using the current form values for all controls that are bound to a primary table column. Properties A property in DB2 Table Editor Developer defines the appearance of a form or its controls. The developer uses properties to define the layout of the form, as well as the physical characteristics of controls. Examples of form properties are background color and form dimensions. Examples of control properties are text font, color and control dimensions. Resource Limits Groups Resource limits groups are set up by the system administrator and are designed to provide users with sufficient access to database severs without adversely affecting database or network performance. Each DB2 Table Editor user is a member of a resource limits group. Once the system administration defines and assigns a resource limits group to a DB2 Table Editor user, that user is limited to resource usage as defi9ned by that resource limits group. If a system administrator does not assign explicit limits, users are limited to resource usage as defined in the default resource limits group Server Definition File (SDF) The DB2 Table Editor server definition file (SDF) is an initialization (.ini) file that contains the technical information that DB2 Table Editor needs to connect end users to database servers. For more information on SDFs, see Working with server definition files (SDFs). Tables A table in DB2 Table Editor refers to a table that is contained in a DB2 database. A DB2 database contains data that is organized into smaller collections, or tables. Each form created with DB2 Table Editor Developer is linked to one or more tables, providing the data source for the form. DB2 Table Editor component and Java Player component are both used to access data stored in tables.
12
Users Guide
Validation rules A validation rule in DB2 Table Editor Developer defines allowable values for the contents of a control. The developer uses validation rules to establish limits which govern what value a user can enter into a control, as well as the format of the value entered. For example, a validation rule can require a user to enter a valid date format in a control. Validation rules can work individually or in groups.
13
14
Users Guide
Servers
Each database server that you or your users access with DB2 Table Editor must be defined with DB2 Table Editor Console. When you define a database, you give the database server a server name. There are no restrictions on what this name can be, it is intended to be a descriptive label for the server, used only in DB2 Table Editor. This name is all that a user of the DB2 Table Editor component or the Java Player component needs to know in order to access that server. DB2 Table Editor Console is used to define each server, giving it a name and also specifying the technical information that DB2 Table Editor needs to access it. This is similar to defining a data source in ODBC. The parameters that you must specify include: v The RDB name for the server (also known as the location name in DB2 for z/OS or OS/390 terminology, or the database name in DB2 for Multiplatforms), or the database alias if connecting through CLI. v The appropriate network connection information if connecting via DRDA--either the CPI-C symbolic destination name or TCP/IP host name and port number.
Maintaining packages
To run distributed SQL at any DB2 database, you must bind a package at the database that contains the SQL that you want to run (excluding dynamic SQL). You use DB2 Table Editor Console to choose the collection name and options for the packages that it requires, and to automatically bind the packages at a server. The DB2 Table Editor packages refer to the set of DB2 tables that DB2 Table Editor uses, which might not exist at a server. If so, you must create these tables before binding the packages. DB2 Table Editor Console can automatically determine which tables need to be created, and it allows you to automatically create them. Finally, after you bind the DB2 Table Editor packages, you must grant authority to your end users to run the user packages. Again, DB2 Table Editor Console can automatically grant or revoke this authority to the users that you specify.
15
Governing
DB2 Table Editor incorporates a comprehensive resource governor that restricts the actions that a user can perform in DB2 Table Editor and places limits on the resources that a user can consume. This governing feature allows you to provide distributed access to DB2 to your users with the confidence that this will not have a negative impact on your overall database or network performance. Using the DB2 Table Editor Console, you can define sets of limits and restrictions, which are called resource limits groups. You can then assign users to a resource limits group, according to the governing that you want performed for those users. Here are some common questions about governing and their answers:
v The accounting string to pass to the database server v Whether to fetch all rows immediately or only as-needed
16
Users Guide
How does DB2 Table Editor relate a resource limits group to a user?
The relationship between a DB2 Table Editor user and a resource limits group is stored in a table at the database server, specifically, the table named RDBI.PROFILES_VIEW. DB2 Table Editor Console is used to maintain user and resource limits group relationships in this table.
17
How does DB2 Table Editor determine which resource limits group is in effect?
The RESOURCE GROUP column in the RDBI.PROFILES_VIEW table contains the name of the resource limits group that is in effect for users identified by the profile entry. If this field is null or blank, DB2 Table Editor will assume a default value of the user ID. DB2 Table Editor then searches the RESOURCE_GROUP and RESOURCE_OPTION columns in the RDBI.RESOURCE_VIEW view, looking for the rows listed in the following table (Rows searched for in the RESOURCE_GROUP and RESOURCE_OPTION columns in the RDBI.RESOURCE_VIEW view ):
Table 3. Rows searched for in the RESOURCE_GROUP and RESOURCE_OPTION columns in the RDBI.RESOURCE_VIEW view RESOURCE_GROUP RESOURCE_GROUP from RDBI.PROFILES_VIEW RESOURCE_GROUP from RDBI.PROFILES_VIEW RESOURCE_GROUP from RDBI.PROFILES_VIEW RESOURCE_GROUP from RDBI.PROFILES_VIEW RESOURCE_GROUP from RDBI.PROFILES_VIEW RESOURCE_OPTION SHUTTLE_MAIN SHUTTLE_SCHED1 SHUTTLE_SCHED2 SHUTTLE_SCHED3 SHUTTLE_SCHED4
If no matches are found, the user is governed by the default resource limits group. Otherwise, the user is covered based on the limits and controls found in these rows.
18
Users Guide
From Time 17:00 (5 PM) To Time 08:00 (8 AM) This schedule is in effect only on weekdays. For each weekday, this schedule is in effect for the hours 5 PM to midnight, and midnight to 8 AM. For example, this schedule is in effect each Monday morning from midnight to 8 AM as well as each Monday evening from 5 PM to midnight.
Sample Tables
DB2 Table Editor provides nine sample tables that you can use while learning DB2 Table Editor before you begin working with your own tables. The sample tables are used throughout the DB2 Table Editor Getting Started Guides and online help as examples. They contain information about a fictitious electrical parts company. The following table (Sample Tables) lists the name of the sample table and the type of data contained in it.
Table 4. Sample Tables Sample table name DBE. APPLICANT DBE.INTERVIEW DBE.ORG DBE.PARTS DBE.PRODUCTS DBE.PROJECT DBE.SALES DBE.STAFF DBE.SUPPLIER Contains information about The prospective employees of the company. The interview schedule for prospective employees. Organization of the company by department (within division). Materials supplied to the company. Products produced by the company. Company projects. Sales information for the company. The employees of the company. Other companies who supply materials to the company.
19
From the main window in DB2 Table Editor Console, select Edit --> Options. On the Options dialog box in the CPI-C Options group, specify the name of the DLL that your SNA software provides for CPI-C applications.
Open
Save As Opens a Save As window where you can type the name of a new DB2 Table Editor SDF. DB2 Table Editor creates the new SDF using the currently opened SDF as a model. All configured servers and their parameters are included in the new SDF. You can leave the SDF as is, or using the Parameters notebook, you can edit the parameters to make any necessary modifications. Upon saving, DB2 Table Editor points to the new SDF. The open SDF is displayed in the DB2 Table Editor Console window menu bar. Import From DB2 Opens the Import DB2 for Windows Database window that lists the available DB2 for Windows databases. You can select a database and DB2 Table Editor will import many of the SDF parameters that it needs in order to configure the server. DB2 Table Editor opens the Parameters notebook where you can change any of the servers parameters and complete the configuration process. Note: You must have DB2 CONNECT for DB2 Table Editor to discover the available DB2 databases. File List The last four SDFs that you opened are listed in the File list. Click the number or name of the file you want to open. Upon opening, and displays the SDF name in the DB2 Table Editor Console window menu bar. Terminate Connections Terminates any server connections that have been established for this session. Exit Terminate the DB2 Table Editor Console application. DB2 Table Editor terminates any connections to the database servers. Related reference Edit menu - DB2 Table Editor Console component on page 21 Help menu - DB2 Table Editor Console component on page 21
20
Users Guide
Copy
Paste Using the contents of the clipboard as the model server, DB2 Table Editor creates an entry for the server in the SDF and opens the Parameters notebook where you can complete the configuration process. Note: If the clipboard does not contain valid SDF information to use as a model, DB2 Table Editor creates a dummy server entry in the SDF without valid parameter information. DB2 Table Editor opens the Parameters notebook where you must supply the parameter information to complete the configuration process. Delete Removes the selected server and all of its parameters from the DB2 Table Editor SDF without placing it on the clipboard. Note: You can also delete a server from the SDF using the Delete button on the DB2 Table Editor Console window. Options Opens the Options notebook where you can specify global connectivity information for all servers that are configured in the DB2 Table Editor SDF and activate tracing for problem resolution. Related reference File menu - DB2 Table Editor Console component on page 20 Help menu - DB2 Table Editor Console component
21
About DB2 Table Editor Console Displays information about the DB2 Table Editor Console application including version number, copyright and trademark information. Related reference File menu - DB2 Table Editor Console component on page 20 Edit menu - DB2 Table Editor Console component on page 21
22
Users Guide
Authorities Select (DB2 for MVS, DB2 for OS/390, DB2 UDB for OS/390, DB2 UDB for OS/390 and z/OS) Select (SQL/DS, DB2 Server for VSE & VM) Select (SQL/DS, DB2 Server for VSE & VM) Select (DB2 for iSeries) Select (DB2 for iSeries)
v Specify user profiles v Define resource limits v Create catalog objects and bind packages v Selecting the DB2 Table Editor catalog SDFs are usually created and managed by one administrator, not each end user. The administrator is the only person who needs to install the DB2 Table Editor Console component. They create one or more SDFs and save them to a location that is accessible by all DB2 Table Editor component and Developer component users. Whenever any updates are made to an SDF (such as adding a new server), the administrator must save the changes to that shared location in order for all users to use the updated SDF. Information: If more than one person is acting as the DB2 Table Editor administrator, it is possible for one administrator to overwrite the bound packages that are created by another administrator if the same catalog name is used. DB2 Table Editor requires at least one SDF. You can create multiple SDFs. After they are configured, one or more SDFs are distributed to DB2 Table Editor end users, based on how you choose to manage your query environment. If you use a single SDF, you define all physical servers that every DB2 Table Editor user would need to access in the one file. All users share the SDF over a file sharing network. A single SDF file is advantageous because it minimizes and centralizes administrative tasks. If you use multiple SDFs, you define a select set of
Chapter 2. Getting Started with DB2 Table Editor Console component
23
physical servers in several different SDF files. End users and developers will access one or more SDF depending on their requirements. There are two basic ways that you can use SDFs. You can allow each DB2 Table Editor user to have their own SDF, or you can create a single SDF that is shared by multiple users over a file-sharing network. The advantage of the sharing approach is that it centralizes the administration of the SDF (you only need to create and maintain a single file, and your users need only to point to that file when they run DB2 Table Editor). With either approach, you specify the SDF to use on the Options window in the DB2 Table Editor Console. (To access the options window in the DB2 Table Editor Console), select View --> Options.) From within DB2 Table Editor Console, you can create a new SDF for a user or group of users by selecting File --> New or File --> Save As. To open and work with a different SDF, select File --> Open. Related concepts Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
24
Users Guide
Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
3. 4.
5. 6.
25
database. For more information on the types of connectivity that can be used and the associated parameters, see the fields and controls information for the Parameters Notebook. 7. Click Next. The Set User Information window opens. 8. From the Set User Information window, specify the UserID, password, and account to be used to connect to the database that you are defining. 9. Click OK. The Packages page opens if you are working with DB2. 10. From the Packages page, either specify the collection ID for existing DB2 Table Editor packages, or click the Wizard button to launch the Packages wizard to create and bind DB2 Table Editor packages. 11. Click Next. The Catalog page opens. 12. On the Catalog page, specify the desired catalog options. For more information on the catalog options, see the fields and controls information for the Parameters Notebook. 13. Click Finish. The Server is defined in the SDF. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41 Defining a Server that has bound packages associated with it: To configure a server that already has bound packages associated with it, you must follow slightly different steps then when you configure a server that does not have bound packages already associated with it. To create an new entry in the SDF, you must either bind the packages with a different Collection ID, or add the information about the packages that you want to use to the existing SDF. It is necessary to go through these steps because information is not written to the SDF otherwise. If you do not go through the steps, DB2 Table Editor will have no Collection ID specified for this database server and it will attempt to use the default NULLID. To define a server that has packages associated with it: The steps for defining a server to an SDF for which the packages have already been bound are the same as the steps for defining a server to an SDF with no bound packages with one exception. On the Bind Packages page of the wizard,
26
Users Guide
select the Do not bind the packages radio button if you do not want the packages for the SDF to be bound again. For more information on the steps for defining a server to an SDF for which the packages have not been bound, see: Defining a DB2 Database Server in an SDF.
27
Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Specifying server connectivity Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
28
Users Guide
v Select Connect to Informix using ODBC to specify that ODBC connectivity will be used to connect to your Informix database. If you select Connect to Informix using ODBC, the lower half of the Connections page changes and presents fields that are specific to the ODBC network connection, including the Machine data source name and File data source name fields, and the Advanced button to specify advanced DSN settings for ODBC data source drivers. Note: If you are adding an Informix server, you must use ODBC connectivity. v Select Connect to other data sources using ODBC to specify that ODBC connectivity will be used. If you select Connect using ODBC, the lower half of the Connections page changes and presents fields that are specific to the ODBC network connection, including the Machine data source name and File data source name fields, and the Advanced button to specify advanced DSN settings for ODBC data source drivers. 3. Click the Set User Information button to specify the user ID and password to be used to connect to the database server. 4. Click the Test button to establish a connection to the database server. You must test the connection to any new database server that you are configuring in the SDF before proceeding to the remaining steps of configuring the database server in the DB2 Table Editor SDF. 5. Close the Connections page of the Parameters notebook: v Click Next to close the Connections page of the Parameters notebook. If you are configuring a new database server in the DB2 Table Editor SDF, the Packages page of the Parameters notebook opens. v Click OK to close the Connections page of the Parameters notebook. If you are editing a database servers configuration parameters, the Parameters notebook closes, saving any changes that you have made to the database servers configuration parameters. v Click Apply to apply any changes that you have made to the database servers configuration parameters. The Connections page of the Parameters notebook stays open. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
Chapter 2. Getting Started with DB2 Table Editor Console component
29
Creating Catalog Objects and Binding Packages when working with DB2 databases
Use the Packages page of the Parameters notebook to create the DB2 Table Editor objects and bind the DB2 Table Editor packages. Creating the catalog objects and binding the packages is part of the overall task of configuring the DB2 Table Editor SDF. You create a set of catalog objects and bind a set of packages on each database server that you configure in the SDF with the exception of ODBC data servers. The DB2 Table Editor catalog objects consist of database tables, indexes and other objects that contain information used by DB2 Table Editor. The DB2 Table Editor packages contain the SQL that DB2 Table Editor needs to run and access tables, indexes, objects, lists, views and other miscellaneous information. 1. Open the Packages page of the Parameters notebook. 2. In the Collection ID field, specify a unique name that will be used to bind the DB2 Table Editor packages. The name you specify will identify the group of packages as belonging to DB2 Table Editor. In most instances, this name refers to the version of DB2 Table Editor that you are running on this database server. 3. Select a decimal delimiter by clicking the Period radio button or the Comma radio button. You select the decimal delimiter based on what has been defined for your database server. DB2 Table Editor uses the selected decimal delimiter in the text of its SQL statements that will be run on this database server. 4. Select a string delimiter by clicking the Apostrophe radio button or the Quote radio button. You select the string delimiter based on what has been defined for your database server. DB2 Table Editor uses the selected string delimiter in the text of its SQL statements that will be run on this database server. 5. Click the Wizard button to create the DB2 Table Editor catalog objects and bind DB2 Table Editor packages. The Packages Wizard opens. 6. When you have finished creating DB2 Table Editor objects and binding the packages, close the Packages page of the Parameters notebook: v Click Next to close the Packages page of the Parameters notebook. If you are configuring a new database server in the DB2 Table Editor SDF, the Catalog page of the Parameters notebook opens. v Click OK to close the Packages page of the Parameters notebook. If you are editing a database servers configuration parameters, the Parameters notebook closes, saving any changes that you have made to the database servers configuration parameters. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Using the Packages Wizard to create catalog objects and bind packages on page 31 Specifying database-specific bind options on page 33 Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects when working with Informix databases on page 33
30
Users Guide
Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41 Using the Packages Wizard to create catalog objects and bind packages: Use the Packages Wizard to create the DB2 Table Editor catalog objects and bind the DB2 Table Editor packages for the database server. The Packages Wizard is not available when configuring an ODBC database server. ODBC database servers cannot host a DB2 Table Editor catalog. Instead, ODBC servers use a DB2 Table Editor catalog that resides on a DB2 database server. Use the Catalog page of the Parameters notebook to point to a catalog for the ODBC server. In addition, because dynamic SQL is used, ODBC database servers do not require that you bind a set of packages. 1. Open the Packages Wizard. 2. From the Catalog Option page specify whether or not you will create a DB2 Table Editor catalog on the database server that you are configuring in the SDF. Select one of the following options: v Create catalog tables to support short names - to create a set of DB2 Table Editor catalog tables that support short names. v Create catalog tables to support long names - to create a set of DB2 Table Editor catalog tables that support long names. Note: This option is only available for DB2 databases of V8 and above. v Catalog tables have already been created - to bind one or more packages or configure a different flavor of a database server in the SDF when DB2 Table Editor catalog tables already exist. v Do not create catalog tables - to skip creating DB2 Table Editor catalog tables when the database server that you are configuring will not host a DB2 Table Editor catalog but use one that resides on a different database server If you are configuring a database server for the first time and it does not have set of DB2 Table Editor catalog tables then you must create the catalog tables. To do so, select either Create catalog tables to support short names or Create catalog tables to support long names. 3. Click the Next button to open the next page of the Packages Wizard. 4. From the Package Properties page you specify the bind options that should be used when binding the DB2 Table Editor packages. Type the collection ID that you want to use in the Collection ID field. Enter a user ID in Owner ID field if you want to use a user ID other than your primary authorization ID to bind the packages. Click the Advanced button to open the Bind Options notebook where you can specify additional database-specific parameters to use to bind the packages. 5. Click the Next button to open the next page of the Packages Wizard. 6. From the Check Objects page specify whether or not you will be creating a new set of DB2 Table Editor database objects. If you are defining a database server to the DB2 Table Editor SDF for the first time, select the Assume that
Chapter 2. Getting Started with DB2 Table Editor Console component
31
none of the objects exist button to create a new set of DB2 Table Editor database objects. If you have previously bound DB2 Table Editor packages for the database server, select the Automatically check which objects already exist button to only create database objects that dont already exist. If you are sure that all the database objects exist, select the Assume that all of the objects already exist button. If you select the Assume that all of the objects already exist option, the Packages Wizard skips the Object Listing and the Create Objects steps. 7. Click the Next button to open the next page of the Packages Wizard. 8. From the Object Listing Option page specify the level of filtering that will apply when producing lists of objects for DB2 Table Editor users. To impose the least amount of filtering and present all objects stored on the database server to a user regardless of user ID, click the Include all objects without respect to whether or not the user is authorized to access them button. To specify that only the database objects that a users primary ID or current authorization ID is allowed to access, click the Include only those objects that either the users primary or current authorization ID is authorized to access button. If a user is part of multiple groups that require different authorization IDs and you want to specify that all the database objects that can be accessed by the primary user ID, the current authorization ID and all other authorization IDs that the primary user ID is associated with, click the Include only those objects that any of the users primary or secondary authorization IDs are authorized to access. 9. Click the Next button to open the next page of the Packages Wizard. 10. From the Create Objects page you can view and edit the SQL statements that DB2 Table Editor will use to create the required database tables. 11. Click the Next button to open the next page of the Packages Wizard. 12. From the Bind Packages page specify whether or not the Packages Wizard will bind the packages using the parameters and information you have specified. Click the Do not bind the packages button to skip this step. You may skip this step if you have previously bound packages on this database server for the current version of DB2 Table Editor. Click the Bind the packages button to bind the DB2 Table Editor packages. Check the Replace existing packages check box to ensure that packages from previous versions of DB2 Table Editor do not remain on the database server. Check the Keep existing authorizations check boxes to use the same authorizations for the current packages that were in place for any packages that were previously installed. Note: Binding packages opens a connection to the database server. The status line of the Bind Packages dialog window indicates the progress of the bind operation. If errors are encountered, correct the error, then repeat the bind. Upon completion, the DB2 Table Editor packages will be bound and stored with the collection name. 13. Click the Next button to open the next page of the Packages Wizard. 14. From the Permissions page you grant permission to the user IDs that can run DB2 Table Editor on this database server. To grant permission to all user IDs, select the default user ID PUBLIC from the User IDs list box and click the Grant button. To grant permission to a specific user ID, type the user ID in the User IDs list box and click the Grant button. To revoke permission from a user ID, type the user ID in the User IDs list box and click the Revoke button. Note: If you are choosing to use the default user ID PUBLIC to grant all DB2 Table Editor users permission to run queries on this database server,
32
Users Guide
you must actually grant the permission to the PUBLIC user ID by selecting the user ID and clicking the Grant button. 15. Close the Packages Wizard. v Click the Finish button to close the Packages Wizard. The DB2 Table Editor packages are installed on the database server. The Packages page of the Parameters notebook remains open. v Click the Next button is to close the Packages Page. The Catalog page of the Parameters notebook opens. Related tasks Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Specifying database-specific bind options Specifying database-specific bind options: Use the Bind Options notebook to specify additional bind options that will be used by the Packages Wizard to bind the DB2 Table Editor packages. All of the bind options are optional. They apply to very specific requirements that may be needed by your database. 1. Open the Bind Options notebook.. 2. Optional: Click the Identification page of the notebook to specify identification options such as the collection ID, Owner ID, Qualifier, and comments; and specify what to do with existing packages and authorizations. 3. Optional: Click the Formats page of the notebook to specify the decimal and string delimiters, and the date and time formats that is to be used on this database server. 4. Optional: Click the Statement Performance page of the notebook to specify isolation level, query blocking, data release, degree of parallelism, and query optimization options. 5. Optional: Click the Statements page of the notebook to specify explain, time validation, and SQL warnings options. 6. Optional: Click the Miscellaneous page of the notebook to specify dynamic rules, character sub-types, and generic options. 7. Click OK. The Bind Options notebook closes. All bind options are saved and will be applied when the Packages Wizard binds the packages. The Package Properties page of the Packages Wizard stays open. Related tasks Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Using the Packages Wizard to create catalog objects and bind packages on page 31
33
information used by DB2 Table Editor. The DB2 Table Editor procedures enable DB2 Table Editor to run and access tables, indexes, objects, lists, views and other miscellaneous information. 1. Open the Procedures page of the Parameters notebook. 2. In the Owner field, type the userID of the owner of the procedure that you are creating. 3. Click the Wizard button and create the DB2 Table Editor catalog objects. The Procedures Wizard opens. For more information on the Procedures Wizard, see the fields and controls information on the Packages Wizard and Procedures Wizard. 4. When you have finished creating DB2 Table Editor Objects in the Procedures Wizard, close the Procedures page of the Parameters notebook: v Click Next to close the Procedures page of the Parameters notebook. If you are configuring a new database server in the DB2 Table Editor SDF, the Catalog page of the Parameters notebook opens. v Click OK to close the Procedures page of the Parameters notebook. If you are editing a database servers configuration parameters, the Parameters notebook closes, saving any changes that you have made to the database servers configuration parameters. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Using the Procedures Wizard to create catalog objects Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41 Using the Procedures Wizard to create catalog objects: Use the Procedures Wizard to create the DB2 Table Editor procedures when working with Informix databases. The DB2 Table Editor procedures enable DB2 Table Editor to run and access tables, indexes, objects, lists, views and other miscellaneous information. 1. Open the Procedures Wizard. 2. From the Catalog Option page specify whether or not you will create a DB2 Table Editor catalog on the database server that you are configuring in the SDF. Select one of the following options:
34
Users Guide
v Create catalog tables to support long names - to create a set of DB2 Table Editor catalog. v Catalog tables have already been created - the catalog tables have previously been created. Select this option to call the existing procedures. v Do not create catalog tables - to skip creating DB2 Table Editor catalog tables when the database server that you are configuring will not host a DB2 Table Editor catalog but use one that resides on a different database server 3. Click the Next button to open the next page of the Procedures Wizard. 4. From the Procedure Properties page, specify the userID of the owner of the procedure in the field Owner field. 5. Click the Next button to open the next page of the Procedures Wizard. 6. From the Check Objects page specify whether or not you will be creating a new set of DB2 Table Editor database objects. Select the Automatically check which objects already exist radio button. 7. Click the Next button to open the next page of the Procedures Wizard. 8. From the Object Listing Option page specify the level of filtering that will apply when producing lists of objects for DB2 Table Editor users. To impose the least amount of filtering and present all objects stored on the database server to a user regardless of user ID, click the Include all objects without respect to whether or not the user is authorized to access them button. To specify that only the database objects that a users primary ID or current authorization ID is allowed to access, click the Include only those objects that either the users primary or current authorization ID is authorized to access button. If a user is part of multiple groups that require different authorization IDs and you want to specify that all the database objects that can be accessed by the primary user ID, the current authorization ID and all other authorization IDs that the primary user ID is associated with, click the Include only those objects that any of the users primary or secondary authorization IDs are authorized to access. 9. Click the Next button to open the next page of the Procedures Wizard. 10. From the Create Objects page you can view and edit the SQL statements that DB2 Table Editor will use to create the required database tables. 11. Click the Next button to open the next page of the Procedures Wizard. 12. From the Create Procedures page specify whether or not the Procedures Wizard will create the procedures using the parameters and information that you have specified. Click the Do not create the procedures button to skip this step. You may skip this step if you have previously bound procedures on this database server for the current version of DB2 Table Editor. Click the Create the procedures button to bind the DB2 Table Editor procedures. Check the Replace existing procedures (if any) check box to ensure that procedures from previous versions of DB2 Table Editor do not remain on the database server. 13. Click the Next button to open the next page of the Procedures Wizard. 14. From the Permissions page you grant permission to the user IDs that can run DB2 Table Editor on this database server. To grant permission to all user IDs, select the default user ID PUBLIC from the User IDs list box and click the Grant button. To grant permission to a specific user ID, type the user ID in the User IDs list box and click the Grant button. To revoke permission from a user ID, type the user ID in the User IDs list box and click the Revoke button.
35
Note: If you are choosing to use the default user ID PUBLIC to grant all DB2 Table Editor users permission to run queries on this database server, you must actually grant the permission to the PUBLIC user ID by selecting the user ID and clicking the Grant button. 15. Close the Procedures Wizard. v Click the Finish button to close the Procedures Wizard. The Procedures page of the Parameters notebook remains open. v Click the Next button is to close the Procedures Page. The Catalog page of the Parameters notebook opens. Related tasks Creating Catalog Objects when working with Informix databases on page 33
36
Users Guide
7. Optional: Click the Delete icon to delete anextended catalog from the DB2 Table Editor catalog server. Use caution when deleting extended catalogs as DB2 Table Editor removes the extended catalog and all of its contents. 8. Optional: Check the Require the use of this catalog when accessing the current server check box to require all users of the database server that you are configuring in the SDF to use the specific catalog that you have selected. By checking this check box you can ensure that users will only have access to the server based on the resource limits that you have specified. 9. Click Finish. The database server that you are configuring in the SDF will use the catalog that you selected. This button is only available when creating a new entry in the SDF. The Catalog page closes saving any changes you have made to any of the server parameters. 10. Click OK. The database server that you are configuring in the SDF will use the catalog that you selected.The Catalog page closes saving any changes you have made to any of the server parameters. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Setting user information Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
37
3. In the Password field, specify the password associated with the User ID that you typed in the User ID field. 4. Optional: In the Account field, enter an accounting information string that the database server uses to track system usage. 5. Optional: Click the Change button to specify a new password for this User ID. The Change Password window opens where you can specify a new password for the user ID that you entered in the User ID field. 6. Optional: Check the Remember Password check box to have DB2 Table Editor use the password specified in the Password or New Password fields across multiple DB2 Table Editor sessions. If unchecked, DB2 Table Editor uses the password only for the duration of the current session. 7. Optional: Check the Use this information for every server I connect to check box to use the same user ID and password entered in the User ID and Password fields for connecting to all database servers. If checked DB2 Table Editor will use the same user ID and password for all connections unless you open the Set User Information window and make a change. 8. Click OK to set the user information that you have specified. If you specified a new password, it has been changed at the database server. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Defining an Informix Database Server in an SDF Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
38
Users Guide
4. On the Security page, specify the security options for your server. For more information on the security options that are available, see the fields and controls information for the Parameters notebook. 5. Click Next. The Connection page opens. 6. On the Connection page, select the Connect to Informix using ODBC radio button. Specify the ODBC parameters associated with your database. For more information on connectivity parameters, see the fields and controls information for the Parameters notebook. 7. Click Next. The Set User Information window opens. 8. From the Set User Information window, specify the UserID, password, and account to be used to connect to the database that you are defining. 9. Click Next. The Catalog page opens. 10. On the Catalog page, un-check the Use a catalog with the current server check box. 11. Click Finish. The server is defined in the SDF. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
Setting up governing
DB2 Table Editor incorporates a resource governor that limits and controls the use of database and communications resources. Use DB2 Table Editor Console to set up the resource limits groups that manage, control, and restrict this resource usage. The governing function of DB2 Table Editor is always active. If no explicit limits are in effect, governing is performed based on the limits in the default resource limits group.
39
Working with server definition files (SDFs) on page 23 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component
After you have created a SDF, each user must specify which SDF they want to use in the Developer and DB2 Table Editor components. Both the Developer and DB2 Table Editor component use the same SDF. 1. In either the Developer or DB2 Table Editor component, select View --> Options. The Options notebook opens. 2. In the Options notebook, click the General tab. 3. On the General page, in the Server definition file field, type the SDF name, or navigate to the location of the SDF that you want to use and select the file using the ... button. Note: The default location for the server definition file Windows 2000 is the WINNT directory. 4. Click OK. The Options notebook closes. The server definition file that you selected will be used for both the Developer and DB2 Table Editor components of DB2 Table Editor on your machine. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs on page 41 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37
40
Users Guide
Defining an Informix Database Server in an SDF on page 38 Changing the default SDF to be used by the Developer or DB2 Table Editor component
Changing the default SDF to be used by the Developer or DB2 Table Editor component
1. Select View --> Options. The Options notebook opens. 2. In the Options notebook, click the General tab. 3. On the General page, in the Server definition file field, type the SDF name, or navigate to the location of the SDF that you want to use and select the file using the ... button. Note: The default location for the server definition file on Windows 2000 is the WINNT directory. 4. Click OK. The Options window closes. 5. The servers that are defined in the SDF that you selected now appear in your server list. Related concepts Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Managing SDFs Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40
Managing SDFs
After an SDF has been created, it must be managed. SDFs are usually managed by one administrator, not each end user. Whenever any updates are made to an SDF (such as adding a new server), the administrator must save the changes to that location in order for all users to use the updated SDF. The next time each user starts theirDB2 Table Editor component or Developer component session, the changes the updates to the SDF will be available. Some common SDF management tasks are: v Adding a new database server v Changing a database servers configuration parameters v Changing a database servers security parameters v Changing user profiles v Changing resource limits Related concepts
Chapter 2. Getting Started with DB2 Table Editor Console component
41
Working with server definition files (SDFs) on page 23 Setting up governing on page 39 Related tasks Creating a Server Definition File (SDF) on page 24 Defining a DB2 Database Server in an SDF on page 25 Setting security parameters on page 27 Specifying server connectivity on page 28 Creating Catalog Objects and Binding Packages when working with DB2 databases on page 30 Creating Catalog Objects when working with Informix databases on page 33 Selecting the DB2 Table Editor catalog on page 36 Setting user information on page 37 Defining an Informix Database Server in an SDF on page 38 Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 40 Changing the default SDF to be used by the Developer or DB2 Table Editor component on page 41
Sample tables
DB2 Table Editor provides nine sample tables that you can use while learning DB2 Table Editor before you begin working with your own tables. The sample tables are used throughout the documentation as examples. They contain information about a fictitious electrical parts manufacturing company.
Setting up Governing
Through governing you can control the actions a user can perform and implement limits on the resources a user can consume when using DB2 Table Editor. There are three parts to setting up governing. First, you create a resource limits group. Second, you create the schedules for the resource limits group. Third, you assign users to one or more resource limits groups. Once your resource limits group is created, you can modify the schedule and assign users at any time.
42
Users Guide
Setting up resource limits groups with specific schedules and assigned users is optional. If you do not set up specific resource limits groups, all users fall into a default resource limits group that has no restrictions. 1. Open the Resource Limits page of the Parameters notebook. 2. Create the resource limits groups for the database server that you selected from theServers list in the DB2 Table Editor Console window. Create the resource limits groups for the database server that you selected from theServers list in the DB2 Table Editor Console window. To create a resource limits group click the New icon. The New Resource Limits Group window opens. Note: All resource limits groups that exist are listed in the Matching groups list box. Every database server has a resource limits group called default. The default resource limits group includes all users and has no resouce limitations. Use the Show resource limits groups whose names match field and the Refresh List button to search for specific resource limits groups that exist on the database server. Use a % sign in the Show resource limits groups whose names match field to list all resource limits groups that exist on the database server. 3. Create one or more schedules for the resource limits group. Create one or more schedules for the resource limits group. To create a schedule, select the resource limits group from Matching groups list box and click the Edit icon. The Edit Resource Limits Group window opens. Note: All resource limits groups that exist are listed in the Matching groups list box. Every database server has a resource limits group called default. The default resource limits group includes all users and has no resouce limitations. Use the Show resource limits groups whose names match field and the Refresh List button to search for specific resource limits groups that exist on the database server. Use a % sign in the Show resource limits groups whose names match field to list all resource limits groups that exist on the database server. 4. Assign users to a resource limits group. Select a resource limits group from the Matching Groups list box. Click the Assign button. The Assign User Profiles to Group window opens. Note: You can also assign users to a resource limits group by using theUser Profiles page of the parameters notebook. 5. Click OK to close the Resource Limits page of the Parameters notebook. The Parameters notebook closes, saving any changes you have made to any of the server parameter. rameters are saved.
43
2. In the Group name field specify the name for the new resource limits group. 3. Optional:In the Comments field specify up to 80 characters of comments describing the resource limits group. 4. Optional: Check the Create this group using schedules from model group check box to create the resource limits group with the same schedules as the model group. The model group is the resource limits group you selected in the Matching Groups list box from the Resource Limits page of the Parameters notebook. If this check box is unchecked, the new resource limits group has no schedules other than the default schedule. You create or modify a resource limits groups schedule using the Edit Resource Limits Group window. 5. Click OK. The New Resource Limits Group window closes and the new resource limits group is created. The Edit Resource Limits Group window opens. From the Edit Resource Limits Group window you can create or modify the resource limits groups schedule. Related tasks Creating a Resource Limits Group Schedule Assigning Users to a Resource Limits Group on page 45 Specifying Parameters for a Resource Limits Group Schedule on page 46 Assigning Users without a User Profile to a Resource Limits Group on page 47 Creating User Profiles on page 48 Managing User Profiles on page 48 Selecting a Resource Limits Group for a User Profile on page 49
44
Users Guide
radio button. None of the schedules are in effect except the the default schedule. The schedules are saved and can be activated at any time. 6. Click OK. The Edit Resource Limits Group window closes. The new resource limits group schedule is created and any changes that you have made to the resource limits parameters are saved. Related tasks Creating Resource Limits Groups on page 43 Assigning Users to a Resource Limits Group Specifying Parameters for a Resource Limits Group Schedule on page 46 Assigning Users without a User Profile to a Resource Limits Group on page 47 Creating User Profiles on page 48 Managing User Profiles on page 48 Selecting a Resource Limits Group for a User Profile on page 49
45
6. Optional: To remove a user profile from the list of resource limits group assigned users, select the user profile from the Assigned list. Click the Unassign button. The user profile is moved to Not Assigned list. 7. Optional: To remove all the user profiles from the Assigned list and move them to the Not Assigned list. click the Unassign All button. 8. Click the OK button. The Assign User Profiles window closes and your changes to the resource limits group user assignments are saved. The Resource Limits page of the Parameters notebook opens. Related tasks Creating Resource Limits Groups on page 43 Creating a Resource Limits Group Schedule on page 44 Specifying Parameters for a Resource Limits Group Schedule Assigning Users without a User Profile to a Resource Limits Group on page 47 Creating User Profiles on page 48 Managing User Profiles on page 48 Selecting a Resource Limits Group for a User Profile on page 49
46
Users Guide
account information; and the ability to fetch all rows automatically, export data, edit tables, and only run saved queries. v Select the Save Data page to allow users assigned to this resource limits group and using this schedule to save data at the database server. v Select the Binding page to allow users assigned to this resource limits group and using this schedule to bind or drop static packages for their queries. v Select the LOB Options page to control users who are assigned to this resource limits group and using this schedule access to and retrieval of data from tables containing large object data (LOB). v Select the Report Center page to grant users of the DB2 Table Editor Report Center application who are assigned to this resource limits group and using this schedule the authority to create reports, control access to reports, and take ownership of any other users reports. 3. Click OK. The Edit Resource Limits Group Schedule notebook closes. All the changes that you have made to the resource limits parameters are saved. The Edit Resource Limits Group window stays open. Related tasks Creating Resource Limits Groups on page 43 Creating a Resource Limits Group Schedule on page 44 Assigning Users to a Resource Limits Group on page 45 Assigning Users without a User Profile to a Resource Limits Group Creating User Profiles on page 48 Managing User Profiles on page 48 Selecting a Resource Limits Group for a User Profile on page 49
47
48
Users Guide
The Matching Profiles list includes all the user profiles from the profile table that match the value specified in the Show User Profiles whose names match field. 3. Click the Add icon to add a new user profile to the profile table. The User Profile window opens. 4. Optional:To edit a user profile, select the the user profile you want to change from the Show User Profiles whose names matchlist. Click the Edit icon. The User Profile window opens. 5. Optional: To delete a user profile from the profile table on the databasse server, select the user profile that you want to delete from the Show User Profiles whose names matchlist. Click the Delete icon. The user profile is deleted from the profile table on this database server. 6. Click OK to close the User Profiles page of the Parameters notebook. The Parameters notebook closes, saving any changes you have made to any of the server parameter. Related tasks Creating Resource Limits Groups on page 43 Creating a Resource Limits Group Schedule on page 44 Assigning Users to a Resource Limits Group on page 45 Specifying Parameters for a Resource Limits Group Schedule on page 46 Assigning Users without a User Profile to a Resource Limits Group on page 47 Creating User Profiles on page 48 Selecting a Resource Limits Group for a User Profile
49
database servers. The DB2 Table Editor administrator is responsible for creating, configuring and maintaining SDFs for DB2 Table Editor end users. You must supply DB2 Table Editor with at least one SDF to use. DB2 Table Editor installs with a default SDF called db2sdf.ini. that you can use and configure for your environment. If you choose to use this file, you do not need to create a new SDF. You would create a new SDF if you are not planning to use the default SDF, or you are going to distribute multiple SDF files. Note: Editing the DB2 Table Editor SDF using any method or application other than DB2 Table Editor Console is not recommended and may cause the file to be corrupted. 1. Open the DB2 Table Editor Console window. 2. From the File --> New menu, select New. 3. In the File Name field on the New window, type the name of the SDF that you want to create and click save. The new SDF is created. Upon saving, the DB2 Table Editor Console points to the new SDF. The new SDF is displayed in the Console window file menu. Using the Parameters notebook, you must configure each database server that you or your users will access using the new SDF.
Creating a new server definition file based on an existing server definition file
Use Save As from the File menu to create a new SDF. DB2 Table Editor creates a new SDF that is modeled on the currently open SDF. The new SDF contains the same server definitions as the model SDF. You create a new SDF if you plan to distribute multiple SDF files or a SDF other than the default. 1. 2. 3. 4. 5. Open the DB2 Table Editor Console window. Click File > Save As. A Save AS file window opens. In the Save in field specify where to save the new SDF. In the File Name field, type the name of the new DB2 Table Editor SDF. Click Save. The Save As window closes. DB2 Table Editor creates the new SDF using the currently opened SDF as a model. The new SDF includes all the configured servers and their parameters of the model SDF. Control returns to the Console window. Upon saving, DB2 Table Editor Console points to the new SDF. The new SDF displays in the Console window menu bar. You can make changes to the new SDF using the Parameters notebook.
50
Users Guide
3. 4. 5. 6.
the DLL DB2 Table Editor will use to access CPI-C services. If any database server will be accessed by DB2 Table Editor using DRDA over SNA connectivity, you must specify the CPI-C services DLL in the Provider DLL field. Optional: Use the TCP page of the Options notebook to specify timeout limits for all database servers using DRDA over TCP/IP connectivity. Optional: Use the CLI page to specify timeout limits for all database servers using CLI connectivity. Optional: Use the ODBC page to specify timeout limits for all database servers using ODBC connectivity. Click OK. The Options notebook closes and all changes made to the connectivity options are applied.
51
7.
8.
9.
10.
catalog. If you choose to specify that the model ODBC server will not use a DB2 Table Editor catalog, then all of the data sources that are dynamically defined based on that model will not use a DB2 Table Editor catalog. Likewise, if you choose to specify that the model ODBC server will use a specific DB2 Table Editor catalog, then all of the data sources that are dynamically defined based on that model will use that DB2 Table Editor catalog. Optional: Use the Resource Limits page of the Parameters notebook to set up governing for the model ODBC database server. The governing parameters specified will apply to all the local ODBC data sources that are dynamically defined based on the model ODBC database server entry. Optional: Use the User Profiles page of the Parameters notebook to create a new user profile. User Profiles are used to assign users to resource limits groups. All users not assigned to a specific group are included in the default resource limits group. The Connections, Packages, and Sample Tables pages of the Parameters notebook are not available when configuring the model ODBC database server. This is because the type of connectivity is assumed to be ODBC and you cannot create objects, bind packages or create sample tables on any ODBC database server. Click OK to save the model ODBC database server configuration parameters. The Parameters notebook closes.
Activating Tracing
Use the Options notebook to activate tracing. Tracing is usually activated when you are diagnosing a problem. By selecting the Traces option you tell DB2 Table Editor to start recording data about one or more of the components it might use during processing. Note: The amount of data that is recorded during tracing can be significant. It is recommended that tracing be used cautiously as it will impact performance. 1. Open the Options notebook.
52
Users Guide
2. Optional: Use the Tracing page to activate tracing. 3. In the Trace file field specify the name of the trace file that DB2 Table Editor can use to write trace data. To search for a file, click the Browse icon. 4. From the Components list box select one or more of the components for tracing. 5. Click OK. The Options notebook closes and all changes made to the connectivity options are applied. Tracing starts as soon as any user activates DB2 Table Editor using the selected SDF.
53
window opens. Using this window change the keyword or its associated value. Upon closing, the changed keyword and value are listed in the Advanced DSN Settings window. 4. Click OK. The Advanced DSN settings window closes. The new or changed keywords and values are saved. The Connection page of the parameters notebook stays open.
54
Users Guide
Use the DB2 Table Editor Console window to initiate the following tasks:
v v v v v v v v v v v v v Creating a New Server Definition File Creating a new Server Definition File based on an existing Server Definition File Configuring the Server Definition File Assigning the server a name in the Server Definition File Defining a Database Server in the Server Definition File Defining a database in the server definition file Parameters Notebook Overview Deleting a Server from the Server Definition File Importing DB2 for Windows databases Enabling dynamic definition of ODBC servers Publishing the SDF Setting connectivity options Activating Tracing
55
v v v v v v v
Setting security parameters Specifying server connectivity Creating Catalog Objects and Binding Packages Selecting the DB2 Table Editor catalog Setting up Governing Managing User Profiles Creating Sample Tables
Cancel Click this button to close the Resource Limits Groups at Server window. A resource limits group is not inserted in the Resource Groupfield of the New Profile window. The User Profile window stays open.
56
Users Guide
OK
Click this button to close the User Profile window. The user profile is added to the profile table. The User Profile page of the Parameters notebook opens. Click this button to close the User Profile window. The user profile is not added to the profile table. The User Profile page of the Parameters notebook opens.
Cancel
57
search criteria specified in the Show User Profiles with creator matching, and are assigned to the resource limits group. Create New Click this button to create a new user profile. The New Profile window opens. Assign Click this button to assign the selected user profile to the resource limits group. The selected user profile moves from the Not Assigned list to the Assigned list. Unassign Click this button to remove the selected user profile from the list of assigned resource limits group users. The selected user profile moves from the Assigned list to the Not Assigned list. Unassign All Click this button to remove all the user profiles listed in the Assigned list from the resource list group. All of the user profiles move from the Assigned list to the Not Assigned list. OK Click this button to close the Assign User Profiles window. The changes that you made to the resource limits group user profile assignments are saved. The Edit Resource Limits Group window stays open. Click this button to close the Assign User Profiles window The changes that you made to the resource limits group user profile assignments are discarded. The Edit Resource Limits Group window stays open.
Cancel
Edit / New Resource Limits Group Schedule notebook Fields and Controls Information
Main page
Number Select from this drop down list a number from 1 to 99. This number is used to identify the schedule and represent the schedules priority. A number is assigned to the schedule only when it is created. The schedule number must be unique. Once assigned, you cannot change the schedule number and its assigned priority. DB2 Table Editor uses the schedules priority number to decide which schedule is in effect when schedules overlap. If two schedules for the resource limits group cover the same time period, the schedule with the lower number takes precedence. Day Range Select from the From drop down list a day of the week that will be the starting day and select form the To drop down list, a day of the week that will be the ending day for the schedule. The schedule is in effect from the starting day to the ending day, inclusive. You can specify a day range that wraps around the end of the week. For example, selecting Friday through Monday activates the schedule Friday, Saturday, Sunday and Monday. In reverse, selecting Monday through Friday activates the schedule Monday, Tuesday, Wednesday, Thursday and Friday. Time Range In the From field, type a time to start the schedule. In the To field, type a time to end the schedule. The schedule is in effect from the start time to the
58
Users Guide
end time, inclusive. Time is specified using a 24 hour clock. You can specify a time range that wraps around midnight. For example, selecting 23:00 through 7:00 will activate the schedule from 11:00 at night until 7:00 in the morning. In reverse, selecting 7:00 through 23:00 will activate the schedule from 7:00 in the morning till 11:00 at night. Status Use these radio buttons to set the status of the individual schedule. The status of the whole Resource Limits group takes priority set using theStatus button on the Edit Resource Limits Group window takes precedence over the individual schedule status. There are two choices of status: Active Click this radio button to activate this schedule. Inactive Click this radio button to deactivate this schedule. An inactive schedule remains as it was defined until you activate it or delete the schedule from the resource limits group. You may activate the schedule at any time. OK Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are saved. The Edit Resource Limits Group window stays open. Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are discarded. The Edit Resource Limits Group window stays open.
Cancel
Timeouts page
Server Response Timeouts (seconds) Use this field to limit the amount of time DB2 Table Editor waits for a response from the database server before canceling a request. DB2 Table Editor waits asynchronously for a response each time it sends a request to the database server. There are two timeout limits that you can specify: Warning Limit Type the number of seconds that DB2 Table Editor should wait for a response to its request from the database server before the user is informed and asked if the request should be canceled. Cancel Limit Type the number of seconds that DB2 Table Editor should wait for a response to its request from the database server before the request is canceled. Idle Connection Timeout (seconds) Use this field to limit the amount of time DB2 Table Editor retains an idle connection to a database server. There is one timeout limit that you can specify: Cancel Limit Type the number of seconds that DB2 Table Editor should retain an idle connection to a database server before the connection is canceled. By specifying a lower timeout limit you can minimize the resources consumed at database servers by idle connections. By specifying a higher timeout limit you can minimize the overhead of establishing connections. OK Click this button to close the Edit Resource Limits Group Schedule
Chapter 2. Getting Started with DB2 Table Editor Console component
59
notebook. All changes to the resource limits group schedule parameters are saved. The Edit Resource Limits Group window stays open. Cancel Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are discarded. The Edit Resource Limits Group window stays open.
Limits page
Maximum Rows to Fetch Use this field to limit the number of rows of data that are retrieved from a database server when running a query. You can set two timeout limits: Warning Limit Type the number of rows that can be retrieved from the database server before the user is notified that a row limit has been reached. The user is asked if the query should be canceled. Cancel Limit Type the number of rows that can be retrieved from the database server before the row Limit is reached and the query is canceled. Maximum Bytes to Fetch Use this field to limit the number of bytes of data that are retrieved from a database server when running a query. You can set two timeout limits: Warning Limit Type the number of bytes that are retrieved from the database server before the user is notified that a byte limit has been reached. The user is asked if the query should be canceled. Cancel Limit Type the number of bytes that can be retrieved from the database server before the byte limit is reached and the query is canceled. Maximum Connections Use this field to limit the number of simultaneous connections that DB2 Table Editor can establish to a database server. You can set one timeout limits: Cancel Limit Type the number of simultaneous connections that DB2 Table Editor can establish to a database server before the query requesting the next connection is canceled. DB2 Table Editor generally reuses server connections. If you run one query at a database server, than run another query at the same database server, only one connection is required. However, if you run those two queries simultaneously, then two connections are required. OK Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are saved. The Edit Resource Limits Group window stays open. Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are discarded. The Edit Resource Limits Group window stays open.
Cancel
60
Users Guide
Options page
Allow access to server Check this check box to permit all users that are assigned to this resource limits group to access the database server when this schedule is in effect. Account Use this field to specify the default accounting information to be used when members of this resource limits group connect to a database server when this schedule is in effect. Account can be overridden Check this check box to allow members of this resource limits group to override the default accounting information specified in the Accountfield when they connect to a database server and this schedule is in effect. You can enter a new accounting string using the Set User Information window. Account must be specified Check this check box to specify that members of this resource limits group must specify valid accounting information in the Set User Information window before connecting to a database server when this schedule is in effect. OK Click this button to close the Edit Resource Limits Group Schedule notebook. all changes to the resource limits group schedule parameters are saved. The Edit Resource Limits Group window stays open. Click this button to close the Edit Resource Limits Group Schedule notebook. All changes to the resource limits group schedule parameters are discarded. The Edit Resource Limits Group window stays open.
Cancel
61
for a resource limits group are deactivated, DB2 Table Editor uses the default schedule which includes all users and has no resource limits restrictions. All of the deactivated schedules are saved and can be reactivated using the Activate. Schedule List This field lists the schedules that are defined for the resource limits group. A default resource limits group schedule is always included for all database servers. New Click this button to create a new resource limits group schedule. The Main page of the Edit Resource Limits Group Schedule notebook opens. Using this notebook you can specify the schedule and resource limits for the resource limits group. Click this button to modify the resource limits group schedule that you selected from the Schedule List. The Timeouts page of the Edit Resource Limits Group Schedule notebook opens. Using this notebook you can specify the scedule and resource limits for the resource limits group.
Edit
Delete Click this button to remove the resource limits group schedule that you selected from the Schedule List. DB2 Table Editor deletes this schedule and all of its parameters from the resource limits group. OK Click this button to close the Edit Resource Limits Group window. Any new schedules, changes to existing scedules or status changes are saved. The Resource Limits page of the Parameters notebook stays open. Click this button to close the Edit Resource Limits Group window. Any new schedules, changes to existing scedules or status changes are discarded. The Resource Limits page of the Parameters notebook stays open.
Cancel
62
Users Guide
Cancel Click this button to close the New Resource Limits Group window. The resource limits group is not created. The resource Limits page of the Parameters notebook stays open.
63
Comment Use this field to type a comment that can be up to 80 characters in length. Replace Existing package Check this check box to replace all existing DB2 Table Editor packages that exist on this database server with the specified collection ID with the new DB2 Table Editor packages. If you check this check box, the Replace existing packages check box on the Bind packages page of the Packages wizard is also checked. Any changes made to one of these check boxes is also automatically made to the other check box. Keep existing authorizations Check this check box to keep the authorizations that are specified for the existing DB2 Table Editor packages. If you check this check box, the Keep existing authorizations on packages check box on the Bind packages page of the Packages wizard is also checked. Any changes made to one of these check boxes is also automatically made to the other check box. OK Cancel Click this button to close the Bind Options notebook. Any changes that you have made to the options are discarded. Click this button to close the Bind Options notebook. Any changes that you have made to the options are saved.
Formats page
Decimal Delimiter You use the Decimal Delimiter option to specify the character that must be used by DB2 Table Editor to represent a decimal point in the SQL statements that are run on this database server. There are three choices: Unspecified Select this button to specify that there is no decimal delimiter specified for this database server. Period Select this button to specify that a period is to be used as the decimal delimiter in the text of the SQL statements that are run on this database server. If you select this option, the Period button on the Packages page of the Parameters notebook is also checked. Any changes made to one of these buttons is also automatically made to the other button. Comma Select this button to specify that a comma is to be used as the decimal delimiter in the text of the SQL statements that are run on this database server. If you select this option, the Comma button on the Packages page of the Parameters notebook is also checked. Any changes made to one of these buttons is also automatically made to the other button. String Delimiter You use the String Delimiter option to specify the character that must be used to separate character strings in the SQL statements that are run on this database server. There are three choices: Unspecified Select this button to specify that there is no string delimiters specified for this database server.
64
Users Guide
Apostrophe Select this button to specify that an apostrophe is to be used as the string delimiter in the text of the SQL statements that are run at this database server. If you select this option, the Apostrophe button on the Packages page of the Parameters notebook is also checked. Any changes made to one of these buttons is also automatically made to the other button. Quote Select this button to specify that a quote is to be used as the string delimiter in the text of the SQL statements that are run at this database server. If you select this option, the Quote button on the Packages page of the Parameters notebook is also checked. Any changes made to one of these buttons is also automatically made to the other button. Date Format Use the Date Format option to specify how dates are to be formatted for this database server. There are five choices: Unspecified Check this button to specify that there is no date formatting used when binding the DB2 Table Editor packages. ISO Check this button to specify that the International Organization for Standardization (ISO) date format will be used when binding the DB2 Table Editor packages. Dates will appear in the following format: YYYY:MM:DD. Check this button to specify that the United States (USA) date format will be used when binding the DB2 Table Editor packages. Dates will appear in the following format: MM:DD:YYYY. Check this button to specify that the European (EUR) date format will be used when binding the DB2 Table Editor packages. Dates will appear in the following format: DD:MM:YYYY. Check this button to specify that the Japanese Industrial Standard (JIS) date format will be used when binding the DB2 Table Editor packages. Dates will appear in the following format: YYYYMMDD.
USA
EUR
JIS
Time Format You use the Date Format option to specify how times will be formatted. There are five choices: Unspecified Check this button to specify that there will be no time formatting used when binding the DB2 Table Editor packages. ISO Format Check this button to specify that the International Organization for Standardization (ISO) time format will be used when binding the DB2 Table Editor packages. Times will appear in the following format: HH:MM:SS. USA Format Check this button to specify that the United States (USA) time format will be used when binding the DB2 Table Editor packages. Times will appear in the following format: HH:MM:AM or HH:MM:PM.
65
EUR Format Check this button to specify that the European (EUR) time format will be used when binding the DB2 Table Editor packages. Times will appear in the following format: HH:MM:SS. JIS Format Check this button to specify that the Japanese Industrial Standard (JIS) time format will be used when binding the DB2 Table Editor packages. Times will appear in the following format: HH:MM:SDD. OK Cancel Click this button to close the Bind Options notebook. Any changes that you have made to the options are discarded. Click this button to close the Bind Options notebook. Any changes that you have made to the options are saved.
66
Users Guide
database changes. For more information on Isolation Level options, refer to your database products documentation. Query Blocking Use this option to specify the blocking protocol DB2 Table Editor will use. There are four choices: Unspecified Check this radio button to specify that no special query blocking options will be used in binding the DB2 Table Editor packages. DB2 Table Editor uses your database default values. For more information on Query Blocking options, refer to your database products documentation. All Check this radio button to specify that the query blocking option used in binding the DB2 Table Editor packages will be All. For more information on Query Blocking options, refer to your database products documentation.
Unambiguous Check this radio button to specify that the query blocking option used in binding the DB2 Table Editor packages will be Unambiguous. For more information on Query Blocking options, refer to your database products documentation. None Check this radio button to specify that the query blocking option used in binding the DB2 Table Editor packages will be None. For more information on Query Blocking options, refer to your database products documentation.
Release Use this option to specify when the RDB will release the resources used by DB2 Table Editor. There are three choices: Unspecified Release Check this radio button to specify that no special release options will be used in binding the DB2 Table Editor packages. DB2 Table Editor uses your database default values. For more information on Release options, refer to your database products documentation. Commit Check this radio button to specify that the release option used in binding the DB2 Table Editor packages will be Commit. Commit specifies that the RDB releases resources used by the package every time a unit of work is either committed or rolled back. For more information on Release options, refer to your database products documentation. Deallocate Check this radio button to specify that the release option used in binding the DB2 Table Editor packages will be Deallocate. Deallocate specifies that the target RDB releases resources used by the package when the conversation with the database server is finished or deallocated. For more information on Release options, refer to your database products documentation. Degree of Parallelism Use this field to enter the required information if your database supports a degree of parallelism option. For more information on Degree of Parallelism options, refer to your database products documentation.
67
Query Optimization Use this field to enter the required information if your database supports query optimization For more information on Query Optimization options, refer to your database products documentation. OK Cancel Click this button to close the Bind Options notebook. Any changes that you have made to the options are discarded. Click this button to close the Bind Options notebook. Any changes that you have made to the options are saved.
Statements page
Explain Use this option to specify whether DB2 Table Editor will gather and record explain data during processing. There are four choices: Unspecified Check this radio button to specify that DB2 Table Editor will use your database default setting to determine whether or not explain data will be gathered. For more information on Explain options, refer to your database products documentation. All Check this radio button to specify that DB2 Table Editor will use the All option to determine whether or not explain data will be gathered. For more information on Explain options, refer to your database products documentation. Check this radio button to specify that DB2 Table Editor will gather explain data. For more information on Explain data options, refer to your database products documentation. Check this radio button to specify that DB2 Table Editor will not gather explain data. For more information on Explain options, refer to your database products documentation.
Yes
No
Explain Snapshot Use this option to specify whether DB2 Table Editor will gather and record a snapshot version of the explain data during processing. There are four choices: Unspecified Check this radio button to specify that DB2 Table Editor will use your database default setting to determine whether or not a snapshot of the explain data will be gathered. For more information on the Explain Snapshot options, refer to your database products documentation. All Check this radio button to specify that DB2 Table Editor will use the All option to determine whether or not a snapshot of the explain data will be gathered. For more information on the Explain Snapshot options, refer to your database products documentation. Check this radio button to specify that DB2 Table Editor will gather a snapshot of explain data. For more information on the Explain Snapshot options, refer to your database products documentation. Check this radio button to specify that DB2 Table Editor will not gather a snapshot of explain data. For more information on Explain Snapshot options, refer to your database products documentation.
Yes
No
68
Users Guide
Validate Time Use this option to specify when packages are validated in your database environment. There are three choices: Unspecified Check this radio button to specify that DB2 Table Editor will use your database default setting. For more information on the Validate Time options, refer to your database products documentation. Bind Check this radio button to specify that validation will be done during the bind process. For more information on the Validate Time options, refer to your database products documentation. Check this radio button to specify that validation will be done at runtime. For more information on the Validate Time options, refer to your database products documentation.
Run
Return SQL Warnings Check this check box to have any SQL warnings issued during the validation process returned. For more information on the Return SQL Warnings options, refer to your database products documentation. OK Cancel Click this button to close the Bind Options notebook. Any changes that you have made to the options are discarded. Click this button to close the Bind Options notebook. Any changes that you have made to the options are saved.
Miscellaneous page
Dynamic rules Use this option to specify any dynamic rules that are specific to your database environment. There are seven choices: Unspecified Check this radio button to specify that DB2 Table Editor will use your database default settings. For more information on the Dynamic rules options, refer to your database products documentation. Run Check this radio button to specify that DB2 Table Editor will use run as a dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation. Check this radio button to specify that DB2 Table Editor will use bind as a dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation.
Bind
Invoker/requestor Check this radio button to specify that DB2 Table Editor will use invoker/requestor as the dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation. Invoker/owner Check this radio button to specify that DB2 Table Editor will use invoker/owner as the dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation.
69
Definer/requestor Check this radio button to specify that DB2 Table Editor will use definer/requestor as the dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation. Definer/owner Check this radio button to specify that DB2 Table Editor will use definer/owner as the dynamic rule. For more information on the Dynamic rules options, refer to your database products documentation. Character Sub Types Use this option to specify the character sub-types for your database environment. There are five choices: Unspecified Check this radio button to specify that there are no character sub-types defined. For more information on the Character Sub-Type options, refer to your database products documentation. FOR BIT DATA Check this radio button to specify that DB2 Table Editor will use bit data as the character sub-type. For more information on the Character Sub-Type options, refer to your database products documentation. FOR SBCS DATA Check this radio button to specify that DB2 Table Editor will use SBCS data as the character sub-type. For more information on the Character Sub-Type options, refer to your database products documentation. FOR MIXED DATA Check this radio button to specify that DB2 Table Editor will use mixed data as the character sub-type. For more information on the Character Sub-Type options, refer to your database products documentation. Default Check this radio button to specify that DB2 Table Editor will use the default set up in your database for all applications. For more information on the Character Sub-Type options, refer to your database products documentation. Generic options Use this field to specify any generic options that are required in your database environment. For more information on Generic Options options, refer to your database products documentation. OK Cancel Click this button to close the Bind Options notebook. Any changes that you have made to the options are discarded. Click this button to close the Bind Options notebook. Any changes that you have made to the options are saved.
70
Users Guide
71
notebook., you can select the database server that hosts the DB2 Table Editor catalog that will be used by the database server you are configuring. There are several reasons to have database servers share a DB2 Table Editor catalog. One reason is that ODBC database servers cannot host the DB2 Table Editor catalog. The DB2 Table Editor catalog for an ODBC database server must reside on a DB2 database server that is connected to using TCP/IP, SNA or CLI. Another reason to share a catalog is to streamline DB2 Table Editor catalog maintenance or to control an end users view of the database objects stored in the catalog. Back Next Cancel Click this button to close the Catalog Option page of the Packages Wizard or Procedures Wizard. The Packages Wizard or Procedures Wizard closes without completing its processing. The Packages page stays open. This button is not available from the Catalog Option page as it is the first page of the Packages Wizard or Procedures Wizard. Click this button to open the Package Properties page of the Packages Wizard or the Procedure Properties page of the Procedure Wizard.
72
Users Guide
decimal delimiter in the SQL text that is run on this database server. A period is the default decimal delimiter. Changing the decimal delimiter in this field, changes the decimal delimiter selected in the decimal delimiter field on the Packages page of the parameters notebook. Apostrophe Select this radio button to specify that an apostrophe is to be used as the string delimiter in the SQL text that is run on this database server. An apostrophe is the default string delimiter. Changing the string delimiter in this field, changes the string delimiter selected in the string delimiter field on the Packages page of the parameters notebook. Quote Select this radio button to specify that a quote is to be used as the string delimiter in the SQL text that is run on this database server. An apostrophe is the default string delimiter. Changing the string delimiter in this field, changes the string delimiter selected in the decimal delimiter field on the Packages page of the parameters notebook. Advanced Click this button to open the Bind Options notebook. You use the Bind Options notebook to specify additional binding options for the DB2 Table Editor packages. These options are optional. Back Next Cancel Click this button to close the Package Properties page of the Packages Wizard. The Packages Wizard closes without completing its processing. The Packages page of the Parameters notebook stays open. Click this button to close the Packages Properties page of the Packages Wizard. The Catalog Option page of the Packages Wizard opens. Click this button to close the Packages Properties page of the Packages Wizard. The Check Options page of the Packages Wizard opens.
73
Automatically check which objects already exist Check this check box to create only those DB2 Table Editor objects that do not already exist on the database server. Use this option when you are updating DB2 Table Editor on a database server. Assume that all of the objects already exist Check this check box to bypass creating the DB2 Table Editor database objects. Use this option if all the database objects exist and you are not making any changes. If you check this check box, clicking Next opens the Bind Packages page of the Packages Wizard. Back Click this button to close the Check Options page of the Packages Wizard or Procedures Wizard. The Package Properties page of the Packages Wizard or the Procedure Properties page of the Procedures Wizard opens. Click this button to close the Check Options page of the Packages Wizard or Procedures Wizard. The Object Listing page of the Packages Wizard or Procedures Wizard opens. If you checked the Assume that all of the objects already exist check box, the Bind Packages page opens. Click this button to close the Check Options page of the Packages Wizard or Procedures Wizard. The Packages Wizard closes without completing its processing. The Packages page or Procedures page of the Parameters notebook stays open.
Next
Cancel
74
Users Guide
access to are defined outside of DB2 Table Editor. If you check this check box, you must set up a DB2 Table Editor table that includes all the authorization IDs. Back Click this button to close the Object Listing page of the Packages Wizard or Procedures Wizard. The Check Options page of the Packages Wizard or Procedures Wizard opens. Click this button to close the Object Listing page of the Packages Wizard or Procedures Wizard. The Create Objects page of the Packages Wizard or Procedures Wizard opens. Click this button to close the Object Listing page of the Packages Wizard or Procedures Wizard. The Packages Wizard or Procedures Wizard closes without completing its processing. The Packages page or Procedures page of the Parameters notebook stays open.
Next
Cancel
Next
Cancel
75
selected. When this check box is checked, all DB2 Table Editor packages that exist on this database server with the specified collection ID will be replaced with the newly bound packages. If you are binding new DB2 Table Editor packages, it is recommended that you select this option. Keep existing authorizations This option is only available if the Bind the packages radio button was selected. When this check box is checked, the authorizations on the DB2 Table Editor packages that exist on this database server with the specified collection ID are maintained. If you are binding new DB2 Table Editor packages, it is recommended that you select this option. Back Next Cancel Click this button to close the Bind packages page of the Packages Wizard. The Packages Wizard closes without completing its processing. The Packages page of the Parameters notebook stays open. Click this button to close the Bind packages page of the Packages Wizard. The Check Table Authorizations page of the Packages Wizard opens. Click this button to close the Bind packages page of the Packages Wizard. The Permissions page of the Packages Wizard opens.
Permissions page
Do not check for tables with no authorizations Check this check box to specify that DB2 Table Editor should not check to see if there are tables that do not have the appropriate authorization.
76
Users Guide
Check for tables with no authorizations Check this radio button to specify that DB2 Table Editor will check the database server for tables that do not have authorizations. DB2 Table Editor searches the database server after the DB2 Table Editor packages are bound for any tables that may exist without authorizations. If any such tables are found, the Grant Table Authorization window opens requesting a user ID that it will use to grant authorization to the table. Back Next Cancel Click this button to close the Table Authorizations page of the Packages Wizard. The Packages Wizard closes without completing its processing. The Packages page of the Parameters notebook stays open. Click this button to close the Table Authorizations page of the Packages Wizard. The Create Objects page of the Packages Wizard opens. Click this button to close the Table Authorizations page of the Packages Wizard. The Bind Packages page of the Packages Wizard opens.
77
identified in the User IDs field, SELECT authority. The list of tables includes those found on the database server that do not have authorizations. User IDs Use this field to type the user IDs of those users who will be granted authorization on the tables selected in the Tables. Grant Click this button to grant the user IDs specified in the User IDs field authorization on the tables selected Tables list. Finish Click to complete the Packages Wizard or Procedures Wizard processing and return to the Packages page or Procedures page of parameters notebook. Back Cancel Click this button to close the Grant Table Authorizations page of the Packages Wizard. The Packages Wizard closes without granting any authorizations to the tables. The Packages page of the Parameters notebook stays open. Click this button to close the Grant Table Authorizations page of the Packages Wizard. The Permissions page of the Packages Wizard opens.
78
Users Guide
server uses to track system usage. The use of accounting string information is determined by your database administrator. Remember this password Check this check box to have the password specified in the Password or New password fields. saved across DB2 Table Editor sessions. Unchecked, the password is only saved for duration of the current DB2 Table Editor session. The user ID must have permission, as specified by the security parameters, to save passwords for DB2 Table Editor to use across multiple sessions. Use this information for every server I connect to Check this check box to use the user information entered on the Set User Information window for connecting to all database servers. If checked DB2 Table Editor will use the same user ID and password for all connections unless you open the Set User Information window and make a change. OK Click this button to set the user information. The Set User Information window closes. If you specified a new password, it is changed at the database server. Click this button to close the Set User Information window. Any information you specified in the Set User Information window is discarded. is discarded. Change Click this button to open the Change Password window where you can specify a new password for the user ID that you entered in the User ID field.
Cancel
79
specify any number of driver-specific keywords. Information on keywords for the specific drivers can be found in your drivers documentation. Value This field lists the value for the driver-specific keyword you entered in the Keyword field. You specify the value for the keyword using the Keyword and Value window. Information on the syntax and what can be entered as a keyword value depends on the specific driver and can be found in your drivers documentation. Add Edit Click this icon to add a Keyword or Value to the Keywords and Values list. The Keyword and Value window opens. Click this icon to change a Keyword or Value in the Keywords and Values list. The Keyword and Value window opens.
Delete Click this icon to delete a Keyword or Value from the Keywords and Values list. The keyword and value selected in the Keywords and values list are deleted. OK Cancel Click this button to close the Advanced DSN Settings window. Any changes that you have made to the Keywords and Values list are not saved. Click this button to close the Advanced DSN Settings window. Any changes that you have made to the Keywords and Values list are saved.
Next
Cancel
80
Users Guide
Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Security page
UserID and Password are required Check this check box to require DB2 Table Editor users to specify a user ID and password when connecting to the database server. When checked, DB2 Table Editor opens the Set User Information window and requests a valid user ID and password before connecting to this database server. If unchecked, you are specifying that the database server you are configuring in the SDF does not require a user ID and password. DB2 Table Editor will not automatically open the Set User Information window and request a valid user ID and password. The default for this option is to require a user ID and password. DB2 Table Editor security parameters do not override the database servers security requirements. If the database server requires a user ID and password, DB2 Table Editor must pass this information in order to make the connection. By automatically prompting the user with the Set User Information window, DB2 Table Editor ensures it has the information. There are some database servers, ODBC data sources for example, that do not require user IDs and passwords. There are some database servers that accept generic user IDs and passwords. In these cases users might not know a user ID or password. You can uncheck the User ID and password are required check box to prevent DB2 Table Editor from opening the Set User Information window, and allow users to bypass specifying a user ID or password. Allow users to change passwords Check this check box to allow users to remotely change their passwords without logging on to the database server. The database server must support this capability and the user ID must have the required authority. This option is only available for DB2 servers that are connected to using TCP/IP, SNA and CLI. This option is only available if the User ID and password are required check box is checked. Allow users to save passwords Check this check box to allow users to save their passwords. Passwords are saved in encrypted format. When checked, DB2 Table Editor for Windows does not require the user to enter a password in the Set User Information window every time a connection is made to the database server. Instead DB2 Table Editor for Windows retrieves the saved password. The saved password is used across multiple DB2 Table Editor for Windows sessions until a new password is saved or specified. This applies only to connections to DB2 servers. This option is only available if the User ID and password are required check box is checked. Encryption Select from the drop down list the type of encryption that should be used when communicating with the database server over the network. This option applies only to DRDA servers. As different types of servers support different encryption options, check with your database server administrator for more information on the type of encryption that the database server you are configuring in the SDF supports. Select one of the following options: v None to not encrypt any communications
81
v Encrypted password to encrypt just the password v Encrypted user ID and password to encrypt both user ID and password Back Click this button to close the current page of the Parameters notebook. The Back button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The previous page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. The Next button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The next page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded.
Next
OK
Cancel
Connection page
Connect Using DRDA over TCP/IP Check this check box to connect to the DB2 database server that you are configuring in the SDF using DRDA over TCP/IP connectivity. DB2 Table Editor requires a WinSock 1.1 or later interface for the installed TCP protocol stack. If you select this option, the lower half of the Connections window changes and displays the following parameters that are specific to the DRDA over TCP/IP network connection: v Host Name v Port Number v RDB Name v ANSI client CCSID v Unicode client CCSID v Enable Load balancing Connect Using DRDA over SNA Check this check box to connect to the DB2 database server that you are configuring in the SDF using DRDA over SNA. To access a DB2 server using DRDA over SNA, DB2 Table Editor must establish an LU 6.2 session between itself and DB2 using the CPI-C or WINCPIC interface. If you select this option, the lower half of the Connections window changes and displays parameters that are specific to the DRDA over SNA network connection. v Symbolic Destination Name v RDB Name v ANSI client CCSID v Unicode client CCSID v Enable Load balancing Note: If SNA connectivity is selected for the database server, you must also specify the CPI-C DLL using the CPI-C page of the global connectivity Options notebook.
82
Users Guide
Connect Using DB2 for Windows CLI Check this check box to connect to the DB2 database server that you are configuring in the SDF using DB2 for Windows CLI connectivity. To access a DB2 server using DB2 for Windows CLI, the 32-bit version of DB2 Table Editor must establish a CLI connection from the local host to the remote host via the DB2 UDB client. All of the connectivity information is defined in the DB2 UDB client. If you select this option, the lower half of the Connections window changes and displays parameters that are specific to the DB2 for Windows CLI network connection. v Database Alias v Advanced Connect to Informix using ODBC Check this check box to connect to the Informix database server that you are configuring in the SDF using ODBC connectivity. ODBC connectivity must be used to connect to Informix data sources. To connect to multiple data sources using ODBC, you must either configure each data source individually in the SDF or dynamically enable all ODBC data source definitions. If you select this option, the lower half of the Connections window changes and displays parameters that are specific to the ODBC network connection. v v v Machine Data Source Name File Data Source Name Advanced
Connect to other data sources using ODBC Check this check box to connect to the database server that you are configuring in the SDF using ODBC connectivity. To connect to multiple data sources using ODBC, you must either configure each data source individually in the SDF or dynamically enable all ODBC data source definitions. If you select this option, the lower half of the Connections window changes and displays parameters that are specific to the ODBC network connection. v Machine Data Source Name v File Data Source Name v Advanced Set User Information Click this button to specify your user ID and password for this connection to the database server. The Set User Information window opens. Test Click this button to establish a network connection with the database server. You must test the connection to any new database server that you are configuring in the SDF before you proceed to bind packages or set up governing.
Host Name This field is only displayed when Connect using DRDA over TCP/IP is selected. Use this field to specify the IP address of the server that houses the database. If you specify a TCP/IP domain name for the host name, DB2 Table Editor resolves that name to an IP address using the get host by name socket call. Alternatively, you can specify the host address in dotted decimal notation, for example 172.16.39.111. Port Number This field is only displayed when Connect using DRDA over TCP/IP is
Chapter 2. Getting Started with DB2 Table Editor Console component
83
selected. Use this field to specify the port number for the database server. The port number is the port that DB2 is assigned to listen for DRDA TCP/IP conversations. RDB Name This field is displayed when Connect using DRDA over TCP/IP or Connect using DRDA over SNA are selected. Use this field to specify the actual name of the relational database server that you are configuring in the SDF. The RDB name is not visible to DB2 Table Editor users. For DB2 z/OS, OS390, and MVS, you enter the location name. For DB2 Universal Database or DB2 Common Server technology, you enter the database name. For iSeries, you enter the name of the database that is found in the iSeries Relational Database Directory. ANSI client CCSID This field is displayed when Connect using DRDA over TCP/IP or Connect using DRDA over SNA are selected. Use this field to specify the code page to use with the ANSI version of DB2 Table Editor. The default code page is the EBCDIC equivalent value to the Windows CCSID. You can select a code page from the drop down list or type the code page name in the field. Unicode client CCSID This field is displayed when Connect using DRDA over TCP/IP or Connect using DRDA over SNA are selected. Use this field to specify the code page to use with the Unicode version of DB2 Table Editor. The default is the Windows code page. You can select another code page from the drop down list or type a code page name in the field. Enable Load balancing This field is displayed when Connect using DRDA over TCP/IP or Connect using DRDA over SNA are selected. Check this check box to enable load balancing for the DB2 database server you are configuring in the SDF. The DB2 database server must also support load balancing. Symbolic Destination Name This field is displayed when Connect using DRDA over SNA is selected. Use this field to specify the CPI-C or WINCPIC symbolic destination name that is defined in your SNA networking software. This name refers to a set of parameters, known as a CPI-C side information record, which is used when establishing a connection to a partner application, such as DB2, over the network. Database Alias This field is displayed when Connect using DB2 for Windows CLI is selected. Use this field to specify the name of the database server that is defined in your DB2 UDB client software. Machine Data Source Name This field is displayed when Connect using ODBC is selected. Use this field if the ODBC data source you are configuring in the SDF is defined to your local machines registry either as a user DSN or a system DSN. From the Machine data source name list, select the name of the ODBC data source from the list of available user and system DSNs. Note: ODBC user and system DSNs defined to your local machines registry are listed in the ODBC Data Source Console window. File Data Source Name This field is displayed when Connect using ODBC is selected. Click this
84
Users Guide
button if the ODBC data source you are configuring in the SDF is a file data source name. File data source names can reside on your local machine or another machine or server that is part of your network. Press the browse icon to find and select a file data source name. Advanced This button is available when Connect using ODBC or Connect Using DB2 for Windows CLI is selected. Click this button to specify driver-specific keywords and their values that are to be used when connecting to the database server using CLI connectivity or a data source using ODBC connectivity. The Advanced DSN Settings window opens. Back Click this button to close the current page of the Parameters notebook. The Back button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The previous page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. The Next button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The next page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded.
Next
OK
Cancel
Catalog Page
Use a catalog with the current server Check this check box to specify that a catalog must be used with the current server. Server Select the server where you want the catalog for the current sever to be stored. Catalog Lists the available catalogs. Highlight the catalog that you want to use at server that you selected from the Server list. Add Catalog button Click the Add Catalog button (on the right side of the Catalog table) to add a catalog to the table. Change Catalog button Click the Change Catalog button (on the right side of the Catalog table) to modify the selected catalog in theCatalog table. Delete Catalog button Click the Delete Catalog button (on the right side of the Catalog table) to delete a catalog from the table. Require the use of this catalog when accessing the current server Check this check box to indicate that the catalog that you selected from the Catalog table must be used with the current server.
85
Packages page
This page is only present when working with ODBC connectivity. Collection ID Use this field to specify the collection name that should be used to bind the DB2 Table Editor packages. In most instances, this name refers to the version of DB2 Table Editor that you are running on this server, for example, eti43fp7. In DB2, a collection is a group of packages that have the same qualifier or ID. These packages are bound with the ID and become part of the application plan. By identifying the application in the ID field, it makes it easier to spot packages that are related to a particular application. Period Select this button to specify that a period will be used as the decimal delimiter in the SQL statements that are run on this database server. Comma Select this button to specify that a comma will be used as the decimal delimiter in the SQL statements that are run on this database server. Apostrophe Select this button to specify that an apostrophe will be used as the string delimiter in the SQL statements that are run on this database server. Quote Select this button to specify that a quote will be used as the string delimiter in the SQL statements that are run on this database server. Wizard Click this button to open the Packages Wizard. You use the Packages Wizard, when working with DB2 Databases, to create DB2 Table Editor catalog objects, and bind the DB2 Table Editor packages. Back Click this button to close the current page of the Parameters notebook. The Back button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The previous page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. The Next button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The next page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded. Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Next
OK
Cancel
Procedures page
Owner Type the userID of the owner of the procedure in this field.
86
Users Guide
Wizard Click the Wizard button to launch the Procedures Wizard. You use the Procedures Wizard, when working with Informix databases, to create DB2 Table Editor catalog objects. Back Click this button to close the current page of the Parameters notebook. The Back button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The previous page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. The Next button is only available if you are configuring a new database server in the DB2 Table Editor SDF. The next page of the Parameters notebook opens. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded. Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Next
OK
Cancel
Delete Click this icon to remove the resource limits group selected in the Matching groups field. The resource limits group and all of its schedules are deleted from the database server. Assign Click this button to add or remove users to and from the resource limits group selected in the Matching groups field. The Assign User Profiles to a Group window opens.
Chapter 2. Getting Started with DB2 Table Editor Console component
87
OK
Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded.
Cancel
Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Delete Click this icon to remove the user profile selected in the Matching profiles field. The user profile is removed from the profile table RDBI.PROFILE_TABLE. OK Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded. Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Cancel
88
Users Guide
OK
Click this button to close the Sample Tables page of the Parameters notebook. Any changes that you have made to the server parameters are saved. Click this button to close the current page of the Parameters notebook. Any changes that you have made to the database servers configuration parameters are discarded.
Cancel
Apply Click this button to save any changes that you have made to the database servers parameters. The current page of the Parameters notebook stays open.
Network page
TCP Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using TCP/IP. Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using TCP/IP. CLI Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CLI. Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CLI. ODBC Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using ODBC.
89
Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using ODBC. CPI-C Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CPI-C services. Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CPI-C services.
Traces page
Trace file Use this field to enter the name of a file that DB2 Table Editor can use to write trace data. To search for a file click the Browse button. Browse Click this icon to select a file that DB2 Table Editor can use to write trace data. Components Check one or more Components from the check list for DB2 Table Editor to monitor and collect trace information. The following components may be traced: DDM Check this check box to gather trace information that pertains to Distributed Data Management Architecture (DDM). Select this option only if you use a DRDA connection. Check this check box to gather trace information that pertains to Transmission Control Protocol (TCP). Select this option only if you use a DRDA over TCP/IP connection.
TCP
CPI-C Check this check box to gather trace information that pertains to Common Programming Interface-Communications (CPI-C). Select this option only if you use a DRDA over SNA connection. CLI Check this check box to gather trace information that pertains to a Call Level Interface (CLI) connection. Select this option only if you use a CLI connection.
ODBC Check this check box to gather trace information that pertains to an Open Database Connectivity (ODBC) connection. Select this option only if you use an ODBC connection. Messages Check this check box to gather trace information that pertains to
90
Users Guide
DB2 Table Editor messages that are displayed to the user. This option is particularly useful when you are running DB2 Table Editor in unattended mode. Dynamic SQL Check this check box to gather trace information that pertains to the use of dynamic SQL. Embedded SQL Check this check box to gather trace information that pertains to the use of embedded SQL statements. Select this option only if you use CLI to access the data in a database management system. SQLAM Check this check box to gather trace information that pertains to the use of SQL Application Manager (SQLAM). Select this option for all connection types except ODBC. REXX Check this check box to gather trace information that pertains to the use of Restructured Extended Executor (REXX) programming language. Select this option only if you are tracing a procedure that uses IBM Object REXX in a procedure or a form. Internet Mail Check this check box to gather trace information that pertains to the use of SMTP. Select this option to gather trace information if you use the mail command or feature. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
Importing DB2 for Windows Databases window Fields and Controls Information
Databases Lists the databases that are defined in the local DB2 for Windows configuration. From theDatabases list, select the DB2 database that you want to import and configure in the DB2 Table Editor SDF. Import Click this button to import the DB2 for Windows database selected in the Databases list. The DB2 for Windows database server is added to the SDF with many of the required parameters already specified. The Parameters notebook opens. Using the Parameters notebook you can complete configuring this database server in the SDF. Cancel Closes the Import DB2 for Windows Databases window. Control returns to the DB2 Table Editor Console window without importing a DB2 database or updating the SDF.
91
New
Click this button to add a new database server to the current SDF. The General page of the Parameters notebook, opens where you begin the configuration process. To model a new database server on an existing database server, select the model database server in the Servers list. DB2 Table Editor uses the model database servers configuration parameters for the new database server. Using the Parameters notebook you can make changes to the new database servers configuration parameters. If you do not select a model database server, DB2 Table Editor will build a shell and you must supply all of the values for the database servers configuration parameters. Click this button to modify the configuration parameters of the database server that you selected in the Servers list. The Parameters notebook opens.
Edit
Delete Click this button to remove the database server that you selected in the Servers list and all of its parameters from the current SDF. Enable dynamic definition of ODBC servers Check this check box to dynamically configure in the SDF every local ODBC data source for each of your DB2 Table Editor users. If you do not use the Enable dynamic definition of ODBC servers option, you must individually configure in the SDF every local ODBC data source that each of your users needs to access. When this option is checked, every time DB2 Table Editor is run on a local machine using this SDF, DB2 Table Editor builds dynamic entries in the SDF for each local ODBC data source known to the local ODBC Data Source Manager. Each entry uses the configuration parameters of a model ODBC data server. Use the Propertiesbutton to specify the model ODBC database servers configuration parameters. Properties Click this button to specify the configuration parameters for the model ODBC data server. The Properties button is only available if you checked the Enable dynamic definitions of ODBC servers check box. TheParameters notebook opens where you can complete the the process of dynamically configuring ODBC data servers.
Concepts
Correct format for identifiers
Object owners and object names, including column names. The maximum length of table owners and table names depends on the version and platform of DB2. Normal characters include uppercase letters, digits, or the following characters: _, @, #, and $. You must enclose any special characters in quotes. If the identifier includes a quote character, you double each occurrence of the quote character and then enclose the entire identifier in quote characters. For example, you enter the identifier project as project. If you use lowercase letters and do not enclose the identifier in quotes, any lowercase letters are changed to uppercase.
Matching Patterns
When entering queries, forms and table names for searching, you can use the percent % and underscore _ characters to match patterns. Use the percent character % to match a string of any length containing any characters. For example, to list all items beginning with the letter A, you enter %A. To list all items, enter just the % character.
92
Users Guide
Use the underscore character _ to match a single character. For example, to list all items that have the letter A in the second position, enter _A%. If the pattern you enter contains special characters, you must enclose the entire pattern in quotation marks. For example, to include a space as part of a pattern, you enter A B%.
Special characters
Special characters include any characters other than: v A through Z (uppercase only) v 0 through 9 v #, $, @, and _
Wildcards
When typing query or form or table names for searching, you can use the percent % and underscore _ characters as wildcards. Use the percent character % to match a string of any length containing any characters. For example, to list all items beginning with the letter A, you enter A%. To list all items, enter just the % character. Use the underscore character _ to match a single character. For example, to list all items that have the letter A in the second position, enter _A%. If the pattern you enter contains special characters, you must enclose the entire pattern in quotation marks. For example, to include a space as part of a pattern, you enter A B%.
Chapter 2. Getting Started with DB2 Table Editor Console component
93
Schedule 1, because it has the lowest number, is always in effect. The numbering of these schedules as presented above does not make sense. As defined, schedule #3 will never be in effect because its time frame always falls within schedules #1, and schedule #1 will always take precedence. This is a major consideration when assigning numbers to the schedules. When you create a schedule, you as the administrator can choose to assign any number from 1 to 99 to that schedule. It is recommended that for the schedule with the most selective time constraints, you assign the lowest number, and for the schedule with the broadest time expanse, you assign the higher number. Following this logic, the more appropriate way of numbering the above schedules would be:
Schedule # From Day To Day From Time To Time 1 Wednesday Wednesday 10:30 11:30 2 Monday Friday 09:00 17:00 3 Monday Friday 17:00 00:00 4 Saturday Sunday 00:00 24:00
Now, on Wednesday at 10:30AM Schedule 1 is in effect. On Monday at 10:30 am, schedule 2 in effect, and on Sunday at 10:30 am schedule 4 is in effect. Additional considerations when creating schedules: Schedules do not have to be numbered sequentially. Once a schedule is assigned a number it cannot be changed, so it is recommended that you stagger your numbering so additional schedules can be inserted where appropriate or deleted without impact. All time and day ranges of the schedules are inclusive. That means if the From time is 08:00, the schedule is in effect exactly at 08:00:00. If the To time is 17:00, the schedule is in effect until 17:00:59.
94
Users Guide
The From and to times can wrap around midnight, and the From and To days can wrap around weeks. When users are accessing servers in different time zones, the clock used to determine time resides on the server being accessed. For example, an end user if New York is accessing a server in California and it is 9:00am Monday. Based on the examples schedules, schedule 3 is in e effect because according to the server it is 6:00 California time.
Extended catalogs
On each database server that is a DB2 Table Editor catalog server, the main DB2 Table Editor catalog is called Default. All DB2 Table Editor objects and user objects from the DB2 Table Editor catalog server are stored in the main DB2 Table Editor catalog Default. All user objects from a database server that is sharing the catalog are also, by default, stored in the main catalog on the DB2 Table Editor catalog server. You can isolate the objects from a database server that is sharing a DB2 Table Editor catalog by creating an extended catalog. The extended catalog will contain only those objects from a specific database server. You can also specify that multiple database servers can share extended catalogs. That means, an extended catalog can contain objects from several database servers. The ability to have multiple extended catalogs residing on different database servers can effect performance, users views of objects and overall maintenance of your query environment.
Authorization IDs
Write a concept about how to populate a table with authorizations IDs that are external to DB2 Table Editor. DB2 Table Editor only knows about the logon user ID and an authorization ID that the user can define via the SQLID.
95
SNA network environment. It is important that you have the latest corrective service or maintenance for your SNA product as there are known problems with several SNA products. The number of Windows-based SNA products and the different ways they can used are numerous and complex. Rely on your in-house SNA networking staff and your SNA software vendors technical support services to implement and support your network configuration.
96
Users Guide
ODBC Data Sources DB2 Table Editor references ODBC data sources by their Data Set Name (DSN). Most data sources can be accessed by DB2 Table Editor as long as the particular ODBC data source drivers are available. A user ID and password are required to make the connection if it is required by the ODBC data source. The following data sources have been tested using an ODBC connection: v Informix ODBC Drivers Tested for Use with DB2 Table Editor The following ODBC driver has been tested for use with DB2 Table Editor: v INFORMIX Driver 3.81.00.11267 ODBC Support in DB2 Table Editor When connecting to data sources using ODBC the following DB2 Table Editor supportfeatures should be considered: v Support for most ODBC standard object types including long, variable length binary and character values up to 32,700 bytes. Support excludes interval data types. v Support for stored procedures is limited depending on data source, data types and input parameters. v ODBC bookmarks are not supported. v Data within ODBC data sources can only be updated through direct SQL statements, provided that both the data source and the ODBC driver permit update operations. v When a catalog is not used with ODBC connectivity, features of DB2 Table Editor that require the use of the catalog are not available. A Shared DB2 Table Editor Catalog All database servers that are configured in the SDF require the use of a DB2 Table Editor catalog except ODBC servers. When you are configuring ODBC database servers, you can choose whether a catalog will be used. You can configure an ODBC database server so that it does not require a catalog. Some features of DB2 Table Editor are not available to users when ODBC database servers do not have access to a catalog. If you configure an ODBC database server so that it will use a catalog, you must choose a catalog that resides on a DB2 database server that is connected to using TCP/IP, SNA or CLI. ODBC database servers cannot host their own catalogs.
97
v RAARDBX5: Package includes the dynamic user SQL run with NC isolation level. End users require EXECUTE authority to run the package. v RAARDBI1: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. v RAARDBI2: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARDBIA: Package includes internal SQL for DB2 Table Editor administrative functions. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARDBIL: Package includes internal SQL for retrieving LOB values. End users require EXECUTE authority to run the package. v RAASHUT1: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARC1: Package includes internal SQL for Report Center. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog. The following packages are bound for servers with CLI connectivity: v RAARDBC1: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. v RAARDBC2: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARDBCA: Package includes internal SQL for DB2 Table Editor administrative functions. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARDBCL: Package includes internal SQL for retrieving LOB values. End users require EXECUTE authority to run the package. v RAASHTC1: Package includes internal SQL for DB2 Table Editor. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog. v RAARC1C: Package includes internal SQL for Report Center. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a DB2 Table Editor catalog.
Retrieving Data
When retrieving large amounts of data, the factor that typically limits performance is communication over the network. Because of this, DB2 Table Editor keeps the delay between requests to the database server as short as possible, in order to maximize performance. In particular, when DB2 Table Editor receives a buffer of data from the database server, it immediately requests more data, then, while waiting for the new data, it processes the data that has already been received. Whenever DB2 Table Editor requests more data, it first checks how many rows have already been retrieved, and compares this against the row limit in effect. If the row limit has been exceeded, it does not issue any more requests. As described above, though, when it performs this check, it has not yet processed all of the data that has been received in order to see how many rows it contains. That is, an accurate count of how many rows of data have been received is not available when the decision whether or not to retrieve more data is made. As a result, DB2 Table Editor can fetch a large amount of data before determining that the row limit has been
98
Users Guide
exceeded, much more data than the row limit specifies. This problem does not occur with byte limits. The number of bytes of data that have been received is always available, even without actually processing the data. Therefore, in contrast to row limits, the evaluation of byte limits by DB2 Table Editor is always accurate (subject to the buffering discussion above). it is recommended that byte limits be used instead of row limits to effectively control the amount of data fetched.
99
If the query block size is set to a large value, the response time for receiving each block of data is longer. However, the amount of time required to retrieve all of the data is smaller, because a smaller total number of blocks must be transmitted. The smallest allowable query block size is 512. The largest allowable query block size is 32767. If you do not specify a query block size, the default 32,500 is used as the default. For example: to set the query block size for a server named Server1 to 16384, find the section that is labeled Server1 in the SDF: Server1 Replace or add a line as follows: QueryBlockSize=16384
100
Users Guide
Chapter 3. Getting started with the DB2 Table Editor Developer component
DB2 Table Editor Developer is a development environment in which you can build table editing applications. Using DB2 Table Editor Developers drag-and-drop interface, you can build forms that provide a simple, graphical interface to IBMs DB2 database, without programming. The forms you design with DB2 Table Editor Developer allow your users to access, search and edit data. Although DB2 Table Editor Developer is designed to interact with DB2 and Informix, you can also use IBMs DB2 DataJoiner to connect your forms to virtually any other database application. The forms that you create using DB2 Table Editor Developer are platform-independent. When you build a form, DB2 Table Editor Developer automatically translates your work into XML. This means that your form will work with both the Windows and Java versions (components) of the DB2 Table Editor User application. Moreover, you can use applet tags to place any form directly onto a web page, such as a corporate intranet site, granting platform-independent access to many users from one location. Using DB2 Table Editor Developer, you can build custom table-editing applications that provide users a simple, form-based interface to DB2 database tables and Informix tables. DB2 Table Editor Developer helps you create forms that perform query-by-example table editing and many other tasks. Your forms can join tables, include validation rules, run SQL (including DB2-specific SQL), and access multiple DB2 platforms. With DB2 Table Editor Developers intuitive, drag-and-drop development environment, you can build custom forms quickly, without programming. You can store your forms centrally on a DB2 server, for easy modification and distribution. Users can access forms over standard internet, intranet, or LAN connections. Before working with DB2 Table Editor Developer, you must define and configure the database servers to which you want to connect using DB2 Table Editor Console.
File Menu
New Creates a new form document. Form Wizard Creates a new form document using the form wizard. Open Opens an existing form document.
Open From Server Opens an existing form from the database server.
101
Close Closes the active form. Import from DBEDIT Imports a panel from the mainframe application DBEDIT. Save Save the active form with the current file name, location, and file format. save the active form with the current file name, location, and file format.
Save As Saves the active form with a different file name, location, and/or file format. Save At Server Saves the active form at the database server. Print Prints the current form.
Print Preview Displays a preview of the printed form. Print Setup Opens the Print Setup dialog box. File List Reopens one of the last four documents that were open. Click the number or name of the document you want to open. Exit Closes the application. Related reference Edit Menu View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107 Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
Edit Menu
Undo Redo Cut Copy Reverses certain commands or delete the last entry you typed. Repeats commands you have previously undone. Removes the selected item from the active document and place it on the Clipboard, replacing the current contents of the Clipboard. Copies the selected item and place it on the Clipboard, replacing the current contents of the Clipboard.
Paste Inserts the contents of the Clipboard at the insertion point, replacing any selection. Delete Deletes the selection without saving the contents to the Clipboard. Select All Selects all the controls in the active form. Related reference
102
Users Guide
File Menu on page 101 View Menu Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107 Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
View Menu
Zoom In increase the magnification of the current form. Zoom Out Decreases the magnification of the current form. Zoom 1:1 Displays the form in its default size. Toolbars Standard Displays or hides the standard toolbar. Toolbars Format Bar Displays or hides the format toolbar. Toolbars Layout Bar Displays or hides the layout toolbar. Toolbars Object Bar Displays or hides the object toolbar. Status Bar Displays or hides the status bar. Ruler Displays or hides the ruler.
Snap Points Displays or hides the snap points on the controls. Snap points are used by the connector control to draw lines connecting two controls. Set Current SQLID Sets the current SQLID using the Set Current SQLID dialog box. Options Displays the Options dialog box where you can set options for DB2 Table Editor. Related reference File Menu on page 101 Edit Menu on page 102 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107
Chapter 3. Getting started with the DB2 Table Editor Developer component
103
Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
Form Menu
Set Server Selects the database server for the active form. Set User Information Sets your database server user ID, password, and accounting string for the active form. Attributes Displays the attributes of the selected control. Properties Displays the properties of the selected control. Validation Rules Displays the validation rules in effect for a form. Bind Package Creates a package at the database server that binds the dynamic SQL statements for the current form as static SQL. Revert to Dynamic SQL Specifies that, after binding packages for the current form, it will revert the static SQL statements to dynamic SQL so form attributes can be edited. Size to Contents Resizes the form to fit the controls contained within it. Generate HTML Generates HTML an applet tags to display the form in a browser. Run Opens the selected form in the DB2 Table Editor User application. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Layout Menu Window Menu on page 106 Help Menu on page 107 Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
Layout Menu
Order Bring to Front Brings the selected control to the front of all controls in the form.
104
Users Guide
Order Send to Back Sends the selected control to the back of all controls in the form. Group Joins the selected controls together as a group. Ungroup Breaks the selected group of controls into individual controls. Regroup Regroups a previously ungrouped group of controls. Align Objects Left Aligns the selected controls, outlined in blue, to the left most edge of the first selected control, outlined in green. Align Objects Right Aligns the selected controls, outlined in blue, to the right most edge of the first selected control, outlined in green. Align Objects Top Aligns the selected controls, outlined in blue, to the top edge of the first selected control, outlined in green. Align Objects Bottom Aligns the selected controls, outlined in blue, to the bottom edge of the first selected control, outlined in green. Align Objects Vert. Center Aligns the selected controls, outlined in blue, vertically to the center of the first selected control, outlined in green. Align Objects Horz. Center Aligns the selected controls, outlined in blue, horizontally to the center of the first selected control, outlined in green. Space Evenly Across Evenly spaces the selected controls horizontally. Space Evenly Down Evenly spaces the selected controls vertically. Center in View Vertical Centers the selected controls vertically within the form. Center in View Horizontal Centers the selected controls horizontally within the form. Make Same Size Width Resizes the selected controls, outlined in blue, to the width of the first selected control, outlined in green. Make Same Size Height Resizes the selected controls, outlined in blue, to the height of the first selected control, outlined in green. Make Same Size Both Resizes the selected controls, outlined in blue, to the width and height of the first selected control, outlined in green. Grid Settings Displays the Grid Settings dialog box. Check Mnemonics Checks for duplicate accelerator keys.
Chapter 3. Getting started with the DB2 Table Editor Developer component
105
Tab Order Displays the Tab Order dialog box. Preview Displays a preview of the form as it will appear when run in the DB2 Table Editor User application. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Window Menu Help Menu on page 107 Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
Window Menu
Cascade Displays all open windows in a cascading, overlapped fashion. Tile Horizontally Arranges windows horizontally as non-overlapping tiles. Tile Vertically Arranges windows vertically as non-overlapping tiles. Arrange Icons Arranges the icons for minimized windows at the bottom of the main window. Icons may not be visible if they are arranged underneath an open window. Window List Displays a list of all the open document windows. A check mark appears in front of the name of the active window. Click the name of the window that you want to make active. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Help Menu on page 107 Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
106
Users Guide
Help Menu
Help Topics Displays the Contents screen for DB2 Table Editor Developer online help. About DB2 Table Editor Developer Displays the version number of this DB2 Table Editor software, and copyright and trademark information. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Control Shortcut Menu Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
Paste Inserts the contents of the Clipboard at the insertion point, replacing any selection. Delete Deletes the selected control from the form. Order Bring to Front Brings the selected control to the front of all controls in the form. Order Send to Back Sends the selected control to the back of all controls in the form. Group Joins the selected controls together as a group. Ungroup Breaks the selected group of controls into individual controls. Regroup Regroups a previously ungrouped group of controls. Align Objects Left Aligns the selected controls, outlined in blue, to the left most edge of the first selected control, outlined in green. Align Objects Right Aligns the selected controls, outlined in blue, to the right most edge of the first selected control, outlined in green. Align Objects Top Aligns the selected controls, outlined in blue, to the top edge of the first selected control, outlined in green.
Chapter 3. Getting started with the DB2 Table Editor Developer component
107
Align Objects Bottom Aligns the selected controls, outlined in blue, to the bottom edge of the first selected control, outlined in green. Align Objects Vert. Center Aligns the selected controls, outlined in blue, vertically to the center of the first selected control, outlined in green. Align Objects Horz. Center Aligns the selected controls, outlined in blue, horizontally to the center of the first selected control, outlined in green. Space Evenly Across Evenly spaces the selected controls horizontally. Space Evenly Down Evenly spaces the selected controls vertically. Center in View Vertical Centers the selected controls vertically within the form. Center in View Horizontal Centers the selected controls horizontally within the form. Make Same Size Width Resizes the selected controls, outlined in blue, to the width of the first selected control, outlined in green. Make Same Size Height Resizes the selected controls, outlined in blue, to the width of the first selected control, outlined in green. Make Same Size Both Resizes the selected controls, outlined in blue, to the width and height of the first selected control, outlined in green. Attributes Displays the attributes of the selected control. Properties Displays the properties of the selected control. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107 Form Shortcut Menu DB2 Table Editor Toolbars on page 109 DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
108
Users Guide
Zoom In Increases the magnification of the current form. Zoom Out Decreases the magnification of the current form. Zoom 1:1 Displays the form in its default size. Ruler Displays or hide the ruler.
Check Mnemonics Checks for duplicate accelerator keys. Tab Order Displays the Tab Order dialog box. Attributes Displays the attributes of the selected control. Properties Displays the properties of the selected control. Preview Displays a preview of the form. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107 Control Shortcut Menu on page 107 DB2 Table Editor Toolbars DB2 Table Editor Object Toolbar on page 110 DB2 Table Editor Status Bar on page 111
109
Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Object Toolbar DB2 Table Editor Status Bar on page 111
Freehand Places a freehand control on a form. Border Places a border control on a form. Ellipse Places an ellipse control on a form. Frame Places a frame control on a form. Hilite Places a hilite control on a form. Related reference File Menu on page 101 Edit Menu on page 102 View Menu on page 103 Form Menu on page 104 Layout Menu on page 104 Window Menu on page 106 Help Menu on page 107
110
Users Guide
Control Shortcut Menu on page 107 Form Shortcut Menu on page 108 DB2 Table Editor Toolbars on page 109 DB2 Table Editor Status Bar
Chapter 3. Getting started with the DB2 Table Editor Developer component
111
/IPassword:password The /IPassword parameter defines the password of the user specified with the /IUserID parameter. The /IPassword parameter includes the users password in plain text.
112
Users Guide
3. From the Tables window, in the Owner field, type the owner of the table that you want the form to use. This field is case sensitive. Use the % character as a wildcard character. 4. In the Name field, type the name of the table that you want the form to use. This field is case sensitive. Use the % character as a wildcard character. 5. Optional: If you are accessing a z/OS system, you can specify the database, tablespace, and type of the table. 6. Click Search. A list of tables matching those criteria is returned in the lower portion of the Tables dialog box. Note: You can choose from a list of tables stored at a database server. In the Tables dialog box, type the special command character % in the Owner and Name fields (and in the Type Database Name, and Table Space Name field, which are available if you are accessing a z/OS or OS/390 system), and click Search. A list of all tables on the server is returned. You can also specify an owner, to list only that owners tables. 7. From the list in the Tables window, select the table that you want the form to access, and click Next. The Columns dialog box opens, displaying a list of all of the columns in the table. When creating a form you specify the primary table that the form will be used to access and modify. A primary table is the table that is designated by the form developer as the updateable table. For each form there is only one primary table, but there can be a number of secondary tables, which are usually related to the primary table by join conditions. Insert, Update and Delete buttons on a form operate only on the primary table and perform the appropriate database modifications for the action (insert, update and delete) using the current form values for all controls that are bound to a primary table column. 8. Ensure that all of the columns that you want to use on your form are checked. 9. Click Next. The Actions dialog box opens, displaying a list of actions that the form can run. These actions are represented on the form as buttons. 10. Ensure that the actions that you want the form that you are creating to use, are checked, and click Finish. The new form opens in the main window. You can now save or run the file. Related concepts Creating new forms on page 112 Related tasks Creating a new form by importing a panel from DBEDIT Creating a form manually on page 114
Chapter 3. Getting started with the DB2 Table Editor Developer component
113
6. Click OK. the Import Panel from DBEDIT window closes and DB2 Table Editor Developer imports and opens the DBEDIT panel that you have imported. Related concepts Creating new forms on page 112 Related tasks Creating a new form using the Forms wizard on page 112 Creating a form manually
114
Users Guide
1) Click the Join Conditions tab. The Join Conditions page opens. 2) Click Add. The Join window opens. 3) From the two table drop-down lists, select the tables you want to join. 4) From the columns lists, select the column from each table on which you want perform the join. Note: You must choose columns with matching data types. Join columns with matching data. For example, join columns that both contain Last_Name or Product_ID_Number data. 5) Click OK. The Join window closes. Click the Sort Conditions tab. The Sort Conditions page opens. Set the sort conditions for your form: a. Click Add. The Sort window opens. b. Select each column that you want to sort, and click the Ascending radio button or the Descending radio button to specify whether the data will be sorted in ascending or descending order. c. When you have specified all of the necessary sort conditions, click Close. The Sort window closes and your form displays the data in the order that you specified. Select the General tab. The General page opens. Set the General form attributes: a. Specify an initial action. You can specify an initial action for a form. An initial action is an automatic event that occurs each time the form is opened. An example would be to automatically display Help when the form is opened. To specify an initial action: 1) Check the Initial Action check box, and click Actions. The Attributes window opens. 2) From the Attributes window, select an initial action, and click OK. The initial action is set. When the form is opened by the user, it will automatically run the specified action. The Form Attributes dialog box closes. b. Specify an initial focus. You can specify an initial cursor focus for a form. When the user first opens the form, the control with initial focus is the active control. To specify an initial focus: 1) From the Control with initial focus list, select the control that you want to have the initial focus. 2) Click OK. The Form Attributes dialog box closes. When opened by the user, the form will automatically set the cursor focus to the specified control. c. Specify a commit scope. The commit scope is the number of actions that must take place before a unit of work is completed and the data is committed to the DB2 database. To specify the commit scope, In the Commit scope field, type the maximum number of rows to insert before committing changes to the database.
9. 10.
11. 12.
Note: If this value is omitted or zero, all of the rows are inserted before a commit occurs. Otherwise, this value specifies the maximum number of rows to insert before committing changes to the database. All SAVE actions are subject to the commit scope. 13. Click OK. The Form Attributes window closes. 14. Save the form by selecting File --> Save.
Chapter 3. Getting started with the DB2 Table Editor Developer component
115
Related concepts Creating new forms on page 112 Related tasks Creating a new form using the Forms wizard on page 112 Creating a new form by importing a panel from DBEDIT on page 113
116
Users Guide
Note: The connector control is only available if snap points are displayed on the form. To display the snap points on a form, select snap points from the View menu. Edit Box You can use the edit box control to create one-line, editable text boxes. Edit boxes cannot exceed one line of text, or 32,000 characters. Ellipse You can use the ellipse control to place an ellipse on the form. Ellipses have no DB2 Table Editor attributes and have no effect on the function on the form. Ellipses are used only to enhance the appearance of the form. Frame You can use the frame control to place a frame on the form. You can also add descriptive text to the frame border. Frames have no DB2 Table Editor attributes and have no effect on the function on the form. Frames are used only to enhance the appearance of the form. Freehand You can use the freehand control to draw freehand lines on the form. Freehand lines have no DB2 Table Editor attributes and have no effect on the function on the form. Freehand lines are used only to enhance the appearance of the form. Hilite You can use the hilite control to place areas of highlighted color on the form. Hilite areas have no DB2 Table Editor attributes and have no effect on the function on the form. Hilite areas are used only to enhance the appearance of the form.
Image You can use the image control to display a picture on the form. Images have no DB2 Table Editor attributes and have no effect on the function on the form. Images are used only to enhance the appearance of the form. The following formats are supported by the image control: v *.jpg v *.bmp v *.dib v *.ico Label You can use label controls to place descriptive text on the form. The text has no DB2 Table Editor attributes and has no effect on the function on the form. Labels are used only to enhance the appearance of the form. Line You can use the line control to draw lines on the form. Lines have no DB2 Table Editor attributes and have no effect on the function on the form. Lines are used only to enhance the appearance of the form.
List Box You can use the list box control to create one-column, editable lists. These lists can be populated by user-defined values, or populated with values from a table. List You can use the list control to create multiple-column, editable lists. Use an SQL SELECT or CALL statement in the Source attribute of the list control to display multiple columns. The list control displays columns of data in a tabular format. The list control can be populated by user-defined values, or populated with values from a table. Use the LOB control icon to create a LOB control. LOB controls can be used to display graphic, multimedia and text LOB data. You set the properties for your LOB control using the LOB Control Properties window.
Chapter 3. Getting started with the DB2 Table Editor Developer component
LOB
117
Multi Edit Box You can use the multi edit box control to create multiple-line, editable text boxes. The multi edit box contains a string of text or numbers displayed on multiple lines, not a list of data. Multi edit boxes cannot contain more than 32,000 characters. Select The select control lets you select, move, and edit other controls. It has no attributes or properties of its own. Spinner You can use the spinner control to change values in the control associated to it, such as an edit box. Use the spinner controls EditBuddy property to associate it to another control. The control being changed by the spinner control must immediately precede the spinner control in the tab order. Note: The spinner control works only with numeric values. Related concepts Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. DB2 Table Editor form control attributes DB2 Table Editor form control properties on page 125 Using special command characters on page 135 Related tasks Adding a control to a form on page 132 Deleting a control from a form on page 132 Setting control properties on page 133 Creating a LOB control on a form on page 133 Once you have created a LOB control on a form, use the LOB Control Attributes window to set the attributes for your LOB control. You can create LOB controls that display or play text, image or multimedia LOB data. Adding a Jpeg image to a form on page 134 Adding an accelerator key to a button control on page 135 DB2 Table Editor form control attributes: General Attributes Use general attributes to specify the control name, default value, and whether control contents should be ignored when a specified event occurs. General attributes include these options: Object Specify the name of the control. Default value Specify the default value, if any, for the control. Ignore on SELECT Check this option to ignore the contents of the control when running queries using the SQL statement SELECT. Ignore on UPDATE (Where) Check this option to ignore the contents of the control while processing the WHERE component of an SQL UPDATE statement.
118
Users Guide
Ignore on UPDATE (Set) Check this option to ignore the contents of the control while processing the SET component of an SQL UPDATE statement. Allow Edit Contents Check this option to allow the user to edit the contents of a list control. Users can edit all other controls by default. Column Attribute Use the column attribute to choose the column of data you want to bind to a control. The column attribute tab displays a list of each column in the table or tables associated with a form. Click on a column to bind it to a control. The column attribute determines which table and column the selected control will search, update, or delete, it also called the bound column. This can be different from the table and column the selected control will display, also called the source column. You can specify the source column in the source attribute of a list, list box, or combo box control. Format Attributes Use format attributes to determine how the contents of a control are displayed. Some format attributes only affect numeric data types; others affect only character data. There are also unique format attributes for list controls. Character Data Types Format attributes for character data types include. Display contents using hexadecimal format Use this option to display the contents of the control as a series of hexadecimal characters. Display hexadecimal characters in lower case Use this option to display the hexadecimal contents of the control in lower case characters. Numeric Data Types Format attributes for numeric data types include: Negative number format Select a format for representing negative numbers from the drop-down list. Decimal places Select the number of decimal places to display. Thousands separator Check this option to display number values with a comma as a thousands separator. Percentage Check this option to display number values as a percentage. Scientific Check this option to display number values in scientific notation. Currency Check this option to display number values as currency.
Chapter 3. Getting started with the DB2 Table Editor Developer component
119
Symbol Use this in conjunction with the currency option to specify the currency symbol used with currency values. Position Use this in conjunction with the currency option to specify the position of the currency symbol used with currency values. List Controls Format attributes for all controls containing numeric data, including list boxes, are described above. Format attributes for list boxes also include the following unique options. Select the column for which you want to adjust the formatting, and click Change. Header Specify the header name for each column displayed in the control. Width Specify the width of each column displayed in the list control. Alignment Select an alignment for the data within each column from the drop-down list. Locked Position Check the Locked Position check box to lock the column in position. When a column is locked in position, the locked column will not move when you scroll through the grid in your list control. You cannot have a locked column that has an unlocked column to the left of it. If you want to lock more than one column, start locking the columns with the left most column. Replace values Attribute Use the replace values attribute to replace the contents of a control with new values, upon user action. To set the replace values attribute, click Add and set these options: On action Choose the user action that will prompt the control values to be replaced. Make sure the form includes a way for the user to perform the action you choose. Replace contents with Choose the source of the values you want to display upon replacement. Enter a literal, select statement or special register Enter the values you want to display upon replacement. Enter literal values, an SQL SELECT statement, or a special register such as current time or current date. The special registers available to you depend on the database platform you are using. Refer to your DB2 documentation to find out which special registers you can use. Refresh Frequency Attribute Use the refresh frequency attribute to specify when to automatically refresh the contents of a control. The refresh frequency attribute includes these options: Once (fill when the form is opened) Use this option to fill the control when the user opens the form.
120
Users Guide
On Search for matching rows (refresh every time a search is started) Use this option to refresh the control whenever the user starts a search. On Retrieve the next row (refresh every time a row is fetched) Use this option to refresh the control whenever the user retrieves a row. On Selection change (refresh when the selected value of controls change) Use this option to automatically refresh the control when the contents of one or more associated controls change. To choose one or more associated controls, click List, then select one or more controls from the list. When the user changes the contents of an associated control, the control set to refresh on selection change is automatically updated. Name Attributes Use name attributes to specify the name and caption of a button control. Name attributes include these options: Object Specify the name of the button control. Caption Specify the caption you want to appear on the button. Button Action Attribute Use the button action attribute to specify the action to perform when the user clicks the button. The button action attribute includes these options: Clear all displayed values Clears all displayed values on the form. For controls that contain lists, this will remove the current selection. This does not close any open result sets, commit or rollback data or terminate database connections. Close the form Closes the form. This action closes any open result sets and commits pending database modifications but does not close the database connection. Commit pending transactions Commits pending transactions for the form. Selecting Commit pending transactions overrides the Commit Scope setting. Delete the current row from the table Deletes the current row from the table. This action deletes the current row from the primary table only. If any rules have been specified for the delete action, then they are evaluated before doing the delete. If a rule criteria is not met then a message is displayed and the delete is not completed. If the Confirm on Delete option is checked, then a message box will appear asking you to confirm the delete. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Display help Displays DB2 Table Editor online help. Execute command Executes the specified command, including Refer-Back conditions. If this is run using the Java Player component as an applet, then the command is run by passing the command to the browser. If this is run using the
Chapter 3. Getting started with the DB2 Table Editor Developer component
121
Windows user application, or the Java player running as an application, then the command is sent to the operating system to be executed. Exit the application Closes the application. This action closes any open result sets, commits pending database modifications, closes all open database connections and exits DB2 Table Editor. Insert a row into the table Inserts a row into the primary table. This action takes the current values for all controls that are bound to the primary table in the form and inserts a row into the primary table for the form. If a replacement value has been specified for a control then it is used instead of the current control value. If the Enter default values as value has been specified, then the column is not included in the insert and DB2 supplies the default value. If Enter null values as value has been specified, then a null value is used for the bound column. If any rules have been specified for the insert action, they are evaluated before doing the insert. If a rule criteria is not met then a message is displayed and the insert is not completed. If the Confirm on Insert option is checked, then a message box will be produced for the user to confirm the insert. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Launch control Launches the application that is associated with the contents of the specified control. For example, you can use this button action to launch an MP3 file displayed in a control. Select Launch control from the list, then select the desired control. If this form is run using the Java Player component as an applet, then the control is launched by passing the current value of the control to the browser. Multiple Actions The Multiple actions button action allows you to specify more than one action for a button. When the button is clicked, the button actions will be run in the order that they are listed in the Multiple Actions dialog box. This functionality is only available in forms that are accessed using the Windows User interface. Open form Opens another form. When you create the button, you specify the form that you want the button to open. If the form that is being opened has linked controls then the current values of the linked controls on the current form are used to populate linked controls on the form that is being opened, and a search is performed. If the specified form is already opened, it is reused. If the Close master form after opening linked form option was specified, then the master form is closed. If the Refresh form contents whenever the values for the linked controls change option was specified then the child form is synchronized with the values from the master forms linked controls. Refresh the selected controls Refreshes the contents of any selected controls. To use this control, select Refresh the selected controls from the list, then select one or more controls. This action will refresh the contents of any selected controls when clicked. Retrieve the next row Retrieves the next row in the table. If there are no more rows in the current result set, the current form values are cleared and a message is displayed
122
Users Guide
indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Retrieve the previous row Retrieves the previous row in the table. If you are at the beginning of the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Revert to the original values of this row Reverts to the original values of this row. This action sets the form control values to the original database values. This action does not close any open result sets, commit pending database modifications or close open database connections. Run an SQL Statement Runs the specified SQL statement, including Refer-Back conditions. This can be an SQL statement to update, insert or delete data from tables that are not the primary table. Stored procedures are also supported. After an SQL statement is successfully run, a message box is displayed (if this option has been set for the action), allowing the you to confirm or cancel the actions of the SQL statement. If cancel is chosen then a rollback is performed, otherwise a commit is issued. Search for matching rows Searches the table for matching rows. This action uses the current values for all bound controls to create a select statement. It will look for special character commands in all bound controls and uses them in building the search (for more information, see Using Special Command Characters in a Control). The first row that is returned is displayed in the form. A message will appear if no search results are returned. If sort conditions have been used, then the results are returned in that order. If there was already a result set opened, it is closed before performing the new search, however, any pending database modifications are not committed. If a replace value has been specified for a control, it is used instead of the current control value. If the Ignore on select option has been set for a control then the selected column is not included in the search. If the Enter null values as option is used then a null value is used for the bound column. If any rules have been specified for the search action, they are evaluated before doing the select. If a rule criteria is not met then a message is displayed and the search is not completed. If there are any LOB columns bound to controls, they are not automatically retrieved by the search. Update the current row in the table Updates the current row in the table. This action updates the primary table values for the current row. It includes only values that have been changed in the update. If a replace value has been specified for a control then it is used instead of the current control value. There is special handling for updates of primary key values (any foreign keys in associated tables are automatically changed in order to retain the correct relationships to the primary key). If possible, the update is done by using a positioned update (current position of the cursor). If this is not possible, then a searched update is done using the current values for all controls that are bound to the primary table in the form. If the Enter null values as option was specified, then a null value is used for the bound column. If any rules have been specified for the update action, then they are evaluated before doing the update. If a rule criteria is not met, then a message is displayed and the
Chapter 3. Getting started with the DB2 Table Editor Developer component
123
update is not done. If the Confirm on Update option is checked, then a message box will be produced for the user to confirm the update. If the number of pending database modifications exceeds the commit scope (defaults to 1) then a commit is issued. Source Attribute Use the source attribute to specify the column or columns you want to display in a list, list box, or combo box control. The source attribute determines which column the selected control displays, also called the source column. The column attribute determines which table and column the selected control will search, update and delete, also called the bound column. You can specify the source column to be the same as the bound column by choosing Existing Values on the source attribute tab on the Control Attributes window. You can specify the source column to be different from the bound column by choosing Select Statement on the source attribute tab on the Control Attributes window, and specifying the desired table and column to display. The source attribute includes these options: Get values from... Choose the source column for the control: Existing Values Choose this option from the drop-down list to display the column you specified on the Column attribute tab. You use Existing Values to specify that the source column is the same as the bound column for this control. Explicit List Choose this option from the drop-down list to display the specific values you enter. Select Statement Choose this option from the drop-down list to display the column or columns specified in an SQL SELECT statement, or enter a CALL statement to generate the column or columns that are specified in a stored procedure. You can use an SQL statement to specify a source column that is different from the bound column for this control. You can also use an SQL SELECT or CALL statement to display multiple columns in a list control. For a list box or combo box control, the first column specified in the SQL statement is used to populate a control. For example, in the SQL SELECT statement:
SELECT name, address FROM dbe.staff
the name column is used to populate a list box or combo box control. For a list control, that can display multiple columns, both the name and the address columns are used to populate the control. Link Column If you use an SQL SELECT statement to specify a source column different from the bound column for a control, you must create a link between the two. Choose a source column, specified in the SELECT statement, which contains values matching those in the bound column for the control. Related concepts
124
Users Guide
Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. DB2 Table Editor Form Controls on page 116 DB2 Table Editor form control properties DB2 Table Editor form control properties: Properties in the DB2 Table Editor Developer component define the appearance of controls. The developer uses control properties to define the physical characteristics of controls. Accelerator Use the accelerator property to set the accelerator key for a control. You can choose a letter, number or symbol from the drop-down list. Alignment Use the alignment control to specify whether the controls contents align left, center, or right. AllowEditTable Use the AllowEditTable property to specify whether or not a user can edit the values displayed in a list control. AnchorSnaps Use the AnchorSnaps property to specify the number and position of anchor snap points on a control. Arrowhead Use the Arrowhead property to add one or more arrow heads to a line or freehand control. You can add arrowheads to either end of a line, or to both ends. ArrowheadHeight Use the ArrowheadHeight property to specify the height of the arrowhead. AsURL Use the AsURL property to specify whether an image will be embedded in a form or appear as a link on the form. v Set the AsURL property to true to link to the image on your form. v Set the AsURL property to false to have the image embedded on your form. BackColor Use the BackColor property to specify the background color of a control. Bitmap Use the Bitmap property to add a bitmap or jpeg image to the form body or to a button control. BorderColor Use the BorderColor property to specify the color of a frame control border. BorderDrawn Use the BorderDrawn property to specify whether or not to display a border around a control. BorderStyle Use the BorderStyle property to determine the appearance of a frame control border. The BorderStyle property includes these options: Normal Display a single black line border.
Chapter 3. Getting started with the DB2 Table Editor Developer component
125
3D
Sunken Sunken BorderWidth Use the BorderWidth property to specify the width in pixels of a frame control border. Bottom Use the Bottom property to specify the location in pixels of the bottom edge of a control, relative to the dimensions of the form. ButtonShape Use the ButtonShape property to specify the shape of a button control. The ButtonShape Property includes these options: Normal Display a 3-dimensional button. Property Tab (Inactive) Display an unselected, 3-dimensional tab. Property Tab (Active) Display a selected, 3-dimensional tab. CaseOrPassword Use the CaseOrPassword property to control the format of the contents of a control. The CaseOrPassword property includes these options: None Display the contents of a control as they are returned from the database.
Lower Case Display the contents of a control in lower case text. Upper Case Display the contents of a control in upper case text. Password Display the contents of a control as asterisks. ComboType Use the ComboType property to specify the style of combo box you want to use. In DB2 Table Editor Developer, only the drop-down style combo box is available. CursorPointer Use the CursorPointer property to specify the shape of the pointer when it is moved over a control. The CursorPointer property includes these options: Default Display an I-Beam when the cursor is over a control. Arrow Display a standard arrow when the cursor is over a control. IBeam Display an I-Beam when the cursor is over a control. Cross Display a cross when the cursor is over a control. UpArrow Display an up-arrow when the cursor is over a control. NoDrop Display a no-drop symbol when the cursor is over a control.
126
Users Guide
Help
HotSpot Display a standard arrow with a starburst when the cursor is over a control. DecimalBase Use the DecimalBase property to specify whether the control uses a decimal or hexadecimal base. Default Use the Default property to specify whether the control is the default control for the form. EditBuddy Use the EditBuddy property to specify whether a spinner control edits the control immediately preceding it in the tab order. Enable Use the Enable control to specify whether a control can be used. Controls not enabled are visible to the user, but not usable. FlexHorizontal Use the FlexHorizontal control to determine how a control reacts to horizontal resizing of the form. The options for this property are: None Shift When the form is resized horizontally, do not adjust the position or size of the control. When the form is resized horizontally, shift the control to maintain its relative position on the form.
Expand When the form is resized horizontally, expand the control to maintain its relative size on the form. Proportional When the form is resized horizontally, shift and resize the control proportionally to keep the control centered on the form. FlexVertical Use the FlexVertical control to determine how a control reacts to vertical resizing of the form. The options for this property are: None Shift When the form is resized vertically, do not adjust the position or size of the control. When the form is resized vertically, shift the control to maintain its relative position on the form.
Expand When the form is resized vertically, expand the control to maintain its relative size on the form. Proportional When the form is resized vertically, shift and resize the control proportionally to keep the control centered on the form. FileName Use the FileName property to specify the name of the image file that you want to add to your form. This property is available when using the Image control.
Chapter 3. Getting started with the DB2 Table Editor Developer component
127
Font
Use the Font property to specify the font type, style and size for the text displayed in a control.
ForeColor Use the ForeColor to specify the color of the text displayed in a control. Group Use the Group property to specify whether a control is the first in a tab order. HatchStyle Use the HatchStyle property to fill a label, box, ellipse, or closed freehand control with hatch lines. The options for this property are: None Display the control without hatch lines.
Horizontal Fill the control with horizontal hatch lines. Vertical Fill the control with vertical hatch lines. Diagonal Fill the control with left-to-right diagonal hatch lines. DiagRev Fill the control with right-to-left diagonal hatch lines. Cross Fill the control with crossed vertical and horizontal lines. DiagCross Fill the control with crossed diagonal lines. Height or FormHeight Use the Height property to specify the height of the form in pixels. If the user resizes the form to a height less than the FormHeight or FormWidth properties, scroll bars appear. HiliteColor Use the HiliteColor property to specify the color of any highlighting in a control. HorizontalScroll Use the HorizontalScroll property to specify the presence and style of any horizontal scroll bars in the control. IconView Use the IconView to specify the style of icon to display when the ShowIcon property is selected for a list control. The options for this property are: IconChecked Display the Checked icon next to each list item. IconEmptyDoc Display the EmptyDoc icon next to each list item. IconFillDoc Display the FillDoc icon next to each list item. IconInfo Display the Info icon next to each list item. IconPlus Display the Plus icon next to each list item.
128
Users Guide
IncrAccelerator Use the IncrAccelerator to specify the increment displayed by the spin control. Layout Use the Layout property to specify the placement of a bitmap on a button control or form. You can align a bitmap to the center, left, right, top or bottom of a button control. You can align a bitmap to the center, left or right, stretch, or size to fit in relation to a specified area on the form body. Left Use the Left property to specify the location in pixels of the left edge of a control, relative to the dimensions of the form.
ListStyle Use the ListStyle property to specify how the contents of a list control are displayed. The ListStyle property includes these options: List Report Display the contents of a list control in tabular format. Large Icon Display the contents of a list control in separated icon format. Small Icon Display the contents of a list control in a list that continues vertically. MaximizeBox Use the MaximizeBox property to specify whether the user can maximize the form. MaximumEq Use the MaximumEq property to specify the maximum value for a spin control. MinimizeBox Use the MinimizeBox property to specify whether the user can minimize the form. MinimumEq Use the MinimumEq property to specify the minimum value for a spin control. NumDropped Use the NumDropped property to specify the number of list items to display in the drop-down list of a combo box control. Object Use the Object property to specify the name of the selected object. Orientation Use the Orientation property to specify either a horizontal or a vertical orientation for a spinner control. PenStyle Use the PenStyle property to specify the line style for a connector, line, freehand, border or ellipse control. The options for this property are: Solid Dash Display a solid line style. Display a dashed line style.
Chapter 3. Getting started with the DB2 Table Editor Developer component
129
Dot
Dash-Dot Display an alternated dash and dot line style. Dash-Dot-Dot Display an alternated dash and two dot line style. PenWidth Use the PenWidth property to specify the line thickness in pixels for a connector, line, freehand, border or ellipse control. You can also use the PenWidth property to add a border of the specified thickness around an area of text. PrintScale Use the PrintScale property to specify the scale to be used in printing the form. For example, a PrintScale of 2 prints the form at a 2:1 size ratio. ReadOnly Use the ReadOnly property to specify an edit box or multi edit box control as read only. Controls set to read only can display values, but can not be edited by the end user. RemoveSelection Use the RemoveSelection property to specify whether or not to clear the users selection upon update of a list box control. Right Use the Right property to specify the location in pixels of the right edge of a control, relative to the dimensions of the form.
RotateAngle Use the RotateAngle property specify the number of degrees by which to rotate a text, line, freehand, border or ellipse control on a form. ScrollBars Use the ScrollBars property to specify whether to always display scroll bars on the form. Specify: Yes No Always display scroll bars on the form. Display scroll bars on the form only when the user resizes to form to a height or width less than the FormHeight or FormWidth properties.
ShadowStyle Use the ShadowStyle property to specify the presence and position of a shadow for a border or ellipse control. The options for this property are: None Display the control without a shadow.
Top/Left Display a shadow above and to the left of the control. Bottom/Right Display a shadow below and to the right of the control. Bottom/Left Display a shadow below and to the left of the control. Top/Right Display a shadow above and to the right of the control. ShowCheckBoxes Use the ShowCheckBoxes property to display a check box next to each list item in a list control.
130
Users Guide
ShowGrid Use the ShowGrid property to display grid lines between rows and columns in a list control. ShowIcon Use the ShowIcon property to display an icon next to each item in a list control. Use the IconView property to specify the style of icon you want to display. Sort Use the Sort property to specify whether or not to sort the contents of the control.
Tabstop Use the Tabstop property to specify whether or not to include the selected control in the tab order. Tag Text Use the Tag property to assign a developer-assigned value to a control. Use the Text property to specify text to display in an edit box, multi edit box, or list box control when the form opens. This text will be replaced if and when the control is subsequently populated, for example through a default value or user-initiated search.
ToolTopText Use the ToolTipText property to specify the text to display when the cursor moves over a control. You can add multi lined too tip text that is accessible by clicking an arrow in the tool tip. To create multi lined tool tip text, use the following syntax. Type the text that you want to appear on the first line of your tool tip, then type \r then type the rest of the tool tip. To create another line break, type \n where you wan the line to break. When you hover over a control, everything to the left of the \r will be visible followed by an arrow. When you click on the arrow, all of the tool tip will be visible. Top Use the Top property to specify the location in pixels of the top edge of a control, relative to the dimensions of the form.
UseColors Use the UseColors property to specify whether or not to display colors in a control. UseTabStops Use the TabStops property to specify whether or not to allow the user to tab through the list items in a list box control. VerticalScroll Use the VerticalScroll property to specify the presence and style of any vertical scroll bars in the control. Visible Use the Visible property to specify whether or not to display the selected control on the form. Width or FormWidth Use the Width property to specify the width of the form in pixels. If the user resizes the form to a width less than the FormHeight or FormWidth properties, scrollbars appear. WrapAround Use the WrapAround property to specify whether or not a spinner control, after reaching its maximum value in a series, returns to its minimum value at the next increment and displays the series again. Related concepts
Chapter 3. Getting started with the DB2 Table Editor Developer component
131
Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. DB2 Table Editor Form Controls on page 116 DB2 Table Editor form control attributes on page 118
132
Users Guide
Adding a Jpeg image to a form on page 134 Adding an accelerator key to a button control on page 135
133
5.
6.
7. 8.
9.
it accordingly. When the format of the object to be displayed is not recognized by DB2 Table Editor, the object will be displayed as text. If you select Auto Recognize (or show text when format not recognized), you must set format options for each LOB format on the Format page by scrolling through the Format pages for each LOB format using the arrows on the top right of the Format page. Optional: Check the Allow external viewing and editing check box to enable viewing and editing of LOBs using an external program such as Microsoft Paint. When this check box is checked, in the DB2 form that you are creating you can double click the LOB control and the LOB will be displayed in an external viewer. Some LOB types can be edited using the external viewer then saved back to the database if desired. Optional: Check the Allow menu tools check box to allow editing of text or multimedia LOB objects using the editing tools present on your machine. When editing a text object, you can select the portion of the text that you want to edit, then right click and select the appropriate editing tool from the pop-up menu. On the Column page, select the LOB column that you want to have displayed in the LOB control from the list. On the Format page, specify the options corresponding to the type of LOB that you selected from the Display menu on the General page. v If you selected Show images always, you must specify the options for image LOBs. v If you selected Show multimedia always, you must specify the options for multimedia LOBs. v If you selected Show text always, you must specify the options for text LOBs. v If you selected Auto Recognize (or show text when format not recognized) you must specify the options for image, multimedia and text LOBs, by scrolling through the format pages for each LOB type using the arrow buttons on the top right of the format screen. Click OK. Related concepts Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. Using special command characters on page 135 DB2 Table Editor Form Controls on page 116 Related tasks Adding a control to a form on page 132 Deleting a control from a form on page 132 Setting control properties on page 133 Adding a Jpeg image to a form Adding an accelerator key to a button control on page 135
134
Users Guide
5. Go to the AsURL property. Set the AsURL property to true to link to the .jpg on your form. Set the AsURL property to false to have the .jpg image embedded on your form. Related concepts Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. Using special command characters DB2 Table Editor Form Controls on page 116 Related tasks Adding a control to a form on page 132 Deleting a control from a form on page 132 Setting control properties on page 133 Creating a LOB control on a form on page 133 Once you have created a LOB control on a form, use the LOB Control Attributes window to set the attributes for your LOB control. You can create LOB controls that display or play text, image or multimedia LOB data. Adding an accelerator key to a button control
135
%X
*X
=X
Related concepts Working with controls on a form on page 116 There are many controls that can be used when creating a form using DB2 Table Editor. DB2 Table Editor Form Controls on page 116 Related tasks Adding a control to a form on page 132 Deleting a control from a form on page 132 Setting control properties on page 133 Creating a LOB control on a form on page 133 Once you have created a LOB control on a form, use the LOB Control Attributes window to set the attributes for your LOB control. You can create LOB controls that display or play text, image or multimedia LOB data. Adding a Jpeg image to a form on page 134 Adding an accelerator key to a button control on page 135
Opening a form
You can open a DB2 Table Editor form that is saved on a local file or from a database server. If you are opening a form created using an earlier version of DB2 Table Editor Developer, you will be asked if you want to migrate that form to the current version of DB2 Table Editor Developer.
136
Users Guide
1. From the main window of DB2 Table Editor Developer, select File --> Open. The Windows Open dialog box opens. 2. Navigate to the form you want to open and click Open. The form opens in the DB2 Table Editor Developer main window.
Saving a form
You can save a DB2 Table Editor form to a local file or to a database server.
137
1. From the main window of DB2 Table Editor Developer, select File --> Save As. The Save As window opens. 2. Navigate to the location where you want the form to be saved. 3. Type the name for the form, and click Save. Table Editor Developer saves the active form to a local file.
Printing a form
You can print a DB2 Table Editor Developer form. 1. Select File--> Print. The Windows Print dialog box opens. 2. Select the desired print options, and click OK. The active form prints. Related concepts Opening a form on page 136 You can open a DB2 Table Editor form that is saved on a local file or from a database server. If you are opening a form created using an earlier version of
138
Users Guide
DB2 Table Editor Developer, you will be asked if you want to migrate that form to the current version of DB2 Table Editor Developer. Saving a form on page 137 You can save a DB2 Table Editor form to a local file or to a database server. Deleting a form You can delete a DB2 Table Editor form that is stored in a local directory or on a database server. Related tasks Closing a form Remember to save your work before closing a DB2 Table Editor form. Migrating Forms to a Different Environment on page 142 Use the Forms, Servers and Tables window to migrate forms from one environment to another. For instance, you can migrate a form from a test environment to a production environment
Closing a form
Remember to save your work before closing a DB2 Table Editor form. To close a form, select File --> Close. Related concepts Opening a form on page 136 You can open a DB2 Table Editor form that is saved on a local file or from a database server. If you are opening a form created using an earlier version of DB2 Table Editor Developer, you will be asked if you want to migrate that form to the current version of DB2 Table Editor Developer. Saving a form on page 137 You can save a DB2 Table Editor form to a local file or to a database server. Deleting a form You can delete a DB2 Table Editor form that is stored in a local directory or on a database server. Related tasks Printing a form on page 138 You can print a DB2 Table Editor Developer form. Migrating Forms to a Different Environment on page 142 Use the Forms, Servers and Tables window to migrate forms from one environment to another. For instance, you can migrate a form from a test environment to a production environment
Deleting a form
You can delete a DB2 Table Editor form that is stored in a local directory or on a database server.
139
2. From the Server list, select the server that stores the form that you want to delete. 3. In the Owner field, type the name of the owner of the form, and click List. The Object List window opens and it contains a list of all of the forms that are on the specified server and are owned by the specified owner. 4. From the Object list window, select the form that you want to delete, and click Delete. A confirmation dialog box will open. 5. Click Yes to confirm the deletion. DB2 Table Editor Developer deletes the selected form from the server. Related concepts Opening a form on page 136 You can open a DB2 Table Editor form that is saved on a local file or from a database server. If you are opening a form created using an earlier version of DB2 Table Editor Developer, you will be asked if you want to migrate that form to the current version of DB2 Table Editor Developer. Saving a form on page 137 You can save a DB2 Table Editor form to a local file or to a database server. Related tasks Printing a form on page 138 You can print a DB2 Table Editor Developer form. Closing a form on page 139 Remember to save your work before closing a DB2 Table Editor form. Migrating Forms to a Different Environment on page 142 Use the Forms, Servers and Tables window to migrate forms from one environment to another. For instance, you can migrate a form from a test environment to a production environment
140
Users Guide
5. Select the rule type that you want to apply to the control and click Next. A dialog box opens asking for additional validation rule parameters. 6. Type any additional parameters the validation rule requires and click Next. The Action window opens. 7. Specify when to apply the validation rule by checking any appropriate check box on the window, and click Next.The Error Message dialog box opens. 8. In the Error message field, type the error message that you want to display upon violation of the validation rule. If custom help is available, type the name and context number of the help file to associate with the error message. Click Next. A summary of the validation rule opens. 9. Click Finish to create the validation rule. Related concepts Working with validation rules on page 140 Related tasks Creating a validation group Deleting a validation rule You can delete a validation rule from a form. Deleting a validation group on page 142 You can delete a validation group from a form.
1. Select Form --> Validation Rules. The Validation Rules window opens. 2. Click New Group. A new validation group is created. 3. Click New Rule, and a create new validation rules for the group. To create new rule, follow the steps in the following section: Creating a validation rule. Related concepts Working with validation rules on page 140 Related tasks Creating a validation rule on page 140 Deleting a validation rule You can delete a validation rule from a form. Deleting a validation group on page 142 You can delete a validation group from a form.
Chapter 3. Getting started with the DB2 Table Editor Developer component
141
2. Select the rule you want to delete and click Delete. The validation rule is deleted. Related concepts Working with validation rules on page 140 Related tasks Creating a validation rule on page 140 Creating a validation group on page 141 Deleting a validation group You can delete a validation group from a form.
142
Users Guide
4. From the Servers window, select the server from which you want to migrate the forms, from the Origin server drop-down list. 5. Select the server to which you want to migrate the forms, from the Destination server drop-down list. 6. Click Add. 7. Click Next. If you are migrating a form that contains select statements, the Statements window opens. If your form does not contain select statements, the Tables window opens. 8. For forms that contain select statements: a. Select the origin and destination server pair for the form that you are migrating form the Server Link drop down. b. Select the control that contains the SQL statement from the Controls drop-down list. c. Modify the tables in the select statement in the Select Statement box. The tables referenced in the select statement should be changed to tables in the database to which you are migrating the form. d. Click Apply to apply the changes that you made to your select statement in the Select Statement box. (To undo your changes to the SQL statement, click Rollback.) e. Click Next to move to the next step in the migration process. The Tables window opens. 9. From the Tables window, select the origin and destination server combination from the Server link drop-down menu. 10. From the Origin table drop-down menu, select the table in the origin database to which your form connects. 11. From the Destination table drop-down menu, select the table in the destination database to which your form will connect. You can click the browse button to browse for a table using the Object List window. 12. Click Add. The origin and destination tables appear in the Table Links list. 13. Click Finish. Your form is migrated. Related concepts Opening a form on page 136 You can open a DB2 Table Editor form that is saved on a local file or from a database server. If you are opening a form created using an earlier version of DB2 Table Editor Developer, you will be asked if you want to migrate that form to the current version of DB2 Table Editor Developer. Saving a form on page 137 You can save a DB2 Table Editor form to a local file or to a database server. Deleting a form on page 139 You can delete a DB2 Table Editor form that is stored in a local directory or on a database server. Related tasks Printing a form on page 138 You can print a DB2 Table Editor Developer form. Closing a form on page 139 Remember to save your work before closing a DB2 Table Editor form.
Chapter 3. Getting started with the DB2 Table Editor Developer component
143
144
Users Guide
Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open.
145
Position Specifies the position of the currency symbol used with currency values. Currency When checked, displays number values as currency. Column Displays the column name for each column in the control, as returned by the database. This setting is available only for list controls. Header Displays the header name for each column displayed in the control. This setting is available only for list controls. Width Displays the width of a column. This setting is available only for list controls. Alignment Displays the alignment of the data within a column. This setting is available only for list controls. Format Displays any formatting for the data within a column. This setting is available only for list controls. Change Opens the Format dialog box. This button is only available for list controls. OK Cancel Cancels any changes and this dialog box. Apply Accepts any changes and leaves the dialog box open. Accepts the changes you have specified and closes the dialog box.
Change Accepts the changes you have specified and closes the dialog box. Delete Deletes the action from the control. OK Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open. Accepts the changes you have specified and closes the dialog box.
146
Users Guide
Remove Removes a value from an explicit list of values. Move up Moves a value up in an explicit list of values. Move down Moves a value down in an explicit list of values. Link Column Displays the Select Column to Link dialog box. OK Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open. Accepts the changes you have specified and closes the dialog box.
Chapter 3. Getting started with the DB2 Table Editor Developer component
147
Table 6. Command action table (continued) Action Close the form SQL Verb COMMIT Description Closes the form. This action closes any open result sets and commits pending database modifications but does not close the database connection. Commits pending transactions for the form. Selecting Commit pending transactions overrides the Commit Scope setting. Deletes the current row from the table. This action deletes the current row from the primary table only. If any rules have been specified for the delete action, then they are evaluated before doing the delete. If a rule criteria is not met then a message is displayed and the delete is not completed. If the Confirm on Delete option is checked, then a message box will appear asking you to confirm the delete. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Displays DB2 Table Editor online help. Executes the specified command, including Refer-Back conditions. If this is run using the Java Player component as an applet, then the command is run by passing the command to the browser. If this is run using the Windows user application, or the Java player running as an application, then the command is sent to the operating system to be executed. Closes the application. This action closes any open result sets, commits pending database modifications, closes all open database connections and exits DB2 Table Editor. Inserts a row into the primary table. This action takes the current values for all controls that are bound to the primary table in the form and inserts a row into the primary table for the form. If a replacement value has been specified for a control then it is used instead of the current control value. If the Enter default values as value has been specified, then the column is not included in the insert and DB2 supplies the default value. If Enter null values as value has been specified, then a null value is used for the bound column. If any rules have been specified for the insert action, they are evaluated before doing the insert. If a rule criteria is not met then a message is displayed and the insert is not completed. If the Confirm on Insert option is checked, then a message box will be produced for the user to confirm the insert. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Launches the application that is associated with the contents of the specified control. For example, you can use this button action to launch an MP3 file displayed in a control. Select Launch control from the list, then select the desired control. If this form is run using the Java Player component as an applet, then the control is launched by passing the current value of the control to the browser.
Commit pending transactions Delete the current row from the table
COMMIT
DELETE
INSERT
Launch Control
148
Users Guide
Table 6. Command action table (continued) Action Launch LOB Application SQL Verb Description Launches the application that is associated with the LOB contents of the specified control. For example, you can use this button action to launch an image file displayed in a control. Select Launch LOB application from the list, from the Launch LOB Application window, select the desired control and specify the LOB associations for that control. If this form is run using the Java Player component as an applet, then the control is launched by passing the current value of the control to the browser. The Multiple actions button action allows you to specify more than one action for a button. When the button is clicked, the button actions will be run in the order that they are listed in the Multiple Actions dialog box. This functionality is only available in forms that are accessed using the Windows User interface. Opens another form. When you create the button, you specify the form that you want the button to open. If the form that is being opened has linked controls then the current values of the linked controls on the current form are used to populate linked controls on the form that is being opened, and a search is performed. If the specified form is already opened, it is reused. If the Close master form after opening linked form option was specified, then the master form is closed. If the Refresh form contents whenever the values for the linked controls change option was specified then the child form is synchronized with the values from the master forms linked controls. Refreshes the contents of any selected controls. To use this control, select Refresh the selected controls from the list, then select one or more controls. This action will refresh the contents of any selected controls when clicked. FETCH Retrieves the next row in the table. If there are no more rows in the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Retrieves the previous row in the table. If you are at the beginning of the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Reverts to the original values of this row. This action sets the form control values to the original database values. This action does not close any open result sets, commit pending database modifications or close open database connections.
Multiple actions
Open Form
FETCH
Chapter 3. Getting started with the DB2 Table Editor Developer component
149
Table 6. Command action table (continued) Action Run an SQL statement SQL Verb Description Runs the specified SQL statement, including Refer-Back conditions. This can be an SQL statement to update, insert or delete data from tables that are not the primary table. Stored procedures are also supported. After an SQL statement is successfully run, a message box is displayed (if this option has been set for the action), allowing the you to confirm or cancel the actions of the SQL statement. If cancel is chosen then a rollback is performed, otherwise a commit is issued. OPEN CURSOR followed by FETCH Searches the table for matching rows. This action uses the current values for all bound controls to create a select statement. It will look for special character commands in all bound controls and uses them in building the search (for more information, see Using Special Command Characters in a Control). The first row that is returned is displayed in the form. A message will appear if no search results are returned. If sort conditions have been used, then the results are returned in that order. If there was already a result set opened, it is closed before performing the new search, however, any pending database modifications are not committed. If a replace value has been specified for a control, it is used instead of the current control value. If the Ignore on select option has been set for a control then the selected column is not included in the search. If the Enter null values as option is used then a null value is used for the bound column. If any rules have been specified for the search action, they are evaluated before doing the select. If a rule criteria is not met then a message is displayed and the search is not completed. If there are any LOB columns bound to controls, they are not automatically retrieved by the search. Updates the current row in the table. This action updates the primary table values for the current row. It includes only values that have been changed in the update. If a replace value has been specified for a control then it is used instead of the current control value. There is special handling for updates of primary key values (any foreign keys in associated tables are automatically changed in order to retain the correct relationships to the primary key). If possible, the update is done by using a positioned update (current position of the cursor). If this is not possible, then a searched update is done using the current values for all controls that are bound to the primary table in the form. If the Enter null values as option was specified, then a null value is used for the bound column. If any rules have been specified for the update action, then they are evaluated before doing the update. If a rule criteria is not met, then a message is displayed and the update is not done. If the Confirm on Update option is checked, then a message box will be produced for the user to confirm the update. If the number of pending database modifications exceeds the commit scope (defaults to 1) then a commit is issued.
UPDATE
OK
Accepts the changes you have specified and closes the dialog box.
150
Users Guide
Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open.
Chapter 3. Getting started with the DB2 Table Editor Developer component
151
Column The names of the columns that will appear in your list control are listed in the Column column. Value In the value column, next to each column in the list, type the result that you would like to appear in that column in the event of an empty result set.
For example:
jdbc:informix-sqli:myhost:1526/mydatabase:INFORMIXSERVER=myserver
OK Cancel
Accepts the changes you have specified and closes the dialog box. Cancels any changes and closes the dialog box.
Apply Accepts any changes and leaves the dialog box open.
Delete Removes the selected table from the list. Set Primary Changes the primary table to the one currently selected.
152
Users Guide
Refresh Refreshes the forms view of a table that has been modified. A form that needs to be refreshed cannot be opened in the User application. Primary Table Specifies the table being edited. Other tables can be referenced to populate controls, but only one table can be edited per form. OK Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open. Accepts the changes you have specified and closes the dialog box.
Delete Deletes the selected join condition from the list. Move Up Moves the selected join condition up in the join conditions list. Move Down Moves the selected join condition down in the join conditions list. OK Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open. Accepts the changes you have specified and closes the dialog box.
Delete Deletes the selected sort condition from the list of sort conditions used in form. Move Up Moves the selected sort condition up in the sort conditions list. Move Down Moves the selected sort condition down in the sort conditions list. OK Accepts the changes you have specified and closes the dialog box.
Chapter 3. Getting started with the DB2 Table Editor Developer component
153
Cancel Cancels any changes and closes the dialog box. Apply Accepts any changes and leaves the dialog box open.
Refresh Refreshes the list of available tables according to the specified owner and name. Add To List Lists all of the forms matching the owner and name that you specified in the Owner and Name fields and appends this list to the existing forms in the List field. Add Associates the specified table with the form and leaves the dialog box open.
Close Accepts any changes you have specified and closes the dialog box.
154
Users Guide
Columns from table 2 Lists all columns in the selected table. OK Cancel Cancels any changes and closes the dialog box. Creates a join condition between the two specified tables according to the columns selected.
155
Selecting rows from a table When checked, applies the rule before selecting rows from a table. Deleting a row from a table When checked, applies the rule before deleting a row from a table. Back Next Cancels the settings you have specified and returns to the previous dialog box. Accepts the settings you have specified and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
Finish Creates the new validation rule with the settings you have specified. Cancel Closes the dialog box and cancels the creation of the validation rule.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes this dialog box and cancels the creation of the validation rule.
156
Users Guide
Is special register Displays whether or not the value specified is a special register. Back Next Cancels the settings you have specified and returns to the previous dialog box. Accepts the settings you have specified and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. this option is unavailable on the Control dialog box. Cancel Closes the dialog box and cancels the creation of the validation rule.
Chapter 3. Getting started with the DB2 Table Editor Developer component
157
Add
Opens the Value dialog box so you can add a value to the list of valid values.
Remove Removes a value from the list of valid values. Move up Moves a value up in the list of valid values. Move down Moves a value down in the list of valid values. Back Next Cancels the settings you have specified and returns to the previous dialog box. Accepts the settings you have specified and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
158
Users Guide
Control must Displays the value used for comparison when checking for validation. Is special register Displays whether or not the value is a special register. Back Next Cancels the value you have specified and returns to the previous dialog box. Accepts the value you have specified and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. OK Cancel Closes the dialog box and cancels the creation of the validation rule. Accepts the value you have specified and closes the dialog box.
Finish Skips any additional dialog boxes and creates the new validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
Chapter 3. Getting started with the DB2 Table Editor Developer component
159
Back Next
Cancels the settings you have specified and returns to the previous dialog box. Accepts the settings you have specified and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the validation rule.
Finish Skips any additional dialog boxes and creates the validation rule with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. This option is not available on the Logical Connector dialog box. Cancel Closes the dialog box and cancels the creation of the validation rule.
160
Users Guide
Refresh Refreshes the list according to the owner and name that you specified in the Owner and Name fields. Add To List Lists all of the forms matching the owner and name that you specified in the Owner and Name fields and appends this list to the existing forms in the List field. Open Opens the selected form.
Delete Deletes the selected form. Cancel Closes the dialog box without opening a form.
DITA
This dialog box is displayed when you click Add on the Control Attributes dialog box (Replace Values Tab). You use this dialog box to specify replacement values for a control. On action Specifies the user action that will prompt the replacement of the controls contents. Insert When selected, values are replaced when the user inserts a new row into the table. Search When selected, values are replaced when the user starts a search.
Chapter 3. Getting started with the DB2 Table Editor Developer component
161
Update (Set) When selected, values are replaced when the user updates a row in the table. The update occurs at the set clause of the SQL UPDATE statement. Update (Where) When selected, values are replaced when the user updates a row in the table. The update occurs at the where clause of the SQL UPDATE statement. Replace contents with Replaces the contents of the control with the specified value. Default Value Replaces the contents of the control with the default value for the control. Literal Replaces the contents of the control with a literal value. Null Replaces the contents of the control with a null value.
Select Statement Replaces the contents of the control with a value generated by a SELECT statement. If the SELECT statement returns multiple values, only the first value is used to replace the current value. Special Register Replaces the contents of the control with a special register, such as user, current time, or current date. The special registers available to you depend on the database platform you are using. Refer to your DB2 documentation to find out which special registers you can use. OK Cancel Cancels any changes and closes this dialog box. Test SQL Click this button to test the select statement that you have typed. Enter a literal or select statement or special register Displays the literal, SELECT statement, stored procedure call, or special register that you are using to replace the contents of the control. Creates the new replacement value and closes the dialog box.
162
Users Guide
OK Cancel
Imports the selected panel into DB2 Table Editor. Closes the dialog box without importing a panel.
List
Opens the DBEDIT Panels dialog box and lists all panels matching the specified server, owners and IDs.
Chapter 3. Getting started with the DB2 Table Editor Developer component
163
Main Window
This window is displayed when you start DB2 Table Editor. The main window displays the DB2 Table Editor forms you create and edit. You use the forms created with DB2 Table Editor to search and edit data contained in tables stored on your database server.
Form Window
This window is displayed when you open a DB2 Table Editor form. The form window is the space that contains a form.
Down Moves the selected control down in the tab order. Delete Removes the selected control from the tab order. Object Displays the name property of the selected control.
164
Users Guide
Paste Pastes the current contents of the Clipboard to the Bitmap dialog box. Load Clear RLE Link Displays the Windows Browse Files dialog box so you can load a saved image. Clears all settings in the dialog box. When checked, applies file compression to the current image. When checked, links to the image file rather than embedding the image in the form.
File Name Displays the file name of the current image. Transparent Specifies the image color to make transparent.
Delete Removes the specified snap point from the control. Up Moves the selected snap point up in the points list.
Down Moves the selected snap point down in the points list. Type dX Specifies the location on the control of the new snap point. Specifies the horizontal distance in pixels from the control of the new snap point. A positive number places the snap point to the right of the control, while a negative number places the snap point to the left of the control. Specifies the vertical distance in pixels from the control of the new snap point. A positive number places the snap point above the top of the control, while a negative number places the snap point below the bottom of the control.
dY
By pixel When checked converts the unit of measure specified in the dX and dY fields to pixels.
Chapter 3. Getting started with the DB2 Table Editor Developer component
165
Max snapped in Specifies the maximum number of connections that can be made to the specified snap point. Max snapped out Specifies the maximum number of connections that can be made from the specified snap point. Tip Displays the tool tip text.
Use Grid Offset / Snap Point Color When checked, allows you to offset the connector and specify the color of the connector. dG Specifies the amount of offset applied to the connector.
Right
LeftRight Select LeftRight to have the control anchored to the form window on the left and right side of the control. The control will resize when the window is resized. Proportional Select Proportional to remain in the same proportion to the window as it is resized. The control will be anchored to the form window at the center of the control. The control will resize when the window is resized.
166
Users Guide
Center Select Center to have the control anchored to the form window at the center of the control. The control will remain the same size when the window is resized. AnchorSnaps Opens the Enter Snap Points dialog box. AnchorVert Specify how you want the control to be anchored vertically. This determines how the control will act when the window is resized. The options are as follows: Top Select Top to have the control anchored to the form window on the top of the control. The control will remain the same size when the window is resized. Select Bottom to have the control anchored to the form window on the bottom of the control. The control will remain the same size when the window is resized. TopBottom Select TopBottom to have the control anchored to the form window on the top and bottom of the control. The control will resize vertically when the window is resized. Proportional Select Proportional to remain in the same proportion to the window as it is resized. The control will be anchored to the form window at th Center Select Center to have the control anchored to the form window at the center of the control. The control will remain the same size when the window is resized. Arrowhead Specifies the style of arrowhead that is used for the control. ArrowheadHeight Displays the height of the arrowhead. BackColor Specifies the background color that is used by the control. Bitmap Opens the Bitmap dialog box. BorderDrawn Specifies whether or not the control uses a border. BorderColor Specifies the color of the border that is used by the control. BorderWidth Displays the width of the border that is used by the control. BorderStyle Specifies the style of the border that is used by the control. Bottom Specifies the location of the bottom border of the control.
Bottom
Chapter 3. Getting started with the DB2 Table Editor Developer component
167
ButtonShape Specifies the shape of the button control. CaseOrPassword Specifies the appearance of text entered into the control. Color Specifies the color of the form. ComboType Specifies the type of the combo box control. CursorPointer Specifies the shape of the cursor pointer when it is over the control. EditBuddy Specifies whether or not the spinner control edits the control immediately preceding it in the tab order. Enable Specifies whether or not the control is enabled. Controls not enabled are visible to the user, but are not usable. FlexHorizontal Specifies whether the control shifts, expands or adjusts proportionately when the form is resized horizontally. FlexVertical Specifies whether the control shifts, expands or adjusts proportionately when the form is resized vertically. Font Specifies the font that is used in the control.
ForeColor Specifies the font color of the control. FormHeight Displays the minimum height for displaying scroll bars. FormWidth Displays the minimum width for displaying scroll bars Group Specifies whether this control is the first control in a tab order. HatchStyle Specifies the type of hatching appearing in the control. Height Specifies the height of the control. HiliteColor Specifies the color of any highlighting in the control. HorizontalScroll Specifies the presence and style of any horizontal scroll bars in the control. IconView Specifies the icon style that will be displayed next to each list item in a list control. There are five possible icon views as follows: IconChecked The icons in your list control will appear as check marks. IconEmptyDoc The icons in your list control will appear as a blank page.
168
Users Guide
IconFillDoc The icons in your list control will appear as a page with lines on it. IconInfo The icons in your list control will appear as I. IconPlus The icons in your list control will appear as plus signs. IncrAccelerator Displays the increment that is used by the spin control. Layout Specifies the layout of a bitmap image on the control. Left Displays the location of the left border of the control.
ListStyle Specifies the list style of a list control. There are five possible list styles: Grid View The list entries in your list control will appear in grid format. Large Icon The list entries in your list control will appear as large icons. List Report The list entries in your list control will appear in tabular format. Small Icon The list entries in your list control will appear as small icons. MaximizeBox Specifies whether or not you can maximize the display of the form. MaximumEq Specifies the maximum value allowed for a spin control. MinimizeBox Specifies whether or not you can minimize the display of the form. MinimumEq Specifies the minimum value allowed for a spin control. MouseTrack Mouse track is an option for list controls. When mouse track is on, mousing over a list item will highlight it. Hovering over the list item with the mouse will select it. NumDropped Specifies the number of items shown when a combo box control is dropped down. Object Displays the name of the control. Orientation Specifies the orientation of the control. PenWidth Specifies the width of the pen that is used in drawing line controls. The list entries in your list control will appear in list format with property information.
Chapter 3. Getting started with the DB2 Table Editor Developer component
169
PenStyle Specifies the style of the pen that is used in drawing line controls. PrintScale Specifies the scale to be that is used in printing the form. ReadOnly Specifies whether or not to make the contents of the control read only. RemoveSelection Specifies whether or not clicking on a selection will deselect that selection. Right Displays the location of the right border of the control.
RotateAngle Displays the angle of rotation of the control. ScrollBars Displays whether or not the control has scroll bars. ShowCheckBoxes Specifies whether or not to display check boxes next to each list item in a list control. ShowGrid Specifies whether or not to display grid lines between rows and columns in a list control. ShowIcon Specifies whether or not to display an icon next to each list item in a list control. ShadowStyle Specifies the style of shadow appearing in the control. Sort Specifies whether or not to sort the contents of the control.
Tabstop Select Yes to enable tab access to the control. Select No to prevent users from acing the control using the tab key on the keyboard Tag Text Title Enter any comments about the control here. This information will not appear on the form. Displays the text of the control. Displays the title of the control.
ToolTipText Displays the text of the tool tip. You can add multi lined too tip text that is accessible by clicking an arrow in the tool tip. To create multi lined tool tip text, use the following syntax. Type the text that you want to appear on the first line of your tool tip, then type \r then type the rest of the tool tip. To create another line break, type \n where you wan the line to break. When you hover over a control, everything to the left of the \r will be visible followed by an arrow. When you click on the arrow, all of the tool tip will be visible. Top Displays the location of the top border of the control.
UseColors Specifies whether or not the developer can assign colors to the control. UseTabstops Specifies whether or not the control can have a tab stop.
170
Users Guide
VerticalScroll Specifies the presence and style of any vertical scroll bars in the control Visible Specifies whether or not the control is visible to the end user. Width Displays the width of the control. WrapAround Specifies whether or not to allow text wrapping in the control.
Finish Skips any additional dialog boxes and creates the new form with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. This option is not available on the Server dialog box. Cancel Closes the dialog box and cancels the creation of the form.
Finish Skips any additional dialog boxes and creates the new form withthe settings you have specified. Default settings are used for anydialog boxes you skip by clicking Finish. This option is not availableon the Tables dialog box. Cancel Closes the dialog box and cancels the creation of the form.
Chapter 3. Getting started with the DB2 Table Editor Developer component
171
Finish Skips any additional dialog boxes and creates the new form with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. This option is not available on the Columns dialog box. Cancel Closes the dialog box and cancels the creation of the form.
Commit COMMIT pending transactions Delete the current row from the table DELETE
172
Users Guide
Description Inserts a row into the primary table. This action takes the current values for all controls that are bound to the primary table in the form and inserts a row into the primary table for the form. If a replacement value has been specified for a control then it is used instead of the current control value. If the Enter default values as value has been specified, then the column is not included in the insert and DB2 supplies the default value. If Enter null values as value has been specified, then a null value is used for the bound column. If any rules have been specified for the insert action, they are evaluated before doing the insert. If a rule criteria is not met then a message is displayed and the insert is not completed. If the Confirm on Insert option is checked, then a message box will be produced for the user to confirm the insert. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Retrieves the next row in the table. If there are no more rows in the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Retrieves the previous row in the table. If you are at the beginning of the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Reverts to the original values of this row. This action sets the form control values to the original database values. This action does not close any open result sets, commit pending database modifications or close open database connections.
FETCH
Retrieve the previous row Revert to the original values of this row Search for matching rows
FETCH
Searches the table for matching rows. This action uses the current values for all bound controls to create a select statement. It will look for special character commands in all bound controls and uses them in building the search (for more information, see Using Special Command Characters in a Control). The first row that is returned is displayed in the form. A message will appear if no search results are returned. If sort conditions have been used, then the results are returned in that order. If there was already a result set opened, it is closed before performing the new search, however, any pending database modifications are not committed. If a replace value has been specified for a control, it is used instead of the current control value. If the Ignore on select option has been set for a control then the selected column is not included in the search. If the Enter null values as option is used then a null value is used for the bound column. If any rules have been specified for the search action, they are evaluated before doing the select. If a rule criteria is not met then a message is displayed and the search is not completed. If there are any LOB columns bound to controls, they are not automatically retrieved by the search.
Chapter 3. Getting started with the DB2 Table Editor Developer component
173
Action
SQL Verb
Description Updates the current row in the table. This action updates the primary table values for the current row. It includes only values that have been changed in the update. If a replace value has been specified for a control then it is used instead of the current control value. There is special handling for updates of primary key values (any foreign keys in associated tables are automatically changed in order to retain the correct relationships to the primary key). If possible, the update is done by using a positioned update (current position of the cursor). If this is not possible, then a searched update is done using the current values for all controls that are bound to the primary table in the form. If the Enter null values as option was specified, then a null value is used for the bound column. If any rules have been specified for the update action, then they are evaluated before doing the update. If a rule criteria is not met, then a message is displayed and the update is not done. If the Confirm on Update option is checked, then a message box will be produced for the user to confirm the update. If the number of pending database modifications exceeds the commit scope (defaults to 1) then a commit is issued.
Back Next
Cancels the settings you have specified and returns to the previous dialog box. Accepts the settings you have specified and opens the next dialog box. This option is not available on the Actions dialog box.
Finish Skips any additional dialog boxes and creates the new form with the settings you have specified. Default settings are used for any dialog boxes you skip by clicking Finish. Cancel Closes the dialog box and cancels the creation of the form.
174
Users Guide
Decimal places Type the number of decimal places that you want displayed in the Decimal places field. This field will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Thousands separator Check the Thousands separator check box if you want numbers in this column to appear with the thousands separated with a comma. This check box will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Percentage Check the Percentage check box to display number values in this column as a percentage. This check box will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Scientific Check the Scientific check box to display number values in this column in scientific notation. This check box will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Currency Check the Currency check box to display numeric values in the column as currency. This check box will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Symbol Use this in conjunction with the currency check box to specify the currency symbol used with currency values in this column, in the Symbol field type the symbol for the currency that you want to use. This field will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Position Use this in conjunction with the currency option to specify the position of the currency symbol used with currency values. Select the position where you want the currency symbol to appear from the Position drop down list. This drop down list will only appear on the format page if you have selected Select Statement from the Get values from list, and the column that you are formatting is a numeric data type column. Locked Position Check the Locked Position check box to lock the column in position. When a column is locked in position, the locked column will not move when you scroll through the grid in your list control. You cannot have a locked column that has an unlocked column to the left of it. If you want to lock more than one column, start locking the columns with the left most column. This check box will only appear on the format page if you are working with a list control and you have selected grid view format for that control in the ListStyle section of the Property Sheet window. OK Accepts any changes to the contents of the control, and closes the dialog box.
Chapter 3. Getting started with the DB2 Table Editor Developer component
175
Cancel Closes this dialog box without changing the contents of the control.
Select Controls Displays the selected controls. OK Cancel Cancels any selections and closes the dialog box. Accepts the changes you have specified and closes the dialog box.
176
Users Guide
Description Deletes the current row from the table. This action deletes the current row from the primary table only. If any rules have been specified for the delete action, then they are evaluated before doing the delete. If a rule criteria is not met then a message is displayed and the delete is not completed. If the Confirm on Delete option is checked, then a message box will appear asking you to confirm the delete. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Displays DB2 Table Editor online help. Executes the specified command, including Refer-Back conditions. The specified command is sent to the operating system to be executed.
COMMIT
Closes the application. This action closes any open result sets, commits pending database modifications, closes all open database connections and exits DB2 Table Editor.
Chapter 3. Getting started with the DB2 Table Editor Developer component
177
Description Inserts a row into the primary table. This action takes the current values for all controls that are bound to the primary table in the form and inserts a row into the primary table for the form. If a replacement value has been specified for a control then it is used instead of the current control value. If the Enter default values as value has been specified, then the column is not included in the insert and DB2 supplies the default value. If Enter null values as value has been specified, then a null value is used for the bound column. If any rules have been specified for the insert action, they are evaluated before doing the insert. If a rule criteria is not met then a message is displayed and the insert is not completed. If the Confirm on Insert option is checked, then a message box will be produced for the user to confirm the insert. If the number of pending database modifications exceeds the commit scope (the default commit scope is 1) then a commit is issued. Launches the application that is associated with the contents of the specified control. For example, you can use this button action to launch an MP3 file displayed in a control. Select Launch control from the list, then select the desired control. If this form is run using the Java Player component as an applet, then the control is launched by passing the current value of the control to the browser.
Launch Control
178
Users Guide
SQL Verb
Description The Multiple actions button action allows you to specify more than one action for a button. When the button is clicked, the button actions will be run in the order that they are listed in the Multiple Actions dialog box. This functionality is only available in forms that are accessed using the Windows User interface. Opens another form. When you create the button, you specify the form that you want the button to open. If the form that is being opened has linked controls then the current values of the linked controls on the current form are used to populate linked controls on the form that is being opened, and a search is performed. If the specified form is already opened, it is reused. If the Close master form after opening linked form option was specified, then the master form is closed. If the Refresh form contents whenever the values for the linked controls change option was specified then the child form is synchronized with the values from the master forms linked controls. Refreshes the contents of any selected controls. To use this control, select Refresh the selected controls from the list, then select one or more controls. This action will refresh the contents of any selected controls when clicked.
Open Form
FETCH
Retrieves the next row in the table. If there are no more rows in the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections.
Chapter 3. Getting started with the DB2 Table Editor Developer component
179
Description Retrieves the previous row in the table. If you are at the beginning of the current result set, the current form values are cleared and a message is displayed indicating this. This action does not close any open result sets, commit pending database modifications or close open database connections. Reverts to the original values of this row. This action sets the form control values to the original database values. This action does not close any open result sets, commit pending database modifications or close open database connections. Runs the specified SQL statement, including Refer-Back conditions. This can be an SQL statement to update, insert or delete data from tables that are not the primary table. Stored procedures are also supported. After an SQL statement is successfully run, a message box is displayed (if this option has been set for the action), allowing the you to confirm or cancel the actions of the SQL statement. If cancel is chosen then a rollback is performed, otherwise a commit is issued.
180
Users Guide
Description Searches the table for matching rows. This action uses the current values for all bound controls to create a select statement. It will look for special character commands in all bound controls and uses them in building the search (for more information, see Using Special Command Characters in a Control). The first row that is returned is displayed in the form. A message will appear if no search results are returned. If sort conditions have been used, then the results are returned in that order. If there was already a result set opened, it is closed before performing the new search, however, any pending database modifications are not committed. If a replace value has been specified for a control, it is used instead of the current control value. If the Ignore on select option has been set for a control then the selected column is not included in the search. If the Enter null values as option is used then a null value is used for the bound column. If any rules have been specified for the search action, they are evaluated before doing the select. If a rule criteria is not met then a message is displayed and the search is not completed. If there are any LOB columns bound to controls, they are not automatically retrieved by the search.
Chapter 3. Getting started with the DB2 Table Editor Developer component
181
Action
SQL Verb
Description Updates the current row in the table. This action updates the primary table values for the current row. It includes only values that have been changed in the update. If a replace value has been specified for a control then it is used instead of the current control value. There is special handling for updates of primary key values (any foreign keys in associated tables are automatically changed in order to retain the correct relationships to the primary key). If possible, the update is done by using a positioned update (current position of the cursor). If this is not possible, then a searched update is done using the current values for all controls that are bound to the primary table in the form. If the Enter null values as option was specified, then a null value is used for the bound column. If any rules have been specified for the update action, then they are evaluated before doing the update. If a rule criteria is not met, then a message is displayed and the update is not done. If the Confirm on Update option is checked, then a message box will be produced for the user to confirm the update. If the number of pending database modifications exceeds the commit scope (defaults to 1) then a commit is issued.
182
Users Guide
Control Definition Specifies the control on the form, the contents of which will be run when the launch control is clicked by the user. Specifies the column that contains the LOBs to be displayed. This control is a display only control. Its value can be changed in the Launch LOB Applications window. To open the Launch LOB applications window, click Change. Specifies the file extension of the LOB objects that will be launched by the button. This is the Value of the File Extension field on the Launch LOB application window. This control is a display only control. Its value can be changed in the Launch LOB Applications window. To open the Launch LOB applications window, click Change. Specifies the column to which the button is mapped. This is the Value of the Mapping Control field on the Launch LOB application window. This control is a display only control. Its value can be changed in the Launch LOB Applications window. To open the Launch LOB applications window, click Change. Displays the contents of the Mapping Value table from the File Extension Values window. This control is a display only control. Its value can be changed in the Launch LOB Applications window. To open the Launch LOB applications window, click Change. Opens the Launch LOB Application window where you can change the values of the controls on this page. Lists the button actions to be associated with this button in the order in which they will be run.
Column
File Extension
Mapping control
Mapping values
Change
Multiple actions
Actions
Chapter 3. Getting started with the DB2 Table Editor Developer component
183
Button Action
Control Definition Opens the Attributes window to the Button Action page where you can select the desired button action. Allows you to change the selected button action. Removes the selected button action. Moves the selected button action up in the list. Moves the selected button action down in the list. Specifies whether the form will be opened for the server or from a file. The value of this control corresponds to the value of the Location field in the Open Form dialog box. This control is a display only control. Its value can be changed in the Open Form dialog box. To open the Open Form dialog box, click Change. Specifies the name of the form to be opened when this button is pressed. The value of this control corresponds to the value of the Form field in the Open Form dialog box. This control is a display only control. Its value can be changed in the Open Form dialog box. To open the Open Form dialog box, click Change. Specifies the options that are selected on the Open Form dialog box. This control lists the check boxes that are checked on the Open Form dialog box. This control is a display only control. Its value can be changed in the Open Form dialog box. To open the Open Form dialog box, click Change.
Form
Options
184
Users Guide
Button Action
Control Definition Lists the linked controls on the specified form. The value of this control corresponds to the value of the Linked Controls field in the Open Form dialog box. This control is a display only control. Its value can be changed in the Open Form dialog box. To open the Open Form dialog box, click Change. Opens the Open Form dialog box. From the Open Form dialog box, you can change the value of all of the fields on the Advanced page. Lists all controls on the form. Lists all selected controls on the form. The Controls in the Select Controls list will be refreshed when the button that you are defining is clicked. Moves the selected item In the Controls list to the Select Controls list. Moves the selected item In the Select Controls list to the Controls list. Moves all items In the Controls list to the Select Controls list. Moves all items In the Select Controls list to the Controls list. Contains the SQL statement to be run when the button that you are defining is clicked. Indicates that the message specified in the Message field will be displayed after the SQL statement in the Run SQL statement filed is successfully run. Tests the SQL statement in the Run SQL Statement box.
Change
SQL Statement
Test SQL
Chapter 3. Getting started with the DB2 Table Editor Developer component
185
Button Action
Control Definition Contains the message that you want to appear after the SQL statement has been successfully run. This control is only available if the Display a message after successful execution check box is checked.
OK Cancel
Click OK to apply the button attributes that you have defined and close the window. Click Cancel to close the window without saving the button attributes.
Apply Click Apply to implement the button attributes that you have defined and leave the window open.
Next Page Displays the next page of the form as it will look when printed. Prev Page Displays the previous page of the form as it will look when printed. Two Page Displays two pages of the form side-by-side as they will look when printed. The One Page button appears when you click the Two Page button. One Page Displays one page of the form as it will look when printed. The Two Page button appears when you click the One Page button. Zoom In Displays a larger view of the form as it will look when printed. Zoom Out Displays a smaller view of the form as it will look when printed. Close Closes the Print Preview window.
186
Users Guide
Collection ID Displays the collection ID for the package. Package name Displays the name of the package in which you are binding the forms SQL statements. Owner ID Displays the owner ID for the package. In order to bind the package, you must have authority at the server to execute the SQL the package will contain. Bind Options Displays the options selected for the package. Replace existing package (if one exists) When selected, replaces any existing package for the form with the current one. Keep existing authorizations on package When selected, retains permissions from the package being replaced. If this option is not selected, no permissions are assigned to the new package. OK Cancel Closes the dialog box without binding the package. Binds the package and closes the dialog box.
RDBName Specifies the DB2 database alias name. UserID Specifies the user ID with which to log in to the server (optional). Password Specifies the password with which to log in to the server (optional). FormOwner Specifies the owner of the form (optional).
Chapter 3. Getting started with the DB2 Table Editor Developer component
187
FormName Specifies the name of the form to display in the browser window (optional). OK Cancel Closes the dialog box without changing any parameter values. Accepts any changes and closes the dialog box.
188
Users Guide
Chapter 3. Getting started with the DB2 Table Editor Developer component
189
Date Format Specifies the date format used in the SQL statements in this package. ISO DB2 Table Editor Developer uses the ISO date format in any SQL statements.
Time Format Specifies the time format used in the SQL statements in this package. ISO OK Cancel Closes the dialog box without accepting any changes. Apply Accepts any changes and leaves the dialog box open. DB2 Table Editor Developer uses the ISO time format in any SQL statements.
190
Users Guide
Unspecified Uses the database default for release timing. Commit Specifies that resources are released at each commit point. Deallocate Specifies that resources are released only when the program terminates its connection to the database. OK Cancel Closes the dialog box without accepting any changes. Apply Accepts any changes and leaves the dialog box open. Accepts any changes and closes the dialog box.
Chapter 3. Getting started with the DB2 Table Editor Developer component
191
Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CLI. ODBC Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using ODBC. Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using ODBC. CPI-C Timeouts Warning Use this field to specify the number of seconds that can elapse before a user is notified and given the opportunity to cancel a communication request that has not completed. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CPI-C services. Cancel Use this field to specify the number of seconds that can elapse before DB2 Table Editor automatically cancels a communication request that has not completed and returns an error. This timeout limit applies to all database servers in the SDF to which DB2 Table Editor connects using CPI-C services. CPI-C Provider DLL The name of the DLL DB2 Table Editor uses to access CPI-C services. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
192
Users Guide
LOB Retrieval Option You use this field to specify what large object data (LOB) data you will be retrieving. This field is only available if you have permission to override LOBS. There are four choices: Disable LOB columns Select this radio button to disable LOB data retrieval. By selecting this option, you will not be able to query any table that contains LOB data. Disable LOB data retrieval Select this radio button to disable LOB data retrieval but allow access to the other columns in the tables that contain LOB data. By selecting this option, you can query tables that contain LOB data and DB2 Table Editor will return result data for all columns except those that contain LOBs. Retrieve LOB data on demand Select this radio button to specify that you will query tables that contain LOB data and you want your result data to be returned for all columns including those that contain LOB objects. However, you want to select the LOB objects that will be displayed in the contents of the query results. Unless otherwise specified, all users of DB2 Table Editor can query tables that contain LOBs. To conserve resources, DB2 Table Editor stores retrieved LOB data in a file. Pointers to the LOB data objects are displayed in the query results. Click the pointer to view the LOB object. Retrieve LOB data automatically Select this radio button to specify that you will query tables that contain LOB data and you want your result data to be returned for all columns, including those that contain LOB objects. All result data is automatically displayed in the contents of the query results. This option can potentially consume a large amount of resources and time. Maximum LOB column size Use this field to specify the maximum size of a LOB column, in kilobytes, up to 2G (the maximum LOB size). The default is 0, no maximum. If you query a table with LOB data that is larger than the maximum, the LOB data will not be returned for display. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
Chapter 3. Getting started with the DB2 Table Editor Developer component
193
Delete File Click this button to delete the existing trace file. DDM TCP When checked, applies tracing to DDM operations. When checked, applies tracing to TCP operations.
CPI-C When checked, applies tracing to CPI-C operations. CLI When checked, applies tracing to CLI operations.
Dynamic SQL When checked, applies tracing to dynamic SQL operations. Embedded SQL When checked, applies tracing to embedded SQL operations. SQLAM When checked, applies tracing to SQLAM operations. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
194
Users Guide
Message The confirmation message that appears after the SQL statement or stored procedure call is successfully executed. You can alter the default message to one that you prefer. OK Cancel Closes this dialog box without saving the SQL statement you entered. Saves the SQL statement you entered.
Automatically search for matching rows when opening a linked form Check this check box to search for matching rows when opening a linked form. If a matching row is not found the linked form is opened with only the value of the control from which the form was linked. This allows you to enter information into a table using the linked form. Refresh form contents whenever the values for the linked controls change Check this box if you want the contents of the child form to refresh automatically every time the values in the master form change. Close parent form after opening linked form Check this box to automatically close the originating form when the Open Form button is clicked and the linked form opens. Find matching rows in the linked form for the values of the linked controls Check this check box to have DB2 Table Editor search for a matching row in the child forms table and fill in the values for that row in the child form when the child form is opened. If this check box is not checked, only the value in the linked control will be filled in on the child form. Cascade child windows on screen When a child form is opened from a parent form, it will open slightly down and to the right of the parent form, or the previously opened child form, rather than opening on top of the parent form. Linked Controls Lists any current linked controls. Add Opens the Link Controls dialog box.
Delete Removes the selected link control. OK Cancel Closes the Open Form dialog box without saving the settings you entered.
Chapter 3. Getting started with the DB2 Table Editor Developer component
Saves the Open Form button settings you entered and closes the dialog box.
195
Delete Removes the selected button action from the list. Move Up Moves the selected button action up one place in the list. (Button actions are run in the order that they appear in the list) Move Down Moves the selected button action down one place in the list. (Button actions are run in the order that they appear in the list) Cancel Closes the dialog box without saving the button actions that you have selected. OK Closes the dialog box and saves the button actions that you have selected.
196
Users Guide
Show images always Specifies that objects that will be displayed in the field will always be images. Show multimedia always Specifies that objects that will be displayed in the field will always be in multimedia format. Show text always Specifies that objects that will be displayed in the field will always be in text format. Auto Recognize (or show text when format not recognized) Specifies that DB2 Table Editor will determine the format of the LOB object and display it accordingly. When the format of the object to be displayed is not recognized by DB2 Table Editor, the object will be displayed as text. If you select Auto Recognize (or show text when format not recognized), you must set format options for each LOB format on the Format page by scrolling through the Format pages for each LOB format using the arrows on the top right of the Format page. Allow external viewing and editing Check the Allow external viewing and editing check box to enable viewing and editing of LOBs using an external program such as Microsoft Paint. When this check box is checked, in the DB2 form that you are creating you can double click the LOB control and the LOB will be displayed in an external viewer. Some LOB types can be edited using the external viewer then saved back to the database if desired. Allow menu tools Check the Allow menu tools check box to allow editing of text or multimedia LOB objects using editing tools present on your machine. When editing a text object, you can select the portion of the text that you want to edit, then right click and select the appropriate editing tool from the pop-up menu.
Name column The name of a LOB column that is available to hook up to the control that you are creating. Type column The Data type of a LOB column that is available to hook up to the control that you are creating.
Chapter 3. Getting started with the DB2 Table Editor Developer component
197
must set format options for each LOB format on the Format page. To do this scroll through the Format pages for each LOB format using the arrows on the top right of the Format page.
198
Users Guide
maintaining the images proportions. If you select Best Fit, DB2 Table Editor will determine whether fit by width or fit by height is the appropriate option, then add any necessary scroll bars. Stretch Blit Mode If you selected Stretch to Fit, Fit by Width, Fit by Height, or Best Fit, from the Image Representation menu, indicate the way in which the image is to be represented. The options are as follows: Color on Color Select Color on Color mode to show your image with the least amount of noise, because all eliminated lines of pixels are deleted, however, text in images is sometimes more difficult to read with this mode. Black on White Select Black on White mode to make text in your image more readable. There may be more noise in your image display using Black on White then with Color on Color mode. White on Black Select White on Black mode to make text in your image more readable. There may be more noise in your image display using White on Black then with Color on Color mode. Half Tone To have the average color of each area of your image calculated then displayed. This results in smoother lines in an image, less pixilation and greater readability for text. Raster Operation Select the way you want your image to be displayed from the Raster Operation drop down. Display the image directly Select Displays the image directly to have your image displayed in as it is in the LOB file. Display the inverted image Select Display the inverted image to display the negative form of the images. The image in the LOB source is inverted then displayed.
Chapter 3. Getting started with the DB2 Table Editor Developer component
199
MP3 format Select MP3 format to indicate that your LOB images will be in MP3 format. WAV format Select WAV format to indicate that your LOB images will be in wave format. MDI format Select MDI format to indicate that your LOB images will be in MDI format. RMI format Select RMI format to indicate that your LOB images will be in RMI format. Control Buttons Select which play back buttons, if any, will appear in your multimedia LOB control. The options are as follows: No control button available Select No control button available to have no playback buttons displayed in your LOB control. Only Play/Stop button is available Select Only Play/Stop button is available to have only one button on your LOB control. The button would function as a play button when the Multimedia LOB is not playing, and function as a stop button when the multimedia LOB is playing. All default buttons are available Select All default buttons are available to have a Play/Stop button, a Fast Forward button, a Rewind button and a track bar which is a slider that can be used to move through your multimedia LOB. Show track bar Check the Show track bar check box to have a track bar displayed in your multimedia LOB control. The track bar is a slider that can be used to move through your multimedia LOB Show error messages Check Show error messages to have error messages shown if DB2 Table Editor encounters a problem while attempting to play your multimedia LOB. Auto play when data is retrieved Check the Auto play when data is retrieved to have your multimedia LOB start playing as soon as DB2 Table Editor has retrieved it. Rewind when finished playing Check the Rewind when finished playing check box to have the multimedia LOB rewound to the beginning and the slider bar reset when it is finished playing.
200
Users Guide
Vertical scroll bar is visible Select Vertical scroll bar is visible to have a vertical scroll bar on your LOB text control. Horizontal scroll bar is visible Select Horizontal scroll bar is visible to have both a horizontal scroll bar on your LOB text control. None Select None to have no scroll bars on your LOB text control.
Default Alignment Select what the default alignment will be for the text in your LOB control from the Default alignment menu. The options are as follows: Left Aligned Select Left aligned to have the text in your LOB control aligned to the left side of the LOB text area. Right Aligned Select Right aligned to have the text in your LOB control aligned to the right side of the LOB text area. Centered Select Centered to have the text in your LOB control centered in the LOB text area. Replace unprintable characters with dots Check the Replace unprintable characters with dots check box to have any characters that DB2 Table Editor cannot print replaced by dots. This will allow LOB text that would not be displayed by DB2 Table Editor to be displayed with the unrecognized characters replaced by dots. Read only Check the Read only check box to prevent users from editing the LOB text that is displayed in the LOB text control.
Name column The name of a LOB columns that are available to hook up to the control that you are creating. Type column The data type of a LOB columns that are available to hook up to the control that you are creating.
201
File Extension Select the File Extension radio button to specify the file extension of the LOB objects that will be launched by the button. To specify the file extension, type the file extension in the field or select it from the drop-down list. Mapping Control Select the Mapping Control radio button to specify the column to which you want the button mapped. Select the column to which you want the button mapped from the drop-down list. Columns If you are working with a multi-column control, click the Columns button to select a specific column to be mapped. Mapping Click the Mapping button to Map the file extensions of the selected LOB column to the mapping value using the File Extension Mapping window.
202
Users Guide
Form Name The Form Name column indicates the location where the form is stored. Next Click Next to move to the next step in the migration process. The Servers or Statements window opens when you click Next.
Finish The Finish button is not available from the Forms dialog box. Cancel Click Cancel to exit the Forms window without migrating any forms.
Remove Click Remove to remove the selected item from the Server Links list. Remove All Click Remove All to remove all of the items from the Server Links list Back Next Click Back to go back to the Forms window. Click Next to move to the next step in the migration process. The Tables window opens when you click Next.
Finish The Finish button is not available from the Servers or Statements dialog box. Cancel Click Cancel to exit the Servers window without migrating any forms.
Chapter 3. Getting started with the DB2 Table Editor Developer component
203
Server Link Select the origin and destination server pair for the form that you are migrating form the Server Link drop down. Origin table Select the table that your form currently uses from the Origin table drop-down. Destination table Definition Term Select the table that you want your migrated form to access, from the Destination table drop-down.
Table links The Table links list contains the origin and destination table pairs for your form that you are migrating. Origin Table The server that the form currently accesses is listed in the Origin Table column. Destination Table The table that the migrated form will access, is listed in the Destination Table column. Add Click Add to add the selections from the Origin table and Destination table drop-down lists to the Table links list.
Remove Click Remove to remove the selected item from the Server Links list. Remove All Click Remove All to remove all of the items from the Server Links list. Back Next Click Back to go back to the Servers window. Click Next to move to the next step in the migration process. The Tables window opens when you click Next.
Finish Click Finish to migrate your form. Cancel Click Cancel to exit the Tables window without migrating any forms.
204
Users Guide
Rollback Click Rollback to rollback the changes that you made to your select statement in the Select Statement box. Back Next Click Back to go back to the Tables window. Click Next to move to the next step in the migration process. The Tables window opens when you click Next.
Finish The Finish button is not available from the Servers dialog box. Cancel Click Cancel to exit the Servers window without migrating any forms.
Chapter 3. Getting started with the DB2 Table Editor Developer component
205
206
Users Guide
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
Before working with DB2 Table Editor component, you must specify the server definition file (SDF) that you want to use. Use the DB2 Table Editor Windows User component and Java Player component to work with DB2 Table Editor forms created in the DB2 Table Editor Developer component, or to create forms as you go. DB2 Table Editor provides robust table editing operations, including the ability to: v Edit tables on multiple DB2 database platforms Maintain referential integrity while performing inserts, updates and deletes v Quickly search for, and locate specific rows, filter the rows that are displayed, or immediately jump to tables of related data v Update primary keys v Commit accumulated data changes at the end of a session, and use find-and-replace for large-scale changes v Save the specifications of a table editing session (such as row filtering) and call up the same table-editing layout in the future v Edit with the standard DB2 Table Editor interface, or create prototype forms in seconds with the form building wizard v Easily locate and launch previously saved DB2-based forms, including from links in Web pages or e-mail messages (using DB2 Table Editor Java Player) v Launch the standard DB2 Table Editor interface from the DB2 Export Facility, DB2 Web Query, or DB2 Control Center v Access large objects in DB2 databases The DB2 Table Editor Java player is a DB2 JDBC application that requires the use of the DB2 Universal Database JDBC drivers, either the application driver when running as a Java application, or the network driver when running as a Java applet. The primary difference between the application version and applet version is that the application requires the DB2 Client Application Enabler (CAE) to be installed on the client, and uses the CAE to communicate with DB2, while the applet depends on a Java-enabled Web browser, and does not require any DB2 code installed on the client.
207
Calls to JDBC are translated to calls to DB2 CLI, through Java native methods. This dependency requires that the DB2 Client Application Enabler (CAE) component be installed on the client, and is then used by the DB2 Table Editor Java Player to communicate with DB2 via the DB2 UNIVERSAL DATABASE JDBC application driver. A JDBC request flows through DB2 CLI to the DB2 server through the normal CAE communication flow. The DB2 database you want to connect to must therefore be defined in the CAE. You must configure your network infrastructure to support this communications model. DB2 Table Editor Product Support cannot provide support for configuring your network infrastructure.
208
Users Guide
Note: Server definition files must be set up for the servers that you want to access using DB2 Table Editor before you can access these servers using the DB2 Table Editor Developer component, DB2 Table Editor component, or Java Player component. Use the DB2 Table Editor Console component to setup server definition files. Related concepts Installing DB2 Table Editor Java Player on page 213
Advanced installation
After you complete the initial installation of DB2 Table Editor, you are ready to install it on other machines. To make this process more efficient, DB2 Table Editor is able to perform a variety of server and unattended installations. You can pre-define user options by modifying the server definition file, or the CPIC Provider DLL. Related concepts File server installation on page 211 Configuring DB2 Table Editor on page 212 Related tasks Configuring for Unattended Installation You can setup an unattended installation of DB2 Table Editor with predefined user options. An unattended installation allows you to select the installation options for your DB2 Table Editor users before beginning the installation process. This will prevent you from needing to install and configure each instance if DB2 Table Editor individually.
209
d. Save options file on Disk1. After you edit and save the appropriate predefinition file, copy it to Disk1 of the DB2 Table Editor installation diskettes or installation media. 3. Open the file named setup.ini, located in the Disk1 directory in the DB2 Table Editor installation directories that you copied to your hard drive in step one. 4. Edit setup.ini as to set the configuration options as desired. The variables that can be set are listed in the following table (Variables ):
Table 7. Variables [Options] AutoInstall= Possible Settings 0,1 Effect Specify 1 to perform an unattended installation. All other settings in setup.ini are ignored if this parameter is set to 0. Specifies whether DB2 Table Editor is already installed on a file server. If the setting is 0, all DB2 Table Editor files are installed to the directory specified in the InstallPath variable. If the setting is 1, DB2 Table Editor must be previously installed into the directory specified in the InstallPath variable. Specifies the type of installation to perform. v 0 indicates a typical installation v 1 indicates a compact installation v 2 indicates a custom installation If you select 2, you must indicate which components to install. Note: Option 2, the custom installation, is strongly recommended. Most users do not require the Console and Developer components, and the custom installation lets the system administrator give the user the most efficient installation possible. InstallPath= <directory> Specifies the directory that will receive the DB2 Table Editor installation (if FileServerInstall=0) or the file server directory that already contains the installation (if FileServerInstall=1). <program group name> 0,1 Specifies the name of the program group that will be created (under Program Manager) or the program folder that will be created (for the Windows NT, 2000, and XP Start menu). Specifies whether to install the DB2 Table Editor Console component program files. If FileServerInstall=1, files are not copies to the local machine, but program group icons are still created. Always set this option to 0 for user installations. Specifies whether to install the main DB2 Table Editor Developer component program files. If FileServerInstall=1, files are not copied to the local machine, but program group icons are still created.
FileServerInstall=
0,1
SetupType=
0,1,2
ProgramGroup=
Admin=
Developer=
0,1
For Example:
210
Users Guide
[Options] AutoInstall=1 FileServerInstall=0 SetupType=0 InstallPath=C:\Program Files\DB2 Table Editor ProgramGroup=DB2 Table Editor
This sample setup.ini file specifies an unattended installation. This sample file would produce a typical installation with files copied to the C:\Program Files\DB2 Table Editor directory, and a program group or program folder created named DB2 Table Editor. 5. Save setup.ini to the Disk1 in the DB2 Table Editor installation directories that you copied to your hard drive in step one. 6. Run the installation from the source diskettes or server. The installation proceeds automatically. Related concepts Advanced installation on page 209 File server installation Configuring DB2 Table Editor on page 212
To achieve a server installation, you must first install DB2 Table Editor on a server, then on the client machines.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
211
This setup.ini file specifies an unattended installation, where files have already been installed on a file server, in the f:\DB2Forms directory. A custom installation will be performed, installing icons for the main DB2 Table Editor Developer component files, but not the DB2 Table Editor Console component program files. A program group or program folder named DB2 Table Editor is created, with icons referring to the f:\DB2Forms directory. 3. Run the DB2 Table Editor installation from the source diskettes or server. The installation proceeds automatically. Related concepts Advanced installation on page 209 Configuring DB2 Table Editor Related tasks Configuring for Unattended Installation on page 209 You can setup an unattended installation of DB2 Table Editor with predefined user options. An unattended installation allows you to select the installation options for your DB2 Table Editor users before beginning the installation process. This will prevent you from needing to install and configure each instance if DB2 Table Editor individually.
212
Users Guide
2. In the Options notebook, click the General tab. 3. On the General page, in the Server definition file field, type the SDF name, or navigate to the location of the SDF that you want to use and select the file using the ... button. Note: The default location for the server definition file on Windows 2000 is the WINNT directory. 4. Click OK. The Options notebook closes. The server definition file that you selected will be used for both the Developer and DB2 Table Editor components of DB2 Table Editor on your machine. Related concepts Configuring DB2 Table Editor on page 212 Related tasks Changing the SDF to be used by the Developer or DB2 Table Editor Windows User component Changing the SDF to be used by the Developer or DB2 Table Editor Windows User component: 1. In the Developer or Windows User component, select View --> Options. The Options notebook opens. 2. In the Options notebook, click the General tab. 3. On the General page, in the Server definition file field, type the SDF name, or navigate to the location of the SDF that you want to use and select the file using the ... button. Note: The default location for the server definition file on Windows NT and Windows 2000 is the WINNT directory. 4. Click OK. The Options window closes. 5. The servers that are defined in the SDF that you selected now appear in your server list. Related concepts Configuring DB2 Table Editor on page 212 Related tasks Specifying the SDF to be used by the Developer or DB2 Table Editor Windows User component on page 212
213
installed at the client; DB2 Table Editor Java Player uses the CAE to communicate with DB2. A JDBC request flows through DB2 CLI to the DB2 server through the normal CAE communication flow. Your network infrastructure must be configured to support this communications model. DB2 Table Editor Product Support cannot provide support for configuring your network infrastructure. Requirement: In order to work with DB2 V8 data, the Java Runtime Environment (JRE) v1.3.1 is required. The installation steps differ depending on the database to which you want to connect, and whether you have chosen to install it as an applet or as an application. Related concepts Command Line Parameters on page 221 Related tasks To install DB2 Table Editor: on page 208 Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases Installing DB2 Table Editor Java Player as an applet when working with DB2 databases on page 215 Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 218 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 219
Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases
To run DB2 Table Editor Java Player as an application on a client machine, install the Java interpreter, or Java Virtual Machine (JVM), as well as the JDBC driver on the client machine. The JDBC driver is included with the DB2 Client Application Enabler. The DB2 Table Editor application does not include these components. 1. Install the Java interpreter (version 1.1 or higher). 2. Install the DB2 CAE, including the JDBC driver. The JDBC driver file name is db2java.zip. 3. Install DB2 Table Editor according to the installation instructions. The files required for DB2 Table Editor Java Player will be installed automatically. These files are: v db2forms.jar - Class file for the DB2 Table Editor Java Player application v One or more of the following license files. dbehost.lic dbewrkgp.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) 4. Create a desktop shortcut to access the application. Create a new shortcut with the following target command line:
"x:\<location_of_java.exe>\java.exe" -cp "x:\<location_of_db2java.zip>\db2java.zip";"x:\ <location_of_db2forms.jar>\db2forms.jar" com.rocketsoftware.juser.DB2Forms
214
Users Guide
Where x:\<location_of_db2java.zip> specifies the location of the IBM DB2 JDBC driver that was installed as part of the DB2 CAE, and x:\<location_of_db2forms.jar> specifies the location of the DB2 Table Editor classes that were installed with DB2 Table Editor. For example:
"C:\Program Files\SQLLIB\java\jre\bin\java.exe" -cp "C:\Program Files\SQLLIB\java \db2java.zip";"C:\DB2 Table Editor\db2forms.jar" com.rocketsoftware.juser.DB2Forms
Related concepts Command Line Parameters on page 221 Installing DB2 Table Editor Java Player on page 213 Related tasks Installing DB2 Table Editor Java Player as an applet when working with DB2 databases Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 218 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 219
Installing DB2 Table Editor Java Player as an applet when working with DB2 databases
To run the DB2 Table Editor Java Player, or an individual DB2 Table Editor form, as an applet, you must install a web browser that is enabled for Java 1.1 or greater on the client machine. You must install and configure a web server, and establish connectivity between the web server and client via HTTP and TCP/IP protocols. You must then install the DB2 database infrastructure, as well as the DB2 UNIVERSAL DATABASE JDBC driver, on the same host machine as the web server. To connect to some remote DB2 systems, like DB2 on the OS/390 platform, DB2 Connect or DB2 DataJoiner may be required on the web server machine to access the database. DB2 Table Editor does not include these components. 1. On the client machine, Install a web browser enabled for Java 1.1 or greater. 2. On the host machine, install and configure a web server, and establish connectivity between the web server and client machine via HTTP and TCP/IP protocols. 3. Install the DB2 database infrastructure on the same host machine as the web server. DB2 includes the JDBC driver; the file is named db2java.zip. 4. Install DB2 Table Editor according to the installation instructions on any DB2 Table Editor compatible machine. You will copy the DB2 Table Editor Java Player program files from this machine to your web server. Note: The file that is required for DB2 Table Editor Java Player will be installed automatically when you install DB2 Table Editor. This file is: v db2forms.jar - Class file for the DB2 Table Editor Java Player application. 5. Copy the following files and directories to the home directory on your web server: v db2forms.jar v db2java.zip v One or more of the following license files. dbehost.lic dbewrkgp.lic
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
215
dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. v db2jcc.jar (copy this file only if you are connecting to DB2 Version 8. The Home Directory is the directory where any HTML files containing a DB2 Table Editor applet will reside. This is the directory where your HTTP Server serves files from. This directory structure must be followed for DB2 Table Editor Java Player to function properly as an applet. 6. To run a DB2 Table Editor form via an applet, use DB2 Table Editor Developer to create a form. Then, in DB2 Table Editor developer, automatically generate an HTML file with the embedded applet tags for the form. You can create your own custom HTML file containing the following applet tag and parameters: If you are connecting to DB2 Version 7 databases the HTML must be as follows:
<applet code = "DB2FormsApplet.class" width=N height=N align="Position_of_form" archive="db2forms.jar,db2java.zip"> <param name=HostName value=Name_of_host> <param name=Port value=Port_number> <param name=RDBName value=RDB_name> <param name=UserID value=ID_of_user> <param name=Password value=Password_of_user> <param name=FormOwner value=owner_of_form> <param name=FormName value=name_of_form> <param name="bgColor" VALUE="FFFFFF"> </applet>
If you are connecting to a DB2 Version 8 database, the HTML must be as follows:
<applet code = "DB2FormsApplet.class" width=N height=N align="Position_of_form" archive="db2forms.jar,db2java.zip,db2jcc.jar"> <param name=HostName value=Name_of_host> <param name=Port value=Port_number> <param name=RDBName value=RDB_name> <param name=UserID value=ID_of_user> <param name=Password value=Password_of_user> <param name=FormOwner value=owner_of_form> <param name=FormName value=name_of_form> <param name="bgColor" VALUE="FFFFFF"> </applet>
Where: v Width - Specifies the applet display width in the browser window, in pixels. v Height - Specifies the applet display height in the browser window, in pixels. v Align - Specifies the applet display alignment in the browser window, as center, left, or right. v HostName - Specifies the name of the HTTP server from which the JAVA applet will run. v Port - Specifies the port number that the JDBC applet server is listening on. v RDBName - Specifies the DB2 database alias name.
216
Users Guide
v UserID - Specifies the user ID with which to log in to the server (optional). v Password - Specifies the password with which to log in to the server (optional). v FormOwner - Specifies the owner of the form. v FormName - Specifies the name of the form to display in the browser window. v bgColor - Specifies the background color for the applet. Note: Make sure that the location that is specified in the applet for the JDBC driver, db2java.zip, is correct. If the JDBC driver file is not located in the same directory as the HTML file containing this applet, the applet attribute archive must reflect the correct location of db2java.zip. If necessary, edit the applet attribute archive to reflect the location of the JDBC driver, or copy db2java.zip to the same directory as the HTML file. If you are connecting to an Informix database, the HTML must be as follows:
<applet code = "DB2FormsApplet.class" width=N height=N align="Position_of_form" archive="db2forms.jar, ifxjdbc.jar"> <param name=HostName value=Name_of_host> <param name=Informix_host value= <host name> > <param name=Informix_port value= <port number> > <param name=Informix_Database value= <database name> > <param name=Informix_Server value= <server name > > <param name=UserID value=ID_of_user> <param name=Password value=Password_of_user> </applet>
Where: v Width - Specifies the applet display width in the browser window, in pixels. v Height - Specifies the applet display height in the browser window, in pixels. v Align - Specifies the applet display alignment in the browser window, as center, left, or right. v HostName - Specifies the name of the HTTP server from which the JAVA applet will run. v Informix_host Specifies the name of the http server from which the JAVA applet will run. v Informix_port - Specifies the port number that the JDBC applet server is listening on. v Informix_Database - Specifies the name of the Informix database to which you want to connect. v Informix_Server - Specifies the name of the Informix server from which the JDBC applet will run. v UserID - Specifies the user ID with which to log in to the server (optional). v Password - Specifies the password with which to log in to the server (optional). Information: When you are connecting to an Informix database server, the Informix server must be on the same machine as your Web server. 7. Install the HTML file that contains the DB2 Table Editor applet tags in the same directory as db2forms.jar, db2java.zip, db2jcc.jar (for DB2 V8 databases), and the license file:
Home Directory db2forms.jar
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
217
db2java.zip
Where <name_of_file> is the name of the HTML file containing the DB2 Table Editor applet tags. 8. Open the URL that is used to connect to the DB2 Table Editor Java player. The URL is as follows: http://<http server>/<path>/xxx.html Where HTTP server is the name of your HTTP server, <path>/xxx.html is the path to and name of the HTML file that contains the applet parameters that are used to open the form. You can open the HTML file from any web browser enabled for Java 1.1, and run the DB2 Table Editor Java Player application, or DB2 Table Editor form. Related concepts Command Line Parameters on page 221 Installing DB2 Table Editor Java Player on page 213 Related tasks Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases on page 214 Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 219
Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases
To run DB2 Table Editor Java Player as an application on a client machine, install the Java interpreter, or Java Virtual Machine (JVM), as well as the Informix JDBC driver on the client machine. The DB2 Table Editor application does not include these components. The most recent version of the Informix JDBC driver is available for download form http://www.informix.com 1. Install the Java interpreter (version 1.1 or higher). 2. InstallDB2 Table Editor according to the installation instructions. For instructions on installing DB2 Table Editor, see: Installing DB2 Table Editors Graphical User Interface. The files that are required for DB2 Table Editor Java Player will be installed automatically. These files are: v db2forms.jar - Class file for the DB2 Table Editor Java Player application v One or more of the following license files. dbehost.lic dbewrkgp.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) 3. Create a desktop shortcut to access the application. Create a new shortcut with the following target command line:
"x:\<location_of_java.exe>\java.exe" -cp "x:\<location_of_ifxjdbc.jar>\ifxjdbc.jar"; "x:\<location_of_db2forms.jar>\db2forms.jar" DB2Forms
218
Users Guide
Where: v x:\<location_of_ifxjdbc.jar> specifies the location of the Informix JDBC diver on your machine v x:\<location_of_db2forms.jar> specifies the location of the DB2 Table Editor classes that were installed with DB2 Table Editor. For Example:
C:\j2sdk1.4.2\bin\java.exe -cp C:\informix\lib\ifxjdbc.jar";" C:\DB2 Table Editor\db2forms.jar " DB2Forms
Related concepts Command Line Parameters on page 221 Installing DB2 Table Editor Java Player on page 213 Related tasks Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases on page 214 Installing DB2 Table Editor Java Player as an applet when working with DB2 databases on page 215 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases
Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases
To run the DB2 Table Editor Java Player, or an individual DB2 Table Editor form, as an applet, you must install a web browser that is enabled for Java 1.1 or greater on the client machine. 1. Install a web browser enabled for Java 1.1 or greater. 2. On the machine where the Informix database is located, install and configure a web server. 3. Install DB2 Table Editor according to the installation instructions on any DB2 Table Editor compatible machine. You will copy the DB2 Table Editor Java Player program files from this machine to your web server. Note: The files that are required for DB2 Table Editor Java Player will be installed automatically when you install DB2 Table Editor. These files are: v db2forms.jar - Class file for the DB2 Table Editor Java Player application. v The HtmlHelp directory - HTML help files for the DB2 Table Editor Java Player application. 4. Copy the following files and directories to the home directory on your web server: v db2forms.jar v ifxjdbc.jar v One or more of the following license files. dbehost.lic dbewrkgp.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor)
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
219
You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. The Home Directory is the directory where any HTML files containing a DB2 Table Editor applet will reside. This is the directory where your HTTP Server serves files from. This directory structure must be followed for DB2 Table Editor Java Player to function properly as an applet. 5. To run a DB2 Table Editor form as an applet, use DB2 Table Editor Developer to create a form. Then, in DB2 Table Editor developer, automatically generate an HTML file with the embedded applet tags for the form. You can create your own custom HTML file containing the following applet tag and parameters:
<applet code = "DB2FormsApplet.class" width=N height=N align="Position_of_form" archive="db2forms.jar, ifxjdbc.jar"> <param name=Informix_host value= <host name> > <param name=Informix_port value= <port number> > <param name=Informix_Database value= <database name> > <param name=Informix_Server value= <server name > > <param name=UserID value=ID_of_user> <param name=Password value=Password_of_user> </applet>
Where: v Width - Specifies the applet display width in the browser window, in pixels. v Height - Specifies the applet display height in the browser window, in pixels. v Align - Specifies the applet display alignment in the browser window, as center, left, or right. v Informix_host Specifies the name of the http server from which the JAVA applet will run. v Informix_port - Specifies the port number that the JDBC applet server is listening on. v Informix_Database - Specifies the name of the Informix database to which you want to connect. v Informix_Server - Specifies the name of the Informix server from which the JDBC applet will run. v UserID - Specifies the user ID with which to log in to the server (optional). v Password - Specifies the password with which to log in to the server (optional). Requirement: When you are connecting to an Informix database server, the Informix server must be on the same machine as your Web server. 6. Install the HTML file that contains the DB2 Table Editor applet tags in the same directory as db2forms.jar, ifxjdbc.jar, the license file, and the HtmlHelp directory:
Home Directory db2forms.jar <name_of_file>.html <License file>.lic ifxjdbc.jar HtmlHelp Directory
Where <name_of_file> is the name of the HTML file containing the DB2 Table Editor applet tags.
220
Users Guide
7. Open the URL that is used to connect to the DB2 Table Editor Java player. The URL is as follows: http://<http server>/<path>/xxx.html Where HTTP server is the name of your HTTP server, <path>/xxx.html is the path to and name of the HTML file that contains the applet parameters that are used to open the form. You can open the HTML file from any web browser enabled for Java 1.1, and run the DB2 Table Editor Java Player application, or DB2 Table Editor form. Related concepts Command Line Parameters Installing DB2 Table Editor Java Player on page 213 Related tasks Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases on page 214 Installing DB2 Table Editor Java Player as an applet when working with DB2 databases on page 215 Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 218
/IFormName:formname
/IFormFile:formfile
/IUserID:userID
/IPassword:password
Note: The /IPassword parameter includes the users password in plain text. For example, the following string would pass the Server, the UserID, and the Password parameters to the database when DB2 Table Editor is launched:
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
221
Related concepts Installing DB2 Table Editor Java Player on page 213 Related tasks Installing DB2 Table Editor Java Player as an application on a client machine when working with DB2 databases on page 214 Installing DB2 Table Editor Java Player as an applet when working with DB2 databases on page 215 Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 218 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 219
Connecting to an Informix Database using the DB2 Table Editor Java Player component
You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Note: You must use the Informix JDBC driver installed on your machine in order to connect to an Informix database. 1. Ensure that the path to the Informix JDBC diver is added to the path of your shortcut to the DB2 Table Editor Java Player Component. 2. Open the Set Database window by selecting View --> Set Server. 3. Select the Informix radio button to specify that you will be accessing an Informix database server. 4. In the Database Server box, select the database server to which you want to connect. 5. In the Host name or IP address field specify the host name or IP address of the database server to which you want to connect.
222
Users Guide
6. In the Port Number field, specify the port number for the database server to which you want to connect. 7. In the Database Name field, specify the name of the database to which you want to connect. 8. Click OK.
File Menu
Open opens an existing form on your local machine. Open From Server opens a form from the database server. Close closes the active form. Edit Table automatically creates a new form for a table. Print opens the Print dialog box and print the active form.
Exit closes the DB2 Table Editor Java Player application. Related reference Edit Menu View Menu on page 224 Help Menu on page 225 Table Layout Edit Popup Menus on page 225
Edit Menu
The Edit Menu is available in Form Layout mode. The Edit Menu in Table Layout mode displays the Table Layout Edit Popup Menu for the currently selected element. Cut Copy Removes the selected item from the active document and place it on the Clipboard, replacing the current contents of the Clipboard. Copies the selected item and place it on the Clipboard, replacing the current contents of the Clipboard.
Paste Inserts the contents of the Clipboard at the insertion point, replacing any selection. Delete Deletes the contents of the cell. Zoom Opens the Zoom dialog box. Launch Opens the contents of the control in the appropriate Windows application. View/Edit LOB Opens the Column LOB Type Associations dialog box in order to view or edit the selected LOB. Related reference File Menu View Menu on page 224 Help Menu on page 225 Table Layout Edit Popup Menus on page 225
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
223
View Menu
Toolbar Displays or hide the DB2 Table Editor Toolbar. Status Bar Displays or hide the DB2 Table Editor status bar. Grid Options Selects from the following possible actions that can be applied to the grid: Grid Lines On/Off Displays or hides the grid lines on the grid. Row Headers Displays or hides the row headers on the grid. Header Font Changes the header font in the grid. Data Font Changes the font used to display the data in the grid. Refresh Refreshes the cell contents in the grid. Typing replaces selection Turns on or off the type over feature. When Typing replaces selection is turned on, when you type in the cells of the grid, the data that is currently in the cell will be replaced. Validate character data length Turns on or off the Validate character data length feature. When this feature is turned on, the length of the character data that is typed into cells will be validated against the maximum allowable data length that is specified for that row in the DB2 Table. For example if the data type for a row is Char(5) then only 5 characters will be allowed in that row. Set Current SQLID Sets the current SQLID using the Set Current SQLID dialog box. Set User Information Sets your database server user ID, password, and accounting string for the active form. Note: DB2 Table Editor Java Player will not save the user ID, password, or accounting string you specify here after you have closed the application. Options Displays the Options dialog box and set options for DB2 Table Editor Java Player. Note: DB2 Table Editor Java Player will not save the configuration options you specify here after you have closed the application. Related reference File Menu on page 223 Edit Menu on page 223 Help Menu on page 225 Table Layout Edit Popup Menus on page 225
224
Users Guide
Help Menu
Help Topics Displays the DB2 Table Editor Java Player online help facility. About DB2 Table Editor Java Player Displays the version number of this DB2 Table Editor Java Player software, and copyright and trademark information. Related reference File Menu on page 223 Edit Menu on page 223 View Menu on page 224 Table Layout Edit Popup Menus
Replace Replaces the specified value in the table with a new value. Launch Executes the value of the selected cell, if the value is a valid file or application name. Variables Opens the Grid Variables window where you can set variables for use in formulas in the grid. This option is only available in the DB2 Table Editor Windows User component. View/Edit LOB Opens the Column LOB Type Associations dialog box in order to view or edit the selected LOB. Edit Related Opens the Edit Table wizard with the data filled in to generate a table layout form for the table related to the primary key you have selected.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
225
226
Users Guide
Edit Related Opens the Edit Table wizard with the data filled in to generate a table layout form for the table related to the primary key you have selected. Related reference File Menu on page 223 Edit Menu on page 223 View Menu on page 224 Help Menu on page 225
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
227
the LOB in the File Extension field and click the Browse button and browse until you find the executable file for the application with which you want to view and edit the LOB. v To indicate which application will be used to view and edit the LOB via the mapping column, select the Mapping Column radio button. Select the desired mapping column from the drop-down list then click the Mapping button. The File Extension Mapping dialog box opens. Select the file extensions for the formats listed in the column from the LOB Type Associations window. This option is only available for forms that contain a mapping column. 4. Optional: Save the options on the form by selecting File --> Save at Server. Note: The column LOB associations information, including mapping if it has been used, is saved when the form is saved. The next time the form is opened this information will be used. 5. Click OK. The appropriate application launches with the selected LOB open for viewing or editing. Note: Once you have indicated the appropriate application, on subsequent attempts to view the LOB you can simply double click the LOB in order to view it. If you want to change the application that is used to open the LOB, Hold down the shift key, then right click the LOB that you want to view and select View/Edit LOB. The Column LOB Type Associations dialog box opens and you can change your selection. Related concepts Working with LOBs (Large Objects) on page 227
Editing a tables
One of the most powerful features in DB2 Table Editor is the ability to create forms to edit tables in the database. When you use the Edit Table feature, you create a form to insert, update, and delete records from a table in a database (based on your particular privileges). These forms include the ability to update primary keys. When you create a form, you specify a Primary Table. the primary table for each form is that table that will be updated with insert, update and delete actions. The specifications for these forms can be saved using the DB2 Table Editor component application for reuse by the Windows or Java application. You can use the wizard to automatically create a new form for a table. You can then use this form to search and edit the table. You can edit tables in form mode and in table layout mode. Both modes use a wizard to give you full access to the data within one table. Both traditional forms and full-screen edit forms can be saved locally and at a database server. Once saved, these forms can be opened and edited at a later time.
Form mode
Form mode uses a wizard to create a form that is designed to edit the table that you select. The wizard dynamically builds the controls and columns that are displayed in the form based on the selections that you make. Changes are committed when you click the Update, Insert, or Delete buttons.
228
Users Guide
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
229
12. Click the Add button that is adjacent to the Sort Conditions box. The Sort Condition window opens.Select the column or columns from the list, on which you want your data sorted. 13. Select the column or columns from the list, on which you want your data sorted. 14. In the Sort Direction box, specify whether you want your data to be sorted in ascending or descending order. 15. Click Add. the Sort Condition window closes. 16. If you selected the Table Layout format in step 6, select a Save Mode from the Save Mode box. Note: The On Leave Row save mode sends changes you make to DB2 every time you click outside a row you have made changes to. The At End save mode sends changes you make to DB2 when you are finished with all edits to the form. 17. If you selected the At End save mode in step 16, select a Lock Table option from the Lock Table box. The options are as follows: v Select No to edit the table without locking it. v Select Shared to prevent other applications from performing any but read-only operations on the table while you are editing it. v Select Exclusive to prevent concurrent applications from performing any operations on the table. 18. Click Finish. The form or table appears in the DB2 Table Editor component main window. You can now use the form to search and edit the table. Related concepts Editing a tables on page 228 Working with primary keys Working with Rows on page 231 Working with Columns on page 233 Working with Cells on page 233
Primary keys and the Edit Related option for full-screen edit forms
Edit Related is an option for full-screen edit forms when there is a primary key included on the form that has dependent tables. If this is the case, using the full-screen edit pop-up menu produces a menu that includes the Edit Related option. When Edit Related is selected, DB2 Table Editor first checks to see if there is more than one related table. If so, it produces a list of tables to choose from. You can select the related table that they wish to edit. This dialog is not shown if there is only one related table. The Edit Table wizard is then displayed for the related table and will produce a new form for the related table when the Finish button is clicked.
230
Users Guide
If the Edit Related option was invoked when either a cell or row was selected, then the Edit wizard dialog for the related table is automatically populated with row conditions for the row/cell values that were selected. Related concepts Editing a tables on page 228 Working with Rows Working with Columns on page 233 Working with Cells on page 233 Related tasks To create a new form using the Edit Table feature: on page 229
Inserting a row
You can insert a new row into a table from the Table Editor. Note: The Primary table for the form will be updated.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
231
Updating a row
You can update a row from the Table Editor. Note: The Primary table for the form will be updated.
Deleting a row
You can delete a row from a DB2 table using the Table Editor. Note: The Primary table for the form will be updated.
232
Users Guide
Related concepts Working with Rows on page 231 Inserting a row on page 231 Updating a row on page 232
233
Related concepts Editing a tables on page 228 Working with primary keys on page 230 Working with Rows on page 231 Working with Columns on page 233 Related tasks To create a new form using the Edit Table feature: on page 229
Opening a form
You need to open a form in order to use DB2 Table Editor. Forms may be saved on your computer or on a server.
To open a form that is stored on a server using DB2 Table Editor for Windows:
1. 2. 3. 4. 5. Select File --> Open from server. The Open From Server window opens. From the Server list, select the server name where your from is stored. If you know the owner name, enter it in the Owner field. If you know the name of the form, enter it in the Name field. Click the List button. A list of forms, that match the criteria that you specified, opens in the Object List window. Note: The percent sign (%) acts as a wildcard symbol. Enter the percent sign in the Owner and Name fields to return forms with any Owner, or with any Name. 6. From the Object List window, select the form that you want to use. Click OK. The selected form opens.
To open a form that is stored on a server from DB2 Table Editor Java Player component:
1. Select File --> Open from server. The Open From Server window opens. Note: If the server is provided as a command line parameter, DB2 Table Editor uses this server as a default, and the Set Server Dialog Box does not display. 2. Specify the database where the form that you want to access is stored, and click OK. The Open From Server window opens. 3. Specify the owner and name of the form that you want to open, and click List.
234
Users Guide
Note: If you do not know the owner or name of the form, enter the wildcard symbol %, and click List. 4. Enter your User ID and Password if prompted, and click OK. The Object List dialog window opens, containing a list of forms. 5. Select the form that you want to open, and click OK. The form opens.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
235
Validate character data length Check the Validate character data length check box to have the length of character data checked against the allowable data length for the character data length of the column. This control is only available when workign with the DB2 Table Editor Java Player component. OK Cancel Closes this dialog box without saving the options you entered. Closes this dialog box and saves the options you entered.
Main Window
This window is displayed when you start DB2 Table Editor Java Player component or DB2 Table Editor Windows user component. The main window displays the DB2 Table Editor forms that you use to create and edit data that is stored on a database server.
Form Window
This window is displayed when you open a DB2 Table Editor form. The form window is the space that contains a form.
236
Users Guide
Password The password for the user ID that you entered. Note: You must specify a valid user ID and password for the database server you are trying to access, not a local or LAN user ID and password. Case is preserved in the user ID and password you enter, i.e., if your user ID or password is uppercase, you must enter it in uppercase. Some types of database servers treat user IDs and passwords as case sensitive; others do not. Change Displays the New password and Confirm new password fields, and the Hide button. This control is only available when using the DB2 Table Editor Windows User component. New password Type the new password you want to use for the database server. This control is only available when using the DB2 Table Editor Windows User component. Note: Specifying a new password will change your network password for the server to which you are connected. For security reasons, not all networks and servers allow DB2 Table Editor to change a user password. Contact your system administrator to learn whether you can change your password through DB2 Table Editor. Confirm new password The confirmation of the new password you want to use for the database server. This control is only available when using the DB2 Table Editor Windows User component. Hide Hides the New password and Confirm new password fields. This control is only available when using the DB2 Table Editor Windows User component.
Remember this password? Saves your password. When you are prompted by DB2 Table Editor for a user ID and password, this password will be filled in automatically. This control is only available when using the DB2 Table Editor Windows User component. Account The string specifying accounting information to send to the database server when connecting. The database server uses the account to track system usage. Contact your database administrator to learn whether your system uses accounts. This control is only available when using the DB2 Table Editor Windows User component. OK Cancel Closes this dialog box without setting user information. Sets the user information you specify. If you specified a new password, it is saved at the server.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
237
Display Normal Displays the contents of the control they would appear normally. Display Hex Displays the contents of the control as a hexadecimal value. Display Both Displays the contents of the control as both normal and hexadecimal values. OK Cancel Closes the dialog box without changing the contents of the control. Accepts any changes to the contents of the control, and closes the dialog box.
238
Users Guide
Operator Determines the relationship between the left and the right sides of the row. Right Side Enter the condition for which you want to check. Or, enter an expression here You can enter your own row condition in this field. Add Cancel Cancels the condition you were creating, closes the Row Conditions dialog box. Adds the condition to the Edit Table process.
Left Side List Select the column and associated data type that you want to examine from the list. Or, enter an expression here Type the left side of the row condition here. You can specify the Column and Data type in this field instead of selecting them form the Left Side list. Is Select the Is radio button to specify an equal to relationship between the left and the right sides of the row.
Is Not Select the Is Not radio button to specify a not equal to relationship between the left and the right sides of the row. Right Side In the right side fields, type the condition or conditions for which you want to check. Add Cancel Cancels the condition you were creating, closes the Row Conditions dialog box. Adds the condition to the Edit Table process.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
239
Cancel Cancels the sort condition you were creating, closes the Sort Condition dialog box.
Finish Creates the new form with the settings you have specified. Cancel Closes the dialog box and cancels the creation of the form.
240
Users Guide
Select a server for a table Displays a list of available servers. Next Cancel Closes the dialog box and cancels the creation of the form. Accepts the server you choose and opens the next dialog box.
Finish Skips any additional dialog boxes and creates the new form with the settings you have specified. Default settings are used for any dialog boxes you skip. Cancel Closes this dialog box and cancels the creation of the form.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
241
Finish Skips any additional dialog boxes and creates the new form with the settings you have specified. Default settings are used for any dialog boxes you skip. Cancel Closes this dialog box and cancels the creation of the form.
242
Users Guide
Refresh Refreshes the object list and screen buttons according to the server, type, owner, and name specified on the screen. Owner Type the owner that is associated with an object. Database Type the database where the object is stored. This control is only enabled when you are accessing an os/390 or z/OS server. Name Type the name of the object. To search for all tables or forms that have the specified owner, type and exist on the specified server, type % in the Name field then click Refresh. Add To List Lists all of the forms matching the server, type, owner, and name specified and appends this list to the existing forms in the List field. Table Space Type the table space where the object is stored. This control is only enabled when you are accessing an os/390 or z/OS server. Open Modify Click Modify to open the selected form for editing. Delete Click Delete to delete the selected form from the database. Edit Tabular Click Edit Tabular to edit the selected table in a grid format. Edit Columnar Click Edit Columnar to edit the selected table using a form. Edit Wizard Click Edit Wizard to edit the selected table using the Edit Table Wizard. Click Open to open the selected form.
243
Back Next
Returns to the Object List dialog box. Moves to the next dialog box in the edit table process.
Finish Creates the new form with the settings you have specified. Cancel Closes the dialog box and cancels the creation of the form.
Finish Creates the new form with the settings you have specified. Cancel Closes the dialog box and cancels the creation of the form.
Delete Removes the selected row condition from the form. Sort Conditions Sort conditions allow you to specify the way you want to sort the rows in a table. Add Opens the Sort Conditions dialog box to add a sort condition to the form.
244
Users Guide
Row Limit A row limit allows you to limit the number of rows that are returned and displayed in a table. Allow Primary Key Updates Leave this box checked to allow updates to primary key columns. Uncheck it to forbid updates to primary key columns. On Leave Row This save mode sends changes you make to DB2 every time you click outside a row you have made changes to. At End This save mode sends changes you make to DB2 when you are finished with all edits to the form. No Shared Select this Lock Table option to prevent other applications from performing any but read-only operations on the table while you are editing it. Exclusive Select this Lock Table option to prevent concurrent applications from performing any operations on the table. Back Next Moves you back one step in the Edit Table process. This button is grayed out since this dialog is the last in the series. Click the Finish button to proceed. Select this Lock Table option to edit the table without locking it.
Finish Creates the new form with the settings you have specified. Cancel Definition
Delete Removes the selected row condition from the form. Sort Conditions Sort conditions allow you to specify the way you want to sort the rows in a table. Add Opens the Sort Conditions dialog box to add a sort condition to the form.
Delete Removes the selected sort condition from the form. Row Limit A row limit allows you to limit the number of rows that are returned and displayed in a table. On Leave Row This save mode sends changes you make to DB2 every time you click outside a row you have made changes to.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
245
At End This save mode sends changes you make to DB2 when you are finished with all edits to the form. No Shared Select this Lock Table option to prevent other applications from performing any but read-only operations on the table while you are editing it. Exclusive Select this Lock Table option to prevent concurrent applications from performing any operations on the table. Back Next Moves you back one step in the Edit Table process. This button is grayed out since this dialog is the last in the series. Click the Finish button to proceed. Select this Lock Table option to edit the table without locking it.
Finish Creates the new form with the settings you have specified. Cancel Definition
246
Users Guide
Uppercase Forces all text typed for that column to be uppercase. Hexadecimal Format Check the Hexadecimal Format check box to have number shown in hexadecimal format. This control is only available when using the DB2 Table Editor Windows User component. Thousands Separator Check the Thousands Separator check box to have a comma used as a thousands separator when showing numbers. This control is only available when using the DB2 Table Editor Windows User component. Move Up Moves the selected column up in the column order. Move Down Moves the selected column down in the column order. OK Cancel Closes the dialog box without saving any changes. Accepts the column settings and closes the dialog box.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
247
In the DB2 Table Editor Windows User component, once the file extensions are set, double clicking in a cell containing a LOB will automatically display the LOB value. To change the file extension select View/Edit LOB from the Form Layout Edit Menu. File Extension Enter the file extension of the LOB you wish to open here if you do not have a mapping column. Browse Click this button to select the executable file for the applications that you want to use to view or edit the LOB. This option can be used in place of typing the LOBs file extension in the File Extension field. This contol is available when working with the DB2 Table Editor Windows User component. Mapping Column Select a column from which to derive LOB file extensions in this table. Mapping Click this button to select the mapping column from a list in the File Extension Mapping dialog box. This contol is available when working with the DB2 Table Editor Windows User component. OK Opens the selected LOB in an appropriate application with the extension that you indicated. The applications that are available vary depending on the platform on which you are working. Closes this dialog box without opening the selected LOB.
Cancel
Informix Select Informix to specify that you will be accessing an Informix database server. Database server Highlight the database server to which you want to connect. Host name or IP address Specify the host name or IP address of the database server to which you want to connect. This control is only available when connecting to an Informix database server. Port Number Specify the port number for the database server to which you want to connect. This control is only available when connecting to an Informix database server. Database name Specify the name of the database to which you want to connect. This control is only available when connecting to an Informix database server. OK Cancel Closes the dialog box without setting a database server. Sets the specified database server.
248
Users Guide
CPI-C Warning timeout If a communication request does not complete within this period of time, DB2 Table Editor asks whether or not to cancel the request and return an error. CPI-C Cancel timeout If a communication request does not complete within this period of time, DB2 Table Editor automatically cancels the request and returns an error. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
249
Trace file 2 The name of the second trace file that you want to use. ... Browses for the name of the second trace file you want to use.
250
Users Guide
DDM TCP
When checked, applies tracing to DDM operations. When checked, applies tracing to TCP operations.
CPI-C When checked, applies tracing to CPI-C operations. CLI When checked, applies tracing to CLI operations.
Embedded SQL When checked, applies tracing to embedded SQL operations. SQLAM When checked, applies tracing to SQLAM operations. REXX When checked, applies tracing to REXX operations. Internet Mail When checked, applies tracing to Internet Mail operations. Note: Apply tracing only if you are attempting to diagnose a problem, since tracing has an adverse effect on performance. OK Cancel Closes this dialog box without saving the options you entered. Saves the options you entered. Some options do not take effect until you restart DB2 Table Editor.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
251
252
Users Guide
Remove Click Remove to remove the selected condition from the Active Conditions list. Remove All Click Remove All to remove all of the conditions from the Active Conditions list. OK Cancel Click Cancel to close the Filters window without setting any filter conditions. Show only matching rows Select Show only matching rows to have only the rows that match the filter conditions visible in the grid after the filter conditions are applied. Highlight matching rows Select Highlight matching rows to have all rows appear in the grid and have the rows that match the filter conditions highlighted in the grid after the filter conditions are applied. Click OK to set the filter conditions in the Active Conditions list and close the Filters window.
Chapter 4. Getting Started with DB2 Table Editor Windows User component and Java Player component
253
254
Users Guide
255
from database-specific calls in the same way hat printer drivers isolate word-processing programs from printer-specific commands. ODBC drivers are loaded at run time. A user only has to add a new driver to access a new DBMS. It is not necessary to recompile or re-link the application. To set up ODBC connectivity, you must have the following: v ODBC Driver Manager - DB2 Table Editor requires an ODBC Driver Manager. Microsofts ODBC Driver Manager v 3.0 (or later) is recommended. The following files are included: odbccp32.dll odbccp32.cpl odbccp32.dll v ODBC Data Sources - DB2 Table Editor references ODBC data sources by their Data Set Name (DSN). Most data sources can be accessed by DB2 Table Editor as long as the particular ODBC data source drivers are available. A user ID and password are required to make the connection if it is required by the ODBC data source. v ODBC Drivers - The following ODBC driver has been tested for use with DB2 Table Editor: INFORMIX Driver 3.81.00.11267 v ODBC Support in DB2 Table Editor For ODBC servers, DB2 Table Editor supports: - all isolation levels if supported by data source - binding methods by row and by column - auto-commit-off if supported by data source - user, machine, and file data source name (DSN) - use of ODBC cursor library - use of multi-row block fetch if supported by ODBC driver - stored procedures - large objects (LOBs) as long variable length objects For ODBC servers, DB2 Table Editor does not support: - bookmarks - interval data types For more information on configuring your Informix database for ODBC connectivity, consult the most recent version of the Informix documentation. When consulting the documentation, search for information on ODBC drivers. Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Related tasks Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 257 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 258 Connecting to an Informix Database using the DB2 Table Editor Java Player component on page 260 You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Creating Catalog Objects when working with Informix databases on page 260
256
Users Guide
Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases
To run DB2 Table Editor Java Player as an application on a client machine, install the Java interpreter, or Java Virtual Machine (JVM), as well as the Informix JDBC driver on the client machine. The DB2 Table Editor application does not include these components. The most recent version of the Informix JDBC driver is available for download form http://www.informix.com 1. Install the Java interpreter (version 1.1 or higher). 2. InstallDB2 Table Editor according to the installation instructions. For instructions on installing DB2 Table Editor, see: Installing DB2 Table Editors Graphical User Interface. The files that are required for DB2 Table Editor Java Player will be installed automatically. These files are: v db2forms.jar - Class file for the DB2 Table Editor Java Player application v One or more of the following license files. dbehost.lic dbewrkgp.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) 3. Create a desktop shortcut to access the application. Create a new shortcut with the following target command line:
"x:\<location_of_java.exe>\java.exe" -cp "x:\<location_of_ifxjdbc.jar>\ifxjdbc.jar"; "x:\<location_of_db2forms.jar>\db2forms.jar" DB2Forms
Where: v x:\<location_of_ifxjdbc.jar> specifies the location of the Informix JDBC diver on your machine v x:\<location_of_db2forms.jar> specifies the location of the DB2 Table Editor classes that were installed with DB2 Table Editor. For Example:
C:\j2sdk1.4.2\bin\java.exe -cp C:\informix\lib\ifxjdbc.jar";" C:\DB2 Table Editor\db2forms.jar " DB2Forms
Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Configuring your ODBC Environment on page 255 Related tasks Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 258 Connecting to an Informix Database using the DB2 Table Editor Java Player component on page 260 You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Creating Catalog Objects when working with Informix databases on page 260 Using the Procedures Wizard to create catalog objects on page 261
257
Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases
To run the DB2 Table Editor Java Player, or an individual DB2 Table Editor form, as an applet, you must install a web browser that is enabled for Java 1.1 or greater on the client machine. 1. Install a web browser enabled for Java 1.1 or greater. 2. On the machine where the Informix database is located, install and configure a web server. 3. Install DB2 Table Editor according to the installation instructions on any DB2 Table Editor compatible machine. You will copy the DB2 Table Editor Java Player program files from this machine to your web server. Note: The files that are required for DB2 Table Editor Java Player will be installed automatically when you install DB2 Table Editor. These files are: v db2forms.jar - Class file for the DB2 Table Editor Java Player application. v The HtmlHelp directory - HTML help files for the DB2 Table Editor Java Player application. 4. Copy the following files and directories to the home directory on your web server: v db2forms.jar v ifxjdbc.jar v One or more of the following license files. dbehost.lic dbewrkgp.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. The Home Directory is the directory where any HTML files containing a DB2 Table Editor applet will reside. This is the directory where your HTTP Server serves files from. This directory structure must be followed for DB2 Table Editor Java Player to function properly as an applet. 5. To run a DB2 Table Editor form as an applet, use DB2 Table Editor Developer to create a form. Then, in DB2 Table Editor developer, automatically generate an HTML file with the embedded applet tags for the form. You can create your own custom HTML file containing the following applet tag and parameters:
<applet code = "DB2FormsApplet.class" width=N height=N align="Position_of_form" archive="db2forms.jar, ifxjdbc.jar"> <param name=Informix_host value= <host name> > <param name=Informix_port value= <port number> > <param name=Informix_Database value= <database name> > <param name=Informix_Server value= <server name > > <param name=UserID value=ID_of_user> <param name=Password value=Password_of_user> </applet>
Where:
258
Users Guide
v Width - Specifies the applet display width in the browser window, in pixels. v Height - Specifies the applet display height in the browser window, in pixels. v Align - Specifies the applet display alignment in the browser window, as center, left, or right. v Informix_host Specifies the name of the http server from which the JAVA applet will run. v Informix_port - Specifies the port number that the JDBC applet server is listening on. v Informix_Database - Specifies the name of the Informix database to which you want to connect. v Informix_Server - Specifies the name of the Informix server from which the JDBC applet will run. v UserID - Specifies the user ID with which to log in to the server (optional). v Password - Specifies the password with which to log in to the server (optional). Requirement: When you are connecting to an Informix database server, the Informix server must be on the same machine as your Web server. 6. Install the HTML file that contains the DB2 Table Editor applet tags in the same directory as db2forms.jar, ifxjdbc.jar, the license file, and the HtmlHelp directory:
Home Directory db2forms.jar <name_of_file>.html <License file>.lic ifxjdbc.jar HtmlHelp Directory
Where <name_of_file> is the name of the HTML file containing the DB2 Table Editor applet tags. 7. Open the URL that is used to connect to the DB2 Table Editor Java player. The URL is as follows: http://<http server>/<path>/xxx.html Where HTTP server is the name of your HTTP server, <path>/xxx.html is the path to and name of the HTML file that contains the applet parameters that are used to open the form. You can open the HTML file from any web browser enabled for Java 1.1, and run the DB2 Table Editor Java Player application, or DB2 Table Editor form. Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Configuring your ODBC Environment on page 255 Related tasks Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 257 Connecting to an Informix Database using the DB2 Table Editor Java Player component on page 260 You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Creating Catalog Objects when working with Informix databases on page 260 Using the Procedures Wizard to create catalog objects on page 261
259
Connecting to an Informix Database using the DB2 Table Editor Java Player component
You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Requirement: You must use the Informix JDBC driver installed on your machine in order to connect to an Informix database. 1. Ensure that the path to the Informix JDBC diver is added to the path of your shortcut to the DB2 Table Editor Java Player Component. 2. Open the Set Database window by selecting View --> Set Server. 3. Select the Informix radio button to specify that you will be accessing an Informix database server. 4. In the Database Server box, select the database server to which you want to connect. 5. In the Host name or IP address field specify the host name or IP address of the database server to which you want to connect. 6. In the Port Number field, specify the port number for the database server to which you want to connect. 7. In the Database Name field, specify the name of the database to which you want to connect. 8. Click OK. Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Configuring your ODBC Environment on page 255 Related tasks Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 257 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 258 Creating Catalog Objects when working with Informix databases Using the Procedures Wizard to create catalog objects on page 261
260
Users Guide
3. Click the Wizard button and create the DB2 Table Editor catalog objects. The Procedures Wizard opens. For more information on the Procedures Wizard, see the fields and controls information on the Packages Wizard and Procedures Wizard. 4. When you have finished creating DB2 Table Editor Objects in the Procedures Wizard, close the Procedures page of the Parameters notebook: v Click Next to close the Procedures page of the Parameters notebook. If you are configuring a new database server in the DB2 Table Editor SDF, the Catalog page of the Parameters notebook opens. v Click OK to close the Procedures page of the Parameters notebook. If you are editing a database servers configuration parameters, the Parameters notebook closes, saving any changes that you have made to the database servers configuration parameters. Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Configuring your ODBC Environment on page 255 Related tasks Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 257 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 258 Connecting to an Informix Database using the DB2 Table Editor Java Player component on page 260 You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Using the Procedures Wizard to create catalog objects
261
6. From the Check Objects page specify whether or not you will be creating a new set of DB2 Table Editor database objects. Select the Automatically check which objects already exist radio button. 7. Click the Next button to open the next page of the Procedures Wizard. 8. From the Object Listing Option page specify the level of filtering that will apply when producing lists of objects for DB2 Table Editor users. To impose the least amount of filtering and present all objects stored on the database server to a user regardless of user ID, click the Include all objects without respect to whether or not the user is authorized to access them button. To specify that only the database objects that a users primary ID or current authorization ID is allowed to access, click the Include only those objects that either the users primary or current authorization ID is authorized to access button. If a user is part of multiple groups that require different authorization IDs and you want to specify that all the database objects that can be accessed by the primary user ID, the current authorization ID and all other authorization IDs that the primary user ID is associated with, click the Include only those objects that any of the users primary or secondary authorization IDs are authorized to access. 9. Click the Next button to open the next page of the Procedures Wizard. 10. From the Create Objects page you can view and edit the SQL statements that DB2 Table Editor will use to create the required database tables. 11. Click the Next button to open the next page of the Procedures Wizard. 12. From the Create Procedures page specify whether or not the Procedures Wizard will create the procedures using the parameters and information that you have specified. Click the Do not create the procedures button to skip this step. You may skip this step if you have previously bound procedures on this database server for the current version of DB2 Table Editor. Click the Create the procedures button to bind the DB2 Table Editor procedures. Check the Replace existing procedures (if any) check box to ensure that procedures from previous versions of DB2 Table Editor do not remain on the database server. 13. Click the Next button to open the next page of the Procedures Wizard. 14. From the Permissions page you grant permission to the user IDs that can run DB2 Table Editor on this database server. To grant permission to all user IDs, select the default user ID PUBLIC from the User IDs list box and click the Grant button. To grant permission to a specific user ID, type the user ID in the User IDs list box and click the Grant button. To revoke permission from a user ID, type the user ID in the User IDs list box and click the Revoke button. Note: If you are choosing to use the default user ID PUBLIC to grant all DB2 Table Editor users permission to run queries on this database server, you must actually grant the permission to the PUBLIC user ID by selecting the user ID and clicking the Grant button. 15. Close the Procedures Wizard. v Click the Finish button to close the Procedures Wizard. The Procedures page of the Parameters notebook remains open. v Click the Next button is to close the Procedures Page. The Catalog page of the Parameters notebook opens. Related concepts Chapter 5, Using DB2 Table Editor with Informix databases, on page 255 Installing DB2 Table Editor when working with Informix Databases on page 255 Configuring your ODBC Environment on page 255
262
Users Guide
Related tasks Installing and configuring DB2 Table Editor Java Player as an application on a client machine when working with Informix databases on page 257 Installing and configuring DB2 Table Editor Java Player as an applet when working with Informix databases on page 258 Connecting to an Informix Database using the DB2 Table Editor Java Player component on page 260 You can connect to an Informix Version 9.3 database using the DB2 Table Editor Java Player component. Creating Catalog Objects when working with Informix databases on page 260
263
264
Users Guide
You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. v HtmlHelp Directory (Including all sub folders) By default this directory is SQLLIB\tools. The DB2 Control Center requires that these files be located in the Java classpath so that they can be loaded when the Control Center is started. 2. Copy db2plug.v8zip, into SQLLIB\tools directory 3. Rename db2plug.v8zip to: db2plug.zip Note: If there is already another version of db2plug.zip in SQLLIB\tools, you must combine the contents of the existing db2plug.zip and db2plug.v8zip. For Example, if you are using the Zip utility, use the following command:
zip -r0 db2plug.zip com\rocketsoftware\ccplugin\*.*
4. If you are running the Control Center as a Java applet, complete the following steps: a. Copy the db2forms.jar and db2jcc.jar file where the <codebase> tag points to in db2cc.htm. b. Update db2cc.htm to include db2plug.zip, db2jcc.jar, and db2forms.jar in the archive list. You can now start Table Editor from within Control Center by selecting a DB2 Table Editor menu item from the Table popup menu or the new tool bar button.
265
To install the DB2 Table Editor Control Center Plug-in to work with DB2 V7
1. Copy the following files and directories to the SQLLIB\cc: v db2forms.jar v One or more of the following license files. dbehost.lic dbe400.lic dbework.lic dbehost.ecf (if you are working with a trial version of DB2 Table Editor) You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. v HtmlHelp Directory (Including all sub folders) By default this directory is SQLLIB\cc. The Control Center requires that these files be located in the Java classpath so that they can be loaded when the Control Center is started. 2. Copy db2plug.v7zip, into the SQLLIB\cc directory. 3. Rename db2plug.v7zip to: db2plug.zip Note: If there is already another version of db2plug.zip in SQLLIB\cc, you must combine the contents of the existing db2plug.zip and db2plug.v7zip. For Example, if you are using the Zip utility, use the following command:
zip -r0 db2plug.zip com\companyname\myplugin\*.class
Where the plug-in package name is: com.companyname.myplugin 4. Locate the db2cc file in the SQLLIB\bin. If you are using Windows, the file is named db2cc.bat. If you are using the Unix or Linux, the file is named db2cc. 5. Update db2cc to include both db2plug.zip and db2forms.jar. The file names must follow a -c option. With newer releases of DB2, you must add the -c option. If you are using an older version of DB2 which has the -c option specified in db2cc, you can append the values to the end of the existing -c option. The following is an example of db2cc after you have added the files:
IF "%1" == "wait" GOTO WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -o:"-mx128m -ms32m" -a:"%1 %2 %3 %4 %5 %6 %7 %8" GOTO END :WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -w:-o:"-mx128m -ms32m" -a:"%2 %3 %4 %5 %6 %7 %8 %9" GOTO END :end
6. If you are running the Control Center as a Java applet, complete the following steps: a. Copy the db2forms.jar file where the <codebase> tag points to in db2cc.htm. b. Update db2cc.htm to include db2plug.zip and db2forms.jar in the archive list. You can now start Table Editor from within Control Center by selecting a DB2 Table Editor menu item from the Table popup menu or the new tool bar button. Related concepts Chapter 6, The DB2 Table Editor Control Center Plug-in, on page 265 Using the DB2 Table Editor Control Center Plug-in on page 267
266
Users Guide
267
268
Users Guide
Customization summary
Complete the installation instructions can be found in the Program Directory. After you install DB2 Table Editor, you must tailor some files for your system. The following steps necessary to configure your system are detailed in the following table (Overview of steps for configuring DB2 Table Editor).
Table 10. Overview of steps for configuring DB2 Table Editor Step 1 2 3 4 5 6 Description Create the control file. Bind the packages Bind the plans Bind the packages and plans for all other subsystems to which you want to connect Edit SETISAMP members ETICLIST and ETI Optional: Add DB2 Table Editor to the DB2 Administration Tool and Launchpad Job ETICNTFL ETI#BND1 ETI#BND2 ETI#BND1 EIT#BND2 ETICLIST and ETI ETIDB21T and ETIADBO
269
Step 4. Bind the packages and plans for all other sub systems to which you want to connect
Repeat steps 2 and 3 for each subsystem that you plan to run against. Use a unique subsystem identifier each time, SYSTEM(XXXX), where XXXX is the subsystem identifier. You can use the same plan name for all subsystems.
270
Users Guide
&CTCLEVEL..SETIMENU) UNCOND STACK to &CTCLEVEL..SCTCMENU) UNCOND STACK &CTCLEVEL..SETIPENU) UNCOND STACK to &CTCLEVEL..SCTCPENU) UNCOND STACK &CTCLEVEL..SETILOAD) UNCOND STACK to &CTCLEVEL..SCTCLOAD) UNCOND STACK The following is an example of an ETICLIST member. There are notes within the text of this sample file (in lower case) indicating the parts of the file that need to be modified as part of step five.
PROC 0 DIRECT(NO) CNAME(NONE) TNAME(NONE) SNAME(NONE) + WARNA(YES) WARNB(YES) LOCBRSE(YES) + <if yes Table Editor will lock in browse mode> ETILEVEL(HILEVEL.ETI.PDS) + < the prefix of the ETI libraries> CTCLEVEL(HILEVEL.CTC.PDS) + < the prefix of the CTC libraries> DB2CNTFL(ETI.DB2.CONTROL) <the control file> ISPEXEC VPUT (DIRECT CNAME TNAME SNAME) ASIS ISPEXEC VPUT (DB2CNTFL WARNA WARNB LOCKBRSE) ASIS ISPEXEC VPUT (CTCLVL CTCPRE LLIB) ASIS CONTROL NOMSG FREE FILE(ETIPRINT) CONTROL MSG ISPEXEC LIBDEF ISPMLIB DATASET ID(&ETILEVEL..SETIMENU + &CTCLEVEL..SETIMENU) UNCOND STACK <change the above line to &CTCLEVEL..SCTCMENU) UNCOND STACK> ISPEXEC LIBDEF ISPPLIB DATASET ID(&ETILEVEL..SETIPENU + &CTCLEVEL..SETIPENU) UNCOND STACK <change the above line to &CTCLEVEL..SCTCPENU) UNCOND STACK> ISPEXEC LIBDEF ISPLLIB DATASET ID(&ETILEVEL..SETILOAD + &CTCLEVEL..SETILOAD) UNCOND STACK <change the above line to &CTCLEVEL..SCTCLOAD) UNCOND STACK> ALLOC FILE(ETIPRINT) SYSOUT ETI$MAIN FREE FILE(ETIPRINT)
2. You must customize the CLISTs for ISPF dialog access to DB2 Table Editor. Edit SETISAMP member ETI. Change the PROC0 statement to match your installations high level qualifiers for the ETI and CTC libraries by replacing ETILVL with the high level qualifier of the ETI libraries and CTCLVL with the high level qualifier of the CTC libraries. Edit SETISAMP member ETI and specify the library where CLIST is located. The following is an example of an ETI member. There is a note within the text of this sample file (in lower case) indicating the part of the file that needs to be modified as part of step four.
PROC 0 DIRECT(NO) CNAME(NONE) TNAME(NONE) SNAME(NONE) + WARNA(YES) WARNB(YES) LOCKBRSE(YES) + CLISTLIB( LOCATION OF PDS ) CONTROL NOMSG FREE FILE(ETICLIST) CONTROL MSG ALLOC FILE(ETICLIST) DATASET(&CLISTLIB) SHR REU <The PDS where ETI is currently a member.> ALTLIB ACTIVATE APPLICATION(CLIST) FILE(ETICLIST) ISPEXEC SELECT CMD(ETICLIST DIRECT(&DIRECT) NAME(&CNAME) TNAME(&TNAME) SNAME(&SNAME) WARNA(&WARNA)<column selection warning -- a warning when the value is YES and columns are excluded> WARNB(&WARNB)) - <lock table warning -- a warning appears when the value is YES and a LOCK TABLE command is issued from the DB2 Table Editor main panel> NEWAPPL(ETI) PASSLIB ALTLIB DEACTIVATE APPLICATION(CLIST)
Chapter 7. The DB2 Table Editor ISPF component
271
The libraries listed above should match the names that you allocated during installation.
Step 6. Optional: Add DB2 Table Editor to the DB2 Administration Tool and Launchpad
DB2 Administration Tool, program number 5655-E64, provides a central location to launch one or more DB2 tools.You can add DB2 Table Editor to the DB2 Administration Tool and its Launchpad. This step is optional. For detailed information on how to enable an IBM DB2 tool for the launchpad, see DB2 Administration Users Guide (SC27-0974), available on the Web at: http://www.ibm.com/software/data/db2imstools/details/. DB2 Administration Tool, program number 5655-E64, adds launchpad support for installed IBM DB2 tools that have an ISPF interface. It provides a central location to launch one or more DB2 tools. You must have applied APAR PQ45029 and created the Launchpad table. You can configure the DB2 Administration tool so that you can edit tables using DB2 Table Editor. After this configuration, when you select to edit a table from the DB2 Administration Tool, DB2 Table Editor will launch. v To add DB2 Table Editor to the DB2 Administration Tool: 1. Edit the SETISAMP member ETIDB21T by following the instructions contained within ETIDB21T. 2. Run ETIDB21T. v To add DB2 Table Editor to the DB2 Administration Tool launchpad: 1. Locate the sample install CLIST in the following library: (xxx.xxxx(ETIADBI). Where xxx.xxx is the library where DB2 Table Editor is stored. 2. Modify the sample CLIST (ETIADBI) by following the instructions contained in the CLIST. 3. Run the ETIADBI CLIST and DB2 Table Editor will be added to the launchpad.
Completing customization
To complete the installation of DB2 Table Editor on your system, DB2 Table Editor must be configured for your system and default values must be set. The steps for configuring your system are summarized in the following table (Overview of steps for configuring DB2 Table Editor ).
Table 11. Overview of steps for configuring DB2 Table Editor Step 1 2 3 Description Start DB2 Table Editor. Set up the configuration file for DB2 Table Editor. Set the DB2 subsystem parameters Job/Panel ETI Enter DB2 System Parameters panel Update Parameters for DB2 Subsystem panel Enter DB2 System Parameters panel and Update Parameters for DB2 Subsystem panel
Repeat steps 2 and 3 for each DB2Subsystem to which you want to connect.
272
Users Guide
Where &CLIST is the name of the DB2 Table Editor SETISAMP library that is installed. The main panel for DB2 Table Editor opens.
Enter DB2 Subsystem Info: DB2 Subsystem ID ==> (1-4 Character Subsystem ID)
Valid command selection values are: 1: ZPARM, BSDS, and Load Library Information 2: DB2 Table Editor
2. In the DB2 Subsystem ID field, type the subsystem identifier (SSID) for the DB2 subsystem that you want to configure. This field has a four-character maximum.
273
----------------- Update Parameters for DB2 Subsystem systemname Command ==> Enter or Update Specific DB2 Parameters : DB2 DB2 DB2 DB2 DB2 DB2 DB2 DB2 ZPARMs Member ==> Bootstrap DSN #01 ==> Bootstrap DSN #02 ==> Loadlib1 ==> Loadlib2 ==> Loadlib3 ==> Loadlib4 ==> Loadlib5 ==>
2. In the Update Parameters for DB2 Subsystem panel, enter information specific to a particular DB2 subsystem, including ZPARM, BSDS, and load library. a. In the DB2 ZPARMs Member field, type the eight-character ZPARM load module member name generated for this DB2 subsystem. b. In the DB2 Bootstrap DSN #01 and the DB2 Bootstrap DSN #02 fields type the full data set names of the two bootstrap data sets that are being used by this DB2 Subsystem. c. In the DB2 Loadlib1 to DB2 Loadlib5 fields, type the names of the data sets that comprise the current loadlib concatenation for DB2. The loadlib usually consists of: v a subsystem-specific DSNEXIT library v the base DSNEXIT library for the current DB2 version v the base DSNLOAD library for the current DB2 version Note: There are two extra Loadlib fields. They can be left blank or used to enter any other libraries contained in the loadlib. d. Press Enter to submit your changes. A message appears on the screen to indicate that your changes have been saved. e. Press PF3 the Update Parameters for DB2 Subsystem panel closes. A message stating that a record has been added appears. Press PF3 to return to the previous screen. 3. Type 2 on the Command line. The second Update Parameters for DB2 Subsystem panel opens. The Update Parameters for DB2 Subsystem panel is shown in the following figure (Update Parameters for DB2 Subsystem panel).
------DB2 Table Editor - Update Parameters for DB2 Subsystem Command ==> Enter or Update Specific DB2 Parameters: Plan Name ==> ETIPLAN1 ZOOM Command ==> ZOOM
4. In the second Update Parameters for DB2 Subsystem panel, type information specific to the DB2 Table Editor parameters. a. In the Plan Name field, type the eight character plan name used for DB2 Table Editor. This is the same plan name that was used in member ETI#BND1 in the SETISAMP library when the plan for DB2 Table Editor was bound.
274
Users Guide
b. In the ZOOM Command field, type the command that you want to use for the ZOOM functionality. For more information on the ZOOM command, see DB2 Table Editor ISPF Component Commands. c. Press Enter to submit your changes. A message appears on the screen to indicate that your changes have been saved. d. Press PF3 to return to the previous screen. 5. Press Enter to submit your changes. A message appears on the screen to indicate that your changes have been saved.
Step 4. Setup the configuration file and set the DB2 subsystem parameters for all other DB2 Subsystems to which you want to connect
Repeat steps 2 and 3 for all DB2 subsystems to which you want to connect.
Permissions
In order to use DB2 Table Editor, the user must have EXECUTE permission on the DB2 Table Editor plan and on the load lib. You must also have read permission on the control file. The Administrator must also have UPDATE authority on the control file.
Invoking DB2 Table Editor from the Administration tool Launch pad
You can invoke DB2 Table Editor from the Administration Tool Launchpad if you added DB2 Table Editor to the DB2 Administration Tool and Launchpad during installation and configuration. 1. From the DB2 Administration Menu (panel ADB2), select 1 (DB2 system catalog) 2. From the System Catalog (panel ADB21), fill in the Standard Selection Criteria near the bottom of the panel to specify the tables that you want to see, then select T (Tables, views, and aliases) 3. From the Tables, Views, and Aliases (panel ADB21T), place a ? in the Sel column and press Enter. The list of available commands is displayed. Select the option from the list that indicates that you can edit the table.
275
(Yes / No)
The fields on the IBM DB2 Table Editor panel are listed and described in the following table (Fields on the IBM DB2 Table Editor main panel and their descriptions. ).
Table 12. Fields on the IBM DB2 Table Editor main panel and their descriptions. Field DB2 Subsystem ID Current SQLID User Table Location Table Creator Like Description Type the four character DB2 Subsystem ID (SSID) for the subsystem that contains the table you want to edit or view. Type the SQLID for the User under whom you want to run all SQL. Displays the current User. Type the location of the table in this field. Type the table creator name for which you want to search. You can use wildcards in your search. Use the * character or the % character as the wildcard character. Typing an * returns all table creators. You can also type a LIKE clause here, if desired. Type the table name for which you want to search. You can use wildcards in your search. Use the * character or the % character as the wildcard character. Typing an * returns all table names. Type the maximum number of rows that you want the query to return. Type 0 to indicate no limit. Type the maximum number of characters that you want to be displayed in each column. the default is 30 characters. If a field exceeds this maximum it will appear in white and you must use the zoom command to see all of the data. For more information of using the zoom command, see the section: Editing a long cell.
276
Users Guide
Table 12. Fields on the IBM DB2 Table Editor main panel and their descriptions. (continued) Field Lock Table Description Type N (No) to edit the table without locking it. Type S (Shared) to prevent other applications from performing anything but read-only operations on the table while you edit it. Type E (Exclusive) to prevent concurrent applications from performing any operations on the table while you edit it.
NULL default value Type Y to have empty cells filled with nulls when you insert a blank row. Type N to have empty cells left empty when you insert a blank row. Note: Rows that are marked as not null will not be filled with nulls, even if Y is selected. If you have selected N, but later edit a cell to insert a null value, DB2 Table Editor will change your selection from N to Y Show separator Type Y to have thousands separated by a specified character when numbers greater than 999 are shown. Type N to show no thousands separator character when numbers greater than 999 are shown. Type the character to be used to separate the thousands in when numbers greater than 999 are shown. Type the character to be used to represent a decimal when numbers are shown. Type Y to save the options that you have specified in this panel. Type N if you do not want to save these options.
Opening a table
You can use DB2 Table Editor to view or edit table data. 1. From the DB2 Table Editor main panel, in the DB2 Subsystem ID field, type the ID for the DB2 Subsystem where the table that you want to open is located. 2. In the Table Creator Like field, type the name of the creator of the table that you want to open. You can use wildcards or a LIKE clause to search for a table. To see a list of all tables, type * in the Table Creator Like field. 3. In the Fetch Limit field, type the maximum number of rows that you want the query to return. Type 0 to indicate no limit. 4. In the Max Char Display field, type the maximum number of characters that you want to be displayed in each column. If a field exceeds this maximum it will appear in white and you must use the zoom command to see all of the data. 5. In the Lock Table field, type N (No) to edit the table without locking it. Type S (Shared) to prevent other applications from performing anything but read-only operations on the table while you edit it. Type E (Exclusive) to prevent concurrent applications from performing any operations on the table while you edit it. 6. In the NULL default value field, type Y to have empty cells filled with null when you insert a blank row. Type N to have empty cells left empty when you insert a blank row. Note: Rows that have the not null attribute associated with them will not be filled with nulls, even if Y is selected. If you have selected N, but later edit a cell to insert a null value, DB2 Table Editor will change your selection from N to Y.
277
7. In the Save Options field, type Y to save the options that you have entered on this panel, or, type N if you do not want to save these options. 8. Press the Enter key. A list of tables that match the criteria that you entered is displayed in the Table Selection panel. The Table Selection panel is shown in the following figure (Table Selection Panel)
ETI$DPTB V4R3 ------ Table Selection ----- 2004/05/13 15:25:24 Option ===> Scroll ===> PAGE ---------------------------------------------------------------------- +> Location Row 1 of 61 Creator Like USERID DB2 Subsystem: SYS1 Tables Like * -------------------------------------------------------------------------Cmd _ _ _ _ _ Table Name TABLE1 TABLE2 TABLE3 TABLE4 TABLE5 Creator USERID USERID USERID USERID USERID Database Tablespace OBID DBNAME1 TSNAME 01036 2001-06-13-11.5 DBNAME2 TSNAME1 00003 2001-05-29-16.1 DBNAME1 TSNAME 01033 2001-06-08-17.3 DBNAME2 TSNAME1 01030 2001-06-12-22.0 DBNAME4 TSNAME2 00004 2001-05-29-16.1
9. If the table the you want to open is not listed you can search further as follows: In the Table Name Like field, type the name of the table that you want to open. You can use wildcards or a LIKE clause to search for a table. To see a list of all tables, type * in the Table Name Like field. 10. Type S in the Command (cmd) column next to the table that you want to open. Press the Enter key. The Select Columns panel opens. The Select Columns panel is shown in the following figure (Select Columns panel).
ETI$DPSC V4R3 ------ Select Columns ------ 2004/05/13 15:31:05 Option ===> Scroll ===> PAGE ---------------------------------------------------------------------> Location ==> And/Or on Where Clause A Creator ==> USERID Long or Short Data Types L (L or S) Table ==> TBL -------------------------------------------------------------------------Select Ord Srt Frz Type Column Name Where Clause 1 ___ A N DECIMAL(5,2) COL1 2 ___ A N DECIMAL(5,2) COL1 3 ___ A N DECIMAL(5,2) COL2 4 ___ A N DECIMAL(5,2) COL3 ************************ Bottom of Data **************************** Valid Commands: Edit, Browse, SQL, Count, CANcel/PF3
The fields on the Select Columns panel are listed and described in the following table (Fields in the Select Columns panel and their descriptions).
Table 13. Fields in the Select Columns panel and their descriptions Field Location And/Or on Where Clause Description Lists the location of the database to which you are connected. Type A to connect all WHERE clause statements with AND. Type O to connect all WHERE clause statements with OR.
278
Users Guide
Table 13. Fields in the Select Columns panel and their descriptions (continued) Field Long or Short Data Types Description Type L to specify that you want to view the long name for data type names shown in the table (as shown in the screen capture above). Type S to have abbreviated data type names shown in the table. Displays the name of the current table. Displays the creator of the current table. The Select column contains a number that indicates the order in which the corresponding column will be selected. You can change the numbering in the columns if desired. Type N, or leave the Select column blank to exclude the corresponding column from the generated table. Note: To mark all rows to be included in the generated table, (rows with a number in the Select column will be included) type include all on the command line, this will re-number all rows. To mark all rows to be excluded from the generated table, (marked N in the Select column) type exclude all on the command line. Use this option to indicate by which columns to order the data. Type 1 next to the column that you want to order by first. To order by additional columns, type numbers next to the desired columns in the order that you want them to be sorted. Type A to sort the corresponding column in ascending order. Type D to sort the column in descending order. Type Y in the Frz column to freeze the associated column when the table is being edited. When the table is open in the Edit Table Rows panel, the column appears in the table, it will be left justified. When you scroll through the table, the frozen column will always be on the screen. Tip: You can also use the CSET command to Freeze columns while you are editing data. Displays the data type of the corresponding column. Displays the column name of each column in the selected table. Type a WHERE clause to apply to the corresponding column. For example, > 100.
Ord
Srt Frz
Table 14. Line Commands in the Select Columns panel and their descriptions Line Command E B Description Type E on the command line to edit the table. Type B on the command line to browse the contents of the table.
11. Optional: In the Where Clause column, type A to connect all WHERE clause statements with AND. Type O to connect all Where Clause statements with OR. 12. Optional: In the Select column, you can modify the number that is associated with the row in the table. The number in the Select column indicates the order in which the corresponding column will be selected. To exclude the corresponding column from the generated table, type N, or leave the Select column blank. Note: To mark all rows to be included in the generated table, (rows with a number in the Select column will be included) type include all on the
Chapter 7. The DB2 Table Editor ISPF component
279
command line, this will re-number all rows. To mark all rows to be excluded from the generated table, (marked N in the Select column) type exclude all on the command line. 13. Optional: In the Ord field, type 1 next to the column that you want to order by first. To order by additional columns, type numbers next to the desired columns in the order that you want them to be sorted. 14. Optional: In the Srt field, type A to sort the corresponding column in ascending order. Type D to sort the column in descending order. 15. Optional: in the Frz column type Y to freeze a column, so that when it appears on the Edit Table Rows panel, it will remain on the screen when you scroll left and right through the table. Frozen columns are left justified on the edit table rows panel. Tip: You can also use the CSET command to Freeze columns while you are editing data. Optional: If you want to edit or view the generated SQL for your table, Type SQL on the command line and press the Enter key. The Generate Select Statement panel opens. Make the changes that you want to make to the SQL and press PF3. You can save the SQL that you add or modify using the SAVE command. You can also LOAD SQL that you have previously saved using the LOAD command. For more information on SAVE and LOAD, see DB2 Table Editor ISPF Component Commands. Optional: Type COUNT on the command line. A popup box is displayed indicating the number of rows that will be returned by the your SQL statement. Optional: Type E on the command line to edit the table. Optional: Type B on the command line to browse the contents of the table. Press the Enter key. The table will be displayed according to your specifications.
16.
Specifying how a table will be displayed in DB2 Table Editor for viewing or editing
When viewing or editing a table in DB2 Table Editor, you can specify that you want to view or edit all or part of a table using the ETI$DPSC panel. You can specify the columns that you want to view or edit from the selected table. You can also use the options on this panel to customize the way that the table data is organized and displayed in DB2 Table Editor for viewing or editing. 1. From the ETI$DPTB panel, select the table that you want to edit by typing S in the Sel column next to the desired table. The ETI$DPSC panel opens.
280
Users Guide
ETI$DPSC V4R3 ------ Select Columns ------ 2004/05/14 16:53:47 Option ===> Scroll ===> PAGE ---------------------------------------------------------------------> Location ==> And/Or on Where Clause A Creator ==> USERID Long or Short Data Types L (L or S) Table ==> TABLE ------------------------------------------------------------------------Select Ord Srt Frz Type 1 A N VARCHAR(32) 2 A N VARCHAR(32) 3 A N VARCHAR(32) *************************** Bottom of Data ******************************* Valid Commands: Edit, Browse, SQL, Count, CANcel/PF3
Figure 7. The ETI$DPSC panel Table 15. Panel fields and their descriptions for the ETI$DPSC panel Field And/Or on Where Clause Long or Short Data Types Description Type A to connect all WHERE clause statements with AND. Type O to connect all WHERE clause statements with OR. Type L to specify that long data types will be used or type S to specify short data types. A long data type is the full name of the data type while a short data type is the first three letters of the data type name. Short data types have the advantage for a longer Where Clause. The Select column contains a number that indicates the order in which the corresponding column will be selected. You can change the numbering in the columns if desired. Type N, or leave the Select column blank to exclude the corresponding column from the generated table. Tip: To mark all rows to be included in the generated table, (rows with a number in the Select column will be included) type include all on the command line, this will re-number all rows. To mark all rows to be excluded from the generated table, (marked N in the Select column) type exclude all on the command line. Use this option to indicate by which columns to order the data. Type 1 next to the column that you want to order by first. To order by additional columns, type numbers next to the desired columns in the order that you want them to be sorted. Type A to sort the corresponding column in ascending order. Type D to sort the column in descending order. Type Y in the Frz column to freeze the associated column when the table is being edited. When the table is open in the Edit Table Rows panel (ETI$EDIT), the column appears in the table, it will be left justified. When you scroll through the table, the frozen column will always be on the screen. Tip: You can also use the CSET command to Freeze columns while you are editing data.
Select
Ord
Sort Frz
Table 16. Commands and their descriptions for the ETI$DPSC panel. Command E Description Type E on the Command line to edit the rows in the table on the ETI$EDIT (Edit Table Rows) panel.
281
Table 16. Commands and their descriptions for the ETI$DPSC panel. (continued) Command B S Description Type B on the Command line to browse the rows in the table on the ETI$EDIT (Browse Table Rows) panel. Type S on the Command line to view the SQL statement that DB2 Table Editor uses to display table data using the ETI$DSQL panel. Type COUNT on the Command line to count the number rows in the table. Type CAN on the command line to cancel any changes that you have made on the panel and exit the panel. Type SAVE on the command line of the Select Columns panel or the Generated Select Statement panel to save your SQL for future use. Type LOAD on the command line of the Select Columns panel or the Generated Select Statement panel to load SQL that you have previously saved.
LOAD
2. On the ETI$DPSC panel, specify: v Whether WHERE clauses in the SQL statement that is used to display the table data for viewing or editing will be connected with an AND or an OR. Tip: You can specify WHERE clauses on the ETI$DSQL panel which is accessible by typing S on the command line. v Whether long data type names or short data type names will be used. Information: Type L to specify that long data types will be used or type S to specify short data types. A long data type is the full name of the data type while a short data type is the first three letters of the data type name. Short data types have the advantage for a longer Where Clause. v The columns that you want to edit or view using DB2 Table Editor. v The order in which you want the columns to be displayed v Which columns, if any, you want to freeze. Information: Type Y in the Frz column to freeze the associated column when the table is being edited. When the table is open in the Edit Table Rows panel (ETI$EDIT), the column appears in the table, it will be left justified. When you scroll through the table, the frozen column will always be on the screen.
Viewing or editing the generated SQL statement that is used to display table data
You can view the SQL statement that DB2 Table Editor uses to display table data and you can edit parts of the SQL statement. The SQL statement is generated based on the criteria that you specify on the ETI$DPSC panel. You can edit or add a WHERE clause to your SQL statement. You can also save this SQL statement using the SAVE command. 1. From the ETI$DPSC panel, type S on the Command line. The ETI$DSQL panel opens.
282
Users Guide
ETI$DSQL V4R3 --- Generated Select Stmt --- 2004/05/13 16:24:30 Option ===> Scroll ===> PAGE ----------------------------------------------------------------------> Creator ==> USERID Table ==> TABLE --------------------------------------------------------------------------SELECT ONE ,TWO ,THR FROM "USERID"."TABLE" ************************** Bottom of Data ******************************* Valid Commands: Edit, Browse, Count, CANcel/PF3 Valid Line Commands: Insert, Repeat, Delete
Figure 8. The ETI$DSQL panel Table 17. Fields and their descriptions for the ETI$DSQL panel. Field Creator Table Description Lists the current creator ID. lists the current Table.
Table 18. Commands and their descriptions for the ETI$DSQL panel. Command E B COUNT CAN SAVE LOAD Description Type E on the Command line to edit the rows in the table on the ETI$EDIT (Edit Table Rows) panel. Type B on the Command line to browse the rows in the table on the ETI$EDIT (Browse Table Rows) panel. Type COUNT on the Command line to count the number rows in the table. Type CAN on the command line to cancel any changes that you have made on the panel and exit the panel. Type SAVE on the command line to save your SQL for future use. Type LOAD on the command line to load SQL that you have previously saved.
Table 19. Line commands and their descriptions for the ETI$DSQL panel. Line Command I R D Description To insert a row, type I in the command column of the line that you want to insert. To repeat a row, type R in the command column of the line that you want to repeat. To delete a row, type D in the command column of the line that you want to delete.
2. On the ETI$DSQL panel you can view and make any necessary changes to the SQL statement. 3. Optional: you can save the SQL that you have modified for future use by typing SAVE on the command line.
283
4. When you are finished viewing or editing the SQL, run the SQL by typing E to edit or B to browse on the command line. The specified table opens in the ETI$EDIT panel.
Editing a table
You can use DB2 Table Editor for z/OS to perform inserts, updates, and deletes to your DB2 tables. DB2 Table Editor will commit the changes that you make automatically when you finish editing the table.
Editing a row
You can use the Edit Table Rows panel to edit a row in a table. When editing a row you can choose to view the row alone (one row is shown at a time) in form mode or you can view the row in tabular mode where you will see more than one row displayed at once.
To edit a row:
1. In an open table, move the cursor to the cell in the row that you want to edit and type the necessary changes. Note: If the data in the cell is too long to appear on the screen the cell will appear in white. To view or edit the to the entire contents of the cell, use the zoom Command line. To edit rows one row at a time, select the row that you want to edit and type F on the Cmd column corresponding to that row. Press Enter. The row appears in form format. In form mode, you can browse through the rows in a table using PF10 to go to the previous row and PF11 to go to the next row. To return to tabular format press PF3. 2. When you have completed your changes, press the Enter key. DB2 Table Editor marks the row as updated and highlights the changes in yellow. The changes that you have made will be committed in DB2 when you exit the table that you are editing.
284
Users Guide
ETI$EXPL V4R3 ------------ Column Editor ------------ 2002/06/20 17:50:16 Option ===> ________________________________________________ Scroll ===> PAGE ------------------------------------------------------------------------Table Column Length Pad ==> ==> ==> ==> TABLENAME COLNAME 00000005 40 Creator Type Max Null ==> ==> ==> ==> USERID DATATYPE 00000016 N
------------------------------------------------------------------------------****** *********************** Top of Data ************************************ ****** ----+----1----+----2----+----3----+----4----+----5----+----6----+----7-...... COLUMN CONTENTS ***************************** Bottom of Data **********************************
Note: The fields that appear in this panel vary based on the data type of the selected cell. The fields on the Column Editor panel are listed and described in the following table (Fields on the Column Editor panel and their descriptions).
Table 20. Fields on the Column Editor panel and their descriptions Field Table Creator Column Type Length Max Pad Description The name of the table in which the selected cell exists. The creator of the table in which the selected cell exists. The name of the column in which the selected cell exists. The data type of the column in which the selected cell exists. The length in characters of the data in the selected cell. The maximum length in characters of the data in the selected cell. Contains the character that the contents of the cell will be padded with when the contents of the selected cell are shorter than the value in the Max field. This value is N if the selected cell does not have a value of null. The Value is Y if the selected cell does have a value of null.
Null
3. View or edit the data. Note: When you are editing a VARCHAR column in zoom mode, the length is determined automatically by removing the PAD character. This means that when you are editing a column of a specified length, if you type a value that is longer than the specified length, the length of the column will be changed by DB2 Table Editor ISPF component by removing the necessary number of pad characters. The length cannot exceed the maximum length specified by the data type. 4. When you are finished viewing or editing the data, press PF3. If you have made changes to the cell, DB2 Table Editor updates the cell with the information that you entered and returns to the Edit Table Rows panel. Viewing and editing the contents of a cell with a hex editor: You can view the contents of a cell with hex in the zoom panel. v In the Zoom panel, type hex on, on the Command (cmd) line and press the Enter key. The hex editor is turned on. v To turn the hex editor off, type hex off. The hex editor is turned off.
285
Locking
Locking is implemented as follows in the Edit table feature. The LOCK TABLE statement is used to control locking. The options for locking mode are either SHARE MODE or EXCLUSIVE MODE. v In share mode, concurrent application processes are prevented from executing all but read-only operations on the table. v In exclusive mode, concurrent application processes are prevented from executing any operations on the table. Exclusive mode does not prevent concurrent application processes that are running at the Uncommitted Read (UR) isolation level from executing read-only operations on the table. If you select no lock, then DB2 Table Editor does not issue the LOCK TABLE statement, but only obtains locks as needed to perform updates, inserts or deletes. Note that if a table contains a large number of rows, and no row conditions are specified, then not all of data is automatically loaded into the grid until requested. In this case a read cursor will remain open until all of the data is loaded.
Updating
When DB2 Table Editor, ISPF component, is updating a row, it looks for the row in one of two ways. v If the table is locked, DB2 Table Editor uses a unique index (if one exists) to find the row that is to be updated. v If the table is not locked, or it does not have a unique index, DB2 Table Editor examines all columns in the row, with the exception of some types of columns, to determine whether it has found the correct row. The following columns are not examined: LOB columns A string that is too long for a LIKE clause. Strings up to 4000 characters in length can be used in a like clause in z/OS. Note: If a string is greater than 4000, and no duplicate rows exist it can be used, if duplicate rows exist, then the long string must be replaced with a short string. If a string is less than 255 characters in length, an equal (=) operator is used. User-defined data type (UDT) columns. After the ISPF component of DB2 Table Editor has completed an update, it checks to see whether more than one row has been updated. If so, DB2 Table Editor rolls back the transaction, opens a cursor to the first occurrence of the row, and updates that row.
286
Users Guide
1. In the Select Columns panel, ensure that there is a number in the Select column of the rows that you want to edit. If you do not want to have a particular column selected type N in the Select column or leave it blank. 2. Type E on the command line and press Enter. The Edit Table Rows panel opens. The Edit Table Rows panel is shown in the following figure (Edit Table Rows panel).
ETI$EDIT V4R3 ----------- Edit Table Rows ----------- 2002/06/25 12:19:50 Option ===> ________________________________________________ Scroll ===> PAGE ------------------------------------------------------------------------> Row 1 of 4 Table ==> TABLENAME Creator ==> USERID ------------------------------------------------------------------------------Cmd S N ONE N COLNAME ___ N 1 N CONTENT ___ N 2 N DATA ___ N 3 N INFO ___ Y N NAME ***************************** Bottom N COLNAME2 N CONTENT2 N DATA2 N INFO2 N NAME2 of Data **********************************
Valid Line Commands: Delete, Insert, Repeat, Undo, Copy, Before, After, Form
3. In the Edit table rows panel, type I in the Command (cmd) column of the row below which you want the new row to appear. Note: To remove the row that you inserted and exit the Edit Table Rows panel without committing your changes, type CANcel on the Command line. 4. Press the Enter key. A blank row appears below the row that you selected. 5. Enter data in any fields required in that row. For example, if one of the cells must have a value that is not null, you must enter a value in that cell. The changes that you have made will be committed in DB2 when you exit the table that you are editing. 6. To cancel the action that you have taken before you exit the table, enter the command to cancel (CANcel) on the command line and press Enter. You will exit the panel without committing the changes. Note: To insert more than one row into the table that you are editing, type I, followed by the number of new rows that you want to insert in the Command column of the row below which you want the new rows to appear. Note: You can insert a blank row into an empty table by opening an empty table from the DB2 Table EDitor main panel then, in the Edit Table Rows panel, type Insert on the command line. A blank row is inserted into the table.
Repeating rows
You can repeat one row or a range of rows using the Edit Table Rows panel.
287
The changes that you have made will be committed in DB2 when you exit the table that you are editing.
Copying rows
You can copy rows using the copy command from the Edit Table Rows panel.
To copy a row:
1. Type C in the Command column of the row that you want to copy. 2. Type A in the Command column of the row above which you want the row to be inserted, or, type B in the Command column of the row below which you want the row to be inserted. 3. Press the Enter key.
Deleting rows
You can delete a row or many rows using the Edit Table Rows panel.
288
Users Guide
To delete a row:
In an open table, type D in the Command (cmd) column of the row that you want to delete. Press the Enter key. DB2 Table Editor marks the selected row for deletion. The row will appear in green. The delete will be committed to the database when you exit the table.
Undoing an action
You can undo an action before it is committed. You can undelete a row before committing the delete to the database, remove an inserted row before the insert has been committed to the database, and undo changes that have been made.
To undo an action:
In an open table, type U in the Command (cmd) column of the row that contains the result of the action that you want to undo. For example, if you wanted to undo an insert, you would type U in the command column of the row that was inserted. Press the Enter key.
289
1 1 Save changes 2 Discard changes 2 1 Abort on error 2 Return to edit on error COMMIT every 1____ (0-32767) rows
The fields on the Confirmation panel are listed and described in the following table (Fields on the Confirmation panel and their descriptions ).
Table 21. Fields on the Confirmation panel and their descriptions Field Save changes Discard changes Abort on error Return to edit on error Commit everyx rows Description Type 1 to commit the changes that you have made to DB2. Type 2 to prevent the changes that you have made from being committed to DB2. The DB2 transaction will be aborted if an error is encountered. If an error is encountered, the editor will open and all uncommitted rows that contain a change will be displayed. Type the number of rows after which you would like DB2 to commit your changes. For example, if you type 5 in the Commit every x rows field, your changes will be committed every 5 rows. If you type 0, your changes will be committed at the end of the table.
The following keywords can be used with the FIND command: NEXT PREV FIRST LAST ALL Use this to find the next instance of the string that you are searching for. Use this to find the previous instance of the string that you are searching for. Use this to find the first instance of the string that you are searching for. Use this to find the last instance of the string that you are searching for. Use this to find all of the instances of the string that you are searching for. The total number of occurrences of the found string appears in the upper right-hand corner of the panel when using the FIND ALL command.
The results of the find command are highlighted in white. If no keyword is specified, the next occurrence of the find string will be found. You can search for strings with spaces or multiple words by enclosing the string in single quotes. Tip: If the text that you are searching for is the same as one of the keywords, issue the find command as follows:
FIND first FIRST
290
Users Guide
This command will find the first instance of the word first.
To search a table:
1. On the command line, in an open table, type FIND followed by the text string that you want to find. If you are searching for a text string that includes spaces, enclose the string in single quotes. Note: to search for a text string that contains spaces, enclose the text string in single quote marks. (See example below). For example, if you want to find all occurrences of the text JENNIFER SMITH, type FIND JENNIFER SMITH ALL on the command line. 2. Press the Enter key. DB2 Table Editor moves the cursor to the first occurrence of the text you typed and highlights the text in white. Note: To find the next occurrence of the text that you specified press PF5 or type rfnd on the command line. Tip: Searching is case sensitive, so be sure to use the correct case when typing the text string that you want to search for. Searching a column in a table: Find command
F text string column name or number
Note: to search for a text string that contains spaces, enclose the text string in single quote marks. (See example below). 1. On the command line, type F followed by the text string that you want to find followed by the name or number of the column in which you want to search. If you are searching for a text string that includes spaces, enclose the string in single quotes. For example, if you want to find the text JENNIFER SMITH in the employee column, type
F JENNIFER SMITH employee
on the command line. Tip: Searching is case sensitive, so be sure to use the correct case when typing the text string that you want to search for. 2. Press the Enter key. DB2 Table Editor moves the cursor to the first occurrence of the text that you typed and highlights the text in white. Note: To find the next occurrence of the text that you specified press PF5 or type rfnd on the command line. Searching a table and changing the contents of cells in the table: You can search a table and replace the contents of a cell using the change command. Change
(1) C text string A text string B (2)
291
Notes: 1 2 Where text string A is the text that you are searching for. Where text string B is the text that will replace text string A.
You can change all occurrences of one text string to another text string with the change all command. Change all
(1) C text string A text string B (2) ALL
Notes: 1 2 Where text string A is the text that you are searching for. Where text string B is the text that will replace text string A.
To search a table and change the contents of a cell: 1. On the command line, type C, followed by the text that you want to change, followed by the text that you want to change it to. If either text string contains spaces, enclose the text string in single quotes. For example, if you want to find the text JENNIFER SMITH and change it to JENNIFER JONES, type C JENNIFER SMITH JENNIFER JONES on the command line. Tip: Searching is case sensitive, so be sure to use the correct case when typing the text string that you want to search for. 2. Press the Enter key. DB2 Table Editor changes the first occurrence of the text that you specified and highlights the changed row in yellow. Note: To find and change the next occurrence of the text that you specified, press PF6. Searching a table and changing the contents of cells in the table: You can search a table and replace the contents of a cell using the change command. Change
(1) C text string A text string B (2)
Notes: 1 2 Where text string A is the text that you are searching for. Where text string B is the text that will replace text string A.
You can change all occurrences of one text string to another text string with the change all command. Change all
292
Users Guide
(2) ALL
Notes: 1 2 Where text string A is the text that you are searching for. Where text string B is the text that will replace text string A.
Searching a table and changing the contents of all cells that match the search criteria: 1. On the command line, type: C, followed by the text that you want to change, followed by the text that you want to change it to followed by ALL. If either text string contains spaces, enclose the text string in single quotes. For example, if you want to find all of the instances of the text 4500 and change them to 5600, type C 4500 5600 ALL on the command line. Tip: Searching is case sensitive, so be sure to use the correct case when typing the text string that you want to search for. 2. Press the Enter key. DB2 Table Editor changes all of the occurrences of the first text string that you specified to the second text string that you specified and highlights the changed rows in yellow. Note: If a match is found in a truncated cell, (a cell that contains data that is too long to appear on the screen) the row will be highlighted and the cursor will be positioned at the beginning of the row. You can edit the cell by using the zoom command. Searching a table and changing the contents of all cells within a column that match the search criteria: You can search for and replace the text that matches your search criteria within a specified column using the change all in column command. Change all
(1) C text string A text string B (2) ALL column name or number
Notes: 1 Where text string A is the text that you are searching for.
2 Where text string B is the text that will replace text string A. 1. On the command line, type: C, followed by the text that you want to change, followed by the text that you want to change it to followed by ALL followed by the name or number of the column in which you want the changes to be made. If either text string contains spaces, enclose the text string in single quotes. For example, if you want to find all of the instances of the text 4500 and change them to 5600 that occur in column 14, type C 4500 5600 ALL 14 on the command line. 2. Press the Enter key. DB2 Table Editor changes all of the occurrences of the first text string that you specified to the second text string that you specified in the specified column and highlights the changed rows in yellow.
293
Note: If a match is found in a truncated cell, (a cell that contains data that is too long to appear on the screen) the row will be highlighted and the cursor will be positioned at the beginning of the row. You can edit the cell by using the zoom command.
HELP
CSET options where you can find additional information about each of these options. 1CFIX Enables you to fix and unfix columns. 2CORDER Enables you to reposition columns. 3CSIZE Enables you to change the displayed width of columns. 4CSORT Enables you to select one or more columns for sorting and thus modify the order of the rows displayed.
294
Users Guide
5CRESET Enables you to reset all customizations. 6CREMOVE Enables you to remove all customizations. 7PVIEW Enables you to toggle between permanent view and temporary view. 2. Type the number corresponding to the option you want to access in the Command line and press Enter. Note: You can also directly invoke each CSETUP option by typing the corresponding command (for example, CFIX, CORDER, CSIZE, CSORT, CRESET, CREMOVE, or PVIEW) in the option line on any dynamic display and pressing Enter.
Fixing a column
The CFIX option enables you to fix and unfix columns. A fixed column is always located at the far left side of the display. It does not shift horizontally (as unfixed columns do) when scrolling to the left or right. INNER COLUMN SCROLLING and CEXPAND may be used on a fixed column if the column is narrower than its maximum width. Certain columns may be permanently fixed in the report and cannot be unfixed by the user. Such a column has a fix status of P (permanently fixed). A column cannot be fixed if it is larger than the available display area. There are also restrictions for fixing columns related to the size requirements of other columns. 1. ype CFIX in the option line on any display panel and press Enter. The Define Fixed Columns panel displays.
CFIX ------------------ Define Fixed Columns -------------- YYYY/MM/DD HH:MM:SS Option ===> Scroll ===> PAGE -----------------------------------------------------------------------+> ROW 1 OF 9 Column Function ===> 1 (1-Fix/Unfix, 2-Order, 3-Size, 4-Sort) Permanent View ===> Y (Y-Perm, N-Temp) Reset View ===> N (Y,N) Device_Width : 80 Old_Fixed_Width: 37 Old_Unfixed_Width: 43 New_Fixed_Width: New_Unfixed_Width: ------------------------------------------------------------------------------Cmd New Old Len Column_Name P P P 5 CMD P P P 32 NAME _ 10 CREATOR _ 5 UPDT _ 32 DESCRIPTION _ 10 LAST_USER Enter: Process selections; PF3: Exit and save; CAN: Exit without save Line Cmds: F Fix U Unfix
Fields and descriptions for the Define Fixed Columns pane Column Function Enables you to jump to any of the CSET functions by typing in the appropriate number. The number corresponding to the current option displays in this field. Valid options are: v 1Provides access to the CFIX option.
Chapter 7. The DB2 Table Editor ISPF component
295
v 2Provides access to the CORDER option. v 3Provides access to the CSIZE option. v 4Provides access to the CSORT option. Permanent View Indicate whether or not the view you define is permanent or temporary. Valid values are: v YView customizations are permanent. v NView customizations are temporary. Reset View Resets all customizations. Device_Width Shows the current display device size (panel width). Old_Fixed_Width Shows the sum of the FIXED column widths prior to any changes in the current CFIX panel. Old_Unfixed_Width Shows the sum of the FIXED column widths prior to any changes in the current CFIX panel. Old_Unfixed_Width Shows the UNFIXED area prior to any changes in the current CFIX panel. Old_Unfixed_Width = Device_Width - Old_Fixed_Width. New_Fixed_Width Shows the sum of the FIXED column widths that will result if the FIX/UNIFIX changes are saved. New_Unfixed_Width Shows the UNFIXED area that will result if the FIX/UNFIX changes are saved. New_Unfixed_Width = Device_Width - New_Fixed_Width. Cmd New Old Len Field where you specify line commands. Valid line commands are F (fix) and U (unfix). Displays the new view settings. Displays the previous view settings. Shows the length of the column.
Column_Name Shows the name of the column. 2. Type F in the Cmd field next to column(s) you want to fix. 3. Type U in the Cmd field next to column(s) you want to unfix. 4. Press Enter. The changed values display in the New column next to the corresponding column(s). 5. Press PF3 to save changes and return to the display panel.
Repositioning columns
The CORDER option enables you to reposition report columns. If any columns are fixed, they are grouped together as the leftmost report columns. The unfixed columns are grouped together to the right of any fixed columns.
296
Users Guide
CORDER does not move a column out of its group. A fixed column cannot be relocated to the right of an unfixed column. Likewise, an unfixed column cannot be relocated to the left of a fixed column. 1. Type CORDER in the option line on any display panel and press Enter. The Define Column Display Order panel displays.
CTCORD ----------------- Define Column Display Order ----- YYYY/MM/DD HH:MM:SS Option ===> Scroll ===> PAGE -----------------------------------------------------------------------> ROW 1 OF 9 Column Function ===> 2 (1-Fix/Unfix, 2-Order, 3-Size, 4-Sort) Permanent View ===> N (Y-Perm, N-Temp) Reset View ===> N (Y,N) Cmd Fix New Old Column_Name ___ P 1 CMD ___ P 2 NAME ___ 3 CREATOR ___ 4 UPDT ___ 5 DESCRIPTION ___ 6 LAST_USER ___ 7 LAST_UPDATED ___ 8 CRTD_USER ___ 9 CREATED_USER ***************************** Bottom of Data ********************************** Enter: Process selections; PF3: Exit and save; CAN: Exit without save Line Cmds: Specify number for column position
Define Column Display Order field descriptions Column Function Enables you to jump to any of the CSET functions by typing in the appropriate number. The number corresponding to the current option displays in this field. Valid options are: v 1Provides access to the CFIX option. v 2Provides access to the CORDER option. v 3Provides access to the CSIZE option. v 4Provides access to the CSORT option. Permanent View Indicate whether or not the view you define is permanent or temporary. Valid values are: v YView customizations are permanent. v NView customizations are temporary. Reset View Resets all customizations. Cmd Fix Field where you specify the number for column position. Displays fixed columns. Valid values are: v FIndicates the column is fixed. v PIndicates the column is permanently fixed. Displays the new view settings. Displays the previous view settings.
New Old
297
Column_Name Shows the name of the column. 2. Type a number next to a column to specify its order. 3. Press Enter. The new column order numbers display in the New column next to each column. 4. Press PF3 to return to the display panel.
Resizing columns
The CSIZE option enables you to change the displayed width of columns. This function is primarily intended for non-numeric data where there are large blank areas in all (or most) rows in a given column. Although the displayed width may change, the underlying data does not change. If a columns size is less than the column maximum, it is possible that some date is not displayed. INNER COLUMN SCROLLING and CEXPAND can be used to see data outside the display range of the resized column. 1. Type CSIZE in the option line on any display panel and press Enter. The Define Column Size panel displays:
CSIZE -------------------- Define Column Size ------------- YYYY/MM/DD HH:MM:SS Option ===> Scroll ===> PAGE -------------------------------------------------------------------------- +> ROW 1 OF 9 Column Function ===> 3 (1-Fix/Unfix, 2-Order, 3-Size, 4-Sort) Permanent View ===> N (Y-Perm, N-Temp) Reset View ===> N (Y,N) Device_Width : 80 Old_Fixed_Width: 37 Old_Unfixed_Width: 43 New_Fixed_Width: New_Unfixed_Width: ------------------------------------------------------------------------------Cmd New 5 32 10 5 32 10 Old 5 32 10 5 32 10 Min 5 32 10 5 32 10 Max Fix Column_Name 5 P CMD 32 P NAME 10 CREATOR 5 UPDT 32 DESCRIPTION 10 LAST_USER
Enter: Process selections; PF3: Exit and save; CAN: Exit without save Line Cmds: Column size, between MIN and MAX
Define Sort Columns field descriptions Column Function Enables you to jump to any of the CSET functions by typing in the appropriate number. The number corresponding to the current option displays in this field. Valid options are: v 1Provides access to the CFIX option. v 2Provides access to the CORDER option. v 3Provides access to the CSIZE option. v 4Provides access to the CSORT option. Permanent View Indicate whether or not the view you define is permanent or temporary. Valid values are:
298
Users Guide
v YView customizations are permanent. v NView customizations are temporary. Reset View Resets all customizations. Device_Width Shows the current display device size (panel width). Old_Fixed_Width Shows the sum of the FIXED column widths. Old_Unfixed_Width Shows the UNFIXED area. New_Fixed_Width Shows the sum of the FIXED column widths. New_Unfixed_Width Shows the UNFIXED area. Cmd New Old Min Max Fix Field where you specify the number for column position. Displays the new view settings. Displays the previous view settings. Displays the minimum column length. Displays the maximum column length. Displays fixed columns. Valid values are: v FIndicates the column is fixed. v PIndicates the column is permanently fixed.
Column_Name Shows the name of the column. 2. Type the desired column size in the Cmd field next to the column you want to resize. Note: The column size you specify must be between the Min and Max values shown for that column. 3. Press Enter. The new view criteria display in the New column. 4. Press PF3 to return to the display panel.
Sorting
CSORT functionality enables you to select one or more columns for sorting and thus modify the order of the rows displayed on many of DB2 Test Database Generators product panels. Columns are selected by sort priority and direction. Direction is either ascending (default) or descending. When more than one column is selected for sorting, the second column only differentiates when rows have matching data in the first column. Similarly, a third column only impacts the sort when data in both the first two columns are identical. A maximum of nine columns can be selected for sorting at one time. Internal requirements may create a smaller maximum. A message is issued if the maximum number of columns selected for sorting is exceeded. 1. Type CSORT in the option line on any display panel and press Enter. The Define Sort Columns panel displays:
299
SORT -------------------- Define Sort Columns ------------ YYYY/MM/DD HH:MM:SS Option ===> Scroll ===> PAGE -----------------------------------------------------------------------> ROW 1 OF 9 Column Function ===> 4 (1-Fix/Unfix, 2-Order, 3-Size, 4-Sort) Permanent View ===> N (Y-Perm, N-Temp) Reset View ===> N (Y,N) Stop Sorting ===> N (Y,N) Cmd Dir New Old Column_Name CMD _ _ NAME _ _ CREATOR _ _ UPDT _ _ DESCRIPTION _ _ LAST_USER _ _ LAST_UPDATED _ _ CRTD_USER _ _ CREATED_USER Enter: Process selections; PF3: Exit and save; CAN: Exit without save Ord: 1-9 Dir: A Asc D Desc
Define Sort Columns field descriptions Column Function Enables you to jump to any of the CSET functions by typing in the appropriate number. The number corresponding to the current option displays in this field. Valid options are: v 1Provides access to the CFIX option. v 2Provides access to the CORDER option. v 3Provides access to the CSIZE option. v 4Provides access to the CSORT option. Permanent View Indicate whether or not the view you define is permanent or temporary. Valid values are: v YView customizations are permanent. v NView customizations are temporary. Stop Sorting Indicates whether or not to stop sorting as specified. Valid values are: v YStop sorting. v NContinue sorting. Cmd Dir Field where you specify the sort order. Specifies the lexicographic order for the column. Valid values are: v A(Default) Values are listed in ascending order, smallest to largest. v DValues are listed in descending order, largest to smallest. Displays the new view settings. Displays the previous view settings.
New Old
Column_Name Shows the name of the column. 2. Type A or D in the Cmd field next to the columns on which you want to base your sort.
300
Users Guide
3. Press Enter. The new sort preferences are displayed in the New column. 4. Press PF3 to return to the display panel.
Restrictions
The following restrictions apply to CSET options: v Total fixed column sizes cannot exceed panel width. v Total fixed column sizes must leave enough unfixed space for the minimum allowed size for all unfixed columns. If a column is not eligible for resizing, the columns minimum size requirement is the same as its maximum size. Minimum and maximum sizes for all columns are shown in the CSIZE display. v If a column has been resized, then its current width is treated as its current width is treated as its smallest allowable size. When a column is resized its current size must fit on the panel completely. For example, on an 80-byte panel with no fixed columns, a 128-byte column can only be resized to 80 bytes or less (assuming no conflicting minimum size associated with the column). If there were two 10-byte fixed columns, for a total fixed area size of 20-bytes, the 128-byte column would be limited to 60 bytes or its minimum allowed size, whichever was smaller.
301
Table 22. The use of color in DB2 Table Editor (continued) Color Yellow Meaning Indicates one of two things: v The value has been updated v The row has been inserted Green White The row is marked for deletion The column is truncated. (Truncated columns can be edited using the Zoom command (or pressing PF4))
Highlighted in white Indicates that the highlighted text has been found by the Find or Find all command.
302
Users Guide
EX To start DB2 Table Editor, run the SETISAMP &CLIST(ETI) library member ETI. S ABOUT To set up the configuration file, type S on the command line.
To display the IBM copyright notice, type ABOUT Main Panel on the command line. This information is also displayed when you start the product the first time. To return to the previous screen, press the PF3 key. Main Panel
To select and re number all columns type Select Columns panel INCLUDE ALL on the command line and the Select column will be renumbered. If two ore more columns has the same number, the order in which they appear on the screen will prevail. To have all columns excluded from the generated table, type EXCLUDE ALL on the command line and an N will appear in the Select column next to all rows. Type E on the command line to edit the table in the Edit Table Rows panel. Type B on the command line to browse the table in the Edit Table Rows panel. Type F on the Cmd line of the row that you want to enter in the Edit Table Rows panel to edit the row in form format. Select Columns panel
EXCLUDE ALL
Select Columns panel and Generated Select Statement panel Select Columns panel and Generated Select Statement panel Edit Table Rows panel
FORM
Type FORM on the command line of the Edit Edit Table Rows panel Table Rows panel to edit the first row listed on the panel in form format. This allows you to edit rows one at a time. Type SQL on the command line of the Select Columns panel to open the Generated Select Statement panel. From this panel you can edit the SQL Select Columns panel
SQL
SAVE
Type SAVE on the command line of the Select Select Columns panel Columns panel or the Generated Select Statement and Generated Select panel to save your SQL for future use. Statement panel Type LOAD on the command line of the Select Select Columns panel Columns panel or the Generated Select Statement and Generated Select panel to load SQL that you have previously saved. Statement panel Type COUNT on the command line to display a popup box indicating the number of rows that will be returned by your SQL statement. Select Columns panel and Generated Select Statement panel
LOAD
COUNT
303
Table 24. DB2 Table Editor Commands (continued) Command Function Panel where available Edit Table Rows panel
ZOOM, PF4, To view or edit entire contents of a long cell, and or HEX additional information about the cell, type ZOOM or HEX on the command line or press the PF4 key. For more information on using this command see Editing a long cell. You can change the command name of this command on the Update Parameters for DB2 Subsystem panel accessible my typing S, then 2 on the command line. For more information on changing the command name for the Zoom command, see Step 3. Set the DB2 subsystem parameters. HEX ON HEX OFF CAPS ON CAPS OFF
In the Zoom Panel, to edit a row with a hex editor, ZOOM panel type HEX ON on the command line. In the Zoom Panel, to turn the hex editor off, type HEX OFF on the command line. To force all changes to capital letters, type CAPS ON. on the command line. To resume entering data using uppercase and lowercase letters, type CAPS OFF on the command line. To turn on checking (checking checks the screen for edit errors), type CHECK ON on the command line. ZOOM panel Edit Table Rows panel and ZOOM panel Edit Table Rows panel and ZOOM panel Edit Table Rows panel
CHECK ON
CHECK OFF To turn off checking (checking checks the screen for edit errors), type CHECK OFF on the command line. I To insert a new row into the table that you are editing, type I in the Command column of the row below which you want to insert a new row. For more information on using this command, see Inserting a blank row.
I<nn>
To insert more than one row into the table that you Edit Table Rows panel are editing, type I, followed by the number of new and Generated Select rows that you want to insert in the Command Statement panel column of the row below which you want the new rows to appear. To repeat a row, type R in the Command column Edit Table Rows panel of the row that you want to repeat.Repeating rows. and Generated Select Statement panel To insert a repeated row more than once, type R in the Command column of the row that you want to repeat, followed by the number of times that you want to repeat that row. To repeat a range of rows between two specified rows, type RR in the Command columns of two different rows. Edit Table Rows panel and Generated Select Statement panel Edit Table Rows panel and Generated Select Statement panel
R<nn>
RR
304
Users Guide
Table 24. DB2 Table Editor Commands (continued) Command C Function Panel where available
To copy a row, type C in the Command column of Edit Table Rows panel the row that you want to copy, then type A in the Command column of the row above which you want the row to be inserted, or, type B in the Command column of the row below which you want the row to be inserted. To copy more than one row at a time, type C in Edit Table Rows panel the Command column of the row that you want to copy, followed by the number of rows that you want to copy, then type A in the Command column of the row above which you want the rows to be inserted, or, type B in the Command column of the rows below which you want the row to be inserted. To copy all rows between two specified rows, type CC in the Command columns of two different rows, then type A in the Command column of the row above which you want the rows to be inserted, or, type B in the Command column of the row below which you want the rows to be inserted. To delete a row, type D in the Command column of the row that you want to delete. For more information on using this command, see Deleting rows. To delete more than one row, type D in the Command column of the row that you want to delete, followed by the number of rows that you want to delete. Edit Table Rows panel
C<nn>
CC
Edit Table Rows panel and Generated Select Statement panel Edit Table Rows panel and Generated Select Statement panel
D<nn>
DD
To delete all rows between two specified rows, Edit Table Rows panel type DD in the Command columns of two different and Generated Select rows to delete the range of rows in between those Statement panel two rows. To undo an action previously performed on a row, type U in the Command column. For more information on using this command, see Undoing an action. Type U in the Command column of the row for which you want to undo an action, followed by the number of rows for which you want to undo actions. Edit Table Rows panel
U<nn>
UU
Type UU in the Command columns of two different Edit Table Rows panel rows to undo the previous actions for the range of rows in between those two rows. Type F followed by the text that you want to All panels search for, enclosed in quotes followed by the keyword. The FIND command supports the NEXT, PREV, FIRST, LAST, and ALL keywords. For more information on using this command, see Searching a table using the FIND command.
305
Table 24. DB2 Table Editor Commands (continued) Command F <text string> <column name or number> PF5 Function To search for a text string within a specified column, type F, followed by the text string for which you want to search, followed by the column name or number in which you want to search. To find the next occurrence of the text string that you were searching for using the Find command, press the PF5 key. Panel where available Edit Table Rows panel
C <text To change one text string to a new value, type C string> <new followed by the text string that you want to text string< replace, followed by the text string that you want to replace it with. For more information on using this command, see Searching a table and changing the contents of cells in the table PF6 To change the next occurrence of the text string that you were searching for using the Change command, press the PF6 key.
To change all matching text strings to a new value, Edit Table Rows panel type C, followed by the text string that you want to replace, followed by the text string that you want to replace it with. For more information on using this command, see To search a table and change the contents of all cells that match. To change all matching text strings that are found in a specified column to a new value, type C followed by the text string that you want to replace, followed by the text string that you want to replace it with followed by ALL followed by the name or number of the column in which you want the changes to be made. Edit Table Rows panel
C <text string> <new text string> ALL <column name or number> CANcel
Type CANcel on the Command line to exit the Edit Edit Table Rows panel Table Rows panel without committing the changes that were made. Print the contents of any scrollable area of the All scrollable panels. screen that displays tabular data. The contents of the current view are sent to a SYSOUT file allocated to your user ID. The name of the SYSOUT file is dynamically created by the system in the format SYSnnnnn, where nnnnn is a decimal between 1 and 99999. To view the output of a PRINTX command, choose the SDSF option on the ISPF main menu and select your active TSO ID. The attached SYSOUT file contains the information that PRINTX captured.
PRINTX
306
Users Guide
307
To perform main tasks in windows by using the keyboard instead of the mouse, use the keyboard shortcuts that are listed in the following table (Keyboard shortcuts for windows):
Table 26. Keyboard shortcuts for windows Action Display Help Close the active window Refresh displayed data Cut Copy Paste Print Shortcut F1 Ctrl+W or Alt+F4 F5 Ctrl+X Ctrl+C Ctrl+V Ctrl+P
To perform main tasks in dialogs by using the keyboard instead of the mouse, use the keyboard shortcuts that are listed int he following table (Keyboard shortcuts for dialogs):
Table 27. Keyboard shortcuts for dialogs Action Confirm a dialog Cancel a dialog Activate a button that has the focus Select and deselect check boxes and radio buttons Navigate within check box and radio button groups Open combination box menu Close combination box menu Move up and down in combination box menu Activate combination box menu item Move within a list box Activate a list box entry Move between the pages of a window containing tabs if the tab has the focus Shortcut Enter Esc Spacebar or Enter Spacebar Arrow keys Alt+down arrows Esc Up arrow, down arrow Enter Up arrow, down arrow Enter Right arrow, left arrow
308
Users Guide
Chapter 9. Troubleshooting
This section contains information on problems that can occur while using the DB2 Table Editor Administrative Console Component, Developer Component, DB2 Table Editor Windows User Component and Java Player Component and their solutions. This section contains information on frequently asked questions and common problems when using the DB2 Table Editor graphical user interface.
309
Cause Either Java 2 runtime environment is not installed on your machine or it is not enabled in Microsoft Internet Explorer. Action Ensure that Java 2 (JRE V 1.3.1 or higher) is installed on your machine and enabled in Microsoft Internet Explorer. This can be accomplished as follows: 1. 1. In Microsoft Internet Explorer, select Tools --> Internet Options. The Internet options window opens. Click the Advanced tab. In the settings list, scroll down until you find the Java (Sun) section. Ensure that the Use Java 2 v1.4.1_02 for <applet> check box is checked. Note: the name of this check box contains the version of the JRE that you have installed. Any version above V1.3.1 is sufficient. Ensure that the check box is checked, if the check box is not present, or references a version of the JRE that is below V 1.3.1, go to step 2. 2. Download and install a Java 2 JVM. Installing this JVM will automatically update the Java plug-in in your Internet Explorer browser. A Java 2 JVM (V1.4.1_02) that can be downloaded from java.sun.com. 3. In Microsoft Internet Explorer, select Tools --> Internet Options. The Internet options window opens. Click the Advanced tab. In the settings list, scroll down until you find the Java (Sun) section. Ensure that the Use Java 2 v1.4.1_02 for <applet> check box is checked. Note: the name of this check box contains the version of the JRE that you have installed. Any version above V1.3.1 is sufficient.
Working with date format data in the DB2 Table Editor Windows user component
When inserting or updating timestamps the following format should be used:
yyyy-mm-dd-hh.mm.ss.ffffff
Working with timestamps in the DB2 Table Editor Java Player component
When working with timestamps in the Java Player component, you must use the following format:
yyyy-mm-dd hh:mm:ss.fffffffff
310
Users Guide
http://www.dbcenter.cise.ufl.edu/triggerman/InfoShelf/gls/01.fm4.html#153039
Chapter 9. Troubleshooting
311
312
Users Guide
Appendix A. Messages
The error messages that can occur in DB2 Table Editor are described in this topic. All of the messages that are generated by DB2 Table Editor have a severity code printed as the last character of the message ID. The severity codes are described in the following table:
Table 28. Error message severity codes Severity Code I W E Description Information only. No user action required. Warning message. Results may not be as expected. Error message. Some may be user-correctable, read the User Response to determine the course of action.
Explanation: A value other than S, E, or N was specified. Only a value of S, E, or N is valid. User response: Specify S to indicate that the table should be locked in share mode during editing, specify E to indicate that the table should be locked in exclusive mode during editing or specify N to indicate that the table should not be locked during editing. ETI006E Invalid Value - Please enter the maximum number of rows you would like to fetch for your browse/edit session
Explanation: Informational message detailing the copyrights for DB2 User response: None required. ETI002E A valid DB2 subsystem is required. Please enter a valid DB2 subsystem
Explanation: The DB2 Subsystem that was specified is not valid. User response: Specify a valid DB2 subsystem. ETI003E Invalid Value - Please enter a Y if you would like commas to be shown in large numbers. Enter a N if you so not wish to see commas.
Explanation: The value specified was not valid. User response: Type the number of rows that you would like to fetch at a time for browsing or editing. ETI007E Invalid Value - Please enter a Y if you would like the options on this screen to be saved in your ISPF profile or N to bypass saving options
Explanation: A value other than Y or N was specified. Only a value of Y or N is valid. User response: Specify Y to indicate that you want commas to be shown or N to indicate that you do not want commas to be shown.
Explanation: A value other than Y or N was specified. Only a value of Y or N is valid. User response: Specify Y to have the options that you specified on this screen saved in your ISPF profile. Specify N if you do not want to save the specified options.
313
ETI008E
No entries match the entered like criteria. Please enter valid like criteria for the table creator and table name.
WHERE clause will use the OR operand between the specified columns. ETI014I Fetch Limit Reached - Processing has halted due to the number of rows fetched exceeded the fetch limit you entered on the main menu
Explanation: The specified criteria were not found or were invalid. User response: Specify valid like criteria. ETI009E It is not possible to perform a LOCK operation on a VIEW. Please turn off locking or select a Table.
Explanation: LOCK operations can only be performed on Tables, not on Views. User response: To perform a LOCK, select a table to lock. ETI010E Invalid Value - The Order By nbr must be numeric. Please enter the number you would like the column sort in
Explanation: Processing has stopped because the fetch limit that was specified from the DB2 Table Editor main menu has been reached. The fetch limit specifies the maximum number of rows that will be returned by DB2 Table editor. User response: No action is required, however, if you want to retrieve more rows, you can change the fetch limit from the DB2 Table Editor main menu. ETI015E Invalid Value - Please enter a value from 1 to 32768 which is the maximum nbr of characters you want to display for character and varchar type data
Explanation: The order by number that was specified is not numeric. User response: Specify a numeric value in the order by field. ETI011E Invalid Value - Please enter an A if you would like the column sorted in Ascending sequence or D if you would like the column sorted in a Descending sequence
Explanation: The value specified for the number of characters to be displayed for character and varchar data types is invalid. Values from 1 to 32768 are valid. User response: Specify a value from 1 to 32768. ETI016E Invalid Command - The command you entered is not valid for this screen. Please reenter a valid command
Explanation: A value other than A or D was specified. Only a value of A or D is valid. User response: Specify A to have the column sorted in ascending order. Specify D to have the column sorted in descending order. ETI012E You have performed an edit on a row that is not updatable.
Explanation: The command that you specified is not valid on this screen. User response: specify a valid command. For information on valid commands, see the online help for this screen. ETI017E Invalid Line Command - The command you entered is not valid for this Line. Please reenter a valid command
Explanation: The row that you edited is not updatable. Your edits will not be committed. Only updatable rows can be edited. User response: Select an updatable row to edit. ETI013E Invalid Value - Please enter an A if you want the WHERE clause to use the AND operand between different columns or O to use the OR operand
Explanation: The command that you specified is not valid on this line. User response: specify a valid command. For information on valid commands, see the online help for this screen. ETI018E The Cursor Must be on a Column or Column Heading in the Display to perform this command.
Explanation: A value other than A or O was specified. Only a value of A or O is valid. User response: Specify A to indicate that the WHERE clause will use the AND operand between the specified columns. Specify O to indicate that the
Explanation: The cursor was not on a column or column heading in the display when you attempted o perform this command. User response: Place the cursor on on a column or column heading and attempt the command again.
314
Users Guide
ETI019E
Invalid reply - Enter a Y if you would like to continue fetching rows or N to display the rows that have been fetched so far. Enter C if you would like to return without working with data.
ETI024
Explanation: The length of the column exceeds the specified column definition length. User response: Shorten the length of the column or extend the length in the column definition. ETI025 Null column Column currently null. Reset null indicator on panel to override
Explanation: An invalid reply was specified. Valid replies are Y, N, or C. User response: Specify Y to indicate that you want to continue fetching rows. Specify N to indicate that you want the rows that have been fetched to be displayed. Specify C to indicate that you want to return without working with the fetched data. ETI020 Invalid hex character Invalid hexadecimal character entered
Explanation: The null column has a null value. User response: Reset the null indicator on the panel to override this message. ETI026 Invalid Primary Command Valid Primary Commands are Zoom, Browse, Edit, Find, Change, FORM, and Caps
Explanation: The hexadecimal character specified is not valid. User response: Specify a valid hexadecimal character. ETI021 Invalid command Valid commands are CANCEL, COLS, END, FIND, HEX, and SAVE
Explanation: An invalid primary command was specified. The valid primary commands are: v Zoom v Browse v Edit v Find v Change v FORM v Caps User response: Specify a valid command. ETI027 Invalid parameter Invalid parameter passed to LOCATE
Explanation: An invalid command was specified. The following commands are valid: v CANCEL v COLS v END v FIND v HEX v SAVE User response: Specify a valid command. ETI022 Unrecognized parameter Valid parameters are OFF/ON
Explanation: An invalid parameter was specified. User response: Specify a valid parameter. ETI028E Insufficient Storage - Your TSO session does not contain enough storage to display the data you selected. Lower the fetch limit on the main menu and try your request again.
Explanation: The parameter that was specified is not recognized. User response: Specify a valid parameter. Valid parameters are OFF and ON. ETI023 Data saved Column data saved for update
Explanation: Your TSO session does not contain enough storage to display the data that you selected. User response: Lower the fetch limit on the DB2 Table Editor main menu and try your request again. ETI029E Invalid Decimal Point Character - Enter a character that is not a number, E, +, -, _ and not equal to the Separator Character.
Explanation: Column data has been saved. the Column will be updated. User response: No action required.
Explanation: The character that you specified as the decimal character is not a valid decimal character. The
Appendix A. Messages
315
following characters are not valid as a decimal character: v a number v E v + v - v _ v the Separator Character User response: Specify a valid decimal character. ETI030 Invalid Subsystem The plan name for the table editor could not be fetched from the control file. Make sure the plan name and subsystem are correct.
v + v - v _ v the decimal character User response: Specify a valid decimal character. ETI035 The Range of a Datatype of INTEGER is -2147483648 thru 2147483647
Explanation: The value specified for the integer is out of range. The valid range for an INTEGER is -2147483648 thru 2147483647. User response: Specify a valid value for the INTEGER. ETI036 The Range of a Datatype of SMALLINT is -32768 thru 32767
Explanation: The plan name for DB2 Table Editor could not be fetched from the control file. User response: Check the control file to be sure that the DB2 Table Editor plan name and subsystem are correct. ETI031 Invalid value Enter either a Y or N for the null indicator value
Explanation: The value specified for the SMALLINT is out of range. The valid range for an SMALLINT is -32768 thru 32767. User response: Specify a valid value for the SMALLINT. ETI037 An Overflow has Occurred - Please Re-Enter a Valid Floating Point Number
Explanation: The specified null indicator value is invalid. User response: Specify Y to indicate that the column can have a null value. Specify N to indicate that the column cannot have a null value. ETI032 Invalid length Enter a valid numeric value for the column length
Explanation: An overflow has occurred. User response: Specify a valid floating point number. ETI038 Invalid Data Entered for a Numeric Datatype
Explanation: The specified column length is invalid. User response: Specify a valid column length. Column lengths must be numeric. ETI033 Invalid length Invalid value entered for null indicated column
Explanation: The specified data is not valid NUMERIC data. User response: Specify valid NUMERIC data. ETI039 Expand Not Available for Floating Point Numbers
Explanation: The specified length is invalid for this null indicated column. User response: Specify a valid column length. ETI034E Invalid Separator Character - Enter a character that is not a number, E, +, - and not equal to the Decimal Point Character.
Explanation: The expand function is not available for floating point numbers. User response: Select an alternative function. ETI040 Invalid Null Value Entered
Explanation: The null value that was specified is invalid. User response: Specify a valid null value. ETI041I Your query did not return data. Use the INSERT command to insert a new row.
Explanation: The character that you specified as the decimal character is not a valid decimal character. The following characters are not valid as a decimal character: v a number v E
Explanation: The query that you ran did not return any data. If no data is returned, there is nothing to edit.
316
Users Guide
User response: If you want to insert data, use the INSERT command to insert a new row. ETI042E Unable to Save Data in Browse Mode
ETI049E
Explanation: The find command that was entered was not valid. User response: Specify a valid find command. For information on DB2 Table Editor ISPF component commands, see the documentation. ETI050 Enter a valid FIND command.
Explanation: Data cannot be saved when browsing. Data can only be saved when editing. User response: Switch to edit mode in order to save your data. ETI043I SQLID has been changed successfully
Explanation: The specified find command was not valid. User response: Specify a valid find command. ETI051E The INSERT command is disabled. You have chosen to exclude at least one column of data that is necessary to allow INSERT.
Explanation: You have successfully switched to a different SQLID. User response: None required. ETI044E An error occurred while updating the SQLID
Explanation: Your SQLID has not been updated. An error occurred while attempting the update. User response: Check your update request and attempt the update again. ETI045E You have entered an invalid COMMIT SCOPE
Explanation: The INSERT command is currently disabled because one or more columns of data that is necessary in order to perform an INSERT has been excluded. User response: Ensure that no necessary data columns are excluded. ETI052 Bottom of data reached.
Explanation: The value that you specified for the commit scope is invalid. The commit scope is the number of actions that must take place before a unit of work is completed and the data is committed to the DB2 database. User response: Specify a valid commit scope. In the Commit scope field, type the maximum number of rows to insert before committing changes to the database. ETI046E A row that you have modified is not updatable.
Explanation: You have reached the bottom of the data. User response: None required. ETI053 No changes were made.
Explanation: No changes were made to the data. User response: None required. ETI054 A match was found in truncated data.
Explanation: At least one of the rows that you modified is not updatable. User response: Select an updatable row to modify. ETI047 Your changes were NOT saved.
Explanation: A match to your search criteria was found in truncated data. User response: Use the ZOOM command to see the entire record. ETI055 Enter a valid CHANGE command.
Explanation: The changes that you made were not saved. User response: None required. ETI048E You must choose to edit at least one column.
Explanation: The change command that you specified is not valid. User response: Specify a valid change command. ETI056E You must insert at least one column of data.
Explanation: A column must be selected in order to edit data. User response: Select column to edit.
Explanation: In order to use the INSERT command you must specify at least one column of data to be inserted. When inserting a row you can leave it blank and DB2 Table Editor will insert the DEFAULT for the
Appendix A. Messages
317
row (if there is a default) by leaving the column out of the INSERT statement. However, you cannot leave out all columns, you must insert at least 1 column. User response: Specify a column for insertion. ETI057E Invalid Value - Please enter either Y or N.
ETI064
CHECK is OFF.
Explanation: Checking has been turned off. Checking checks the screen for edit errors. User response: None required. ETI065 CHECK must be ON before exiting. Use the CHECK ON command first.
Explanation: An invalid value was specified. Valid values are either Y or N. User response: Specify a valid value. ETI058 Enter a valid option.
Explanation: Checking must be on before you can exit this screen. Checking checks the screen for edit errors. User response: Turn checking on using the CHECK ON command. ETI066E Invalid Value - The values must be either 1 or 2.
Explanation: An invalid option was specified. User response: specify a valid option. ETI059E Invalid Value - The Select number must be numeric.
Explanation: Valid values are either 1 or 2. User response: Specify a value of 1 or 2. Select the number corresponding to the desired option. ETI067 There is not enough room to perform this CHANGE.
Explanation: The value specified for the Select number is invalid. The Select number must be a numeric value. User response: Specify a numeric Select number. ETI060E Invalid Value - The Frozen value must be Y or N.
Explanation: There is insufficient space to preform the requested change. User response: Ensure that there is sufficient space to run your command. ETI068 Command conflict.
Explanation: Valid values for the Frozen value are Y or N. User response: Specify a valid value for the Frozen value. ETI061 CAPS is ON.
Explanation: The specified command cannot be run at this time. User response: Specify a different command or attempt your command at another time. ETI069 Incomplete block command.
Explanation: All changes will be forced to capital letters, type CAPS ON. User response: None required. ETI062 CAPS is OFF.
Explanation: The specified command is incomplete. User response: Specify a complete block command. ETI070E It is not possible to enter BROWSE mode after making changes. Explanation: Caps lock is off, data can now be entered using uppercase and lowercase letters. User response: None required. ETI063 CHECK is ON.
Explanation: Once changes have been made, you cannot switch form Edit mode to browse mode. User response: None required. ETI071E It is not possible to perform a LOCK operation on a System Table. Please turn off locking or select a different Table.
Explanation: Checking has been turned on. Checking checks the screen for edit errors. User response: None required.
318
Users Guide
User response: Turn off locking or select a non-system table to edit while locking is turned on. ETI072 COPY is pending
User response: Specify a valid command. ETI078 You have chosen over 65 characters of frozen table space
Explanation: The requested copy is pending. User response: None required. ETI073E COMMIT SCOPE must be 1 to delete or update a duplicate row.
Explanation: Over 65 characters of frozen table space has been chose. A maximum of 65 characters of frozen table space can be selected. User response: Select less than 65 characters of frozen table space. ETI079 You have entered an invalid Column Name or Number.
Explanation: The commit scope is not set to 1. User response: To delete or update a duplicate row, set the commit scope to 1. ETI074 The Range of the Decimal exceeds the Tables Decimal Definition
Explanation: The column name or column number that was specified is invalid. User response: Check the column name and number. ETI080E SORT is not supported for the specified column.
Explanation: The range of the specified decimal is greater than the decimal definition of the table. User response: Specify a decimal range that is within the decimal definition of the table. ETI075E It is not possible to perform a LOCK operation on a Temporary Table. Please turn off locking or select a different Table.
Explanation: Sort cannot be performed on this column. User response: Select another column to sort. ETI081I At least one DEFAULT value will be used.
Explanation: The selected table is a temporary table and therefore, cannot be locked. User response: Turn off locking, or select a table that is not temporary. ETI076E There was an error allocating the DB2 Parms Control File DB2CNTFL DB2 Table Editor can not run without allocating a valid Control File. Please verify that the control file in your execution clist is correct.
Explanation: Not all values were specified. At least one default value will be used. User response: None required. ETI082I Your query returned no data. Browse data must have at least one row.
Explanation: The specified query did not return any data. User response: None required. ETI083 Invalid Primary Command Valid Primary Commands are Zoom, Browse, Edit, Find, and FORM
Explanation: The DB2 Parms Control File (DB2CNTFL DB2) cannot be allocated. DB2 Table Editor cannot run without allocating a control file. User response: Check that the control file specified in your clist is correct. ETI077 Invalid command Valid commands are CANCEL, END, FIND, and HEX ON/OFF
Explanation: The specified primary command was not valid. Valid primary commands are: v Zoom v Browse v Edit v Find v FORM User response: Select a valid command.
Explanation: The specified command is invalid. Valid commands are: v CANCEL v END v FIND v HEX ON v HEX OFF
Appendix A. Messages
319
ETI084E
The sign byte (the first bit) may only be a space or a negative sign.
ETI094E
Explanation: The specified sign byte is invalid. A sign byte (the first bit) can be either a space ( ) or a negative sign (-). User response: Specify a valid sign byte.
Explanation: Valid values are L or S. User response: Specify L to indicate a long data type. Specify S to indicate a short data type. ETI095E A row has either been changed or deleted by another user and cannot be deleted.
ETI085E
Explanation: The specified time stamp is invalid. The valid timestamp fomat is dependant on the default that is set for your subsystem. User response: Specify a valid time stamp. ETI086E This is an invalid date
Explanation: One of the rows that you are attempting to delete cannot be deleted because it has been changed or deleted by another user. User response: None required. ETI097E A row has either been changed or deleted by another user and cannot be updated.
Explanation: The specified date is invalid. The valid date fomat is dependant on the default that is set for your subsystem. User response: Specify a valid date. ETI087E This is an invalid time
Explanation: The row that you are attempting to update or delete cannot be found. It is possible that the row is being changed by another user. User response: Ensure that the row that you are attempting to update or delete exists. Also, you can change your DB2 Table Editor preferences so that table locking is used. This can prevent rows from being updated by more than one user at a time. Adding a primary key to the table that you are editing can also prevent this error from occurring. ETI098E This table contains an unknown column type. The table definition must be complete before continuing.
Explanation: The specified time is invalid. The valid time fomat is dependant on the default that is set for your subsystem. User response: Specify a valid time. ETI090E This in an invalid Decimal Value
Explanation: The specified decimal value is not valid. User response: Specify a valid decimal value. ETI091 The end of the data has been reached
Explanation: The specified table contains an unknown column type. User response: Ensure that the table definition, including all column types, is complete before continuing. ETI099E The Where Clause was truncated
Explanation: You have reached the end of the data. User response: None required. ETI092 The beginning of the data has been reached
Explanation: You have reached the beginning of the data. User response: None required. ETI093E This is an invalid ZOOM area
Explanation: The specified WHERE clause was truncated. There is insufficient space to display the entire WHERE clause on the screen. User response: None required. ETIA900E Invalid Column Function value. Valid values: 1, 2, 3, 4
Explanation: The area of the screen where you have placed your cursor cannot be zoomed. User response: Move your cursor to a valid location and attempt the ZOOM command again.
Explanation: The specified column function value is not valid. User response: Specify a valid column function value.
320
Users Guide
ETIA901E
ETI803E
Explanation: The permanent view value that was specified is invalid. The permanent view flag indicates whether or not the view you are defining is permanent or temporary. Valid values are: v YView customizations are permanent. v NView customizations are temporary. User response: Specify Y or N.
THE FIRST CHARACTER OF THE COMMAND IS NOT A DASH. CORRECT THE SYNTAX OF THE DB2 COMMAND AND RESUBMIT.
Explanation: You entered a command without using a dash as the first character. User response: Correct the syntax of the DB2 command and resubmit. ETI901E The Rocket Software default load library could not be located.
ETIA902E
Explanation: The specified reset view value is not valid. Valid values are: v Yresets all customizations. v N customizations are not reset. User response: Specify Y or N. ETIA903E Invalid Stop Sorting value. Valid values: Y, N
Explanation: The Rocket Software default load library could not be located. User response: Contact IBM Customer Support. ETI903E The default GDG base dataset name could not be located.
Explanation: The default GDG base dataset name could not be located. User response: Ensure that GDG base dataset name is correct and that it exists. ETI904E The specified dataset could not be opened for I/O.
Explanation: The specified stop sorting value is not valid. Indicates whether or not to stop sorting as specified. Valid values are: v YStop sorting. v NContinue sorting. User response: Specify Y or N. ETIA911E Invalid ICR command. Use RIGHT command.
Explanation: The specified dataset could not be opened for I/O. User response: Contact IBM Customer Support. ETI905E An unexpected return code from VSAM was encountered while doing a read of the control file. RC=code.
Explanation: The ICR command is invalid. User response: Use the RIGHT command. ETIA912E Invalid ICL command. Use LEFT command.
Explanation: An unexpected return code from VSAM was encountered while doing a read of the control file. RC=code. User response: Contact IBM Customer Support. ETI908I The control file record for DB2 subsystem ssid has been successfully added.
Explanation: The ICL command is invalid. User response: Use the LEFT command. ETI802E AN INVALID RETURN CODE OF return code REASON CODE reason code WAS ENCOUNTERED ON function FUNCTION. THE ERROR MESSAGE TEXT FOLLOWS: messages
Explanation: The control file record for DB2 subsystem ssid has been successfully added. User response: None required. ETI909E The valid values are 1 and 2.
Explanation: An invalid return code was encountered. User response: If you cannot resolve this issue using the messages displayed, contact IBM Customer Support.
Explanation: You entered an invalid value. User response: Enter a valid value.
Appendix A. Messages
321
ETI911E
ETI920E
Explanation: The (F)IND command was entered but no parameters were specified. User response: Enter a FIND parameter. ETI912I Find string not found
Explanation: File tailoring open returned a file tailoring already in progress condition. User response: Contact IBM Customer Support. ETI921E File tailoring open returned the output file already in use condition -- ENQ failed.
Explanation: The requested find string was not found. User response: None required. ETI913E Format mix data element not updated.
Explanation: File tailoring open returned the output file already in use condition -- ENQ failed. User response: Contact IBM Customer Support. ETI922E File tailoring open returned the skeletal file or output file not allocated condition.
Explanation: The MIXED data cannot be edited or updated. User response: Use the ZOOM or CEXPAND command to edit the data or update the screen. ETI914E An unknown column was specified using the SORT command.
Explanation: File tailoring open returned the skeletal file or output file not allocated condition. User response: Contact IBM Customer Support. ETI923E File tailoring open returned a severe error condition.
Explanation: An unknown column was specified using the SORT command. User response: Verify that you correctly typed the name of the column or select another column. ETI915E SORT is not supported for the specified column.
Explanation: File tailoring open returned a severe error condition. User response: Contact IBM Customer Support. ETI924E File tailoring open returned an unknown code -- severe error.
Explanation: SORT is not supported for the specified column. User response: You must select a different column. ETI916E Sort column not entered. Column name or number must be specified.
Explanation: File tailoring open returned an unknown code -- severe error. User response: Contact IBM Customer Support. ETI925E File tailoring close returned a file not open condition -- severe error.
Explanation: Sort column not entered. Column name or number must be specified. User response: Contact IBM Customer Support. ETI918 *Bottom of Data reached*
Explanation: File tailoring close returned a file not open condition -- severe error. User response: Contact IBM Customer Support. ETI926E File tailoring close returned an output file in use condition.
Explanation: The search function encountered the end of the data. User response: Press PF5 to continue from the top. ETI919 *Top of Data reached*
Explanation: The search function encountered the top of the data. User response: Press PF5 to continue from the bottom.
Explanation: File tailoring close returned an output file in use condition. User response: Contact IBM Customer Support. ETI927E File tailoring close returned a skeletal file or output file not allocated condition.
Explanation: File tailoring close returned a skeletal file or output file not allocated condition.
322
Users Guide
User response: Contact IBM Customer Support. ETI928E File tailoring close returned a severe error.
ETI935E
Explanation: File tailoring include returned an unknown condition -- severe error. User response: Contact IBM Customer Support. ETI936E Allocation Error - The ISPFILE DD is already allocated and can not be deallocated - Process not completed.
Explanation: File tailoring close returned a severe error. User response: Contact IBM Customer Support. ETI929E File tailoring close returned an unknown code -- severe error.
Explanation: File tailoring close returned an unknown code -- severe error. User response: Contact IBM Customer Support. ETI930E File tailoring close returned a output member exists in the output library and NOREPL was specified.
Explanation: Allocation Error - The ISPFILE DD is already allocated and can not be deallocated - Process not completed. User response: Contact IBM Customer Support. ETI937E Allocation Error - An error was encountered allocating the ISPWRK1 or ISPWRK2 DD - Process not completed.
Explanation: File tailoring close returned a output member exists in the output library and NOREPL was specified. User response: Contact IBM Customer Support. ETI931E File tailoring include returned a skeleton does not exist condition.
Explanation: Allocation Error - An error was encountered allocating the ISPWRK1 or ISPWRK2 DD Process not completed. User response: Contact IBM Customer Support. ETI938E Field Required -- The dataset entered is a partitioned dataset and the member name is required.
Explanation: File tailoring include returned a skeleton does not exist condition. User response: Contact IBM Customer Support. ETI932E File tailoring include returned a skeleton in use -- ENQ failed condition.
Explanation: The dataset entered is a partitioned dataset and the member name is required. User response: Enter a member name and retry. ETI939E The only valid values are T for tracks and C for cylinders.
Explanation: File tailoring include returned a skeleton in use -- ENQ failed condition. User response: Contact IBM Customer Support. ETI933E File tailoring include returned a data truncation or skeleton library or output file not allocated condition.
Explanation: The only valid values are T for tracks and C for cylinders. User response: Enter a valid value. ETI940E The specified dataset could not be found in the MVS catalog.
Explanation: File tailoring include returned a data truncation or skeleton library or output file not allocated condition. User response: Contact IBM Customer Support. ETI934E File tailoring include returned a severe error condition.
Explanation: The specified dataset could not be found in the MVS catalog. User response: Ensure that the dataset name is correct. ETI941E Enter a FIND command
Explanation: File tailoring include returned a severe error condition. User response: Contact IBM Customer Support.
Explanation: You attempted to use the RFIND key. The RFIND key works only after a FIND character string is entered. User response: Enter a FIND character string first and retry.
Appendix A. Messages
323
ETI942E
FIXed area, and allows it to scroll horizontally when LEFT and RIGHT scroll commands are issued. User response: Either remove the invalid character or enter a valid one. ETI951E Invalid entry. Must be numeric
Explanation: You entered an invalid SORT number. User response: Enter a valid digit. ETI943E Same Sort number entered twice.
Explanation: You entered the same SORT number twice. User response: Enter a different SORT number and retry. ETI944E Sort sequence skips a number.
Explanation: An invalid Cmd value was entered. Cmd values must be numeric. If the column is FIXed, the number must be in the FIXed range. If the column is not FIXed, the number must be in the UNFIXed range. User response: Either remove the invalid number or enter a valid one. ETI952E Invalid entry for fixed column
Explanation: The SORT sequence skips a number. User response: Change the SORT sequence so that it does not skip a number. ETI945E Invalid Dir entered. Must be A or D (ascending/descending)
Explanation: An invalid Cmd value was entered for a FIXed column. Valid selections for a FIXed column are 1 up to the number of fixed columns. User response: Either remove the invalid number or enter a valid one. ETI953E Invalid entry for unfixed column
Explanation: You entered an invalid direction. User response: Enter an A or a D and retry. ETI946E Dir not valid without Ord.
Explanation: The direction value is not valid without the ORDER command. User response: Specify the ORDER command and retry. ETI947E Max Sort Columns exceeded. Sorting first 10 columns.
Explanation: An invalid Cmd value was entered for an UNFIXed column. The number must be less than the number of columns, and greater than the number of FIXed columns. User response: Either remove the invalid number or enter a valid one. ETI954E Invalid value entered for column size: non-numeric data
Explanation: You have exceeded the maximum number of columns for sorting. Sorting will be performed on the first 10 columns. User response: No response required. ETI948E Fix Columns cannot exceed screen size.
Explanation: An invalid Cmd value was entered. This must be a number between the values in the MIN and MAX fields. User response: Either remove the invalid number or enter a valid one. ETI955E Invalid value entered for column size: out of range
Explanation: You have attempted to FIX more columns than can fit on the screen. Fix Columns cannot exceed screen size. User response: Do not try to FIX columns greater than the screen size. ETI950E Invalid selection character. F and U are valid
Explanation: An invalid Cmd value was entered. This must be a number between the values in the MIN and MAX fields. MIN is the smallest acceptable value. MAX is the largest acceptable value. User response: Either remove the invalid number or enter a valid one. ETI956E Total fixed column sizes cannot exceed screen size
Explanation: An invalid Cmd character was entered. Valid characters are F (Fix) and U (Unfix). F (Fix) causes the column to move to the fixed area on the left side of the screen. FIXed columns do not scroll horizontally when LEFT or RIGHT scrolling commands are issued. U (Unfix) moves the column out of the
Explanation: The Cmd values entered would result in the sum of the FIXed column sizes to exceed the screen size. This is not allowed. The FIXed columns are those with an F or P in the Fix
324
Users Guide
column. FIXed columns are always displayed, and so must fit on the screen. User response: Either change the FIXed column sizes so that the total is less than the screen size, or CANCEL to return to the previous panel. ETI957E New configuration makes column size invalid
ETI960E
Invalid fixed selections. Would not leave enough space for this column
Explanation: FIXing the columns requested would make at least one UNFIXed column undisplayable. The cursor is positioned on the row that represents one such UNFIXed column, whose minimum displayable size would not fit in the available screen area. User response: Shrink the requested FIXed area by either: v Requesting fewer FIXed columns. v UNFIXing one or more FIXed columns. v CANCEL out of CFIX and invoke CSIZE to shrink one or more FIXed columns enough so that all UNFIXed columns have the space they require. ETI962E Duplicate Cmd values entered
Explanation: The requested column sizes make at least one UNFIXed column undisplayable. The cursor is positioned on the value where the problem was detected. The UNFIXed area on the screen would be too small to show the column where the cursor is placed. User response: The following options are available: v Make the column where the cursor is smaller so that it can fit in the available UNFIXed area. v Set it to its maximum size (width). v Make the FIXed area smaller. v Type CANCEL to return to the previous panel. ETI958E Column does not fit in unfixed area in new configuration
Explanation: Duplicate Cmd numbers were entered. The cursor points to the second instance of a Cmd value. User response: Either change this value, clear it, or exit the CORDER function. ETI963E Cursor not on data element
Explanation: The requested column sizes would make the UNFIXed column where the cursor is positioned undisplayable. The UNFIXed area on the screen would be too small to show this column. User response: You can shrink the FIXed area by either unfixing columns or making FIXed columns smaller. The column where the cursor is cannot be partially displayed (Min=Max), so its size cannot be changed. ETI959E New configuration makes this column size invalid
Explanation: CEXPAND was issued and the cursor was not located on a valid (expandable) area. CEXPAND requires the cursor to be positioned on a data element (non-heading area) in the dynamic area of the display. User response: Either place the cursor on a valid expandable area, or issue CEXPAND and specify the row and column of the data element to expand. The command format is: CEXPAND R C Where R is the row number (1 would be the first line after the heading line) and C is the column number (1 would be the leftmost visible column). ETI964E Invalid scroll amount for CRIGHT. Must be numeric
Explanation: FIXing the requested columns would shrink the available area for UNFIXed columns so that one or more UNFIXed columns would not fit in the remaining UNFIXed area of the screen. The cursor is placed on a row that represents one such column. An UNFIXed column will fit in the UNFIXed area if either: v Its current size is less than or equal to the UNFIXed area v Its size is its maximum size and it has a minimum allowable size that will fit in the UNFIXed area. In that case, a partial column can be displayed. User response: To change column sizes, CANCEL out of the CFIX function and invoke the CSIZE function. You can also blank out one or more FIX selections until an allowable FIXed size is reached.
Explanation: An invalid (non-numeric) parameter to CRIGHT was specified. CRIGHT accepts one numeric parameter: the number of columns to scroll right. If no parameter is entered, a value of 1 is assumed. User response: Correct the invalid parameter. ETI965E Invalid scroll amount for CLEFT. Must be numeric
Explanation: An invalid (non-numeric) parameter to CLEFT was specified. CLEFT accepts one numeric parameter: the number of columns to scroll left. If no parameter is entered, a value of 1 is assumed.
Appendix A. Messages
325
User response: Correct the invalid parameter. ETI966E Invalid parameter to ICRIGHT; must be numeric
ETI971E
Explanation: A parameter to ICRIGHT is not numeric. ICRIGHT (Inner column scroll Right) accepts either zero, one, or two numeric parameters. ICRIGHT can be abbreviated as ICR. If scroll_amount is not specified, a scroll_amount of the column width is assumed. User response: Correct the invalid parameter. The command format is: ICR ICR scroll_amount ICR column_number ICR column_number scroll_amount For the one parameter case, if the cursor is positioned on a column, the parameter is interpreted as scroll_amount. Otherwise, it is interpreted as column_number. ETI967E Parameter to ICRIGHT too long. Invalid
Explanation: A column number parameter to ICRIGHT must be between 1 and the number of columns currently on the display screen. User response: To refer to a column by number, position the display window so that the desired column is visible. ETI972E Invalid parameter to ICLEFT; must be numeric
Explanation: A parameter to ICLEFT is not numeric. ICLEFT (Inner column scroll Left) accepts either zero, one, or two numeric parameters. ICLEFT can be abbreviated as ICL. User response: Correct the invalid parameter. The command syntax is: ICL ICL scroll_amount ICL column_number ICL column_number scroll_amount For the one parameter case, if the cursor is positioned on a column, the parameter is interpreted as scroll_amount. Otherwise, it is interpreted as column_number. If scroll_amount is not specified, a scroll_amount of the column width is assumed. ETI973E Parameter to ICLEFT too long. Invalid
Explanation: A parameter to ICRIGHT is too long. ICRIGHT does not process more than eight digits in a parameter. User response: Shorten the invalid parameter to eight digits or less. ETI968E Parameter to ICRIGHT is zero. Invalid
Explanation: A parameter to ICRIGHT has the value zero. This is not supported. User response: Enter a valid parameter to ICRIGHT. Refer to message ETI966E for the correct syntax. ETI969E ICRIGHT: unspecified column
Explanation: A parameter to ICLEFT is too long. ICLEFT does not process more than eight digits in a parameter. User response: Shorten the invalid parameter to eight digits or less. ETI974E Parameter to ICLEFT is zero. Invalid
Explanation: ICRIGHT was invoked with no parameters and the cursor is not positioned in the dynamic panel area. User response: Either put the cursor in the column that should be scrolled or specify the column by number. Column numbers can refer to visible columns (in the current display window) only. Numbering starts at 1, on the left side. ETI970E MIXED format not eligible for ICRIGHT. Suggest CEXPAND.
Explanation: A parameter to ICLEFT has the value zero. This is not supported. User response: Enter a valid parameter to ICLEFT. Refer to message ETI972E for the correct syntax. ETI975E ICLEFT: unspecified column
Explanation: ICLEFT was invoked with no parameters and the cursor is not positioned in the dynamic panel area. User response: Either put the cursor in the column that should be scrolled or specify the column by number. Column numbers can refer to visible columns (in the current display window) only. Numbering starts at 1, on the left side.
Explanation: You cannot use the ICRIGHT command because of a MIXED format. User response: Use the CEXPAND command.
326
Users Guide
ETI976E
screen. This can be followed by a sort direction value A or D (ascending/descending). ETI982E Invalid view. View adjusted
Explanation: You cannot use the ICLEFT command because of a MIXED format. User response: Use the CEXPAND command. ETI977E ICLEFT: Column number specified is too big
Explanation: The current view was adjusted but not deleted. The saved view did not match the report requirements. This could be caused by the report changing, or corruption of the view file. User response: The (adjusted) view will be used. You can issue the CSET command to modify the view. ETI983E Invalid view. View deleted
Explanation: A column number parameter to ICLEFT must be between 1 and the number of columns currently on the display screen. User response: To refer to a column by number, you must first position the display window so that the desired column is visible. ETI978E Invalid column number specified for SORT (not numeric)
Explanation: Invalid data was found in a view for this report. The view was deleted and its contents ignored. This could have been caused by the report changing, or corruption of the view file. User response: Issue the CSET command to create a view that will match the current report. ETI984E Unexpected return code from TBSTATS: return_code
Explanation: A non-numeric column number parameter to CSORT was specified. User response: Correct the invalid parameter. A column number parameter to CSORT must be between 1 and the number of columns currently on the display screen. This can be followed by a sort direction value A or D (ascending/descending). ETI979E Invalid column number specified. Too many digits
Explanation: An unexpected failure issuing TBSTATS was received. User response: Refer to the ISPF Services Guide for information about the listed return code for TBSTATS. In addition, review the ISPTLIB and ISPTABLE allocations. For information about ISPTLIB and ISPTABL, refer to the ISPF user guides for your version of ISPF. Refer to the configuration chapter of this user guide for the recommended method of allocating ISPTLIB and ISPTABL. ETI985E View library not allocated
Explanation: A parameter to CSORT was invalid. More than eight digits were specified. User response: Correct the invalid parameter. A column number parameter to CSORT must be between 1 and the number of columns currently on the display screen. This can be followed by a sort direction value A or D (ascending/descending). ETI980E Invalid column number specified: zero
Explanation: An invalid parameter to CSORT was specified. User response: Correct the invalid parameter. A column number parameter to CSORT must be between 1 and the number of columns currently on the display screen. This can be followed by a sort direction value A or D (ascending/descending). ETI981E Invalid column number specified: out of range
Explanation: A view input library has not been allocated. Views are read from the ISPTLIB data set(s) and saved to the ISPTABL data set. To save and use report customizations that are created via the CSET command, ISPTABL and ISPTLIB must be allocated. The TBSTATS service has indicated that ISPTLIB is not allocated. Only temporary views will be available. User response: Issue the CSET command and access online help for details on the online report customization options available through the CSET command. In addition, review the ISPTLIB and ISPTABLE allocations. For information about ISPTLIB and ISPTABL, refer to the ISPF user guides for your version of ISPF. Refer to the configuration chapter of this user guide for the recommended method of allocating ISPTLIB and ISPTABL.
Explanation: An invalid parameter to CSORT was specified. The parameter is out of the allowed range. User response: Correct the invalid parameter. A column number parameter to CSORT must be between 1 and the number of columns currently on the display
Appendix A. Messages
327
ETI986E
v See ISPF Services Guide under TBCLOSE. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm ISPTLIB data set extents. v Confirm ISPTLIB data set directory size. v Confirm security controlled access to ISPTLIB data sets. ETI991E TBDELETE failed. RC=return_code
Explanation: TBCREATE was issued to create a view. It failed with a (hex) return code of return_code. User response: Review the following and make necessary adjustments: v See ISPF Services Guide under TBCREATE. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm security controlled access to ISPTLIB data sets. ETI987E TBOPEN failed. RC=return_code
Explanation: An unexpected return code of (hex) return_code occurred during TBDELETE. User response: Review the following and make necessary adjustments: v See ISPF Services Guide under TBDELETE. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm ISPTLIB data set extents. v Confirm ISPTLIB data set directory size. v Confirm security controlled access to ISPTLIB data sets. ETI992E Invalid selection
Explanation: TBOPEN was issued to open an existing view. It failed with a (hex) return code of return_code. User response: Review the following and make necessary adjustments: v See ISPF Services Guide under TBOPEN. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm security controlled access to ISPTLIB data sets. ETI988E TBGET failed. RC=return_code
Explanation: An unexpected return code of (hex) return_code occurred during TBGET. User response: Review the following and make necessary adjustments: v See ISPF Services Guide under TBGET. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm security controlled access to ISPTLIB data sets. ETI989E TBMOD failed. RC=return_code
Explanation: A command that is not supported on this panel was selected. User response: The following options are available: v Enter one of the displayed options, by name or number. v Issue HELP in the function for help on the available commands. v Issue END/EXIT (PF3). v Issue the HELP command for a general overview of CSETUP. ETI993I Permanent view not supported
Explanation: An unexpected return code of (hex) return_code occurred during TBMOD. User response: Review the following and make necessary adjustments: v See ISPF Services Guide under TBMOD. v Confirm ISPTLIB allocation. v Confirm ISPTLIB data set characteristics. v Confirm security controlled access to ISPTLIB data sets. ETI990E TBCLOSE failed. RC=return_code
Explanation: The permanent view flag cannot be set to Y. User response: Ensure that ISPTLIB and ISPTABL have been allocated. For information about ISPTLIB and ISPTABL, refer to the ISPF user guides for your version of ISPF. Refer to the configuration chapter of this user guide for the recommended method of allocating ISPTLIB and ISPTABL. ETI994E Invalid row number
Explanation: The CEXPAND command was issued with an invalid row number. User response: Issue CEXPAND with no parameters and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be
Explanation: An unexpected return code of (hex) return_code occurred during TBCLOSE. User response: Review the following and make necessary adjustments:
328
Users Guide
expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window. ETI995E Invalid column number
and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window. ETI998E Zero parameter invalid
Explanation: The CEXPAND command was issued with an invalid column number. User response: Issue CEXPAND with no parameters and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window. ETI996E Invalid digits
Explanation: The CEXPAND command was issued with a zero for one of its parameters. Zero is not a valid parameter. User response: Issue CEXPAND with no parameters and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window. ETI999E Invalid parameter count: must be either two or zero parms
Explanation: The CEXPAND command was issued with an invalid parameter. User response: Issue CEXPAND with no parameters and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window. ETI997E Too many digits
Explanation: The CEXPAND command was issued with an invalid number of parameters. User response: Issue CEXPAND with no parameters and the cursor on a data field, or with two parameters. The two parameters are the row number, followed by the column number of the data element to be expanded. The row number is counted down from the top, starting with the first scrollable row (the heading is not counted). The column number is counted from left to right, starting with the leftmost column in the current display window.
Explanation: The CEXPAND command was issued with too many digits in one of its parameters. User response: Issue CEXPAND with no parameters
Messages for the DB2 Table Editor Console, Developer, Windows User, and Java Player components
ETI2001I You cant change bound rule if the form uses static SQL. You should revert package to dynamic usage. User response: To Change attributes revert back to dynamic SQL usage in the form. ETI2003W This form has been saved using a previous version of DB2 Forms. Would you like to convert it to the current version?
Explanation: The validation rule cannot be changed or modified since the form is using static SQL. User response: Revert to dynamic SQL in order to modify the validation rule. ETI2002I You cannot change attributes if the form uses static SQL. You should revert package to dynamic usage.
Explanation: The form has been saved with a previous version of Table Editor. User response: Convert the form to the current version to open it and work with it in the current version. ETI2004E Linked control %s not found.
Explanation: Attributes cannot be changed when the form uses static SQL for inserts, updates and deletes.
Appendix A. Messages
329
Explanation: The named control cannot be found in the form. User response: The control may have been deleted. Modify the form accordingly. ETI2005W Collection Name is required.
ETI2011W
The form you are trying to delete is a Full Screen Edit form, and cannot be modified using the DB2 Table Editor Developer Application. Please use the DB2 Table Editor User application to delete this form.
Explanation: A collection name is required to bind the packages. User response: Provide a collection name. ETI2006E No servers are defined. You must specify the name of a server definition file containing one or more servers in order to continue.
Explanation: The full screen edit form was created usng the DB2 Table Editor User component. It cannot be modified or deleted form the Developer component. User response: Use the DB2 Table Editor User component to modify or delete this form. ETI2012W You must enter a positive number as the help context.
Explanation: The developer component needs to point to a server definition file where the required servers are defined. User response: Point to a server definition file.
Explanation: A valid positive number is needed for the help context. User response: Use a valid positive number. ETI2013E An error occurred while deleting %1.%2.
ETI2007E
Explanation: An unknown error occurred while opening the document from the server. The form may have been saved with a version not compatible with the current version. User response: Check connections to the server and make sure the form exists on the server. ETI2008E An error occurred while saving the document at the server.
Explanation: An error occured while deleting the form represented by 1 and 2 where 1 is the owner and 2 is the form name. User response: Check to see if the form being deleted exists. ETI2014W The specified SQL select statement is not valid.
Explanation: The SQL statement is not valid. User response: Enter a valid SQL statement. ETI2015E An error occured while retrieving the list of tables.
Explanation: The form was not saved at the named server due to an error. User response: Check connections to the named server and make sure DB2 Table Editor objects and packages exist on the server. ETI2009W Are you sure you want to delete the primary table?
Explanation: DB2 Table Editor Developer component encountered an error while retrieving the list of tables from the DB2 catalog talbes. User response: Check to make sure all DB2 Table Editor objects and packages exist on the server. ETI2016E An error occured while retrieving the list of forms.
Explanation: The primary table is the table being edited. User response: Verify table before deleting the primary table. ETI2010W Deleting this table will automatically delete all the join and sort conditions associated with this table. Are you sure that you want to continue?
Explanation: DB2 Table Editor Developer component encountered an error while retrieving the list of forms from the catalog talbes. User response: Check to make sure all DB2 Table Editor objects and packages exist on the server.
Explanation: There may be join and sort conditions associated with this table. Deleting the table will delete all associated join and sort conditions. User response: Recomfirm before deleting table.
330
Users Guide
ETI2017E
ETI2024I
Explanation: Error retrieving controls from a DBEdit panel while importing the panel into a DB2 Table Editor Form. User response: Check the DBEdit panel and make sure it exists and is not corrupted. ETI2018E An error occurred while deleting the form from the server.
The form is resized so as not to obscure any of the controls in the form.
Explanation: The form is been automatically resized such that the controls in the form are not obscured. User response: No action necessary ETI2025W Tables are not matching.
Explanation: An error occured while deleting the form from the DB2 Table Editor catalog tables on the server. User response: Check if the form exists on the server. ETI2019W One or more rules are defined for this control. Please delete the rules before deleting the control.
Explanation: When migrating froms from one server to the next the tables being edited should have matching columns and data types. User response: Verify that the form is migrated using matching tables. ETI2026W The server specified for this form, %1, is not defined in the server definition file.\nUse master server instead?
Explanation: The control cannot be deleted when it has validation rules assosicated with it. User response: Delete the rules associated with the control before deleting the control. ETI2020E %1. This file could not be found.
Explanation: The server defined in the form to be opened using the Open Form button has not been defined in the server definition file. User response: Define the server in the server definiton file. ETI2027W The defined links will be deleted.\nDo you wish to continue?
Explanation: The server definition file denoted by %1 could not be found. User response: Make sure the file exists or make sure the path pointing to the file is valid. ETI2021E An error occurred.
Explanation: The source location of the form has been changed so the existing links currently associated with this form will be lost. User response: Verify if you want to change the source location of the form ETI2028W An attempt to allocate memory failed.
Explanation: A general error occured. User response: Record the error number and call technical support. ETI2022W Unable to join columns with incompatible data types.
Explanation: Not enough memory available on the system to allocate memory needed by the application. User response: Free up some memory by closing some running applications. ETI2029I Before changing attributes you must revert package for dynamic use. Do you want to revert it now?
Explanation: When creating a join condition the data types have to be compatible. User response: Create a join condition with compatible data types. ETI2023E An error occurred while inserting items into the list control.
Explanation: After binding the package for a form, you cannot alter the attributes for the form without first reverting to dynamic SQL. User response: To change form attributes after binding a package, select Revert to Dynamic SQL on the Form menu.
Explanation: An error occured when initializing the list conrtol. User response: Check the items being added to the list control.
Appendix A. Messages
331
ETI2030I
ETI2038I
Explanation: The selected forms have been migrated from one environment to another. User response: No action necessary ETI2031I Specify one or more actions on which this rule will apply.
Explanation: The validation rule needs a value to be validated. User response: Enter a value for the validation rule. ETI2039I You must specify values for this rule.
Explanation: Select an action on which the validation rule is applied to a control. User response: Select an action such as select, insert, update or delete. ETI2032W You must enter a numeric value.
Explanation: The validation rule needs these values to to be validated. User response: Enter the values needed for the validation rule. ETI2040I This type of control does not have DB2 Table Editor attributes.
Explanation: A numeric value is needed to use in this validation rule. User response: Enter a numeric value. ETI2033I You must specify a form to open.
Explanation: Some controls like lables, borders etc do not have attributes. They have properties. User response: No action necessary. ETI2041I The table, %s, has not been modified since the form was created.
Explanation: A panel ID is needed to indicate the panel to be imported into DB2 Table Editor. User response: Enter a panel id. ETI2034I You must specify a form by entering its owner and name.
Explanation: This message indicates that the table has not been altered since it was created. User response: No action necessary. ETI2042W No matching forms were found.
Explanation: Specify a form by entering the owner and form name. User response: Enter the form owner and name. ETI2035I Please select the table to be edited as the primary table.
Explanation: No forms matching the search criteria were found in the Table Editor caltog tables. User response: Make sure the correct catalog server is being used. ETI2043I Select a server to be used with this form.
Explanation: The table to be edited is known as the primary table. The primary table needs to be selected from the list of tables selected for the form. User response: Select a primary table. ETI2036I You must enter a SELECT statement to generate values for this rule.
Explanation: Select a server from the server definition file to be used with this form. User response: Select a server from the server definition file. ETI2044W No matching aliases were found.
Explanation: The result set from the select statement will be used in the validation rule. User response: Enter a select statement. ETI2037I You must specify a table by entering its owner and name.
Explanation: No Aliases matching the search criteria were found in the DB2 catalog tables. User response: Make sure the correct server and catalogs are being used. ETI2045W No matching objects were found.
Explanation: A table can be specified by entering its owner and name. User response: Enter the table owner and name.
Explanation: No DB2 objects like tables, views or aliases matching the search criteria were found in the DB2 catalog tables. User response: Make sure the correct server and catalogs are being used.
332
Users Guide
ETI2046W
ETI2053W
Explanation: No DBEdit panels matching the search criteria were found in the DBEdit catalog tables. User response: Make sure the correct server and catalogs are being used. ETI2047W No matching tables were found.
Explanation: When importing panels from DBEdit the name of the table in the panel needs to be valid. User response: Make sure the panel has a valid table name. ETI2054W The form you are trying to open is a Full Screen Edit form, and cannot be modified using the DB2 Table Editor Developer Application. Please use the DB2 Table Editor User application to open this form.
Explanation: No tables matching the search criteria were found in the DB2 catalog. User response: Make sure the correct server and catalogs are being used. ETI2048W No matching views were found.
Explanation: No views matching the search criteria were found in the DB2 catalog. User response: Make sure the correct server and catalogs are being used. ETI2049W This XML file cannot be loaded into the developer environment as it was saved with an earlier version of the product. \nOpen the associated DBE file and then re-save the project to update the XML file.
Explanation: The full screen edit form was created usng the DB2 Table Editor User component. It cannot be opened form the Developer component. User response: Use the DB2 Table Editor User component to open this form. ETI2055W You are not authorized to save or modify forms with Owner = %1.
Explanation: The owner name represented by 1 does not have the authority to save or modify forms. User response: Contact a DB2 system administrator. ETI2056W %1.%2 already exists. Are you sure that you want to replace it?
Explanation: An earlier version of the product was used to save the form into the XML file. User response: Open the form using the binary file with the dbe or dbj extension and save the form into the XML file again. ETI2050I The scroll bars should remain on since the form size is greater than the window size.
Explanation: A form represented by 1 and 2 where 1 is the owner name and 2 is the form name already exixsts in the Database. User response: Overwrite the existing form or save the form under another name. ETI2057W Package name is required.
Explanation: The scroll bars property for the form is automatically set to true if the form size is greater than the window size. User response: No action is necessary.
Explanation: In order to bind the static SQL for this form a package name is required. User response: Enter a package name. ETI2058W Query was not bound.
ETI2051W
Explanation: The package for the form cannot be created because none of the controls in the form are bound to a column in the table. User response: Bind at leaset one of the contorls to a column using the control attributes. ETI2052W You must enter a control name.
Explanation: Encountered an error when binding static SQL for the form. User response: Retry binding packages. ETI2059I Do you want to revert the package %s.%s for dynamic usage?
Explanation: The bound package for the form running static SQL is being reverted to dynamic SQL. User response: Choose to keep the package or revert to dynamic SQL.
Explanation: A control name has not been entered. Every control has to have a unique contol name. User response: Enter a control name.
Appendix A. Messages
333
ETI2060I
Explanation: The server being accessed is not defined in the server definition file. User response: Define the server in the server definition file. ETI2068I Select a table from the list to delete.
Explanation: The bound package using static SQL is reverted to dynamic SQL User response: No action necessary. ETI2061W Some of your changes will not take effect until you restart the application.
Explanation: The selected table will be deleted. User response: Select a table from the list. ETI2069W Select a table from the list to make it the primary table.
Explanation: If the server definition file has been changed the application needs to be restarted for the new SDF to be used. User response: Restart the application. ETI2062W The control does not have a Text property.
Explanation: The primary table is the table being edited. User response: Select a table from the list to be edited. ETI2070I You should specify a join condition when more than one table is used in the form.\nIf you do not specify a join condition, all combinations of rows from all tables will be returned.
Explanation: Validation rules cannot be set on controls that do not have a text property. User response: Choose a control that has a text property to use in the validation rule. ETI2063E Unable to create the character conversion component.
Explanation: Error when evaluating a validation rule. An OLE component for code page conversion was not available. User response: Call technical support.
Explanation: When more than one table is added to the list of tables in a form you need to create a join conditon so that all the rows from all the tables are not returned. User response: Create a join condition. ETI2071I The SQL statement was successfully tested.
ETI2064W
Explanation: The control on the form is not bound to a column in the table being edited. User response: Bind the control to a column in the table being edited. ETI2065I Form %1.%2 saved.
Explanation: The SQL statement can be tested to ensure the form is saved with a valid SQL statement. User response: No action necessary. ETI2072W The table %1 does not exist in this database.
Explanation: The form is saved at the server. User response: No action is necessary. ETI2066E An error occurred while connecting to the server.
Explanation: The table denoted by 1 does not exist in the database catalog tables. User response: Make sure the table was created on this databse. ETI2073E An initialization error occurred.
Explanation: Encountered an error when connecting to the server. User response: Check if the server is up and running and the user has access to the server. ETI2067W The server %1 was not found in the Server Definition File. Select an existing server or use the DB2 Table Editor Console to add the server to the Server Definition File.
Explanation: The application cannot be started probably due to some installation error. User response: Contact technical support. ETI2074W Unable to have unlocked column(s) on the left side of locked one(s).
Explanation: When using the list contorl with the grid view property enabled it is possible to lock columns in the control starting from the left and moving right.
334
Users Guide
User response: Start locking columns from the left. ETI2075W Please enter a valid date format.
ETI2083W
Explanation: There is an invalid character in the expression. User response: Make sure there is no invalid character in the expression. ETI2084W Expression is empty
Explanation: A valid date format is one of the formats available in the Windows control panel settings. User response: Enter a valid date format. ETI2076W Please enter a valid time format.
Explanation: The formula expression is empty. User response: Enter a valid expression. ETI2085W Variable type mismatch in expression.
Explanation: A valid time format is one of the formats available in the Windows control panel settings. User response: Enter a valid time format. ETI2077W Please enter a valid timestamp format.
Explanation: The variables in the expression should match. User response: Match the variables in the expression. ETI2086W Division by zero occured in expression
Explanation: A valid timestamp format is one of the formats available in the Windows control panel settings. User response: Enter a valid timestamp format. ETI2078E Syntax expression error.
Explanation: An error was encountered in the formula. User response: Enter a valid expression. ETI2087W Expression result is undefined
Explanation: The formula has a syntax error. User response: Correct the syntax error. ETI2079E Internal error occured when set expression
Explanation: The formula resulted in an error. User response: Enter a valid expression. ETI2088W Overflow or infinity expression result
Explanation: An GPF error occured when setting a formula. User response: Contact technical support. ETI2080W Variable %1 is undefined
Explanation: The formula resulted in an error. User response: Enter a valid expression.
Explanation: The variable denoted by %1 being used in the formula has not been defined. User response: Define the variable or enter a formula without a variable. ETI2081W Quote or apostrophe has been missed in expression.
ETI2089W
Explanation: A Row Limit limits the number of rows that will be retrieved and displayed. User response: Set a higher row limit. ETI2090W One or more formulas contains references to the row that is being deleted. Do you wish to delete this row and lose the formulas?
Explanation: Unmatched quotes or apostrophes in the expression. User response: Match quotes or apostrophes in the expression. ETI2082W Parenthesis or brace has been missed in expression.
Explanation: If the row is deleted the references to this row in the formula will be lost. User response: Keep the row and validate the formula or delete the row and lose the formula. ETI2091I The action was cancelled.
Explanation: There are unmatched parenthesis or braces in the expression. User response: Match the parenthisis or braces in the expression.
Explanation: Message confirming that a performed action was cancelled in response to the cancel command.
Appendix A. Messages
335
User response: No action necessary. ETI2092W This row has been modified by another user, unable to update
ETI2099E
Explanation: An error was encountered while initializing the OLE libraries. User response: Contact a system administrator or technical support. ETI2100W The /IFormName parameter must be specified as OWNER.FORMNAME.
Explanation: The table is not being accessed exclusively. There are more than one users updating rows in the table. User response: Refresh the table to get the latest values from DB2 and then update. ETI2093W Continue replace all?
Explanation: To start the DB2 Table Editor User applcaiton from the command line the IFormName parameter must have the owner.formname format. User response: Enter a valid format for the command line parameter. ETI2101W To use the /IFormName parameter, you must also specify the /IServer parameter.
Explanation: Message requesting comfirmation for the find and replace feature. User response: Press OK to replace all or cancel to abort the attempt. ETI2094I %1 rows in the database will be updated.
Explanation: The number of rows denoted by %1 will be updated in the table. User response: Press OK to continue or Cancel to abort. ETI2095W An error occurred while launching the contents of the control. %1
Explanation: The sever needs to be specified in addition to the form name to start the application using command line paramteres. User response: Enter a valid server for the command line parameter. ETI2102W This form is empty and does not contain any information. Use developer application to modify the form.
Explanation: An application could not be launched based on the contents of the control denoted by %1 User response: Check if the contents of the control are valid for launching an application. ETI2096W Click OK when you have finished editing the value or click Cancel to cancel the operation.
Explanation: An empty form has been created and saved from the developer component of DB2 Table Editor. User response: Use the developer component to create a valid form. ETI2103E An error occurred while opening the document.
Explanation: An external application has been used to edit a LOB. User response: Press OK to update changes made to the LOB. Pressing Cancel will not update the changes. ETI2097W %1 must contain a valid Hexadecimal format.
Explanation: The form could not be opened in the user component of DB2 Table Editor. User response: Verify that the form being opened is a valid DB2 Table Editor form. ETI2104E Invalid file format.
Explanation: The control denoted by %1 needs a valid Hexadecimal format. User response: Enter a valid hexadecimal value. ETI2098W Directory can not be dropped.
Explanation: The file being opened has an invalid format. User response: Verify that the file has a valid format. ETI2105W You can only specify the column default value when inserting a row. It is not allowed when searching for, updating, or deleting a row.
Explanation: When dropping an object a directory was encountered. User response: Verify that the obkect being dropped is not a directory.
Explanation: Columns in a table can have default values defined when the table is created. The default
336
Users Guide
values can be used when inserting rows into the form only. User response: Use the column default values only when inserting rows. ETI2106W You can only retrieve rows after performing a search.
ETI2113I
Explanation: There are no changes to the values in the form to be updated. User response: Change values in the form before performing an update. ETI2114W The delete will affect one of a set of matching rows, and it is not known which row will be affected. Are you sure that you want to delete the row?
Explanation: In the form layout the next button cannot be used before using the search button. User response: Retrieve rows using the search button before using the next button. ETI2107I There are no more rows matching the search criteria.
Explanation: The row being deleted is not unique. There is more than one row in the form mathing the search criteria to delete the row. User response: Either delete a uniqe row or continue to delete any one of the multiple rows that match the search criteria. ETI2115I %1 rows in the database will be deleted.
Explanation: DB2 Table Editor cannot find any more rows in the table that matches the search criteria spcified in the form. User response: No action necessary. ETI2108I No changes were specified.
Explanation: An update was not possible since no changes were made to any value in the form. User response: Change values in the form before performing an update. ETI2109I No changes were made in the primary table.
Explanation: The number of rows denoted by %1 will be deleted from the table in the database. User response: Press OK to continue or Cancel to abort. ETI2116W The update will affect one of a set of matching rows, and it is not known which row will be affected. Are you sure that you want to update the row?
Explanation: Updates were not performed since no changes were made to the table with the primary key. User response: Change values in the primary table before performing an update. ETI2110I 1 row will be inserted into the database.
Explanation: The row being updated is not unique. There is more than one row in the form mathing the search criteria to update the row. User response: Either update a uniqe row or continue to update any one of the multiple rows that match the search criteria. ETI2117E An error occured during table editing.
Explanation: The row with the specified values in the form will be inserted into the table in the database. User response: No action necessary. ETI2111I 1 row in the database will be deleted.
Explanation: An error was encountered while editing the table. User response: Verify that there are adequate permissions to edit the table and that the table is valid. ETI2118W Updates not allowed for primary keys on this form.
Explanation: The row with the specified values in the form will be deleted from the table in the database. User response: No action necessary. ETI2112I 1 row in the database will be updated.
Explanation: As per the setting when the form was created primary keys cannot be updated on this form. User response: Create the form with Priamary Key enabled to update the primary keys.
Explanation: The row with the specified values in the form will be updated in the table in the database. User response: No action necessary.
Appendix A. Messages
337
ETI2119W
ETI2125I
Explanation: No column values were specified during the insert operation. User response: Specify column values. ETI2120W All the rows of the table will be deleted. Continue with delete?
Explanation: Message confirming the deletion of the form denoted by %1 and %2. User response: Confirm or cancel the deletion of the form. ETI2126W There are no forms saved on this server.
Explanation: Message confirming the deletion of all the rows in the table. User response: Confirm if this is the desired outcome. ETI2121W The table, %1, has been modified since the form was created. The form cannot be loaded.
Explanation: No DB2 Table Editor forms were found in the catalog tables. User response: Verify if the correct server is being used or if any forms were saved at this server. ETI2127W The launch string contains [%1], which is an invalid control name.
Explanation: The table denoted by %1 has been altered or modified since the form was created. User response: Recreate the form with the modified table. ETI2122W Commit scope must be set to 0 because this server does not support the CURSOR WITH HOLD option.
Explanation: The string parsed for launching a file or applicagtion has an invalid string denoted by %1. User response: Correct the invalid string before using the launch feature. ETI2128I Form %1 saved into %2.
Explanation: If the commit scope is set to 0 changes will be committed every transaction. Commit scope of a higher value will not be supported for this server since it does not support the CURSOR WITH HOLD option. User response: Create the form with a commit scope of 0 ETI2123W The form contains [%1], which is an invalid referback value.
Explanation: Message confirming the form denoted by %1 is saved to file denoted by %2. User response: No action necessary. ETI2129E General error occured in expression.
Explanation: An error was encountered while evaluating the formula. User response: Verify the formula has no syntax errors or the variables used, if any, are valid. ETI2130I %1 database changes will be undone.
Explanation: The referback value denoted by %1 that was specified when the form was created in the developer component is not valid. User response: Verify that the referback value is valid when creating the form in the developer component. ETI2124W This is not FSE form. Only FSE form can be deleted or modified.
Explanation: The number of database transactions denoted by %1 will be undone. User response: Press OK to continue rollback or Cancel to abort. ETI2131E An error occurred while running the SQL statement. %s
Explanation: Only forms created in the user component can be modified in the user component of DB2 Table Editor.These forms have a file extension of fse. The other forms need to be modified in the developer component. User response: If not a form created in the user component use the developer component to modify the form.
Explanation: An error was encountered when running the SQL statement denoted by %s. User response: Verify the SQL statment is valid. ETI2132W Filter is not valid.
Explanation: A filter used to sort the result set is not valid. User response: Verify that the filter is valid.
338
Users Guide
ETI2133W
ETI2140W
Variable %1 is a number.
Explanation: The grid layout should display at least one column. User response: Check the visible check box of at least one column in the columns dialog. ETI2134W Unable to have unlocked column(s) on the left side of locked one(s). Do you want to rearrange columns automatically?
Explanation: The variable name cannot be a number. User response: Create a variable name that is not a number. ETI2141W Hex value is not valid.
Explanation: The hexadecimal value is not valid. User response: Enter a valid hexadecimal value. ETI2142W You have not fetched all of the data.\nDo you want to fetch all of the data first?
Explanation: When using the grid layout it is possible to lock columns starting from the left and moving right. User response: Start locking columns starting form left or press ok to rearrange columns automatically. ETI2135W Variable name should not be empty.
Explanation: All the data from the table needs to be fetched before using the sort feature or the replace all feature. User response: Enter Yes to fetch all the data from the table. ETI2143W Finished searching for %1.
Explanation: The variable name used for formulas cannot be empty. User response: Enter a name for the variable. ETI2136W Duplicate variable %1 has been found.
Explanation: The value denoted by %1 was not found in a search. User response: Check the value being searched. ETI2144W Do you want to copy processed data into clipboard?
Explanation: A variable with a name denoted by %1 is a duplicate of another variable. User response: Create a unique variable. ETI2137W Variable name %1 must not duplicate column headers.
Explanation: Message to comfirm copying the data into clipboard. User response: Press OK to continue or Cancel to abort. ETI2145W No column values specified, continue with insert?
Explanation: The variable name cannot be the same as a column name. User response: Create a unique name for the variable. ETI2138W Symbols [ and ] should be only first and last characters.
Explanation: Message to confirm inserting an empty row. User response: Press OK to continue or Cancel to abort. ETI2146W Edit is not allowed when there are multiple tables.
Explanation: The braces cannot be used in the variable name other than the first and last characters. User response: Enter a variable name with no braces in the middle of the name. ETI2139W Variable name %1 contains invalid symbols.
Explanation: DB2 Table Editor does not support editing multiple tables. User response: Select one table to edit. ETI2147W Enter null and enter default values must be different.
Explanation: The character denoted by %1 cannot be used in the variable name. User response: Do not use the invalid symbol in the variable name.
Explanation: The representation for the default value shoudl be different from the representation of the null value.
Appendix A. Messages
339
User response: Enter uniqe values to represent default and null values. ETI2148E Error retrieving column list, the SQL select statement is not valid.
the database. You must either save or discard the requests before refreshing the list. User response: Click Yes to save them or No to discard them. ETI2156E An error occurred while retrieving the list of user profiles.
Explanation: The SQL statement used to retrieve colums is not valid. User response: Use a valid select SQL statement. ETI2149W There are no one column checked.
Explanation: An error occurred while retrieving the list of matching user profiles at the database server. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages. ETI2157I The user profiles were updated.
Explanation: At least one column needs to be checked to create a form using the wizard. User response: Select at least one column. ETI2150W There are no one button checked.
Explanation: At least one button action is needed to create a form using the wizard. User response: Select at least one button action.
Explanation: The assignment or unassignment requests you specified have been saved in the database. User response: No action necessary. ETI2158E An error occurred while updating the user profiles.
ETI2151W
Explanation: All columns cannot use default values. User response: Enter an explicit value for at least one column. ETI2152W Timeout must be a positive integer (or zero, to specify no limit).
Explanation: An error occurred while updating the assignment and unassignment requests you specified. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages. ETI2159I The packages were bound.
Explanation: The CLI timeout value must be a number greater than zero (in seconds), or the value zero to specify no limit. User response: Enter a timeout value greater than zero. ETI2153W Creator is required.
Explanation: The user and administrator database packages have been bound. You must now grant authority to your users to execute the user packages. User response: No action necessary. ETI2160E An error occurred while binding the packages.
Explanation: You must specify a value for the creator. User response: Enter a value for the creator. ETI2154W The specified creator is too long.
Explanation: An error occurred while binding the DB2 Table Editor packages. Additional messages produced with this message describe the error in more detail. User response: Verify that the collection name used is valid. Try rebinding the packages under a different collection name. ETI2161W Name is required.
Explanation: The creator you entered is too long. Specify a valid identifier for the creator and try the operation again. User response: Enter a valid identifier for the creator. ETI2155W You selected profiles for assignment or unassignment. Do you want to process these profiles before refreshing the list?
Explanation: You must specify a value for the name. User response: Enter a value for the name.
Explanation: You have specified assignment or unassignment requests that have not yet been saved in
340
Users Guide
ETI2162I
ETI2168E
Explanation: All of the objects referenced by the packages already exist. You do not need to create any additional objects before binding the packages. User response: Continue to bind the packages if necessary. ETI2163E An error occurred while checking for the existence of the required objects.
Explanation: This message indicates that an error occurred while executing the SQL statements you entered to create the tables required by DB2 Table Editor. User response: Verify that the SQL statements entered are valid. ETI2169E An error occurred while deleting the schedule.
Explanation: This message indicates that an error occurred while determining whether or not any of the required Table Editor objects already exist. User response: call system administrator or customer support. ETI2164E An error occurred while checking table authorizations.
Explanation: An error occurred while deleting the resource limits group schedule from the database server. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support. ETI2170E An error occurred while saving the resource limits group.
Explanation: An error occurred while determining whether you have the required table authorizations. User response: Contact the system administrator for authorizations. ETI2165W No tables were found.
Explanation: An error occurred while saving the current resource limits group at the database server. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support. ETI2171W Group Name is required.
Explanation: DB2 Table Editor did not find any tables with the name and owner information specified. User response: Verify the table information, and try the operation again. ETI2166W You have not specified any SQL statements to execute. Are you sure that you want to continue
Explanation: You must specify a value for the Group Name. User response: Enter a value for the group name. ETI2172E An error occurred while retrieving the resource limits group from the server.
Explanation: You did not enter any SQL statements to create tables or other database objects. This message confirms that you are aware no statements will be executed. User response: Continue if no SQL statements are required otherwise enter SQL statements to execute. ETI2167I The SQL statements that you entered were executed.
Explanation: An error occurred while retrieving the current resource limits group from the database server. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support. ETI2173E An error occurred while saving the resource limits group.
Explanation: The SQL statements you specified have been successfully executed and the tables and other database objects they created now exist. User response: You can now bind the packages.
Explanation: An error occurred while saving the current resource limits group at the database server. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support.
Appendix A. Messages
341
ETI2174E
ETI2181W
Explanation: An error occurred while saving the changes to the servers default schedule. This may be because there is insufficient disk space on the drive containing the server definition file, or you do not have permission to update the file. User response: Check disk space and premissions to save file. ETI2175E An error occurred while saving the schedule.
Explanation: The idle connection timeout value must be a number greater than zero (in seconds), or the value zero to specify no limit. User response: Enter a valid idle connection timeout. ETI2182W Server Response Timeout must be a positive integer or zero.
Explanation: Server Response Timeout value must be a number greater than zero, or the value zero to indicate no limit. User response: Enter a positive integer. ETI2183W Maximum Bytes must be a positive integer or zero.
Explanation: An error occurred while saving the current resource limits group schedule at the database server. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support. ETI2176W From time is required.
Explanation: Maximum Bytes value must be a number greater than zero, or the value zero to specify no limit. User response: Enter a positive integer. ETI2184W Maximum Connections must be a positive integer or zero.
Explanation: You must specify a value for the From Time. User response: Enter a value for the From Time. ETI2177W A schedule with this number is already defined.
Explanation: The Maximum Connections value must be a number greater than zero, or the value zero to specify no limit. User response: Enter a positive integer. ETI2185W Maximum Rows must be a positive integer or zero.
Explanation: There is already a schedule in the resource limits group with the specified number. Schedule numbers must be unique within a resource limits group. User response: Specify a different number. ETI2178W Schedule number must be a positive integer.
Explanation: Maximum Rows value must be a number greater than zero, or the value zero to specify no limit. User response: Enter a positve integer. ETI2186W The specified account is too long.
Explanation: The Schedule Number value must be a number greater than zero. User response: Enter a number greater than zero. ETI2179W Schedule number is required.
Explanation: The account passed to InitializeServer was invalid. See InitializeServer for more information. User response: Enter a valid account.
Explanation: You must specify a value for the Schedule Number. User response: Enter a value for the schedule number. ETI2180W To time is required.
ETI2187E
Explanation: An error occurred while setting permissions on the tables. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support.
Explanation: You must specify a value in the To Time field. User response: Enter a value in the To Time field.
342
Users Guide
ETI2188I
ETI2195W
Explanation: You have successfully granted authority to tables to the specified users. They can now use these tables in DB2 Table Editor. User response: No action necessary.
Explanation: The object owner you entered is too long. User response: Specify a valid identifier for the object owner and try the operation again. ETI2196W Exiting without terminating connections can cause serious system problems. Are you sure that you want to exit?
ETI2189W
Explanation: The combination of creator, translation, and environment must be unique for all user profiles. The profile you are trying to create has the same values as an existing profile. User response: Specify a different creator and try the operation again. ETI2190E An error occurred while creating the user profile.
Explanation: You are attempting to exit while still connected to at least one database server. User response: Terminate server connections before exiting. ETI2197W A connection has not responded to a request for %1 seconds.
Explanation: An error occurred while creating the user profile. Additional messages produced with this message describe the error in more detail. User response: Check additional messages or call technical support. ETI2191I The specified user profile has been created.
Explanation: DB2 Table Editor is terminating the connections that were established with any database server. These connections must be terminated before exiting the application. However, a request to terminate has not completed within the specified time limit. This could indicate a problem with the database server, a problem with your CPI-C software or TCP software, or an internal application error. Additional messages produced with this message describe the options available to you. User response: Follow addition messages or contact the system administrator. ETI2198E An error occurred while granting permission to execute the user packages to the specified user IDs.
Explanation: The user profile you specified has been created and assigned to the resource limits group you are currently working with. User response: No action necessary. ETI2192W Creator is required.
Explanation: You must specify a value for the creator. User response: Specify a value for the creator. ETI2193W The specified creator is too long.
Explanation: An error occurred while setting permissions on the DB2 Table Editor user packages or procedures. Additional messages produced with this message describe the error in more detail. User response: Follow addition messages or contact the system administrator or technical support. ETI2199I Permission to execute the user packages has been granted to the specified user IDs.
Explanation: The creator you entered is too long. Specify a valid identifier for the creator and try the operation again. User response: Enter a valid creator. ETI2194W The specified collection ID is too long.
Explanation: The collection ID you entered is too long. Specify a valid collection ID for the package and try the operation again. User response: Enter a valid collection ID.
Explanation: You have successfully granted authority to execute the DB2 Table Editor packages to the specified users. They can now run DB2 Table Editor. User response: No action necessary.
Appendix A. Messages
343
ETI2200E
An error occurred while revoking permission to execute the user packages from the specified user IDs.
ETI2206W
You must specify a number between 1 and 65535 for Port Number.
Explanation: An error occurred while setting permissions on the DB2 Table Editor packages. Additional messages produced with this message describe the error in more detail. User response: Follow addition messages or contact the system administrator or technical support. ETI2201I Permission to execute the user packages has been revoked from the specified user IDs.
Explanation: Enter the TCP port number that the database server is configured to use. Valid port numbers are from 1 to 65535. The default port number is 446, but servers are not required to use this value. The administrator of the database server can provide you with this information. User response: Enter a valid port number. ETI2207W Database alias is required.
Explanation: You must specify a database alias to create a connection using CLI. User response: Enter a valid database alias. ETI2208W Host name is required.
Explanation: You have successfully revoked authority to execute the DB2 Table Editor packages from the specified users. They can no longer run DB2 Table Editor. User response: No action necessary. ETI2202W You must specify at least one user ID.
Explanation: You must enter at least one user ID to which to grant or revoke permission to execute the DB2 Table Editor packages. User response: If you do not want to perform this action, click Cancel. ETI2203W The specified RDB name was not found at the server.
Explanation: Enter the host name of the machine on which the database server is running. The administrator of the database server can provide you with this information. The value that you enter can be either the host name of the machine, or the machines address, in dotted decimal notation (for example, 1.2.3.4). User response: Enter a valid host name. ETI2209W RDB name is required.
Explanation: You must specify a value for the RDB Name. User response: Enter a value for the RDB name. ETI2210W Symbolic Destination Name is required.
Explanation: The database server returned an error indicating that the RDB name specified for this server is invalid. User response: Confirm the correct value to use and enter it in the Server Parameters dialog box. For DB2 for MVS or z/OS database servers, this value is NOT necessarily the same as the subsystem ID. ETI2204I The connection to the server was established.
Explanation: You must specify a value for the CPI-C Symbolic Destination Name. User response: Enter a valid symbolic destination name. ETI2211I Users of the server definition file that you are currently editing must supply their own user information. The information that you supply now applies only to you.
Explanation: DB2 Table Editor was able to connect to the database server. This indicates your network and database configuration is most likely correct. You can continue to use DB2 Table Editor. User response: No action necessary. ETI2205W A server with this name is already defined.
Explanation: There is already a database server with this name defined in the current server definition file. Servers must have unique names. User response: Specify a different name and try the operation again.
Explanation: Each user must provide their own user ID and password to access a database server. This information is not part of a server definition file. When you specify a user ID and password on the subsequent Set User Information dialog box, it is only for your use, not your users. User response: Have each user provide their own user id and password.
344
Users Guide
ETI2212W
Collection ID is required.
ETI2218E
Explanation: You must specify a collection ID for the package you are binding. Database security mechanisms may restrict what values you may specify for a collection ID. See your database administrator for more information. User response: Enter a valid collection ID. ETI2213W The specified collection ID is too long.
Explanation: An error occurred while retrieving the list of resource limits at the database server. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages or contact technical support or an administrator. ETI2219I The user profiles were deleted.
Explanation: The collection ID you entered is too long. Specify a valid collection ID for the package and try the operation again. User response: Enter a valid collection ID. ETI2214I You cannot assign the default resource limits group.
Explanation: The user profiles you specified have been deleted. User response: No action necessary. ETI2220E An error occurred while deleting the user profiles.
Explanation: The default resource limits group is only used when a user is not explicitly assigned to a resource limits group, or when none of the schedules in the users group is currently in effect. You cannot assign the default resource limits group to a user User response: Do not assign the default resource limits group to a user. ETI2215I You cannot delete the default resource limits group.
Explanation: An error occurred while deleting the specified user profiles. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages or contact technical support or an administrator. ETI2221E An error occurred while retrieving the user profile.
Explanation: The default resource limits group is only used when a user is not explicitly assigned to a resource limits group, or when none of the schedules in the users group is currently in effect. You cannot delete the default resource limits group. User response: Do not delete the default resource limits group. ETI2216E An error occurred while retrieving the resource limits group.
Explanation: An error occurred while retrieving the specified user profile. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages or contact technical support or an administrator. ETI2222I Are you sure that you want to create (or recreate) the sample tables?
Explanation: If you confirm this action, the sample tables are created, and any existing sample tables are overwritten. If you cancel this action, the tables are not created. User response: Confirm this to create sample tables or cancel to not create tables. ETI2223I The sample tables were created.
Explanation: An error occurred while retrieving the selected resource limits group from the database server. Additional messages produced with this message describe the error in more detail. User response: Follow the additional messages or contact technical support or an administrator. ETI2217I The resource limits group was created.
Explanation: DB2 Table Editor sample tables were created. User response: No action necessary. ETI2224E An error occurred while creating the sample tables.
Explanation: The resource limits group was created at the database server. User response: No action necessary.
Explanation: An error occurred while creating the sample tables. User response: Contact technical support or a system administrator.
Appendix A. Messages
345
ETI2225E
ETI2231W
No servers are defined in the local DB2 client that can be imported.
Explanation: An error occurred while saving the specified user profile to the database. Additional messages produced with this message describe the error in more detail. User response: Contact a system administrator or technical support. ETI2226W The specified resource limits group name is too long.
Explanation: DB2 Table Editor is unable to import any of the servers defined in the local client. User response: Check that the servers are properly configured. ETI2232E An initialization error occurred.
Explanation: An unexpected internal error occurred. User response: Exit DB2 Table Editor restart Windows, and try the operation again. If the problem persists, contact your system administrator or technical support. ETI2233E OLE initialization failed.
Explanation: The resource limits group name you entered is too long. User response: Specify a valid name and try the operation again. ETI2227W The file %1 could not be created.
Explanation: DB2 Table Editor was unable to initialize the OLE system libraries via the OleInit() call. User response: Make sure both DB2 Table Editor and OLE 2 are properly installed on your system. ETI2234E An unhandled internal error has occurred (code = %1). Exit DB2 Table Editor Console and restart Windows.
Explanation: An error occurred while trying to save a copy of the current server definition file. User response: Check to make sure the specified drive is valid, there is not an existing file with the same name that is read-only, etc. ETI2228E Re-opening the original file %1 failed.
Explanation: DB2 Table Editor Console was unable to open the original server definition file. User response: Click Open on the File menu to select a different server definition file, or restart DB2 Table Editor Console. ETI2229W The file %1 is read-only and cannot be opened.
Explanation: An unexpected exception condition occurred. This may indicate a memory allocation failure, file access error, or an internal application error. User response: Restart Windows and try the operation again. If the problem persists, contact your system administrator or technical support. ETI2235W Owner is required.
Explanation: You must specify a value for the Owner field. User response: Enter a valid owner. ETI2236I Additional error messages may be contained in %1.
Explanation: DB2 Table Editor Console must be able to write to the server definition file you open. The file you selected is read-only. User response: Either make the file writable or select a different file. ETI2230E An error occurred while saving the file %1.
Explanation: When binding packages at a server that is being accessed via the DB2 UDB call level interface, error messages may be written to a separate log file. User response: Consult the file specified in the message text for more information about why the bind process failed. Consult your database administrator for further assistance.
Explanation: An error occurred while trying to save a copy of the current server definition file. User response: Make sure the drive is valid, there is not an existing file with the same name that is read-only, etc., and try the operation again.
346
Users Guide
Appendix B. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs
347
and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBMs application programming interfaces.
348
Users Guide
Other Notices
XMLParser.Java, AELfred, Version 1.1: AElfred Version 1.1 Microstars Java-Based XML Parser Copyright (c) 1997, 1998 by Microstar Software Ltd. Home page: http://www.microstar.com/XML/ Licensing Terms: AElfred is free for both commercial and non-commercial use and redistribution, provided that Microstars copyright and disclaimer are retained intact. You are free to modify AElfred for your own use and to redistribute AElfred with your modifications, provided that the modifications are clearly documented. Disclaimer: This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of merchantability or fitness for a particular purpose. Please use it AT YOUR OWN RISK. WFC XMLParser: Im just a simple little NT programmer. Most of the work I do is remote controlling equipment in real time. I started out using Windows 3.0. Then came Windows 3,1 and then NT. I started using NT but unfortunately, Microsoft didnt. I started using MFC but unfortunately, Microsoft didnt (and still doesnt) put any real support for NT into MFC so I wrote a bunch of C++ classes to make my life easier. Like all class libraries, mine grew. Now Im giving it away. I call it Win32 Foundation Classes.
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both.
AIX AS/400 DataJoiner DB2 DB2 Connect DB2 Universal Database Distributed Relational Database Architecture DRDA IBM Informix iSeries NUMA-Q MVS OS/2 OS/390 Redbooks SAA SQL/DS z/OS
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries.
Appendix B. Notices
349
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
350
Users Guide
Glossary
A
Accelerator Key An accelerator key allows a user to select a control using a keyboard shortcut rather than a mouse or other selection device. The accelerator key for a control is usually the first letter of the label or caption for that control, and is underlined. To use an accelerator key, press and hold the ALT key, and press the accelerator key for the desired control. ad hoc query A query that has not been named or saved. Advanced DSN settings In the DB2 Table Editor Console component, for ODBC connections, driver-specific key words used to connect to a server not listed under Machine data source. For more information on any keywords that may be required by the selected driver, consult the document. aggregation An aggregation is a collection. In DB2 Table Editor, individual items of data are sometimes aggregated into the database. Attributes An attribute in the DB2 Table Editor Developer component defines the data values and behaviors associated with a form or control. The developer uses attributes to define which data is linked to a form and its controls, when and how the data appears, as well as the function of each control in the form. For example, form attributes can define which database tables are linked to a form, and how multiple tables are joined. Similarly, control attributes can define which data values are displayed in a list box, and how often those values should be refreshed. Attributes in the DB2 Table Editor Windows User and Java Player components define the data values and behaviors associated with a form or control. For example, form attributes can define which database tables are linked to a form, and how multiple tables are joined. Similarly, control attributes can define what data is displayed in a list box, and how often that data should be refreshed to reflect user actions.
C
CCSID Coded character set identifier. CCSID values identify the codes (code points) used to represent characters, and the (character data) conversion of these codes, as needed, to preserve the characters and their meanings. CLI Abbreviation for call level interface, a programming interface that enables applications to interact with DB2. It has much in common with ODBC, but provides additional extensions specific to DB2.
CPI-C CPI-C is a programming interface that implements the APPC verb set. Applications that require the use of the APPC verb set can be written using CPI-C in order to achieve SNA product and vendor independence. DB2 Table Editor is an application that is written using CPI-C. CPI-C Provider DLL The name of the DLL that DB2 Table Editor uses to access CPI-C services.
351
CPI-C Symbolic Destination Name A name defined in your SNA software that refers to a set of parameters (known as a CPI-C side information record) for establishing a connection to a partner application (DB2) over the network. For more information, see your SNA softwares documentation. Catalog A collection of database tables that store database objects (such as tables) or DB2 Table Editor objects (such as queries, forms, and procedures). catalog server The database server on which the DB2 Table Editor catalog resides. collection A collection is a group of packages that have the same qualifier or ID. These packages are bound with a collection ID and become part of the application plan. collection ID The name that you give, in the DB2 Table Editor Console component to a collection of packages that reside on a database server and are used by an application. You can use any name, but usually the collection ID refers to the application that runs the packages. By identifying the application in the collection ID field, it makes it easier to spot packages that are related to a particular product. Command Line Parameter Commands and settings set to take effect when DB2 Table Editor is activated. These parameters are defined on the DB2 Table Editor command line. They can be used to preset settings, or to run unattended sessions. Controls A control in DB2 Table Editor is an individual component of a form. Controls allow users to view and edit data. Examples of controls include edit boxes, list boxes and buttons. correlation ID A unique identifier assigned to a table in a query. In a prompted query, DB2 Table Editor assigns the correlation ID A to the first table you add, B to the second, and so on. These correlation IDs are used throughout the prompted query to qualify column names for join conditions, columns, sort conditions, and row conditions. When you select File --> Draw Query, you can specify a string to use as the correlation ID for each table in the query that you build.
D
DB2 Table Editor Catalog A DB2 Table Editor catalog is a set of database tables that contain resource limits, saved objects, and other settings used by the product. A catalog is required for each server that users will access with DB2 Table Editor. The DB2 Table Editor catalog may reside at the same server that is being accessed or at a different server depending on how the administrator of DB2 Table Editor configured the system. DB2 Table Editor Objects Queries, prompted queries, and procedures are all DB2 Table Editor objects. DRDA Distributed Relational Database Architecture (DRDA). DB2 Table Editor and
352
Users Guide
DB2 are both distributed relational database applications that operate together in a client/server relationship. Each component plays a separate and distinct role in this relationship: DB2 Table Editor as the client/requester and DB2 as the server. Both DB2 Table Editor and DB2 adhere to the Open Groups Distributed Relational Database Architecture (DRDA). This architecture is a comprehensive and detailed blueprint that specifies all of the layers and functions required in a client/server distributed database application. DSN An abbreviation for data source name.
Default Resource Limits Group When the system administrator does not assign a user to a resource limits group or when there are no active schedules in the resource limits group to which a user is assigned, the user is automatically assigned to the default resource limits group named default. Dynamic Query A query whose SQL text is passed to a database server each time it is executed. Dynamic queries can contain substitution variables.
E
Edit Codes Edit Codes determine how a column is formatted in a report. You use different edit codes depending on the type of data that you want to format.
F
File Data Source Name In the DB2 Table Editor Console component, the name of a file whose contents define how to connect to an ODBC data source. A file data source can reside on any client or server machine in the network. Unlike a machine data source, whose connection information resides in the local machines registry, file data sources can be shared by many users across a network. Forms A form created using DB2 Table Editor Developer is a table-editing application designed to access data stored in a DB2 database. The forms you create using DB2 Table Editor Developer allow the user to access, search and edit the DB2 database table to which the form is linked by using the DB2 Table Editor Windows User component or the DB2 table Editor Java Player component.
G
Global Variable A variable that, once set, can be used for an entire DB2 Table Editor session. A global variable can be used in a query, form, or procedure.
H
host name Host name is the name of the machine on which the database server is running. The value that you enter for DB2 Table Editor can be either the host name of the machine, or the machines address, in dotted decimal notation.
Glossary
353
host variable Host variables enable you to use the same static query to retrieve different data. To retrieve different data, you do not need to rebind a package for the static query; you supply different values for the host variables in the query.
I
Identifier Object owners and object names, including column names. The maximum length of table owners and table names depends on the version and platform of DB2. Normal characters include uppercase letters, digits, or the following characters: _ @ # $. You must enclose any special characters in quotes. If the identifier includes a quote character, you double each occurrence of the quote character and then enclose the entire identifier in quote characters. For example, you enter the identifier project as project. If you use lowercase letters and do not enclose the identifier in quotes, any lowercase letters are changed to uppercase. Idle Connection The first time you run a query, DB2 Table Editor acquires a connection to the database server. There is overhead involved in establishing this connection. Once the query is complete, DB2 Table Editor can maintain the connection to the database server. A connection in this state is considered an idle connection. Idle connections still consume resources at the database server. Idle query A query that uses a database server connection but does not actively request data from the database server. Isolation level DB2 provides isolation levels that determine how much to isolate an application from the effects of other running applications. The isolation levels are Repeatable Read (RR), Read Stability (RS), Cursor Stability (CS), Uncommitted Read (UR), and No Commit (NC).
J
Job A file used to schedule and run unattended procedures. A job file can store a user ID, encrypted password, and substitution variables.
L
LU 6.2 LU 6.2 is a SNA communications architecture. APPC (Advanced Program-to-Program Communication) is a language based on the LU 6.2 architecture. A developer of SNA transaction programs has many different implementations of APPC from which to choose. Even though each implementation of APPC adheres to the LU 6.2 architecture, two implementations of APPC may not be exactly the same. Therefore, programs that rely on one vendors APPC implementation may not work with another vendors implementation. CPI-C (Common Programming Interface-Communications) is a standard, common programming interface that solves this problem. Launch Control A Launch Control is a function that allows a developer to specify forms or
354
Users Guide
files within a combo-box, which when selected and launched using a linked button control opens the form, or opens a file in its associated application. Large Object (LOB) A large object, or LOB, is a database entry containing a file that is stored within the database. LOBs can contain text files, multimedia files, or virtually any type of object. local host The system on which DB2 Table Editor is running. load balancing In DB2, load balancing distributes processing and communications activity evenly across a network so that no single device is overwhelmed. Load balancing is frequently used for networks where it is difficult to predict the number of requests that will issued to a server. DB2 Table Editor supports DB2 database servers that use load balancing. By checking Enable load balancing for DB2 database servers that supports load balancing, DB2 Table Editor will receive a list of network addresses that can be used as alternatives after the initial connection to the DB2 database server is made. Subsequent connections can use one of the addresses returned by DB2. These addresses are not necessarily the same address that is configured in the SDF, but they will connect to the same set of database tables.
M
Machine Data Source Name The name of an ODBC data source that is defined in the registry of a client machine, either as a user DSN or a system DSN. Matching Patterns When entering query, form, and table names, you can use the percent (%) and underscore (_) characters to match patterns rather than entering a specific character. v Use the percent character (%) to match a string of any length containing any characters. For example, to list all profiles with a creator beginning with the letter A, you enter A%. v Use the underscore character (_) to match a single character. For example, to list all profiles with a creator that has the letter A in the second position, enter _A%. If the pattern you enter contains special characters, you must enclose the entire pattern in quotation marks. For example, to include a space as part of a pattern, you enter: A B%.
O
Object A form or table. ODBC Open Database Connectivity (ODBC) is a programming interface that enables applications to access data in heterogeneous database management systems that use Structured Query Language (SQL) as a data access standard. Within DB2 Table Editor, ODBC allows you to access data stored in data sources other than DB2.
Glossary
355
P
Packages In DB2, a package is a single bound DBRM with optimized access paths. It contains a set of SQL statements that have been statically bound and is available for processing. A package is always part of an application plan. They are never directly executed, it is only indirectly executed when the plan in which they are contained executes. Packages Wizard The Packages Wizard creates the required database objects and binds the required packages during server set up. TCP/IP, SNA, and CLI connections all require the binding of packages; therefore the Wizard function must be performed when setting up these types of connections. The Packages Wizard button is accessed from the Packages page of the Server Parameters dialog box. port number In TCP/IP networks; an endpoint to a logical connection. The port number identifies what type of port it is. For example, port 80 is used for HTTP traffic. Procedure A procedure is a set of commands that enable you to run queries, print reports, import and export data, as well as perform other functions with a single command. Use the Procedure window to create and edit your procedures. Procedure Comments Text that is not part of the actual commands that are executed when you run a procedure. You use comments to store information for future reference about a procedure in the procedure itself. Procedure comments begin with two hyphens (--) and can continue to the end of the line they appear on. You can include as many comments as you want in a procedure. Everything in the procedure comment (including the two hyphens) is ignored by DB2 Table Editor. Procedure Continuation Lines typically, each line of a procedure contains s single command. However you can continue a command over multiple lines by placing a plus sign (+) as a continuation character in the first column of each additional line. Procedures Wizard The Procedures Wizard creates the required database objects during server set up. The Procedures Wizard button is accessed from the Procedures page of the Parameters Wizard. Properties A property in the DB2 Table Editor Developer component defines the appearance of a form and its controls. The developer uses properties to define the layout of the form, as well as the physical characteristics of controls. Examples of form properties are background color and form dimensions. Examples of control properties are text font, color and control dimensions. Properties, in the DB2 Table Editor Windows User and Java Player components, define the appearance and formatting of forms and controls. Examples of form properties are background color and form dimensions. Control properties include text font, color and control dimensions.
356
Users Guide
Prompted Query A prompted query is a graphical representation of the components that make up a query. If you are not familiar with SQL syntax, use the Prompted Query window to create and edit your queries. Provider DLL The name of the DLL DB2 Table Editor uses to access CPI-C services.
Q
Query A description of a result set of data that you want to retrieve from a database server. In DB2 Table Editor, you can work with a SQL query, a prompted query or a natural query. Quoting Characters The system administrator defines the quoting characters for character values and identifiers when configuring the database server. Legal characters are the apostrophe () and the quotation mark (), and cannot be the same for each. In other words, if the quoting character for the identifier is the apostrophe, then the quoting character for the character value is the quotation mark.
R
RDB Name An identifier for an instance of a database. For DB2 for OS/390, this is synonymous with the location name. For DB2 for VM & VSE, this is synonymous with the application server name, For DB2 for iSeries, this is synonymous with the system name. For DB2 for workstation platforms, this is synonymous with the database name. REXX REXX (Restructured Extended Executor) is an interpreted script language developed by IBM originally for use by personal users of large operating systems. It was designed for ease of learning and use and to make programming accessible to non-programmers. It offers powerful character-manipulation, automatic data typing, manipulation of words, numbers, and names, and debugging capabilities. Remote Host The system on which DB2 is running. Remote Port The TCP/IP port on which DB2 is listening. Resource Limits Various limits and controls that govern the use of database and communication resources by DB2 Table Editor users. Resource Limits Group In the DB2 Table Editor Windows User and Java Player components, resource limits groups are set up by the system administrator and are designed to provide users with sufficient access to database servers without adversely affecting database or network performance. Each DB2 Table Editor user is a member of a resource limits group. Once the system administrator defines and assigns a resource limits group to a DB2 Table Editor user, that user is limited to resource usage as defined by that resource limits group.
Glossary
357
Note: If a system administrator does not assign explicit limits, users are limited to resource usage as defined in the default resource limits group. Resource Limits Group Schedule In the DB2 Table Editor Windows User and Java Player components, A resource limits group consists of zero or more schedules. The system administrator assigns each schedule a unique schedule number. In addition, the system administrator also specifies an effective day-of-week and time-of-day range. DB2 Table Editor determines which schedules are in effect by determining if the current day is within the specified day range, and if the current time is within the specified time range. If more than one schedule is in effect at the same time, DB2 Table Editor uses the one with the lowest schedule number. Restricted Object An object that is available only to its owner.
S
SNA Abbreviation for Systems Network Architecture, a set of network protocols developed by IBM. Originally designed for IBMs mainframe computers, SNA has evolved over the years so that it now also supports peer-to-peer networks of workstations. In DB2 Table Editor terminology, server refers to a database server. Server Definition File (SDF) The DB2 Table Editor server definition file (SDF) is an initialization (.ini) file that contains the technical information DB2 Table Editor needs to connect end users to database servers. The DB2 Table Editor administrator is responsible for creating, configuring and maintaining SDFs for DB2 Table Editor users. Editing the DB2 Table Editor SDF using any method or application other than DB2 Table Editor Console is not recommended and may cause the file to be corrupted. DB2 Table Editor requires at least one SDF. DB2 Table Editor installs with a default SDF called db2sdf.ini. You can create multiple SDFs. After configuring, one or more SDFs are distributed to DB2 Table Editor end users, based on how you choose to manage your query environment. Shared Object An object that is available to all users. Special Characters Any characters NOT included in the following list of regular characters: v A through Z (uppercase only) v 0 through 9 v #$@_ SQL Query A query that you create and modify using Structured Query Language (SQL) statements. You enter SQL statements in a Query window. The database server defines the rules (grammar, syntax, etc.) for valid SQL queries. Make sure the SQL code you write is valid for the specified database viewer.
Server
358
Users Guide
Static Query A query whose SQL text has been previously passed to a database server and bound into a package. When a static query is executed, the database server uses the SQL text bound into its package rather than the SQL text currently appearing in the query window. Static queries can contain host variables. Stored Procedure A DB2 user written application that can be stored and invoked through the use of the SQL CALL statement. System DSN The name of an ODBC data source that is defined in the registry of a client machine. A system DSN, unlike a user DSN, is available to all users of the machine including those users accessing the machine remotely via the network.
T
TCP/IP Abbreviation for Transmission Control Protocol/Internet Protocol, the set of communications protocols used to connect hosts on the Internet and enable them to exchange data. Table A table in DB2 Table Editor Developer refers to a table contained in a DB2 or Informix database. A DB2 database contains data that is organized into smaller collections, or tables. Each form created with DB2 Table Editor Developer is linked to one or more tables, providing the data source for the form.
U
Usage Codes Usage codes provide summary information about the data in a column. For example, usage codes can provide total summary information at the end of a column, or partial summaries at control breaks in a table. The usage codes available depend on the data in the column and the type of summary. User DSN The name of an ODBC data source that is defined in the registry of a client machine. A user DSN, unlike a system DSN, is available only to a single user of the local machine.
V
Validation Rules A validation rule in DB2 Table Editor Developer defines allowable values for the contents of a control. The developer uses validation rules to establish limits, which govern what value a user can enter into a control, as well as the format of the value entered. For example, a validation rule can require that a user enter a valid date format in a control. Validation rules can work individually or in groups.
W
WinCPIC Windows CPI-C, a variant of CPI-C (Common Programming Interface Communications), is a Windows-based programming interface that implements the APPC verb set. Applications that require the use of the
Glossary
359
APPC verb set can be written using WINCPIC in order to achieve SAN product and vendor independence. DB2 Table Editor supports WINCPIC. Winsock Winsock (Windows Sockets) is an application programming interface (API) standard that implements the TCP/IP protocol. Applications that require the use of the TCP/IP protocols can be written using WinSock in order to achieve TCP/IP vendor independence.
360
Users Guide
Index A
ABOUT, command 303 accessibility, features 307 accessibility, keyboard shortcuts 307 applet, error using java Player component as 309 attributes 11 attributes, control 116, 118 authorizationID about 95 command, copy 305 command, COUNT 303 command, D 305 command, delete 305 command, exclude all 279, 280, 281 command, EXCLUDE ALL 303 command, F 305 command, FIND 305 command, FORM 303 command, hex off 285 command, HEX OFF 304 command, hex on 285 command, HEX ON 304 command, I 304 command, include all 279, 281 command, INCLUDE ALL 303 command, insert 304 command, LOAD 303 command, PF3 303 command, PF4 304 command, R 304 command, repeat row 304 command, S 303 command, SAVE 303 command, SQL 303 command, U 305 command, undelete 305 command, zoom 284 command, ZOOM 304 committing, changes 289 communications 4 concepts 11 configuration file, setup 303 configuring your CLI environment 6 configuring your network environment 5 configuring your SNA environment 5 configuring your TCP/IP environment 6 connectivity DB2 for Windows CLI 28 DRDA over SNA 28 DRDA over TCP/IP 28 ODBC 28 connectivity options CPI-C 50 DRDA using SNA 50 DRDA using TCP/IP 50 ODBC 50 setting 50 connectivity, DB2 Table Editor 3 Console add new server to server definition file 55 configure server definition file 55 delete server from server definition file 55 edit SDF server parameters 55 enable dynamic ODBC server definitions 55 getting started 55 import DB2 databases 55 main tasks 55
B
binding packages 30 blank row, insert 286 bytelimits over shooting 99
C
C, command 305, 306 Call Level Interface (CLI) 3 capital letters, force changes to 304 CAPS OFF, command 304 CAPS ON, command 304 catalog creating extension 36 extendedcatalog 95 for non-host servers 36 for ODBC servers 36 shared using ODBC 97 sharing 36 change all, command 292 change, command 306 changes, committing 289 changing the SDF 41 CHECK OFF, command 304 CHECK ON, command 304 checking, turn off 304 checking, turn on 304 CLI driver-specific keywords 54 CLI (Call Level Interface) 3 CLI environment, configuring 6 CLIconnectivity requirements 96 Column Editor, panel 284 columns, select 303 columns, select all 303 command, ABOUT 303 command, C 305, 306 command, CAPS OFF 304 command, CAPS ON 304 command, change 306 command, change all 292 command, CHECK OFF 304 command, CHECK ON 304
361
Console (continued) set global connectivity options 55 Console component, DB2 Table Editor 1 control properties 125 controls 11 controls and their attributes 118 controls and their attributes and properties 116 controls and their properties 125 copy, command 305 copy, row 305, 306 copyright notice, displaying 303 COUNT, command 303 CPI-C and LU 6.2 5 creating DB2 Table Editor catalog tables 30, 33, 260 DB2 Table Editor objects 30, 33, 260
E
edit, contents of a long cell 304 edit, long cell 284 edit, row 284 edit, row with hex editor 304 edit, table 284 edit, with hex editor 285 editing generated SQL statement used to display table data 282 Enter DB2 System Parameters, panel 273 error, SDF (server definition file) does not appear in Server List 309 error, using java Player component as an applet 309 ETI$DPSC panel 280 ETI$DSQL panel 282 exclude all, command 279, 280, 281 EXCLUDE ALL, command 303 extended catalog adding 54 editing 55
D
D, command 305 data 11 data retrieval buffers 99 Query BlockSize 99 database 11 dataretrieval byte limits 98 over shooting 98 row limits 98 datasharing environment, setting up 275 DB2 for Windows databases command 52 importing to the server definition file 52 list of available 52 DB2 Table Editor component 1 DB2 Table Editor connectivity 3 DB2 Table Editor Console add new server to server definition file 55 configure server definition file 55 delete server from server definition file 55 edit server definition file server parameters 55 enable dynamic ODBC server definitions 55 getting started 55 import DB2 databases 55 main tasks 55 set global connectivity options 55 DB2 Table Editor Console component 1 DB2 Table Editor Developer 1 DB2 Table Editor Java Player 1 DB2 Table Editor, overview 1 DB2 Table Editor, working with 275 DB2, using DB2 Table Editor after migrating to a new version of 213 DB2Table Editor, main panel 276 delete, command 305 delete, row 288, 305 Developer, DB2 Table Editor 1 display, number of rows to be returned 280, 303 displaying, IBM copyright notice 303
F
F, command 305 find, command 305 form control properties 125 form controls and their attributes 118 form controls and their attributes and properties 116 FORM, command 303 forms 11 forms, full screen 12 full-screen forms 12
G
governing assign users to resource limits groups 42 control database access 43 control resource usage 43 create resource limits group 43 edit resource limits group schedule 44 resource limits 42 resource limits groups 42 resource limits schedules 42 setup 42 governing, profile use 17 governing, resource limits group 16
H
hex editor, edit row with 304 hex editor, edit with 285 hex editor, turning off 304 hex off, command 285 HEX OFF, command 304 hex on, command 285 HEX ON, command 304
362
Users Guide
I
I, command 304 IBM copyright notice, displaying 303 IBM DB2 Table Editor, overview 1 identifiers format 92 include all, command 279, 281 INCLUDE ALL, command 303 insert, blank row 286 insert, command 304 insert, row 304
P
packages listof 97 Packages wizard bind options 33 binding packages 31 creating catalog 31 creating objects 31 panel, Column Editor 284 panel, DB2 Table Editor main panel 276 panel, Enter DB2 System Parameters 273 panel, ETI$DPSC 280 panel, ETI$DSQL 282 panel, Select Columns 278 panel, Table Selection 278 panel, Update Parameters for DB2 Subsystem (option 1) 273 panel, Update Parameters for DB2 Subsystem (option 2) 274 PF3, command 303 PF4, command 304 primary table 112 Procedures wizard creating catalog 34, 261 creating objects 34, 261 properties 12 properties, control 116, 125
J
Java Player, DB2 Table Editor 1 Java Player, error using as an applet 309 join 12
K
keyboard shortcuts 307
L
LOAD, command 303 long cell, edit 284 long cell, edit or view contents 304 long cell, view or edit contents 304 LU6.2 and CPI-C 5
R
R, command 304 repeat row, command 304 repeat, row 287, 304 resource limits assign users 42 creating groups 43 governing 42, 43 groups 42 schedules 42 resource limits group 18 assign users 45 assigning user profiles to 49 listing of available 49 schedule creating 44, 46 editing 44, 46 modeling on existing 46 multiple schedules for one group 46 options, account information 46 options, API access 46 options, bind packages 46 options, confirm database updates 46 options, export data 46 options, fetch all rows 46 options, fetch limits 46 options, isolation level 46 options, LOBs 46 options, maximum connections 46 options, Report center 46 options, save data 46
Index
M
matchingpatterns wildcards 92 migrating to a new version of DB2, Using DB2 Table Editor after 213
N
network environment,configuring 5 number of rows to be returned, display 280, 303
O
ODBC advanced DSN settings 53 connectivity DB2Table Editor catalog 96 requirements 96 toDB2 data 96 toInformix data sources 96 data sources 97 driver manager 96 driver-specific keywords 54 enabling dynamic definition of servers 51 supported features 97 opening, table 277 overview, IBM DB2 Table Editor 1
363
resource limits group (continued) schedule (continued) options, saved queries only 46 options, SQL verbs 46 options, table editor 46 options, time outs 46 options, user interface access 46 timedifferences 94 resourcelimits group schedule effective days 94 effective time 94 schedule priority 94 resourcelimitsgroup 16 return to the previous screen 303 row, copy 305, 306 row, delete 288, 305 row, edit 284 row, insert 304 row, repeat 287, 304 row, undelete 289, 305 rowlimits data retrieval 99 over shooting 99 rows to be returned, display number 280, 303
T
Table Selection, panel 278 table, display for editing 280 table, edit 284 table, opening 277 table, search and change in 291 table, searchand change in 292 table, searching a 290 TCP/IP and WinSock 5 TCP/IP environment, configuring 6 TCP/IPconnectivity requirements 95 tracing activating 52 problem resolution 52 troubleshooting, DB2 Table Editor 309 turn off, checking 304 turn on, checking 304
U
U, command 305 undelete, command 305 undelete, row 289, 305 Update Parameters for DB2 Subsystem (option 1), panel 273 Update Parameters for DB2 Subsystem (option 2), panel 274 user information setting 37 user profile creating new 47 resource limits group 47 user profiles assigning to resourcelimits group 48 create user profiles 48 creating 48
S
S, command 303 SAVE, command 303 SDF, changing 41 SDF, does not appear in Server List 309 search and change, in a table 292 search, table 290 searchand change, in a table 291 select all, columns 303 Select Columns, panel 278 select, columns 303 server definition file connectivity 28 creating new 49, 50 default 93 deleting a server from 54 multiple 93 sampleSDF 93 setting security parameters 27 server parameters overview 55 set up, configuration file 303 SNA environment, configuring 5 SNAconnectivity requirements 95 specialcharacters matching patterns 93 SQL, command 303 SQL, viewing or editing generated SQL statement used to display table data 282 starting DB2 Table Editor 303
V
validation rules 13 view contents of a long cell 304 viewing generated SQL statement used to display table data 282
W
wildcards/idxterm> search 93 WinSock and TCP/IP 5 working with, DB2 Table Editor 275
Z
zoom, command 284 ZOOM, command 304
364
Users Guide
Printed in USA
SC27-1616-09