Can Someone explain this?

[bill lechner]

I have entered a series of commands below with the release
# for reference. The move command fails because: The file
name or extension is too long.

G: is a network root level administrative share. c$

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>ver

Microsoft Windows 2000 [Version 5.00.2195]

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>move Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
The filename or extension is too long.

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>copy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite Yload_b_zzzzzzzz_name_and_addr.sql?
(Yes/No/All): Y
1 file(s) copied.



G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>Xcopy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_B\Yload_b_zzzzzzzz_name_and_addr.sql (Yes/No/All)? Y
G:Xload_b_zzzzzzzz_name_and_addr.sql
1 File(s) copied

This does not make sense to me.

WDLIII.
..

 

[Mark V]

bill lechner wrote in

I have entered a series of commands below with the release
# for reference. The move command fails because: The file
name or extension is too long.

G: is a network root level administrative share. c$

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>ver

Microsoft Windows 2000 [Version 5.00.2195]

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>move Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
The filename or extension is too long.

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>copy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite Yload_b_zzzzzzzz_name_and_addr.sql?
(Yes/No/All): Y
1 file(s) copied.



G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>Xcopy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_B\Yload_b_zzzzzzzz_name_and_addr.sql (Yes/No/All)? Y
G:Xload_b_zzzzzzzz_name_and_addr.sql
1 File(s) copied

This does not make sense to me.

No I can't explain it. It does seem clear that there is some
internal limit in MOVE that chokes on the command-line length.
Likely that the 2 fully qualified paths exceed something internally.

Aside from the curiousity/bug factor you clearly have alternatives in
COPY, XCOPY, DEL and REN. And SUBST'ing the path to a letter does
not choke MOVE either.

All on W2K SP3. Anyone with XP to test it?

 

[GeoffOs]

Even with long filename support the limit for filenames is
still 255 characters. You seem to have about 387. Don't
forget that the 255 characters includes the file path

-----Original Message-----
bill lechner wrote in news:243c01c33f07$986f5560 [email protected]:

I have entered a series of commands below with the release
# for reference. The move command fails because: The file
name or extension is too long.

G: is a network root level administrative share. c$

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>ver

Microsoft Windows 2000 [Version 5.00.2195]

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>move Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
The filename or extension is too long.

G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>copy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite Yload_b_zzzzzzzz_name_and_addr.sql?
(Yes/No/All): Y
1 file(s) copied.



G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_s>Xcopy Xload_b_zzzzzzzz_name_and_addr.sql
Yload_b_zzzzzzzz_name_and_addr.sql
Overwrite G:\staging\RELEASE_PROD_20030521_P0_001
\xxxxxxxxxx\yyyy\home\zzzzzz\bin\LOAD\LOAD_xxxxONE\RELOAD_x
xxxxxx_B\Yload_b_zzzzzzzz_name_and_addr.sql (Yes/No/All)? Y
G:Xload_b_zzzzzzzz_name_and_addr.sql
1 File(s) copied

This does not make sense to me.

No I can't explain it. It does seem clear that there is some
internal limit in MOVE that chokes on the command-line length.
Likely that the 2 fully qualified paths exceed something internally.

Aside from the curiousity/bug factor you clearly have alternatives in
COPY, XCOPY, DEL and REN. And SUBST'ing the path to a letter does
not choke MOVE either.

All on W2K SP3. Anyone with XP to test it?


.