Domain-neutral?

Having been active in the job market for awhile, I have been surprised that while there are numerous project management opportunities out there, a long term IT PM seemingly has less chance of being a fit for them. The reason for this is that a majority of these
job posting are domain-specific.

How does this lessen the chance of a seasoned PM being a fit? Let's look at an example:
Let's say that you were a whiz-bang C programmer back in the 80's or early 90's (yeah, you know, back in the last century), and you evolved into a leadership position, first as a team lead, and then as a "Project Manager". You find that you are good at project management and before you know it, you realize that you have done 6 or 7 projects. Since you like what you're doing, you decide that this is something to pursue for the rest of your career. What's wrong with that?

The real problem is that once you commit to being a professional project manager, you attack the profession with passion and energy to the exclusion of what got you to that level... and your once-formidable technical skills wither. In and of itself, this is not a bad thing....just as long as you stay in the same enterprise. If you are downsized, or otherwise find yourself jobless, you awake to a job market that wants PM skills AND Java, or Ab Initio, or SAP, etc.

If you are a domain-neutral PM, you will find that more than 85% of the project manager positions that are listed are requiring specific technical skills, or particular industry experience to go along with that PMP of yours.

There is an obvious message in here for you young-uns of the PM congregation out there: "Keep your tech skills sharp....and stay abreast of current technology!!"