DECwindows Motif
Version 1.2-5 for OpenVMS
Release Notes
Previous Contents Index

Proxy Gateway Resources

When your proxy gateway has been established by your network or system administrator, you can use its resources. Table 1-5 provides additional details about proxy gateway support in the NCSA Mosaic Version 2.4 browser.

Table 1-5 Proxy Gateway Resources
Resource Description
ftpProxy: String Used for ftp URLs.
gopherProxy: String Used for gopher URLs.
httpProxy: String Used for http URLs.
newsProxy: String Used for news URLs.
waisProxy: String Used for wais URLs.
ProxyGateway: String Used for all access methods.

1.15.5 Restrictions for Using Mosaic from Behind a Firewall

V1.2--3

The following sections present information about using the ProxyGateway and NoProxy resources with Mosaic to access information on the Internet when security restrictions (that is, a firewall) exist between internal and external network access at your site.

1.15.5.1 ProxyGateway Resource

NCSA Mosaic Version 2.4 provided in DECwindows Motif for OpenVMS supports the proxy gateway (ProxyGateway) resource. A proxy gateway is a trusted agent that enables Mosaic to access network information that is either within or outside the firewall, but not both.

When the Mosaic browser is used from behind a firewall, Mosaic can use the proxy gateway to pass network requests to the Internet in a URL formatted address. The proxy gateway returns the results to the Mosaic browser. The process of passing and returning network requests is transparent to the user. You can view documents on the Internet without difficulty.

Note, however, that if the proxy gateway is located outside of your firewall, then information behind the firewall (such as home pages, World Wide Web documents, and Notes files) cannot be accessed by the proxy gateway.

1.15.5.2 NoProxy Resource

If your site requires the ability to access Internet information both within and outside the firewall, then a version of Mosaic that supports the NoProxy resource is required. This resource allows you to specify a list of domains that should not be consulted by the proxy gateway (that is, access to information in these domains does not go through the proxy gateway).

NCSA Mosaic Version 2.4a for OpenVMS supports the NoProxy resource and enables access to a proxy gateway. If your site operates in a firewall environment and you need to access information from both within and outside of the firewall, you can copy this pre-release version of Mosaic from the following URL: 


   ftp://gatekeeper.dec.com/pub/DEC/Mosaic/

As previously stated, the NoProxy resource restricts access for the proxy gateway to a set of domains that are not consulted by the proxy gateway. You can specify the NoProxy resource, provided that you have NCSA Mosaic Version 2.4a for OpenVMS, in the file DECW$USER_DEFAULTS:MOSAIC.DAT according to the following format: 


     Mosaic*ProxyGateway:    http://www-proxy.site.org:8080/ 
     Mosaic*NoProxy:         localhost, site.org
Where: Description
www-proxy.site.org Name of the host that runs the proxy server
8080 Port number through which Mosaic communicates to the proxy server through the firewall
local host, site.org List of site names, which are separated by commas, excluded from going through the proxy server

Refer to the following location (URL) for additional information about proxy gateways: 


  http://info.cern.ch/hypertext/WWW/Daemon/user/Guide.html

Chapter 2
System Manager Release Notes

This chapter contains system manager release notes.

2.1 Recommended Reboot After Installation

V1.2--4

Although system parameters are correct, it may be necessary to reboot the system after installing DECwindows Motif for OpenVMS.

If the DECwindows login box does not appear after you install DECwindows Motif and restarting DECwindows Motif with the command @SYS$MANAGER:DECW$STARTUP RESTART, you will need to reboot the system.

2.2 Log Off Console Before DECwindows Can Start

V1.2--4

If DECwindows is not started during OpenVMS startup, it can be started later by running SYS$MANAGER:DECW$STARTUP.COM from a system account. Perform the following steps:

  1. Define the logical name DECW$IGNORE_DECWINDOWS with a value of TRUE in SYS$STARTUP:SYSTARTUP_VMS.COM.
  2. Reboot the system.
  3. When system startup has completed, press Return and log in to the workstation console.
  4. After logging in, start DECwindows by invoking the SYS$MANAGER:DECW$STARTUP.COM command procedure, as in the following example: 


    $ @SYS$MANAGER:DECW$STARTUP

    Note
    Once DECW$STARTUP.COM has completed, you must log out of the console in order for DECwindows to start.

2.3 Installation Verification Procedure Error in UIL Compiler

