HE - model management - batch options

[Gagan Kakkar]

Hi there,

If I want to update model info (e.g. rename & change owner) in batch can I just update HE data table: DMDL (I could use DNSTEP2/DNSTEP4) or do I have to update any other table also ?

Thanks.

------------------------------
Gagan
IT Consultant (Mainframe)
------------------------------

[Carlo Jamar]

Hi Gagan,

just saw your question hasn't received any answers yet. 

In case you are still wondering, the answer is Yes. DMDL is the only table that holds the model name and owner; updating DMDL will effectively change the model.

Be aware that you are updating the encyclopedia tables directly, so proceed with caution.  Also make sure the models (nor any subsets) are checked out.

Carlo

[Gagan Kakkar]

Thank you Carlo. Yes, I concur I have to be extra careful while updating the encyclopedia tables directly.

------------------------------
Gagan Kakkar
IT Consultant (Mainframe)
Ph: [phone]
------------------------------

[Carlo Jamar]

Noticed a rather important typo in my reply. Below is the obvious correction ... 

make sure the models (nor any subsets) are NOT checked out.

Carlo

[Gagan Kakkar]

Thanks Carlo. Yes, I did notice the obvious typo. :))

I have one more question...Say if I have to update a couple of things for a model in batch - Change Owner & Grand Read Access, do I have to update DHLOG data table as well with appropriate HLG_ACTIVITY_TYPE type (e.g. or Change Owner :  'CHG OWNER' and for Read Access: GRANT ACCE).  ??
Any other HE data table I have to update ??  DSUBUS ??

Thanks !

------------------------------
Gagan Kakkar
IT Consultant (Mainframe)
Ph: [phone]
------------------------------

[Lisa.West]

I would not recommend updating the tables directly.  In addition to updating the DMDL and DHLOG tables, the rename model will sometimes update the DFAMILY table. It also updates the name of the root subject area. There is also validation logic that validates the user has the correct authority to update, model and subsets are not checked out, new name does not exist, enques model so concurrency is preserved correctly, etc...  Also, you are correct that the model grant access logic updates the DSUBUS table.