DOCSLIB.ORG

Command-Line Interface User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Command-Line Interface User's Guide Storage Productivity Center for Replication for System z Version 4.2.2.1 Command-line Interface User's Guide SC27-2323-06 Storage Productivity Center for Replication for System z Version 4.2.2.1 Command-line Interface User's Guide SC27-2323-06 Note Before using this information and the product it supports, read the information in “Notices” on page 133. This edition applies to version 4, release 2, modification 2, fix pack 1 of IBM Tivoli Storage Productivity Center for Replication for System z (product number 5698-B30 and 5698-B31) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC27-2323-05. © Copyright IBM Corporation 2005, 2011. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ...............v lslss .................55 lsmc .................57 Tables ...............vii lspair ................59 lsparameter ..............63 lspath ................65 About this guide ...........ix lspool ................67 Intended audience ............ix lsrolepairs ...............70 Command-line interface conventions ......ix lsrolescpset ..............73 Presentation of command information ....ix lssess ................75 Command entry ............xi lssessactions ..............78 Command modes ...........xii lssessdetails ..............80 User assistance for commands .......xiv lssnapgrp ...............82 Output from command processing .....xv lssnapgrpactions.............85 Accessing the IBM Tivoli Storage Productivity lssnapshots ..............87 Center for Replication Information Center ....xix lssnmp ................89 Publications and related information for IBM Tivoli lsstorcandidate .............90 Storage Productivity Center for Replication for lsvol .................92 System z publications...........xix mkauth ................95 Web resources .............xxi mkbackup ...............97 Providing feedback about publications .....xxii mkcpset ...............98 mklogpkg ..............100 Chapter 1. Customizing the mkpath ...............100 command-line interface ........1 mksess ...............101 Configuring the command-line interface .....1 mksnmp ...............105 Setting up automatic login to the CLI ......1 refreshdevice .............106 rmactive ...............106 Chapter 2. csmcli command rmassoc ...............107 descriptions .............3 rmauth ...............108 rmcpset ...............109 adddevice ...............7 rmdevice ...............110 addhost ................9 rmhost................111 addmc ................9 rmmc ................112 addstorsys...............10 rmpath ...............113 chauth ................11 rmsess................114 chdevice ...............13 rmsnmp ...............114 chhost ................14 rmstdby ...............115 chlocation ...............15 rmstorsys...............116 chmc ................16 setasstdby ..............117 chsess ................17 setparameter..............118 chvol ................25 setstdby ...............118 cmdsess ...............26 showcpset ..............119 cmdsnapgrp ..............28 showdevice ..............120 exportcsv ...............32 showgmdetails .............124 hareconnect ..............33 showha ...............126 hatakeover ..............34 showmc ...............127 importcsv ...............35 showsess ...............128 lsauth ................37 ver.................131 lsavailports ..............38 whoami ...............132 lscpset ................40 lscptypes ...............42 Notices ..............133 lsdevice................45 lshaservers ..............49 Trademarks ..............135 lshost ................51 lslocation ...............53 Index ...............137 © Copyright IBM Corp. 2005, 2011 iii iv Command-line Interface User's Guide Figures © Copyright IBM Corp. 2005, 2011 v vi Command-line Interface User's Guide Tables 1. Exit codes for CLI commands ......xvi © Copyright IBM Corp. 2005, 2011 vii viii Command-line Interface User's Guide About this guide This section briefly describes the content and the audience of this publication and explains how the information in this publication is organized. This guide provides definitions, syntax, and examples for these command-line interface (CLI) commands that are used for the varieties of IBM® Tivoli® Storage Productivity Center for Replication: v IBM Tivoli Storage Productivity Center for Replication Two Site Business Continuity v IBM Tivoli Storage Productivity Center for Replication Three Site Business Continuity v IBM Tivoli Storage Productivity Center for Replication Basic Edition for System z® v IBM Tivoli Storage Productivity Center for Replication for System z IBM Tivoli Storage Productivity Center for Replication is supported on the following platforms: v AIX® V5.3 ML3 and AIX 6.1 v Red Hat Enterprise Linux 4 Update and Red Hat Enterprise Linux 5 AS v Windows Datacenter Edition and Windows 2003 Enterprise Edition v Windows Server 2008 Standard Edition and Windows Server 2008 Enterprise Edition v z/OS® V1.9 or later Intended audience This publication is intended for users of the CLI program for IBM Tivoli Storage Productivity Center for Replication. Command-line interface conventions This topic provides information about using the CLI program for IBM Tivoli Storage Productivity Center for Replication. It includes information about command conventions and modes, command format requirements, and other usage information. Presentation of command information This topic describes how information is presented in the command descriptions. A syntax diagram uses symbols to represent the elements of a command and to specify the rules for using these elements. A keyword represents the name of a command, flag, parameter, or argument. Required key words indicate the parameters or arguments that must be specified for the command. Syntax diagrams conventions To read syntax diagrams, follow the path of the line. Read the diagrams from left-to-right, top-to-bottom, following the main path line: © Copyright IBM Corp. 2005, 2011 ix v Required keywords are displayed on the main path line. Mutually exclusive required keywords are stacked vertically. Optional key words indicate the parameters or arguments you can choose to specify for the command. Optional keywords appear below the main path line. Mutually exclusive optional keywords are stacked vertically. v The main path line begins on the left with double arrowheads (>>) and ends on the right with two arrowheads facing each other (><). If a diagram is longer than one line, each line to be continued ends with a single arrowhead (>) and the next line begins with a single arrowhead. The -->< symbol indicates the end of the syntax diagram. v A dash (-) indicates that you must supply parameters from the stdin file rather than entering parameters. v An arrow returning to the left means you can repeat the item. A character or space within the arrow means you must separate repeated items with that character or space. v A stack of items followed by an arrow returning to the left means that you can select more than one item or, in some cases, repeat a single item. v When a group of parameters is lengthy or a section is used more than once in a command, it is shown as a separate fragment following the main diagram. Syntax diagrams use position to indicate required, optional, and default values for keywords, variables, and operands: v If an element is shown on the line, the element is required. If an element is shown below the line, the element is optional. If an element is shown above the line, the element is the default. v If an operand has a default value, the operand is shown both above and below the main line. A value below the main line indicates that the operand must be specified. You must specify the default value or one of the other valid values that are shown. If an operand is not specified, the default value above the main line is used. v When one or more items are shown below the main line, all of the items are optional. Command emphasis The following typefaces are used to show command emphasis: boldface Text in boldface represents command names. italics Text in italics is used for variables for which you supply actual values, such as a default directory or the name of a cluster. monospace Text in monospace identifies the data or commands that you type, samples of command output, examples of program code or messages from the system, or names of command flags, parameters, arguments, and name-value pairs. Special characters The following special characters are used in the command descriptions: minus sign (-) Flags are prefixed with a minus sign (-). Flags define the action of a command or modify the operation of a command. You can use multiple x Command-line Interface User's Guide flags, followed by parameters, when you issue a command. This character cannot be used as the first character of an object name. vertical bar ( |) A vertical bar signifies that you choose only one value. For example, [a|b]indicates that you can choose a, b, or nothing. Similarly, {a|b}indicates that you must choose either a or b. quotation marks (" ") Quotation marks around a string indicate that the value can include spaces, for example, "my session name." brackets ([ ]) Brackets indicate optional options, parameters, and arguments. braces ({ }) Braces indicate a required choice between two or more options or arguments. ellipsis (...) Ellipses indicate repetition or multiple values or arguments. Command entry This
Load more