V1.2--5

If you installed a previous version of DECwindows (for example, V1.2--4) without using the PCSI_INSTALLATION.COM procedure, you might get this error. Enter the following code into a command file and run it. This will check for .CLD files. If it finds any, it deletes them: 


$ VAX   = 1 
$ Alpha = 2 
$ ARCH = F$Getsyi("ARCH_TYPE") 
$! 
$! See if the user wants the New Desktop to be the default desktop. 
$! 
$ if ARCH .ne. Alpha then goto skip_new_desktop 
$ type sys$input 
 
  The New Desktop is a graphical user interface that is derived from the 
  Common Desktop Environment (CDE).  It offers the following features not 
  available with the traditional DECwindows desktop: 
 
        o Multiple workspaces for greater flexibility in managing windows on 
          the screen. 
 
        o An icon-based File Manager to make it easier to manipulate files 
          from the graphical user interface. 
 
        o Enhanced support for the drag-and-drop feature, which is fully 
          supported in the new File Manager and Application Manager 
          applications. 
          o New Image Viewer and Icon Editor applications. 
 
  Both the New Desktop and the DECwindows desktop provide the same underlying 
  X and Motif libraries and the same DECterm, Bookreader, Mail, and Calendar 
  applications. 
 
$ inquire/nopunct answer - 
   "Do you want the New Desktop to be your default desktop ([y]/n)?" 
$ if answer .eqs. "" then answer = "yes" 
$ ! 
$ ! Create the decw$default_desktop.com file on the destination device. 
$ ! 
$ dest = "sys$sysdevice:[vms$common]" 
$ sysmgr_dir = f$search(dest+"SYSMGR.DIR") 
$ sysmgr_node = f$parse(sysmgr_dir,,,"NODE") 
$ sysmgr_device = f$parse(sysmgr_dir,,,"DEVICE") 
$ sysmgr_directory = f$parse(sysmgr_dir,,,"DIRECTORY") - "]" + ".SYSMGR]" 
$ dname = sysmgr_node + sysmgr_device + sysmgr_directory + - 
        "DECW$DEFAULT_DESKTOP.COM" 
$ if f$search(dname) .nes. "" then delete 'dname';* 
$ open/write/error=dopenerr dfile 'dname' 
$ if answer 
$   then write dfile "$ DECW$START_NEW_DESKTOP == ""TRUE""" 
$   else write dfile "$ DECW$START_NEW_DESKTOP == ""FALSE""" 
$ endif 
$ close dfile 
$ set protection=(sy:rwed,ow:rwed,gr:re,wo:re) 'dname' 
$ goto skip_new_desktop 
$dopenerr: 
$ write sys$output "" 
$ write sys$output "  WARNING: Can't create ''dname'" 
$ write sys$output "" 
$skip_new_desktop: 
$! 
$! Update [SYSLIB]DCLTABLES.EXE with new verbs 
$! 
$ create_new_dcltable: 
$ IF f$search("SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD") .EQS. "" - 
   THEN GOTO skip_uil 
$ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD 
$!$ skip_uil: 
$ IF f$search("SYS$COMMON:[SYSLIB]ddif$view.cld")  .EQS. "" THEN GOTO skip_view 
$ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      SYS$COMMON:[SYSLIB]ddif$view.cld 
$! 
$skip_view: 
$ IF f$search("SYS$COMMON:[SYSLIB]pswrap.cld")  .EQS. "" THEN GOTO skip_pswrap 
$ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 
      SYS$COMMON:[SYSLIB]pswrap.cld 
$skip_pswrap: 
$! 
$! Install the DCLTABLES 
$! 
$ set noon 
$ INSTALL LIST SYS$LIBRARY:DCLTABLES 
$ status = $status 
$ if status .eq. %X10000001 !%SYSTEM-S-NORMAL 
$ then 
$   INSTALL REPLACE SYS$LIBRARY:DCLTABLES/OPEN/HEADER_RESIDENT/SHARED 
$ endif 
$ set on

2.4 Problem With Delayed DECwindows Startup (Alpha Only)

V1.2--4

On OpenVMS Alpha systems, error messages similar to those shown in Example 2-1 are displayed when:

These error messages are generated because there is not enough memory in the granularity hints region to install images resident. The images are installed nonresident, without shared address linkage, so DECwindows startup can complete. However, the performance and memory advantages of using shared address linkage are lost.

