=;The OpenVMS Frequently Asked Questions (FAQ)D

The OpenVMS Frequently Asked Questions (FAQ)



 r \ ^  
PreviousContentsIndex

x

11.11 %DECW-W-NODEVICE, No graphics device found on this system?



To resolve the following error:

 

"
:%DECW-W-NODEVICE, No graphics device found on this system ?-DECW-I-NODECW, DECwindows graphics drivers will not be loaded 






:Also see Section 11.5.f

11.12 How can I reset the warning bell volume?



@With DECwindows CDE drivers and ECOs starting with ECOs for the EDECwindows keyboard driver SYS$IKBDRIVER.EXE in OpenVMS Alpha V7.1-2 Gand V7.2-1 and with the SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1 Eand later, the DECwindows CDE controls will now correctly manage the #setting of the warning bell volume.

EUnfortunately, the equivalent controls in the older DECwindows Motif Ginterface are not compatible and can no longer manage the warning bell volume.

GIf you need to manage the volume with DECwindows Motif, consider using the following approach:

 

"
 $ @decw$utils:decw$define_utils $ xset b 1 100 100 




?The numerics are the volume, pitch, and duration, respectively.

GWhy? When OpenVMS first started supporting the PC-style keyboards, the GX Windows Server and the keyboard driver interface did not support the Epitch and duration, and neither did DECwindows Motif. The DECwindows Ckeyboard driver was accordingly changed to use the volume from the Hkeyclick setting (keyclick is not available in a PC-style keyboard) and :the bell volume setting to control the pitch and duration.

GDECwindows CDE does provide sliders for setting pitch and duration, so Fthe keyboard driver and X Windows Server were modified to provide all Bof the information, and now the DECwindows CDE sliders work. This Echange is unfortunately incompatible with the old scheme used on the Hpre-CDE desktops, and the volume controls are now incompatible with the 0current keyboard drivers. Hence the use of xset.j

11.13 How can I alter the DECwindows CDE backdrop?



CTo select a separate backdrop to be displayed on each screen using DECwindows CDE:

n

11.14 How can I enable the DECwindows TCP/IP Transport



FTo configure the TCP/IP transport for DECwindows, first ensure that a DTCP/IP package is installed and configured. Then set the DCL symbol GDECW$SERVER_TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to Hthe appropriate local value, based on the comments in that file. If you Edo not have a copy of SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM, the @use the following COPY command to create this file based on the provided template file:

 

"
8$ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE - 4$_ SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COM 


u

11.15 Can I use DECwindows 1.2-* on OpenVMS V7.3-2 or later?



The short answer is no.

GOpenVMS Alpha V7.3-2 only supports DECwindows Motif V1.3 and later. If Byou require DECwindows V1.2-6 or earlier, then you are limited to 8operations on OpenVMS Alpha V7.3-1 and earlier releases.

GThe central technical reason involves depdendencies among the parts of Ethe X11 subsystem that are delivered with the base OpenVMS operating Hsystem including the X Windows display server and the transport images, Fand the parts of the DECwindows product that are delivered within the DDECwindows installation kits including the client libraries and the DECwindows applications.

DDECwindows V1.3 and later made substantial changes to the transport Glayer, and these required corresponding changes to both the associated Eclient and server code. OpenVMS Alpha V7.3-2 includes the server and Htransport with the V1.3 modifications. These changes were in support of Gthe upgrade of Xlib from X11R5 to X11R6.6, and transport-level changes 9associated with support of the Kerberos and LBX features.

FIf you attempt to load DECwindows V1.2-6 images onto an OpenVMS Alpha HV7.3-2 or later system, the DECwindows libraries will not function with ?with system images and will particularly not function with the transport layer.b

11.16 How to add Fonts into DECwindows?



EThe following assumes DECwindows V1.3-1 and OpenVMS Alpha V7.3-2 and Glater unless stated otherwise, and can permit fonts of various formats ,to be added into the DECwindows environment.

EThe recommended location for user font files is to place them in the Cdirectories which are reserved for this purpose, typically located .below the SYS$COMMON:[SYSFONT.DECW] directory.

 

"
&SYS$COMMON:[SYSFONT.DECW.USER_100DPI] %SYS$COMMON:[SYSFONT.DECW.USER_75DPI] 




