| Previous | \Contents | ^Index |
E Dismount the disk, and mount it privately. If the disk is mounted by E more than one node in an OpenVMS Cluster, dismount it from all other C nodes. If this disk is an OpenVMS system disk, shut down all other + nodes that are bootstrapped from this disk.
= Issue the SET VOLUME/LABEL command, specifying the new label.
E On OpenVMS V6.0 and later, issue the following PCSI command to reset E the label information stored within the PCSI database to reflect the new disk volume label:
|
" + $ PRODUCT REGISTER VOLUME old-label device |
E Locate any references in the system startup (typically including the B disk MOUNT commands) and any DISK$label references in application / files, and change the references appropriately.
G If this is a system disk (for the host or for a satellite), also check H the DECnet MOP or LANCP boot database, as well as any references to the $ disk created by CLUSTER_CONFIG*.COM.
E If Compaq Analyze is in use, check the system startup procedures for H the Compaq Analyze tool. Certain versions of Compaq Analyze will record : specific disk volume labels within the startup procedures.
Remount the disk appropriately. a 5.14 How can I set up a shared directory?
H To set up a shared directory---where all files created in the directory H are accessible to the members of specified group of users---you can use / an access control list (ACL) and an identifier.
D The following also shows how to set up a resource identifier, which A further allows the disk resources to be charged to the specified F identifier rather than each individual user. (If you don't want this, H then omit the attributes option on the identifier creation and omit the ' entry added in the disk quota database.
. Add an identifier using the AUTHORIZE utility:
|
" 2 ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier |
? Grant the identifier to each user in the group using AUTHORIZE:
|
" * GRANT/IDENTIFIER groupidentifier username |
A If disk quotas are in use, add an entry via SYSMAN for each disk:
|
" E DISKQUOTA ADD groupidentifier/PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu: |
G Set the shared directory to have an ACL similar to the following using F the SET SECURITY (V6.0 and later) or SET ACL (versions prior to V6.0) command:
|
" ' (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W) N (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE) > (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE) * (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE) |
@ If there are files already resident in the directory, set their E protections similarly. (The OPTIONS=DEFAULT, DEFAULT_PROTECTION, and # CREATOR ACEs apply to directories.)
B The default protection mask is used to establish the default file B protection mask, this mask does not prevent the users holding the B specified groupidentifier from accessing the file(s), as they can D access the file via the explicit identifier granting access that is present in the ACL.
F For further information, see the OpenVMS Guide to System Security D Manual, specifically the sections on ACLs and identifiers, and resource identifiers. m 5.15 Why do I get extra blank pages on my HP Printer?
H For information on configuring telnet print symbiont, on device control H libraries such as SYSDEVCTL.TLB, and for ways of dealing with the extra B blank pages that can arise on various HP printers, please see the E OpenVMS Ask The Wizard area, starting particularly with topic (1020):
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9.
C There are a variety of discussions of this and of related printing ? topics in the Ask The Wizard area, in addition to topic (1020).
; Also see Section 5.34. s 5.16 Drivers and Configuration of New Graphics Controllers?
B This section contains information on various graphics controllers F supported by OpenVMS Alpha, and specifically information on where and D how to obtain device drivers for specific early OpenVMS releases--- D device drivers for controllers are integrated into and shipped with G OpenVMS Alpha, but versions of these device drivers are sometimes made 0 available for specific earlier OpenVMS releases. : 5.16.1 The ELSA GLoria Synergy
C On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the appropriate 9 GRAPHICS PCSI kit, and all prerequisite OpenVMS ECO kits:
> The ELSA GLoria Synergy is the PBXGK-BB; the PowerStorm 3D10T. @ Please ensure you have the most current ECOs for this and other B graphics controllers installed; check for and install the current l GRAPHICS kit. (See Section 4.2.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.
G An earlier kit (ALP4D20T01_071) (for V7.1, V7.1-1H1, and V7.1-1H2) was G once available, but has been superceded and is not recommended. Use of H V7.1-2 or later (and use of one the above GRAPHICS kits as required) is typically the best approach.
@ OpenVMS V7.2-2 and later mainline releases directly support the controller.
G Additional information is available in topics (3419) and (5448) in the Ask The Wizard area:
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9.
C Support for the ELSA GLoria Synergy is integrated into all current OpenVMS Alpha releases. J 5.16.2 PowerStorm 300, PowerStorm 350
D The PowerStorm 300 is the PBXGD-AC, while the PowerStorm 350 is the PBXGD-AE.
> For support of the PowerStorm 300 and PowerStorm 350 graphics B controllers, acquire and install the following available ECO kits:
For OpenVMS Alpha V7.1-2:
For OpenVMS Alpha V7.2-1:
B Support 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
6 PowerStorm 3D30 (PBXGB-AA), PowerStorm 4D20 (PBXGB-CA) B information is available in Ask The Wizard topics including topic (2041):
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9. 4 5.16.4 Radeon 7500
H Install the current GRAPHICS ECO kit for OpenVMS Alpha V7.2-2 or V7.3-1 for support of the Radeon 7500 ( series PCI and AGP graphics controllers.
E Support for this controller (without an ECO kit) is first integrated F into and available in OpenVMS Alpha V7.3-2. (Please do always install F the most current GRAPHICS ECO kit whenever one is available, however.) p 5.17 How can I acquire OpenVMS patches, fixes, and ECOs?
F You can acquire and download kits containing OpenVMS fixes (ECOs) for > various releases, as well as related support information, via:
G Some systems with Internet firewalls may/will have to use passive mode G FTP to access the above sites. Assuming recent/current versions of the : TCP/IP Services package, the DCL FTP command necessary is:
|
" 4 $ DIRECTORY/FTP/ANONYMOUS/PASSIVE ftp.itrc.hp.com:: |
A You can subscribe to an email notification list at the ITRC site.
> For a list of OpenVMS ECO kits recently released, you can use:
@ You can also sign up for ECO kit email notifications (Digest or . individual notifications) directly from HP at:
C Examples and ECO kit installation instructions are included in the > cover letter. For available ECO kits, cover letters and other " associated documentation, look in:
Y For additional information, please see Section 5.17.
G Do NOT attempt to install a VMSINSTAL-based OpenVMS ECO kit on OpenVMS H Alpha V7.1-2 and later. While VMSINSTAL itself remains available, it is F not 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.
[ See Section 5.30 for information on ECO kit checksums. f 5.18 How do I move the queue manager database?
0 To move the location of the queue database, the H SYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_MANAGER.QMAN$JOURNAL files, to a disk that is fast(er), has A plenty of free space, and that is not heavily used. If the queue B database 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:
|
" $ RUN SYS$SYSTEM:JBC$COMMAND JBC$COMMAND> DIAG 0 7 |
|
" $ STOP/QUEUE/MANAGER/CLUSTER |
|
" D $ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$* DISK:[DIR] |
|
" $ CREATE/DIR fast_disk:[qman] |
|
" E $ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$* fast_disk:[qman] |
|
" 7 $ DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*;* |
|
" ' $ START/QUEUE/MANAGER fast_disk:[qman] |
G "Undeleteable" jobs are usually "undeleteable" for D a reason---this can track back to insufficient process quotas, to a C kernel-mode error in OpenVMS or a third-party device driver, or to other odd problems.
E These undeletable jobs typically become of interest because they are @ holding onto a particular resource (eg: tape drive, disk drive, H communications widget) that you need to use... If the particular device G supports firmware, ensure that the device firmware is current -- TQK50 F controllers are known for this when working with old firmware. (That, F and the infamous "MUA4224" firmware bug.) If this device has a driver F ECO kit available, acquire and apply it... If the particular relevant 0 host component has an ECO, acquire and apply it.
E Useful tools include SDA (to see what might be going on) and DECamds G (which increase and thus potentially fix quota-related problems). (nb: = Applications with quota leaks will obviously not stay fixed.)
G If the stuck application is BACKUP, ensure you have the current BACKUP B ECO and are directly following the V7.1 or (better) V7.2 or later B process quota recommendations for operator BACKUP accounts. Quota < details are in the OpenVMS System Manager's Manual.
D If the firmware and ECO levels are current, the best approach is to C take a system crashdump, and pass a copy of the dump file along to = whomever is maintaining the device driver for the particular D device/widget/driver involved, with any details on how you got into D this situation. (The reboot involved with taking the crashdump will obviously clear the problem.)
E There was some kernel-mode code (typically for OpenVMS VAX) that can G reset the device ownership field, but that is rather obviously only an E interim solution---the real fix is avoiding the loss of the IRP, the E process quota leak, or whatever else is "jamming up" this particular
process... _ 5.20 How do I reset the error count(s)?
F The system reboot is the only supported approach, but it is obviously D undesirable in various situations---there is presently no supported C mechanism to reset error counts once the error(s) have been logged.
C As for an unsupported approach---and be aware of the potential for causing a system crash...
G To reset the error count, one needs to determine the system address of E the error count field. For a device, this is at an offset within the G device's UCB structure. On VAX, the field is at an offset symbolically G defined as UCB$W_ERRCNT. On Alpha, this field's offset is symbolically G defined as UCB$L_ERRCNT. The former is a word in size; the latter is a B longword. (Could it be that Alpha devices are more error prone? ;)
G You now need to locate the system address of the UCB$%_ERRCNT field of H the device you wish to reset. Enter SDA. In the following, you will see G designations in {} separated by a /. The first item in braces is to be E used on the VAX and the second item should be used on an Alpha. (ie. {VAX/Alpha})
|
" $ ANALYZE/SYSTEM 6 SDA> READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STB P SDA> SHOW DEVICE <ddnc:> ! device designation of device with error ' SDA> EVALUATE UCB+UCB${W/L}_ERRCNT : Hex = hhhhhhhh Decimal = -dddddddddd UCB+offset |
1 Record the hexadecimal value 'hhhhhhhh' returned.
H You can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I prefer to do, issue the following:
|
" " SDA> SPAWN RUN SYS$SHARE:DELTA |
C On both VAX and Alpha, the DELTA debugger will be invoked and will @ ident- ify itself. On Alpha, there will be an Alpha instruction H decoded. For those unfamiliar with DELTA, it does not have a prompt and F only one error message---Eh? (Well, for sake of argument, there might H be another error produced on the console if you're not careful---aka. a system crash!)
* If you are on a VAX, enter the command: [W
* If you are on Alpha, enter the command: [L
H These set the prevailing mode to word and longword respectively. Remem- % ber the UCB${W/L)_ERRCNT differences?
Now issue the command 1;M
DELTA will respond with 00000001
F You are now poised to ZAP the error count field. To do so you need to D en- ter the system address and view its contents. The format of the " command to do this is of the form:
|
" IPID:hhhhhhhh/ |
H For an IPID, use the IPID of the SWAPPER process. It is always: 00010001
. Thus, to ZAP the error count, you would enter:
|
" 00010001:hhhhhhhh/ |
@ When you enter the / SDA will return the content of the address H hhhhhhhh. This should be the error count (in hexadecimal) of the device G in question. If it is not, you did something wrong and I'd suggest you E type a carriage return and then enter the command EXIT to get out of 4 DELTA. Regroup and see where your session went awry.
G If you entered your address correctly and the error count was returned - as in the following example, you can proceed.
|
" K 00010001:80D9C6C8/0001 ! output on VAX 1 error |
|
" K 00010001:80D9C6C8/00000001 ! output on Alpha 1 error |
@ You can now ZAP the error count by entering a zero and typing a carriage return. For example:
|
" Q 00010001:80D9C6C8/0001 0[return] ! output on VAX 1 error |
|
" Q 00010001:80D9C6C8/00000001 0[return] ! output on Alpha 1 error |
0 Now type the command EXIT and a carriage return.
! Alternatively, reboot the system. v 5.21 How do I find out if the tape drive supports compression?
6 For various SCSI-based MK-class magnetic tape devices:
|
" 3 $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2") $ Comp_sup = %X00200000 $ Comp_ena = %X00400000 2 $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN - - WRITE SYS$OUTPUT "Compression supported" 2 $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN - + WRITE SYS$OUTPUT "Compression enabled" |
C The format of the SYSUAF.DAT, RIGHTSLIST, and associated files are G upward-compatible, and compatible across OpenVMS VAX and OpenVMS Alpha G systems. (This compatibility is a a basic requirement of mixed-version C OpenVMS Cluster configurations and OpenVMS upgrades---for specific H support information, please see the OpenVMS Cluster rolling upgrade and H mixed-version requirements.) That said, it's the contents of the SYSUAF : and RIGHTSLIST files that will make this more interesting.
F The same basic steps necessary for moving RIGHTSLIST and SYSUAF files D to another node are rather similar to the steps involved in merging D these files in an OpenVMS Cluster---see the appendix of the OpenVMS F Cluster documentation for details of merging files. (You might not be E merging the contents of two (or more) files, but you are effectively F merging the contents of the files into the target system environment.)
Considerations:
E The lattermost case---resolving the identifier values---is often the D most interesting and difficult part. If you find that an identifier D value (or identifier name) from the source RIGHTSLIST collides with D that of an identifier existing on the target system, you must first D determine if the two identifiers perform the same function. In most D cases, they will not. As such, you will have to find and chance all B references to the identifier value(s) (or name(s)) to resolve the "collision".
E If you encounter a collision, changing both of the identifier binary E values (or names) involved in the collision to new and unique values = can prevent security problems if you should miss a couple of E identifiers embedded somewhere on the target system during the whole F conversion process---rather than the wrong alphanumeric value for the H identifier being displayed, you'll simply see the binary format for the H identifier displayed, and no particular access will be granted. And any C DCL commands or such that reference the old alphanumeric name will D fail, rather than silently (and potentially erroneously) succeeding.
C Similar requirements exist for UIC values, as these too tend to be F scattered all over the system environment. Like the binary identifier F values, you will find UIC values associated with disks, ACLs, queues, and various other structures.
F For a list of the various files shared in an OpenVMS Cluster and that H can be involved when relocating an environment from one node to another B (or merging environments into an OpenVMS Cluster), please see the E SYLOGICALS.TEMPLATE file included in OpenVMS V7.2 and later releases.
D Procedures to extract the contents of a (potentially corrupt) queue F database are provided on the OpenVMS Freeware (V5) and can be used to C combine two queue databases together while shuffling files between OpenVMS Cluster hosts.
H For related discussions of splitting a cluster into two or for removing G a node from cluster (political divorce, etc), see topics (203), (767), , (915) and others in the Ask The Wizard area:
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9.
| Previous | YNext | \Contents | ^Index |