Sorry if the information sources were not helpful. I do not have access to big iron, so cannot even begin to try this stuff out. If the module itself was solid, then I might be able to resurrect enough of my memory from the little I did with VSAM under MVS back before the dawn of time to help you--though you seem to have a pretty good handle on it yourself--but if the module itself is flaky, there is pretty much nothing more I can offer.
It sounds as if your next best option will be to try and contact the modules author, and if that doesn't produce satisfactory results you may be faced with the prospects of trying to:
- fix the module yourself.
You'll need some C skills and a lot of reading on XS to understand what is going on in Studio.xs
- Resort to using another language.
REXX is pretty easy to pick up if you are not already familiar with it, and from my brief look at the IBM documentation links I provided, will support full access to VSAM datasets. And via IBM supplied/tested libraries.
If you would rather do the bulk of your work in Perl, you could consider using REXX to read/write the datasets and then invoke perl from within the REXX to do the rest. Not elegant, but Perl regex are rather more flexible than PARSE.
Again, sorry if the information didn't help you solve your problem.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Well, that's what I feared.
We'll have to migrate our old VSAM files into database tables to be able to access them. Well, maybe not the worst way to deal with the issue but the access to VSAM would habe been cool.
| [reply] |