FTP Issues On Tandem/Nonstop Guardian OS

[Leon Arens]

OSS personality works but has limitations

We have the OSS personality installed on our Tandem and I am able to download files from the Tandem Guardian space.

When I compare a Tandem directory like $SYSTEM.LEON.* to $DATA.LEON.* on my \OMHA node, I enter
sftp://[email protected]//G/system/leon in the left path and
sftp://[email protected]//G/data/leon in the right path

Via the OSS personality I can get to Guardian files, but there are limitations.

Guardian files have different structures, like Entry sequenced/relative/keyed sequence/unstructured/SQLmp/SQLmx. I primarily use Beyond compare to compare TEXT files and unstructured files so it works for me most of the time.

[Aaron]

We would like to add support for Nonstop, and this is still an open Wishlist entry. Our Customer Wishlist is not currently scheduled development, but a place our developers go for ideas for new features and enhancements. Unfortunately, we do not have a timeframe for when this support could be added.

[nvallinger]

Thanks for the insight, Terry. I'll add your notes to a Tandem/Nonstop wishlist entry we're compiling. We've got a lot of other projects on our plate right now, so the workaround for now would require OSS to be installed/configured.

Any updates? Ultracompare able to compare NSK and Windows Folders. I did not like how they present it. Can you guys let me know will this done or not? I doubt it is hard. Please revert to me.

[Aaron]

Thanks for the insight, Terry. I'll add your notes to a Tandem/Nonstop wishlist entry we're compiling. We've got a lot of other projects on our plate right now, so the workaround for now would require OSS to be installed/configured.

[TerrydlM]

This thread is getting a little confused with the quote workaround.

Tandem Hosts have two possible 'personalities'- Guardian & OSS.

Guardian is the 'native' original operating system personality.

The OSS personality may not exist on the machine if it has not been configured.

The OSS personality is a Unix-type environment and file paths have Unix style directory paths.

The original issue logged seems to be caused because the CWD command sent from BC has an extra leading character '/' being sent to the Guardian personality which expects a path name of \node.$volume.subvol as is being sent back in the PWD content.

Tandem node names start with a '\' character.

ASCII files transferred to Tandem should have a filecode of '101'.

On Binary transfers it would be nice t be able to set a value for the filecode to be created.

[Aaron]

Hello,

It looks like the custom command "OSS" is being sent, but we are receiving back a failed message from the server. You probably need to configure the server in a way to accept this command?

[lutmi02]

I tried this solution, but had the same negative results;

12/8/2011 3:22:39 PM Sent> OSS
12/8/2011 3:22:39 PM Recv> 550 Root Fileset is not mounted
12/8/2011 3:22:39 PM Sent> SYST
12/8/2011 3:22:39 PM Recv> 500 'SYST': command not understood.
12/8/2011 3:22:39 PM Sent> PWD
12/8/2011 3:22:39 PM Recv> 257 "\DALLAS.$C35.MICHAEL" is current default.
12/8/2011 3:22:39 PM Sent> REST 1
12/8/2011 3:22:39 PM Recv> 502 REST command not implemented.
12/8/2011 3:22:39 PM Sent> REST 0
12/8/2011 3:22:39 PM Recv> 502 REST command not implemented.
12/8/2011 3:22:39 PM Sent> CWD \DALLAS.$C35.MICHAEL
12/8/2011 3:22:40 PM Recv> 250 CWD command successful.
12/8/2011 3:22:40 PM Sent> PWD
12/8/2011 3:22:40 PM Recv> 257 "\DALLAS.$C35.MICHAEL" is current default.
12/8/2011 3:22:40 PM Sent> CWD /\DALLAS.$C35.MICHAEL
12/8/2011 3:22:40 PM Recv> 550 XCWD valid $volume.subvolume format required.
12/8/2011 3:22:40 PM Unable to load ftp://[email protected]//\DALLAS.$C35.MICHAEL: XCWD valid $volume.subvolume format required.

[montyplease]

In case anyone comes across this in the future, here's how to get BC3 FTP working on the Nonstop Guardian O/S

1) In the FTP Profile General tab, enter OSS in the custom login commands box.
2) In the Listings Tab only check the MLSD command box and nothing else.

This should allow BC3 to work with Nonstop file structure and get the file and subvol compares working ok.

However, still not able to get BC3 to create files on the Nonstop with the correct filecode. Everything gets created as filecode 180, unfortunately.

[montyplease]

Hi, the debug log is what I attached below. I ran it again and it is no different than what I already attached.

If I had to guess, I think it's simply a matter of just omitting the "\" when dealing with Nonstop servers. That's how it works from the command line, and it looks like that's also how Filezilla deals with it.

Cheers.

[Aaron]

Hello,

We have FTP debugging logging which can be enabled in the Tweaks dialog (Ctrl+Shift+T), Folder Views tab, "Include debug messages in log."

Would you be able to post a followup with that enabled here or email us at [email protected]. If you email us, please also include a link back to this forum thread for our reference.

[montyplease]

BC3 FTP has issues with Tandem/Nonstop servers. Anyone have a workaround? Please see logs below. Thanks.


BC3 LOG11/11/2011 4:20:02 p.m. Sent> SYST
11/11/2011 4:20:02 p.m. Recv> 215 Nonstop S-series Server : G06.32.
11/11/2011 4:20:02 p.m. Sent> PWD
11/11/2011 4:20:02 p.m. Recv> 257 "\NODE.$VOL.SUBVOL" is current default.
11/11/2011 4:20:02 p.m. Sent> REST 1
11/11/2011 4:20:02 p.m. Recv> 502 REST command not implemented.
11/11/2011 4:20:02 p.m. Sent> REST 0
11/11/2011 4:20:02 p.m. Recv> 502 REST command not implemented.
11/11/2011 4:20:02 p.m. Sent> CWD \NODE.$VOL.SUBVOL
11/11/2011 4:20:02 p.m. Recv> 250 CWD command successful.
11/11/2011 4:20:02 p.m. Sent> PWD
11/11/2011 4:20:02 p.m. Recv> 257 "\NODE.$VOL.SUBVOL" is current default.
11/11/2011 4:20:02 p.m. Sent> CWD /\NODE.$VOL.SUBVOL
11/11/2011 4:20:02 p.m. Recv> 550 XCWD valid $volume.subvolume format required.

FILEZILLA LOG
Command: CWD \NODE.$VOL.SUBVOL
Response: 250 CWD command successful.
Command: PWD
Response: 257 "\NODE.$VOL.SUBVOL" is current default.
Command: TYPE A
Response: 200 Type set to A.
Command: PASV
Response: 227 Entering Passive Mode (1,1,1,1,1)
Command: RETR FILE
Response: 150 Opening data connection for FILE (1.1.1.1,54898d)
Response: 226 Transfer complete.