DDWKEY0013 in job BDUPG06, BDACTDD2, or AXACTDD2
Article ID: 30694
Updated On:
Products
Issue/Introduction
Datacom upgrade job receives DDWKEY0013 errors in STEP6C of job BDUPG06 (or in step STEP2B of job BDACTDD2 for Datacom/DB or job AXACTDD2 for Datacom/AD).
This step is running -CXX BUILD,DATABASE,DDD-DATABASE(PROD,DD,PRIV)
I received these warning messages:
*** VERIFY WARNING MESSAGES ***
DDWKEY0013 SIGNED NUMERIC FIELD IN KEY
ENTITY=SYSCONSTROBJ.RAAT-KEY
DDWKEY0013 SIGNED NUMERIC FIELD IN KEY
ENTITY=SYSCONSTROBJ.SQLNAME-KEY
DDWKEY0013 SIGNED NUMERIC FIELD IN KEY
ENTITY=SYSCONSTRSRC.SOURCE-KEY
DDWKEY0013 SIGNED NUMERIC FIELD IN KEY
ENTITY=MSG-TABLE.MSGKY
Is this expected or something of concern?
Environment
Component : Datacom/DB
Component : Datacom/AD
Cause
These are only warnings - see further explanation below.
Resolution
The DDWKEY0013 message is a warning that a key contains signed numeric fields. It just tells you that a field that makes up a key is signed numeric. This is normal for the DDD-DATABASE and can be ignored. The JCL for the BDACTDD2 and AXACTDD2 jobs contains the message, "Expected Condition Code EQ 04 (or less)."
Therefore, in these steps, the messages are to be expected and are not a problem. These steps with only these messages should be considered successful.
From the DDWKEY0013 message description:
Reason:
During the verification of a DATABASE structure, a KEY substructure was detected that contains a FIELD entity-occurrence with a TYPE attribute-value of N or D and a SIGN attribute-value of Y. Use of a signed numeric FIELD entity-occurrence in a key can cause the data records to be sorted and retrieved in a different sequence than expected.
Action:
This is a warning message only. No action is required if this manner of sorting and retrieval is acceptable. To obtain a logical sorting sequence, change the KEY entity-occurrence DATA-SENSITIVE attribute-value to Y.
Additional Information
As always, please contact Broadcom support for Datacom if you have further questions.
Feedback
