|
View previous topic :: View next topic
|
| Author |
Message |
Bharath RajaramSridharan
New User
Joined: 10 Dec 2012
Posts: 20
Location: Australia
|
|
|
|
Hi,
In the site that am currently working, we have lot of IMS DB. I am working as part of the SIT Environments team where we would like to get notified whenever the DBA's change the structure of the IMS DB.
How can I automatically build a system which I will notify me the changes. Any pointers will help me develop such automation.
Thanks! |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| we would like to get notified whenever the DBA's change the structure of the IMS DB. |
changing the structure of an IMS DB is not something that gets done every day,
usually there are business reasons for the change and a paper trail which documents it.
ask to be put on the distribution list . |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
| There are IBM and third party utilities that will "decode" the IMS DBD and PSB library entries. You could run them and compare the outputs. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
| What happens when you change the DB? If you change the programs or any other modules then set up a dependant job which sends You/DL email regarding these changes. |
|
| Back to top |
|
|
Gary Jacek
New User
Joined: 17 Dec 2007
Posts: 64
Location: Victoria, BC, Canada
|
|
|
|
If you use traditional IMS MPP or BMP programs, then the DBAs who manage IMS databases must perform DBDGEN, possibly PSBGEN and ACBGEN whenever they make structural changes to IMS databases. These same DBAs will generally be updating the COPYBOOK members that map the database segments, whenever they make a change.
BMP and MPP applications are somewhat insulated from these very infrequent changes. You may have to recompile if a COPYBOOK member is changed. If a segment your program uses is dropped, well you have bigger problems.
If on the other hand, you are using other tools to look at IMS data, then I have four suggestions:
1. If you are not already there, upgrade to IMS V12 or V13. (V11 goes out of support at the end of October this year)
2. On V12 or V13, enable and use DFS3PU00 to populate the IMS Catalog. Then have your DBAs update their ACBGEN processes to use DFS3UACB to keep the IMS Catalog updated.
3. IMS Catalog contains all the metadata about the databases and segments in IMS. You should use the IMS Catalog tooling to import field level information into the IMS Catalog from PLI structures or COBOL COPYBOOKS. In this way, data about the data, is kept right on IMS where it can be kept in sync.
4. Go out to your vendors and ask them when they will support the IMS Catalog, rather than making you re-key metadata about IMS databases. And start using IMS Enterprise Suite to see how you can get at IMS data and IMS metadata via the JDBC interface.
IMS Catalog is the next big thing. It has huge potential. |
|
| Back to top |
|
|
|
|
