My PowerShell library for WebSphere MQ has been out for a month or so now, and it seems to have been well-received. I’ve seen a surprising amount of blog posts and news articles about it, the download stats for the SupportPac are very encouraging, and I’m getting a steady (if slowly growing) stream of emails with requests for help and new features.
There is still more to finish with the WMQ library – the biggest piece of outstanding work is adding support for z/OS queue managers, but there are a few other bits and pieces to do as well.
But even so – with my usual attention span of an easily distracted child, I’m starting to look at what I might try next.
I’m thinking a PowerShell extension for DB2 might be a good next step.
Why?
- Like WebSphere MQ, the prospect of writing it is made much easier by the fact that there is already a .NET API and support for building C# applications for DB2
- Database administration seems to lend itself quite well to PowerShell’s object-oriented nature. Using Select, Where, et al. still reminds me of SQL pretty much every time I type it
- I know very little about DB2, and it’d be a chance to learn something new
Okay, so my third reason sounds a little weak, but on a personal level, it’s a consideration.
But would there be a demand for supporting DB2 administration using PowerShell? I don’t know… I’ve not heard anyone ask for it, and other than a post on a developerWorks forum, I haven’t been able to find much of a call for it.
Still, it’s an interesting idea.