The amount of memory in the granularity hints region is determined by the system parameter GH_RSRVPGCNT. In DECwindows Motif Version 1.2-3 for OpenVMS and earlier versions, this parameter was set to 512, which allowed DECwindows to start at any time with shared address linkage. However, this also consumed a large amount of physical memory.

To prevent memory from being wasted, OpenVMS temporarily increases the size of the granularity hints region during system startup and releases the unused memory once startup has completed. Starting with DECwindows Motif Version 1.2-4 for OpenVMS DECwindows Motif takes advantage of this by allowing GH_RSRVPGCNT to remain at its default value of zero. DECwindows images can be installed resident and with shared address linkage as long as DECwindows is started during system startup, as it is by default.

Example 2-1 Error Messages Displayed Due to Low Memory in Granularity Hints Region 

%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%RUN-S-PROC_ID, identification of created process is 00000092 
 
%RUN-S-PROC_ID, identification of created process is 00000093 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -SYSTEM-F-PAGOWNVIO, page owner violation 
 -SYSTEM-S-NORMAL, normal successful completion 
 -DEBUG-W-NOIOCHAN, no I/O channel available 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -SYSTEM-F-VA_IN_USE, virtual address already in use 
 -SYSTEM-S-NORMAL, normal successful completion 
 -DEBUG-W-NOIOCHAN, no I/O channel available 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -SYSTEM-F-VA_IN_USE, virtual address already in use 
 -SYSTEM-S-NORMAL, normal successful completion 
 -DEBUG-W-NOIOCHAN, no I/O channel available 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -SYSTEM-F-VA_IN_USE, virtual address already in use 
 -SYSTEM-S-NORMAL, normal successful completion 
 -DEBUG-W-NOIOCHAN, no I/O channel available 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re 
 
%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. 
 -SYSTEM-F-VA_IN_USE, virtual address already in use 
 -SYSTEM-S-NORMAL, normal successful completion 
 -DEBUG-W-NOIOCHAN, no I/O channel available 
 
%INSTALL-I-NONRES, installed image non-resident with other specified options 
 -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re

2.5 DECwindows Motif Login Screen---Known Color Problem

V1.2

A problem may occur on systems that have a customized DECW$LOGIN.DAT file. The Start Session dialog box is the color blue instead of tan. If this condition exists, look for a customized DECW$LOGIN.DAT file in the directory SYS$COMMON:[DECW$DEFAULTS.USER] and move it to SYS$MANAGER. A DECW$LOGIN.DAT file in SYS$COMMON:[DECW$DEFAULTS.USER] prevents the "*background:" resource from being defined; thus, it will default to the color blue.

Compaq provides a copy of the DECW$LOGIN.DAT file in the SYS$COMMON:[DECW$DEFAULTS.SYSTEM] directory. Any customized versions of this file should reside only in SYS$MANAGER.

2.6 System Tuning for Non-VGA Devices

V1.2

The DECwindows server requires specific tuning for graphics-intensive and 3D applications because of greater demand for system resources. You need to make adjustments for server quotas on 3D accelerated systems. These are minimum values suggested for a system with as little as 64 MB of physical memory and for running complex clients.

Use the AUTHORIZE utility to set the following SYSTEM account quotas to the minimum values shown in Table 2-1.

Table 2-1 Recommended Quotas for System Tuning
Parameter Value
FILLM 400
ENQLM 1024
WSDEF 10240
WSQUO 16384
WSEXTENT 1 20480
PGFLQUO 2 3 270000

1This value cannot exceed WSMAX.
2PAGEFILE.SYS must be of the same or greater size.
3Use for 370000 for ZLX--E and ZLXp--E systems.

The server has its own quotas that are set in SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COM. If this file does not exist, copy the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM and edit the file to include the following values:
Quota Value
DECW$SERVER_FILE_LIMIT 400
DECW$SERVER_ENQUEUE_LIMIT 1024
DECW$SERVER_WSDEF 10240
DECW$SERVER_WSQUOTA 16384
DECW$SERVER_WSEXTENT 20480
DECW$SERVER_PAGE_FILE 1 270000

1Use for 370000 for ZLX--E and ZLXp--E systems.

If you use larger values, you must also modify the corresponding SYSTEM account quotas that you set with the AUTHORIZE utility.

Tuning for Animation Applications

