Getting Started with IBM Data Studio for DB2

More documents

Recommendations

Info

196 Getting Started with IBM Data Studio for DB2 Notification Chains user ID that will run the job. If you schedule a job to run on more than one database, the job is run on each database by the user ID that is stored in the database connection for that database. Notifications are one of two methods that you can use to determine whether your jobs ran successfully. Use notifications to alert you by email on the successful or failed run of a job on your databases. The other method of determining the outcome of your jobs is to look in the job history tab of the job manager, where you can see the status of all jobs on all databases that are configured for your system. You can add a chain of subsequent jobs that run depending on the outcome of the primary job. A job chain can consist of three consecutive jobs: the primary job, a job that runs if the primary job is successful or a job that runs if it is unsuccessful, and finally an ending job that runs at the end of the chain regardless of the outcome of the preceding jobs. Important: When a job is run as part of a chain, any schedules and chains that are associated with that job are ignored. Table 6.1 – Components of a job 6.3.2 Job types The job manager supports three default job types. The job type indicates the way that the job manager connects to the databases to run the scripts. Job type SQL-only script DB2 command line processor script Executable/Shell script Connection method The job manager connects to the database and runs the SQL commands that are included in the job script directly on the database. The job manager logs in to the database server by using SSH as the user ID defined in the database connection, and then it runs command line processor commands directly on the DB2 console of the server. The job manager logs in to the database server by using SSH as the user ID that is defined in the database connection, and then runs shell commands directly on the server. Note: To run DB2 command line processor script jobs or executable/shell script jobs on a database, the user ID that is used to run the job must have permission to log in to the database server by using SSH.
Chapter 6 – Managing jobs 197 6.4 Create and schedule a job Use the Job List tab in the web console to create, schedule, and manage jobs for your databases or to run existing jobs directly against a database without scheduling. The first time you open the job manager, no jobs have been created, and the job manager informs you what needs to be done to create one. Figure 6.2 – The Job List page with no jobs created When you create a job or open an existing job, the job details open in the job editor. If you have more than one job open for editing, each job opens in its own tab. Within each tab you can use the Job Components menu to drill down into the components of each job. If you have configured the Data Studio full client for Data Studio web console, you can also schedule a script to run as a job directly from the SQL script editor. See 6.7 Scheduling jobs from the Data Studio client for more information.
Page 1 and 2:
]
Page 3 and 4:
3 Notices This information was deve
Page 5 and 6:
Table of contents 5 Table of conten
Page 7 and 8:
3.3.1 Exporting data...............
Page 9 and 10:
Chapter 7 - Tuning queries ........
Page 11 and 12:
11.4 Community and resources ......
Page 13 and 14:
Preface 13 Keeping your skills curr
Page 15 and 16:
around the world have participated
Page 17 and 18:
17 About the authors Dimple Bhatia
Page 19 and 20:
Contributors 19 The following peopl
Page 21:
21 Acknowledgements The authors owe
Page 24 and 25:
24 Getting Started with IBM Data St
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Getting Started with IBM Data S
Page 103 and 104:
103 Chapter 3 - Maintaining the dat
Page 105 and 106:
Chapter 3 - Maintaining the databas
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Figure 3.35 - Selecting additional
Page 135 and 136:
Page 137:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147: 146 Getting Started with IBM Data S
Page 159 and 160: 159 Chapter 5 - Creating SQL and XQ
Page 161 and 162: Chapter 5 - Creating SQL and XQuery
Page 181 and 182: On Success On Error Result Chapter
Page 193 and 194: 193 Chapter 6 - Managing jobs Job m
Page 195: Chapter 6 - Managing jobs 195 6.3 J
Page 199 and 200: Chapter 6 - Managing jobs 199 Figur
Page 201 and 202: Chapter 6 - Managing jobs 201 Comp
Page 207 and 208: Chapter 6 - Managing jobs 207 6.5 R
Page 209 and 210: Chapter 6 - Managing jobs 209 6.6.2
Page 213 and 214: 213 Chapter 7 - Tuning queries In t
Page 215 and 216: Chapter 7 - Tuning queries 215 Figu
Page 217 and 218: Chapter 7 - Tuning queries 217 You
Page 219 and 220: Chapter 7 - Tuning queries 219 •
Page 223 and 224: 7.4.2 Run the Statistics Advisor an
Page 225 and 226: Chapter 7 - Tuning queries 225 7.4.
Page 227 and 228: Chapter 7 - Tuning queries 227 For
Page 231 and 232: Chapter 7 - Tuning queries 231 To s
Page 233 and 234: Chapter 7 - Tuning queries 233 3. O
Page 235 and 236: Chapter 7 - Tuning queries 235 7.6
Page 237 and 238: 237 Chapter 8 - Developing SQL stor
Page 239 and 240: Chapter 8 - Developing SQL stored p
Page 247 and 248:
Chapter 8 - Developing SQL stored p
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 355 and 356:
355 Appendix D - The Sample Outdoor
Page 357 and 358:
Appendix D - The Sample Outdoor Com
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Appendix E - Advanced topics for de
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
E.5.4 Data web services artifacts A
Page 391 and 392:
References 391 References [1] HAYES
Page 393 and 394:
References 393 Books and articles 1
Page 396:
396 Getting started with IBM Data S
show all

Getting Started with IBM Data Studio for DB2

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?