DOCSLIB.ORG

Illiiiiiiii Liltiiiiii11111iillllllllll IIIIIIIIIIIIIIIIIIIIII Z

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Illiiiiiiii Liltiiiiii11111iillllllllll IIIIIIIIIIIIIIIIIIIIII Z IllIIIIIIIIlILtIIIIII11111IIIIillllllllllIIIIIIIIIIIIIIIIIIIIIIz_,"_",'-" 3 1176 00139 9808 NASA Technical Memorandum 80144 NASA-TM-80144 19800012559 p ISISUSERSMANUAL ._,.__-:_._::-_:-,_C2, _o_ _o B__A_ rBO_ _ BO0_ CAROLYN GRANTHAM Ar_-'!. igzg LANGLEY' FdLSLAR,.m _.,c..l_|ER LIBRARY, NASA HAMFffON,VIRGINIA MARCH1980 NASA National Aeronautics and Space Administration Langley Research Center Hampton,Virginia 23665 ABSTRACT The Interactive Software Invocation System (ISIS) is an interactive data management system. ISIS is being developed to act as a buffer between the user and host computing system. ISIS provides the user with a powerful system for developing software systems in an interactive environment. ISIS protects the user from the idiosyncracies of the host computing system by providing such a complete range of capabilities that the user should have no need for direct access to the host computing system. These capabilities include a data editor, a file manager, and a tool invoker, all under the control of a PASCAL-like Interactive Programming Language (IPL). I TABLE OF CONTENTS I. Introduction .............................. 6 II. Interactive Programming Language (IPL) Syntax ............. 7 A. Writeup Conventions ........................ 8 B. Break Key ............................ I0 . Co Errors .............................. ii D. Programming Statements ....................... 12 i. IPL/PASCAL Differences ..................... 12 2. System Variables ........................ 14 3. Comments ............................ 16 4o Declarative Statements ao ABBREV ........................... 18 b. TYPE ........................... 19 Co VAR ........................... 20 do ERASE ........................... 21 So Action Statements a. Assignment ......................... 22 b. EXITIF .......................... 23 Co IF .......................... 24 do FOR .......................... 2S e. LOOP .......................... 26 f. WHILE .......................... 27 go REPEAT .......................... 28 h° FOREACH .......................... 29 i. XEQ .......................... 30 jo SET TAG .......................... 31 ko CLEAR TAG ......................... 31 2 I. SET TRACE ........................ 33 m. CLEAR TRACE ......... ............... 33 n. ASK ............................ 34 o. PRINT, PRINTLN ........................ 36 p. CLEAR RUN ......................... 38 6. Programming Operators and Functions ............... 39 F. Library Statements ......................... 40 i. SET NAHE ............................ 42 2. USE ............................ 43 3. SAVE ............................ 44 4. PURGE ........................... 45 5. VOID ............................ 46 6. STORE ............................ 47 7. RESTORE ............................ 48 G. Text Editing Statements ....................... 49 i. FRAME Concept ......................... 49 2. RANGE Concept ......................... 51 3. Edit Statements ......................... 56 a. FRAME ........................... 56 b. ACTIVE ........................... 57 c. ERASE ........................... 58 d. LIST ........................... 59 e. INSERT ........................... 61 • f. READ ........................... 63 g. WRITE ........................... 65 h. DELETE ........................... 67 i. REPLACE ........................... 69 j. CIIANGE ........................... 71 3 k. ADD ........................... ?4 i. MODIFY ........................... ?6 m. COPY ........................... ?8 n. MOVE ........................... 80 o. REKEY ........................... 82 P. COUNT ........................... 83 q. EXEC ........................... 84 H. Tool Invocation Statements ..................... 86 i. BATCH Tools a. RUN .......................... 8? b. SEND .......................... 89 2. INTERACTIVE Tools a. STOP:SEND ....................... 90 I. Interrogation Statements ...................... 91 i. SHOW SHOWS ........................ 92 2. SHOW RESERVED ........................ 9S 3. SHOW STATEMENTS ........................ 94 4. SHOW AVAIL ........................ 9S 5. SHOW ABBREVS ........................ 96 6. SHOW TYPES ........................ 97 7. SHOW VARS ........................ 98 8. SHOW ID ........................ 99 "i 9. SHOW SETS ........................ I00 i i0 .........................SHOW CLEARS I01 .i! ii • SHOW NAME •°ooo•o•o•oooeo. eeoeooooo 102 z 12 • SHOW PAGES •ooo•o•oooooeeoooooeoooe 103 13. SHOW OPTIONS ........................ 105 14. SHOW COLUMNS ........................ 106 15. SHOW RUN .......................... 107 Appendix A.- Statement Summary Sheet .................... 108 Appendix B.- Alphabetical Statement Summary Sheet ............. 109 Appendix Co- ISIS Local Files ....................... Iii Appendix D.- IPL Error Messages ....................... 112 References ................................. 114 Index ................................... I15 INTRODUCTION _lis document covers the latest version of the Interactive Software Invocation System (ISIS) (12/20/79) discussing the syntax and operation of the Interactive Program Language, IPL. IPL is based on the higher order ._ language PASCAL and anyone wishing to use ISIS should have a working knowledge of PASCAL or have access to a PASCAL Manual (see ref. i). PASCAL was chosen as tilebase language because of its simplicity and its wide range of capabilities. IPL and PASCAL differences are discussed on page 12. IPL contains most of the arithmetic operations, functions, and control statements of a traditional programming language. This language has been extended to include statements for data and text editing, file management, and tool invocation. _e editor manipulates pages of text or data. The IPL statements allow insertion, deletion, replacement, and modification of lines of text or data. The file manager allows the user to save, access, and purge pages within a 5-1evel hierarchical file system. The tool invoker allows the user to communicate with the host computer system. ISIS is being developed by Dro Wo Joseph Berman on contract for Langley Research Center (LaRC). ISIS was originally developed under the CDC NOS-BE operating system at the University of Virginia and is currently running under the CDC NOS 1.3 operating system at LaRC. The transportability of ISIS is being tested by efforts to rehost it to an IBM 370 system and to a PDP-11 machine. Anyone having an application for ISIS is welcome to use it with .i i the understanding that ISIS is not a production system, but a developing system, i On the LaRC system, ISIS is stored on a direct access permanent file under 6 the user number 961300N° The control statements to access and execute ISIS are: .....,::r_.,.:t_.._,:::._i-..i.:h_.:..-"L_n:[...,:,.:,"9_!:0'"',:_Fin - Retrievethe ISIS file. .....i--.i'.Q-. - ExecutesISIS :[iS .T'.?; t,it"iI.!i'......."T_'t:.:.' ',,' 1 =-i _..,"-" :::...._:i...0 2 ..'"_1:':::...,, "i....._:'_. -:.i:::'.o 1:::,_ J.5. i;i:.i2. ,..,:..,"::":'? ' b • - Acceptable ISIS statements. .t5° i-i:-. :!;::"._"-t. ,::.:F::,, _ - Terminate ISIS session. i $ i S i ERt"i]:I.Ii::_:TE]::_o ,::FI:[_:[)F::EL:;:!!;: 5 ::, - L.0Fii:..iFL i;..j4::5:2J.,":'., STFIZ::KF'L. ':,::, i:,."T':,,:=:,J..::,l! ":, :: °.. INTERACTIVE PROGRA_IING LANGUAGE (IPL) SYNTAX The IPL descriptions provided in subsequent sections have the following format: The IPL statement syntax at the top of the page. The words appearing in caps must be typed as shown, whereas, the words in small letters can be replaced with appropriate information° A discussion of the statement, what it does, and how to use it is followed by examples illustrating how the statement can be used° See example page 18. The statements are discussed in groups according to capabilities. The first group, Interactive Programming Statements, contains statements of a traditional programming language. _le second group, File Management Statements, allows the user to save, replace, access, and purge information which is contained within a S-level hierarchical file system. _le third group, Text Editing Statements, contains statements which allows editing (Insertion, Deletion, Replacing, and Hodification) of lines of text or data which is contained in the file system. The fourth group, Tool Invocation Statements, allows the user to communicate with the host computer system. The fifth, and last group, Interrogation Statements, allows the user to make inquiries of ISIS, relating to statements in any of the above groups. 8 SYNTAX Syntax Conventions These conventions will be used in the IPL statements or in the discussions of the statements• ? ISIS prompt - informs the user that ISIS is ready > ISIS indication that the current statement is not yet complete and more input is required id Identifier id(s) One or more identifiers separated by commas J £n Line number n£ A specific number of lines [ ] Optional information for command I I_ Command choices are enclosed in brackets separated by vertical slashes (I) col Column number inc Line increment ... ISIS acknowledgement to the _ key • Separators in DATA BASE library page name , List separator BREAK Key Key The _ key has two functions. It enables the user to discard a lly typed line and reenter it. This is in:addition to the normal key. It also allows the user to terminate a command. The line to be reentered may be a command statement (statement verb) or a line in the ACTIVE page the user is in the process of editing. A good example would be if he made a typographical error in the text being inserted. The user hits the BREAK
Load more

