SYSALIASES & VOC QFILES (AREV Specific)
At 13 JAN 2004 04:47:37AM Craig X Tildesley wrote:
I am having real trouble with permanent QFILEs. Having read TB21 which states that VOC type of QFILE will allow me to permanently point at the file in question I was a little disappointed to discover that it doesn't work anymore. I realised, of course, that SETALIAS sets up entries in the SYSALIASES file when the W options is used. However, I can only get permanent pointers to work when I point at a data location which doesn't have a VOLUME label using an absolute path. This is a little disapointing as I have test areas to set up as well as live and of course if the system changes path then things become trickier.
Does anyone have any info about why this happens or any handy workaround?
At 13 JAN 2004 10:22AM Victor Engel wrote:
] However, I can only get permanent pointers to work when I point at a data location which doesn't have a VOLUME label using an absolute path.
This statement is ambiguous. Are you saying that using an absolute path is what makes it work or what makes it not work? Maybe if you rephrase the question…
Getting back to what I think is the issue, though, the SETALIAS command only sets up the pointer. You still have to attach the volume the file is located on, or the specific table using the qfile name.
At 13 JAN 2004 11:29AM Craig X Tildesley wrote:
Fair enough.
Using a filepath to reference the qfile works. Using a volume label doesn't work. And of course you can't just reference the labeled volume with its filepath as it complains of a duplicate entry.
At 13 JAN 2004 03:58PM Victor Engel wrote:
It sounds like maybe you have a stale setattach image. Try refreshing it and see if that solves the problem. I've never used setattach images except on an experimental basis, so I can't help further if it's a setattach issue.