QKDFK

[heaslips@ozemail.com.au]

Aha! Thanks Chris - problem solved.

It turns out I don't have some permission required to write a new version of that executable.

Originally I was getting a similar error in the same place but specifying "Failure to access the file (QKMNU)".  
The cause of this was that the logical QKMNU wasn't defined. I found a .QKM file and set the logical, and then started getting the QKDFK error message in the same place.
I assumed (I know - never assume) the problem was the same sort of thing - that a logical for QKDFK wasn't defined correctly, or that some file didn't exist. 

When you suggested the problem might be the permissions on the SYS$SCRATCH directory it made me re-think the whole thing from that angle.
I knew I had the privileges for the SYS$SCRATCH area okay, but when I checked my privileges for the EXE directory I found that was the cause of the problem. 
The strange part is that other screen programs specify the same executable directory and they don't give this same error.

Anyway I'll create my own executable directory instead of using the old generic development executable area (I'm the only developer, so I wasn't going to bother - until now) and define the EXE logical to point there first.

Thanks for the help.


Regards,
 
Steve Heaslip
 
Email:  heaslips@ozemail.com.au
 

-----Original Message-----
From: powerh-l-admin@lists.sowder.com [mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Chris Sharman
Sent: Friday, 20 May 2005 18:30
To: PowerH List
Subject: Re: QKDFK

heaslips@ozemail.com.au wrote:

> G'day all
>  
> We've a client with a legacy system (no work has been done on the system for years) and I've just tried to re-compile a few screens.
> For some screens I'm getting the following error message immediately after the SCREEN statement:
>  
> *E* Failure to access the file (QKDFK)
> %RMS-E-CRE, ACP file create failed 
> %SYSTEM-W-NOSUCHFILE, no such file 
> "
> 
> Can anyone shed any light on this? Is Quick trying to create a file here? Or is it trying to find a file? Currently there is a logical QKDFK that is just pointing to SYS$SCRATCH. Should it be pointing somewhere else?
> Any advice would be appreciated.

Is sys$scratch pointing to a directory that exists & is writeable ?
Not seen this error myself, but it looks like the directory is either 
missing or protected, or possibly the old version of the file (which 
you're about to 'mask' by creating a new version) is protected from your 
ownership, writing, or deleting - when you create a new version it 
inherits most of the attributes, which can be a problem if the original 
belongs to someone else.
I'd recommend pointing sys$scratch somewhere clean, empty, and writeable.
The other thing to watch for with PH is .sf files with missing .sfd 
files, or vice versa.

Chris




This message was sent through MyMail http://www.mymail.com.au