zos fundamentals se

z/OS Fundamentals for Tivoli Technical SalesStudent Exercises

March 2009

Copyright NoticeCopyright © 2010 IBM Corporation, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Soft-ware License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corpora-tion. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior writ-ten permission of IBM Corporation. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose.Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Den-mark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.Lotus is a registered trademark of Lotus Development Corporation.PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license.ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both.SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For fur-ther information, see http://www.setco.org/aboutmark.html.Other company, product, and service names may be trademarks or service marks of others.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM prod-ucts, programs, or services can be used. Subject to valid intellectual property or other legally pro-tectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.Printed in Ireland.

©Copyright IBM Corp. 2010 z/OS Fundamentals for Tivoli Technical Sales I

• • •••

Table of contents

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Student Exercises for Unit 1


Student Exercises for Unit 3 Exercise 1 – Logging on to TSO . . . . . . . . . .3-1

Introduction . . . . . . . . . . . . .3-1Log on to TSO . . . . . . . . . . . .3-1

Exercise 2 – Navigating the ISPF panels . . . . . . . . .3-2Introduction . . . . . . . . . . . . .3-2

Move the command line to the top . . . . . . . . .3-3Examine the menus . . . . . . . . . . . .3-3Work with split screens . . . . . . . . . . .3-4

Exercise 3 – Work with sequential data sets . . . . . . . .3-4Introduction . . . . . . . . . . . . .3-4

Create a sequential data set . . . . . . . . . .3-5Note: Notice the Directory blocks field. If you wanted to create a new partitioned data set, you

must specify a number of directory blocks here. That is the only difference between creating a se-quential data set and a partitioned data set. . . . . . . . . .3-6

Edit the new data set . . . . . . . . . . .3-6Change the name of your new data set . . . . . . . . .3-6Delete your data set using the Data Set List Utility. . . . . . . .3-7

Exercise 4 – Work with partitioned data sets . . . . . . . .3-7Introduction . . . . . . . . . . . . .3-7

Copy selected members from existing PDS . . . . . . . .3-7Create a new member in an existing PDS . . . . . . . .3-8Copy a single member . . . . . . . . . . .3-8Use edit line commands . . . . . . . . . . .3-9

Exercise 5 – Find and Change . . . . . . . . . 3-11Introduction . . . . . . . . . . . . 3-11

Exercise 6 – Search and Compare . . . . . . . . . 3-12Introduction . . . . . . . . . . . . 3-12

Compare two PDS members . . . . . . . . . 3-12Search a PDS for a string . . . . . . . . . . 3-13

This concludes the exercises for this unit. . . . . . . . 3-14

Student Exercises for Unit 4 Exercise 1 – Create a batch job . . . . . . . . . .4-1

Introduction . . . . . . . . . . . . .4-1Create the PDS member and copy an existing job card . . . . . .4-1This concludes the exercises. . . . . . . . . . .4-3

Student Exercises for Unit 5 Introduction . . . . . . . . . . . . .5-1

Start SDSF . . . . . . . . . . . . .5-1Display available jobs and job elements . . . . . . . .5-1Purge a job and its elements . . . . . . . . . .5-2Look at the status of a started task . . . . . . . . .5-2Look at z/OS console messages . . . . . . . . . .5-3Enter z/OS console commands . . . . . . . . . .5-4End of Unit 5 exercises . . . . . . . . . . .5-4

II z/OS Fundamentals for Tivoli Technical Sales ©Copyright IBM Corp. 2010

• • • ••

Table of contents


Student Exercises for Unit 6 Exercise 1 – Work with the z/OS UNIX shell . . . . . . . 6-1

Introduction . . . . . . . . . . . . 6-1Exercise 2 – Work with the ISPF Shell . . . . . . . . 6-3

Introduction . . . . . . . . . . . . 6-3This concludes the exercises. . . . . . . . . . 6-6

• • • ••

1-1

Note to the user:

These exercises were written to be performed on a specific z/OS image in Raleigh, NC.

The data set names and member names will be different on the z/Os image where you perform the exercises. Ask the system administrator for suitable data sets to substitute in the exercise steps. These exercises do not change any system resources except for allocating user data sets.

Whether you use a z/OS in Raleigh or elsewhere, take care to not change anything that is not part of these exercises.


There are no lab exercises for Unit 1.

• • • ••

2-1


There are no lab exercises for Unit 2

• • • ••

3-1


Exercise 1 – Logging on to TSO

Introduction

This exercise will take you through the steps to log on to a TSO session. You need to know how to complete these steps in order to proceed to the subsequent exercises.

Note: Each student has a unique user ID assigned. The format is USERnn, where nn is a number. Every place you see reference to USERnn or userNN, substitute your user ID including the numbers.

TSO and ISPF commands and actions are generally not case sensitive. Commands and data set references are in capital letters in these exercise for readability. You do not have to use the same case as the exercise guide.

Log on to TSO

___ 1. Start the 3270 terminal emulator session that connects you to VTAM.

___ a. Click New Session.

___ b. Click Link Parameters.

___ c. Type the IP address of the z/OS image in the Primary Host Name or IP address field:

9.44.15.197

Note: The IP address is converted through network address translation (NAT). If you examine the actual IP address within z/OS, you will find 10.44.15.197.

___ d. Click OK, then click OK again. The terminal emulation sessions opens and you see the USS MSG10 screen.

Some environments take you to a VTAM MSG10 screen where you choose the online application such as TSO, and others are configured to put you directly into a TSO session.

