Posted: Thu Nov 17, 2005 10:54 pm
The routine is obviously adapted from the 'KeyMgtGetNextValueConcurrent' sdk routine. It was the sdk development team that, in their infinite wisdom, decided to use SeqFile to refer to the Sequence File the routine manipulates. Yes, it is confusing.ray.wurlod wrote:The original problem seems to relate to the SeqFile variable in the ReadU statement. (Unrelated question: why use this name for a hashed file? It only confuses future developers.)
Yes, the permissions issues are fairly specific and obvious. The CREATE and DROP discussion came into play because the OP was attempting to use DELETE.FILE and the routine as posted uses 'CREATE TABLE' if the initial open fails. Simple as that.ray.wurlod also wrote:The subsequent questions about CREATE TABLE and DROP TABLE don't really belong in this thread. But "permission denied" is a fairly specific diagnostic message. Either operating system permissions or SQL privileges are preventing you from dropping the table.