=;The OpenVMS Frequently Asked Questions (FAQ)D

The OpenVMS Frequently Asked Questions (FAQ)



 r \ ^  
PreviousContentsIndex

x

10.5 How do I link against SYS$SYSTEM:SYS.STB on an Alpha system?



GLINK/SYSEXE is the OpenVMS Alpha equivalent of linking against SYS.STB.5This links against the base image: SYS$BASE_IMAGE.EXE

iAlso see Section 10.11, particularly for pointers to the details on ishareable images and shareable image creation, and see Section 10.22 ?for details of inner-mode floating point requirements, of data @alignment, requirements for use of /NOSYSLIB, and other related minner-mode programming details, and see Section 10.11 for image-related information.l

10.6 How do I do a SET DEFAULT from inside a program?



EThe problem is that SYS$SETDDIR only changes the default directory - DNOT the default disk. The default disk is determined by the logical HSYS$DISK. If you want to change the default disk within a program, then Fcall LIB$SET_LOGICAL to change the logical SYS$DISK. You will need to Fcall both LIB$SET_LOGICAL and SYS$SETDDIR to change both default disk and the default directory!|

10.7 How do I turn my Fortran COMMON into a shareable image on Alpha?



BYou need to add SYMBOL_VECTOR=(<common-name>=PSECT) to your Goptions file. On OpenVMS VAX all OVR/REL/GBL psects were automatically Dexported into the shareable image's Global Symbol Table. On OpenVMS FAlpha you have to tell the linker that you want this done by means of >the PSECT keyword in the SYMBOL_VECTOR options file statement.

GThis has several advantages over OpenVMS VAX. First, you don't have to Cworry about the address of the psect when you try to create a new, Dupwardly compatible version of the shareable image. Second, you can Econtrol which psects, if any, are made visible outside the shareable image.

FBy default, COMMON PSECTs in HP Fortran for OpenVMS Alpha (as well as Gmost other OpenVMS Alpha compilers) are NOSHR. On VAX, the default was FSHR which required you to change the attribute to NOSHR if you wanted Cyour COMMON to be in a shareable image but not write-shared by all ;processes on the system. If you do want write-sharing, use:

 

"
CDEC$ PSECT common-name=SHR 




Fin the Fortran source code (the CDEC$ must be begin in column 1) or a Alinker options file PSECT_ATTR statement to set the COMMON PSECT attribute to SHR.

/For further information, see the Linker manual.p

10.8 How do I convert between IEEE and VAX floating data?



GIn OpenVMS V6.1 and later, the routine CVT$CONVERT_FLOAT is documented Hin the LIB$ Run-Time Library Reference Manual, and can perform floating Gpoint conversions between any two of the following floating datatypes: EVAX (F,D,G,H), little-endian IEEE (single, double, quad), big-endian :IEEE (single, double, quad), CRAY and IBM System\370, etc.

DHP Fortran (all OpenVMS platforms) has a feature which will perform Eautomatic conversion of unformatted data during input or output. See Dthe HP Fortran documentation for information on "non-native data in -I/O" and the CONVERT= OPEN statement keyword.

GThere are floating-point conversion source code packages available for various platforms.

4For further floating-point related information, see:

q

10.9 How do I get the argument count in a Fortran routine?



FOn VAX, many programmers would use a MACRO routine which accessed the AP registerDof the caller to get the address of the argument list and hence the Dargument count. This was not guaranteed to work on VAX, but usually Fdid. However, it doesn't work at all on OpenVMS Alpha, as there is no BAP register. On Alpha systems, you must use a language's built-in Dfunction to retrieve the argument count, if any. In Fortran this is AIARGCOUNT, which is also available in DEC Fortran on OpenVMS VAX.

HNote that omitting arguments to Fortran routines is non-standard and is Gunsupported. It will work in many cases - read the DEC Fortran release !notes for additional information.u

10.10 How do I get a unique system ID for licensing purposes?



