DDFBWT0009 INVALID STATUS FOR ENTITY-TYPE
Article ID: 272570
Updated On:
Products
Issue/Introduction
I'm trying to setup a process for changing a NAME attribute in the PERSON Table in the DataDictionary using the 7156 transaction card with DDUPDATE.
-UPD PERSON,JMZTST1(PROD,DD)
1000 RESTORE,T001
-END
-UPD PERSON,JMZTST1(T001)
7156 JOHN SMITH
-END
-CPY PERSON,JMZTST1(T001,DD),PROD
-END
-RPT DETAIL,PERSON,RFD001(PROD)
-END
I am getting the following error message. What am I doing wrong?
DDFBWT0009 INVALID STATUS FOR ENTITY-TYPE
Environment
Release : 15.1
Resolution
In this case, since the PERSON entity type was being updated and is part of the ENT-MAINT and not a part of the DB-MAINT, you do not have to follow the DB-MAINT convention of restoring to test, make changes in test, promoting TEST to PROD, then cataloging.
You can simply update the PROD versions if changes are need to be done with entity types that deal with ENT-MAINT or FILE-MAINT. So the following JCL below would be correct for this entity type
-USR DATACOM-INSTALL,NEWUSER
-UPD PERSON,JMZTST1(PROD,DD)
7156 JOHN SMITH
-END
-RPT DETAIL,PERSON,JMZTST1(PROD)
-END
Additional Information
To see what can or cannot be done in batch (DDUPDATE) you can log onto Data-Dictionary Online (DDOL) to see if the options exist.
Example:
Going into DB-MAINT >> Option 1 DATABASE panel P01M has the following options. Note that there is a RESTORE option.
Going into ENT-MAINT >> panel P02M has the following options. Note that there is not a RESTORE option and there is a UPDATE option to update some attributes directly in PROD. So restoring an entity type that is a part of ENT-MAINT is not valid since it does not exist in DDOL.
The following below includes a list of the DB-MAINT entity types and the following transactions if done in batch via DDUPDATE. To see the full list of entity types that are non-DB-MAINT related, please look into the DDUPDATE documentation along with ENTMAINT mode and FILEMAINT mode
Feedback