3-2 z/OS Fundamentals for Tivoli Technical Sales ©Copyright IBM Corp. 2010

• • • ••

Student Exercises for Unit 3Exercise 2 – Navigating the ISPF panels


Note: The default cursor for a new user ID is the underline. This can be hard to locate at times on a busy screen. You can change to a block cursor by pressing Alt+F11.

___ 2. Type TSO in the Application field and press Enter.

Note: The Enter key on most 3270 emulators is labeled Ctrl on most keyboards and is located to the right of the space bar. The Reset key is the Ctrl key to the left of the space bar. You can change the keyboard mapping in PCOMM if you want to use a different key as Enter.

___ 3. Type the user ID you were assigned and press the Enter key.

___ 4. Type the appropriate password (case does not matter here). Before you press Enter, notice the other fields on the TSO/E Logon panel. There is a Procedure name, which specifies which CLIST will be run. You can also provide commands to run or optionally change the region size (if your installation allows this). Now press Enter.

___ 5. After your password is validated you are presented with the TSO READY prompt.

Exercise 2 – Navigating the ISPF panels

Introduction

This exercise takes you through the ISPF dialogs. You will explore the various actions, options, and function keys.

©Copyright IBM Corp. 2010 z/OS Fundamentals for Tivoli Technical Sales 3-3

• • •••

Student Exercises for Unit 3Exercise 2 – Navigating the ISPF panels


___ 1. Start from the TSO READY prompt. Type ISPF and press Enter. You should see the Primary Option Menu.

___ 2. Press F10 to position the cursor on the Action bar. Press Enter to see the functions that are available under that action. Press F12 to close the actions menu window. Look at all of the actions by tabbing to each and pressing Enter.

Note: ISPF implements IBM’s Common User Access (CUA) standard, which defines the use of function keys and tabs to navigate to the various parts of the panel. You can also simply use your mouse or the cursor arrow keys to position the cursor over the desired spot. You can combine the use of function keys and the mouse to position the cursor – it is entirely up to you.

Move the command line to the top

___ 3. Position the cursor on the Option field. Type a zero (“0”) and press Enter. The ISPF Settings panel opens. Notice the first line labeled “Command line at bottom” has a slash (/). This setting positions the command line at the bottom of the screen, and you have to tab or use the mouse to locate it.

___ 4. Delete the character in this field next to this line and press Enter. What happened?

You now see the command line at the top of the panel. Most ISPF uses do not like having their command line at the bottom of the screen. Changing this setting is the first thing they do with a new user ID.

___ 5. Notice the More: + in the upper right corner. This indicates that there more lines than can be displayed on this panel. Press F8 to scroll forward and observe what happens to the More: +. No more lines are available to display. Press F7 to scroll back.

You can customize your ISPF presentation by changing the values in the ISPF Settings panel. These changes are specific to your user ID and are saved in your profile data set. Press F12 to cancel any changes you might have made and return to the Primary Option Menu.

___ 6. Press F3 to exit ISPF Settings and return to the primary menu.

Examine the menus

___ 7. Put the cursor on the Utilities action at the top of the screen and press Enter. Make note of the functions displayed. Press F12 to close the menu and then enter 3 on the Option line to see the Utility Selection Panel. Notice that the list of functions is very similar to those displayed on the Utilities action menu. There are usually multiple ways to get to a specific function, and most users settle on one and use it consistently.


• • • ••

Student Exercises for Unit 3Exercise 3 – Work with sequential data sets


___ 8. Enter 4 on the Utility Selection Panel option line and observe the Data Set List Utility panel. This is one of the most commonly used panels.

Press F3 until you get back to the Primary Option Menu.

___ 9. Enter 3.4 on the option line. Observe that you go directly to the Data Set List Utility panel. You can stack commands in ISPF to save time and avoid loading your processor. If you prefix your command with an equal sign (=), you can go directly to a specific panel from anywhere within ISPF. This technique is a real time saver if your response time is slow.

Work with split screens

___ 10. Invoke the Split Screen function by pressing F2. This will open another ISPF dialog with the same settings. Having two dialogs is a very convenient way of running a batch job and viewing the output without constantly changing to another panel. The two dialogs are independent of each other but both are running in a single TSO session with the same user ID.

___ 11. The location of the cursor will determine where the new window opens. Move the cursor about half way down the screen and press F2 again. Notice how the top of the second dialog moved to the cursor location. You can position the top of the second dialog wherever you want with F2.

___ 12. Press F9 a few times. Note that the cursor switches from one screen the other. You can also move the cursor yourself with the mouse or cursor arrow keys.

A common technique for using split screens is to position the cursor at the very top of the panel before pressing F2. This will make both screens as large as possible. Press F9 to switch between screens. The dialog on which the cursor is positioned is the active window.

___ 13. Close one of the dialogs by pressing F3 or F12 and leave the other open for the next exercise.

Exercise 3 – Work with sequential data sets

Introduction

This exercise shows you how to create and manage sequential data sets using ISPF. Some installations use an option that prefixes the user’s TSO user ID to the data set name, so if you are creating a data set with your user ID as the high level qualifier you do not need to


• • •••



specify it. To use something other than your user ID as the high level qualifier, wrap the data set name in single quotation marks.

To prevent confusion, it is a good practice to fully qualify the data set name and wrap it in quotation marks.

Create a sequential data set

___ 1. Go to the Data Set Utility panel. Use the Utilities action and select Data Set or enter option 3.2 on the Primary Option Menu.

