APAR status
Closed as canceled.
Error description
This apar documents changes to the DB2 Application Programming and SQL Guide that did not make R230 GA Pubs. 5740XYR00 SC26437702 ================================================================ Book Title: Application Programming and SQL Guide Page Number: p. 64 The INSERT statement is incorrect (it won't produce the expected results mentioned in the second paragraph on page 65). The INSERT statement should be as follows: INSERT INTO YDEPT VALUES ('E31', 'DOCUMENTATION', '000010', 'E01', ' '); ================================================================ Book Title: Application Programming and SQL Guide Page Number: p. 65 Change Description: The second paragraph on page 65 has been deleted. The information was incorrect. ============================================================== Book Title: Appl Programming and SQL Guide (SC26-4377-02) Page Number: p. 102 In the second to the last sentence in the third paragraph, the word "warning" has been changed to "message" and now reads: "(... A message is issued when a colon does not precede the name of a host variable in an SQL statement.)" ============================================================== Book Title: Appl Programming and SQL Guide (SC26-4377-02) Page Number: p. 162 The following bulleted entry has been added to the subsection "Special COBOL Considerations": "o Dashes cannot be used in ordinary SQL identifiers if SQL statements will be bound remotely." ============================================================== Page Number: p.167 In Table 16, the notes to entry "DECIMAL(p,s) or NUMERIC(p,s)" should read: p is precision; s is scale. 0<=s<=p<=18. If s=0, S9(p)V or S9(p) should be used. If p-s=0, SV9(s) should be used. ============================================================== Book Title: Appl Programming and SQL Guide (SC26-4377-02) Page Number: p. 292 The subsection "Execution (Command Level) Diagnostic Facility (EDF)" has been rewritten as follows: If you are using CICS Version 3, EDF allows commands to be displayed in source form on a screen, both before and after execution. EDF also stops before and after executing each SQL statement. See "CICS Execution Diagnostic Facility" on page 368 for more information. If you are using an earlier version of CICS, the commands will not be displayed in source form before or after execution. Instead, the CALL TO RESOURCE MANAGER DSNCSQ screen will display a status of "ABOUT TO EXECUTE" or "COMMAND EXECUTION COMPLETE." ================================================================ Book Title: DB2 Application Programming and SQL Guide Page Number: p. 306 Change Description: The text under the heading, "Requirements for Using DB2 in a DL/I Batch Job," incorrectly states that the DLIBATCH procedure must run module DSNMTV01 as the application program. This can be done, but it is no longer required as there is an alternative method available. The alternative method can run an application program without using module DSNMTV01. To accomplish this, do the following: o Specify SSM= in the DL/I batch procedure o In the batch region of the application's JCL, specify the following: MBR=application-name SSM=DB2-subsystem-name An example of the JCL used to submit a DL/I batch application (without using DSNMTV01) has also been added: //TEPCTEST JOB 'USER=ADMF001',MSGCLASS=A,MSGLEVEL=(1,1), // TIME=1440,CLASS=A,USER=SYSADM,PASSWORD=SYSADM //******************************* //BATCH EXEC DLIBATCH,PSB=IVP8CA,MBR=IVP8CP22, // BKO=Y,DBRC=N,IRLM=N,SSM=SSDQ //******************************* //SYSPRINT DD SYSOUT=A //REPORT DD SYSOUT=* //G.DDOTV02 DD DSN=&TEMP,DISP=(NEW,PASS,DELETE), // SPACE=(CYL,(10,1),RLSE), // UNIT=SYSDA,DCB=(RECFM=VB,BLKSIZE=4096,LRECL=4092) //G.DDITV02 DD * SSDQ,SYS1,DSNMIN10,,Q,",DSNMTES1,,IVP8CP22 //G.SYSIN DD * /* //**************************************************** //* ALWAYS ATTEMPT TO PRINT OUT THE DDOTV02 DATA SET //**************************************************** //PRTLOG EXEC PGM=DFSERA10,COND=EVEN //STEPLIB DD DSN=IMS410.RESLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSUT1 DD DSN=&TEMP,DISP=(OLD,DELETE) //SYSIN DD * CONTROL CNTL K=000,H=8000 OPTION PRINT /* ================================================================ Book Title: Application Programming and SQL Guide Page Number: p.415 In Table 40 (Examples of CAF CONNECT Calls), the parameter STARTECB has been added to CAF CONNECT calls for assembler, COBOL, FORTRAN, and PL/I. In all cases, STARTECB follows TERMECB. ================================================================ Book Title: Appl Programming and SQL Guide (SC26-4377-02) Page Number: p. 415, 417 through 420 Remove "fnret=" from the call example for C in tables 40 through 44. ================================================================ Book Title: Application Programming and SQL Guide Page Number: pp. 551 through 553 Change Description: Corrections to "Appendix G: List of DB2 Mapping Macros": 1) Delete the word "Mapping" from the appendix title. 2) Add the following macros and descriptions to the list: DSNDLOGX Maps the exit parameter list for log capture routines. DSNDQDST Maps the instrumentation statistics block. DSNDQMDA Maps the accounting facility data. DSNXNBRM Describes the format of the entry statement for DB2 Version 2 Release 3. DSNXPOPT Maps the parser option list. 3) Delete the following macro names and their descriptions: DSNCRCT DSNMAPN DSN6SCLS DSN6SPRC DSNDSPRM DSNMTV DSN6SPCK DSN6STOK ============================================================== DB2 Version 2 Release 3 Application Programming and SQL Guide, SC26-4377-02, page 185: Replace the third row of Table 20: Table 20: SQL Data Types Mapped to Typical PL/I Declarations SQL Data Type | PL/I Equivalent | Notes -----------------+------------------------+------------------- DECIMAL(p,s) or | If p<16: | p is precision; NUMERIC(p,s) | DEC FIXED(p) or | s is scale. | DEC FIXED(p,s) or | 1<=p<=31 and | | 0<=s<=p | PICTURE | There is no exact | picture-string | equivalent for | | p>15. (See | | "PL/I Data Types | | with No | | SQL Equivalent" on | | page 186 for more | | information.) ================================================================ DB2 Version 2 Release 3 Application Programming and SQL Guide, SC26-4377-02, page 409: Replace the section under "Implicit Connections" with the following: Implicit Connections -------------------- In a CAF application program, executable SQL statements not explicitly specified in a CALL DSNALI statement cause CAF to initiate implicit CONNECT and OPEN requests to DB2. Although these connection requests are performed by CAF using the default values defined below, they are still subject to the same DB2 return and reason codes encountered when using explicit connection requests in the application program. Implicit connections use the following defaults: Parameter Default Subsystem name The default name given when installing DB2 Plan name The name of the database request module (DBRM) associated with the module making the first SQL call. If your program can make its first SQL call from different modules with different DBRMs, then you cannot use a default plan name; you must use an explicit call using the OPEN function If your application includes both SQL and IFI calls, you must issue at least one SQL call before you issue any IFI calls. This will ensure that your application uses the correct plan. There are different types of implicit connections. The simplest is for application to run neither CONNECT nor OPEN. Or, you can omit just CONNECT, or just OPEN. Each of these is a form of implicit connection, and requires appropriate calls to terminate your connection. See Table 45 on page 421 for details. Since the implicit or explicit connection to DB2 must be successfully established before the execution of any SQL calls to the CAF DSNHLI entry point, the application program must first determine the success or failure of all implicit connection requests prior to examining any SQLCODEs. For implicit connection requests, register 15 contains the return code and register 0 contains the reason code. The application program should examine the connection codes immediately after the first executable SQL statement within the application program. If the implicit connection was successful, then the SQLCODE associated with the first SQL statement, and subsequent SQL statements can be examined. ================================================================ DB2 Version 2 Release 3 Application Programming and SQL Guide, SC26-4377-02, page 421: Replace the text of the third bulleted item under "Summary of CAF Behavior" with the following (the last sentence has been changed): Summary of CAF Behavior ----------------------- o The intersection of a row and column shows the effect of the call if it follows upon the corresponding connection history. For example if the call is OPEN and the connection history is CONNECT, the effect is OPEN: the OPEN function is performed. If the call is SQL and the connection history is empty (the SQL call is the first CAF function in the program), the effect is that an implicit CONNECT and OPEN function is performed, followed by the SQL function. ================================================================
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for Internet viewing
APAR Information
APAR number
II06453
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-10-19
Closed date
1997-11-07
Last modified date
1997-11-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 December 2020