Recommended publications
  • Rexx Hands-On Lab
    1 2 Welcome to the Introduction to Rexx Hands-on Lab. This lab will cover a series of topics about the Rexx language. At the end of each topic, there will be exercises that use the concepts covered in the charts and text for that topic. The solutions for the exercises are in Appendix A. This is not a graded class or lab so you are free to refer to the solutions if you would like or if you need help with any of the exercises. Also, if you need assistance with any of the lab material or exercises, please raise your hand and someone will come to assist you. 3 These are the exercises that you will be doing today. There are 2 PDF files on your desktop that you might find helpful as you work on the exercises: • REXX Reference will help you with statement syntax and usage • Appendix H is a summary of XEDIT commands that might be helpful when you are writing and updating your Rexx programs 4 This section introduces the Rexx Language and explains how to create and execute Rexx programs on z/VM and TSO systems. It also includes some z/VM hints to help you with today's exercises. 5 REXX is a nickname for Restructured eXtended eXecutor. The Rexx language was designed to be intuitive, easy to read, and easy to follow a program's logic. Rexx programs can be very simple, ranging from personal tools and utilities such as "scripts" of commands that you might run every day to set up your system or run test cases, to very complex programs that might be part of a licensed product.
    [Show full text]
  • Using REXX to Build a Front-End User Interface Han-Li Lee, United Illuminating Company
    220 Host Operating Systems Using REXX to Build a Front-end User Interface Han-li Lee, United Illuminating Company present a problem fclo those who do not have any Abstract knowledge or training in SAS language. A user­ This paper presents the UISSP (UI Social Suppon friendly system is thus required. Since back in early Programs) System, a menu-driven reporting system 1986 UI had not installed SAS/AF yet, the author using IBM's REXX (Restructured EXtended eXecu­ then decided to use REXX to build a user-friendly tor) language, base SAS e, and SAS/FSP e (SAS front-end interface. UISSP system, to allow the user version 5.18 under CMS operating system) for the to enter the data and run reports easily. United lliuminating Company, an electric utility company located in New Haven, Connecticut. The Running the UISSP System System uses the REXX to write a front-end user REXX is a general pwpose, high-level language. interface to the SAS System. It creates new files, This interface program is written in a REXX lan­ updates existing files, and produces reports. This guage EXEC, with a filename UISSP and a filetype paper shows the techniques used for building such a EXEC. It contains CP and CMS commands. REXX user-friendly reporting system. It will also compare programs are executed by an interpreter without fiJ'St the use of REXX and SAS/AF ® in building menu­ being translated into another form. This program is driven systems. written under the host system CMS. To stan running the system, the user just types a word "uissp," the Background filename of the EXEC, at the command line.
    [Show full text]
  • Real World Z/VSE to Z/OS Migration Experience from a Z/VSE Bigot
    Honesty | Loyalty | Integrity | Quality z/VSE to z/OS Migration Experience From a z/VSE Bigot’s Perspective Tony Thigpen – Senior System Programmer Agenda . Customer Background . Methods . Source Conversion . JCL Conversion . Utility Conversion . Operations Conversion . Data Conversion . Training . Issues that were discovered sooner or later . Discussion . Wrap Up Customer Background . Manufacturer located in Mississippi and North Carolina . Initial Configuration: o Z9 in MS running 4 z/OS LPARs (mix of 1.4 and 1.7) – 160mips o Z10 is NC running 5 VSE/ESA LPARs (1.5) – 70mips o Multiple AS/400s in different locations . First major changes o Both CPUs and some AS/400s were relocated to PZG facilities in FL . Second major changes o 3 of the VSE LPARs were slowly migrated off-platform o 2 VSE LPAR was merged into 1 VSE LPAR o All but one of the AS/400s located in FL were eliminated o All z/OS LPARs upgraded to 1.12 to allow them to run on a Z10 . Resulting Configuration: o Z9 in FL running 4 z/OS LPARs (all 1.12) – 150mips o Z10 in FL running 1 VSE/ESA LPAR (1.5) – 70mips Customer Background . Customer goal to cut costs o An os for each machine from IBM ($$) o Adabas for each machine ($$$) o Similar Third-party software on both machines ($$$) o Maintenance, floor space, HVAC costs ($$) o Operations (staff) costs ($) . Customer was concerned with older VSE/ESA o Out of Service o CICS/VS – CICS/TS conversion . The decision was to take the money budgeted for upgrading the VSE and use it instead to migrate the one remaining VSE LPAR to z/OS o Unpopular with VSE programmers but there were only 3 left.
    [Show full text]
  • Programmable Command Languages for Window Systems Egie
    Programmable Command Languages for Window Systems Rlchard Joel Cohn CMU-CS-88-139 June 1988 _egie Programmable Command Languages for Window Systems Report number CMU-CS-88-139 Copyright © 1988 by Richard Joel Cohn. All rights reserved. This dissertation was submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University. The research in this dissertation was supported by the Information Technology Center, a joint project of Carnegie Mellon University and International Business Machines Corporation. This dissertation was produced with Scribe. Illustrations were produced with Pic, Troff, and TranScript. Aldus and PageMaker are trademarks of Aldus Corporation. Apple and Macintosh are registered trademarks of Apple Computer, Inc. Clads is a trademark of Clads Corporation. DEC is a trademark of Digital Equipment Corporation. Hypercard is a trademark of Apple Computer, Inc. IBM is a registered trademark of International Business Machines Corporation. MacDraw, MacPaint, and MacWrite are registered trademarks of Clads Corporation. NeWS and Sun-3 are trademarks of Sun Microsystems, Inc. PostScript and TranScript are trademarks of Adobe Systems, Inc. Scribe is a registered trademark of Scribe Systems. SmaUtalk-80is a trademark of Xerox Corporation. Tempo is a trademark of Affinity Microsystems, Ltd. UNIXis a registered trademark of AT&T Bell Laboratories. Abstract Programmable command and macro languages have long served as important tools for users of computer systems. This thesis describes the design and implementation of a general-purpose command language for a window system. This has never been tried be- fore because these systems are new and because the problems inherent in providing a command language for a window system are hard.
    [Show full text]
  • VM/SP Introduction.Pdf
    GC19-6200-1 File No. S370/4300-20 Program Product GC19-6200-1 File No. S370/4300-20 IBM Virtual Machine/ System Product: Program Product Introduction Program Number 5664-167 Release 2 -----~- - i::~~ Second Edition (April 1982) This edition, GC19-6200-1, is a reV1S10n of GC19-6200-0. It applies to the IBft Virtual ~achine/System Product (5664-167) until otherwise indicated in new editions or ~echnical Newsletters. Changes are continually made to the information contained herein; before using this publication in connection with the operaticn of IBft systems, consult the IB~ 2:i2tem/370 and .!!300 f!:~.§§£!§ Bibli.£g~, GC20-0001, for the editions that are applicable and current. For a list of changes, see page iii. Technical changes or additions to the text cr illustrations are indicated by a vertical bar to the left of the change. It is possible that this material may contain reference to, or information about, IB~ products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that lEft intends to announce such IB~ products, programming, or services in your country. Publications are not stocked at the address given below; requests for IB~ publications should be made to your IBft representative or to the IB~ branch office serving your locality. A form for reader's comments is provided at the back of this publication. If the torm has been removed, comments may be addressed to IB~ Corporation, Programming Publications, Department G60, P.O. Box 6, Endicott, New York, U.S.A.
    [Show full text]
  • System Productivity Facility (ISPF) and ISPF/Program Development Facility
    GC34-2172-3 Interactive System Productivity Facility (ISPF) and ISPF/Program Development Facility What's New in ISPF? Version 2 Release 3 MVS Version 2 Release 2 VM/SP I , . .. GC34-2172-3 Interactive System Productivity Facility (ISPF) and ISPF/Program Development Facility What's New in iSPF? Version 2 Release 3 MVS Version 2 Reiease 2 VM/SP I Fourth Edition (July 1987) This edition applies to Version 2 Release 3, of the program products Interactive System Productivity Facility (ISPF) ^ (5665-319), and Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) (5665-317), and to all subsequent releases and modifications of both until otherwise indicated in new editions or Technical Newsletters. In the 370 environment, they are for use with with MVS/SP Version 1.3.5 or later. In the Extended Architecture (XA) environment, they are for use with MVS/SP Version 2.1.2 or later. This edition also applies to Version 2 Release 2 of the program products Interactive System Productivity Facility (ISPF) (5664-282), and Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) (5664-285), and to all subsequent releases and modifications of both until otherwise indicated in new editions or Technical Newsletters. They are for use with VM/SP Release 3. With Double-Byte Character Support (DECS), they are for use with VM/SP Release 4. Changes are made periodically to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM Systeml370 and 4300 Processors Bibliography, GC20-0001, for the editions that are applicable and current.
    [Show full text]
  • Unit 2 Basics of C
    Basics of C UNIT 2 BASICS OF C Structure 2.0 Introduction 2.1 Objectives 2.2 What is a Program and what is a Programming Language? 2.3 C Language 2.3.1 History of C 2.3.2 Salient Features of C 2.4 Structure of a C Program A simple C Program 2.5 Writing a C Program 2.6 Compiling a C Program 2.6.1 The C Compiler 2.6.2 Syntax and Semantic Errors 2.7 Link and Run the C Program 2.7.1 Run the C Program through the Menu 2.7.2 Run from an Executable File 2.7.3 Linker Errors 2.7.4 Logical and Runtime Errors 2.8 Diagrammatic Representation of Program Execution Process 2.9 Summary 2.10 Solutions / Answers 2.11 Further Readings 2.0 INTRODUCTION In the earlier unit we introduced you to the concepts of problem-solving, especially as they pertain to computer programming. In this unit we present C language - a standardized, industrial-strength programming language known for its power and portability as an implementation vehicle for these problem solving techniques using computer. A language is a mode of communication between two people. It is necessary for those two people to understand the language in order to communicate. But even if the two people do not understand the same language, a translator can help to convert one language to the other, understood by the second person. Similar to a translator is the mode of communication between a user and a computer is a computer language.
    [Show full text]
  • Solaris X Window System Reference Manual
    Solaris X Window System Reference Manual Sun Microsystems, Inc. 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. 1995 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 USA. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX system, licensed from UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third- party software, including font technology in this product, is protected by copyright and licensed from Sun's Suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark of Novell, Inc.
    [Show full text]
  • Ntm.Alttttr I Volume 13 Number 9 September, 1979
    /1 ) ~ j ,.. ) Uniersity Computer Center Newsletter I i UNIVERSITY COMPUTER CENTER UNIVERSITY OF MINNESOTA-TWIN CITIES MINNEAPOLIS, MINNESOTA 55455 contents bulletins CHANGE/6400/170-720/* P• 74 MERITSS up and running, no problems An additional "Introduction to UCC" class will be held on Tuesday, September 25th, 2:15-3:15 in NEW VERSION OF XEDIT P· 74 Mechanical Engineering 108. This will be an Highlights of Xedit 3.1 abbreviated version of tne October 5th class and is intended for users of the UNITE educational DATA BASE MANAGEMENT P· 75 system, however, other.; are 1o1elcome to attend. User group proposed, System 2000 notes VIDEO TAPE COPIES P· 75 Costs you more FOR SALE P• 75 USAGE STATISTICS p. 76 D 0 N' T FORGET THE SYSTEM CHANGE SHORT COURSE DESCRIPTIONS P· 77 I f SEE WRITEUP,UPGRADE. ntm.alttttr I Volume 13 Number 9 September, 1979 Director: Peter c. Patton Editor : Amy Koepke Comments about the content ot this newsletter, or suggestions for changes may be directed to the editor, 235a Experimental Engineering, 612/373-7744. The University of dinnesota adheres Lo L1te principle that all persons shall have equal opportunity and access to facilities in any phase of University activity 1o1ithout regard to race, I creed, color, sex, or national origin. I Copyright University of Minnesota, 1979. Permission to copy is hereby granted, provided that proper ackno1o1ledgement is given. ---------------------~~------ • - ,_J__.- ------------------- ~ . September, 1979 UCC NEI>/SLJ::TTER Page 73 s~veral powerful new commands have been added to During the weekend of August 25-26 a CDC Cyber provide XEDIT with text formatting capabilities.
    [Show full text]
  • The Basics of Using Z/VM
    Brian W. Hugenbruch, CISSP z/VM Development Team, IBM: Endicott, NY, USA The Basics of Using z/VM © 2010 IBM Corporation Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: *, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter® The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
    [Show full text]
  • Basic CMS and Z/VM Commands
    Basic CMS and z/VM Commands Velocity Software provides a cloud architecture for education and demonstration purposes. This allows users to create CMS servers and Linux servers using our zPRO product, and then use those servers for the duration of their self study education. It also allows for demonstration of our zPRO product. zPRO is Velocity Software's Cloud Enablement product, allowing end users to define and manage their servers without having z/VM knowledge. zPRO supports a private cloud for z/VM that includes support for Linux servers, CMS users, and 2nd level z/VM systems This paper describes the some of the basic CMS and VM commands as an introduction to using the IBM mainframe. The topics covered are: • 3270 keyboard • CMS help command • CMS query command • CMS xedit command • CMS filelist command • CMS profile exec file • CMS profile xedit file • CMS REXX commands More detailed information is available in these documents: • IBM Redbook - Introduction to the New Mainframe: z/VM Basics at http://www.redbooks.ibm.com/abstracts/sg247316.html?Open” Chapter 1 to 5 can give you an quick overview. The CMS commands you could work with, are in chapter 6. • IBM Library at https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/ com.ibm.zvm.v640.hcpa0/liboper.htm#liboper z/VM V6.4 CMS Commands and Utilities Reference, SC24-6166 z/VM V6.1 CMS Primer, SC24-6172 z/VM V6.4 CMS User's Guide, SC24-6173 z/VM: REXX/VM Reference , SC24-6221 z/VM: REXX/VM User’s Guide , SC24-62 3270 Keyboard This section documents the special keys used by z/VM and CMS, that are set up on x3270 or TN3270 emulators.
    [Show full text]
  • UNIX Commands Reference
    Mail Tools Special Command elm Sends and displays mail messages Line Characters Unix mailx Sends and displays mail messages > Redirect standard output to the file; erase mutt Sends and displays mail messages the file first Reference pine Sends and displays mail messages >> Redirect standard output to the file; xbiff Displays a mailbox and flag image on an append to the file X window when mail has arrived < Redirect standard input from the file Card | Pipe the standard output from one Text Editors command to the next A helpful reference to Unix commands on the CECS emacs Text Editor ? Single character wildcard Unix computers. gvim Graphical version of vim * Multiple character wildcard pico Text Editor [...] One of ... wild card vi Text Editor ; Command separator vim vi improved - Text Editor . Current directory xedit Simple Graphical Text Editor .. Parent directory xemacs Graphical version of emacs [gnu] / Directory level separator Text Processing Tools & Run command in the background http://www.cat.pdx.edu $ Begin shell variable name cat Concatenate (list) a file [email protected] = Shell variable assignment cut Displays specified parts from each line of a file dos2unix Convert text file from DOS format to Filename Expansion Program descriptions followed by [packageName] UNIX format Characters indicate which package the program is located in head List the beginning of a file ispell Spelling checker * Matches any characters (0 or more) Packages less Similar to more, but allows backward ? Matches any single character movement [...] matches any character in the enclosed list Packages configure the user's environment based on more List a file page by page or range what software he/she wants to use.
    [Show full text]