GThe above are recommended for PCF files of 100 Dots Per Inch (DPI) and #of 75 DPI resolution, respectively.

 

"
&SYS$COMMON:[SYSFONT.DECW.USER_COMMON] 




>The above is recommended for other PCF files, such as terminalA (character cell) fonts, and fonts used by specific applications.

 

"
(SYS$COMMON:[SYSFONT.DECW.USER_CURSOR16] (SYS$COMMON:[SYSFONT.DECW.USER_CURSOR32] 




&The above are recommended for cursors.

 

"
&SYS$COMMON:[SYSFONT.DECW.USER_SPEEDO] 




$SPEEDO is recommended for SPD files.

 

"
(SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE] 




6USER_TRUETYPE is recommended for TrueType (TTF) fonts.@Fonts placed in this directory should be in the "Windows / Linux" format.

FThe directory will contain the font files themselves, and a data file >that describes each font in the directory. This file is named DDECW$FONT_DIRECTORY.DAT or DECW$FONT_DIRECTORY_extension.DAT, where G"extension" is replaced by the type of font (100DPI, SPEEDO, TRUETYPE, TYPE1, etc.)

EMake sure that the file protection on the font files is set to allow world access to the fonts.

For example: to add TrueType-fonts to DECwindows, place the font files in 'SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]

)A directory listing might look like this:

 

"
2Directory SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]   QARKOI8N.TTF;1                            46KB/48KB        5-MAR-1995 04:00:00.00 Qbackstage.ttf;1                          55KB/56KB       19-JUL-2004 09:42:20.92 QIDAutomationHC39M_Free.ttf;1             27KB/32KB       29-JUL-2003 11:25:48.00 ... Qtexsi.ttf;1                             133KB/136KB      25-MAY-2003 15:31:11.00 Qtexw.ttf;1                              150KB/152KB      25-MAY-2003 15:32:33.00  !Total of 37 files, 3.09MB/3.23MB 




*The case of the filename is not important.

2TrueType fonts should be in Stream_LF file format.

GTo generate the appropriate DECW$FONT_DIRECTORY.DAT file for most font formats, issue the command:

 

"
$ FONTCOMPILER /DIRECTORY 




CThe above may or may not operate with TrueType files, and you will Blikely have to generate the DECW$FONT_DIRECTORY_TRUETYPE.DAT file manually. A sample file follows:

 

"
37 FBACKSTAGE.ttf -Grfonts-Backstage-bold-r-normal--0-0-0-0-p-0-iso8859-1 [IDAutomationHC39M_Free.ttf -IDAutomation-HC39M-medium-r-normal--0-0-0-0-m-0-misc-Barcode39 CSUSESerif-Bold.ttf -Suse-Suse-bold-r-normal--0-0-0-0-p-0-iso8859-1 FSUSESerif-Roman.ttf -Suse-Suse-medium-r-normal--0-0-0-0-p-0-iso8859-1 FSUSESans-Bold.ttf -Suse-Suse-bold-r-normal-sans-0-0-0-0-p-0-iso8859-1 MSUSESans-BoldOblique.ttf -Suse-Suse-bold-o-normal-sans-0-0-0-0-p-0-iso8859-1 KSUSESans-Oblique.ttf -Suse-Suse-medium-o-normal-sans-0-0-0-0-p-0-iso8859-1 ISUSESans-Roman.ttf -Suse-Suse-medium-r-normal-sans-0-0-0-0-p-0-iso8859-1 OSUSESansMono-Bold.ttf -Suse-Suse Mono-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1 ... JMCTIMEBI.TTF -UOregon-MAC C Times-bold-i-normal--0-0-0-0-p-0-macedonian-0 KMCTIMEI.TTF -UOregon-MAC C Times-medium-i-normal--0-0-0-0-p-0-macedonian-0 




DThe first line of this data file is the number of font file entries Dwhich follow. Each entry consists of the font file name, and a font Hdescription. There are fourteen fields in the description, separated by Ehyphens (dashes, "-"). Fields may contain embedded spaces. The fields are



HThe next step is to update the list of fonts known to DECwindows, using the xset utility.

 

"
$ mc decw$utils:xset fp rehash 




:It is also possible to reset the font list to the default:

 

"
 $ mc decw$utils:xset fp default 




2This is useful if you need to recover from errors.

4The Notepad utility, normally available through the F"Applications" menu in Session Manager, is a convenient way ?to see if the font is available. Start the application, select ="Options", then select "Font...". In the D"Family (Foundry)" window, you will see the list of fonts Davailable. User-added TrueType fonts will normally be at the end of Fthis list. Select the desired font family, then select the Size (dpi) E(which will always be 0(0) for TrueType fonts), and the various font Goptions (Weight, Slant, Width, etc.) should appear in the next window. =You should then be able to select the desired font and click H[OK] or [Apply] to use it, or [Cancel] "to exit without changing the font.

CIf you don't see all of the fonts you added, check to see that the @number at the beginning of the DECW$FONT_DIRECTORY*.DAT file is Fcorrect, that the files are set to world (or appropriate) access, and ,that TrueType fonts are in Stream_LF format.

ESome applications require entering a full font name, which will look like the font description entry.

GPlease keep in mind that not all applications can use every font which Emay be available on your system. For example, DECterm is designed to ?use families of fonts specifically designed for character cell Happlications. Other fonts (specifically TrueType) may work erratically, >and may result in an unusable display. It is best to use only @monospaced fonts specifically intended for DECterm with DECterm.

EThe SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE] doesn't exist on OpenVMS HVAX V7.3 with DECwindows V1.2-6, but the procedure above does appear to @work if the directory is created and the instructions above are followed.


