[an error occurred while processing this directive]

HP OpenVMS Systems

Ask the Wizard
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard
» OpenVMS FAQ

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

File name with foreign characters

The Question is:

I observed the following discrepancy:

When doing a

$ CREATE {QUE.DAT
%CREATE-E-OPENOUT, error opening ?QUE.DAT as output
-RMS-F-SYN, file specification syntax error

    but with a

$ CREATE máqana.dat
%CREATE-E-OPENOUT, error opening SYS$SYSROOT:[SYSMGR]MÁQANA.DAT; as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILENAME, bad file name syntax

Apparently, the first gets stopped by RMS and the second by the XQP.
Checking the literature, both the RMS internals book and the VMS system service
reference for such routines as SYS$FILESCAN
clearly consider accented LETTERS in DECMCS to be legal in filenames.
RMS seems to already conform.

The corresponding fix to F11BXQP seems trivial,
(I patched mine, on both VAX and Alpha and nothing broke)
but has never been made. Why not?


The Answer is:

Unfortunately the fix isn't quite as trivial as it seems. You're right, having
F11BXQP accept DECMCS characters in file name strings is a fairly trivial patch.
However, there are a couple of irregularities in the MCS that make a complete
fix more complex. The most obvious of these is that the German sharp S (ß) is a
lower case character only with no upper case form. Yet, of course, F11BXQP
blindly upcases all file names.

Deciding what collating sequense, if any, should be used to sort the names in a
directory is another potential complicating factor.

The set of annoying complications has so far created sufficient resistance to
prevent the file name character set from being expanded. However, we have
recently applied significant engineering effort in this area, and the character
set supported in file names will be substantially expanded in a version of
OpenVMS to release in the near future. Directory entries containing DECMC
characters that you have created with your patched file system should be
compatible with the new release.