f- OpenVMS FAQ -&- page 9)b @5z

HP OpenVMS Systems Documentation

 q> $"b,
Content starts here"D

The OpenVMS Frequently Asked Questions (FAQ)


 l n  
PreviousContentsIndex

m

5.15 Why do I get extra blank pages on my HP Printer?



GFor information on configuring telnet print symbiont, on device controlGlibraries such as SYSDEVCTL.TLB, and for ways of dealing with the extraAblank pages that can arise on various HP printers, please see theEOpenVMS Ask The Wizard area, starting particularly with topic (1020):



GFor additional information on the OpenVMS Ask The Wizard (ATW) area andAfor a pointer to the available ATW Wizard.zip archive, please see@Section 3.8.

BThere are a variety of discussions of this and of related printing?topics in the Ask The Wizard area, in addition to topic (1020).

KAlso see Section 5.34.s

5.16 Drivers and Configuration of New Graphics Controllers?



AThis section contains information on various graphics controllersEsupported by OpenVMS Alpha, and specifically information on where andChow to obtain device drivers for specific early OpenVMS releases---Cdevice drivers for controllers are integrated into and shipped withFOpenVMS Alpha, but versions of these device drivers are sometimes made0available for specific earlier OpenVMS releases.:

5.16.1 The ELSA GLoria Synergy



BOn OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the appropriate9GRAPHICS PCSI kit, and all prerequisite OpenVMS ECO kits:

    $
  • VMS712_GRAPHICS-V0300 or later#
  • VMS72_GRAPHICS-V0100 or later$
  • VMS712_GRAPHICS-V0300 or later


>The ELSA GLoria Synergy is the PBXGK-BB; the PowerStorm 3D10T.?Please ensure you have the most current ECOs for this and otherAgraphics controllers installed; check for and install the current|GRAPHICS kit. (See Section 4.3.2 for some unexpectedly related details.)

>On OpenVMS Alpha V7.2-1, the files necessary for this graphics<controller are located in the distribution CD-ROM directory:

 

"
DISK$ALPHA0721:[ELSA.KIT]




.Also check for any available (later) ECO kits.

FAn earlier kit (ALP4D20T01_071) (for V7.1, V7.1-1H1, and V7.1-1H2) wasFonce available, but has been superceded and is not recommended. Use ofGV7.1-2 or later (and use of one the above GRAPHICS kits as required) istypically the best approach.

?OpenVMS V7.2-2 and later mainline releases directly support the controller.

FAdditional information is available in topics (3419) and (5448) in theAsk The Wizard area:



GFor additional information on the OpenVMS Ask The Wizard (ATW) area andAfor a pointer to the available ATW Wizard.zip archive, please see@Section 3.8.

BSupport for the ELSA GLoria Synergy is integrated into all currentOpenVMS Alpha releases.J

5.16.2 PowerStorm 300, PowerStorm 350



CThe PowerStorm 300 is the PBXGD-AC, while the PowerStorm 350 is the PBXGD-AE.

=For support of the PowerStorm 300 and PowerStorm 350 graphicsBcontrollers, acquire and install the following available ECO kits:

For OpenVMS Alpha V7.1-2:

    .
  • DEC-AXPVMS-VMS712_P350-V0100--4 or later2
  • DEC-AXPVMS-VMS712_GRAPHICS-V0300--4 or later


For OpenVMS Alpha V7.2-1:

    .
  • DEC-AXPVMS-VMS721_P350-V0100--4 or later2
  • DEC-AXPVMS-VMS721_GRAPHICS-V0300--4 or later


ASupport for the PowerStorm 300 and PowerStorm 350 series graphics>controllers is integrated into current OpenVMS Alpha releases.M

5.16.3 PowerStorm 3D30, PowerStorm 4D20



6PowerStorm 3D30 (PBXGB-AA), PowerStorm 4D20 (PBXGB-CA)Ainformation is available in Ask The Wizard topics including topic(2041):



GFor additional information on the OpenVMS Ask The Wizard (ATW) area andAfor a pointer to the available ATW Wizard.zip archive, please see@Section 3.8.4

5.16.4 Radeon 7500