P

Chapter 12
Miscellaneous Information


A

If you are searching for something here, please (consider using the text-format FAQ.

y

12.1 Where can I find information on escape and control sequences?



@Information on escape and control sequences can be found in the DOpenVMS I/O User's Reference Manual, in the chapter on the Bterminal driver. The chapter also includes details on the general &format and content of these sequences.

DSpecific details on the escape and control sequences supported by a Bparticular serial device are typically found in the documentation @provided with the specific device. Information on the sequences Fsupported by DECwindows DECterm terminal emulator are included in the DECwindows documentation.

GExamples of common escape and control sequences---those typically used Gby the OpenVMS screen management package---can be found in the OpenVMS Esystem file SYS$SYSTEM:SMGTERMS.TXT. (This file can be queried under program control usingE SMG$GET_TERM_DATA, and you don't need to use all of SMG to use this  call.)

EThe following refers to the function keys on the LK-series keyboards Ffound on the VT-series terminals such as the VT220 and VT510, and the ?LK-series keyboards found on the OpenVMS workstations, and the Hkeyboards found on compatible terminals. (Though note that the keyboard @itself does not generate the sequence, the terminal or Hterminal emulator generates the sequence in response to user input.) In Dthe following, {CSI} is decimal code 155 and can be replaced by the Bsequence "{ESC}[" (without the quotes) particularly for seven-bit Doperations, SS3 is decimal code 143 and can be replaced by "{ESC}O" Hparticularly for seven-bit operations. Older VT1xx series terminals and Fany other terminals operating with seven-bit characters should not be 1sent eight-bit operators such as {CSI} and {SS3}.

 

"
,PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}S BKP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}u JKP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}m JKPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}D IRTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~ JPREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~ AF10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~ NHELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~ 




=An example of working with escape sequences (in DCL) follows:

 

"
$ esc5m = "*[5m" $ esc5m[0,8] = 27 $ esc0m = "*[0m" $ esc0m[0,8] = 27 3$ write sys$output esc5m + "blinking text" + esc0m 




BDocumentation on an ANSI terminal relatively similar to the VT525 series is available at:



<Also see the various documentation and manuals available at:



@Information on the ReGIS graphics character set is available at:



Also:



lAlso see Section 11.6, Section 8.13.s

12.2 Does DECprint (DCPS) work with the LRA0 parallel port?



No.

HThe parallel printing port LRA0: found on many OpenVMS Alpha systems is Dcapable of some bidirectional communications, with enough for basic 'operations with most parallel printers.

HDECprint (DCPS) requires more than just the simple handshaking provided Dby the LRA0: port, therefore DCPS does not work with the LRA0: port.n

12.3 How do I check for free space on a (BACKUP) tape?



CYou cannot know for certain, though you can certainly estimate the remaining capacity.

