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

C Language: nfbdef from DECC

The Question is:

I am working on the port of a software subsystem from a microVAX
running VMS v5.0 to an Alpha running v6.2.  The S/W talks to other
subsystems on VAX 4000's (v5.0) over DECnet using mailboxes.

The first problem I encountered is that the nfbdef.h include file has
appearantly been obsoleted for v6.2 and information from this header
is used in assigning the network name during initialization.  After
creating the mailbox and assigning the network channel, the network
name assign was previously accomplished using a SYS$QIO with the
IO$_ACPCONTROL function argument and a pointer to an NFB descriptor
defined as follows:

    char func;
    int  terminator;
} nfb = {NFB$C_DECLNAME, 0};

struct dsc$descriptor nfb_desc = {5,0,DSC$K_CLASS_P,(char *)&nfb};

I tried locally #defining the NFB$C_DECLNAME symbol to the value from
v5.0 (0X15) to no avail.  The SYS$QIO call returns an iosb[0] which is

Is there a new and better way to assign a network name for a DECnet
mailbox in version 6.2?

Help Mr. Wizard,

The Answer is:

   nfbdef.h is not obsolete, and is currently used with DEC C
   both OpenVMS VAX and OpenVMS Alpha.  (I've just checked one of
   the local OpenVMS Alpha V6.2 systems, and nfbdef.h _is_ present.)

$! to translate the message, use the debugger EXAMINE/CONDITION, or:
$ exit 36
%SYSTEM-F-NOPRIV, insufficient privilege or object protection violation
$! or another way:
$ msg = f$message(36)
$ sho sym msg
  MSG = "%SYSTEM-F-NOPRIV, insufficient privilege or object protection violation"