Download
 Share
 Print this page
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Desktop
  5. b2600
  6. User reference

HP b2600 User Reference

Hp b2600: reference guide
Hide thumbs
  • Contents

Advertisement

Quick Links

x
Download this manual
Download this manual See also: Troubleshooting Manual, Administration Manual
System Configuration Repository
User's Reference
HP-UX/HP 9000 Computers
Edition 1.2
April 2001
Printed in: USA

Advertisement

Table of Contents
loading

  Also See for HP b2600

HP b2600 Reference Manual
HP b2600 Reference Manual 486 pages
HP b2600 Technical Reference
HP b2600 Technical Reference 206 pages
HP b2600 Administration Manual
HP b2600 Administration Manual 171 pages

  Related Manuals for HP b2600

  Summary of Contents for HP b2600

  • Page 1 System Configuration Repository User’s Reference HP-UX/HP 9000 Computers Edition 1.2 April 2001 Printed in: USA...

  • Page 2: Legal Notices

    Legal Notices The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • Page 3: Table Of Contents

    Contents 1. Introduction 2. SCR Overview Installing SCR ............. . 13 Using SCR.
  • Page 4 Contents...

  • Page 5: About This Manual

    Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive these updates or new editions, see your HP sales representative for details. April 2001…Edition 1.2. April 2000…Edition 1.1.

  • Page 6: How To Use This Guide

    Appendix A , “SCR File Set,” describes the file set for the System Configuration Repository. Comments about this manual (no technical questions, please) can be directed to: editor@fc.hp.com. Please consult your HP service and support representative for technical support questions. Thanks.

  • Page 7: Typographic Conventions

    Typographic Conventions This guide uses the following typographic conventions: Boldface Words defined for the first time appear in boldface. For example, an argument is the part of a command line that indicates what file or directory the command is to act on. Computer font indicates literal items displayed by the Computer computer.

  • Page 9: Introduction

    Introduction This manual describes the features of Hewlett Packard’s System Configuration Repository (SCR) for HP-UX and how to use them. Although powerful, SCR is simple to use, if you have a basic understanding of the HP-UX command syntax. • Chapter 2 describes how to use SCR commands to configure the program for operation.
  • Page 10 Introduction Chapter 1...

  • Page 11: Scr Overview

    SCR Overview This chapter describes SCR and how it works. Then it tells you how to install SCR and how to configure it for first use. With this information, you can be tracking system changes and viewing reports about system nodes with SCR within a short time.
  • Page 12 SCR Overview The Configuration Management component provides the scrconfig and scrstatus commands. Scrconfig maintains the configuration data collection schedule and managed node list. Scrstatus generates a status summary report of data collection activity. The Data Management component provides the scrdaemon, scrupdate, and scrdelete commands.

  • Page 13: Installing Scr

    SCR Overview Installing SCR Installing SCR SCR is part of the SCR+DMI bundle. Install SCR+DMI to use SCR. SCR can only work on system nodes that have been configured to be managed by DMI. See the DMI User’s Reference document for an explanation of DMI installation, concepts, and operations.

  • Page 14: Using Scr

    file to allow access from the CMS. The next step is to configure SCR to perform the data collection and reporting you want, as described in the next section. Description An HP-UX system that maintains Other HP-UX systems to be managed by the CMS. Chapter 2...

  • Page 15: Configuring Scr

    SCR Overview Configuring SCR Configuring SCR SCR must be configured to perform its data gathering and storing tasks. Use the scrconfig command to specify SCR tasks for each managed node. Registering Managed Nodes To begin, each managed node must be registered using the scrconfig elsa command.

  • Page 16: Setting The Data Collection Schedule

    SCR Overview Configuring SCR Setting the Data Collection Schedule The next step is to set up a day and time for the first data collection on each registered node. SCR will collect data automatically at that day and time each week. It takes a “snapshot” of the node data and stores it in the repository.

  • Page 17: Collecting Configuration Data On Demand

    SCR Overview Collecting Configuration Data On Demand Collecting Configuration Data On Demand The above steps set up automatic data collection on particular nodes at particular times. For immediate data collection, use the scrupdate command. For example, enter the following command to get a data snapshot of the managed node ortrud: # scrupdate –n ortrud You will see a message similar to the following:...

  • Page 18: Checking Data Collection Status

    SCR Overview Checking Data Collection Status Checking Data Collection Status To check data collection status of all registered nodes, use the scrsta- tus command. This provides a summary report of the last, current, and scheduled data collection for all registered nodes, in time order. # scrstatus The report, printed to stdout, resembles the following example: TIME (START –...

  • Page 19: Viewing Configuration Information On A Node

    : 04/10/1999 13:05 PDT COMPONENT NAME GROUP NAME ATTRIBUTE NAME HP Visualize Workstation “HP-UX Standard Groups Definition” “General Information” [System Name] [System Location] If we wanted data from an earlier snapshot, we would have to enter the time of the snapshot instead of the “latest” tag, or create a tag to represent that information.

  • Page 20: Tracking Configuration Changes With Scr

    SCR Overview Tracking Configuration Changes with SCR Tracking Configuration Changes with SCR Use the scrhist command to check the configuration collection history for managed nodes. This command reports a brief list with node, time and tag information. To generate a report for all system nodes, enter the following command: # scrhist This command generates a report that resembles the following...

  • Page 21: Checking Node Differences

    [BASE] elsa : 02/14/1999 12:05 PST [TARGET] elsa : 04/10/1999 13:05 PDT (latest) COMPONENT NAME GROUP NAME “HP-UX Standard Groups Definition” “Host File System” The result indicates that between the times specified, a file system, /SCR, was mounted on elsa.
  • Page 22 [BASE] ortrud:04/10/1999 13:25 PDT [TARGET] elsa:04/10/1999 13:05 PDT COMPONENT NAME GROUP NAME ATTRIBUTE NAME “HP-UX Standard Groups Definition” “Host Processor” [Host Processor Index] [Processor Firmware ID The result highlights the processor difference. ortrud is a PA 1.1 single processor model, and elsa is a PA 2.0 multi processor model.

  • Page 23: Using Tags To Simplify Node Management

    Using Tags to Simplify Node Management As you have already noticed, configuration designations are long. It is tedious to type them over and over, and it can be easy to mistype them. SCR allows you to replace a configuration designation with an easy to use tag.
  • Page 24 SCR Overview Using Tags to Simplify Node Management In the future, you can use the StandardConfig tag instead of typing the date and time in commands. Tags can be modified or deleted using options with scrtag. For example, to move the tag, StandardConfig, for node elsa to the next snapshot (now labeled “latest”), enter the following command: # scrtag –m elsa StandardConfig 199904181305...

  • Page 25: Using Filters

    Using Filters Component information collected by SCR might include information you do not want to see. With scrfilter, you can create a view or display filter to limit the information SCR shows you or prints. While the scrfilter command generally does not change what information is collected (only limiting the information you see or print), the probe filter (see “Using the Probe Filter”...

  • Page 26: Simple Filter Example

    SCR Overview Using Filters Simple Filter Example For example, suppose the “HP-UX Installed Software Definition” component is not interesting to you all the time. The following example shows the information that scrviewer reports by default for the HP-UX Installed Software Definition component.
  • Page 27 HP-UX Installed Software component is excluded from the report. You will see none of the information shown in the example. Suppose you only wanted to filter out a group from the HP-UX Installed Software Definition component and not the entire component. You could filter the Subproducts group from the report with the following...

  • Page 28: Standard Filters

    SCR Overview Using Filters Standard Filters SCR comes with nine standard view/display filters that HP has defined for specific components. They are: • Disk • FileSystem • LVM • Network • Probe (special, see “Using the Probe Filter” on page 29) •...

  • Page 29: Using The Probe Filter

    Using the Probe Filter The Probe filter determines what information is collected from DMI components, groups, and attributes. The Probe filter determines what is stored in the SCR Repository. You can set Probe filter extension flags to collect (on) or not collect (off) specific information from the nodes, or to collect or not collect from newly detected components, groups, or attributes.

  • Page 30: Additional Uses Of Scr

    SCR Overview Additional Uses of SCR Additional Uses of SCR With the above procedures, you have configured SCR to begin collecting and reporting node data. You can further customize SCR’s powerful commands using the information available in Chapter 3 and the man pages.

  • Page 31: Change Management

    Change Management SCR can complement your system change management process by keeping good records of changes and alerting you to unplanned changes. • You can configure SCR to automatically take periodic snapshots. • You can take snapshots whenever you want them. •...

  • Page 32: Disaster Recovery

    SCR Overview Additional Uses of SCR Disaster Recovery SCR can also help with disaster recovery by showing you a comparison of the system state before and after recovery. To make disaster recovery most effective, set scrconfig to collect data weekly or more often, as described in step 3 above.

  • Page 33: Scr Reference (Man Pages)

    SCR Reference (man Pages) The System Configuration Repository extracts snapshots of a systems configuration by request and/or schedule and stores it as a record in the SCR persistent repository. The SCR is described in: scr(5) - System Configuration Repository: page 34. •...

  • Page 34: Scr (5)

    Configuration snapshots will include all relevant configuration information covered by HP-UX System Management Information Format (MIF) and HP Software MIF. SCR consists of seven components: Configuration Management, Data Management, Filter Management, Tag Management, Presentation, Repository and Log.
  • Page 35 filter the log file by the creation time of the log entry and by the level of detail. Dependencies Between Software managed nodes The Desktop Management Interface for HP-UX management server The Desktop Management Interface for HP-UX Reference activities in a graphical user interface (see samlog_viewer (1M)).
  • Page 36 SCR Reference (man Pages) scr (5) - EXAMPLES EXAMPLES SCR Configuration Register the management server on managed nodes. • The system administrator adds the management server name to the /var/dmi/dmiMachines file on each managed node to allow access from management server. Register a managed node on the management server.
  • Page 37 Data expiration and data collection timeout parameters can be • customized with the -e and -t options. See the scrconfig (1M) manual page for details. Collecting Configuration Data into SCR For scheduled data collection, no further action is required. A •...
  • Page 38 [BASE] node2 : 02/14/1999 12:05 PST [TARGET] node2 : 04/10/1999 13:05 PDT (latest) No filter applied. COMPONENT NAME GROUP NAME ATTRIBUTE NAME "HP-UX Standard Groups Definition" "Host File System" [Host File System Index] [Mount Point] node4:/SCR [Remote Mount Point] [File System Type]...
  • Page 39 [BASE] node1 : 04/10/1999 13:25 PDT (latest) [TARGET] node2 : 04/10/1999 13:05 PDT (latest) No filter applied. COMPONENT NAME GROUP NAME ATTRIBUTE NAME "HP-UX Standard Groups Definition" "Host Processor" [Host Processor Index] [Processor Firmware ID] PA RISC2.0" [Processor Load] [Host Processor Index] [Processor Firmware ID] PA RISC2.0"...
  • Page 40 MIFs, a filter's extension flag can be set to on (visible) or off (masked). For example, suppose the software configuration data is not needed, the HP-UX Installed Software Definition component can be latest and oldest snapshot for each node. These tags are managed by the system and updated whenever data is collected or removed.
  • Page 41 Create a view filter named filter1. # scrfilter -c Template filter1 Set the mask for the component with # scrfilter -s filter1 "HP-UX Installed Software Definition" off Use the filter1 filter with the scrviewer command to successfully exclude the HP-UX Installed Software Definition component.
  • Page 42 SCR Reference (man Pages) scr (5) - FILES Similarly, the DNS Configuration group of HP-UX Standard Groups Definition component can be masked off with the command: # scrfilter -s filter1 "HP-UX Standard Groups Definition" "DNS Configuration" off FILES /opt/scr/bin Contains SCR executable files.

  • Page 43: Scrconfig (1M)

    scrconfig (1M) NAME scrconfig – configure and query configuration parameters of SCR SYNOPSIS /opt/scr/bin/scrconfig [-f outfile ] /opt/scr/bin/scrconfig -l [-n node ] [-f outfile ] /opt/scr/bin/scrconfig -d [-f outfile ] /opt/scr/bin/scrconfig -n [{+ |- } node ... ] [-f outfile ] /opt/scr/bin/scrconfig -s [ schedule_time | off] [-n node ] [-f outfile ] /opt/scr/bin/scrconfig -i [ interval | off] [-n node ] [-f...
  • Page 44 SCR Reference (man Pages) scrconfig (1M) - Options range 1 to 99 with a suffix of y(ear) or m(onth) or the format of expiration is a numeric value in the range 1 to 14 with a suffix of w(eek). The initial value is 3m (three months).
  • Page 45 -t [ timeout | off] If timeout is not specified, list the default data Formats If configuration parameters or managed nodes are modified, some of the following messages are output. " node " is registered as a managed node. Default parameters are applied: Schedule time: Interval: Expiration period:...
  • Page 46 SCR Reference (man Pages) scrconfig (1M) - RETURN VALUE RETURN VALUE Upon completion, scrconfig returns one of the following exit values: EXAMPLES List Managed Nodes and Parameters View current parameters: # scrconfig -l NODE TIMEOUT node1 5 minutes node3 10 minutes List Managed Nodes View the managed node list: # scrconfig -n...
  • Page 47 Set Data Collection Interval Time Set the interval time for node1 to one week: # scrconfig -n node1 -i 1w Stop Data Collection Schedule Stop monitoring activity for node2: # scrconfig -n node2 -s off NOTE Default parameters are effective only for managed nodes registered after the default value is set or modified.

  • Page 48: Scrdelete (1M)

    SCR Reference (man Pages) scrdelete (1M) - DESCRIPTION scrdelete (1M) NAME scrdelete – remove SCR configuration information from the database SYNOPSIS /opt/scr/bin/scrdelete {-a | -n node } [ -f] [-p time1 [ time2 ]] DESCRIPTION scrdelete removes specified configuration information from the System Configuration Repository.
  • Page 49 EXTERNAL INFLUENCE Environment Variable RETURN VALUE Upon completion, scrdelete returns with one of the following exit values: FILES /var/opt/scr/log/scrlog.log Contains data removal log. SEE ALSO scrconfig (1M), scrtag (1M), scrupdate (1M), scr (5). Reference scrdelete (1M) - EXTERNAL INFLUENCE TZ determines the conversion between the system time in UTC and the time in the user's local time zone.

  • Page 50: Scrdiff (1M)

    SCR Reference (man Pages) scrdiff (1M) - DESCRIPTION scrdiff (1M) NAME scrdiff – list differences between data in SCR configuration snapshots SYNOPSIS /opt/scr/bin/scrdiff [-a] [-f filter ] base_node:base_time target_node:target_time DESCRIPTION scrdiff lists configuration snapshot differences between two nodes at two times: base_node configuration at base_time and target_node configuration at target_time , or in one node at two times.
  • Page 51 [BASE] base_node : MM/DD/YYYY hh:mm tz ( tag_name ) [TARGET] target_node : MM/DD/YYYY hh:mm tz ( tag_name ) ATTRIBUTE NAME m component_name m group_name m attribute_name If only attributes differ, the component_name , and group_name of the attributes are printed out without BASE or TARGET fields. In case of table group, attribute_name is displayed with bracket([]), and a null line is inserted between rows.
  • Page 52 # scrdiff node1:199904231200 node2:latest [BASE] node1 : 04/22/1999 20:52 PDT [TARGET] node2 : 04/23/1999 10:15 PDT (latest) No filter applied. COMPONENT NAME GROUP NAME ATTRIBUTE NAME "HP-UX Standard Groups Definition" "General Information" "System Name" "System Location" FILES /var/opt/scr/log/scrlog.log Contains execution log. SEE ALSO scrfilter (1M), scrtag (1M), scrupdate (1M), scr (5).

  • Page 53: Scrfilter (1M)

    scrfilter (1M) NAME scrfilter – list, set, create, modify, and delete SCR view and collection filters SYNOPSIS /opt/scr/bin/scrfilter [ -l [ filter [ component [ group [ attribute ]]]]] /opt/scr/bin/scrfilter -s filter [ component [ group [ attribute ]]] { on|off} /opt/scr/bin/scrfilter -S filter component group attribute { pattern |reset} /opt/scr/bin/scrfilter -c filter new_filter...
  • Page 54 SCR Reference (man Pages) scrfilter (1M) - Options Options -c filter new_filter Copy filter to new_filter . -d filter -i file -l [ filter [ component [ group [ attribute ]]]] List registered filter -m filter new_filter Rename filter to new_filter . -o filter file Generate filter file from specified filter .
  • Page 55 -u filter Formats The filter name list generated by the scrfilter command without options or with the -l option has the following format: filter_name1 filter_name2 The filter settings list generated with the -l option specified has the following format: Reference search condition is reset.
  • Page 56 SCR Reference (man Pages) scrfilter (1M) - Formats Attribute: attribute2 Where flag above is either on or off. Where option above can be NewlyDetected, if the component , group , or attribute is detected using -u option. If a pattern is set to an attribute in repository, scrfilter prints the pattern in the option field for the attribute and keyword Conditional in the same field for the group .
  • Page 57 to be followed by a blank line. The flag and pattern fields can be modified to customize a filter using -i option. scrfilter outputs the following messages. Filter " original_name " copied to " name ". Filter " name " removed.
  • Page 58 SCR Reference (man Pages) scrfilter (1M) - RETURN VALUE Component: component1 Group: group1 Attribute: attribute2 Search condition for the filter " name " is reset to the following information: Component: component1 Group: group1 Attribute: attribute2 File " file " applied to filter "...
  • Page 59 NOTE System Configuration Repository provides nine default filters, the collection filter, the template view filter and seven other pre-defined view filters. User-defined view filters can be created by copying the template or another view filter and modifying it. Filter names must be alphanumeric without white space or tabulation.
  • Page 60 SCR Reference (man Pages) scrfilter (1M) - EXAMPLES View or collection flag for new data detected by update ( -u) option is set by the following rules: If extension flag is on, all flags for new data are set on. •...
  • Page 61 Newly detected information is displayed by this filter. # scrfilter -s myFilter on Set or Reset Filter for Specific Information Exclude HP-UX Installed Software Definition component, and include HP-UX Standard Groups Definition component for filter myFilter. # scrfilter -s myFilter "HP-UX Installed Software Definition" off # scrfilter -s myFilter "HP-UX Standard Groups Definition"...
  • Page 62 [Device Description] [Device ID] [Device Status] [Device Errors] Reset search condition. # scrfilter -S DiskDevice "HP-UX Standard Groups Definition" \\\ "Host Device" "Device Type" reset Modify filter setting using filter file Generate filter file SettingFile from filter myFilter. # scrfilter -o myFilter SettingFile Edit view flags of groups in filter file SettingFile using vi.
  • Page 63 Apply the new setting from filter file SettingFile to filter myFilter. # scrfilter -i SettingFile FILES /var/opt/scr/log/scrlog.log Contains filter creation, deletion, and SEE ALSO scrdiff (1M), scrupdate (1M), scrviewer (1M), scr (5). Reference modification log. SCR Reference (man Pages) scrfilter (1M) - FILES...

  • Page 64: Scrhist (1M)

    SCR Reference (man Pages) scrhist (1M) - DESCRIPTION scrhist (1M) NAME scrhist – list existing SCR snapshots SYNOPSIS /opt/scr/bin/scrhist [-n node ... ] [-p start_time DESCRIPTION scrhist lists snapshots for target nodes in a given period of time. Target nodes can be specified by -n option and period of time is specified by -p option.
  • Page 65 EXTERNAL INFLUENCE Environment Variable RETURN VALUE Upon completion, scrhist returns with one of the following exit values: EXAMPLES # scrhist -n node1 node2 -p 19980101 latest NODE node1 latest node2 FILES /var/opt/scr/log/scrlog.log Contains execution log. SEE ALSO scrtag (1M), scr (5). Reference scrhist (1M) - EXTERNAL INFLUENCE TZ determines the conversion between the system time...

  • Page 66: Scrstatus (1M)

    SCR Reference (man Pages) scrstatus (1M) - DESCRIPTION scrstatus (1M) NAME scrstatus – list status of SCR data collection SYNOPSIS /opt/scr/bin/scrstatus /opt/scr/bin/scrstatus -a [-n node ] /opt/scr/bin/scrstatus -r [-n node ] DESCRIPTION scrstatus generates a status report of configuration data collection by scrupdate.
  • Page 67 TIME MM / DD / YYYY status is either Completed (without error), Warning (Partial error reported), Error (Full error), Executing (now executing), or Scheduled (in future). detail is displayed only if status field is either Warning or Error. The fifth column, detail indicates encountered errors with three values: Tmout (Timeout), AcErr (Access error), and RtErr (Runtime error).
  • Page 68 SCR Reference (man Pages) scrstatus (1M) - RETURN VALUE RETURN VALUE Upon completion, scrstatus returns with one of the following exit values: EXAMPLES List Status Summary List status information # scrstatus TIME 04/10/1998 00:05 - 00:09 PDT 04/10/1998 00:20 - 00:23 PDT AcErr 04/11/1998 00:05 - 04/11/1998 00:20 -...

  • Page 69: Scrtag (1M)

    scrtag (1M) NAME scrtag – list, create, modify, and delete SCR tag names SYNOPSIS /opt/scr/bin/scrtag /opt/scr/bin/scrtag -l node tag /opt/scr/bin/scrtag -r node time /opt/scr/bin/scrtag -a node tag time /opt/scr/bin/scrtag -m node tag time /opt/scr/bin/scrtag -d node tag DESCRIPTION scrtag provides reference and management interface of SCR tags. The tag is an alias for a configuration snapshot.
  • Page 70 SCR Reference (man Pages) scrtag (1M) - EXTERNAL INFLUENCE With the -l or -r option, scrtag outputs converted time or tag: YYYYMMDDhhmm tag_name With the -a, -m or -d option, scrtag outputs the following messages on successful termination: EXTERNAL INFLUENCE Environment Variable RETURN VALUE Upon completion, scrtag returns with one of the following exit values:...
  • Page 71 EXAMPLES List All Tags List all registered tags # scrtag NODE node1 node2 Display Time Associated with Tag Display the time associated with tag Stable for node node1. # scrtag -l node1 Stable 199901310025 Set tag Set tag Standard for node node1 to Feb 7 13:00, 1999: # scrtag -a node1 Standard 199902071300 Remove Tag Remove the tag Standard for node node1:...

  • Page 72: Scrupdate (1M)

    SCR Reference (man Pages) scrupdate (1M) - DESCRIPTION scrupdate (1M) NAME scrupdate – update SCR contents SYNOPSIS /opt/scr/bin/scrupdate [-t name ] {-a | -n node } DESCRIPTION scrupdate collects system configuration information on registered managed nodes through DMI. scrupdate compares newly collected information with the most recently collected information.
  • Page 73 Reason_code may be one or a combination of Timeout, AccessError, or RuntimeError. RETURN VALUE Upon completion, scrupdate returns with one of the following exit values: EXAMPLES Collect configuration information for node node1. # scrupdate -n node1 Configuration data for "node1:199904101205" collected. Data registered in the repository.

  • Page 74: Scrviewer (1M)

    SCR Reference (man Pages) scrviewer (1M) - DESCRIPTION scrviewer (1M) NAME scrviewer – view SCR configuration information SYNOPSIS /opt/scr/bin/scrviewer [-f filter ] node:time DESCRIPTION scrviewer displays configuration information on the specified node at the specified time . node is the hostname of the desired node. The time format is YYYYMMDD [ hh [ mm ]], or the keyword oldest, latest, or a user defined tag name registered through scrtag.
  • Page 75 PDT. # scrviewer node1:199806231200 node1 : 06/23/1998 12:00 PDT (Stable) No filter applied. COMPONENT NAME GROUP NAME ATTRIBUTE NAME "HP-UX Standard Groups Definition" "DNS Configuration" "Domain Name" Search "Server IP Address(es)" Reference TZ determines the conversion between the system time in UTC and the time in the user's local time zone.
  • Page 76 SCR Reference (man Pages) scrviewer (1M) - FILES FILES /var/opt/scr/log/scrlog.log Contains execution log. SEE ALSO scrfilter (1M), scrtag (1M), scr (5). Reference...

  • Page 77: Scrlog_Viewer (1M)

    Includes Summary level of detail, and adds detail log entries. If no level of detail is specified this is the default. executed. These commands may include HP-UX commands as well as SCR commands. SCR Reference (man Pages) scrlog_viewer (1M) - DESCRIPTION...
  • Page 78 SCR Reference (man Pages) scrlog_viewer (1M) - Options The component filters control the component to be displayed. The component filters are: Configuration scrconfig (1M), scrstatus (1M) Data Management scrupdate (1M), scrdelete (1M) Filter Management scrfilter (1M) Tag Management scrtag (1M) Presentation scrhist (1M), scrdiff (1M) and scrviewer (1M) Repository Other...
  • Page 79 If no start time is given, the beginning of the log is used as the start time. -e MMDDhhmm [[ CC ] YY ] filter to the date/time given by its argument. The date/time is specified as described for the -s option. If no end time is given, then an end date/time of infinity (no end time) is used.
  • Page 80 SCR Reference (man Pages) scrlog_viewer (1M) - EXAMPLES file EXAMPLES Capture the current contents of the SCR logfile using default filtering, and put into the file scr.out: scrlog_viewer -n > scr.out The following example does the same thing: scrlog_viewer -o scr.out View only the commands executed between 8am June 5, 1999 and 10pm August 14, 1999: scrlog_viewer -s 0605080099 -e 0814220099 -lC...
  • Page 81 SCR Reference (man Pages) scrlog_viewer (1M) - SEE ALSO SEE ALSO scrconfig (1M), scrdelete (1M), scrdiff (1M), scrfilter (1M), scrhist (1M), scrstatus (1M), scrtag (1M), scrupdate (1M), scrviewer (1M), scr (5). Reference...
  • Page 82 SCR Reference (man Pages) scrlog_viewer (1M) - SEE ALSO Reference...

  • Page 83: Scr File Set

    SCR File Set This Appendix tells you how to get information on SCR file sets. SCR is comprised of three filesets: SCR-RUN, SCR-MAN, and SCR-MX. If more information regarding the fileset contents and their attributes is needed, then the following command can be executed: /usr/sbin/swlist -v -l file SCR.SCR-RUN SCR.SCR-MAN \ SCR.SCR-MX This command will display the directories and files for each fileset, and...
  • Page 84 SCR File Set Appendix A...

This manual is also suitable for:

J6700J6750Visualize b1000Visualize b132lVisualize b160lVisualize b180l ... Show all