We have a customer that uses Novell Clustered servers, when trying run
a conversion on the data from an older version of our software the
application returns a Status 11 filename is invalid. This error
occurs on some not all of the files to be converted.

The servers are running Netware 6.0, the PSQL is v 8.7 the client OS
is Win XP. The server does have long file name support (ironically the
files that are failing are not long file names) the auto exec.ncf has
been edited to have MGRSTART and BSTART loading at or near the end of
the boot process.

The sequence is this:
sys:etc\initsys.ncf
MOUNT ALL
then at the very end of the ncf file

BSTART.NCF
MGRSTART.NCF

I am by no means a Novell person but shouldn't there be a LOAD NSS
command? I thought I read that it was native and assumed that the LOAD
NSS command would not need to be loaded but on second thought I
wondered if it should.

Secondly shouldn't the MGRSTART.ncf be loading before the BSTART.ncf?

The novell client is 4.90

any ideas?

The P.SQL manual (for 8.6) enter for error 11 states that on a Novell
server LOAD NSS should be executed before the LOAD ALL.

This is to make sure that when Btrieve/P.SQL loads it see that the
volumes have long file name support.

What are the full old and new filenames - including the paths?

Lisa@IMC wrote:

--
Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

A few things:

1) First, your call to INITSYS starts up the Btrieve engine. Since the
volumes are not mounted yet, there will be NO long name support on any
volumes other than SYS. MOve the MOUNT ALL command to BEFORE the
INITSYS command. This may take care of it if any [part of the path is
over 8 characters (i.e. a long name).

2) Second, verify that the application is null-terminating filenames.
If you are unable to tell, try verifying the setting on the client
workstations for "Allow Embedded Spaces" and be sure that this is
turned OFF.

3) If you turn off embedded spaces, of course, you'll want to make sure
that your application doesn't use a path with embedded spaces, like
"C:\My Documents". Again, eliminating any "long names" in the path
will usually clean this up, too.

4) Since MGRSTART actually calls BSTART, the BSTART is redundant.
However, I have found it most stable to call BSTART to load the Btrieve
engine shortly after running INITSYS, and then use MGRSTART at the VERY
end of the AUTOEXEC.NCF script to load the SQL engine after everything
else is done.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***


Lisa@IMC wrote:

Thank you for the information! Thanks Guy for emailing me also!

I have passed the suggestions along to my customer. I do not maintain
their servers so I can only suggest that they move things around in
the NCF file.

The funny thing is that the data on their test server converted fine.
I briefly (very very briefly) looked at the autoexec.ncf for the test
server and it appeared to load in the same order. I will keep you
posted on the outcome.

Guy the funny think about the file names is that they didn't change at
all. The path is vol1\imc\rms\rmsdata\offense.dat. It is the same in
the old and new versions.

Cheers!

Lisa