Recommended publications
  • A First Course to Openfoam
    Basic Shell Scripting Slides from Wei Feinstein HPC User Services LSU HPC & LON [email protected] September 2018 Outline • Introduction to Linux Shell • Shell Scripting Basics • Variables/Special Characters • Arithmetic Operations • Arrays • Beyond Basic Shell Scripting – Flow Control – Functions • Advanced Text Processing Commands (grep, sed, awk) Basic Shell Scripting 2 Linux System Architecture Basic Shell Scripting 3 Linux Shell What is a Shell ▪ An application running on top of the kernel and provides a command line interface to the system ▪ Process user’s commands, gather input from user and execute programs ▪ Types of shell with varied features o sh o csh o ksh o bash o tcsh Basic Shell Scripting 4 Shell Comparison Software sh csh ksh bash tcsh Programming language y y y y y Shell variables y y y y y Command alias n y y y y Command history n y y y y Filename autocompletion n y* y* y y Command line editing n n y* y y Job control n y y y y *: not by default http://www.cis.rit.edu/class/simg211/unixintro/Shell.html Basic Shell Scripting 5 What can you do with a shell? ▪ Check the current shell ▪ echo $SHELL ▪ List available shells on the system ▪ cat /etc/shells ▪ Change to another shell ▪ csh ▪ Date ▪ date ▪ wget: get online files ▪ wget https://ftp.gnu.org/gnu/gcc/gcc-7.1.0/gcc-7.1.0.tar.gz ▪ Compile and run applications ▪ gcc hello.c –o hello ▪ ./hello ▪ What we need to learn today? o Automation of an entire script of commands! o Use the shell script to run jobs – Write job scripts Basic Shell Scripting 6 Shell Scripting ▪ Script: a program written for a software environment to automate execution of tasks ▪ A series of shell commands put together in a file ▪ When the script is executed, those commands will be executed one line at a time automatically ▪ Shell script is interpreted, not compiled.
    [Show full text]
  • Bash Guide for Beginners
    Bash Guide for Beginners Machtelt Garrels Garrels BVBA <tille wants no spam _at_ garrels dot be> Version 1.11 Last updated 20081227 Edition Bash Guide for Beginners Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions, translations and availability.........................................................................................2 4. Revision History..................................................................................................................................2 5. Contributions.......................................................................................................................................3 6. Feedback..............................................................................................................................................3 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................4 9. Conventions used in this
    [Show full text]
  • Lecture 17 the Shell and Shell Scripting Simple Shell Scripts
    Lecture 17 The Shell and Shell Scripting In this lecture • The UNIX shell • Simple Shell Scripts • Shell variables • File System commands, IO commands, IO redirection • Command Line Arguments • Evaluating Expr in Shell • Predicates, operators for testing strings, ints and files • If-then-else in Shell • The for, while and do loop in Shell • Writing Shell scripts • Exercises In this course, we need to be familiar with the "UNIX shell". We use it, whether bash, csh, tcsh, zsh, or other variants, to start and stop processes, control the terminal, and to otherwise interact with the system. Many of you have heard of, or made use of "shell scripting", that is the process of providing instructions to shell in a simple, interpreted programming language . To see what shell we are working on, first SSH into unix.andrew.cmu.edu and type echo $SHELL ---- to see the working shell in SSH We will be writing our shell scripts for this particular shell (csh). The shell scripting language does not fit the classic definition of a useful language. It does not have many of the features such as portability, facilities for resource intensive tasks such as recursion or hashing or sorting. It does not have data structures like arrays and hash tables. It does not have facilities for direct access to hardware or good security features. But in many other ways the language of the shell is very powerful -- it has functions, conditionals, loops. It does not support strong data typing -- it is completely untyped (everything is a string). But, the real power of shell program doesn't come from the language itself, but from the diverse library that it can call upon -- any program.
    [Show full text]
  • ASCII Delimited Format Plug-In User’S Guide
    ASCII Delimited Format Plug-in User’s Guide Version 3.4 ASCII DELIMITED ......................................................................................................... 4 CREATING AN ASCII DELIMITED MESSAGE ....................................................... 4 ASCII DELIMITED EXTERNAL MESSAGE UI........................................................ 6 DEFINING AN ASCII DELIMITED MESSAGE FORMAT...................................... 7 ASCII DELIMITED FORMAT OPTIONS .............................................................................. 7 Delimiter ..................................................................................................................... 8 Message Options......................................................................................................... 9 Treat Entire Input/Output as a Single Message (Message Mode) ...................... 9 Treat Each Record as a Separate Message (Batch Mode) ................................ 10 Single Record Mode ......................................................................................... 10 Header/Trailer Option.............................................................................................. 11 ADDING A NEW FIELD.................................................................................................... 12 SPECIFYING FIELD PROPERTIES...................................................................................... 13 The Required Property.....................................................................................
    [Show full text]
  • STAT579: SAS Programming
    Note on homework for SAS date formats I'm getting error messages using the format MMDDYY10D. even though this is listed on websites for SAS date formats. Instead, MMDDYY10 and similar (without the D seems to work for both hyphens and slashes. Also note that a date format such as MMDDYYw. means that the w is replaced by a number indicating the width of the string (e.g., 8 or 10). SAS Programming SAS data sets (Chapter 4 of Cody book) SAS creates data sets internally once they are read in from a Data Step. The data sets can be stored in different locations and accessed later on. The default is to store them in WORK, so if you create a data set using data adress; the logfile will say that it created a SAS dataset called WORK.ADDRESS. You can nagivate to the newly created SAS dataset. In SAS Studio, go to the Libraries Tab on the left (Usually appears toward the bottom until you click on it). Then WORK.ADDRESS should appear. SAS Programming SAS data sets SAS Programming SAS data sets SAS Programming Making datasets permanent You can also make SAS datasets permanent. This is done using the libname statement. E.g. SAS Programming Permanent SAS datasets The new dataset should be available to be accessed directly from other SAS programs without reading in original data. This can save a lot of time for large datasets. If the SAS dataset is called mydata, the SAS dataset will be called mydata.sas7bdat, where the 7 refers to the datastructures used in version 7 (and which hasn't changed up to version 9).
    [Show full text]
  • Positive Pay Format Guide
    Positive Pay Format Guide Check File Import Contents Contents ........................................................................................................................................................ 1 I. Supported File Types ............................................................................................................................. 2 A. Delimited Text Files ........................................................................................................................... 2 B. Microsoft Excel Files.......................................................................................................................... 2 C. Fixed-width Text Files ....................................................................................................................... 2 D. Header and Trailer Records .............................................................................................................. 2 II. File Data Requirements ......................................................................................................................... 3 A. Required Columns ............................................................................................................................. 3 B. Optional Columns.............................................................................................................................. 3 Positive Pay 1 of 3 BankFinancial, NA Format Guide 11-2016-1 I. Supported File Types Positive Pay supports the following three types of issued files: A. Delimited
    [Show full text]
  • Teach Yourself Perl 5 in 21 Days
    Teach Yourself Perl 5 in 21 days David Till Table of Contents: Introduction ● Who Should Read This Book? ● Special Features of This Book ● Programming Examples ● End-of-Day Q& A and Workshop ● Conventions Used in This Book ● What You'll Learn in 21 Days Week 1 Week at a Glance ● Where You're Going Day 1 Getting Started ● What Is Perl? ● How Do I Find Perl? ❍ Where Do I Get Perl? ❍ Other Places to Get Perl ● A Sample Perl Program ● Running a Perl Program ❍ If Something Goes Wrong ● The First Line of Your Perl Program: How Comments Work ❍ Comments ● Line 2: Statements, Tokens, and <STDIN> ❍ Statements and Tokens ❍ Tokens and White Space ❍ What the Tokens Do: Reading from Standard Input ● Line 3: Writing to Standard Output ❍ Function Invocations and Arguments ● Error Messages ● Interpretive Languages Versus Compiled Languages ● Summary ● Q&A ● Workshop ❍ Quiz ❍ Exercises Day 2 Basic Operators and Control Flow ● Storing in Scalar Variables Assignment ❍ The Definition of a Scalar Variable ❍ Scalar Variable Syntax ❍ Assigning a Value to a Scalar Variable ● Performing Arithmetic ❍ Example of Miles-to-Kilometers Conversion ❍ The chop Library Function ● Expressions ❍ Assignments and Expressions ● Other Perl Operators ● Introduction to Conditional Statements ● The if Statement ❍ The Conditional Expression ❍ The Statement Block ❍ Testing for Equality Using == ❍ Other Comparison Operators ● Two-Way Branching Using if and else ● Multi-Way Branching Using elsif ● Writing Loops Using the while Statement ● Nesting Conditional Statements ● Looping Using
    [Show full text]
  • Installing and Configuring PHP
    05 6205 CH03.qxd 11/20/03 11:27 AM Page 51 CHAPTER 3 Installing and Configuring PHP In the last of the three installation-related chapters, you will acquire, install, and configure PHP and make some basic changes to your Apache installation. In this chapter, you will learn . How to install PHP with Apache on Linux/Unix . How to install PHP with Apache server on Windows . How to test your PHP installation . How to find help when things go wrong . The basics of the PHP language Current and Future Versions of PHP The installation instructions in this chapter refer to PHP version 4.3.3, which is the current version of the software. The PHP Group uses minor release numbers for updates containing security enhancements or bug fixes. Minor releases do not follow a set release schedule; when enhancements or fixes are added to the code and thor- oughly tested, the PHP Group will releases a new version, with a new minor version number. It is possible that by the time you purchase this book, the minor version number will have changed, to 4.3.4 or beyond. If that is the case, you should read the list of changes at http://www.php.net/ChangeLog-4.php for any changes regarding the installation or configuration process, which makes up the bulk of this chapter. Although it is unlikely that any installation instructions will change between minor version updates, you should get in the habit of always checking the changelog of software that you install and maintain. If a minor version change does occur during the time you are reading this book, but no installation changes are noted in the 05 6205 CH03.qxd 11/20/03 11:27 AM Page 52 52 Chapter 3 changelog, simply make a mental note and substitute the new version number wherever it appears in the installation instructions and accompanying figures.
    [Show full text]
  • Understanding the Command-Line Interface
    Understanding the Command-Line Interface This chapter helps you understand the command-line interface. • Information About the CLI Prompt, on page 1 • Command Modes, on page 2 • Special Characters, on page 5 • Keystroke Shortcuts, on page 5 • Abbreviating Commands, on page 7 • Completing a Partial Command Name, on page 8 • Identifying Your Location in the Command Hierarchy, on page 8 • Using the no Form of a Command , on page 9 • Configuring CLI Variables, on page 10 • Command Aliases, on page 12 • Command Scripts, on page 14 • Context-Sensitive Help , on page 16 • Understanding Regular Expressions, on page 17 • Searching and Filtering show Command Output, on page 19 • Searching and Filtering from the --More-- Prompt, on page 23 • Using the Command History, on page 24 • Enabling or Disabling the CLI Confirmation Prompts, on page 26 • Setting CLI Display Colors, on page 26 • Sending Commands to Modules, on page 27 • BIOS Loader Prompt, on page 28 • Examples Using the CLI , on page 28 Information About the CLI Prompt Once you have successfully accessed the device, the CLI prompt displays in the terminal window of your console port or remote workstation as shown in this example: User Access Verification login: admin Password:<password> Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved. Understanding the Command-Line Interface 1 Understanding the Command-Line Interface Command Modes The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Second Internet Edition William E. Shotts, Jr. A LinuxCommand.org Book Copyright ©2008-2013, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, 171 Second Street, Suite 300, San Fran- cisco, California, 94105, USA. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. This book is also available in printed form, published by No Starch Press and may be purchased wherever fine books are sold. No Starch Press also offers this book in elec- tronic formats for most popular e-readers: http://nostarch.com/tlcl.htm Release History Version Date Description 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. 09.11 November 19, 2009 Fourth draft with almost all reviewer feedback incorporated and edited through chapter 37. 09.10 October 3, 2009 Third draft with revised table formatting, partial application of reviewers feedback and edited through chapter 18. 09.08 August 12, 2009 Second draft incorporating the first editing pass. 09.07 July 18, 2009 Completed first draft. Table of Contents Introduction....................................................................................................xvi
    [Show full text]
  • DATALINES, Sequential Files, CSV, HTML, and More
    SUGI 31 Tutorials Paper 228-31 DATALINES, Sequential Files, CSV, HTML and More – Using INFILE and INPUT Statements to Introduce External Data into the SAS® System Andrew T. Kuligowski, Nielsen Media Research ABSTRACT / INTRODUCTION The SAS® System has numerous capabilities to store, analyze, report, and present data. However, those features are useless unless that data is stored in, or can be accessed by, the SAS System. This presentation is designed to review the INFILE and INPUT statements. It has been set up as a series of examples, each building on the other, rather than a mere recitation of the options as documented in the manual. These examples will include various data sources, including DATALINES, sequential files, CSV files, and HTML files. GETTING STARTED – BASIC INFILE / INPUT with DATALINES In order to bring data from an external source into your SAS session, the user must provide the answers to a couple of simple questions: Where is the data, and what does it look like? The INFILE statement will define the data source and provide a few tidbits of information regarding its form, while the INPUT statement will define the format of the data to be processed. /* INTRO EXAMPLE */ NOTE: Invalid data for ConfName in DATA SasConf; line 9 1-9. INFILE DATALINES; NOTE: Invalid data for ConfCity in INPUT ConfName line 9 16-18. ConfYear NOTE: Invalid data for ConfST in ConfCity line 9 20-28. ConfST ; RULE: ----+----1----+----2----+----3--- DATALINES; 9 SUGI 2006 San Francisco CA SUGI 2006 San Francisco CA ConfName=. ConfYear=2006 ConfCity=. PHARMASUG 2006 Bonita Springs FL ConfST=.
    [Show full text]
  • YAML Based Input File Format for Finite Element Analysis
    Oskar Hvalstad-Nilsen Oskar Hvalstad-Nilsen YAML Based Input File Format For Finite Element Analysis Master’s thesis in Engineering and ICT Supervisor: Associate professor Bjørn Haugen June 2019 Master’s thesis Master’s YAML Based Input File Format For Finite Element Analysis Element Finite For Format Based Input File YAML NTNU Faculty of Engineering Faculty Norwegian University of Science and Technology of Science University Norwegian Department of Mechanical and Industrial Engineering and Industrial Department of Mechanical Oskar Hvalstad-Nilsen YAML Based Input File Format For Finite Element Analysis Master’s thesis in Engineering and ICT Supervisor: Associate professor Bjørn Haugen June 2019 Norwegian University of Science and Technology Faculty of Engineering Department of Mechanical and Industrial Engineering Abstract The finite element method (FEM) can be used to perform finite element analysis (FEA) of any given physical phenomenon, and is widely used in the fields of structural and mechanical engineering. Since FEA is computationally laborious it is best performed by a computer, and the FEM model is typically conveyed to the solver software by input files. These input files are generally formatted for specific FEA software, hence interoperability between them is an intricate matter. YAML 1.2 is an openly accessible data serialization language for all programming languages. Among its design goals are human readability, data portability, expressiveness, and easy imple- mentation. Its portability and expressiveness combined with the fact that well-defined YAML parsers already exist, makes it an interesting choice for FEA input files. The objectives of this thesis are to: I. Propose a YAML based input file format for finite element analysis of structural problems, and II.
    [Show full text]