From: RICK@QUCDNEE.BITNET (Rick Pim)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: problem saving files on a file service using amipro
Date: 6 Nov 92 02:43:00 GMT
Content-transfer-encoding: 7BIT

a pathworks user here has been having some problems with amipro and
maipulating amipro files on a file service. i've never used amipro
(don't even know what it purports to do :-) and this failure mode is
new to me as far as pathworks is concerned.
 
i asked him to write up a summary of his problem; here it is. does
this ring any bells with anyone?
 
rp
 
 
Here is the scenario that I observe with AMIPRO 2.0, when trying to
save a new .SAM file to a directory on the VAX that has been
connected via a USE command: say it is n:\myfiles
 
Program:        Menu/command    Action:                 Message:
 
AMIPRO          file/new        Open a default .SAM file
AMIPRO                          write some date to file
AMIPRO          file/save       asks for directory and name
USER                            set name e.g. "TESTFILE.SAM"
AMIPRO          OK              Error:  "CANNOT OVERWRITE N:\MYFILES
                                                        TESTFILE.SAM"
NORTON or WINDOWS file/attributes       check file
(....... there is now an empty file with the name "TESTFILE.SAM")
 
NORTON          file/attributes                         bytes=0
                                                        attrib=r--a
VMS LOGIN       dire/size       check file status       bytes=0
                                                        Prot=(r,r,r,)
 
 
(.....At this point, if I change the attributes with NORTON desktop or
WINDOWS to remove the write only attribute, I am still unable to save
my file. The VMS protection is not changed from (r,r,r,). If I change
the protection on TESTFILE.SAM to (r,rwd,r,) from the VMS login, then
ask AMIPRO to save the open file (which is still called "UNTITLED",
it now works (sort of):)
 
AMIPRO          file/save       name the file TESTFILE.SAM
AMIPRO                                                  "TESTFILE.SAM
                                                        Already exists.
                                                        Do you want to
                                                        overwrite it?"
USER            YES             File is written, name changed to
                                TEMPFILE.SAM
 
 
(From now on, I can handle the file normally)
 
I have no difficulties with other applications, such as Excel 4.0, or
the various text editors, creating a new file on a vax directory.
 
The AMIPRO situation is different, in that AMIPRO apparently creates
a directory entry for the new file with (r,r,r,) protection, before
it tries to write the file contents.
 
 
 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rick Pim                                            bitnet:rick@qucdnee
Department of Electrical Engineering         rick@qucdnee.ee.queensu.ca
Queen's University, Kingston                     (bitnet:rick@qucdnast)
(613) 545-6772                               (rick@bill.phy.queensu.ca)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"I'll have you all executed!"
"I think not."