GInstall the current GRAPHICS ECO kit for OpenVMS Alpha V7.2-2 or V7.3-1for support of the Radeon 7500(series PCI and AGP graphics controllers.

DSupport for this controller (without an ECO kit) is first integratedEinto and available in OpenVMS Alpha V7.3-2. (Please do always installFthe most current GRAPHICS ECO kit whenever one is available, however.)p

5.17 How can I acquire OpenVMS patches, fixes, and ECOs?



EYou can acquire and download kits containing OpenVMS fixes (ECOs) forAvarious releases, as well as related support information, via theITRC support center:



FSome systems with Internet firewalls may/will have to use passive modeFFTP to access the above sites. Assuming recent/current versions of the:TCP/IP Services package, the DCL FTP command necessary is:

 

"
3$ DIRECTORY/FTP/ANONYMOUS/PASSIVE ftp.itrc.hp.com::




AYou can subscribe to an email notification list at the ITRC site.

>For a list of OpenVMS ECO kits recently released, you can use:



BExamples and ECO kit installation instructions are included in theEcover letter. For ECO kit email notifications, lists of available ECO@kits, cover letters and other associated documentation, look in:



iFor additional information, please see Section 5.17.

FDo NOT attempt to install a VMSINSTAL-based OpenVMS ECO kit on OpenVMSGAlpha V7.1-2 and later. While VMSINSTAL itself remains available, it isEnot used for OpenVMS Alpha ECO kits starting in OpenVMS Alpha V7.1-2.=OpenVMS Alpha V7.1-2 and later use PCSI for OpenVMS ECO kits.

kSee Section 5.30 for information on ECO kit checksums.f

5.18 How do I move the queue manager database?



/To move the location of the queue database, theGSYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_MANAGER.QMAN$JOURNAL files,to a disk that is fast(er), has@plenty of free space, and that is not heavily used. If the queueAdatabase is on a (busy) OpenVMS system disk, you can and probably;should move it off the system disk to another disk spindle.

To move the queue database:

    D
  1. Checkpoint the journal file. This reduces the file size to the; in-memory database size. This will cause the noted delay.

     

    "
    $ RUN SYS$SYSTEM:JBC$COMMANDJBC$COMMAND> DIAG 0 7
    
    
    

  2. Stop the queue manager

     

    "
    $ STOP/QUEUE/MANAGER/CLUSTER
    
    
    F

  3. Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from the present location for safety.

     

    "
    @$ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]
    
    
    E

  4. Create a new directory for the queue database. Insure that thisH disk is accessible to all nodes that can run the queue manager. If theI /ON list for the queue manager is "/ON=(*)", the disk must be' available to all nodes in the cluster

     

    "
    $ CREATE/DIR fast_disk:[qman]
    
    
    H

  5. Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the new directory

     

    "
    D$ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]
    
    
    $

  6. Delete the old queue database.

     

    "
    6$ DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*;*
    
    
    <

  7. Restart the queue manager pointing to the new location

     

    "
    &$ START/QUEUE/MANAGER fast_disk:[qman]
    
    
    

x

5.19 How do I delete an undeletable/unstoppable (RWAST) process?



F"Undeleteable" jobs are usually "undeleteable" forCa reason---this can track back to insufficient process quotas, to aBkernel-mode error in OpenVMS or a third-party device driver, or toother odd problems.

DThese undeletable jobs typically become of interest because they are?holding onto a particular resource (eg: tape drive, disk drive,Gcommunications widget) that you need to use... If the particular deviceFsupports firmware, ensure that the device firmware is current -- TQK50Econtrollers are known for this when working with old firmware. (That,and the infamousF"MUA4224" firmware bug.) If this device has a driver ECO kitBavailable, acquire and apply it... If the particular relevant host+component has an ECO, acquire and apply it.

DUseful tools include SDA (to see what might be going on) and DECamdsF(which increase and thus potentially fix quota-related problems). (nb:=Applications with quota leaks will obviously not stay fixed.)

FIf the stuck application is BACKUP, ensure you have the current BACKUPAECO and are directly following the V7.1 or (better) V7.2 or laterAprocess quota recommendations for operator BACKUP accounts. Quota<details are in the OpenVMS System Manager's Manual.

CIf the firmware and ECO levels are current, the best approach is toBtake a system crashdump, and pass a copy of the dump file along to<whomever is maintaining the device driver for the particularCdevice/widget/driver involved, with any details on how you got intoCthis situation. (The reboot involved with taking the crashdump willobviously clear the problem.)

