DB2 to IDMS

[Anon Anon]

Tired of hearing that IDMS is a dinosaur, we decided to buck the trend and recently converted our DB2 databases & batch applications to IDMS SQL. Overall the process was rather simple and the code changes minimal. The only down side was the need to create additional indexes that contained all the columns in the predicate in order to maintain performance. The driving factor behind the conversion was cost, since we already had our main applications running in IDMS.

[Legacy User]

Way to go Grant!

 

Just curious, have you turned on anything like the SQL Cache or caching the database in 64-bit storage or dataspaces to see if that helps performance?

 

Chuck

[Anon Anon]

Thanks Chuck.

 

The application is static sql, so I don't think the sql cache will help here? The database was rather large, 132GB, so I tried playing with dataspace, but we found getting the extra index to allow a leaf scan seemed to resolve the issue.

[Chris Hoelscher]

What did you do with sequences? Just convert them to OOAK record types?

 

Chris hoelscher

Technology Architect | Database Infrastructure Services

Technology Solution Services

 

123 East Main Street |Louisville, KY 40202

[e-mail]

Humana.com

[phone] – office

[phone] - blackberry

Keeping CAS and Metavance safe for all HUMANAty

[Anon Anon]

The application didn't have any sequence functionality so we didn't have to worry about that one.

[Edward Gorga]

Grant, thanks for letting everyone know about this.

[Jan Rabaut]

Quite interesting

You converted to a network schema or a SQL schema?

 

How many tables contains the DB?

 

Jan Rabaut ... From my mobile, sorry if the message seems terse

[Anon Anon]

Thanks for the feedback. We converted to an SQL schema. The database was comprised of only 26 tables and132gb in size, which on our current platform took a while to unload and reload using standard DB2 and IDMS utilities.

[Anon Anon]

Thanks Ed – the conversion shows that IDMS is a viable option to DB2.