HP Archive Backup System for OpenVMS Guide to Operations
Share Embed Flag
Download ePaper

HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

Troubleshooting 12.2 Media Management 12.1.6 Volume Set Locking and Coordinator Cleanup Process 12.2Media Management 12.2.1 Log Files 12.2.2 OPCOM Each volume set used by ABS has a corresponding volume set record. This record is contained in the MDMS volume database and is named “&+XXXXXX” where the x’s represent the volume set name. You may view this record by issuing either of the commands $ MDMS SHOW VOLUME “&+XXXXXX” $ MDMS SHOW VOLUME/ABS_VOLSET xxxxxx The description field in the record represents the locks on the volume. If it is all zeroes (0), then the record is not locked by a request. If there are one(s) (1) in the field, then the record is locked by one or more requests. The allocation field is used by ABS while setting and clearing the locks. If it is allocated, ABS is in the processing of locking or unlocking the record. If the record is locked a second request attempting the use the volume set will wait for it to be unlocked. In cases where a request fails and the record does not get unlocked, the second request could wait forever. There is a process called ABS$COORD_CLEAN which must be running at all times. This process keeps track of the requests and which volume sets they are using. If a request fails this process will unlock the volume set record so that it is available to other requests. The coordinator cleanup process logs its activities by OPCOM messages and in a log file called ABS$LOG:ABS$COORD_CLEANUP.LOG. This log generally does not contain much information. If you are finding that volume set records are not getting unlocked and want to be sure that the coordinator cleanup process is working, you may define a logical name $ DEFINE/SYSTEM EPCOT_COORD_CLEANUP_DEBUG TRUE This will cause more information to be logged to the log file. To manually unlock the volume set record you may issue the command $ MDMS SET VOLUME “&+XXXXXX”/DESCRIPTION=”000000000000000000000000000000” There are 32 zeroes in the string. You may also set the volume set record to /STATE=FREE. It is not advised to use these commands unless you are sure that the volume set is not in use by another request. The MDMS$SERVER process writes to a log file called MDMS$LOG:MDMS$LOGFILE__.LOG when it is not an active database server, and a file called MDMS$LOG:MDMS$LOGFILE_DBSERVER.LOG when it is an active database server. These files contains information about MDMS requests which have been executed, other MDMS activities, and errors. The amount of information is controlled by a logical name MDMS$LOGFILTER. This logical is defined in SYS$STARTUP:MDMS$SYSTARTUP.COM. There are bitmask values called LT_xxxx in the command procedure If you wish to turn on more logging you may set the value to these bitmask symbols OR’d together. See the command procedure for more information. When MDMS requires user intervention, such as making a tape available to a jukebox, an OPCOM message will be generated. The OPCOM messages are sent to the TAPE operator class by default. You may set another operator class in the MDMS domain by using the $ MDMS SET DOMAIN/OPCOM_CLASS = opcom_class 12-2 Troubleshooting

12.2.3 MDMS Requests Troubleshooting 12.2 Media Management A list of supported classes is available in MDMS HELP or in the MDMS Reference Manual. To enable OPCOM on a terminal so that you may see and reply to the messages, type $ SET REPLY/ENABLE=opcom_class To disable OPCOM, type $ REPLY/DISABLE Operator privilege is required in order to enable OPCOM. These message are particularly useful when an ABS save or restore request is hung waiting for volume. If MDMS is having difficulty obtaining or loading a volume the OPCOM message may be helpful in determining the problem. Whenever an MDMS request is issued, you may view them using the command $ MDMS SHOW REQUESTS Or, you may view the requests by selecting the request tab in MDMSView GUI. If a request is stalled for some reason you may be able to determine the problem by viewing the request. It is also useful to look in the MDMS$LOGFILE__.LOG or MDMS$LOGFILE_DBSERVER.LOG files. The following table provides the various state values under MDMS SHOW REQUEST/FULL. Comp DCSC Comp MRD Comp Object Comp OPCOM Comp RDF Comp System Comp Timer- Completed Starting Wait DCSC Wait Domain Wait Drive Wait Group Wait Jukebox Wait Location Wait MRD Completed DCSC request Completed MRD request Completed lock information request for Object Completed OPCOM request display Completed RDF operation Completed the operation to be performed by system like allocate drive etc. Completed the time period of time Particularly for repetion of some requests Completed the request Started the processing of the request The DCSC is being queried and hence wait on the same Wait on domain Wait on drive Wait on group Wait on Juke Wait on Location Wait on MRD response Troubleshooting 12–3

12.2.3 MDMS Requests<br />

Troubleshooting<br />

12.2 Media Management<br />

A list of supported classes is available in MDMS HELP or in the MDMS Reference Manual.<br />

To enable OPCOM on a terminal so that you may see and reply <strong>to</strong> the messages, type<br />

$ SET REPLY/ENABLE=opcom_class<br />

To disable OPCOM, type<br />

$ REPLY/DISABLE<br />

Opera<strong>to</strong>r privilege is required in order <strong>to</strong> enable OPCOM.<br />

These message are particularly useful when an ABS save or res<strong>to</strong>re request is hung waiting <strong>for</strong><br />

volume. If MDMS is having difficulty obtaining or loading a volume the OPCOM message may<br />

be helpful in determining the problem.<br />

Whenever an MDMS request is issued, you may view them using the command<br />

$ MDMS SHOW REQUESTS<br />

Or, you may view the requests by selecting the request tab in MDMSView GUI.<br />

If a request is stalled <strong>for</strong> some reason you may be able <strong>to</strong> determine the problem by viewing the<br />

request. It is also useful <strong>to</strong> look in the MDMS$LOGFILE__.LOG or<br />

MDMS$LOGFILE_DBSERVER.LOG files.<br />

The following table provides the various state values under MDMS SHOW REQUEST/FULL.<br />

Comp DCSC<br />

Comp MRD<br />

Comp Object<br />

Comp OPCOM<br />

Comp RDF<br />

Comp <strong>System</strong><br />

Comp Timer-<br />

Completed<br />

Starting<br />

Wait DCSC<br />

Wait Domain<br />

Wait Drive<br />

Wait Group<br />

Wait Jukebox<br />

Wait Location<br />

Wait MRD<br />

Completed DCSC request<br />

Completed MRD request<br />

Completed lock in<strong>for</strong>mation request <strong>for</strong> Object<br />

Completed OPCOM request display<br />

Completed RDF operation<br />

Completed the operation <strong>to</strong> be per<strong>for</strong>med by system like allocate<br />

drive etc.<br />

Completed the time period of time Particularly <strong>for</strong> repetion of some<br />

requests<br />

Completed the request<br />

Started the processing of the request<br />

The DCSC is being queried and hence wait on the same<br />

Wait on domain<br />

Wait on drive<br />

Wait on group<br />

Wait on Juke<br />

Wait on Location<br />

Wait on MRD response<br />

Troubleshooting 12–3

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!