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

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

Parsing routine

The Question is:

Are there any (RTL or public domain) routines for parsing
standard DCL file-selection qualifiers? I would like to
make a program DCL-like and accept things like


Of course I could code this up myself, but it seems like a major
wheel-reinventing exercise. I'm hoping there might be
something a bit better than LIB$FIND_FILE, since obviously
you must have written this for DIRECTORY, TYPE, SEARCH,...

The Answer is:

    There is no CLI$ support for this. What they want is the "LIB$"
    routine (I forget its name) used by DELETE, RENAME, etc, to do the
    "common file qualifier parsing".  This routine is NOT part of the RTL
    and is available only in SYSBLDLIB.OLB during a VMS build.  Too bad -
    it would be generally useful.

    We should really provide that functionality, either as a full fledged
    lib$ version, or at least in source form 'as is'.

    It would be better still if we could fix it first such that it
    deals better with 'locked files' that would not match the selection.