Conference annecy::ftso

108.0. "set alias command fails with ACCVIO" by COMICS::SHELLEY (Lead, follow, or get out the way) Thu Apr 10 1997 21:18

Hi,

A customer has just purchased and installed FSTO V1.3.1 on a MicroVax 
running VMS 6.1, however when they try to add an alias the command 
fails as shown:-

$ ftso set alias /system test1 nmrlond_x/administrator/xxxxxxx "c:\temp\"
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000000,
PC
=000AFB68, PSL=0BC00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents
 
        Number = 00000005                00000000
        Name   = 0000000C                20FC0000
                 00000004                7FEACBBC
                 00000000                7FEACB94
                 000AFB68                0001636B
                 0BC00004                00000000
                                         00000000
                                         00000000
                                         00000001
                                         00078300
        Register dump

        R0 = 04000005  R1 = 000056F0  R2 = 00000005  R3 = 00000000
        R4 = 00000000  R5 = 00000000  R6 = 0000002F  R7 = 0000002A
        R8 = 00000448  R9 = 00006F5C  R10= 00009508  R11= 00006E58
        AP = 7FEACB08  FP = 7FEACAC8  SP = 7FEACB44  PC = 000AFB68
        PSL= 0BC00004


They tracked this down to the fact that is no file called FTSO_ALIAS.DAT
located in SYS$SYSDEVICE:[FTSO], if they create a 0 block file with the above
name the command works, however the SHOW ALIAS and DELETE ALIAS commands
produces strange results as shown:-

$ cre sys$sysdevice:[ftso]ftso_alias.dat
 Exit
$ ftso set alias /system test1 nmrlond_x/administrator/xxxxxxx "c:\temp\"
$ ftso delete alias /system test1
%FTSO-W-ALIASNOTEX, alias test1 does not exist
$ ftso sho alias
(SYS)   t
e
s
t
1
                n
m
r
l
o
n
d
_
_
x
                a
d
m
i
n
i
s
t
r
a
t
o
r

(SYS)
$



Can you please advise .

Thanks

Royston 
UK CSC

Hello,

The 'set alias' problem is a well known problem which has been fixed for the next version of FTSO.
It's true that the problem only appears when the file ftso_alias.dat does not exist, but unfortunately, 
you can't avoid the problem by creating an empty file with the 'create' command.

We are working on a small utility program which will help you to create this file (this will be a workaround 
until the new version 1.4 of FTSO). This program will be soon available on the network (in the beginning of
the next week).

Thanks.

Christophe THIVEL
[email protected]

    Thanks Christophe for your quick response.
    
    Can you please reply here and/or mail me when the fix is available.
    
    Regards
    
    Royston

Hi,

As I told you, a small program called ftso_alias_file.exe is available on the node AEOENG::FTSO$PUBLIC, and will
help the customer to create alias files.
Two alias files are created as you run this program :
- one for the user in his home directory SYS$LOGIN
- another for the system (that means every user) in the ftso directory SYS$SYSDEVICE:(FTSO)
The files are created empty if they don't exist.
But if they do exist, the program will not erase all the existing aliases which could have been previously defined.
So be sure that if you have wrong alias files (like the one you showed me), you must suppress them before running
the program. 
And after that, everything should be OK...

Don't hesitate to contact me again if it doesn't work properly.
Thanks

Christophe THIVEL

    Christophe, I sent the image to the customer and I've just heard
    back and its work fine.
    
    Thanks again for your help
    
    Royston