TSO Commonly Used Commands

8/3/2019 TSO Commonly Used Commands

1/8

1

GD ITD India, Command Center Operations TSO Commonly Used Commands

For support ofNavistar Inc.

Note: This process document reflect our understanding of the work executed by the ITD GD India teamfor Command Center Operations MVS Service / Softwareprocess on the accounts supported.

Navistar Mainframe Operations TSO Commonly Used Commands

Copyright International Business Machines Corporation 1999, 2007. All rights reserved.


2/8

2

Table of Contents

Document Control........................................................................................................3

Summary of Changes...................................................................................................3

Document Review Plans..............................................................................................3

How to Find the Latest Level of this Document............................................................31.0 Preface.............................................................................................................4

1.1 Purpose of this Document......................................................................................4

1.2 Who Should Use this Document?...........................................................................4

5


Copyright International Business Machines Corporation 1999, 2007. All rightsreserved.


3/8

3

Document Control

Summary of ChangesVersionNumber

VersionDate

Nature of Change DateApproved

1.0 Initial version

The document owner maintains document approval for this document. Corrections to grammar,spelling and format do not require approval or review. Unless otherwise noted in the revisiontable. All updates have been made by the document owner. Distribution/Notification TheDocument Approvers are notified via Lotus Notes Email when revised document is issued.

Document Review Plans

This document will be reviewed and updated, if necessary, as defined below:

As required to correct or enhance information content.

Following any organizational changes or restructuring.

Following a half yearly review.

Comments or other information related to the content of the document should be directedto the document owner.

How to Find the Latest Level of this DocumentAll other softcopy or hardcopy versions are invalid and are not to be used. Please note that

printed copies of this document are for reference only and are not controlled.




4/8

4

1.0 Preface

1.1 Purpose of this Document

The purpose of this document is to provide a comprehensive document that:

w Enables Production Control Analysts to understand the Control-M Environment Setup.

w Easy to find, read, and understand.

1.2 Who Should Use this Document?

This document should be used by the steady state Operators within the Command Center (andtheir back-up).

The Rogers Production Control-Enterprise Scheduling team should use this document.

Note: This process document reflects the work currently being executed by the deliveryteam(s) at the ITD GD-India centre based on their understanding and learning throughKnowledge Transfer / similar activities.




5/8


6/8

6

CHANGE(C or CHG): Causes the system to change the first whatever to the new name:.

COPY: Causes data to be copied from one dataset to another.

FIND(F): Will locate a character, word, or string of characters/words; however, if a space(s)exists between the words/characters, put the string in single quotes (').

LOCATE(L): In a patitioned dataset will locate a member, in a sequential dataset or memberwill locate a line number

MOVE: Same as COPY, except that the source is deleted after the move operation.

RESET: Causes a general resetting of intensified messages, incomplete line commands, andspecial lines.

SAVE: The data being edited in a dataset is kept and allows editing to be continued. Only inEDIT mode.

SUBMIT(SUB): Causes a print or production batch JCL to be executed.

CREATE: Causes a line or block of lines to be stored in any partitioned dataset as a newmember. The line(s) to be stored are designated by the C or CC line command (if using adouble line command, such as CC, the command must be used on the first line and again on thelast line of the block).

REPLACE: Same as CREATE, except that it allows an existing member or an entire sequentialdataset to be replaced.

The following commands are known as 'LINE COMMANDS' and are used in the first position of thenumerical column on the left hand side of the terminal screen:

BNDS: Causes display of the column boundary lines, to allow redefinition of boundary positions.(Column 1 of the text portion of the dataset is a command column. If you wish to move all ofthe data to the right or left, you would not want to remove the informative characters incolumn 1. BNDS would be typed on a line and entered. In column 2, place '' indicates the right hand boundary. After setting the boundaries, thetext could be shifted without affecting the column 1 command characters.)

COLS: Causes a grid to be displayed numbering the columns on the display screen.

TABS: Causes and allows the setting of TAB markers, which regulate the right ->| and left |


7/8

7

RR on the last line. Multiple blocks of the repeated block can be created by placing a numericfigure immediately after the RR on the first line of the block.

M (= MOVE): Identifies a line to be moved. Must be used in conjunction with a (after) or b(before) on another line. A MM block can be used to move successive lines at one time. Place aMM on the first line and a MM on the last line of the block to be moved. Remember to use the A

or B on the line where the moved lines are to be inserted.

C (= COPY): Identifies a line to be copied and moved at the same time. A or B must be used toidentify where the insert is to take place. A CC block can be used to copy and move a block oflines.

A (= AFTER): As stated in previous definitions, an A dictates that moved data is to be insertedafter that line.

B (= BEFORE): As stated in previous definitions, an B dictates that moved data is to be insertedbefore that line.

< (= LEFT): Causes the contents of the line to be shifted to the left (the column 1 warningunder BNDS about losing column 1 print commands does not apply - DATA only will be shifted).The standard movement is two characters; however more or less will be performed whenindicated by a numeric designation following > block command can be used, and a numeric figure following >> indicates the number of

characters that the block will be shifted to the right. if the boundary is not protected.

( (= LEFT): Same as ; however, column 1 print commands will be lost if the boundary is notprotected, for column 1 will be move to the right and no longer be in column 1.

X (= EXCLUDE): Causes the line to be excluded from display. May also be used to limit the scopeof the FIND and CHANGE commands.

S (= SHOW): Causes the above EXCLUDED line to be displayed.

TE: Facilitates bulk text entry by allowing to type continuously without regard to the linenumber area.

TF: Causes reflowing of a paragraph of text from the cursorposition to the end of theparagraph.




8/8

8

TS: Causes splitting of a line into two lines at the designated cursor position to facilitate theinsertion of new material in existing text.

The following are the print commands that were referred to previous in the precedingdefinitions:

+ (PLUS) allows print to overlap or produce darker print. This command does not work on theRM904 or dowstairs laser printers.

(SPACE) allows the cursor to drop to the next line.

0 (ZERO) allows the cursor to drop down two lines.

- (DASH) allows the cursor to drop down three lines.

C P'' ALL Changes all lower case characters in the dataset to upper case. To change allupper case characters to lower case use: C P'>' p'

TSO Commonly Used Commands

Documents

Transcript of TSO Commonly Used Commands