___ 2. Enter option A (for Allocate) and tab to the Data Set Name line. Type EXERCISE in the Data Set Name field and press Enter.

If you want to develop the habit of using single quotation marks, enter the data set name as ‘USERnn.EXERCISE’, where USERnn is your TSO user ID.

___ 3. The next panel is Allocate New Data Set, where you specify the data set characteristics. Press F1 to access the help panels. Scroll through the help panels by pressing Enter. Press F3 to exit help when you have read enough.

___ 4. Fill in the required fields (those that cannot be left blank) and press Enter to create the new data set. The minimum requirements for a sequential data set are:

Data Set Characteristic Description Value

Space units Usually cylinders, tracks, or blocks Track

Primary quantity How many units in the primary allocation 15

Secondary quantity How many units in the secondary allocations 15

Record format FB (fixed, blocked) for sequential file FB

Record length The logical record length 80

Block size Must be a multiple of the record length 3200


• • • ••



Note: Notice the Directory blocks field. If you wanted to create a new partitioned data set, you must specify a number of directory blocks here. That is the only difference between creating a sequential data set and a partitioned data set.

Edit the new data set

___ 5. The easiest way to edit a data set is from the Data Set List Utility (option 3.4). Enter part or all of the data set name on the DSName Level field and press Enter. If you enter USERnn, you will see a list of all data sets whose high level qualifier is USERnn.

___ 6. Select data set USERnn.EXERCISE by positioning the cursor next to and pressing Enter. You see a menu of actions that you can take. Select Edit (number 1) and press Enter. The next panel is the EDIT Entry Panel. Leave the values as defaulted and press Enter again.

You could have also typed letter E by the data set name and gone directly to the edit dialog.

___ 7. You are now in the edit dialog. Move the cursor under the line of asterisks and type a few lines of data. Do not type over the six red dots – those are the line numbers. Press Enter and the dialog will collapse the empty lines and assign line numbers. Save your changes by pressing F3 and you will return to the Data Set List Utility.

Tip: The editor only saves lines that contain text. If you press the Enter key before you type any lines of text, the editor collapses to just the top and bottom indicators because the file is empty. Put the cursor in the asterisks at the far left of the Top of Data line and type I 10 (letter I followed by the number 10) to insert 10 new lines. Press Enter and the editor will show the 10 blank lines.

Practice this a few times to understand how the editor behaves for empty files.

Change the name of your new data set

___ 8. From the Data Set List Utility, enter all or part of your data set name. Press Enter to go to the list of data sets.

Cancelling changes

Pressing F12 (Cancel) after changing a data set will show a dialog that asks you to confirm that you want to cancel. You could also type CANCEL on the command line to discard any changes you have made. If you make changes and then exit (F3), the change is immediate and permanent.


• • •••

Student Exercises for Unit 3Exercise 4 – Work with partitioned data sets


___ 9. Type a slash next to the data set and press Enter. Type a 6 for the Rename action and press Enter. You could also type the letter R next to the data set name and skip the menu.

___ 10. Type a new name for your data set. Remember that data set names are nodes of up to eight character separated by dots (periods) and can be no longer than 44 characters (including the dots). Press Enter and your data set will be recataloged with the new name.

___ 11. Go back to the Data Set List Utility and find your data set by its new name.

Delete your data set using the Data Set List Utility.

___ 12. Select your data set (with its new name) with a slash and press Enter.

___ 13. Locate and enter the Delete action, press Enter, and respond to the confirmation message by pressing Enter. Note that you can only delete sequential or partitioned data sets using this utility. VSAM data sets are deleted using the IDCAMS utility.

Note: Deleted data sets cannot be recovered, unless they were backed up in some way. There is no Trash can in ISPF.

Exercise 4 – Work with partitioned data sets

Introduction

This exercise shows you how to manage members of a partitioned data set (PDS). You will copy selected members to a new data set, create a new member, use an existing member to create a new one, and edit a member using edit line commands.

Copy selected members from existing PDS

___ 1. Use the Data Set List Utility (=3.4) to locate data set USER.PROCLIB.

___ 2. Place the cursor next to the data set name and press Enter. You see a list of data set actions. Enter 17 (for Copy) and press Enter.

___ 3. You see the list of members in this PDS. Assume you want to copy all the members that start with SHR2. Type S SHR2* (for Select SHR2*) on the Command line and press Enter.


• • • ••



S SHR2*

The next panel is the COPY Entry Panel. This panel shows the data set that you are copying from. Notice the Options. The option to replace like-named members is important to remember. If you need to replace a member with the same name, you must select that option. Otherwise, your copy operation will not work.

___ 4. Enter MY.PROCLIB as the name of your new PDS on the Data Set Name field. Remember that if you do not use quotation marks, TSO will make your user ID the first node of the data set name. Press Enter.

___ 5. Because the data set is new, the Allocate Target Data Set panel is next. Enter 1 in the Allocations Options field and press Enter. If you wanted to change the data set attributes (make it smaller, larger, different volume, and so on), you could do so with this panel.

___ 6. The selected members are copied to your new data set. Press F3 until you return to the Data Set List Utility panel.

___ 7. Locate your new data set with the Data Set List Utility. Type an E (for Edit) next to the PDS name is the list. You will see a list of the members of the PDS, and they should all begin with SHR2.

Create a new member in an existing PDS