DThere was some kernel-mode code (typically for OpenVMS VAX) that canFreset the device ownership field, but that is rather obviously only anDinterim solution---the real fix is avoiding the loss of the IRP, theCprocess quota leak, or whatever else is "jamming up" thisparticular process..._

5.20 How do I reset the error count(s)?



GThe system reboot is the only supported approach prior to V7.3-2, but a@reboot is obviously undesirable in various situations---there is?presently no supported mechanism to reset error counts once theGerror(s) have been logged on these older releases. On V7.3-2 and later,you can use the DCL command:

 

"
$ SET DEVICE/RESET=ERROR_COUNT




BAs for an unsupported approach---and be aware of the potential forFtriggering a system crash, you need to determine the system address ofDthe error count field. For a device, this is at an offset within theFdevice's UCB structure. On VAX, the field is at an offset symbolicallyFdefined as UCB$W_ERRCNT. On Alpha, this field's offset is symbolicallyFdefined as UCB$L_ERRCNT. The former is a word in size; the latter is a longword.

FYou now need to locate the system address of the UCB$%_ERRCNT field ofGthe device you wish to reset. Enter SDA. In the following, you will seeFdesignations in {} separated by a /. The first item in braces is to beDused on the VAX and the second item should be used on an Alpha. (ie. {VAX/Alpha})

 

"
$ ANALYZE/SYSTEM5SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STB3SDA>  ! SHOW DEVICE the device with the error(s)B"SDA>  SHOW DEVICE <ddnc:>&SDA>  EVALUATE UCB+UCB${W/L}_ERRCNT9Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offsetV

<


c1Record the hexadecimal value 'hhhhhhhh' returned.=

aGYou can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I preferpto do, issue the following:c

r 
e
"
!SDA> SPAWN RUN SYS$SHARE:DELTAg




