II08290: CHANGES TO DB2 APPLICATION PROGRAMMING & SQL GUIDE SC26-4889-00 THAT DID NOT MAKE V.3 GA PUBS. CONTINUED IN II07606 & II08058.

APAR status

• Closed as canceled.

Error description

• 5740xyr00 R310 DB2
  This info. APAR documents changes to the DB2 Application
  Programming & SQL Guide SC26488900 which did not make the GA
  pubs.  Continuation of II07606 & II08058. Continued in II09789.
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 3-15
  Change Description:
  In the CICS box under heading "Obtaining the Text for a
  Message" under the second paragraph, add:
  
     "If you use DSNTIAC, be sure to
      define both DSNTIAC and DSNTIA1 to CICS in the CSD."
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 3-44
  Change Description:
  In Table 9, change the notes for DECIMAL(p,s) to these:
  
     p is precision; s is scale.  1<=p<=31 and
     0<=s<=p.  1<=n<=16.  value is a literal value
     that includes a decimal point.  You must use Ln,
     value, or both.  We recommend that you use
     only value.
  
     Precision:  If you use Ln, it is 2n-1; otherwise,
     it is the number of digits in value.
  
     Scale:  If you use value, it is the number of digits
     to the right of the decimal point; otherwise, it is 0.
  
     For Efficient Use of Indexes:  Use value. If p is even,
     do not use Ln and be sure that the precision of
     value is p and the scale of value is s.  If p is
     odd, you can use Ln  (although it is not
     advised), but you must choose n so that 2n-1=p,
     and the scale of value is s.  Include a decimal
     point in value, even when the scale of value is 0.
  ============================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages:  3-61
  future change, not in manual yet (11-14-95)
  under the DYNAM and NODYNAM COBOL compiler options add:
  CAF: You must specify the NODYNAM option when compiling a
       COBOL program that includes SQL statements. DYNAM is not
       allowed and will cause (-927) SQLcode927.
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 3-61
  Change Description:
  In "Special COBOL Considerations,"   Add this bullet:
  
  - Observe the rules in the SQL Reference when you name SQL
    identifiers.  Do not use hyphens in an SQL identifier or
    begin the identifier with a digit.
  
  Change the bullet on hyphens to this:
  
  - Observe these rules for hyphens:
  
    - Surround hyphens used as subtraction operators with
      spaces.  DB2 usually interprets a hyphen with no spaces
      around it as part of a host variable name.
    - Do not use hyphens in SQL identifiers.  You cannot bind
      SQL statements remotely that have hyphens in SQL
      identifiers.
  ============================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages:  3-61
  Change Description:
    Deleted the last sentence of bullet 3 on the page:
  
    "The addresses of the host variables cannot be changed
  later, although the values within them can be changed."
  ================================================================
  Version 3 Book Title:  Application Programming and SQL Guide
  Pages:  3-61
  Change Description:
  Under "Special COBOL Considerations" first bullet first box,
  (TSO and IMS) the last sentence changed from:
    If you are using IMS, the IMS RESLIB must precede the
    SDSNLOAD library in the link list, JOBLIB, or STEPLIB
    concatenations.
  To:
    IMS and DB2 share a common alias name, DSNHLI, for the
    language interface module.  You must do the following when
    you concatenate your libraries:
    - If you use IMS with the COBOL option DYNAM, be sure to
      concatenate the IMS library first.
    - If you run your application program only under DB2, be
      sure to concatenate the DB2 library first.
  ================================================================
  Version 3 Book Title:  Application Programming and SQL Guide
  Pages:  3-61
  Change Description:
    Special COBOL considerations bullet 6 is changed from:
      . Hyphens cannot be used in ordinary SQL identifiers if
        SQL statements are bound remotely to a non-DB2 server.
    to:
      . Do not use hyphens in ordinary SQL identifiers if you
        bind SQL statements remotely.
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 3-66
  Change Description:
  Add to the bulleted list at the bottom of the page:
  o  An SQL statement within an included member
  In Version 3, change the paragraph before the bulleted
  list to be the same as the Version 2.3 book, which is:
   A host structure is complete if it contains one of the
   following.  The precompiler does not recognize host
   variables or host structures on any subordinate
   levels after one of these items:
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages:  4-10
  Change Description:
  Add the following paragraph on p.4-10 under the heading
  "Automatic Rebinding" before the paragraph that begins "For
  some changes, you must initiate...":
    If you encounter lock contention during an automatic
    rebind, DSNT501I messages do not accompany any DSNT376I
    messages that appear.  To see the matching DSNT501I
    messages, you must explicitly rebind the plan or package.
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 4-17
  Change Description:
  Change the box at the bottom of the page to this:
  
  +--TSO, Batch, and CAF-------------------------------------+
  |  When a deadlock or timeout occurs in these environments,|
  |  DB2 sets SQLCODE -913 in the SQLCA for one of the       |
  |  applications and attempts to roll back the SQL for that |
  |  application. If the ROLLBACK is successful, DB2 replaces|
  |  SQLCODE -913 with SQLCODE -911. If ROLLBACK fails,      |
  |  SQLCODE -913 remains in the SQLCA. Because an           |
  |  application normally abends when ROLLBACK fails,        |
  |  however, the application is unlikely to receive         |
  |  SQLCODE -913.                                           |
  +----------------------------------------------------------+
  ==============================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 4-61
  Change Description:
  Add the following sentence to the description of VERSION
  in the DB2 Precompiler Options table:
  
  The timestamp used is based on the System/370 Store Clock
  value.
  ============================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 4-72, 4-76
  Change Description:
  The following text was added to page 4-72, at the end of
  the paragraph beginning "If the CURRENT PACKAGESET register
  is set":
  
  "Explicitly specifying the intended collection with the
  CURRENT PACKAGESET register can avoid a potentially costly
  search through the package list when there are many
  qualifying entries."
  
  The following text was added to page 4-76, at the end of
  the topic "Using DEFER (PREPARE) with Distributed
  Processing":
  
  "When you use DEFER(PREPARE) with application directed
  access, the package containing the statements whose
  preparation you want to defer must be the FIRST
  qualifying entry in DB2's package search sequence.
  (See "Identifying Packages at Run Time" on page 4-71
  for more information.)  For example, assume that the
  package list for a plan contains two entries:
  
  PKLIST(LOCB.COLLA.*, LOCB.COLLB.*)
  
  "If the intended package is in collection COLLB, ensure that
  DB2 searches that collection first.  You can do this by
  executing the SQL statement
  
  SET CURRENT PACKAGESET = 'COLLB';
  
  or by listing COLLB first in the PKLIST parameter of
  BIND PLAN:
  
  PKLIST(LOCB.COLLB.*, LOCB.COLLA.*)
  
  "For NODEFER(PREPARE), the collections in the package list
  can be in any order, but if the package is not found in the
  first qualifying PKLIST entry, there is significant network
  overhead for searching through the list."
  ===========================================================
  Version 3 Title:  DB2 Application Programming and SQL Guide
  Page:  4-78
  Change Description:
  Add the following paragraph at the end of the section titled
  "Running a Program in TSO Foreground":
  DSN RETURN CODE PROCESSING: At the end of a DSN session,
  register 15 contains the highest value placed there by any
  DSN subcommand used in the session or by any program run by
  the RUN subcommand.  Your run-time environment might format
  that value as a return code.  The value DOES NOT, however,
  originate in DSN.
  ================================================================
  Version 3 Book Title:  Application Programming and SQL Guide
  Pages: 4-128, 4-130, 4-133
  Change Description:
  Page 4-128:  Change the third bullet under "Requirements for
  Using DB2 in a DL/I Batch Job" to:
  
   You must either specify an input data set using the DDITV02
   DD statement, or specify a subsystem member using the
   SSM= parameter on the DL/I batch invocation procedure.
   Either of these defines information about the batch job
   step and DB2.   For detailed information, see "DB2 DL/I
   Batch Input" on page 4-130.
  
  Page 4-130:
  
  Change "Use of the DDITV02 Data Set" to "DB2 DL/I Batch
  Input".  Delete the first paragraph under "Use of the
  DDITV02 Data Set".
  
  Change the second and third paragraphs to:
  
   The DB2 DL/I batch support uses the IMS attachment
   facility.  You can provide the required input in one of
   two ways:
  
   o  Use a DDITV02 DD statement that refers to a file
      that has DCB options of LRECL=80 and RECFM=F or FB.
  
   o  Name an IMS subsystem member on the SSM= parameter in
      the DB2 DL/I batch invocation.  The subsytem member name
      is the value of the SSM parameter concatenated to the
      value of the IMSID parameter.
  
   If you both use the DDITV02 DD statement and specify a
   subsystem member, the DDITV02 DD statement overrides the
   specified subsystem member.  If you provide neither, then
   the DB2 DL/I support abends the application program with a
   system X'04E' abend code and a unique reason code in
   register 15.
  
   The fields in the subsystem member specification or DDITV02
   data set, which are positional and delimited by commas,
   are:
  
      SSN,LIT,ESMT,RTT,ERR,CRC,CONNECTION_NAME,PLAN,PROG
  
  Page 4-133:  Add a bullet after
    o In the DDITV02 input data set
  that says:
  
    o In the DB2 DL/I batch subsystem member specification
  ================================================================
  Version 3 Book Title: Application Programming and SQL Guide
  Pages: 5-114
  Change Description:
  Replace the second paragraph under "CALL DSNALI Parameter
  List" with this:
  
  When you code CALL DSNALI statements, you must specify all
  parameters that come before Return Code.
  You cannot omit any of those parameters by coding zeros or
  blanks.  There are no defaults for those parameters for
  explicit connection service requests.  Defaults are
  provided only for implicit connections.
  
  All parameters starting with Return Code are
  optional.  For all languages except assembler language,
  code zero for a parameter in the CALL DSNALI statement
  when you want to use the default value for that parameter
  but specify subsequent parameters.  For example, suppose
  you are coding a CONNECT call in a COBOL program.
  You want to specify all parameters except Return Code.
  Write the call in this way:
  
       CALL 'DSNALI' USING CONNFN SSID TECB SECB RIBPTR
          BY CONTENT ZERO BY REFERENCE REASCODE SRDURA.
  
  For an assembler language call, code a comma for a parameter
  in the CALL DSNALI statement when you want to use the
  default value for that parameter but specify subsequent
  parameters.  For example, code a CONNECT call like this to
  specify all optional parameters except Return Code:
   CALL  DSNALI,(CONNFN,SSID,TERMECB,STARTECB,
                 RIBPTR,,REASCODE,SRDURA)
  ============================================================
  This APAR is continued in II09789.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• close for INTERNET viewing
  

APAR Information

• 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