___ 8. Leave your MY.PROCLIB PDS open in edit mode. To create a new member, type s (for Select) NEWPROC and press Enter. You will see the familiar Edit panel where you can type whatever data you wish. Enter a few lines of text and press Enter, then press F3 to close the Edit panel. Note that you cannot save an empty member.

Copy a single member

Copying an existing member can save a tremendous amount of time and typing.

___ 9. Locate USER.PROCLIB again. Type Mon the Command line to show a list of the members. Scroll until you see the member named SAMPPROC.

Tip: You can locate a PDS member quickly by entering the letter L followed by part of the member name. For example, L SAMP will position the list to the first occurrence of a member whose name begins with SAMP.

___ 10. Type C in the Command Line to copy the member. Press Enter.

___ 11. On the COPY Entry Panel, enter the name of the MY.PROCLIB data set that you created earlier. Assume that you want the copied member to have a different name


• • •••



in your PROCLIB. Tab to the NEW member name field and enter myproc. Press Enter.

___ 12. Return to the Data Set List Utility and locate your MY.PROCLIB. List the members using the M command and validate that the member MYPROC is present. Exit the member list and return to the Data Set List Utility panel.

Use edit line commands

___ 13. Open your MY.PROCLIB in edit mode and select member SHR2DSST. Remember that online help is always available using F1 if you forget the commands.

Use line commands to manipulate data from within the edit dialog. Practice using the Copy, Move, Delete, Repeat, and Insert commands. These commands are typed into the sequence number field on the lines you want to affect. Keep in mind that the multiple format commands, such as CC and MM, must be used in pairs (each has a beginning and an end).

___ a. If you see CAUTION or Warning messages at the top of the edit session, type res (for Reset) lon the Command line and press Enter.

Note: The following instructions are random and serve no particular purpose other than providing you with some practice using the editor.

___ b. Find a DD definition labeled RKANPARU using the Find command.

___ c. Duplicate the two RKANPARU DD definition lines. You can enter CC (copy multiple) on both lines, and enter B (before) on the line following, or you can enter RR (repeat multiple) on both lines. The result is the same.

Command Description

C, CC Copy one line, multiple lines

M, MM Move one line, multiple lines

D, DD Delete one line, multiple lines

R, RR Repeat one line, multiple lines

A After this line

B Before this line

I, In Insert one line, insert n number of lines


• • • ••



