Application Programming and SQL Guide - Kmlinux

More documents

Recommendations

Info

G.DDOTV02 DD DSN=&TEMP2,DISP=(NEW,PASS,DELETE), // SPACE=(TRK,(1,1),RLSE),UNIT=SYSDA, // DCB=(RECFM=VB,BLKSIZE=4096,LRECL=4092) //G.DDITV02 DD * DB2X,SYS1,DSNMIN10,,A,-,BATCH001,,IVP8CP22 /* //*************************************************************** //*** ALWAYS ATTEMPT TO PRINT OUT THE DDOTV02 DATA SET *** //*************************************************************** //STEP8 EXEC PGM=DFSERA10,COND=EVEN //STEPLIB DD DSN=IMS.RESLIB,DISP=SHR //SYSPRINT DD SYSOUT=A //SYSUT1 DD DSNAME=&TEMP2,DISP=(OLD,DELETE) //SYSIN DD * CONTROL CNTL K=000,H=8000 OPTION PRINT /* // Finding the DL/I batch checkpoint ID When an application program issues an IMS CHKP call, IMS sends the checkpoint ID to the z/OS console and the SYSOUT listing in message DFS0540I. IMS also records the checkpoint ID in the type X'41' IMS log record. Symbolic CHKP calls also create one or more type X'18' records on the IMS log. XRST uses the type X'18' log records to reposition DL/I databases and return information to the application program. 532 Application Programming and SQL Guide During the commit process the application program checkpoint ID is passed to DB2. If a failure occurs during the commit process, creating an indoubt work unit, DB2 remembers the checkpoint ID. You can use the following techniques to find the last checkpoint ID: v Look at the SYSOUT listing for the job step to find message DFS0540I, which contains the checkpoint IDs issued. Use the last checkpoint ID listed. v Look at the z/OS console log to find message(s) DFS0540I containing the checkpoint ID issued for this batch program. Use the last checkpoint ID listed. v Submit the IMS Batch Backout utility to back out the DL/I databases to the last (default) checkpoint ID. When the batch backout finishes, message DFS395I provides the last valid IMS checkpoint ID. Use this checkpoint ID on restart. v When restarting DB2, the operator can issue the command -DISPLAY THREAD(*) TYPE(INDOUBT) to obtain a possible indoubt unit of work (connection name and checkpoint ID). If you restarted the application program from this checkpoint ID, it could work because the checkpoint is recorded on the IMS log; however, it could fail with an IMS user abend U102 because IMS did not finish logging the information before the failure. In that case, restart the application program from the previous checkpoint ID. DB2 performs one of two actions automatically when restarted, if the failure occurs outside the indoubt period: it either backs out the work unit to the prior checkpoint, or it commits the data without any assistance. If the operator then issues the following command, no work unit information is displayed: -DISPLAY THREAD(*) TYPE(INDOUBT)
# | | | Part 6. Additional programming techniques Chapter 24. Coding dynamic SQL in application programs . . . . . . . 543 Choosing between static and dynamic SQL . . . . . . . . . . . . . . 543 Flexibility of static SQL with host variables . . . . . . . . . . . . . 544 Flexibility of dynamic SQL . . . . . . . . . . . . . . . . . . . 544 Limitations of dynamic SQL . . . . . . . . . . . . . . . . . . . 544 Dynamic SQL processing . . . . . . . . . . . . . . . . . . . 544 Performance of static and dynamic SQL . . . . . . . . . . . . . . 545 Static SQL statements with no input host variables . . . . . . . . . 545 Static SQL statements with input host variables . . . . . . . . . . 545 Dynamic SQL statements . . . . . . . . . . . . . . . . . . 545 Caching dynamic SQL statements . . . . . . . . . . . . . . . . . 546 Using the dynamic statement cache . . . . . . . . . . . . . . . . 547 Conditions for statement sharing . . . . . . . . . . . . . . . . 548 Using the statement cache table . . . . . . . . . . . . . . . . . 549 Keeping prepared statements after commit points . . . . . . . . . . 549 Limiting dynamic SQL with the resource limit facility . . . . . . . . . . . 551 Writing an application to handle reactive governing . . . . . . . . . . 552 Writing an application to handle predictive governing . . . . . . . . . 552 Handling the +495 SQLCODE . . . . . . . . . . . . . . . . . 552 Using predictive governing and down-level DRDA requesters . . . . . . 552 Using predictive governing and enabled requesters . . . . . . . . . . 553 Choosing a host language for dynamic SQL applications . . . . . . . . . 553 Dynamic SQL for non-SELECT statements . . . . . . . . . . . . . . 553 Dynamic execution using EXECUTE IMMEDIATE . . . . . . . . . . . 554 Declaring the host variable . . . . . . . . . . . . . . . . . . 554 Dynamic execution using PREPARE and EXECUTE . . . . . . . . . 555 Using parameter markers with PREPARE and EXECUTE . . . . . . . 556 Using the PREPARE statement . . . . . . . . . . . . . . . . 556 Using the EXECUTE statement . . . . . . . . . . . . . . . . 557 Preparing and executing the example DELETE statement . . . . . . 557 Using more than one parameter marker . . . . . . . . . . . . . 557 Dynamic execution of a multiple-row INSERT statement . . . . . . . . 557 Using EXECUTE with host variable arrays . . . . . . . . . . . . 558 Using EXECUTE with a descriptor . . . . . . . . . . . . . . . 558 Using DESCRIBE INPUT to put parameter information in an SQLDA . . . 559 Dynamic SQL for fixed-list SELECT statements . . . . . . . . . . . . 560 Declaring a cursor for the statement name . . . . . . . . . . . . . 561 Preparing the statement . . . . . . . . . . . . . . . . . . . . 561 Opening the cursor . . . . . . . . . . . . . . . . . . . . . . 562 Fetching rows from the result table . . . . . . . . . . . . . . . . 562 Closing the cursor . . . . . . . . . . . . . . . . . . . . . . 562 Dynamic SQL for varying-list SELECT statements . . . . . . . . . . . 562 What your application program must do . . . . . . . . . . . . . . 562 Preparing a varying-list SELECT statement . . . . . . . . . . . . . 563 An SQL descriptor area . . . . . . . . . . . . . . . . . . . 563 Obtaining information about the SQL statement . . . . . . . . . . 564 Declaring a cursor for the statement . . . . . . . . . . . . . . 564 Preparing the statement using the minimum SQLDA . . . . . . . . 565 SQLN determines what SQLVAR gets . . . . . . . . . . . . . . 565 If the statement is not a SELECT . . . . . . . . . . . . . . . . 565 Acquiring storage for a second SQLDA if needed . . . . . . . . . . 566 Describing the SELECT statement again . . . . . . . . . . . . . 566 Acquiring storage to hold a row . . . . . . . . . . . . . . . . 567 © Copyright IBM Corp. 1983, 2004 533
Page 1:
DB2 ® DB2 Universal Database for z
Page 4 and 5:
Note Before using this information
Page 6 and 7:
# | # | Deleting rows: DELETE . . .
Page 8 and 9:
| | | | vi Application Programming
Page 10 and 11:
Defining a user-defined function .
Page 12 and 13:
Step 4: Run the application . . . .
Page 14 and 15:
| | | | xii Application Programming
Page 16 and 17:
| xiv Application Programming and S
Page 18 and 19:
| | | | | | | | # # # # # # | Chapt
Page 20 and 21:
# # # # # # # xviii Application Pro
Page 22 and 23:
RACF ® How to read the syntax diag
Page 24 and 25:
xxii Application Programming and SQ
Page 26 and 27:
| | | | | | | | | | | | | | xxiv Ap
Page 28 and 29:
| | | | | # | # 2 Application Progr
Page 30 and 31:
Data types When you create a DB2 ta
Page 32 and 33:
DEPTNO DEPTNAME MGRNO ADMRDEPT LOCA
Page 34 and 35:
| | | | | column list of CREATE VIE
Page 36 and 37:
Specifying the sort key The order o
Page 38 and 39:
# Subjecting groups to conditions:
Page 40 and 41:
| | | | | | | | | | | | | | | | | |
Page 42 and 43:
| | | | | | | | | | | | | | | | | |
Page 44 and 45:
Finding information in the DB2 cata
Page 46 and 47:
v UNIQUE, when the value for each r
Page 48 and 49:
Temporary tables can also return re
Page 50 and 51:
If the base table, created temporar
Page 52 and 53:
When a program accesses the data de
Page 54 and 55:
Inserting a single row You can use
Page 56 and 57:
v You can write an application prog
Page 58 and 59:
| | | | | | | | | | | | | | | | | |
Page 60 and 61:
| | | | | | | | | | | | | | | | | |
Page 62 and 63:
| | | | | | | | | | | | | | | Examp
Page 64 and 65:
Deleting every row in a table The D
Page 66 and 67:
Inner join 40 Application Programmi
Page 68 and 69:
Left outer join 42 Application Prog
Page 70 and 71:
SQL rules for statements containing
Page 72 and 73:
000170 YOSHIMURA MANUFACTURING SYST
Page 74 and 75:
A table function or a table express
Page 76 and 77:
SELECT EMPNO, LASTNAME, COMM FROM D
Page 78 and 79:
IN keyword If a subquery that retur
Page 80 and 81:
SELECT EMPNO, LASTNAME, WORKDEPT, E
Page 82 and 83:
| | | 56 Application Programming an
Page 84 and 85:
58 Application Programming and SQL
Page 86 and 87:
| | | # # # # Changing SPUFI defaul
Page 88 and 89:
# # # # # # # # # # # # # # # # # #
Page 90 and 91:
| | | | | # # # # # # # # # # The r
Page 92 and 93:
DSNESP04 SQL STATEMENT RESOURCE LIM
Page 94 and 95:
than the value you choose for field
Page 96 and 97:
| | | | 70 Application Programming
Page 98 and 99:
| | | | | | | | | | | | | | | | | 7
Page 100 and 101:
v DCLGEN — Chapter 8, “Generati
Page 102 and 103:
| | | | v Insert null values in col
Page 104 and 105:
| | | | | | | | | | | | | | | | You
Page 106 and 107:
| | variable and its indicator vari
Page 108 and 109:
| | | | | | | | | | | | | | | | | |
Page 110 and 111:
| | | | | | | | | | | | | | | | | |
Page 112 and 113:
Page 114 and 115:
- SQLWARN5 contains a character val
Page 116 and 117:
| | | | | | | | | | | | | | | | | |
Page 118 and 119:
| | | | | | | | | | | | | | | | | |
Page 120 and 121:
| Table 5. Data types for GET DIAGN
Page 122 and 123:
DSNTIAR places up to 10 lines in th
Page 124 and 125:
Page 126 and 127:
| | | | | | 100 Application Program
Page 128 and 129:
IF SQLCODE = 100 GO TO DATA-NOT-FOU
Page 130 and 131:
| | | | | | | | | | | | | | | | | |
Page 132 and 133:
| | | | | | | | | | | | | | | | | |
Page 134 and 135:
| | | | | | | | | | | | | | | | | |
Page 136 and 137:
Page 138 and 139:
| | | | | | | | | | | | | | | | | |
Page 140 and 141:
| | | | | | | | | | | | | | | | | |
Page 142 and 143:
Figure 15. Values for COL1 of table
Page 144 and 145:
| | | | Figure 18. Removing an upda
Page 146 and 147:
FROM DSN8810.EMP WHERE WORKDEPT <
Page 148 and 149:
***********************************
Page 150 and 151:
| | | | | | | | | | | | | | | | | |
Page 152 and 153:
Page 154 and 155:
| | | DSNEDP01 DCLGEN SSID: DSN ===
Page 156 and 157:
Table 10. Declarations generated by
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Assembler If you specify STDSQL(YES
Page 164 and 165:
Assembler 138 Application Programmi
Page 166 and 167:
| | | Assembler ►► variable-nam
Page 168 and 169:
Assembler ►► variable-name SQL
Page 170 and 171:
Assembler Table 12. SQL data types
Page 172 and 173:
Assembler Overflow: Be careful of o
Page 174 and 175:
| | | | | Assembler Handling SQL er
Page 176 and 177:
C Whether you define the SQLCODE or
Page 178 and 179:
| | | | | | | | | | | C v Do not us
Page 180 and 181:
| | | | | | | C ►► auto extern
Page 182 and 183:
| | | | | | | C ►► auto extern
Page 184 and 185:
| | C ►► ► ▼ , auto extern
Page 186 and 187:
| | | | | | | | | | | | | | | | | |
Page 188 and 189:
| | | | | | | | | | | | | | | | | |
Page 190 and 191:
| | | | | | | | | | | | | | | | | |
Page 192 and 193:
| | C ►► struct tag ► char un
Page 194 and 195:
| C Table 13. SQL data types the pr
Page 196 and 197:
| | | | | | | C Table 14. SQL data
Page 198 and 199:
C In C, a real (floating-point) con
Page 200 and 201:
| | | | | | C ►► auto extern st
Page 202 and 203:
C Examples of calling DSNTIAR from
Page 204 and 205:
COBOL Unlike the SQLCA, a program c
Page 206 and 207:
COBOL 180 Application Programming a
Page 208 and 209:
| | | | | | | | | | | | | | | | | |
Page 210 and 211:
| | | | COBOL ►► ► 01 77 leve
Page 212 and 213:
COBOL ►► 01 77 level-1 Figure 6
Page 214 and 215:
COBOL ►► 01 variable-name Figur
Page 216 and 217:
| | | | | | | | | | | | | | | | | |
Page 218 and 219:
| | | | | | | | | | | | | | | | | |
Page 220 and 221:
| | | | | | | | | | | | | | | | | |
Page 222 and 223:
COBOL ►► level-1 ► ▼ level-
Page 224 and 225:
COBOL ►► ► ►► ► 49 VALU
Page 226 and 227:
# # # COBOL 3. For elements within
Page 228 and 229:
COBOL Table 17. SQL data types mapp
Page 230 and 231:
COBOL Special purpose COBOL data ty
Page 232 and 233:
| | | | | COBOL Using indicator var
Page 234 and 235:
COBOL DSNTIAR syntax CALL ’DSNTIA
Page 236 and 237:
COBOL Rules for host variables: You
Page 238 and 239:
FORTRAN SQL on one line. The SQL ex
Page 240 and 241:
FORTRAN ►► INTEGER*2 *4 INTEGER
Page 242 and 243:
FORTRAN Table 19. SQL data types ma
Page 244 and 245:
FORTRAN v Character data types are
Page 246 and 247:
FORTRAN the library DSN8810.SDSNSAM
Page 248 and 249:
PL/I EXEC SQL INCLUDE member-name;
Page 250 and 251:
| | | | | | | | | | | | | | | | | |
Page 252 and 253:
PL/I ►► ► DECLARE DCL variabl
Page 254 and 255:
| | | | | | | | | | | | | | | | | |
Page 256 and 257:
| | | | | | | PL/I ►► DCL DECLA
Page 258 and 259:
PL/I Table 20. SQL data types the p
Page 260 and 261:
| | | | PL/I Table 21. SQL data typ
Page 262 and 263:
| | | | | | | PL/I - Use a SET assi
Page 264 and 265:
PL/I sqlca An SQL communication are
Page 266 and 267:
REXX See Appendix D of DB2 SQL Refe
Page 268 and 269:
REXX Embedding SQL statements in a
Page 270 and 271:
REXX Using cursors and statement na
Page 272 and 273:
REXX Because the data that is assig
Page 274 and 275:
REXX Using indicator variables When
Page 276 and 277:
REXX 250 Application Programming an
Page 278 and 279:
v A check constraint that contradic
Page 280 and 281:
In some cases, using a timestamp as
Page 282 and 283:
v A view that can be updated that i
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:
▌1▐ CREATE TRIGGER REORDER ▌2
Page 298 and 299:
Granularity Triggers are not activa
Page 300 and 301:
This insert statement, and the subs
Page 302 and 303:
Table 27. Valid SQL statements for
Page 304 and 305:
example, user-defined function PAYR
Page 306 and 307:
When an insert operation occurs on
Page 308 and 309:
| | | | | If the user does not have
Page 310 and 311:
Table T1 Table T2 Table T3 A1 B1 C1
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
| | | | | | | | | | | one auxiliary
Page 318 and 319:
# # # # # # # # # Sample LOB applic
Page 320 and 321:
| Table 30. Examples of C language
Page 322 and 323:
Table 33. Examples of PL/I variable
Page 324 and 325:
Because the program in Figure 121 u
Page 326 and 327:
# # # # # # # # # # # # # # # # # #
Page 328 and 329:
This step is necessary only for an
Page 330 and 331:
Table 34. User-defined function sam
Page 332 and 333:
# # # # # # | | | | | | | | # Table
Page 334 and 335:
| BOAT is based on a BLOB data type
Page 336 and 337:
v You must close all cursors that w
Page 338 and 339:
Page 340 and 341:
# # # # For all data types except L
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
| | | 322 Application Programming a
Page 350 and 351:
| Reserved area 26 bytes. Table fun
Page 352 and 353:
v The argv variable contains an arr
Page 354 and 355:
| #pragma runopts(plist(os)) #inclu
Page 356 and 357:
CBL APOST,RES,RENT IDENTIFICATION D
Page 358 and 359:
| | | | | | | | | | | 332 Applicati
Page 360 and 361:
| | | | | | | | | Table 41. Charact
Page 362 and 363:
Table 41. Characteristics of specia
Page 364 and 365:
| 338 Application Programming and S
Page 366 and 367:
PROGAREA DSECT WORKING STORAGE FOR
Page 368 and 369:
CHECK_EMP: PROC(TRIG_TBL_ID) RETURN
Page 370 and 371:
Preparing user-defined functions to
Page 372 and 373:
TEST(ALL,TESTDD,PROMPT,*) The first
Page 374 and 375:
►► ► TABLE AS ( function-name
Page 376 and 377:
is the same as or lower than the re
Page 378 and 379:
How you can simplify function resol
Page 380 and 381:
| Casting of user-defined function
Page 382 and 383:
You cannot execute this SQL stateme
Page 384 and 385:
Page 386 and 387:
| | | Using distinct types in appli
Page 388 and 389:
to the other because the columns ar
Page 390 and 391:
| CREATE FUNCTION HOUR(FLIGHT_TIME)
Page 392 and 393:
CREATE LOB TABLESPACE DOCTSLOB LOG
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
| | | 374 Application Programming a
Page 402 and 403:
Planning to bind Depending on how y
Page 404 and 405:
CICS With packages, you probably do
Page 406 and 407:
Table 44. Behavior of REBIND PACKAG
Page 408 and 409:
| | | | | | | | | | | | | | | | | I
Page 410 and 411:
Page 412 and 413:
Effects of DB2 locks Suspension Tim
Page 414 and 415:
| | Notes: Job EMPLJCHG (1) OK Tabl
Page 416 and 417:
| | | | | | | | | | Recommendations
Page 418 and 419:
| | 392 Application Programming and
Page 420 and 421:
Aspects of transaction locks The si
Page 422 and 423:
matter what tables the data belongs
Page 424 and 425:
| | | | | 398 Application Programmi
Page 426 and 427:
| | Options for tuning locks Bind o
Page 428 and 429:
Page 430 and 431:
| | | | | 404 Application Programmi
Page 432 and 433:
Page 434 and 435:
Application Time line DB2 Request r
Page 436 and 437:
Application Request row or page Tim
Page 438 and 439:
In all cases, it is a good programm
Page 440 and 441:
| | | | | | | | | | | | | | | Table
Page 442 and 443:
Page 444 and 445:
acquired. Table 58. Locks that are
Page 446 and 447:
v Alter the LOB table space to chan
Page 448 and 449:
| | | | | | | | | | Unit of work in
Page 450 and 451:
v The program issues a checkpoint c
Page 452 and 453:
When are checkpoints important? Iss
Page 454 and 455:
v The number of root segments your
Page 456 and 457:
Page 458 and 459:
| | | | | | v Integration: DRDA acc
Page 460 and 461:
| | Bind processes for DRDA and DB2
Page 462 and 463:
Page 464 and 465:
| | | v Three-part table names, as
Page 466 and 467:
| | | However, you cannot perform t
Page 468 and 469:
Coordinating updates to two or more
Page 470 and 471:
Coding efficient queries A query th
Page 472 and 473:
Remember that statically bound SQL
Page 474 and 475:
CURRENTDATA(NO) Use this bind optio
Page 476 and 477:
| | Table 60. Effect of CURRENTDATA
Page 478 and 479:
Page 480 and 481:
| | | | | | | | Limiting the number
Page 482 and 483:
| | | | | | | | | | | the server su
Page 484 and 485:
Identifying the server at run time
Page 486 and 487:
Page 488 and 489:
| | | | | | | | | | | | | | | | | |
Page 490 and 491:
Page 492 and 493:
precompiler, regardless of the valu
Page 494 and 495:
| | | | | | | | | | | | | | | | | |
Page 496 and 497:
| - DB2 load library (prefix.SDSNLO
Page 498 and 499:
| | Table 63. SQL processing option
Page 500 and 501:
| | | | | | | | | Table 63. SQL pro
Page 502 and 503:
| | | | Table 63. SQL processing op
Page 504 and 505:
value of DSNHDECP parameter DYNRULS
Page 506 and 507:
IMS Include the DB2 IMS (Version 1
Page 508 and 509: 482 Application Programming and SQL
Page 510 and 511: | | | | | | | | | | | | | | | | | |
Page 512 and 513: | | | | | | | | | | | | | | | | | |
Page 514 and 515: | - The program is called by a stor
Page 518 and 519: Using packages with dynamic plan se
Page 524 and 525: assembler. The procedures are in pr
Page 528 and 529: CICS (continued) //****************
Page 530 and 531: | | | | | | | | | | | | | | | | | |
Page 534 and 535: Table 72. Description of the applic
Page 536 and 537: v The LOAD utility obtains data fro
Page 538 and 539: Some sites run a BMP at the end of
Page 540 and 541: This is the type of SQL statement t
Page 542 and 543: Locating the problem The attachment
Page 544 and 545: Notes for Figure 155: 1. Error mess
Page 546 and 547: DB2 SQL PRECOMPILER TMN5P40:PROCEDU
Page 550 and 551: parameter of the DDITV02 data set f
Page 552 and 553: Synchronization call abends If the
Page 554 and 555: table, the translated name is used
Page 556 and 557: Restart and recovery //G.DDOTV02 DD
Page 560 and 561: | | | | 534 Application Programming
Page 562 and 563: | | | | | | | | | | | 536 Applicati
Page 564 and 565: | | 538 Application Programming and
Page 566 and 567: | | | | | | | 540 Application Progr
Page 570 and 571: Flexibility of static SQL with host
Page 572 and 573: | | | | | | | | | | | | | | | | | |
Page 576 and 577: Relationship between KEEPDYNAMIC(YE
Page 578 and 579: Your system administrator can estab
Page 580 and 581: | | | | | | | | | | | | | | | | | |
Page 582 and 583: v Use parameter markers instead of
Page 584 and 585: | | | | | | | | | | | | | | | | | |
Page 586 and 587: After you execute DESCRIBE INPUT, y
Page 588 and 589: Opening the cursor The OPEN stateme
Page 590 and 591: Obtaining information about the SQL
Page 592 and 593: Figure 164. The full-size SQLDA str
Page 594 and 595: Figure 168 shows the SQLDA after yo
Page 598 and 599: Figure 172 shows the contents of FU
Page 600 and 601: The first variable (VAR1 in the exa
Page 602 and 603: | | | | | | | | | | | | | | | | | |
Page 604 and 605: Figure 173 shows processing without
Page 606 and 607: Figure 175. Stored procedure overvi
Page 608 and 609:
| | | | | | | Setting up the stored
Page 610 and 611:
# # | | | | | # | Table 75. Charact
Page 612 and 613:
| | | | | | | | | 18 Linux 19 DYNIX
Page 614 and 615:
| | The method that you use to perf
Page 616 and 617:
| | | | | | | | | | | | | | | | | |
Page 618 and 619:
Page 620 and 621:
# # # # /**************************
Page 622 and 623:
| | | | | | | | | Table 77. Charact
Page 624 and 625:
DSNTIP5. A value of PRIVATE tells D
Page 626 and 627:
Using a temporary table to return r
Page 628 and 629:
# # # | | | v A plan or package con
Page 630 and 631:
Page 632 and 633:
| v Write a CREATE PROCEDURE statem
Page 634 and 635:
| | Statements that you can include
Page 636 and 637:
input parameter of type CHAR(6). Al
Page 638 and 639:
| | | | | | | | Example: EXIT handl
Page 640 and 641:
| | | | | | | | | | | | | | | | | |
Page 642 and 643:
Page 644 and 645:
| | | | | | | | | | | | | | 618 App
Page 646 and 647:
| | | | | | | | | | | | | | | | | |
Page 648 and 649:
| | | | | | | | | | | | | | | | | |
Page 650 and 651:
| | | | | | | | | | | | | | | | | |
Page 652 and 653:
| | | | | | | | | | | | | | | | | |
Page 654 and 655:
Page 656 and 657:
Page 658 and 659:
Page 660 and 661:
| Figure 189. Parameter convention
Page 662 and 663:
#pragma runopts(PLIST(OS)) #pragma
Page 664 and 665:
parameters. See “Examples of usin
Page 666 and 667:
#pragma options(RENT) #pragma runop
Page 668 and 669:
Page 670 and 671:
| | | | 644 Application Programming
Page 672 and 673:
Page 674 and 675:
| | | | | | | | | | | | | | | | | |
Page 676 and 677:
| | | . DCL 01 SP_DBINFO BASED(DBIN
Page 678 and 679:
# # # # # # SQL data type declarati
Page 680 and 681:
Page 682 and 683:
Table 87. Compatible PL/I declarati
Page 684 and 685:
Page 686 and 687:
Page 688 and 689:
Accessing transition tables in a st
Page 690 and 691:
Page 692 and 693:
Preparing a client program You must
Page 694 and 695:
v If the stored procedure does not
Page 696 and 697:
| | | | | | | | | | | | | You can o
Page 698 and 699:
Testing a stored procedure CICS Sto
Page 700 and 701:
| program that is produced by the p
Page 702 and 703:
with DD name INSPLOG in the stored
Page 704 and 705:
Page 706 and 707:
| | | | | | | | | | | | | | | | | |
Page 708 and 709:
| | | | | | | | | | | | | If your q
Page 710 and 711:
Local or join Local predicates refe
Page 712 and 713:
| | | | | If T2 is the first table
Page 714 and 715:
| | | # | | # | # Summary of predic
Page 716 and 717:
# # | | | | | | | | | | | | |# |# |
Page 718 and 719:
| | | | | | | | | | | | | | | | | |
Page 720 and 721:
access. Rows that satisfy the compo
Page 722 and 723:
Interpolation formulas Definition:
Page 724 and 725:
| | | | | | | | | | | | | | | | | |
Page 726 and 727:
| | | Column correlation Two column
Page 728 and 729:
| | | | | “Nonmatching index scan
Page 730 and 731:
Example: The predicate, X.C2>12, fi
Page 732 and 733:
| | | | | | | | | | | | | | | v COL
Page 734 and 735:
| | | | | | | | | | | | | | | | | |
Page 736 and 737:
| | | | | | | | | | | | | | | The R
Page 738 and 739:
SELECT * FROM T1 WHERE C1 BETWEEN :
Page 740 and 741:
The in-memory table saves execution
Page 742 and 743:
| | | | | | Conditions for DB2 to t
Page 744 and 745:
| | | | | | SELECT * FROM DSN8810.E
Page 746 and 747:
| | | | | | | | | | | | | | | | | |
Page 748 and 749:
Obtaining information about access
Page 750 and 751:
When OPTIMIZE FOR n ROWS is effecti
Page 752 and 753:
| | | | | | | | | | | | | | | | | |
Page 754 and 755:
SELECT * FROM PART_HISTORY WHERE PA
Page 756 and 757:
S-{Cm} The current set of columns,
Page 758 and 759:
| | INSERT INTO SYSIBM.SYSCOLDIST (
Page 760 and 761:
Page 762 and 763:
| | response time from adding proce
Page 764 and 765:
| | | | | | | # # # # # | | | | | |
Page 766 and 767:
| | | | Table 99. Descriptions of c
Page 768 and 769:
| | | | | | | Table 99. Description
Page 770 and 771:
| | | | | | | | | | | | | | | | | |
Page 772 and 773:
All rows with the same non-zero val
Page 774 and 775:
| | | | | | The plan table for this
Page 776 and 777:
Example: Assume that the host varia
Page 778 and 779:
| | | | | Is a view or nested table
Page 780 and 781:
| | | | METHOD 3 sorts: These are u
Page 782 and 783:
Table space scans of nonsegmented t
Page 784 and 785:
| | The predicates can be applied o
Page 786 and 787:
One-fetch access (ACCESSTYPE=I1) On
Page 788 and 789:
Example: Figure 212 shows a two-ste
Page 790 and 791:
Nested loop join (METHOD=1) This se
Page 792 and 793:
Merge scan join (METHOD=2) Merge sc
Page 794 and 795:
SELECT A, B, X, Y FROM OUTER, INNER
Page 796 and 797:
| | | | | | 770 Application Program
Page 798 and 799:
1, 2, or 3 Star join is always cons
Page 800 and 801:
| | | | | | | | | | | | | | | | | |
Page 802 and 803:
| | | | | | | | | | | | | | | | | |
Page 804 and 805:
| | | | List prefetch does not pres
Page 806 and 807:
Determining sort activity Sorts of
Page 808 and 809:
With parallelism: v At OPEN CURSOR,
Page 810 and 811:
Table 120. Cases when DB2 performs
Page 812 and 813:
View defining statement: CREATE VIE
Page 814 and 815:
| Estimating a statement’s cost 7
Page 816 and 817:
| | | | | | | | Table 125. Descript
Page 818 and 819:
Page 820 and 821:
Figure 219 shows sequential process
Page 822 and 823:
| | | | | | | | Enabling parallel p
Page 824 and 825:
Interpreting EXPLAIN output DB2 avo
Page 826 and 827:
| | | | | | | | | Table 130. Part o
Page 828 and 829:
Page 830 and 831:
Figure 222. DSN task structure Note
Page 832 and 833:
Page 834 and 835:
Page 836 and 837:
How to use CAF 810 Application Prog
Page 838 and 839:
v “Error messages and dsntrace”
Page 840 and 841:
If you do not specify the precompil
Page 842 and 843:
Page 844 and 845:
Page 846 and 847:
Using a CONNECT call is optional. T
Page 848 and 849:
Table 135. Examples of CAF OPEN cal
Page 850 and 851:
Table 136. Examples of CAF CLOSE ca
Page 852 and 853:
Table 137. Examples of CAF DISCONNE
Page 854 and 855:
Table 139. Effects of CAF calls, as
Page 856 and 857:
Recovery routines The call attachme
Page 858 and 859:
jobname JOB z/OS_jobcard_informatio
Page 860 and 861:
PLAN The plan name to use on the OP
Page 862 and 863:
CLC REASCODE,F30012 Hunt for X’00
Page 864 and 865:
Page 866 and 867:
Task capabilities Any task in an ad
Page 868 and 869:
| | | | | | | | | How to use RRSAF
Page 870 and 871:
| | | | | | | | | | | | | | | | | |
Page 872 and 873:
v Entry point DSNRLI handles explic
Page 874 and 875:
| | | | | | | | | | | | | | | | | |
Page 876 and 877:
Table 143. Register conventions for
Page 878 and 879:
Page 880 and 881:
etcode A 4-byte area in which RRSAF
Page 882 and 883:
| | | | | | | 856 Application Progr
Page 884 and 885:
v Associate the ACEE with the user
Page 886 and 887:
| | | | | | reascode A 4-byte area
Page 888 and 889:
| | | “DSNRLI CONTEXT SIGNON func
Page 890 and 891:
the same data. A global transaction
Page 892 and 893:
| | | | | | | | | | | | | | | | | T
Page 894 and 895:
| | | | | | | | | | | | | | | | | |
Page 896 and 897:
Using a package list can have a neg
Page 898 and 899:
Table 154. Examples of RRSAF TERMIN
Page 900 and 901:
sqlca The program’s SQL communica
Page 902 and 903:
| | v Task 1 then creates context c
Page 904 and 905:
In the example that follows, LISQL
Page 906 and 907:
Page 908 and 909:
| | | | | | | UPNREADY DS 0H attach
Page 910 and 911:
| | | | | | | | | | | | | | | | | |
Page 912 and 913:
| | | | | | | | | | | | | | | | | |
Page 914 and 915:
| | | | | | | | | | | | | | | | | |
Page 916 and 917:
| | | | | | | | | | | | | | | | | |
Page 918 and 919:
| | | | | | | | | | | | | | | | | |
Page 920 and 921:
| # # # # # # # # # # # # # # # # #
Page 922 and 923:
# # # # # # # # # # # # # # # # # #
Page 924 and 925:
# # # # # # # # # # # # # # # # # #
Page 926 and 927:
# # # # # # # # # # # # # # # # # #
Page 928 and 929:
# # # # # # # # # # # # # # # # # #
Page 930 and 931:
Page 932 and 933:
***********************************
Page 934 and 935:
* Fetch backward 5 rows */ /*******
Page 936 and 937:
Use OPTIMIZE FOR 1 ROW to influence
Page 938 and 939:
Page 940 and 941:
Page 942 and 943:
Table 161. Columns of the activity
Page 944 and 945:
It is a dependent of the employee t
Page 946 and 947:
Table 168. Left half of DSN8810.EMP
Page 948 and 949:
Table 171. Indexes of the employee
Page 950 and 951:
Table 175 shows the content of the
Page 952 and 953:
| | | This table has no indexes Rel
Page 954 and 955:
CREATE VIEW DSN8810.VEMP AS SELECT
Page 956 and 957:
CREATE VIEW DSN8810.VPSTRDE1 (PROJ1
Page 958 and 959:
| | | | | | | | | | | Storage group
Page 960 and 961:
| | | | | | | | | | | | | | | | | |
Page 962 and 963:
These applications let you pass DB2
Page 964 and 965:
TSO Table 182. Sample DB2 applicati
Page 966 and 967:
IMS CICS Table 183. Sample DB2 appl
Page 968 and 969:
# # # Running DSNTIAUL 942 Applicat
Page 970 and 971:
DSNTIAUL processes a SELECT stateme
Page 972 and 973:
Running DSNTIAD This section contai
Page 974 and 975:
| | # # # # # # 948 Application Pro
Page 976 and 977:
| | | | | | | | | | | | | | | | | |
Page 978 and 979:
Example 952 Application Programming
Page 980 and 981:
Page 982 and 983:
Page 984 and 985:
Page 986 and 987:
Page 988 and 989:
Page 990 and 991:
Sample dynamic and static SQL in a
Page 992 and 993:
Page 994 and 995:
DRAW syntax: ►► %DRAW object-na
Page 996 and 997:
Generate a template for an UPDATE s
Page 998 and 999:
Page 1000 and 1001:
Page 1002 and 1003:
Page 1004 and 1005:
Page 1006 and 1007:
Page 1008 and 1009:
Page 1010 and 1011:
Page 1012 and 1013:
PROG-END. CLOSE PRINTER. GOBACK. **
Page 1014 and 1015:
***********************************
Page 1016 and 1017:
Page 1018 and 1019:
Page 1020 and 1021:
PERFORM PTSQLCA. IF SQLCODE IS EQUA
Page 1022 and 1023:
Calling a stored procedure from a C
Page 1024 and 1025:
Page 1026 and 1027:
IDENTIFICATION DIVISION. PROGRAM-ID
Page 1028 and 1029:
* MAKE THE CALL IF SQLCODE NOT EQUA
Page 1030 and 1031:
1004 Application Programming and SQ
Page 1032 and 1033:
C stored procedure: GENERAL WITH NU
Page 1034 and 1035:
COBOL stored procedure: GENERAL Thi
Page 1036 and 1037:
CBL RENT IDENTIFICATION DIVISION. P
Page 1038 and 1039:
CBL RENT IDENTIFICATION DIVISION. P
Page 1040 and 1041:
ASUTIME NO LIMIT PARAMETER STYLE GE
Page 1042 and 1043:
Page 1044 and 1045:
| | | | | | | | | | | | | | | | | |
Page 1046 and 1047:
| | | | | | | | | | | | | | | | | |
Page 1048 and 1049:
Page 1050 and 1051:
Page 1052 and 1053:
| | | | | | | | | | | | | SELECT SU
Page 1054 and 1055:
Page 1056 and 1057:
Table 195. SQL reserved words ADD A
Page 1058 and 1059:
Page 1060 and 1061:
| | | | | | Table 196. Actions allo
Page 1062 and 1063:
Table 196. Actions allowed on SQL s
Page 1064 and 1065:
| | Table 197. SQL statements in ex
Page 1066 and 1067:
| | Table 198. Valid SQL statements
Page 1068 and 1069:
Page 1070 and 1071:
| | | | Table 199. Program preparat
Page 1072 and 1073:
Environment for WLM_REFRESH WLM_REF
Page 1074 and 1075:
strcpy(WLMENV,"WLMENV1"); strcpy(SS
Page 1076 and 1077:
Page 1078 and 1079:
Parameter list for DSNACICX At invo
Page 1080 and 1081:
***********************************
Page 1082 and 1083:
# # # # # # # # # # # # # # # # # #
Page 1084 and 1085:
# # # # # # # # # # # # # # # # # #
Page 1086 and 1087:
Page 1088 and 1089:
Licensees of this program who wish
Page 1090 and 1091:
Page 1092 and 1093:
| APF basic sequential access metho
Page 1094 and 1095:
| catalog closed application catalo
Page 1096 and 1097:
connection cost category connection
Page 1098 and 1099:
| | | | | | | | | | | | | | | | | |
Page 1100 and 1101:
| | | | # # # dependent row drain l
Page 1102 and 1103:
executable statement foreign key ex
Page 1104 and 1105:
| | | | group level image copy pool
Page 1106 and 1107:
| | | | | instrumentation facility
Page 1108 and 1109:
| | | | | | location alias LUW loca
Page 1110 and 1111:
| | | | network identifier (NID) pa
Page 1112 and 1113:
| | partner logical unit primary au
Page 1114 and 1115:
| | | | | RACF referential integrit
Page 1116 and 1117:
esource manager scale resource mana
Page 1118 and 1119:
shift-out character SQL path shift-
Page 1120 and 1121:
subquery table space subquery. A SE
Page 1122 and 1123:
trigger activation unit of recovery
Page 1124 and 1125:
| | | | | Virtual Storage Access Me
Page 1126 and 1127:
v CICS Transaction Server for z/OS
Page 1128 and 1129:
DFSORT v DFSORT Application Progra
Page 1130 and 1131:
v VTAM for MVS/ESA Messages and Cod
Page 1132 and 1133:
Page 1134 and 1135:
application program (continued) pre
Page 1136 and 1137:
calculated values (continued) summa
Page 1138 and 1139:
CONNECT (connection function of CAF
Page 1140 and 1141:
deadlock (continued) with RELEASE(D
Page 1142 and 1143:
DSNHDECP (continued) implicit RRSAF
Page 1144 and 1145:
GET DIAGNOSTICS statement (continue
Page 1146 and 1147:
ISPF (Interactive System Productivi
Page 1148 and 1149:
multiple-row FETCH statement (conti
Page 1150 and 1151:
precompiler (continued) precompilin
Page 1152 and 1153:
ROWID variable (continued) COBOL 18
Page 1154 and 1155:
single-mode IMS programs 426 SOME q
Page 1156 and 1157:
SQLDA (SQL descriptor area) (contin
Page 1158 and 1159:
trigger (continued) coding 271 data
Page 1160 and 1161:
WHENEVER statement (continued) Fort
Page 1162:
Readers’ Comments — We’d Like
show all

Application Programming and SQL Guide - Kmlinux

Create successful ePaper yourself

Delete template?

Save as template?