Re: IA64 Librarian corrupts TLB's

The libraries were all originally created on VAXen running VMS 6.2 and earlier The compression was done to save disk space. Back in those days we were working on RL02's and RA60's, so ...

In any case the libraries have not been compressed or rebuilt for years. This corruption started when we converted our software to run on the IA64 and did the editing and re-insertion into the source libraries from the IA64. Going through this process we have found that there are many undocumented new features (bugs) in hte IA64 porting of VMS.

We have an AXP running 8.4, so are surprised that it can't read these libraries that as far as AXP and VAX are now corrupt.

The problem is that we are dealing with thousands of libraries not one or two. We also use tlb's on large customer systems to store production data. They run in mix architecture clusters. The cusotmers haven't yet been bitten by this problem, but when is happens we need to be able to quickly repair and move forward. They do not compress their libraries.

If this is corrupt libraries or latent issues with the compatibility with older text libraries, then there's a wildcard-library-extraction libext-based DCL bulk-extraction tool here; that'll serve as a building block that can allow you to bulk-rebuild these libraries.

For grins, I might try turning off DCX. But whether DCX or enabled or not, this stuff should be compatible. So head for the patches.