___ d. Insert two new lines below the RKANPARU DD definition. Make both lines JCL comments (//* in columns 1 to 3) and type some text. It is always a good practice to document any changes you make with JCL comment.

___ e. Move the cursor to the of the first RKANPARU line (after DISP=SHR,).

Note: Do not use the End key on the keyboard to get to the end of the line. The default IBM PCOMM setting for End is Erase End of Field (erases from the cursor position to the end of the text).

___ f. Type some text in lower case. Press Enter.

Did the text you entered get converted to upper case? If not, the edit sessions has CAPS OFF, meaning that lower or mixed case will be honored and not converted.

___ g. ALL JCL must be in upper case. Type CAPS ON on the Command line and press Enter. Type over one of the characters anywhere on the line that you modified and press Enter. The lower case text is shifted to upper case. As long as CAPS ON is set, any text you enter will be converted to upper case automatically the next time you press Enter.

___ h. Scroll to the bottom of the file. You can press F8 repeatedly, or type m on the Command line and press F8. M (for Maximum) works for scrolling forward, backward, left, and right.

___ i. Assume that the comments about SYSTCPD are obsolete. Delete them all. You can enter DD on the first and last lines to delete and press Enter. You can also enter Dnn on the first line to delete, where nn is the numbers of lines you want to delete.

Note: In most installations, UNDO is not available. If you make a mistake editing data, you can cancel all the changes using F12 or the Cancel command, but you cannot undo a single action.

___ j. Locate the job step labeled TEMS (you can also search for PGM=KLV). Rearrange the sequence of the STEPLIB concatenation by moving the KANMODL data set after the KANMOD data set. Be sure to move both lines that comprise the data definition.

___ k. Cancel all of the changes you made to the SHR2DSST member. You can use F12 or the can (Cancel) command.

These are the most commonly used line commands but there are many more. You can see them in the online help for Edit, option 12. Line commands work in any edit session and are not limited to PDS members.


• • •••

Student Exercises for Unit 3Exercise 5 – Find and Change


Exercise 5 – Find and Change

Introduction

You can locate (find) and change text within a sequential file or PDS member. Find and Change are two of the Edit Primary Commands and are entered on the command line, rather than in the sequence number field.

FIND can be abbreviated F. The string (if it exists) is highlighted. You can find subsequent occurrences by pressing F5 (Repeat find) until you see the *Bottom of data reached* message. Keep in mind that the find function is relative to where you are in the file. You can add the parameters FIRST, LAST, PREV, NEXT, or ALL to the command to control the direction or scope of the operation.

___ 1. Edit the PDS member userNN.MY.PROCLIB(SHR2OC0) (O is the letter o, and 0 is a zero).

___ a. Locate the first occurrence of the string //RKANPARU using the Find command:

F //RKANPARU

___ b. Repeat the Find command by pressing F5 (Rfind). There is only one occurrence of that string in the file, and you see the *Bottom of data reached* message.

___ c. Return to the top of the file. Find the first occurrence of the string RKANPARU (without the slashes). Repeat the find until you reach the bottom of the file. There are five occurrences of the string.

CHANGE can be abbreviated C. ISPF will locate the first occurrence of the string you specify and change it to the value of the second parameter. You can keep making the same change by pressing F6 (Repeat change). Change also supports the FIRST, LAST, PREV, NEXT, or ALL parameters.

___ d. Return to the top of the file. Change the first occurrence of RKANPARU to MYFILE.

C RKANPARU MYFILE

___ e. Continue changing RKANPARU to MYFILE by pressing F6 (Rchange).

___ f. Cancel all of the changes to the member and open it again for editing.

___ g. This time, change all occurrences of RKANPAR (without the U at the end) to MYFILE with a single command.

C RKANPAR MYFILE ALL


• • • ••

Student Exercises for Unit 3Exercise 6 – Search and Compare


What happened? Do you see some unintended changes (MYFILEU)? Be careful performing global changes, because you might have unintended consequences.

___ h. Save the changes to the member before proceeding to the next exercise.

Exercise 6 – Search and Compare

Introduction

The ISPF Utility option provides the SuperC function to compare two sequential files or partitioned data set members and the Search-For function to globally search for strings. This exercise shows you how to compare two PDS members which are cataloged procedures and list the differences, then how to search an entire PDS for occurrences of a given character string.

Compare two PDS members

Find the differences between two cataloged procedures of the same name in two partitioned data sets using the SuperC function.

___ 1. Invoke SuperC (option 12) from the Utility Selection Panel. SuperC asks you to specify the new data source (data set or PDS member) and the old data source and then shows you the records that were inserted into or deleted from the new data.

Most users do not use the top portion of the panel (Project, Group, and so on). It is easier to specify the entire data set name and member name in the Other Partitioned, Sequential, or VSAM Data Set area.

___ 2. Type the name of your MY.PROCLIB, followed by the member name SHR2OC0 in parenthesis, on the New Data Set panel.

MY.PROCLIB(SHR2OC0)

Surround the data set name with quotation marks if you typed the fully-qualified name. Do not use quotation marks if you left off the user Id.

___ 3. Notice the Execution and Output Mode fields. The default settings are to run in the foreground and to show the results in an edit session. Press Enter to go the next panel.


• • •••



___ 4. Type the original PDS name USER.PROCLIB and member name SHR2OC0 name on the Old Data Set panel. This time you must use the quotation marks. Press Enter.

‘USER.PROCLIB(SHR2OC0)’

SuperC invokes the compare function and writes the results to the data set specified on the Listing DS Name field. Since you left the output mode as the default, you see the results in an edit session. You could modify the results and save your changes as a report or for other uses.

The results show the differences between the old proc and the new proc. Lines with a D in the ID field are present in the old proc and not present (deleted) in the new proc. Lines with an I are inserted in the new proc (not found in the old proc). Lines that were changed are shown with an I then a D.

Because you changed RKANPAR to MYFILE in a previous step, you see each an add and a delete for each line that had the string RKANPAR.

Search a PDS for a string

Search all members of a partitioned data set to find a particular text string using the Search-For function.

___ 5. Invoke the Search-For function (option 14) from the Utility Selection Panel.

Assume that you want to locate all of the members in your MY.PROCLIB PDS that have the string RKANPAR.

___ 6. Type RKANPAR in the Search String field.

___ 7. Type the name of your MY.PROCLIB in the Other Partitioned, Sequential, or VSAM Data Set field. Follow the data set name with an asterisk inside of parenthesis.

MY.PROCLIB(*)

The (*) indicates that you want to search all members of the PDS. If you only wanted to search a single member, put that member name inside the parenthesis. Press Enter.

___ 8. Search-For lists the members where the string was found and the line number of each occurrence. Note that this is the physical line number, which could differ from the sequence number in the file.


• • • ••



This concludes the exercises for this unit.

• • • ••

4-1


Exercise 1 – Create a batch job

Introduction

In this exercise you will create the Job Control Language necessary to run the DFSMS utility program IEBGENER to print a PDS member to a sequential file. Copy an existing JOB card and create the remaining necessary Job Control Language (JCL) statements.

Create the PDS member and copy an existing job card

___ 1. Create a new partitioned data set with the following characteristics. Leave any unspecified field blank.

• Data set name: MY.JCL (use quotation marks if you specify the user ID as the high-level qualifier)

• Volume serial: TVED14

• Space units: Track

• Primary quantity: 15

• Secondary quantity: 15

• Directory blocks: 10

• Record format: FB

• Record length: 80

• Block size: 3120

___ 2. Copy the JOB card in USER.JCLLIB(JOBCARD) to your PDS.

___ 3. Locate and edit the BJOBCARD you just copied. It is a standard, generic JOB card. Edit your job card member and put your user ID in place of the eight underscores on the first line. It is very important that you be able to distinguish your jobs from those of other students.


• • • ••

Student Exercises for Unit 4Exercise 1 – Create a batch job


Notice the TYPRUN=SCAN command on the second line. If you remove the asterisk in column 3 and submit the job, JES2 will scan the JCL for validity but not actually execute the job. This is a good way of checking your JCL before you run it.

Leave the card commented for now.

___ 4. Add some comments that document what this job does.

//USER01 JOB (TIV,251A),JMIMS,NOTIFY=&SYSUID, //* TYPRUN=SCAN, // MSGCLASS=H,CLASS=A //********************************************************//* This job runs IEBGENER to print a PDS member//********************************************************

___ 5. Add an EXEC statement (job step) to execute program IEBGENER

//USER01 JOB (TIV,251A),JMIMS,NOTIFY=&SYSUID, //* TYPRUN=SCAN, // MSGCLASS=H,CLASS=A //********************************************//* THIS JOB COPIES A PDS MEMBER TO //* A SEQUENTIAL FILE. //********************************************//STEP1 EXEC PGM=IEBGENER

___ 6. If you were executing an application program, you would need a STEPLIB DD statement to identify where the load module is located. IEBGENER does not need a STEPLIB DD because it is an MVS utility. Create a dummy STEPLIB just for the practice and make it a comment.

//USER01 JOB (TIV,251A),JMIMS,NOTIFY=&SYSUID, //* TYPRUN=SCAN, // MSGCLASS=H,CLASS=A //*********************************************//* THIS JOB COPIES A PDS MEMBER TO //* A SEQUENTIAL FILE. //*********************************************//STEP1 EXEC PGM=IEBGENER //*STEPLIB DD DSN=USER1.STEPLIB,DISP=SHR

___ 7. Add the required utility DD statements

DD Name Specification

SYSPRINT DD SYSOUT=*

SYSIN DD DUMMY

SYSUT1 DD DSN=USERnn.MY.PROCLIB(SHR2DSST), DISP=SHR Substitute the numeric part of your user ID for nn.


• • •••



___ 8. When you are satisfied with your JCL, submit it to the JES internal reader by typing SUB on the ISPF command line. This will cause your JCL to be submitted for execution as a batch job and will generate the IKJ56250I message.

IKJ56250I JOB USER01(JOB01446) SUBMITTED

___ 9. Make a note of the job number. Press Enter to acknowledge the message. Press Enter again when you see the message saying the job has ended.

The NOTIFY=&SYSUID parameter on the JOB card causes your user ID to receive a message when the job completes. That message includes the return code (MAXCC=0). A zero return code normally indicates successful job execution.

___ 10. Submit the same job two more times so you will have several sets of output files to work on in the next exercise.

If your job had any JCL errors or other problems, you would need to review the job log and other output to determine what to do. The next unit covers the use of SDSF to monitor jobs and tasks, including how to review job output.

This concludes the exercises.

SYSUT2 DD SYSOUT=*

DD Name Specification


• • • ••



• • • ••

5-1


Introduction

In this lab exercise SDSF commands and MVS commands from the SDSF ISPF dialogs.

The answers to many of the questions asked in this lab will vary from one system to the next. If the answer is known and common to all systems it is supplied immediately following the question. Otherwise the answer must be ascertained from the information displayed on your system.

SDSF action codes and commands are not case sensitive. The commands are shown in the steps in capital letters for readability.

Start SDSF

___ 1. Log on to TSO/ISPF.

The system programmer who set up the z/OS system for your labs made SDSF option S on the Primary Option menu. Different sites might put the option elsewhere, and you have to ask where it is.

___ 2. Start SDSF using option S. The SDSF PRIMARY OPTION MENU opens.

Display available jobs and job elements

___ 3. Display the lab jobs that you and other students have submitted. Set the prefix filter to USER* and go to the Output queue.

PRE USER*;O

___ 4. If the list of jobs in the output queue is very long, you can refine the filter to show only jobs with your user ID as the job name. Do this now.

___ 5. Tab to the first job in the list. Enter the ? (Question mark) action code in the NP column and press Enter.

___ 6. This action shows the job elements as a list.


• • • ••



___ 7. Examine the first job element by putting the action code S next to it and pressing Enter. The first element is typically named JESMSGLG (JES2 message log). This file is where JES2 writes informational messages about the job during execution.

___ 8. Notice that part of the job element might be off the screen to the right. The screen is set to view 80 columns, and printer output (called SYSOUT) is typically 133 columns. Press F11 to scroll to the right. Press F10 to scroll back to the left.

___ 9. Put the cursor on some text in the middle of the screen. Press F11. The view is shifted relative to where the cursor was positioned. This technique is very useful for viewing just the part of the file that you want to see.

___ 10. Press F3 to return to the list of job elements. Examine the other elements.

___ 11. Examine the element named SYSUT2. This file is the output of the job you submitted. That job executed a utility that converted a partitioned data set member to a printable file.

___ 12. Press F3 until you return to the list of jobs. Enter action code S next to one of them and press Enter.

All of the job elements are presented as one continuous file. You can scroll or search the entire job this way. Be aware of the size of the files when you are listing the entire job in this manner. The number of records in each element can be seen at the far right side of the list of jobs. The column header is Tot-Rec.

___ 13. Press F3 to return to the list of jobs in the output queue.

Purge a job and its elements

___ 14. Assume that you do not want to keep one of the jobs. Tab to the command column next to one of the jobs and enter the action code P. This action opens a dialog asking that you confirm the command. Leave the selection set to 1, the default action, and press Enter. The job elements are purged from the JES2 spool and cannot be recovered. Press Enter again and the job you purged is no longer seen in the list.

You can put the P action by multiple jobs. You are prompted to confirm each one. It is not a good practice to select option 3 in the Confirm Action window. That option turns off the prompt and you could purge jobs by accident.

Look at the status of a started task

CICS Transaction Server is running on your lab system. Use SDSF to look at its status.

___ 15. Set the prefix filter to CICS*. Go to the Active queue (DA).


• • •••



___ 16. Use action code ? to list the job elements for CICS31T3 (the CICS terminal owning region).

___ 17. Select the JESMSGLG job element. The messages seen in JESMSGLG can also be found in the system log.

___ 18. Select the job element MSGUSR. This file contains messages written by CICS itself (as opposed to messages written by z/OS or JES2).

___ 19. Select the CEEMSG job element. SDSF responds by telling you that there is no data in that data set. An output element can be created but never written to, so this is not an unusual condition.

Look at z/OS console messages

You might need to enter console commands and not have access to a running console. Most z/OS and JES2 commands that you are authorized to run can be entered from SDSF.

___ 20. Type LOG in the command input field and press Enter. This action shows the z/OS console log (SYSLOG). One major difference between the SDSF SYSLOG and a master console (or any channel-attached console) is that SDSF console does not scroll automatically. You must press F8 or F7 to scroll down and up.

Note also that the SYSLOG is wider than will fit on the screen. The log file is 132 characters wide. You can scroll right and left using F11 and F10.

___ 21. Type M in the COMMAND INPUT field and press F7. This action scrolls to the top of the SYSLOG, where you can see messages about the environment. Sometimes it is very useful to see these messages about which PARMLIB members were used, for example.

___ 22. The SYSLOG is a data set, so it can be searched just like any other data set. Find the string:

‘control is being given’

Assuming that a CICS region is operational, this message is returned:

+DFHSI1517 CICS01 Control is being given to CICS.

That message is what system programmers look for to determine that CICS has successfully initialized and is ready for work.


• • • ••



Enter z/OS console commands

You can submit console commands from SDSF. Keep in mind that the console does not automatically scroll, so you might have to scroll down to find the results of a command.

___ 23. Commands are entered in the COMMAND INPUT field. Commands must be prefixed with a slash (/). Enter the command to list the currently-running jobs and tasks.

/D A,L

The response is a list of running address spaces, whether they are started tasks, batch jobs, or online uses.

___ 24. Display the VTAM major nodes.

/D NET,MAJNODES

The response is a list of VTAM nodes that are active.

Consult the z/OS operations library to see all of the commands. Be very careful submitting z/OS commands because some of them can have wide spread consequences.Press F1 and review the help information for SDSF.

End of Unit 5 exercises

• • • ••

6-1


Exercise 1 – Work with the z/OS UNIX shell

Introduction

This exercise provides an opportunity to work with the z/OS shell script OMVS. You will work within the shell environment to navigate file structures, browse and edit files, and run some UNIX commands to work with directories and files.

___ 1. Log onto TSO and run ISPF. Go to the ISPF Command shell (option 6) and type OMVS. Press Enter to start the shell script.

Wait until the shell environment is established. You will know that the shell is ready when you see the word RUNNING in the lower right part of the screen. RUNNING changes to INPUT after a few seconds, indicating the shell is waiting for you to do something.

___ 2. Change directories to where the Internet files are located:

cd /usr/lpp/internet

___ 3. List the contents of that directory using the list command with the long form:

ls -l

The command is the letters LS, space, minus sign, L. UNIX is case-sensitive, and commands must be entered in the proper case and spelling.

___ 4. You will see several directories. Change to the etc directory:

cd etc

Why did you not need a slash before the directory name?

Hint: Relative reference versus absolute reference

___ 5. List the contents of the etc directory. You will see a file named httpd.conf. That is the HTTP (Web) server configuration file. Browse the contents of that file using the OBROWSE shell command:

obrowse httpd.conf


• • • ••

Student Exercises for Unit 6Exercise 1 – Work with the z/OS UNIX shell


Note that it is important that you use proper case (capitalization). UNIX commands and names are case-sensitive.

Scroll forward and back a few times to see some of the HTTP server configuration values. The function keys are similar to those found in the ISPF environment.

Close the browser by pressing F3 or typing CANCEL on the command line.

___ 6. Change back to your personal directory one step at a time:

cd ..

until you get to the root (/), then change to your own user directory, where NN is the numeric part of your user ID.:

cd /u/userNN

___ 7. Create a new directory called test:

mkdir test

___ 8. Change to that directory and list its contents (it will be empty):

cd testls -l

___ 9. Use the oedit shell to create a files called myFile.txt (mixed case names like myFile are common in UNIX):

oedit myFile.txt

___ 10. Type a few lines of text into the edit shell and press Enter. You will observe that the editor behaves very much like the ISPF editor (because it is the ISPF editor). Press F3 to save your file and close the editor.

___ 11. Do another file list using the long form (ls -l). What do the permissions flags tell you?

-rwx------

Only the file owner (you) can read, update, or execute the file. No one else (except super users) can read or update the file.

___ 12. Navigate back to the /usr/lpp/internet/etc directory. List the contents and observe that the file socks.conf has permissions set such that it can be read but not updated by anyone (except a super user). Run the oedit shell on socks.conf and see what happens:

oedit socks.conf

___ 13. Make a small change to the file and press F3 to save it. What happens?


• • •••

Student Exercises for Unit 6Exercise 2 – Work with the ISPF Shell


___ a. You will receive an error message saying that you tried to write to a file opened as read-only.

___ b. When you press Enter you go back to the editor shell. Press F12 or type CANCEL on the command line, respond to the prompt, and return to the OMVS shell.

___ 14. Navigate back to your personal directory (/u/userNN) and run some more UNIX commands.

___ a. Copy myFile.txt as anotherFile.text

cp myFile.txt anotherFile.text

___ b. Print the contents of anotherFile.text to the terminal:

cat anotherFile.text

Only use the cat command on small files.

___ c. Delete both of the files that you created (myfile.txt and anotherFile.text). You can delete multiple files using wild cards but be very careful doing so as there is no “do you really want to” prompt:

rm *.t*

___ 15. Remove the directory you created earlier (you will have to back up in the tree one level):

rmdir test

___ 16. Exit the OMVS shell and return to ISPF by typing EXIT on the command line and responding to the prompt.

Exercise 2 – Work with the ISPF Shell

Introduction

In this exercise you will use the ISHELL to perform several of the same tasks that you just completed with OMVS. This provides you an opportunity to see different methods of accomplishing the same task and you can decide which you prefer. You will also use one of the ISHELL tools to examine the mounted file systems.

___ 1. Type ISHELL (or just ISH) on the ISPF command line (option 6) and press Enter to run the ISPF shell.


• • • ••



___ 2. You will see a series of actions across the top of the panel. The navigation is similar to that of ISPF where you press F10 to get to the action bar (or just use the cursor keys or the mouse).

Go to the Options action and press Enter to list the action menu. Select number 2, Default actions.

Default actions are what happens when you select a file on the directory list panel and press Enter. Press F1 for help to see what the actions mean for the different types of resources. Close the help panel and then close the default action menu to return to the pathname panel.

___ 3. Type the path to get to the same directory you used in the OMVS exercise and press Enter:

/usr/lpp/internet/etc

___ 4. Remember that the default action for a file was set to browse? Type a slash next to httpd.conf and press Enter to perform the default action.

If you type a slash next to the file and then select the File action, you will see a menu of actions you can use. If you had selected a directory instead of a file, you would open the Directory action instead.

As you gain familiarity with the command structure you will find that you use the action command directly instead of opening a menu. You will quickly learn the more commonly used commands such as B for browse, E for edit, L for list directory, and so on.

___ 5. Return to the path list panel by closing the editor, then pressing F3. Type the name of your home directory (/u/user1) on the path field and press Enter. You will see that your home directory is empty except for a special file named .sh_history (shell command history). You can browse this file to see a history of the UNIX commands you have entered.

___ 6. Create a new directory in your home path called ispf. Start from the main pathname panel. Type the complete name of the new directory in the pathname field (/u/user1/ispf) and press Enter.

The Create a New File dialog appears (remember: a directory is a file that contains the names of other files). Set the permissions to 600 for now, type 1 for directory in the file type field, then press Enter. Your new directory is created.

___ 7. Create a new file called myExercise.txt in the ispf directory. On the main path name panel, type the complete name of the new file (/u/user1/ispf/myExercise.txt) and press Enter. What happens? Why is permission to create the new file denied?

___ a. Go back and list your home directory (/u/userNN). Type a slash next to the ispf directory, place the cursor on the Directory action bar and press Enter.


• • •••



Type the action code for Attributes and press Enter again. Look at the file permissions. What does 600 mean? It means that the file owner (you) can read and update (4 + 2) the directory but not search it. You must have permission to search a directory in order to create files in it.

___ b. Place your cursor on the Edit action at the top of the Display File Attributes panel and press Enter. Select Mode fields and then change the 600 to 700 and press Enter. Press F3 to exit the dialog and return to the Directory List, where you will be able to add files since you have given yourself appropriate permissions. Add the file myExercise.txt and edit it to create a few lines of text. Close the file and return to home directory list. You will see the new file in the list.

___ 8. Copy your new file to an MVS data set.

___ a. Select the new file and open the File actions menu (type slash next to the file name, place the cursor on File action and press Enter). Select the Copy To action and press Enter.

___ b. Select Data set on the next dialog. Remember: File is a UNIX term, data set is an MVS term. Leave the additional options blank and press Enter.

___ c. Type a name for your MVS file on the next panel, such as FILE.COPY. It must be a data set that you are authorized to create. Your user ID becomes the first node in the data set name unless you wrap the name in quotation marks. It is usually safe to create a data set whose high level qualifier is your TSO user ID. Press Enter and your UNIX file will be copied to an MVS data set.

___ d. Split your ISPF screen by pressing F2, then navigate to where you can browse your new MVS data set. You will see that it contains the same text as the UNIX file.

___ e. Use ISPF to view information on your new file (=3.4, then type S next to the data set name and press Enter). Find the Record format, Record length, and Block size values. Notice that the record format is VB, which means blocked variable length records. The record length is 255 and the block size is 32760. These are arbitrary values used by the shell if the MVS data set is not preallocated.

___ 9. Next you will view information about mounted file systems. Return to the IShell path list panel and place the cursor on the File Systems action. Press Enter to view the actions menu. Notice the informational message you receive about some actions needing super user or a special attribute. This indicates that the shell has detected that your user ID is not a super user.

___ 10. Type the action code for the Mount Table (action 1) and press Enter. You will see the list of mounted file systems and their data set names.

___ 11. Scroll to the file system that contains users’ data (OMVS.U in the demonstration). Type the action code for Attribute and press Enter. Notice that the Mount Point is /u. Look at the list of attributes and find the Mount Mode. R/W means read and


• • • ••



write. In other words, uses can write to files in this file system. Close the File Systems panel by pressing F12.

___ 12. View the Mount Table again and select attributes for one of the Java file systems (AJV.V1R4M0.HFS in the demonstration). Notice the Mount Point, then find the Mount Mode. Notice that it is set to R/O, which means Read Only. Users cannot write to files or directories in this file system.

This concludes the exercises.

It is a good idea to clean up your environment before logging off your sessions by deleting any files or directories that you created.

zos fundamentals se

Documents