If your application involves lengthy animation sequences of large models or assemblies, performance may be improved by setting the following working set quotas and values:
Parameter Value
WSDEF 10240
WSQUO 20480
WSEXTENT 32768

You need to set the corresponding server quotas as follows:
Quota Value
DECW$SERVER_WSDEF 10240
DECW$SERVER_WSQUOTA 20480
DECW$SERVER_WSEXTENT 32768

Note
The parameters should not be tuned upward unless you have at least 128 MB of physical memory.

Determining Tuning Needs

To determine whether you need to set larger parameters, monitor the server process during the heaviest display usage. If the working set use approaches the maximum WSEXTENT, then you need to adjust the values. However, do not set large values unless it is necessary. If you set these values too high, performance may be degraded. Optimal DECwindows server performance depends on application demands.

Use the SYSGEN utility to issue the SHOW VIRTUALPAGECNT command to determine the current virtual page count a process is allowed to have. If it is less than 525000, edit the SYS$SYSTEM:MODPARAMS.DAT file and add the following line: 


   MIN_VIRTUALPAGECNT = 525000

Note that the minimum value for VIRTUALPAGECNT for a working X server needs to be 525000 when a ZLX-E or a ZKXp-E graphics card is installed. MIN_VIRTUALPAGECNT could be set as high as the equivalent of your total available physical memory and page file space.

MIN_WSMAX must be at least as large as the largest WSEXTENT value set from among your accounts. Please refer to the OpenVMS System Manager's Manual for more information. Do not exceed what AUTOGEN gives for WSMAX. See the warning in the AUTOGEN report.

The next time you run AUTOGEN and reboot, the new values will take effect. VIRTUALPAGECNT should not be less than the sum of your WSEXTENT and PGFLQUO, or the server cannot make full use of the quotas. In addition, you need to increase the size of the page file to accommodate the pagefile quotas of both the server and your clients. Note that pagefile quota for the server is derived from system page files.

If, after initial tuning and considerable use, the server is failing or is unnecessarily unresponsive, the server may have run out of memory or memory may have become fragmented. A particularly demanding application may require that you give the server even larger PGFLQUO and VIRTUALPAGECNT values.

If the server error log SYS$MANAGER:DECW$SERVER_0_ERROR.LOG contains the statement xxx: Out of memory, increase the pagefile quota for the server. Set this by modifying both system quota PGFLQUO and DECW$PRIVATE_SERVER_SETUP.COM and virtual page count via MODPARAMS.DAT and AUTOGEN.

Note that, in multiheaded configurations (for example, ZLX--E1 and ZLX--E2), the PGFLQUO and the DECW$SERVER_PAGE_FILE parameters should be increased to meet your system requirements.

System Hangs With Some Graphics Cards

V1.2--5

On systems with Powerstorm 4d20 or ZLXp-E2 graphics cards, the operating system may hang or become extremely sluggish if you have a large number of open application windows or if certain CDA documents are opened. To verify that a system hang is caused by this problem, use the Watch Errors utility in the Desktop Tools drawer of the Application Manager. If the system hang is due to this problem, you will see the following: 


-> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn
%SYSTEM-F-EXBUFOBJLM, exceeded systemwide buffer object page limit (MAXBOBMEM) 
-> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn
SYSTEM logged out at dd-mmm-yyyy hh:mm:ss

At the present time, there is no workaround for this problem other than using fewer windows (increasing the MAXBOBMEM value doesn't fix the problem). If you experience this problem, you may want to keep a DECterm window free so that you can perform a graceful system reboot. Otherwise, you will need to perform a hard reboot.

2.7 Previously Optional Files Moved

V1.2--4

The files listed in Table 2-2 from the optional areas have been moved into the required files areas. These files are now installed by default.

Table 2-2 Previously Optional Files Now Required
File Name File Function
[SYSHLP.EXAMPLES.DECW]ICO.EXE Programming example image
[SYSHLP.EXAMPLES.DECW.UTILS]BITMAP.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]ATOBM.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]BMTOA.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XDPYINFO.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XEV.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XLSATOMS.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XLSFONTS.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XLSWINS.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XMAG.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XMBIND.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XMODMAP.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XPR.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XPROP.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XRDB.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XREFRESH.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XSET.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XSETROOT.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XWD.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XWININFO.EXE MIT utility image
[SYSHLP.EXAMPLES.DECW.UTILS]XWUD.EXE MIT utility image

Previous Next Contents Index