|
HP OpenVMS Systems Documentation |
|
HP OpenVMS System Management Utilities Reference Manual
SHOW QUEUE_ENTRY
Displays information about requests, or entries, queued on the local node. FormatSHOW QUEUE_ENTRY [queue-entry-id] Parameter
Qualifiers
DescriptionThe SHOW QUEUE_ENTRY command displays information about requests, or entries, queued on the local node. You can display information about a specific entry by including the queue entry ID on the command line or you can display information about all entries (the default). Use the DELETE QUEUE_ENTRY command to delete specific entries from the queue.
|
| #1 |
|---|
LATCP> SHOW QUEUE_ENTRY
|
This command produces the following type of display:
Position Entry ID Source Node Service Port Name -------- -------- ---------------- ---------------- --------- 1 79EC NODE1 LAT_LIMITED 2 7AEC NODE2 LAT_LIMITED 3 7CEC NODE3 LAT_LIMITED
| #2 |
|---|
LATCP> SHOW QUEUE_ENTRY/FULL
|
This command produces the following type of display:
Entry ID: 7AEC Remote Node: NODE1 Node Queue Position: 1 Address: 08-00-2B-0A-A0-A0 Service Queue Position: 1 Target Port: Target Service: LAT_LIMITED Soliciting Link: LAT$LINK -------------------------------------------------------------------------------- Entry ID: 7CEC Remote Node: NODE2 Node Queue Position: 2 Address: AA-00-04-00-37-DD Service Queue Position: 2 Target Port: Target Service: LAT_LIMITED Soliciting Link: LAT$LINK
Displays the status and LAT characteristics of LAT services known to the local node.
SHOW SERVICE [service-name]
service-name
Specifies the name of the service for which information will be displayed. If you do not specify a service name, LATCP displays information about all services known to the node.You can also specify any valid wildcard for this parameter. For example, the SHOW SERVICE LAT_* command displays the status and characteristics of all services that begin with the LAT_ prefix.
/BRIEF
Displays the status and identification string of the service./COUNTERS
Displays the counters kept for the service. Do not use the /BRIEF or /FULL qualifier with this qualifier. The following table lists and describes the counters:
Counter Description Remote Counters Connections attempted The total number of times the local node attempted to connect to the service offered on a remote node. Connections completed The total number of times the local node successfully connected to the service offered on a remote node. Local Counters Connections accepted The total number of times the local node accepted a connection request from a remote node to a locally offered service. Connections rejected The total number of times the local node rejected a connection request from a remote node to a locally offered service. Password failures The total number of connect requests to the service which were rejected due to password violation errors. /FULL
Displays the status, identification string, and type of service, and the values set for service characteristics. This qualifier also displays the status of all service nodes offering the service./LOCAL
Displays information about services offered by the local node only. You can use this qualifier with the /BRIEF, /COUNTERS, or /FULL qualifier.
This command displays information about services. If you do not specify a service name, the command displays information about all services known to your local node. If you do not specify a service name but specify the /LOCAL qualifier, the command displays information about all services offered by your local node.Depending on whether you use the /BRIEF, /COUNTERS, or /FULL qualifier, you can display the status, identification string, and type of service, the status of all service nodes offering the service, the values set for service characteristics, and service counters.
| #1 |
|---|
LATCP> SHOW SERVICE NODE1 /FULL
|
This command produces the following display of information about service NODE1. This service is offered by the local node.
Service Name: NODE1 Service Type: General Service Status: Available Connections: Enabled Service Password: Enabled Queueing: N/A Service Ident: NODE1 - Test system Node Name Status Rating Identification LAV On 31 D . LATP Reachable 48 . LITTN Reachable 37 . LTDRV Reachable 82 .The display in this example indicates that the locally offered service NODE1 is available and its service type is general, meaning that it is a general timesharing service (in contrast to a dedicated application service). The display also lists the status of all the nodes that offer the service. The local node is LAV. The status of the local node can be either On, Off, or Shut. Here node LAV's status is On. The status of the other nodes indicates whether they are reachable. The display lists the ratings of each service node, indicating their relative capacity to accept new connections. The D next to the locally offered service indicates that node LAV computes its rating dynamically. An S would indicate that the node's rating was set permanently by the node's system manager.
| #2 |
|---|
LATCP> SHOW SERVICE OFFICE/FULL
|
This command produces the following display of information about the service OFFICE, which is offered by a remote node:
Service Name: OFFICE Service Status: Available Service Ident: . Node Name Status Rating Identification BURGIL Reachable 121 . DARWIN Reachable 43 .The display in this example indicates that the service is available. The display also indicates the status and other information about the nodes that offer the service, BURGIL and DARWIN.
Creates a subprocess, enabling you to execute DCL commands without terminating your LATCP session. The LATCP command SPAWN is similar to the DCL command SPAWN.To return to your LATCP session, either log out of the subprocess by entering the DCL command LOGOUT, or use the DCL command ATTACH to attach your terminal to the process running LATCP.
SPAWN [DCL-command]
DCL-command
Specifies a DCL command. If you specify a DCL command, LATCP executes the command in a subprocess. Control returns to LATCP when the DCL command terminates.If you do not specify a DCL command, LATCP creates a subprocess and you can then enter DCL commands. You can continue your LATCP session by logging out of the spawned subprocess or by attaching to the parent process with the DCL command ATTACH.
The SPAWN command acts exactly like the DCL command SPAWN. You can enter DCL commands (such as to create print queues, change the protection of a device, answer mail, and so forth) without ending your LATCP session.You cannot use this command to gain access to DCL if you are running LATCP from a captive account.
LATCP> SPAWN
$
|
This command creates a subprocess at DCL level. You can now enter DCL commands. Log out or enter the DCL command ATTACH to return to the LATCP prompt.
Resets the link, node, and service counters maintained by the local node. You must have OPER privilege to use this command.
ZERO COUNTERS
None.
/LOG
/NOLOG (default)
Specifies whether LATCP displays a message confirming that the counters were reset. If you do not specify the /LOG or /NOLOG qualifier, the default is that no message will be displayed./LINK[=link-name]
Specifies the link (on your local node) for which you want counters reset. If you do not specify a link name, LATCP zeroes counters for the link LAT$LINK./NODE[=node-name]
Specifies the node for which you want counters reset. If you do not specify a node name, LATCP zeroes the counters for your local node./PORT=port-name
Specifies the port (on your local node) for which you want counters reset./SERVICE=service-name
Specifies the service (on your local node) for which you want counters reset.
This command resets counters. You can specify whether you want to reset link, node, or service counters. You must specify either /LINK, /NODE, or /SERVICE.
LATCP> ZERO COUNTERS/SERVICE=LTVM
LATCP> SHOW SERVICE LTVM /COUNTERS
Service Name: LTVM
Seconds Since Zeroed: 9
Connections Attempted: 0 Connections Accepted: 0
Connections Completed: 0 Connections Rejected: 0
Password Failures: 0
|
This command resets the counters kept for service LTVM. The display produced by the SHOW SERVICE command shows how the ZERO COUNTERS command reset the counters to zero.
14.1 LMCP Description
The Log Manager Control Program (LMCP) utility creates and manages the
transaction logs used by DECdtm services.
Some LMCP commands can corrupt data. Refer to the HP OpenVMS System Manager's Manual to understand the reasons for using LMCP and how to use it safely. |
LMCP lets you create and manage the transaction logs used by DIGITAL's distributed transaction manager, DECdtm services.
RUN SYS$SYSTEM:LMCP
None
To invoke LMCP, enter RUN SYS$SYSTEM:LMCP at the DCL command prompt. At the LMCP> prompt, you can enter any of the LMCP commands described in the following section.To exit from LMCP, enter the EXIT command at the LMCP> prompt, or press Ctrl/Z.
The following table summarizes the LMCP commands:
| Command | Description |
|---|---|
| CLOSE LOG | Closes the transaction log and stops the TP_SERVER process |
| CONVERT LOG | Creates a new transaction log and copies records from an existing transaction log to the new transaction log |
| CREATE LOG | Creates a new transaction log |
| DUMP | Displays the contents of a transaction log |
| EXIT | Exits LMCP |
| HELP | Gives help on LMCP commands |
| REPAIR | Changes the state of transactions |
| SHOW LOG | Displays information about transaction logs |
Closes the transaction log and stops the TP_SERVER process.Requires the SYSNAM privilege.
CLOSE LOG
Use the CLOSE LOG command to:
- Close the transaction log of the local node.
- Stop the TP_SERVER process on the local node.
The CLOSE LOG command fails if the node is currently executing transactions.
Creates a new transaction log and copies records from an existing transaction log to the new one.Use the CONVERT LOG command when you want to move a transaction log or change its size.
Caution
If a node already has a transaction log, using the CONVERT LOG command to create a new one can corrupt data. Refer to the HP OpenVMS System Manager's Manual for information about how to use the CONVERT LOG command safely.The CONVERT LOG command requires:
- The CMKRNL privilege
- Read access to the existing transaction log and the directory it is in
- Read and write access to the directory in which the new transaction log is to be created
CONVERT LOG old-filespec new-filespec
old-filespec
The file specification of the transaction log whose records are to be copied.The CONVERT LOG command uses the following defaults:
- If you omit the disk and directory, the CONVERT LOG command looks for the transaction log in the directories pointed to by the logical SYS$JOURNAL, which must be defined in executive mode in the system logical name table.
- If you omit the file type, the CONVERT LOG command uses .LM$JOURNAL.
new-filespec
The file specification of the new transaction log to be created.For DECdtm services to use the transaction log, the file must have a name of the form SYSTEM$node.LM$JOURNAL, where node is the name of the node.
The CONVERT LOG command uses the following defaults:
- If you omit the disk and directory, the CONVERT LOG command creates the new transaction log in the first accessible directory pointed to by the logical SYS$JOURNAL, which must be defined in executive mode in the system logical name table.
- If you omit the file type, the CONVERT LOG command uses .LM$JOURNAL.
/OWNER=uic
Specifies the owner of the new transaction log.Specify the owner using the standard UIC format, as described in the OpenVMS User's Manual.
/SIZE=size
Specifies the size of the new transaction log in blocks.The minimum size is 100 blocks. If you omit this qualifier, the new transaction log is created with the default size of 4000 blocks.
LMCP> CONVERT LOG/SIZE=6000 DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD -
_LMCP> DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL
|
This example creates a 6000-block transaction log called SYSTEM$RED.LM$JOURNAL in directory DISK$LOG2:[LOGFILES]. It then copies records from the existing transaction log, SYSTEM$RED.LM$OLD in directory DISK$LOG2:[LOGFILES], into the new transaction log.
Creates a new transaction log.
Caution
If a node already has a transaction log, using the CREATE LOG command to create a new one can corrupt data.Requires read and write access to the directory in which the transaction log is to be created.
CREATE LOG filespec
filespec
The file specification of the transaction log to be created.For DECdtm services to use the transaction log, the file must have a name of the form SYSTEM$node.LM$JOURNAL, where node is the name of the node.
The CREATE LOG command uses the following defaults:
- If you omit the disk and directory, the CREATE LOG command creates the transaction log in the first accessible directory pointed to by the logical SYS$JOURNAL, which must be defined in executive mode in the system logical name table.
- If you omit the file type, the CREATE LOG command uses .LM$JOURNAL.
If you specify a disk and directory not pointed to by SYS$JOURNAL, a warning message is displayed. However, the transaction log is still created, but will not be used until either (a) SYS$JOURNAL is modified to point to the disk and directory where the log was created, or (b) you move the new transaction log to a directory pointed to by SYS$JOURNAL.
/NEW_VERSION
Forces the CREATE LOG command to create a new version of an existing transaction log.
Caution
Creating a new version of an existing transaction log can lead to data corruption.The data in the two transaction logs cannot be merged. Once it has started using the new transaction log, DECdtm services cannot access any transaction records in the old transaction log.
/OWNER=uic
Specifies the owner of the transaction log.Specify the owner using the standard UIC format, as described in the OpenVMS User's Manual.
/SIZE=size
Specifies the size of the transaction log in blocks.The minimum size is 100 blocks. If you omit this qualifier, the transaction log is created with the default size of 4000 blocks.
LMCP> CREATE LOG/SIZE=5000 DISK$LOG1:[LOGFILES]SYSTEM$ORANGE.LM$JOURNAL
|
This example creates a 5000-block transaction log for node ORANGE in DISK$LOG1:[LOGFILES].
Displays the contents of a transaction log.Requires read access to the transaction log and the directory it is in.
DUMP filespec
filespec
The file specification of the transaction log whose contents you want to display.The DUMP command uses the following defaults:
- If you omit the disk and directory, the DUMP command looks for the transaction log in the directories pointed to by the logical SYS$JOURNAL, which must be defined in executive mode in the system logical name table.
- If you omit the file type, the DUMP command uses .LM$JOURNAL.
/ACTIVE
Selects records only for transactions that have not yet been forgotten./FORMAT (default)
Determines whether the contents of the transaction log are displayed as formatted records. Specify both the /NOFORMAT and the /HEX qualifiers to display the contents of the transaction log in hexadecimal only.
/NOFORMATIf the /NOFORMAT qualifier is specified without the /HEX qualifier, only the transaction log header is displayed.
/HEX
Specifies that the contents of the transaction log are displayed as both ASCII characters and hexadecimal longwords. Specify both the /NOFORMAT and /HEX qualifiers to display the contents of the transaction log in hexadecimal only.
/NOHEX (default)/LOGID=logid
Selects records only for transactions that have participants whose logid field matches the specified value.The logid is in the Log ID field, to the right of the Type field. The value you specify must be exactly as it appears in the display, including hyphens.
Note that you can use this qualifier only with the /RM qualifier.
/OUTPUT[=filespec]
Requires read and write access to the directory in which the output file is to be created.Specifies where the output from the DUMP command is sent. If you omit this qualifier, output is sent to the current SYS$OUTPUT device (usually your terminal). To send the output to a file, use the /OUTPUT qualifier. If you do not supply a file specification, the output is sent to the file LMCP_DUMP.LIS in your default directory.
/RM=name
Selects records only for transactions that have participants whose names begin with the specified value.The participant name is shown in the Name field, and is output in both ASCII and hexadecimal.
If the participant name includes undisplayable characters, you can select records for that participant by using the hexadecimal form of its name. When specifying the hexadecimal form of the name, you must convert it by reversing the pairs in the hexadecimal number. For example, the participant name is:
The value you specify for the /RM qualifier is:
Name (11): "SYSTEM$RED" (4445 52244D45 54535953)
/RM=%X53595354454D24524544/STATE=COMMITTED
Selects records only for transactions in either the Committed or Prepared states.
/STATE=PREPARED/TID=transaction_id
Selects records only for the specified transaction.The transaction_id is shown in the Transaction ID field. The value you specify must be exactly as it appears in the display, including hyphens.
Use the DUMP command to display the contents of a transaction log. Example 14-1 is a sample of a transaction log, with the important fields identified.
Example 14-1 Sample Transaction Log
Log Manager Control Program V1.1 Dump of transaction log DISK$LOGFILE:SYSTEM$BLUE.LM$JOURNAL;1 End of file block 4002 / Allocated 4002 Log Version 1.0 Transaction log UID: 647327A0-2674-11C9-8001-AA00040069F8 (1) Penultimate Checkpoint: 000000000239 0039 Last Checkpoint: 00000000042E 002E Dump of transaction log DISK$LOGFILE:SYSTEM$BLUE.LM$JOURNAL;1 Present Length: 134 (00000086) Last Length: 0 (00000000) VBN Offset: 0 (00000000) Virtual Block: 2 (00000002) (2) Section: 3 (00000003) Record number 1 (00000001),(3) 114 (0072) bytes (4) Transaction state (1): PREPARED (5) Transaction ID: 1D017140-2676-11C9-9F34-08002B174360 (6) (8-JUL-2002 14:08:29.14) DECdtm Services Log Format V1.1 (7) Type ( 2): CHILD (8) Log ID: F1469720-4A0C-11CC-8001-AA000400B7A5 (9) Name (13): "SYSTEM$WESTRN" (4E 52545345 57244D45 54535953) (10) Type ( 8): CHILD NODE (8) Log ID: F1469720-4A0C-11CC-8001-AA000400B7A5 (9) Name (6): "WESTRN" (4E52 54534557) (10) Type ( 3): LOCAL RM (8) Log ID: 037100C0-0019-0003-0100-000000000000 (9) Name (6): "ORANGE" (4547 4E41524F) (10)In this example, the significant fields are:
Previous Next Contents Index