PH29534: IMS DFS0915I MESSAGE WHEN CREATING SECONDARY INDEX DATABASES WITH /SX FIELD USING DDL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• There are several problems with defining a SIX using the system
  related field /SX to make secondary index keys unique.
  
  DDL Example (only DDL relative to /SX field):
  "/SX1" CHAR
  INTERNALNAME "/SX1",
  .
  .
  LCHILD SS2.SS2
  INDEX,
  XDFLD SS2KEY,
  SRCH(FIELD1,FIELD2,FIELD3)
  SUBSEQ("/SX1")
  
  Here are the issues found when defining /SX field with DDL.
  Also, as documented, "the length of a /SX system-related field
  is known and therefore, when specified, the BYTES parameter is
  disregarded".
  
  (1) When just "/SX1", coded:
  java.sql.SQLException: -104: Illegal symbol , was used.
  Legal symbols might be: ARRAY BINARY BIT BY..
  
  Note: ("Data Type" should not be required on /SX Field
  definition)
  
  (2) When "/SX1" INTERNALNAME "/SX1", coded:
  java.sql.SQLException: -199: Illegal use of INTERNALNAME was
  detected. Expected token is ARRAY BINA..
  
  Note:  ("Data Type" should not be required on /SX Field
  definition)
  
  (3) When defining "/SX1" as 1 Byte field, DFS0915I is generated
  in DLISAS:
  DFS0915I INDEX DBD --SS2 -- HAS INCORRECT SEQ FIELD LENGTH.
   LENGTH SHOULD BE n BYTES.
  (n bytes includes data type length provided in DDL, should be
  ignored)
  
  (4) When defining "/SX1" as a 4 byte field:
  STDERR:
  com.ibm.ims.dli.PSBInternalFactory createPSB
  INFO: IMS Universal Drivers build number: 15116
  java.sql.SQLException: -8005: IMS returned the AIB return code
  00000108 and the reason code 0000071F
  
  DLISAS (1 or more DFS0931I messages):
  DFS0931I INVALID INDEX RELATIONSHIP BETWEEN INDEX DBD --SS2 --
  AND INDEXED DBD --"primdb" -- IN PSB --"dbd"
  
  Note: Correct length provided for /SX field but still these
  errors produced.  AIB Reason code x71F not documented.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IMS V15 users of DDL.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * DDL CREATE statement with secondary index results in         *
  * DFS0915I and DFS0931I message.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  Problem 1
  DDL CREATE TABLE with  /SX1 field results in  DFS0915I: INDEX
  DBD --<DBDNAME>-- HAS INCORRECT SEQ FIELD LENGTH. LENGTH SHOULD
  BE --025 BYTES
  Problem 2
  DDL CREATE TABLE without SINGLE results in DFS0931I: INVALID
  INDEX RELATIONSHIP BETWEEN INDEX DBD <DBDNAME> AND INDEX DBD
  <DBDNAME>
  Probelm 3
  DDL CREATE PROGRAMVIEW for logical DBDs results in -9055: SENSEG
  <TABLENAME> FROM SCHEMA <DBNAME> NOT FOUND IN <LOGICAL DBDNAME>
  

Problem conclusion

• DFSDDL20 module was changed to support CHAR without BYTES
  specified.
  DFSDDL10 module was changed to default to SINGLE for LCHILD
  INDEX field.
  DFSDDL10 module was also changed to set workdone when it is the
  root element.
  
  Additional Keywords: IMSDDL/K
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI73813

Modules/Macros

• DFSDDL20 DFSDDL10
  

Fix information

• Fixed component name

  IMS V15

• Fixed component ID

  5635A0600

Applicable component levels

• R500 PSY UI73813

     UP21/02/09 P F102 &

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.