Would appreciate help with a strange problem

[Clive Lansink]

Hi everyone.

I am trying to use an account on our OpenQM system that has been disused for some time. All the files appear to be there but strange things are happening.

I tried set-file to set a qfile pointer to a file in another account. That should create a qfile entry in the voc but it's not there. I have confirmed that programs like set-file and my own programs report that they can't open file voc. As yet I haven't found the reason why as these same programs do open the voc in other accounts.

But if I go to another account and do set-file account-name voc to set a qfile pointer to the voc in the account I am working on, then these programs do open qfile and can create entries in this same voc. It's just that these programs say they can't open voc from within the account itself.
I can successfully use ed to create items in the voc.

Can anyone explain what the problem might be and what to do to fix it?

Thank you.


Clive Lansink
Email: Cl...@Lansink.Co.NZ
Phone: +64 9 520-4242
Mobile: +64 21 663-999

[ERICM76903]

Personally, I would start with three things:

1. Check the VOC record in the account in question. Make sure it is valid.

2. At the OS level, make sure that the VOC  directory is present and is dynamic, meaning that there are  %0 and %1 files there.

3. You said your programs fail when trying to open the VOC. Have you used STATUS with the ON ERROR or ELSE clause of the OPEN statement? If so, the STATUS gets you the error number which in turn you can use to get the error text with the !ERRTEXT subroutine.

That's where I would start.

E.

[Brian Speirs]

Hi Clive,

My initial thoughts are to check the file permissions (at the O/S level). On the other hand, it makes no sense that you can update the VOC using ED, or through a Q-pointer from another account, but not from within the account - because the file permissions should the same in all instances.

Does this account use a different LOGIN paragraph? Is there anything in that LOGIN paragraph that will affect user permissions? Is there a security subroutine on the SET.FILE entry in the VOC of the account?

If the worst comes to the worst, then rename the account at the O/S level, and delete it from QM.ACCOUNTS. Then recreate the account, and get a program to recreate the files in the new account and copy the data from the old account. That is a bit tedious, but it should get you a working account.

Cheers,

Brian