Guardian and FTP errors

[wedelenbos]

Hi, anybody the same problem as i do:
ftp open of a guardian-file is no problem (except for the boring xcwd error: everytime a / is thrown in before the nodename).
ftp save always gives an error (STOR failed).
when you do a ftp save as than you can see that there is always an "/" in front of the filename. CHanging this "/" manually in a "." makes the ftp save work!
the filename convention on guardian is \node.$volume.subvolume.file

please advice.
regards,
willem

[ChrisB]

Willem,

Momenteel draait ik ultraedit 12.2.
Server Type Tandem Guardian
Full path leading Character \
Path/Node seperator.

Als het goed is moet het zo lukken.

En de groeten van Jos H!

[peterj]

Hee Chris,

we gebruiken hier 12.10+1
de settings die jij hebt gebruik ik ook maar ultraedit negeert de eerste en plaatst vooraan een punt en tussen subvolume en filenaam een punt.

de workaround is via file, FTP, open from FTP te werken. Dat werkt het wel. Doe mij maar Codewright.....

groeten aan Jos H en de rest daar.

Peter de J.

[arathorn2005]

Just to point it out,

you're not the only one wanting to use UE with a Tandem. It would be great if the UE team improves Tandem support just a little bit!

Cheers,

Björn

[muckypaws]

The main issue is that Tandem edit files have additional information stored and therefore is not a plain ASCII file, file code 101 contains line numbers and edit information.

There's plenty of documentation that describes file code 101 formats, however when FTP back to NSK/Tandem this will result in a filecode 180 which requires the use of CTOE parsing.

If on the other hand, your going into OSS, (which is a Guardian file) you still encounter issues when FTP the edit file back.

The question is, how many users are on NSK platforms use UE?

I tend to use EDIT or the more girlie TEDIT in rare circumstances, doing the main edit in UE and FTP the files back down or cut and paste from screen back to my EDIT session.

Regards
Jason