CTape media is different than disk media, as disks have a known and Bpre-determined fixed capacity. Modern disks also appear logically Eperfect, based on bad block revectoring support and the extra blocks Bhidden within the disk structure for these bad block replacements.

DThe capacity of tape media is not nearly as pre-determined, and the Hcapacity can vary across different tape media (slightly different media Elengths or different foil markers or other variations, for instance) Hand even on the same media over time (as bad spots in the media arise). HTapes can vary the amount of recording media required, depending on the =remaining length of the tape, the numbers of correctable and Funcorrectable media errors that might occur, the numbers and sizes of ?the inter-record gaps and related tape structure overhead, the >particular media error recovery chosen, the tape density, the Eefficiently of any data compression in use, and the storage overhead 4required by BACKUP, tar, and other similar commands.

DBACKUP using with the default settings results in approximately 15% Foverhead, in terms of saveset size. (eg: Assuming a 500 KB input, the total size would be 575 KB.)

Assuming no compression:
. 4 GB media / 575 KB saveset = 7294 savesets

Assuming 1:2 compression:
,8 GB media / 575 KB saveset = 14588 savesets



/  
Note

DThere are no inter-record gaps on DAT tapes. When determining media Hcapacity, you have to consider these gaps with nine-track magtape media Eand other formats with gaps. This is not the case with DAT (DDS), as ?the format has no recording gaps. However, the block structure Dunderneath the variable length record recording is based on a block Fsize of circa 124 KB. Further, writing doubles filemarks and such can Hcause a loss of up to the underlying block size. Thus even though there Care no inter-record gaps on DAT, larger savesets are still usually best.


EThe compression algorithms used on various devices are generally not Fdocumented---further, there is no way to calculate the effective data Fcompression ratio, the tape mark overhead, and similar given just the Cdata to be stored on tape---short of actually trying it, of course.

DA typical compression ratio found with "everyday" data is somewhere around 1:1.8 to 1:2.



/  
Note

FOpenVMS often uses the term COMPACTION for compression control, as in /the qualifier /MEDIA_FORMAT=COMPACTION.
b

12.4 Correctly using license PAKs and LMF?



HIf you have multiple LMF$LICENSE.LDB databases in your OpenVMS Cluster, Dthen each and every PAK must be installed in each and every license Ddatabase present in an OpenVMS Cluster. Even if you use /EXCLUDE or F/INCLUDE, you need to have a consistent set of PAKs registered across 7all licensing databases present in the OpenVMS Cluster.

CIf your software license permits it, you can use the following two "commands to transfer license PAKs:

 

"
$ LICENSE COPY... 2$ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,... 




HTo display the particular license(s) required (such as when you receive 3a NOLICENSE error), use the following DCL sequence:

 

"
$ SET PROCESS/PRIVILEGE=ALL $ REPLY/ENABLE 4$ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE 




DThis logical name will cause all license failures to generate OPCOM Dmessages, and this will hopefully show which license(s) you need--- Athere may well also be additional license failures displayed, as Fvarious products can check for and can be enabled by multiple license <PAKs. You will want to deassign this logical name when done.

%Some of the more common license PAKs:

 

"
C  DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP* C  DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP* *  TCP/IP Services:   UCX, or NET-APP-SUP* :  OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USER   OpenVMS VAX:       VAX-VMS $  OpenVMS Galaxy:    OPENVMS-GALAXY .  Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP* .  Cluster (VAX):     VAXCLUSTER, NET-APP-SUP* 




DVarious NET-APP-SUP (NAS) license packages are available, each with Bdiffering collections of products authorized. See the various NAS BSoftware Product Description (SPD) documents for specific details.



GTo determine which license PAK is failing (via a license check failure OPCOM message), use the command:

 

"
9$ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUE 




GRealize that defining this logical name will cause license checks that Hare otherwise hidden (unimplemented, latent, or part of a check for any Fof a series of licenses) to become visible. In other words, expect to Gsee zero or more spurious license check calls when you define this, in 1addition to the check for the particular license.

EFor information on PAKGEN and on generating license PAKs, please see iSection 10.10. For information on obtaining commercial and hobbyist Flicenses, and for additional adminstrative information on LMF, please ksee Section 2.8.4 and Section 2.8.1.




 r Y \ ^  
PreviousNextContentsIndex