>BOn both VAX and Alpha, the DELTA debugger will be invoked and will?ident- ify itself. On Alpha, there will be an Alpha instructioniGdecoded. For those unfamiliar with DELTA, it does not have a prompt and Eonly one error message---Eh? (Well, for sake of argument, there might Dbe another error produced on the console if you're not careful. This7second error is more commonly known as a system crash.)p

o*If you are on a VAX, enter the command: [W

C*If you are on Alpha, enter the command: [L

lGThese set the prevailing mode to word and longword respectively. Remem- %ber the UCB${W/L)_ERRCNT differences?t

lNow issue the command 1;M7

g DELTA will respond with 00000001

SEYou are now poised to ZAP the error count field. To do so you need touCen- ter the system address and view its contents. The format of thet"command to do this is of the form:

i 
0
"
IPID:hhhhhhhh/

n


oHFor an IPID, use the IPID of the SWAPPER process. It is always: 00010001

e.Thus, to ZAP the error count, you would enter:

< 
o
"
00010001:hhhhhhhh/




x?When you enter the / SDA will return the content of the addressyGhhhhhhhh. This should be the error count (in hexadecimal) of the device Fin question. If it is not, you did something wrong and I'd suggest youDtype a carriage return and then enter the command EXIT to get out of4DELTA. Regroup and see where your session went awry.

rFIf you entered your address correctly and the error count was returned-as in the following example, you can proceed.i

i 
n
"
100010001:80D9C6C8/0001   ! output on VAX, 1 errord

<


d 
r
"
700010001:80D9C6C8/00000001   ! output on Alpha, 1 errorn




e?You can now ZAP the error count by entering a zero and typing a>carriage return. For example:t

m 
l
"
F00010001:80D9C6C8/0001 0[return]   ! output on VAX. 1 error




 
e
"
L00010001:80D9C6C8/00000001 0[return]   ! output on Alpha, 1 error

v


d0Now type the command EXIT and a carriage return.

e!Alternatively, reboot the system.=v

5.21 How do I find out if the tape drive supports compression?



e6For various SCSI-based MK-class magnetic tape devices:

0 
7
"
2$ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")$ Comp_sup = %X002000005$ Comp_ena = %X00400000x1$ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -r,    WRITE SYS$OUTPUT "Compression supported"1$ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -n*    WRITE SYS$OUTPUT "Compression enabled"


t

5.22 Can I copy SYSUAF to another version? To VAX? To Alpha?



oBThe format of the SYSUAF.DAT, RIGHTSLIST, and associated files areGupward-compatible, and compatible across OpenVMS VAX, OpenVMS Alpha and DOpenVMS I64 systems. (This compatibility is a a basic requirement ofGmixed-version OpenVMS Cluster configurations and OpenVMS upgrades---forDspecific support information, please see the OpenVMS Cluster rollingEupgrade and mixed-version requirements.) That said, it's the contents Hof the SYSUAF and RIGHTSLIST files that will make this more interesting.

EThe same basic steps necessary for moving RIGHTSLIST and SYSUAF files Cto another node are rather similar to the steps involved in mergingrCthese files in an OpenVMS Cluster---see the appendix of the OpenVMSdECluster documentation for details of merging files. (You might not beeDmerging the contents of two (or more) files, but you are effectivelyFmerging the contents of the files into the target system environment.)

Considerations:t

    I
  • applications often hold SYSUAF or RIGHTSLIST open, meaning a system05 reboot is often the best way to activate new files./F
  • the meanings of the RESTRICTED and CAPTIVE flags settings on the% UAF entries have changed over time.nG
  • the new NET$PROXY.DAT file that is initially created based on the,F contents of the NETPROXY.DAT during the OpenVMS VAX V6.1 upgrade andC during the OpenVMS Alpha V6.2 upgrade. This file is maintained in> parallel with NETPROXY.DAT.aA
  • the RIGHTSLIST identifier values and UIC values that end up B scattered around the target system must be rationalized with the2 contents of the new RIGHTSLIST and SYSUAF files.
1

DThe lattermost case---resolving the identifier values---is often theCmost interesting and difficult part. If you find that an identifier Cvalue (or identifier name) from the source RIGHTSLIST collides withlCthat of an identifier existing on the target system, you must firstrCdetermine if the two identifiers perform the same function. In mostlCcases, they will not. As such, you will have to find and chance allwAreferences to the identifier value(s) (or name(s)) to resolve the"collision".

ADIf you encounter a collision, changing both of the identifier binaryDvalues (or names) involved in the collision to new and unique values<can prevent security problems if you should miss a couple ofDidentifiers embedded somewhere on the target system during the wholeEconversion process---rather than the wrong alphanumeric value for the>Gidentifier being displayed, you'll simply see the binary format for thedGidentifier displayed, and no particular access will be granted. And anypBDCL commands or such that reference the old alphanumeric name willDfail, rather than silently (and potentially erroneously) succeeding.

rBSimilar requirements exist for UIC values, as these too tend to beEscattered all over the system environment. Like the binary identifierfEvalues, you will find UIC values associated with disks, ACLs, queues,cand various other structures. 

sEFor a list of the various files shared in an OpenVMS Cluster and thateGcan be involved when relocating an environment from one node to anotherAA(or merging environments into an OpenVMS Cluster), please see the2ESYLOGICALS.TEMPLATE file included in OpenVMS V7.2 and later releases.,

=CProcedures to extract the contents of a (potentially corrupt) queueiEdatabase are provided on the OpenVMS Freeware (V5) and can be used tooBcombine two queue databases together while shuffling files betweenOpenVMS Cluster hosts.

eGFor related discussions of splitting a cluster into two or for removingtFa node from cluster (political divorce, etc), see topics (203), (767),,(915) and others in the Ask The Wizard area:

s

bGFor additional information on the OpenVMS Ask The Wizard (ATW) area andgAfor a pointer to the available ATW Wizard.zip archive, please seet@Section 3.8.f

5.23 How do I delete (timeout) idle processes?



DThere is no such command integrated within OpenVMS, though there areG(optional) timers available within certain terminal servers and similar Gdevices, and there is an integrated time-of-day mechanism that providest,control over when a user can access OpenVMS.

_BAs for available tools, there are DECUS, freeware, and third-partyBtools known variously as "idle process killers" (IPK) orF"terminal timeout" programs, as well as various other names.9Examples include: Saiga Systems Hitman, Watchdog, MadGoateCWatcher (via the MadGoat site or the OpenVMS Freeware), Kblock, thetBNetworking Dynamics tool known as Assassin, and the Zap tool. Also?available is the XLNperformance system management utility, fromt XLNsystems..

9A related package (for DECwindows sessions) is xtermlock. 

aGIf the forgetful users are in an application menu environment, the menuO7can potentially be extended to provide this capability.p

5.24 Do I need a PAK for the DECevent (HP Analyze) tool?



m@DECevent and HP (Compaq) Analyze are available to customers withFsupport contracts. The PAK is required only for the advanced functionsEof DECevent, the basic bits-to-text translation of the error log doesaFnot require a license PAK. Ignore the prompt, in other words. (The PAKEshould be available to you if you have a hardware support contract or/Ewarrantee, and the PAK enables the use of the advanced error analysisa/and notification capabilities within DECevent.)n

o;Please see the following website for details and downloads:i Analyze)z

o

h Also see the+tool that is available on V7.3-2 and later.D

O 
p
"
$ ANALYZE/ERROR/ELV=


k

5.25 INITIALIZE ACCVIO and ANSI tape label support?

t

iBA change was made (back in 1988) to (as it was then known) VAX/VMSCV5.1-1 that added support for the then-new ANSI X3.27-1987 magnetic Dtape label standard. Prior to the ANSI X3.27-1987 standard, the dateEfield in the ANSI HDR1 record permits dates only as far as the end ofdGYear 1999. With ANSI X3.27-1987, dates through Year 1999 and dates fromt!Years 2000 to 2099 are permitted.m

BVersions of INIT.EXE and MTAACP.EXE from VAX/VMS releases prior toGV5.1-1 will potentially have problems properly processing ANSI magneticetapes when Y2KEand later dates are involved---the DCL INITIALIZE command is known toe+encounter access violation (ACCVIO) errors.

CThe available solutions include upgrades, or setting the date back.YDDirect initialization of the tape with the new headers (via $qio) isFalso clearly possible, though the limitation within the old MTAACP.EXE2magtape ACP image is not nearly so easy to bypass.d

5.26 How do I recover from INSVIRMEM errors?



u<Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX releases,FVIRTUALPAGECNT and PGFLQUOTA limit the amount of virtual address space"that is available to each process.

BFurther limiting the amount of address space is the size of systemGspace (S0 and S1 space). On OpenVMS Alpha versions prior to V7.0 and onaCall OpenVMS VAX releases, VIRTUALPAGECNT and MAXPROCESSCNT togetherpFdetermine the size of the page table data structures that occupy large?tracts of system space. When no system virtual address space is,Favailable for the stuff that needs it---this includes the page tables,Anon-paged pool, and various other structures---then the values ofb5VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.i

eDIn OpenVMS Alpha V7.0 and later, the page table data structures haveGbeen moved out of S0 and S1 space and into page table space. In OpenVMStFAlpha V7.2 and later, certain large data structures found in non-pagedApool (eg: lock management structures) have been moved into 64-bitiDspace, thus freeing up room in non-paged pool and in S0 and S1 spaceE(where non-paged pool resides) while also permitting much larger datar structures.tr




 i nl n  
PreviousNextContentsIndex

 

n#p6pn<whomever is maintaining the device driver for the particularCdevice/widget/driver involved, with any details on how you got inta>BUCX$CONFIGURATION.DAT or TCPIP$CONFIGURATION.DAT database. Thus ifDSCSNODE is changed, the IP host name reconfiguration must occur, andBthe required reconfiguration can occur only after a system reboot.@Accordingly, it is best to perform the TCP/IP Services host name&reconfiguration step after the reboot.o

tEThere are likely a few other areas where the nodename will be stored.sGLocal procedures and data files are one such example, and various sites=Fwill have the system name loaded in the operator control panel via theDOCP_TEXT console environment variable available at the SRM prompt onsome Alpha systems is another.

:If the system is configured in a VMScluster and you changeFeither the SCSNODE or the SCSSYSTEMID---but not bothvalues---then youtDwill have to reboot the entire VMScluster. (The VMScluster remembers<the mapping between these two values, and will assume that aCconfiguration problem has occured if a mismatched pair appears, andaFwill refuse to let a node with a mismatched pair join the VMScluster.)

iETo calculate the correct SCSSYSTEMID value, multiply the DECnet Phase DIV area number by 1024, and add the DECnet Phase IV node number. ForFexample, the SCSSYSTEMID value for a DECnet node with address 19.22 is!19478. ((19 * 1024) + 22 = 19478)o

tCThis may well have missed one or two configuration tools (or more!)mDthat are needed at your site---the node name tends to get stored all=over the place, in layered products, and in local software...x

>uAlso see Section 15.6.3 and Section 15.6.4.hw




 r