?Many software developers desire to use a unique hardware ID to E"lock" a given copy of their product to a specific system. =Most VAX and Alpha systems do not have a unique hardware-set D"system ID" that can be used for this purpose. HP OpenVMS Cproducts do not use hardware IDs in the licensing methods, as many @users consider a hardware-based licensing scheme to be negative .attribute when considering software purchases.

FHP OpenVMS uses a software-based system called the License Management GFacility (LMF). This provides for software keys (Product Authorization FKeys or PAKS) which support capacity and user-based license checking. DHP offers an LMF PAK Generator to DSPP (formerly CSA) members---see kSection 2.8.3 for general details on the DSPP offerings, and on the GDSPP-provided Freeware PAKGEN PAK that is available for those that are Einterested in details. (Sorry, no; you can't use the Freeware PAKGEN DPAK to generate any PAK you might want. Folks at HP also thought of that one, too.)

[For information on licensing, please see Section 12.4.

HHowever, if a hardware-based method is required, the most common method Eis based on an Ethernet adaptor hardware address. Sample source code &for implementing this is available at:



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference.u

10.11 What is an executable, shareable, system or UWSS image?



GExecutable code in OpenVMS typically resides in an image---an image is Ca file---the file extension is typically .EXE---that contains this Bcode. Common types of images include executable images, shareable 3images, system images, and protected (UWSS) images.

DExecutable images are programs that can be directly executed. These 5images can grant enhanced privileges, with an INSTALLJ of the image with /PRIVILEGE, or can grant enhanced access with the M specification of a subsystem identifier on the ACL associated with the image.

DShareable images contain code executed indirectly, these images are Freferenced from executable images and/or from other shareable images. EThese images can not grant enhanced privileges, even with the use of INSTALL with /PRIVILEGEL or a subsystem identifier. These shareable images can be dynamically : activated (a LINK that occurs at run-time) via the < LIB$FIND_IMAGE_SYMBOL run-time library (RTL) routine.H (See `protected images' for information on `privileged shareable  images'.)

?System images are intended to run directly on the VAX or Alpha Fhardware---these are normally used for the kernel code that comprises an operating system.

CProtected images---also refered to as User-Written System Services F(UWSS), or as privileged shareable images---are similiar in some ways Cto a standard shareable images, but these images include a `change Dmode' handler, and execute in an `inner' processor mode (privileged Bmode; executive or kernel), and code executing in inner modes has Fimplicit SETPRV privilege. Must be INSTALLed with /PROTECT. Note that Binner-mode code has restrictions around calling library routines, Haround calling various system services, and around calling code located 'in other protected or shareable images.

FLoadable images and device drivers are images that can be used to add Gcode into the OpenVMS kernel. Pseudo-device drivers are a particularly Fconvenient way to add executable code, with associated driver-defined Hdata structures, into the kernel. The pseudo-device driver includes the UCB and DDB data structures,@ and a calling interface with support for both privileged and ? unprivileged access to the driver code via sys$qio[w] calls.

FA cookbook approach to creating OpenVMS shareable images is available at the URL:



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference.e

10.12 How do I do a file copy from a program?



DThere are several options available for copying files from within a >program. Obvious choices include using lib$spawn(), system(), Hsys$sndjbc() or sys$creprc() to invoke a DCL COPY command. Other common Halternatives include using the callable convert routines and the BACKUP 3application programming interface (V7.1 and later).S

10.13 What is a descriptor?



FA descriptor is a data structure that describes a string or an array. DEach descriptor contains information that describes the type of the Ddata being referenced, the size of the data, and the address of the Gdata. It also includes a description of the storage used for the data, Atypically static or dynamic. Descriptors are passed by reference.

HThe following are examples of creating and using descriptors in C, with Athe use of the angle brackets normally expected by the C include 5statements deliberately altered in deference to HTML:

 

"
    #include {descrip.h}     #include {lib$routines.h}     #include {stsdef.h}     int RetStat;     char TxtBuf[TXTSIZ] &    struct dsc$descriptor StaticDsc = 1      { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL }; #    struct dsc$descriptor DynDsc = 1      { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL };     int DynDscLen = 255; 1    $DESCRIPTOR( ConstDsc, "This is a string" );  0    /* finish setting up a static descriptor */ *    StaticDsc.dsc$w_length      = TXTSIZ; 3    StaticDsc.dsc$a_pointer     = (void *) TxtBuf;  1    /* finish setting up a dynamic descriptor */ ;    RetStat = lib$sget1_dd( &DynDscLen, &DynDsc ); +    if ( !$VMS_STATUS_SUCCESS( RetStat ) )       return RetStat;  &    /* release the dynamic storage */ ,    RetStat = lib$sfree1_dd( &DynDsc ); )    if (!$VMS_STATUS_SUCCESS( RetStat ))       return RetStat; 




HStatic descriptors reference storage entirely under application program Bcontrol, and the contents of the descriptor data structure can be Cmodified as required (by the application). OpenVMS routines do not Bmodify the contents of a static descriptor, nor do they alter the Daddress or length values stored in the static descriptor. (The term F"static" refers to the descriptor data structure, and not necessarily -to the storage referenced by the descriptor.)

HDynamic descriptors reference storage under the control of the run-time Hlibrary, and the contents of a dynamic descriptor data structure---once Einitialized---can only be modified under control of run-time library Froutines. The dynamic storage referenced by the dynamic descriptor is Callocated and maintained by the run-time library routines. Various >OpenVMS routines do alter the contents of the descriptor data Dstructure, changing the value for the amount and the address of the Fstorage associated with the dynamic descriptor, as required. Routines Fcan obviously access and alter the contents of the storage referenced by the descriptor.

AOpenVMS languages that include support for strings or arrays are Gexpected to use descriptors for the particular structure. Most OpenVMS ?languages, such as Fortran and BASIC, use descriptors entirely Ftransparently. Some, like DEC C, require the programmer to explicitly #create and maintain the descriptor.

CFor further information on string descriptors, see the OpenVMS HProgramming Concepts manual, part of the OpenVMS documentation set.

DFortran defaults to passing integers by reference and characters by Ddescriptor. The following sites discuss mixing Fortran and C source code in the same application:

o

10.14 How do I create a process under another username?



HMany server processes can operate within the context of the target user Gusing privileges, using calls such as sys$chkpro and (more commonly in Fthis context) sys$check_access as needed to determine if access would Fbe permitted for the specified user within the current security model.

9With OpenVMS V6.2 and later, the persona system services C(SYS$PERSONA_*) can be used to assume the persona of the specified Euser---these allow the server to operate as the specified user, in a Dcontrolled fashion. The persona services can be used as a "wrapper" Haround a sys$creprc process creation call, as well---this will create a 4seperate process entirely under the assumed persona.

FInformation on the persona system services is included in the OpenVMS CV6.2 new features documentation, and in the OpenVMS V7.1 and later Csystem services documentation. These system services exist and are -supported in OpenVMS V6.2 and later releases.

ATypical mechanisms for creating a process under another username include:



DThere are likely a few other mechanisms around... There are various Ftools available from DECUS and other sources that allow various forms 9of user impersonation, as well. These tools will require Fversion-dependent kernel code and enhanced privileges for some of (or all of) their operations.z

10.15 Why do lib$spawn, lib$set_symbol fail in detached processes?



GThe processing within run-time library (RTL) calls such as lib$attach, Clib$disable_ctrl, lib$do_command, lib$enable_ctrl, lib$get_symbol, Dlib$run_program, lib$set_symbol, lib$set_logical, and lib$spawn, is =dependent on and requires the presence of a command language Einterpreter (CLI), such as DCL. Without a CLI present in the current Hprocess, these calls will fail with a "NOCLI, no CLI present to perform function" error.

7Detached processes typically do not have a CLI present.

HIn place of lib$spawn, sys$creprc can often be used. The context of the Gparent process (symbols and logical names) will not be propogated into Dthe subprocess when sys$creprc is used, though when there is no CLI :present in the process this (lack of) propogation is moot.

FTo create a detached process with a CLI, you must specify LOGINOUT as Fthe target image as discussed elsewhere in the FAQ, or only use these Acalls (and any other calls requiring a CLI) from images that are >running in an "interactive", "batch", or "other" mode process.

BAlso note that the lib$spawn and the C system call will fail in a GCAPTIVE login environment. The lib$spawn call can be gotten to work in <this environment with the specification of the TRUSTED flag.

10.16 Where can I obtain Bliss, and the libraries and supporting files?



DThe Bliss language compilers and documentation are available on the OpenVMS Freeware distributions.

ABliss language source code that contains the following statement:

 

"
%  LIBRARY 'SYS$LIBRARY:STARLET.L32'; 




?or similar requires the presence of the Bliss libraries. These Clibraries are created on the target system using the Bliss require 8files, and are built using the following Bliss commands:

6STARLET.L32 contains the public interfaces to OpenVMS:

 

"
6    $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 -          SYS$LIBRARY:STARLET.REQ 




CLIB.L32 contains both the public and private interfaces to OpenVMS:

 

"
2    $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 - 4        SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQ 




2The equivilent files for Bliss64 are created with:

 

"
5    $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]LIB.L64 - 4        SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64 9    $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L64 -          SYS$LIBRARY:STARLET.R64 




ESome Bliss code may also require the OpenVMS VAX architecture flags. BThe following is the equivilent of the Alpha ARCH_DEFS.REQ module:

 

"
! 8! This is the OpenVMS VAX version of ARCH_DEFS.REQ, and ;! contains the architectural definitions for conditionally :! compiling OpenVMS Bliss sources for use on VAX systems. ;! (If you should encounter compilation errors here, please 5! seriously consider upgrading your Bliss compiler.) ! MACRO VAXPAGE = 1%; MACRO BIGPAGE = 0%; ! <MACRO VAX =                     ! = 1 if compiled BLISS/VAX @        %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAX  PMACRO EVAX =                    ! = 1 if compiled BLISS/E* (Obsolete, old name) M        (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  KMACRO ALPHA =                   ! = 1 if compiled BLISS/E* (New arch name) M        (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  KMACRO IA64 =                    ! = 1 if compiled BLISS/I* (New arch name) P        (%BLISS(BLISS32I) OR %BLISS(BLISS64I))%; ! = 0 if compiled /VAX or /Ann  MACRO ADDRESSBITS = D        %BPADDR%;               ! = 32 or 64 based on compiler used  




GSome Bliss code may require the definition files for the OpenVMS older =LIBRTL routine lib$tparse, or the newer lib$table_parse call:

 

"
5    $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]TPAMAC.L32 -         SYS$LIBRARY:TPAMAC.REQ 


f

10.17 How can I open a file for shared access?



EWhen creating a file, it is often useful to allow other applications Fand utilities---such as TYPE---to share read access to the file. This @permits you to examine the contents of a log file, for instance.

DA C source example that demonstrates how to do this is available in 0topic (2867) in the OpenVMS Ask The Wizard area:



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference.

HDepending on the environment, you may need to use C calls such as fsync ?and fflush, and---in specific cases---the setvbuf(_IONBF) call.

FFor related materials around commands that can potentially be used to Goverride file locking---to view the file contents as currently written Dto disk---see Section 9.12.t

10.18 How can I have common sources for messages, constants?



EUse the GNM tools on the OpenVMS Freeware to have common sources for EMSG (message) files and SDML (Document) documentation files. Use the FDOCUMENT command to convert the SDML documentation into the necessary Hformats (Text, Postscript, HTML, etc). Use the MESSAGE/SDL tool (latent Fin OpenVMS) to create an SDL file based on the messages. Then use the ESDL tool (available on the OpenVMS Freeware) to convert the SDL file Finto language-specific definitions. (There is also a converter around Bto convert SDL into SDML, if you want to get pictures of the data #structures for your documentation.)




 r Y \ ^  
PreviousNextContentsIndex