[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

5381.0. "4.1 eco4 no name_conversion" by UTOPIE::FISCHER_J () Wed Mar 26 1997 09:38

Hi,

I can't uses on a AXP VMS 7.1 and UCX 4.1 ECO 4 
the 'ucx add export /option=name_conversion'

Any help will be highly appreciated.

Thanks,
Johann

-----------------------------------------------------------------------
Output from my test:

AXPBWO>ucx add export "/dka200/fischer_j" /host=* /option=name_conversion
%UCX-I-EXPORTADD, Export information added to database
-UCX-W-DUPHIEXPO, Filesystem already exported at higher level

AXPBWO>ucx sho export

File System                             Host name

/dka200                                 *
/dka200/fischer_j                       *  <-----------no Options:information
/dka200/wolfgang/koffer                 KOFFER.AUI.DEC.COM, koffer.aui.dec.com


When I copy on the client a file (name=�hans.txt) into the mounted
directory, the filename is '224' and not '�hans.txt'.
T.RTitleUserPersonal
Name		DateLines
5381.1LASSIE::CORENZWITstuck in postcrypt queueWed Mar 26 1997 10:1419
    There are three different issues here:
    
    1.  There is an important bug fix affecting name conversion in patch
    	image C of UCX$CHS_SHR.EXE.  I believe this is in ECO 5.  You
    	haven't seen the problem yet, but its best to have this fix if you
    	are using name conversion.
    
    2.  There is a bug in the UCX control program that prevents seeing that
        name conversion is enabled unless some other export option is also
        enabled.  See #4839 in this Notes conference or QAR 350.  This is
    	fixed in V4.2.
        
    3.  Name conversion support for mixed case and characters that are
    	invalid for VMS file names, but it does not at present include
    	8-bit support.  There is an enhancement request for this.  See QAR
    	483.  For now, it is still necessary to use a container file system
    	if you need 8-bit characters in file names.
    
    Julie
5381.2 < re .1 >UTOPIE::FISCHER_JWed Apr 02 1997 02:2231
Hi Julie, thanks for your reply.


>1.  There is an important bug fix affecting name conversion in patch
>    image C of UCX$CHS_SHR.EXE.  I believe this is in ECO 5.  You
>    haven't seen the problem yet, but its best to have this fix if you
>    are using name conversion.

I can't find in UCX the UCX$CHS_SHR.EXE, I think you mean the UCX$CFS_SHR.EXE;
I have used this image in my test.
(Image copied from LASSIE::UCX$INTERNAL:UCX$CFS_SHR.EXE_ECO_C_41_AXP70;1) 

>3.  Name conversion support for mixed case and characters that are
>    invalid for VMS file names, but it does not at present include
>    8-bit support.  There is an enhancement request for this.  See QAR
>    483.  For now, it is still necessary to use a container file system
>    if you need 8-bit characters in file names.

A big customer of us has read the release notes of the UCX 4.1 telling about
the NFS File-Naming Enhancement and has updated his systems to version 4.1,
because the notes says that he can use this feature without any container
file system. Because of fact that the customer has read the release notes,
it is difficult to tell him that this problem will be solved in a later
version (QAR).

Is there really no other solution for this problem ?
Would there be any advance or would it accelerate to solve the problem
if I let it escalate (IPMT) ?

Regards,
Johann
5381.3LASSIE::CORENZWITstuck in postcrypt queueWed Apr 02 1997 11:2211
>I can't find in UCX the UCX$CHS_SHR.EXE, I think you mean the UCX$CFS_SHR.EXE;
    
    Yes.  Sorry for the typo.
    
>Would there be any advance or would it accelerate to solve the problem
>if I let it escalate (IPMT) ?
    
    An additional formal customer escalation might affect the priority of
    the problem.
    
    Julie