es10bstud

Enterprise Computing Solutions

Business Intelligence

Data Centre Cloud Mobility

Comunidad de Madrid

Dirección General de Formación

CONSEJERÍA DE EMPLEO,TURISMO Y CULTURA

UNIÓN EUROPEAFONDO SOCIAL EUROPEO

El Fondo Social Europeo invierte en tu futuro

EDUCATIONS E R V I C E S

Student Manual

V8.0

cover

Exclus

ivo fo

r

proy

ecto

Front cover

Fundamental System Skills in z/OS (Course code ES10)

Student NotebookERC 11.0

mación

C.F.T.I.C.

Student Notebook

.

Trademarks

IBM® is a registered trademark of International Business Machines Corporation.

The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in the United States, and/or other countries.

Pentium is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Windows is a trademark 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.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

AIX/ESA AIX BookManagerC/370 CICS DataPowerDB2 ESCON eServerFICON HiperSockets IMSLanguage Environment MVS Open ClassOS/390 Parallel Sysplex PowerPOWER7 PR/SM RACFResource Measurement Facility

RMF S/390

SecureWay System x System zSystem z10 System z9 System/390VTAM WebSphere z/Architecturez/OS z/VM z/VSEzEnterprise zSeries z10z9

xclus

ivo fo

rmac

ión

yecto

C.F.T.I.C

June 2013 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.

© Copyright International Business Machines Corporation 2001, 2013.This document may not be reproduced in whole or in part without the prior written permission of IBM.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 Corp.

E pr

o

Student Notebook

.

Other product and service names might be trademarks of IBM or other companies.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C

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

iii z/OS Fundamentals © Copyright IBM Corp. 2001, 2013

Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


iv z/OS Fundamentals © Copyright IBM Corp. 2001, 2013

Student NotebookV8.0

TOC

E

Contents

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Unit 1. Review of the z/Architecture and z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.1. z/Architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5z/Architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7z/Architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8IBM Mainframe operating systems (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10IBM Mainframe operating systems (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12z/Architecture for System z servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14IBM zEnterprise EC12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15IBM zEnterprise 196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17IBM zEnterprise 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19IBM System z10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21IBM System z10 BC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23IBM System z9 BC and EC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25IBM System z: System design comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27z/OS highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Processor types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Logical partitioning and partitioning with zVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

1.2. z/OS system overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35z/OS system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37z/OS system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38z/OS functional groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39The concept of virtual storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41Virtual storage and zArchitecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43Address space, data space, and hiperspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44Address space layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46At execution time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47Job entry subsystem (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48Job entry subsystem (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50Catalog management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51System-managed storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52TSO, ISPF, and ISPF/PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54Establishing a TSO session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55Time sharing option/extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56Interactive System Productivity Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Contents v

Student Notebook

.

Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-59Checkpoint (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-60Checkpoint (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-61Checkpoint (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-62Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-63

Unit 2. An introduction to ISPF, ISPF/PDF, and RACF . . . . . . . . . . . . . . . . . . . . . . . .2-1Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.1. ISPF and ISPF/PDF overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5ISPF and ISPF/PDF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7ISPF and ISPF/PDF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8Dialog Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10Panel hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11Program Development Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12General structure of ISPF/PDF panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14Navigating in ISPF/PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15The jump function and command stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-17Action bar menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-18Pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19Option 0: Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20Option 1: View a data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-22Option 2: Edit data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-23Option 3: Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24Option 6: ISPF Command Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26Option S: System Display and Search Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-28Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29

2.2. Security in a z/OS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31Security in a z/OS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-33Security in a z/OS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34Data security is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36Security Server RACF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-37Security in a distributed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-38Distributed signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40System without RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42System with RACF: User authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43Password and password phrase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44User profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-47Security Server RACF group terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-48Resource authorization checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49Resource managers and RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-50RACF resource profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-51Access authorities for data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-52Example: Authorization checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-54Protecting catalogs example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-55

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


vi z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


TOC

E

PROTECTALL (Protect - all) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Logging and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57RACF major functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58RACF - Services Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59RACF - Group Profile Services panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60RACF - Display for Group Profile panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Display of a group profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62RACF - User Profile Services panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63RACF - Display for User Profile panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64RACF display user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65User and group data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66Data set profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67Discrete and generic profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Generic versus discrete profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69PERMIT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75

Unit 3. Working with ISPF/PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1. Allocating data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Allocating data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Allocating data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Record format and blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7z/OS data set types (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8z/OS data set types (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9VSAM data set types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Data set naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Partitioned data set naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Data set naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Entering data set and library names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Entering member names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18ISPF Primary Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Utility Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Data Set Utility panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Allocate New Data Set panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Data set allocation panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Data Set Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

3.2. Editing data sets: The ISPF/PDF editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Editing data sets: The ISP/PDF editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Editing data sets: The ISPF/PDF editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Edit member selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Contents vii

Student Notebook

.

ISPF/PDF editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35ISPF/PDF profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38More scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39Scrolling left and right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40Split screen (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41Split screen (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-42Resplit screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43Swap the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44SWAPBAR system command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45SWAPBAR example (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-46SWAPBAR example (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-47Save and cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48FIND command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-49FIND command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50BOUNDS and EXCLUDE commands (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52BOUNDS and EXCLUDE commands (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53CHANGE command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55CHANGE command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-56CREATE command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-58CREATE command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-59COPY command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-61COPY command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-62SORT command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-63SORT command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-64Additional primary commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-65More primary commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-67Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-68Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-69

3.3. Editing data sets: Line commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-71Editing data sets: Line commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-72Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-73Editing data sets: The ISPF/PDF editor line commands . . . . . . . . . . . . . . . . . . . . .3-74Prefix area commands: Copy, move, and repeat a single line . . . . . . . . . . . . . . . .3-75Prefix area commands: Copy and move over . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-76Prefix area commands: Copy, move, and repeat multiple lines . . . . . . . . . . . . . . .3-77Prefix area commands: Insert or delete a single line . . . . . . . . . . . . . . . . . . . . . . .3-78Prefix area commands: Insert or delete multiple lines . . . . . . . . . . . . . . . . . . . . . .3-79COLS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-80Cut and paste (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-82Cut and paste (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-83Cut and pasted result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-84Additional line commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-85Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-87Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-88

3.4. Copying, moving, renaming, deleting data sets and data set members . . . . . . . . .3-89Copying, moving, renaming, deleting data sets and data set members . . . . . . . . .3-90Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-91

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


viii z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


TOC

E

Copying and moving data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92Move/copy utility: Specifying the “to” data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93Copy/move complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94Copy/move member: Specifying the “from” data set . . . . . . . . . . . . . . . . . . . . . . . 3-95Copy/move member: Specifying the “to” data set . . . . . . . . . . . . . . . . . . . . . . . . . 3-96Member selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97Copy/move complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98Renaming a data set or member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99Data Set Utility panel: Specifying the new data set name . . . . . . . . . . . . . . . . . . 3-100Data Set Utility panel: Successful data set rename . . . . . . . . . . . . . . . . . . . . . . 3-101Library Utility panel: Specifying the old member name . . . . . . . . . . . . . . . . . . . . 3-102Rename member complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103Deleting a data set or member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104Confirm Delete pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105Data set deleted message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106Library Utility panel: Specifying the member to be deleted . . . . . . . . . . . . . . . . . 3-107Confirm Member Delete pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108Member deleted message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111

3.5. Working with data set lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113Working with data set lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115Working with data set lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116DSLIST display panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-117Data Set List Actions pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119Block commands in Data Set List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120Block commands in Data Set List: Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122Checkpoint (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123Checkpoint (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124Checkpoint (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

Unit 4. Working with TSO/E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.1. TSO/E commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3TSO/E commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4General notation of a TSO/E command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6The HELP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7The ALLOCATE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9The DELETE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12The LISTDS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14The LISTCAT command (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16The LISTCAT command (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19The LISTALC command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21The FREE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Contents ix

Student Notebook

.

The PRINTDS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26The PROFILE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-28The SUBMIT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-30The SEND command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32The TRANSMIT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-34The RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36How to issue TSO/E commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40

Unit 5. Working with JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1Unit objectives (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3Unit objectives (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

5.1. JES2 job processing phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5JES2 job processing phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7Job entry subsystem (JES2 and JES3) overview . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8JES2 job processing phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9JES3 job processing phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11Job input phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13Job conversion phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14Job execution phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15Job output and purge phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17

5.2. Introduction to job control language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19Introduction to job control language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-20Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21Introduction to job control language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22General layout of a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23General layout of a JCL statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24The identifier field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26The name field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27The operation field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28The parameter field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30Positional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31Keyword parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32Comment field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-33Statement continuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34Three major types of JCL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36The JOB statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-37Examples of JOB statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-39The EXEC statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-40Examples of EXEC statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42The DD statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-43Examples of DD statements (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-46Examples of DD statements (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-47In-stream data (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-48

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


x z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


TOC

E

In-stream data (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49IF/THEN/ELSE/ENDIF statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Keywords, operators of IF/THEN/ELSE/ENDIF . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51IF/THEN/ELSE/ENDIF example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

5.3. The Outlist Utility and SDSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55The Outlist Utility and SDSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57The Outlist Utility and SDSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58ISPF/PDF option 3.8: Outlist Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59Displaying job names and job IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60Display job output with PDF option 3.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61System Display and Search Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62Display the JES2 held output queue with SDSF . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63Display job’s held output with SDSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

5.4. JCL Utility overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69JCL Utility overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71JCL Utility overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72IEFBR14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74Common utility DDnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75IEBCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77Copying using IEBCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Renaming and replacing data set members with IEBCOPY . . . . . . . . . . . . . . . . . 5-81Compressing a PDS with IEBCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83IEBGENER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85Creating a backup copy with IEBGENER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Deleting data sets with IDCAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87DFSORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-88DFSORT utility DDnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91The SORT process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92SORT JCL example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95

5.5. Introduction to JCL procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97Introduction to JCL procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99Introduction to JCL procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100Types of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101Procedure usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103Example of an in-stream procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104Calling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105Procedure search order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106Specifying private proclibs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Overriding procedure statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108JCL symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-110

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Contents xi

Student Notebook

.

INCLUDE groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114Checkpoint (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-115Checkpoint (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116Checkpoint (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117Checkpoint (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-118Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Unit summary (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120Unit summary (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-121

Unit 6. Working with UNIX System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.1. UNIX System Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3UNIX System Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5UNIX System Services: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6UNIX applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8What are the benefits of UNIX services? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9Access to shell and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10Network access to the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11TSO/E and the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12Shell and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13OMVS TSO/E command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14The shell screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16Asynchronous terminal access to shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17The shell screen for the async user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18Accessing files from the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19Shell command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20TSO/E interface to UNIX services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-21ISPF shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22ISHELL directory menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-23z/OS UNIX directory list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-24z/OS UNIX Directory List Utility entry panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-25z/OS UNIX Directory List panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-26Horizontal scrolling through RIGHT and LEFT commands/column order and size 6-27Line commands available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-28Create New z/OS UNIX File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30Copy From z/OS UNIX File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31Copy From z/OS UNIX Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32Replace z/OS UNIX File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-33Copy Into z/OS UNIX Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-34z/OS UNIX File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35Modify z/OS UNIX File Mode Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36Execute Command for z/OS UNIX File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-37Native ISPF edit and browse z/OS UNIX files . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-38Edit and browse z/OS UNIX files: Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-40View Entry Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-41Edit Entry Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


xii z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


TOC

E

TSO and shell interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44Commands and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45Accessing files from TSO/E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46File copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48

6.2. UNIX System Services files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49UNIX System Services files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51UNIX System Services files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52HFS and zFS as UNIX file systems in z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54File types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55Files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56HFS data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57HFS data set characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58File system structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59Path name and file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61File identification comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62File system structure comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63File access comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-64HFS / UNIX file creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65JCL support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66Allocate HFS (root file system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67Format a zFS aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68JCL example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70

6.3. UNIX System Services: Program support and security . . . . . . . . . . . . . . . . . . . . . 6-71UNIX System Services: Program support and security . . . . . . . . . . . . . . . . . . . . . 6-72Topic objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73UNIX System Services program support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74Program file operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75NFS support for UNIX System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76UNIX pipes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77The BPXBATCH utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78Submitting jobs: The submit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79Standard input, output, and error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80TSO and shell comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82What is a socket? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83Sockets example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84UNIX System Services security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86UNIX System Services users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87File security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89Permission bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-90Topic summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91Checkpoint (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92Checkpoint (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93Checkpoint (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Contents xiii

Student Notebook

.

Appendix A. Checkpoint solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. z/OS documentation and information center . . . . . . . . . . . . . . . . . . . B-1

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


xiv z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


TMK

E

Trademarks

The reader should recognize that the following terms, which appear in the content of this training document, are official trademarks of IBM or other companies:

IBM® is a registered trademark of International Business Machines Corporation.

The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in the United States, and/or other countries.

Pentium is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Windows is a trademark 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.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.

AIX/ESA® AIX® BookManager®C/370™ CICS® DataPower®DB2® ESCON® eServer™FICON® HiperSockets™ IMS™Language Environment® MVS™ Open Class®OS/390® Parallel Sysplex® Power®POWER7® PR/SM™ RACF®Resource Measurement Facility™

RMF™ S/390®

SecureWay™ System x® System z®System z10® System z9® System/390®VTAM® WebSphere® z/Architecture®z/OS® z/VM® z/VSE®zEnterprise™ zSeries® z10™z9®

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Trademarks xv

Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


xvi z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


pref

E

Course description

Fundamental System Skills in z/OS

Duration: 4 days

Purpose

This course is designed to teach students the fundamental practical skills to navigate and work in a z/OS environment.

This includes the use of ISPF/PDF dialogs, TSO/E commands, JCL, UNIX System Services shell, and BookManager.

Audience

The intended audience for this class is IT personnel with a theoretical background of z/OS (for example, as taught in ES05) and some general practical IS experience.

Prerequisites

ES05, An Introduction to the z/OS Environment or equivalent on-the-job training.

Objectives

After completing this course, you should be able to:

• Review the main concepts of z/OS

• Log on to TSO and start ISPF/PDF

• Navigate through ISPF/PDF dialogs and use the basic ISPF/PDF functions and the ISPF Editor

• Use ISPF/PDF to allocate data sets and edit data sets (including hierarchical file system (HFS) files) via the ISPF Editor primary and line commands

• Use ISPF to create and manipulate (copy, rename, delete, list, sort and merge) data sets

• Identify security considerations for Multiple Virtual Storage (MVS) data sets and HFS files

• Describe and use TSO/E commands

• Perform simple modifications to existing ISPF/PDF panels

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Course description xvii

Student Notebook

.

• Invoke a REXX exec and TSO CLIST

• Tailor existing JCL and submit batch jobs

• Review job status and job output using SDSF

• Invoke UNIX processes

• Manipulate HFS directories and file systems using the UNIX System Services ISHELL

Contents

This course consists of a mixture of theoretical and practical sections. The major objective of the course is to familiarize the students with the everyday activities involved in working in a z/OS environment.

The main focus is, therefore, on the class exercises.

ES10 teaches the students:

• How to log on to the z/OS system

• How to work with TSO/E, ISPF/PDF and the UNIX System Services shell

• How to create, copy, rename and delete MVS data sets

• How to work with UNIX System Services files

• How to execute CLISTs and REXX execs

• How to submit jobs for execution and view the output online

• How to use BookManager and the InfoCenters to search softcopy publications

Curriculum relationship

ES05 An Introduction to the z/OS Environment

H3838 z/OS JCL and Utilities

ES52 z/OS REXX Programming Workshop

OP05 Introducing z/OS UNIX System Services Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


xviii z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


pref

E

Agenda

Day 1

Welcome Unit 1: Review of the z/Architecture and z/OS Unit 2: An Introduction to ISPF, ISPF/PDF, and RACFExercise 1: System familiarizationUnit 3: Working with ISPF/PDF (Part 1) Exercise 2: Allocate new data sets

Day 2

Review/wrap upUnit 3: Working with ISPF/PDF (Part 2) Exercise 3: ISPF editor primary commandsExercise 4: ISPF editor line commandExercise 5: Copy/move/rename/delete data sets and membersExercise 6: Data set listsUnit 4: Working with TSO/E Exercise 7: Using TSO/E commands

Day 3

Review/wrap upUnit 5: Working with JCL Exercise 8: Submit a jobExercise 9: JCL exercises

Day 4

Review/wrap upUnit 6: Working with UNIX System Services Exercise 10: ProceduresExercise 11: ISHELL and hierarchical file systemxc

lusivo

form

ación

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Agenda xix

Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


xx z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


Uempty

E

Unit 1. Review of the z/Architecture and z/OS

What this unit is about

This unit reviews the basic concepts of the z/Architecture and the z/OS operating system at the level of knowledge that is required or helpful in understanding the education presented in the units of this course.

What you should be able to do

After completing this unit, you should be able to:

• Identify the operating systems and IBM mainframes supporting the z/Architecture

• Describe the partitioning capabilities used with z/Architecture • Name the functional groups that comprise z/OS • Explain the concept of virtual storage and how it is used in z/OS • Indicate how work is managed in a z/OS system • Identify the different kinds of catalogs and discuss DFSMS DASD

management in z/OS • Describe the main end-user interfaces of z/OS

How you will check your progress

• Checkpoint questions

References

SC26-7397 DFSMS Introduction

GA22-7502 z/OS Introduction and Release Guide

GA22-7504 z/OS Planning for Installation

SA22-7500 z/OS Information Roadmap

SA22-7535 JES2 Introduction

SA22-7551 JES3 Introduction

SA22-7661 Parallel Sysplex Overview: An Introduction to Data Sharing

GC35-0033 Device Support Facilities R17 (ICKDSF r17) Guide and Reference

SA22-7832 z/Architecture Principles of Operation

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 1. Review of the z/Architecture and z/OS 1-1

Student Notebook

.

SC26-7409 DFSMS Managing Catalogs

SA22-7643 MVS Program Management: User’s Guide and Reference

SC26-7410 DFSMS Using Data Sets

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


1-2 z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


Uempty

E

Figure 1-1. Unit objectives ES1011.0

Notes:

US Government Users Restricted Rights - Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp© Copyright IBM Corporation 2001, 2013. All Rights Reserved.

Unit objectives After completing this unit, you should be able to:• Identify the operating systems and IBM mainframes supporting

the z/Architecture• Describe the partitioning capabilities used with z/Architecture• Name the functional groups that comprise z/OS• Explain the concept of virtual storage and how it is used in

z/OS• Indicate how work is managed in a z/OS system• Identify the different kinds of catalogs and discuss DFSMS

DASD management in z/OS• Describe the main end-user interfaces of z/OS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

1.1. z/Architecture overview

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-2. z/Architecture overview ES1011.0

Notes:


z/Architecture overview


z/OS system overview

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-3. Topic objectives ES1011.0

Notes:


Topic objectivesAfter completing this topic, you should be able to:• Identify the operating systems and IBM mainframes supporting

the z/Architecture• Describe the partitioning capabilities used with z/Architecture

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-4. z/Architecture overview ES1011.0

Notes:

z/Architecture is an extension to the System/360 (S/360), System/370 (S/370), System/390 (S/390), and ESA/390 architectures. z/Architecture was announced in late 2000 as the next generation of architecture.

The z/Architecture is a blueprint providing a set of definitions and rules required for the interaction of z/Architecture hardware with an operating system control program that coordinates the use of system resources, executes all I/O instructions, handles exceptional conditions, and supervises scheduling and execution of multiple programs. z/Architecture determines processor instruction sets, addressing range and modes, communication mechanisms such as interrupts, and so on. It lays the groundwork for every System z server and every operating system running on it.

z/Operating System (z/OS) is the IBM flagship operating system designed to run on a z/Architecture platform. In total there are five operating systems that are supported on the IBM mainframes. They are the z/OS, z/VSE, z/TPF and Linux for System z.

z/OS supports great numbers of users along with large amounts of data while still providing reasonable performance.



ESA/390 Architecture

z/Architecture hardware

z/Architecture software

z/VM

IBM System z servers

z/VSE

z/Architecture

Linux on System z

z/TPFz/OS

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

The design of the z/Architecture still incorporates an evolutionary approach, meaning, even though it grows in functionality, it still provides a high degree of compatibility with its ancestors, ESA/390, System/390, System/370, and System/360.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-5. IBM Mainframe operating systems (1 of 2) ES1011.0

Notes:

There are five operating systems that are supported on the IBM mainframes. Identified here are the z/OS, z/VSE and z/TPF operating systems that are developed and supported by IBM.

The z/OS operating system is IBM’s premier flagship OS. It is the most widely used mainframe OS in business today. z/OS is built for a wide variety of workloads, online transaction processing (OLTP), batch and even analytics. IBM provides extensive support, backward compatibility and OS migration assistance that is the best in the industry. z/OS is a highly secure, scalable, high-performance enterprise operating system on which to build and deploy Internet and Java-enabled applications, providing a comprehensive and diverse application execution environment.

z/VSE would be used by smaller shops that does not need the high Quality of Service (QoS) that z/OS provides. Compared to z/OS, the z/VSE operating system provides a smaller, less complex base for batch processing and transaction processing. The design and management structure of z/VSE is excellent for running routine production workloads consisting of multiple batch jobs (running in parallel) and extensive, traditional transaction


IBM Mainframe operating systems (1 of 2)• z/OS

– IBM’s premier operating system, most widely used, contains the highest QoS of any OS.

– z/OS is known for its ability to serve thousands of users concurrently and for processing large workloads in a secure, reliable, and expedient manner.

• z/VSE: z/Virtual Storage Extended– Used in smaller mainframe shops, does not contain all the QoS as

z/OS, and provides a smaller, less complex base for batch processing and transaction processing.

• z/TPF: z/Transaction Processing Facility– Special-purpose system that is used by companies with high

transaction volume, such as credit card companies and airline reservation systems.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

processing. In practice, most z/VSE users also have the z/VM operating system and use this as a general terminal interface for z/VSE application development and system management.

The z/TPF system is a high availability operating system designed to provide quick response times to high volumes of messages from large networks of terminals and workstations. It is most commonly used for the purpose of accessing a large centralized database that is an inventory of business information. An example of this would be a reservation system that is used for large hotels or airlines.

z/TPF was once known as Airline Control Program (ACP). It is still used by airlines and other business that require high-speed, high-volume transaction processing requirements.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-6. IBM Mainframe operating systems (2 of 2) ES1011.0

Notes:

Here the remaining two supported mainframe operating systems are identified, z/VM and Linux on System z.

As a control program, z/Virtual Machine (z/VM) is a hypervisor because it runs other operating systems in the virtual machines it creates. It is provided and supported by IBM.

z/Virtual Machine (z/VM) has two basic components: a control program (CP) and a single-user operating system (CMS). The control program artificially creates multiple virtual machines from the real hardware resources. To users, it appears as though they have dedicated use of the shared real resources. The shared real resources include printers, disk storage devices, and the central processors. The control program ensures data and application security among the guest systems. The real hardware can be shared among the guests, or dedicated to a single guest for performance reasons. The system programmer allocates the real devices among the guests. For most customers, the use of guest systems avoids the need for larger hardware configurations.


IBM Mainframe operating systems (2 of 2)• z/VM: z/Virtual Machine

– The z/VM control program is a hypervisor that can run other operating systems in the virtual machines it creates.

– Any IBM OS, such as z/OS, Linux on System z, z/VSE, and z/TPF, can be run as guest systems in their own virtual machines, and z/VM can run any combination of guest systems.

• Linux on System z– UNIX-like OS assembled under the model of free and open source

software development and distribution.– Several Linux distributions can be used on a mainframe. There are

two generic names for these distributions:• Linux on S/390 (uses 31-bit addressing and 32-bit registers)• Linux on System z (uses 64-bit addressing and registers)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

z/VM’s other major component is the Conversational Monitor System (CMS). This component of z/VM runs in a virtual machine and provides both an interactive user interface and the general z/VM application programming interface.

Linux on System z is used to refer to Linux running on a System z system. It does not specifically refer to a 31-bit version or the 64-bit version. Linux on System z exploits the strengths and reliability features of the System z hardware, while preserving the openness and stability of Linux. Linux on System z distributions are offered by Linux distribution partners who provide services and support.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-7. z/Architecture for System z servers ES1011.0

Notes:

64-bit addressing mode is actually two things: Real and virtual 64-bit addressing. 64-bit real addressing came first; virtual 64-bit addressing came later in z/OS. z/OS must run on z/Architecture in 64-bit mode.

Starting in z/OS release 2, system software packages started to use the increased virtual address range for buffers, status areas, and management functionality. User applications created by standard compilers, however, could not exploit this storage for their own purposes. The C and C++ compilers can be used to create 64-bit applications.

In z/OS release, many components support 64-bit AMODE 64:

• Workload Manager (WLM) Virtual 64-bit support provides services to 64 bit applications

• z/OS UNIX enables C interface for usages for 64-bit applications

• Language Environment provides a 64-bit run-time environment

• z/OS has a 64-bit C/C++/Java programming environment

• And a 64-bit C/C++ compiler and debugger


z/Architecture for System z servers• z/Architecture is a 64-bit superset of ESA/390.

• The addressing range moves from 2 GB to 16 EB (billion billion).– That is 16,000,000,000,000,000,000.

• This architecture has been implemented on the architecture processors to allow full 64-bit real and virtual storage support.

• There is 64-bit virtual and real storage support.

• Application programs are written in C or C++ can execute in 64-bit virtual mode.

IBM zEnterprise 196 (z196)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-8. IBM zEnterprise EC12 ES1011.0

Notes:

The IBM zEnterprise EC12, machine type of 2827 with five model offerings (H20, H43, H66, H89, and HA1), builds upon the strengths of its predecessor, the IBM zEnterprise 196. It was designed to help overcome problems in today's IT infrastructures and provide a foundation for the future. The zEC12 continues the evolution of integrated hybrid systems beginning with the z196.

The zEC12 central processor complex (CPC) has a redesigned z/Architecture chip. It is the first six-core chip in mainframe history and operates at an industry leading, high frequency, 5.5 GHz. The zEC12 is a scalable symmetric multiprocessor (SMP) that can be configured with up to 101 processors running concurrent production tasks with up to 3 TB of memory. It introduces several PCIe I/O features, such as exploitation of Storage Class Memory through the Flash Express feature, and technologies, such as the IBM System z Advanced Workload Analysis Reporter (IBM zAware), an appliance with cutting edge pattern recognition analytics that uses “heuristic techniques” and represents the next generation of system health monitoring.


IBM zEnterprise EC12• Processor

– Up to 101-way– 5.5 GHz superscalar – 60 LPARs– Unified Resource Manager

• Memory– Up to 3 TB for server, new cache levels and

up to 1 TB per LPAR– Optional storage class memory (Flash

Express)• Channels

– Four LCSSs– PCIe and InfiniBand I/O infrastructure– Three subchannel sets– FICON Express4, Express8 and 8S– HiperSockets: Up to 32

• Announce 8/12: Server with up to 120 PU cores– Five models: Up to 101-way– PU (Engine) characterization

• CP, SAP, IFL, ICF, zAAP, zIIP– On Demand capabilities

• CoD, CIU, CBU, On/Off CoD, CPE• Optional zAWARE LPAR

zEnterprise EC12 (zEC12)Machine type: 2827

Five models: M20, H43, H66, H89, and HA1

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Flash Express is an innovative optional feature introduced with the zEC12, with the objective of driving performance improvements and better availability for critical business workloads that cannot afford any hits to service levels. It implements Storage Class Memory (SCM) in a PCIe card form factor using internal NAND Flash solid state disk (SSD) providing a total maximum capacity of 6.4 TB of storage that can be used for paging. Each PCIe card has a capacity of 1.6 TB of usable storage, are installed in pairs providing mirrored data to ensure a high level of availability and redundancy.

The zEC12 goes beyond previous designs while continuing to enhance the traditional mainframe qualities, delivering unprecedented performance and capacity growth. The zEC12 has a well-balanced general-purpose design that allows it to be equally at ease with compute-intensive and I/O-intensive workloads

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-9. IBM zEnterprise 196 ES1011.0

Notes:

The IBM zEnterprise 196 is designed with improved scalability, performance, security, resiliency, availability, and virtualization. The z196 Model M80 provides up to 1.6 times the total system capacity of the z10 EC Model E64, and all z196 models provide up to twice the available memory of the z10 EC.

zEnterprise System is designed to deliver:

• Improved total system capacity in a 96-way core design.

• Up to 80 cores that are customer-configurable.

• Quad-core 5.2 GHz processor chips with 100+ new instructions that enable improved code efficiency, and are designed to help improve the execution of CPU-intensive workloads.

• Up to 3 terabytes (TB) of available real memory per server for growing application needs (with up to 1 TB real memory per LPAR).

• Availability in the memory subsystem with redundant array of independent memory (RAIM).


IBM zEnterprise 196• Processor

– Up to 80-way– 5.2 GHz superscalar – 60 LPARs– Unified Resource Manager

• Memory– Up to 3 TB for server and

up to 1 TB per LPAR• 16 GB fixed HSA

• Channels– Four LCSSs– Three subchannel sets– 63.75 subchannels– Up to 240 ESCON channels– Up to 288 FICON channels– FICON Express4 and 8– InfiniBand Coupling Links– HiperSockets: Up to 32

• Announce 7/10: Server with up to 96 PU cores– Five models: Up to 80-way– PU (Engine) characterization

• CP, SAP, IFL, ICF, zAAP, zIIP– On Demand capabilities

• CoD, CIU, CBU, On/Off CoD, CPE

zEnterprise 196 (z196)Machine type: 2817

Five models: M80 M66 M49 M32 M15

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

• Up to 128 coupling CHPIDs (double that of z10) and up to 80 physical external coupling links (12x InfiniBand, 1x InfiniBand, ISC-3), a 25% increase compared to z10.

• Up to 72 I/O, networking, and crypto features.

• Up to 240 ESCON channels.

• Up to 32 HiperSockets (double the number available on z10 EC).

• Optional water cooling, providing the ability to cool systems with user-chilled water.

• Unified Resource Manager, enabling management and virtualization of heterogeneous workloads. Unified Resource Manager manages the deployment of heterogeneous hardware resources based on individual workload requirements by providing:

- Performance management - Integrated private data network - Virtual server lifecycle management - Hypervisor management - Integrated operational controls - Management as system z firmware

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-10. IBM zEnterprise 114 ES1011.0

Notes:

The z114 continues the heritage in mainframe qualities of service with extreme granularity. structure and significant improvements in packaging, performance, and total system scalability over prior generations.

More processing capacity and performance: System resources are powered by up to 14 microprocessors running at 3.8 GHz. The z114 provides up to an 18% improvement in uniprocessor performance and up to a 12% increase in total system capacity for z/OS, z/VM, z/VSE, and Linux on System z workloads as compared to its predecessor, the z10 BC.

Its superscalar microprocessor chip has a higher-frequency design that leverages IBM technology leadership with a new out-of-order execution sequence that delivers world-class per-thread performance. With over 100 new instructions and numerous compiler related enhancements, the z114 can deliver up to 25% performance improvement, based on measurements and projections, for CPU Intensive workloads when accompanied by multiple C/C++ compiler level improvements going from XL C/C++ V1R9 to V1R12.


IBM zEnterprise 114• Machine type: 2818• Two models:

– M05 and M10– Single frame, air cooled– Non-raised floor option available– Overhead cabling and DC power options

• Processor units (PUs):– Seven PU cores per processor drawer (one for M05 and two for M10)– Up to two SAPs per system, standard– Two spares designated for Model M10– Dependant on the H/W model, up to 5 or 10 PU cores available for

characterization:• Central processors (CPs), Integrated Facility for Linux (IFLs), Internal

Coupling Facility (ICFs), System z Application Assist Processors (zAAPs), System z Integrated Information Processor (zIIP), optional - additional SAPs

– 130 capacity settings• Memory:

– Up to 256 GB for system including HSA• System minimum = 8 GB (Model M05), 16 GB (Model M10)• 8 GB HSA separately managed• RAIM standard• Maximum for customer use 248 GB (Model M10)• Increments of 8 or 32 GB

• I/O:– Support for non-PCIe channel cards– Introduction of PCIe channel subsystem

• Up to 64 PCIe Channel Cards – Up to two logical channel subsystems (LCSSs)

• STP: Optional (no ETR)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Scalability and flexibility for growth: The z114 will be available in two models: a single central processing drawer model, the M05, and a two drawer model, the M10, which offers the additional flexibility for I/O and coupling expansion and/or increased specialty engine capability. With up to 10 configurable cores, the model naming is indicative of how many total processor units are available for user characterization. The cores can be configured as general purpose processors (CPs), Integrated Facilities for Linux (IFLs), System z Application Assist Processors (zAAPs), System z Integrated Information Processors (zIIPs), Internal Coupling Facilities (ICFs), additional System Assist Processors (SAPs), or can be used as additional spares (M10 only).

With 130 available capacity settings and a granular cost structure offered across either model, you have the freedom to choose the right capacity setting for your needs with the flexibility to scale on demand as workload demands increase.

To help secure sensitive data and business transactions, the z114 is designed for Common Criteria Evaluation Assurance Level 5 (EAL5) certification for security of logical partitions. Support for the next generation of public key technologies is available with Elliptic Curve Cryptography (ECC), which is ideal for constrained environments such as mobile devices. The z114 also offers support for key ANSI and ISO standards for the banking and finance industry.

256 GB memory for application growth: The z114 will support up to 248 GB of real (usable) RAIM-protected memory, an industry exclusive currently available only on System z. Beyond the purchased memory, there is an additional 8 GB of memory for the hardware system area (HSA), which holds the I/O configuration data for the server.

High-speed access to your resources: High-speed connectivity is critical in achieving sufficient levels of transaction throughput and enabling resources inside and outside the server to maximize application performance. The host bus interface of the z114 is designed to help satisfy clustering, security, SAN, and LAN requirements. Security for Secure Sockets Layer (SSL) transactions and secure coprocessing is delivered with Crypto Express3. IBM now also offers a PCIe I/O drawer for FICON and OSA-Express multimode and single mode fiber optic environments designed to deliver increased capacity, infrastructure bandwidth, and reliability.

Packaging: For ease of installation, the z114 is a single-frame, air-cooled system that now supports either top- or bottom-exit I/O and power, raised-floor and non-raised-floor options, and high-voltage DC power, providing increased flexibility to accommodate small data center installations and support for future data center design and efficiencies. Exc

lusivo

form

ación

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-11. IBM System z10 ES1011.0

Notes:

The IBM System z10 Enterprise Class (z10 EC) represents the latest state of the art scalable server designed and optimized for growth and large scale consolidation as well as the premier platform to host traditional mission critical workloads alongside new application workloads. The z10 EC provides an advanced combination of scalability, availability, reliability, security, and virtualization.

Built with modular book design, the z10 EC delivers higher total system capacity, memory, and I/O bandwidth. The z10 EC is focused on providing a strong combination of mainframe characteristics plus new functions designed around scalability, availability and security. The intent of the z10 EC is to help increase the flexibility to configure a server to meet current needs, provide a powerful and advanced data serving environment, and help reduce risks and business costs without sacrificing features or functions.


IBM System z10 • The System z10 family of

servers offers:– Five models, from one-way to

64-way– A maximum 1.5 TB of real

storage– zAAP and zIPP specialty engines– New levels of energy efficiency– Just-In-Time deployment of

resources– Unprecedented capacity and

virtualization to meet consolidation needs

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

The z10 EC is designed and optimized for growth and large scale consolidation. The z10 EC provides:

• Up to 64 customer processor units (PUs)

• Up to 384 GB of memory per book

• Up to 1.5 TB of total available server memory

• Up to 12 PUs available for subcapacity use

• Reduction in the preplanning requirements by:

- Providing a fixed hardware system area (HSA)

- Reducing the number of power-on resets (PORs)

- Allowing dynamic add/remove of a new logical partition (LPAR) to a new or existing logical channel subsystem (LCSS)

• Coupling using InfiniBand

- A z10 EC to z10 EC connection is provided by an InfiniBand Double Data Rate.

- A System z10 EC to System z9 dedicated coupling facility connection is provided by an InfiniBand Single Data Rate.

• IBM System z10 Integrated Information Processor (zIIP)

zIIP is a specialty engine designed to help improve resource optimization and lower the cost of eligible workloads, enhancing the role of the mainframe as the data hub of the enterprise.

• IBM System z10 Application Assist Processor (zAAP)

zAAP is a specialty engine that provides an attractively priced Java execution environment if you desire the traditional qualities of service and the integration advantages of the System z10 EC platform.

• Integrated Facility for Linux (IFL)

An IFL is a specialty engine that provides additional processing capacity exclusively for Linux workloads.

• Internal Coupling Facility (ICF)

An ICF is a specialty engine that provides additional processing capability exclusively for the execution of the coupling facility control code (CFCC) in a coupling facility partition. Exc

lusivo

form

ación

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-12. IBM System z10 BC ES1011.0

Notes:

The IBM System z10 BC updates the processor packaging using “drawers” instead of the traditional “book” technology to provide additional cost savings and availability. The CPC drawer package contains single chip modules (SCMs), storage controllers, memory and interfaces to I/O. This new packaging also leverages the new Enterprise Quad-core z10 processor chips introduced with z10 EC. The z10 BC processors operates at 3.5 GHz, which deliver up to 1.9x performance improvements for CPU intensive jobs over the z9 BC.

There are 12 processor unit cores on the z10 BC, of which up to 10 can be configured as various processor types. Up to five general purpose cores and up to five additional specialty engines or up to 10 IFLs or coupling facility cores may be configured. Two system assist processors (SAPs) used with I/O processing are standard on z10 BC, while z9 BC had one. Two additional optional SAPs may be added.

The z10 BC is designed to provide spares for a failing engine only when the full ten engines are not configured.

The big news in memory on the z10 BC is the size and a lower entry point of 4 GB and up to 248 GB of memory in a fully configured server — almost four times that offered in z9 BC.


IBM System z10 BC• Single model: E10

– Single-frame, air-cooled and non-raised option available– Up to 30 logical partitions

• Processor units (PUs):– 12 PUs– Two SAPs, standard– Zero spares when all PUs characterized– Up to 10 PUs available for characterization

• Central processors (CPs), optional specialty processors, and optional additional system assist processors (SAPs)

• Memory:– System minimum of 4 GB– Up to 128 GB, included HSA.

• 8 GB fixed HSA, standard • Up to 120 GB for Customer use • Four and eight GB increments

• I/O:– Up to 12 I/O interconnects per system @ 6 GBps each– Two logical channel subsystems (LCSSs)– Up to 480 ESCON channels– Up to 128 FICON Express4 channels

CMOS 11S 12 PU cores per z10 BCCore cycle time is 0.286 ns, frequency 3.5 GHz4 GB – 128 GB memory

M/T 2097

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

The other significant change is that the standard 8GB hardware system area (HSA) is separately managed, whereas in the past a customer had to use some of their purchased memory to house the HSA.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-13. IBM System z9 BC and EC ES1011.0

Notes:

The IBM System z9, while having classic strengths on which its reputation was formed, continues to be a leader in areas such as data management, availability, security and resiliency, virtualization, and integration. Its ability to support many open and industry standards, with comprehensive support for service-oriented architecture (SOA), makes it an ideal platform for deploying new workloads or for interoperating with new workloads on alternative technologies. The System z9 Business Class (z9 BC) provides tight collaboration with IBM storage and software to help achieve advanced I/O function and performance. The z9 BC represents the continuation of the new generation of System z9 servers introduced with the IBM System z9 Enterprise Class (z9 EC), formerly the IBM System z9 109 (z9-109) that is designed and optimized for On Demand Business.

This new generation of IBM mainframes provides an advanced combination of reliability, availability, security, scalability, and virtualization, together with the ability to reallocate processing power, and is designed to match changing business priorities on demand.

PUs defined as Internal Coupling Facilities (ICFs), Integrated Facility for Linux (IFLs), System z Application Assist Processors (zAAPs) and System z9 Integrated Information


IBM System z9 BC and EC • The System z9 BC family of

servers offers:– Two air-cooled models, from

one-way to seven-way– A maximum 512 GB of real

storage– zAAP and zIPP specialty

engines• The System z9 EC processor

has:– Four models, from one-way to

54-way– Up to 60 LPARS– Tri-modal addressability– A maximum of 512 GB of real

storage

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Processor (zIIPs) are no longer grouped together in one pool as on the z890, but are grouped together in their own pool, from which they can be managed separately. This simplifies LPAR capacity planning and management significantly. The separation also has an effect on weight management since CP weights and zAAP and zIIP weights can now be managed separately. Capacity BackUp (CBU) features are available for IFLs, ICFs, zAAPs and zIIPs.

The System z Application Assist Processor (zAAP), available also on the z9 EC, z990 and z890 servers, is a specialized processor that provides a strategic z/OS (z/OS.e) application execution environment for those who desire the powerful integration advantages and traditional qualities of service of the platform. Java is the first application exploiter of the zAAP.

The System z9 Integrated Information Processor (zIIP) is the latest customer inspired specialty engine designed to help improve resource optimization and lower the cost of portions of eligible workloads. The zIIP can help to strengthen the System z9 mainframe as the data serving hub, helping customers to more fully leverage their valuable assets.

DB2 for z/OS V8 (and DB2 9 for z/OS) exploits the zIIP capability for portions of eligible workload. Eligible work that access DB2 (such as Customer Relationship Management (CRM), Enterprise Resource Planning (ERP), Business Intelligence (BI), and data warehousing applications) can have portions of their work directed to the zIIP.z9 EC, building upon the structure introduced on the IBM eServer zSeries 990 (z990) – scalability and z/Architecture.

z/Architecture is implemented on the System z9 platform to allow 64-bit real and virtual storage support. A maximum 512 GB of real storage is available on z9 EC. z9 EC can define any logical partition as having 31-bit or 64-bit addressability.

With a modular book design, the z9 EC is designed to provide up to 95% more total system capacity than the z990 Model D32, and has up to double the available memory. The maximum number of processor units (PUs) has grown from 32 to 54, and memory capacity has doubled, up to 128 GB per book and up to 512 GB per system.

The z9 EC has five models offering between 1 to 54 PUs, which can be configured to provide a highly scalable solution designed to meet the needs of both high transaction processing applications and On Demand Business. Four models (S08, S18, S28 and S38) have 12 PUs per book, and the high capacity model, S54, offers 16 PUs in each of its four books. The PUs can be characterized as either CPs, IFLs, ICFs, zAAPs or zIIPs. An easy-to-enable ability to turn off CPs or IFLs is available on z9 EC, allowing you to purchase capacity for future use with minimal or no impact on software billing. An miscellaneous equipment specification (MES) feature will enable the “turned off” CPs or IFLs for use where you require the increased capacity. Exc

lusivo

form

ación

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-14. IBM System z: System design comparison ES1011.0

Notes:

IBM designs and delivers a balanced system design for mainframes.

When a mainframe system is designed many items and how they interact must be considered.

The four identified items in the chart: processors, memory, IO bandwidth, and internal throughput rate (ITR) shown for the zEC12 server is also contrasted with previous IBM mainframe servers.


z10 EC

z9 EC

zSeries 990

zSeries 900

z196

* Servers exploit a subset of its designed I/O capability

** Up to 1 TB per LPARPCI – Processor Capacity Index

Balanced systemCPU, nWay, memory,

I/O bandwidth*

101-wayprocessors

PCI for1-way

1514

Memory3 TB**

System I/O Bandwidth 384 GBps*

zEC12

80-way

64-way

54-way

32-way

16-way

1.5 TB** 512 GB 256 GB

64 GB

1202920600450300

288 GB/sec*

96 GB/sec

24 GB/sec

172.8 GB/sec*

IBM System z: System design comparison

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-15. z/OS highlights ES1011.0

Notes:

As implemented on the IBM System z, z/Architecture is a 64-bit architecture mode that is a superset of ESA/390. The 64-bit architecture eliminates the need to move data into expanded storage by implementing a larger amount of central storage, up to 64 GB.The zSeries Architecture (z/Architecture) is a trimodal architecture capable of executing in 24-bit, 31-bit, or 64-bit addressing modes. Initial implementation of the z/Architecture is limited to exploitation by the operating systems and middleware products which have been modified to exploit the new capabilities of z/Architecture.Middleware products such as DB2, IMS and others has been modified to exploit z/Architecture. Middleware is used to describe the software layer that lies between the operating system and the application. Middleware software provide services that are typically not part of the operating system or the application. It can be used to describe a wide range of software services and products including software that enables communication and management of data in distributed applications.Intelligent Resource Director (IRD) extends the function of the z/OS Workload Manager (WLM) to operate with System z servers to dynamically manage resources across an LPAR cluster.


z/OS highlights• The z/Architecture is a trimodal architecture capable of

executing in 24-bit, 31-bit, or 64-bit addressing modes.• z/OS and middleware products have been modified to exploit

the new capabilities of the z/Architecture. Among exploiters areDB2 UDB, IMS, VSAM, HFS, and XRC.

• z/OS and z/Architecture introduce the Intelligent Resource Director (IRD) to enable resources to be dynamically managed across LPARs, based on workload priorities.

• 24-bit and 31-bit application programs run unmodified on the System z and zEnterprise servers.

• New 64-bit applications can be written in Assembler, Java, C and C++ to run on z/OS.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-16. Processor types ES1011.0

Notes:

An IBM z/Architecture system consists of hardware and software products. The hardware consists of the central processor, the storage, channels, and so forth. The software running on the System z hardware comprises system application programs, end-user applications, tools, utilities, and so on. The primary program executing on the system is an operating system such as z/OS or zLinux. Together, the hardware and software make up a central processor complex (CPC).

The z/Architecture requires that each central processor processes one and only one program instruction at a time. The operating system manages the instructions to be processed and the resources required to process them. A single processor system is called a uniprocessor.

By adding more processors to a CPC (referred to as an n-way processor), you provide a processor backup and enable a system to process multiple program instructions simultaneously.

N-way refers to the number (n) of CPs in a CPC. For example, a 6-way CPC contains six CPs.


Processor typesUniprocessor n-way processor

Storage

Channel SubsystemChannel subsystem

CP

Storage

Channel subsystem

CP CP CP CP

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Some of these n-way processors provide the physical capability to be divided into two separate systems, running two separate operating systems. An n-way processor system that possesses this feature is a multiprocessor.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-17. Logical partitioning and partitioning with zVM ES1011.0

Notes:

A single z/Architecture system can be partitioned to run multiple operating system images. Logical partitioning and partitioning through the use of zVM are both supported.

• Logical partitioning

Logical partitioning describes the logical subdivision of an z/Architecture's resources into two or more parts, called logical partitions. These logical partitions run different operating system images.

To logically partition an z/Architecture it has to be equipped with the Processor Resources/Systems Management (PR/SM) feature. PR/SM allows multiple logical partitions (LPARs) of:

- Processors

- Storage (central/expanded)

- Channel Paths

Processors can be shared among logical partitions or dedicated to a specific LPAR.


Logical partitioning and partitioning with zVM

Logical partitioning Partitioning using zVM

CPC

LPA

R

PR/SM

LPA

R

LPA

R

LPA

R.....

CPC

Imag

e 1

zVM

Imag

e 2

Imag

e 3

Imag

e n.....

zEnterprise servers implement zVM operating in a logical partition.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

You can share channels among logical partitions via PR/SM and the multiple image facility (MIF) that is on every current IBM mainframe server.

• Partitioning with zVM

Using Virtual Machine (zVM) to partition a system is the most flexible way of running multiple images on the same physical machine. zVM acts as a resource manager to build multiple virtual machines which each run their own operating system image.

Note

Logical partitioning, and partitioning through zVM, can be combined for flexibility.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-18. Topic summary ES1011.0

Notes:


Topic summaryHaving completed this topic, you should be able to:• Identify the operating systems and IBM mainframes supporting

the z/Architecture• Describe the partitioning capabilities used with z/Architecture

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

1.2. z/OS system overview

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-19. z/OS system overview ES1011.0

Notes:



System z server hardware overview


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Name the functional groups that comprise z/OS• Explain the concept of virtual storage and how it is used in


DASD management in z/OS• Describe the main end user interfaces of z/OS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-21. z/OS system overview ES1011.0

Notes:

z/OS provides basic system services for the traditional workloads as well as the UNIX or Java workloads.



Communications Services

Security Services

CICS IMS/TM

System Services• TSO • Batch• UNIX• APPC• STC

Application Enablement

UNIX System Services

Applications

Non-VSAM VSAM HFS

zFS

DB2 IMS/DB

Sof

tcop

y pu

blic

atio

n su

ppor

t

Sys

tem

s m

anag

emen

t

LAN Services

DistributedComputing

Cryptographic Services

e-Business Services

z/OS servers

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-22. z/OS functional groups ES1011.0

Notes:

Prior to OS/390 and the later z/OS, large software system consisted of many different products that had to be ordered, installed, and maintained separately. Now, with z/OS, customers order products en bloc and receive a tailored package of all the base and optional products they need for their IS installation. IBM ensures that all products shipped with the order are at the proper release level and that all prerequisites are met.

z/OS products are organized in functional groups such as:

System Services Basic functions and services that are provided through the Base Control Program (BCP) or MVS, the Job Entry Subsystem (JES), UNIX base services, and other related elements and features. These functions support storage, workload and data management.

Systems Management Services z/OS uses Systems Management Services to deliver products that help you install, configure and maintain software and manage system performance.


z/OS functional groups

Systems Management

Services

ApplicationEnablement

Services

UNIXSystemServices

CommunicationsServer

SoftcopyPublication

Services

e-BusinessServices

SystemServices

Distributed Computing

Services

LANServices

SecurityServices (RACF)

CryptographicServices

IntegratedSecurityServices

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Security Services (RACF) This component provides all the necessary functions to ensure a high degree of security within a local or distributed environment. Other third-party security products can be installed on z/OS as an alternative to this product.

Application Enablement Services z/OS delivers a language-independent service platform for traditional and object-oriented application programs, and enables 3270 terminal applications to exploit workstation graphics and dialogs.

Distributed Computing Services z/OS provides support for distributed applications based on common industry solutions like distributed computing environment (DCE), distributed file system (DFS), and network file system (NFS).

Communications Server z/OS supports common programming interfaces such as Advanced Program to Program Communication (APPC), SOCKETS, Remote Procedure Call (RPC), Systems Network Architecture (SNA or 3270) and Wide Area Network (WAN) protocols including SNA, Transmission Control Protocol/Internet Protocol (TCP/IP), and Asynchronous Transfer Mode (ATM).

e-Business Services This component provides secure Internet access and enables z/OS to act as an Internet server. Allows Internet access to IMS, DB2, and CICS transactions.

LAN Services This component enables z/OS to actively participate in a Local Area Network (LAN) as data or print server, thus making z/OS resources accessible to LAN users and LAN resources to z/OS users.

UNIX System Services z/OS meets open system standards as specified in the X/Open Company's Single UNIX Specification, also known as UNIX 95 or XPG4.2. This feature allows your UNIX programmers and other users to interact with z/OS as a UNIX system without necessarily having to learn the z/OS command language or other interactive interfaces.

Softcopy Publication Services z/OS provides the necessary services which allow you to manage, display, and search books online.

Cryptographic Services This component is used by other components to exploit cryptographic hardware devices installed in the processor. Cryptography is used by z/OS applications to encrypt and decrypt application and network data,

This course covers the highlighted functional groups on the diagram.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-23. The concept of virtual storage ES1011.0

Notes:

z/OS allows users to access a greater range of storage than is physically available in the form of central storage. This storage range is called virtual storage. Before 64-bit virtual storage support, each user has access to a maximum of 2 GB of virtual storage. z/OS Release 2 is the first phase of 64-bit virtual storage support. This support allows each user to have access to a maximum of 16 EB of virtual storage. What makes virtual storage work is that the operating system keeps only active portions of virtual storage in central storage (memory). Inactive portions are moved to expanded storage (memory) or auxiliary storage (DASD).

Note

Expanded storage was supported by previous z/OS releases on older mainframe servers in ESA/390 mode. Current z/OS releases do not support expanded storage with z/Architecture.


The concept of virtual storage

PageA CD E FG H IJ K LVirtual storage

Central storage

Expanded storage

D K

C A L

H

FFrame

Auxiliary storage

E B

J I G

Slot

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Virtual storage consists of 4 KB blocks called pages. A page can be stored in real storage or on auxiliary storage. A 4 KB block in real storage is referred to as a frame, a 4 KB block in on auxiliary storage is called a slot.

A storage location within the virtual storage is identified through a virtual address.

Dynamic address translation (DAT) is the hardware process of translating a virtual storage address, during a storage reference, into the corresponding central storage address (called real address).

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-24. Virtual storage and zArchitecture ES1011.0

Notes:

Virtual storage in this environment includes:

• Address spaces: Addressable in bytes. Address spaces in z/OS are 64-bit addressable

• Data spaces: Addressable in bytes • Hiperspaces: Addressable in 4 K-blocks

In z/OS, address spaces, data spaces, and hiperspaces are backed by central storage and auxiliary storage.

Pages (virtual storage), frames (real storage), and slots (auxiliary storage) are all 4K bytes in size.

Note, however, that with the z10 and zEnterprise, large page support (1 megabyte pages) is supported.


Virtual storage and zArchitecture

Addressspaces

z/Architecture64-bit address

Centralstorage

Auxiliarystorage

Hiperspaces

Dataspaces

Note: Previous to z/Architecture, hiperspaces resided in expanded storage. With z/Architecture Hiperspace use is no longer needed and has been discontinued.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-25. Address space, data space, and hiperspace ES1011.0

Notes:

The sequence of virtual addresses associated with a virtual storage is called an address space. An address space contains 2 GB of virtual storage before z/OS. An address space can contain 16 EB of virtual storage beginning with z/OS Release 2. z/OS offers this virtual addressing capability to every user in the system by assigning each user its own separate address space. Programs in separated address spaces are protected from each other. Isolating data in its own address space also protects the data.

The concept of having multiple virtual storages is the basic concept of the z/OS operating system’s base control programs (BCP). The BCP is often called MVS because it is based on the Multiple Virtual Storage/ESA (MVS/ESA) operating system.

System address spaces are created when the z/OS system is started. Other address spaces are generated when a user logs on to the system, when a task is started from the operating system console, or when JES creates initiators for batch jobs to execute in.

Data spaces and hiperspaces are similar in that both are areas of virtual storage that can be created by the system upon user request. The size of data spaces and hiperspaces can range from 4 KB to 2 GB, depending on the user's request. Unlike an address space, a


Data spaceor

HiperspaceAddress space

User data

User programsand data

User programsand data

2 GB

4 KB

16 MB

2 GB

4 KB

System programsand data

16 EB

User/system data

(for 64-bit programs only)

(the bar)

Address space, data space, and hiperspace

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

data space or hiperspace contains only user data or user programs stored as data. Program code cannot directly be executed in a data space or a hiperspace. A program references data in a data space directly, in much the same way it references data in an address space. The program uses the same instructions that it would use to access data in its own address space.

Data stored in a hiperspace is not directly accessible. It has to be transferred to an address space or data space before it can be accessed. This is done through system services. Hiperspaces have been discontinued and are no longer used in z/OS.

To access the address space storage between 2 GB and 16 EB, a program must be running in 64-bit mode (using 64-bit storage addresses). Programs cannot execute in this storage area, so it is limited to storing user data for programs that are loaded in the address space below 2 GB.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-26. Address space layout ES1011.0

Notes:

Each virtual address space consists of:

• A private area below 16 MB • A common area below 16 MB • An extended common area above 16 MB • An extended private area above 16 MB

Private area and extended private area: This area can contain the user programs, data buffers and control information. Since no other user can address this area, its contents are secure.

Common area and extended common area: The common area contains system control programs and control blocks.

A z/OS virtual address space has also a private area above the bar, that is, above 2 GB.


0

Note: Not to scale. 8+ billion traditional address spaces in one 64-bit address space(billion = million million)

2 GB

16 MB

24-bit

31-bit

64-bit

16 EB

The bar

The line

K - kilo - 210

M - mega -220

G - giga - 230

T - tera - 240

P - peta - 250

E - exa - 260

High storage

Above storage

Private area

Common area

Extendedcommon area

Extendedprivate area

Highprivate area

Address space layout

z/OS64-bittri-modal addressing

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-27. At execution time ES1011.0

Notes:

The data to be processed and the program that processes it must be identified to the operating system. The way we do this is different for each environment, ISPF, TSO/E, batch, and UNIX.

The basics, though, are conceptually the same. We must first allocate the data sets and then call the program to do the processing.

Allocate means to make a logical connection with the data set.

The program is found using a standard method we will discuss later in the course.


Central storagePages

PROGRAM

DATA

Loaded by z/OS Program Manager

Read into a buffer by the program during execution

At execution time

• The program to be executed and the data to be processed reside in a data set (MVS) or file (UNIX).

• Before execution, data sets or files must be allocated.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-28. Job entry subsystem (1 of 2) ES1011.0

Notes:

z/OS use a job entry subsystem (JES) to receive jobs into the operating system, schedule them for processing, and to control their output processing. IBM provides two JESs: JES2 and JES3. The management of jobs and resources in z/OS is handled between JES and the base control program (BCP). In this manner, JES manages jobs before and after execution; the base control program manages them during processing.

JES has data sets that contain input job queues (that is, lists of jobs to be processed by z/OS) and output queues on direct access storage devices (DASD). Future work is added to these queues and JES selects work for processing from them. These data sets are called spool and checkpoint data sets.

• Spool: Simultaneous Peripheral Operation OnLine

In an installation that has only one processor, JES2 and JES3 perform similar functions. That is, they read jobs into the system, convert them to internal machine-readable form, select them for processing, process their output, and purge them from the system.


Processor

SPOOL

JES2devices

JES2:

JES2devices

Processor

Loosely coupled

z/OS + JES2 z/OS + JES2

Job entry subsystem (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

However, for an installation that has more than one processor in a configuration, (a loosely coupled multiprocessor) JES2 and JES3 work differently.

Within JES2, each processor controls its own job input, job scheduling, and job output processing, while sharing the spool and checkpoint data sets.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-29. Job entry subsystem (2 of 2) ES1011.0

Notes:

In contrast, JES3 exercises centralized control over its processing functions through a single global JES3 processor.

This global processor provides all job selection, scheduling, and device allocation functions for all the other JES3 systems. The centralized control that JES3 exercises provides increased job scheduling control, deadline scheduling capabilities, and increased control by providing its own device allocation.


Local processor

Local processor

Globalprocessor SPOOLJES3

devices

JES3: z/OS + JES3

z/OS + JES3

z/OS + JES3

Job entry subsystem (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-30. Catalog management ES1011.0

Notes:

z/OS keeps track of the location of its data sets through the use of catalogs. A catalog is a data set which contains information about other data sets. It provides users with the ability to locate a data set by name, without having to know where the data set resides; data can be moved from one device to another, without, for example, requiring a change in its references.

z/OS uses Integrated Catalog Facility (ICF) catalogs to administer data sets on DASD. All VSAM data sets and all SMS-managed data sets must be cataloged.

In a z/OS system, there is usually one master catalog and one or more user catalogs. The master catalog contains direct pointers to all system data sets, used for system initialization, and indirect pointers, called aliases, to the user data sets.

An alias is a pointer, based on a predefined number of qualifiers (usually the first), that directs catalog management to a user catalog where the related data set is cataloged.


VVDSVTOC

SYSRES

Master catalogAliasSystem DS

USRVOL

Data set

User catalog

User catalog

User catalog

User DS

Catalog management

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-31. System-managed storage ES1011.0

Notes:

The Data Facility Storage Management Subsystem (DFSMS) simplifies the task of managing storage by providing the storage management subsystem (SMS) facility. Under the storage administrator's control, the storage management subsystem of DFSMS works with other components of DFSMS to help automate and optimize storage management.

As a new data set is created, the storage management subsystem automatically assigns services and attributes to the data using values defined by the installation. The storage management subsystem also automatically controls system storage and decreases user concern about the physical characteristics of storage devices (device independence).

With SMS, users can establish policies for the use of hardware resources and effectively control how those resources are used and what service levels are to be provided. Requirements for data availability, performance, space, and security are handled by the Storage Management Subsystem.

The DFSMS allows IS installations to separate the logical view of data from its physical characteristics. A user is no longer responsible for the device allocation; the system takes care of that through a set of Automatic Class Selection (ACS) routines. These ACS


System-managed storage

Data set allocationrequest

Storage management subsystemData class ACS routine

Storage class ACS routine

Management class ACS routine

Storage group ACS routine

Managed?System

resourcesmanager

Managed volumes

NO

YES

Non-managed volumes

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

routines, to be defined for every installation, are run at data set allocation time and assign a new data set a Management class, data class, storage class, and storage group. Together these four describe every aspect of the data set:

Management class Data set management information such as number of backup versions, migration criteria, expiration date, and so on.

Data class A list of physical data set attributes, including data set type, record length, space information, and so forth.

Storage class Performance and availability criteria for the data set allocation, for example, desired response time, special availability precautions, and so forth.

Storage group A group of logically connected volumes that is processed as if it was a single volume.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-32. TSO, ISPF, and ISPF/PDF ES1011.0

Notes:

TSO/E Time sharing option extensions (TSO/E) is an integral component of z/OS and is an exclusive base element. It allows for a direct, interactive communication with the operating system and other software components. TSO/E enables users to interactively share computer time and resources. In general, TSO/E makes it easier for people with all levels of experience to interact with the z/OS system.

ISPF The Interactive System Productivity Facility (ISPF) allows programmers to easily implement new, dialog-oriented applications by providing commonly needed display and dialog services, test facilities, tools, and so forth.


Storage management

Application development Maintenance

Job management Security

Data managementISPF

ISPFISPF ISPF

ISPF

ISPFTSO

TSO, ISPF, and ISPF/PDF

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-33. Establishing a TSO session ES1011.0

Notes:

Performing a logon to a TSO system means starting a TSO/E session and identifying yourself to TSO/E. To do so you have to provide:

• A unique, valid user identification called a user ID • A valid password that is associated with the user ID

(In addition, you might also have to specify an account number, a procedure name, and possibly a RACF GROUP name.)

To actually log on to a TSO system, you have to enter the TSO LOGON command. The logon request is passed on to terminal control access space (TCAS). If TCAS accepts the logon request, it creates the user's address space and initializes its buffers. Once the user address space is set up, TCAS declares the user address space to VTAM, which now handles all further communications.


TSO useraddress space

TSO user ID(logon screen)PasswordREADY or ISPF

Buffer

Establishing a TSO session

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-34. Time sharing option/extensions ES1011.0

Notes:

TSO/E is a base element of the z/OS System Services function.

You can use TSO/E in many environments, such as with the Interactive System Productivity Facility/Program Development Facility (ISPF/PDF), session manager, and line mode TSO/E. How you interact with TSO/E depends upon the environment.

ISPF/PDF Interactive System Productivity Facility (ISPF) and its Program Development Facility (ISPF/PDF) provide panels through which users can interact with the system. PDF provides an environment for the development, testing and execution of programs and applications.

Session manager The TSO/E session manager is an interface to line mode TSO/E. It saves the commands that you enter and the responses that you receive and allows you to redisplay or print them.

Line mode A command-oriented interaction with the z/OS system, one command (-line) at a time. On most display terminals, when you


------------ TSO/E INFORMATION CENTER FACILITY --------------------

OPTION ===>

1 Administrator

2 User Services

To use this panel you must have completed the customization for TSO/E in section Information Center Facility of the MVS CBIPO CUSTOMIZATION AND USE GUIDE.

PRESS END or RETURN key to terminate

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

READY_

----------------------------- TSO/E LOGON-------------------------------

Enter LOGON parameters below: RACF LOGON parameters:

Userid ===> AUES100

Password ===> New Password ===>

Procedure ===> LOGON Group Ident ===>

Acct Nmbr ===> ACCNT#

Size ===> 4096

Perform ===>

Command ===> isppdf

Enter an 'S' before each option desired below: -Nomail -Nonotice -Reconnect -OIDcard

PF1/PF13 ==> Help PF3/PF15 ==> Logoff PA1 ==> Attention PA2 ==> ReshowYou may request specific help information by entering a '?' in any entry

Time sharing option/extensions

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

are in line mode TSO/E, three asterisks (***), on the screen means that when you read the screen and press the Enter key, TSO/E will present you with a new screen and allow you to continue.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-35. Interactive System Productivity Facility ES1011.0

Notes:

This is the ISPF Primary Option Menu.


Menu Utilities Compilers Options Status Help --------------------------------------------------------------------------

ISPF Primary Option Menu

0 Settings Terminal and user parameters User ID . : AUES100 1 View Display source data or listings Time. . . : 14:41 2 Edit Create or change source data Terminal. : 3278 3 Utilities Perform utility functions Screen. . : 1 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : ISR 6 Command Enter TSO or Workstation commands TSO logon : LOGON 7 Dialog Test Perform dialog testing TSO prefix: AUES100 8 LM Facility Library administrator functions System ID : SYS1 9 IBM Products IBM program development products MVS acct. : ACCNT# 10 SCLM SW Configuration Library Manager Release . : ISPF 4.8 11 Workplace ISPF Object/Action Workplace

Enter X to Terminate using log/list defaults

Option ===> F1=Help F3=Exit F10=Actions F12=Cancel

Interactive System Productivity Facility

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Name the functional groups that comprise z/OS• Explain the concept of virtual storage and how it is used in


DASD management in z/OS• Describe the main end user interfaces of z/OS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 1-37. Checkpoint (1 of 3) ES1011.0

Notes:


Checkpoint (1 of 3)1. Which operating systems are supported by the System z hardware?

(Mark all that apply.) a. OS/400 b. UNIX c. Windows NT d. zLinuxe. z/OS

2. Which of the following are valid ways to partition z/Architecture system? (Mark all that apply.) a. Partitioned data sets b. Partitioned data sets extended c. Partitioning through VM d. N-way partitioning e. Virtual partitioning f. Logical partitioning

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (2 of 3)3. Which of the following are functional groups of z/OS?

a. Systems management services b. Application enablement services c. UNIX System Services d. Communications server e. Distributed computing services f. All of the above

4. True or False: Virtual storage consists of 4 KB blocks called pages.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (3 of 3)5. True or False: z/OS must run on z/Architecture in 64 bit

mode.

6. True or False: The z/Architecture is a trimodal architecture capable of executing in 24-bit, 32-bit, or 64-bit addressing modes.

7. True or False: A program cannot execute in the space storage between 2 GB and 16 EB.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 1-40. Unit summary ES1011.0

Notes:


Unit summaryHaving completed this unit, you should be able to:• Identify the operating systems and IBM mainframes supporting

the z/Architecture• Describe the partitioning capabilities used with z/Architecture• Name the functional groups that comprise z/OS• Explain the concept of virtual storage and how it is used in


DASD management in z/OS• Describe the main end-user interfaces of z/OS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Unit 2. An introduction to ISPF, ISPF/PDF, and RACF


The first part of this unit should give you a brief overview of the components of Interactive System Productivity Facility (ISPF) in general and of Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) in particular. You will learn how to perform a logon to the lab system and how to activate and use the Program Development Facility.

In the second part of the unit, you will discover how the z/OS system security product Security Server (RACF) authenticates a user logon to the z/OS system and how it authorizes users to access resources such as system data sets.



• Name the components of ISPF

• Describe the general layout of ISPF/PDF panels

• Identify the main ISPF/PDF options

• Be able to run a simple TSO session:

1. Log on to the lab system

2. Start the Program Development Facility

3. Customize ISPF settings

4. View a data set

5. Log off

• Identify the main functions of Security Server (RACF) and the role it plays in controlling user access to the system

• Describe the contents of RACF user, group, and resource profiles

• Describe how RACF profiles are used to authorize user access to a data set resource

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 2. An introduction to ISPF, ISPF/PDF, and RACF 2-1

Student Notebook

.


• Checkpoint questions • Machine exercises

References

SC34-4822 ISPF User’s Guide Vol I

SC34-4823 ISPF User’s Guide Vol II

SA22-7784 TSO/E General Information (GIM)

SA22-7787 TSO/E Primer

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Unit objectivesAfter completing this unit, you should be able to:• Name the components of ISPF• Describe the general layout of ISPF/PDF panels• Identify the main ISPF/PDF options• Be able to run a simple TSO session:

1. Log on to the lab system2. Start the Program Development Facility3. Customize ISPF settings4. View a data set5. Log off


• Describe the contents of RACF user, group, and resource profiles• Describe how RACF profiles are used to authorize user access to a

data set resource

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

2.1. ISPF and ISPF/PDF overview

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-2. ISPF and ISPF/PDF overview ES1011.0

Notes:


ISPF and ISPF/PDF overview


Security in a z/OS environment

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Name the components of ISPF• Describe the general layout of ISPF/PDF panels• Identify the main ISPF/PDF options• Be able to run a simple TSO session:


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-4. ISPF and ISPF/PDF overview ES1011.0

Notes:

Interactive System Productivity Facility or simply ISPF provides a panel-driven interface and can be seen as an extension of the z/OS Time Sharing Option (TSO) host system on which it runs. The services provided through ISPF complement those of the host system. ISPF is similar to a control program or access method in that it provides services to dialogs (applications) during their execution. The types of services provided by ISPF are:

• Display services • Variable services • Table services • Dialog test facilities • And so on

A dialog receives requests and data from a user at a terminal. The dialog responds by using ISPF services to obtain information from, or enter information into, the z/OS system.



ISPF

Dialog Manager

Program Development Facility

Software Configuration and Library Manager

Client/Server

What is ISPF?

Interactive System Productivity Facility

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

ISPF consists of four major components:

The Dialog Manager (DM)

Provides services to dialogs and end users. PDF assists dialog or application developers by providing development services.

The Software Configuration Library Manager (SCLM)

Offers services to application developers to manage their application development libraries. SCLM is a library facility that supports projects in developing complex software applications. SCLM supports the software development cycle of an application from the program design phase to release of the final product.

The client/server component (C/S)

Enables you to run ISPF on a programmable workstation, to display the panels using the display function of your workstation operating system, and to integrate workstation tools and data with host tools and data.

The Program Development Facility (PDF)

Uses integrated work environment to develop programs, dialogs, and documents. It provides numerous productivity-improving functions. Some examples are:

• ISPF dialog test tools • Full-screen editor, with a dialog interface called edit macros • Update access to multiple data sets • Online tutorials • Data set management • Customized library controls

We do not deal with the software configuration and library manager or the ISPF client/server component in the rest of this course.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-5. Dialog Manager ES1011.0

Notes:

The Dialog Manager provides various kinds of services to dialogs during their execution and controls the interaction of the dialog's elements. For example, ISPF can issue requests for panels to be displayed and screens to be formatted. It can verify, process, store input, create output, and so forth. ISPF can also function as a simplified data management system for small amounts of data stored in tables.

The dialog management services of ISPF include:

• Display services for panels, pop-up windows, pull-down menus, messages, tables, and so forth

• Select services for panels and functions • Table manipulation services • File tailoring services • Services to handle and display dialog variables


Dialog Manager

Display services

Select services

Table manipulation services

File tailoring services

Dialog variable services

Dialog

Display panel xxx

Verify selection

Display message

...

Dialog Manager

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-6. Panel hierarchy ES1011.0

Notes:

This visual shows three common panel types, arranged in a hierarchy. The starting panel at the top is a selection panel known as the ISPF Primary Option Menu.

From the ISPF Primary Option Menu (POM), other selection panels can be selected.

Panels used for features like View and Edit use scrollable panels.


Copy/MoveC Copy M Mo CP Cop MP Proj ____Group ____Type ____

Libraryb Blank D DeleteProj ____Group ____Type ____

POM0 Settings1 Browse2 Edit3 Utilities4 DS List5 ...

Settings

/ Cursor at .._ ..._ ..._ ...

ViewProj ____Group ____ Type ____

Other Dsn __

Utilities1 Dataset2 Library3 Copy/Move4 DS List

Dialog Test1 ......2 .....3 ......4 ......

EditProj ____Group ____ Type ____

Other Dsn __

Edit****************0 //JOB1 JOB 0 //S1 EXEC0 //DD1 DD0 ..***************

Datasetb Display D DeleteProj ____Group ____Type ____

Panel hierarchy

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-7. Program Development Facility ES1011.0

Notes:

The Program Development Facility component of ISPF provides the dialog or application developer with a variety of services to create and test applications. PDF lets you manage data sets, create and test panels and messages, generate tables, keep track of variable values, set checkpoints, trace applications, and so forth.

This visual shows the ISPF Primary Option Menu (the main menu of the PDF). It contains the options that you can use to create your own applications online. It is possible to customize the ISPF Primary Option Menu, therefore the PDF main menu at your home system might offer additional or alternative choices to the following options:

0 - Settings Lets you display and change ISPF parameters such as function key definitions, panel display, display colors, and so forth.

1 - View Allows you to view or browse data sets.

2 - Edit Lets you create or update data sets and members. The ISPF/PDF Editor provides macros and models which help you change or create data sets.


Menu Utilities Compilers Options Status Help ------------------------------------------------------------------------------

ISPF Primary Option Menu Location : Option ===>

0 Settings Terminal and user parameters User ID . : TSOFT98 1 View Display source data or listings Time. . . : 09:22 2 Edit Create or change source data Terminal. : 3278 3 Utilities Perform utility functions Screen. . : 1 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : ISR 6 Command Enter TSO or Workstation commands TSO logon : STUDENT 7 Dialog Test Perform dialog testing TSO prefix: TSOFT98 8 LM Facility Library administrator functions System ID : MVS1 C Classes Menus for specific Classes MVS acct. : 1ES10G12 E ITS Menu ITS extended menu Release . : ISPF 5.9 S ITS Schedule ITS schedules SD SDSF Syslog Display and Search Facility 10 SCLM SW Configuration Library Manager 11 Workplace ISPF Object/Action Workplace


Licensed Materials - Property of IBM 5694-A01 (C) Copyright IBM Corp. 1980, 2006.All rights reserved. US Government Users Restricted Rights -Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Option ===> F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap

F10=Actions F12=Cancel

Program Development Facility

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3 - Utilities Offers you a collection of system utility and data set management functions, including printing, renaming, deleting, and so forth, a member or data set.

4 - Foreground Intended to interactively run language processing programs, including assembler, COBOL, VS/FORTRAN, PL/I, VS Pascal, and SCRIPT/VS.

5 - Batch Generates and submits job control statements and command streams to execute language processing programs in background.

6 - Command Enables you to enter TSO commands or invoke CLISTs or REXX EXECs while ISPF/PDF remains active.

7 - Dialog Test Allows for the testing of dialog elements (panels, messages, and so forth) of an application before assembling them in an application.

8 - LM Utilities Library Management Facility (LMF) ensures you are working with the latest level of your development libraries or controlling who is updating what. LMF has been superseded by SCLM.

9 - IBM Products Provides an interface to other IBM products.

10 - SCLM Allows you to work with the Software Configuration and Library Manager component of ISPF.

11 - Workplace Gives you access to the ISPF Workplace Shell, which combines many of the ISPF functions onto one object-action panel.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-8. General structure of ISPF/PDF panels ES1011.0

Notes:

An ISPF/PDF panel consists of the following sections:

Action bar Most ISPF/PDF panels have an action bar at the top. The action bar offers a set of functions grouped in categories.

Panel options This area contains a list of all options that can be selected from this panel.

Dynamic status area The dynamic status area is ISPF/PDF main menu-specific and displays a set of important ISPF/PDF settings.

Command line The command line enables you to execute TSO commands, invoke CLISTs or REXX EXECs, branch to another panel, or enter your selection.

Function keys This area is used to display the settings of the functions keys valid for this panel.


Action bar

Panel options

Command line

Function keys

Dynamic statusarea

Menu Utilities Compilers Options Status Help ---------------------------------------------------------------------------


0 Settings Terminal and user parameters User ID . : AUES1001 View Display source data or listings Time. . . : 16:142 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processing Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: AUES1008 LM Facility Library administrator functions System ID : SYS19 IBM Products IBM program development products MVS acct. : ACCNT#10 SCLM SW Configuration Library Manager Release . : ISPF 5.811 Workplace ISPF Object/Action Workplace

SD SDSF Syslog Display and Search FacilityEnter X to Terminate using log/list defaults

Option ===>

F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=SwapF10=Actions F12=Cancel

General structure of ISPF/PDF panels

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-9. Navigating in ISPF/PDF ES1011.0

Notes:

ISPF offers a user a number of ways to navigate through its dialogs:

Action bars Action bar choices vary from panel to panel, as do the choices from their pull-downs.

An action bar groups the user options into categories. Only the categories are displayed on a panel. To see the options within a category, place the cursor on an action bar choice and press the Enter key. ISPF/PDF now displays the entire list of options for this one category. To select an option, enter the corresponding selection code or move the cursor to the proper selection and press Enter. Options marked with * are unavailable.

Point-and-shoot Point-and-shoot fields are cursor-sensitive. Moving the cursor on a point-and-shoot field and pressing the Enter key selects this panel option.


Menu Utilities Compilers Options Status Help ---------------------------------------------------------

Action bar

0 Settings Terminal and user parameters 1 View Display source data or listings 2 Edit Create or change source data 3 Utilities Perform utility functions .

Point-and-shoot

Option number0 Settings Terminal and user parameters 1 View Display source data or listings 2 Edit Create or change source data 3 Utilities Perform utility functions .. Options ===> 3

Function keysF1=Help F3=Exit F7=Bkwd F8=Fwd F10=Actions F11=Retrieve F12=Cancel

Navigating in ISPF/PDF

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Note: A command entered on a command line is always processed prior to any point-and-shoot selection.

Selection by option code The traditional way of selecting a panel option is by entering the selection code, that is, the number or characters that corresponds to a panel option. This form of selection is available on most ISPF/PDF panels.

Function keys Function keys allow a user to perform a predefined action by simply pressing a specific key. Function keys and their settings are usually displayed at the bottom of a screen. The function key display can be turned off to give you two extra lines on the screen.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-10. The jump function and command stacking ES1011.0

Notes:

ISPF's jump function allows you to branch from one ISPF/PDF panel directly to another panel. When you do so, the old function is ended, before the new one is displayed. To jump from one panel to another, simply enter its ISPF Primary Option Menu selection code preceded by an equal sign on any command line or on most data entry fields. Here is an example of the jump function:

Command ===> =1 This command line entry causes ISPF to leave the current function and to display the entry panel of the first selection of the ISPF Primary Option Menu. ISPF also allows you to combine multiple subsequent panel selections by entering them on the same line separated by a period (.). If you enter 3.4 on a panel's command line, ISPF selects the panel option 3 of the current panel and then option 4 of the second panel. If you enter =3.4 on a panel's command line, ISPF selects the ISPF Primary Option Menu panel option 3 and then panel option 4 of the ISPF Primary Option Menu selection 3. To enter more than one command on a command line, you can stack them by using a delimiter between the commands. The default delimiter is a semicolon (;). If two or more commands are entered in this manner, they are executed in the order of their entry.


Jump function:

Command stacking:...

Command ===> 1st;2nd

equals

.

.

.Command ===> 1st

.

.

.Command ===> 2nd

+

.

.

.Option ===> =3.4 equals

ISPF Primary Option Menu..

Option ===> 3Next Panel ..

Option ===> 4

+

Note the equal sign (=)

.

.

.Option ===> 3.4 equals

Current Panel..

Option ===> 3Next Panel..

Option ===> 4

+

The jump function and command stacking

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-11. Action bar menus ES1011.0

Notes:

Most of the ISPF/PDF panels have action bars at the top.

To move the cursor from any screen location to the action bar:

1. Use the cursor keys to place it on the action bar choice.

2. Enter ACTIONS on any command line and press the Enter key.

3. Press F10 or the Home key.

Use the Tab key to move the cursor among action bar choices. To display the pull-down menu of one of the action bar choices, place the cursor on a choice and press Enter. To select a choice from the pull-down menu, type its number in the entry field (underlined) or place the cursor on your choice and press Enter. To leave a pull-down menu without further selection, press F12 (Cancel).


Actionbar

Menu Utilities Compilers Options Status Help ----- -----------------------------------------

7 1. Library ary Option Menu2. Data set

0 Se 3. Move/Copy arameters User ID . : AUES1001 Vi 4. Data Set List or listings Time. . . : 16:162 Ed 5. Reset Statistics urce data Terminal. : 32783 Ut 6. Hardcopy ctions Screen. . : 14 Fo 7. ISPF C/S Install... e processing Language. : ENGLISH5 Ba 8. Outlist uage processing Appl ID . : ISR6 Co 9. Commands... ation commands TSO logon : LOGON7 Di *0. Reserved ing TSO prefix: AUES1008 LM 11. Format or functions System ID : SYS19 IB 12. SuperC ment products MVS acct. : ACCNT#10 SC 13. SuperCE brary Manager Release . : ISPF 5.811 Wo 14. Search-For Workplace

15. Search-ForE16. Tables17. Udlist

SD SDSF Syslog Display and Search Facility


Option ===>_____________________________________________________________F1=Help F3=Exit F10=Actions F12=Cancel

Pull-downmenu

Action bar menus

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-12. Pop-up window ES1011.0

Notes:

Pop-up windows are windows appearing on top of other panels. In the example shown in this visual, the long message is displayed in a pop-up window. (The long message is displayed when F1 is pressed after a short message is issued.)

Modal pop-up windows are a special kind of pop-up window. They require the user's interaction, that is, some kind of reply, before the underlying dialog continues.

Modeless pop-up windows, in contrast, allow you to interact with the dialog before you interact with the window.


Menu Utilities Compilers Options Status Help----------------------------------------------------------------------------

ISPF Primary Option Menu Invalid Option

0 Settings Terminal and user parameters User ID . : AUES1001 View Display source data or listings Time. . . : 16:162 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processing Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: AUES1008 LM Facility Library administrator functions System ID : SYS19 IBM Products IBM program development products MVS acct. : 582010 SCLM SW Configuration Library Manager Release . : ISPF 5.811 Workplace ISPF Object/Action Workplace



The option that was entered was not valid.

Option ===> ZF1=Help F3=Exit F10=Actions F12=Cancel

Pop-upwindow

Pop-up window

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-13. Option 0: Settings ES1011.0

Notes:

The ISPF Settings option allows you to display and modify selected ISPF parameters. The Settings panel can be invoked from the Primary Option Menu as option 0 or from any panel by entering the SETTINGS command on a command line. All settings are persistent across ISPF sessions except some of those available from the Identifier action bar.

The main ISPF Settings panel has setting options displayed in four areas on the panel:

• Options

• Terminal characteristics

• Print graphics

• General


Log/List Function keys Colors Environ Workstation Identifier Help--------------------------------------------------------------------------

Options Print GraphicsEnter "/" to select option Family printer type 2/ Command line at bottom Device name . . . . / Panel display CUA mode Aspect ratio . . . 0/ Long message in pop-up / Tab to action bar choices / Tab to point-and-shoot fields General / Restore TEST/TRACE options Input field pad . . N

Session Manager mode Command delimiter . ;/ Jump from leader dots

Edit PRINTDS Command / Always show split line _ Enable EURO sign

Terminal Characteristics Screen format 1 1. Data 2. Std 3. Max 4. Part

Terminal Type 6 1. 3277 4. 3278A 7. 3278CF a. 3278DE 2. 3277A 5. 3290A 8. 3277KN b. 3278FI 3. 3278 6. 3278T 9. 3278KN

Command ===>

F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap F10=Actions F12=Cancel

Option 0: Settings

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Additional settings are available from the action bars. Some individual settings can be set from the command line using the following commands:

FKA Controls the display of the function key area at the bottom of the screen.

KEYLIST Invokes the Keylist Utility when entered without parameters.

KEYS Invokes the appropriate utility to modify function keys for the panel from which the command was invoked.

PFSHOW Almost synonymous with the FKA command, PFSHOW controls the display of the function key area at the bottom of the screen.

ZKEYS Invokes the PF Key Definitions and Labels panel.

COLOR Invokes the Global Color Change Utility to modify the display of all colors.

CUAATTR Invokes the CUA Attribute Change Utility to modify the color, intensity, and highlight of CUA panel elements.

PSCOLOR Invokes the CUA Attribute Change Utility to modify the color, intensity, and highlight of CUA panel elements. This command indexes you directly to the point-and-shoot entry.

ENVIRON Invokes the ISPF ENVIRON Command Settings panel, allowing you to enable traces and dumps and obtain information about your terminal or terminal emulator.

PANELID Turns the display of the panel ID on or off. This setting does not persist across ISPF sessions and only affects the screen from which it was entered.

MSGID Turns the display of the message ID on or off. This setting does not persist across ISPF sessions and only affects the screen from which it was entered.

SCRNAME Turns the display of the screen name on or off and assigns a screen name to a logical screen. This setting does not persist across ISPF sessions and only effects the screen from which it was entered.

ISPFVAR Controls some of the settings on the main ISPF Settings panel. xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-14. Option 1: View a data set ES1011.0

Notes:

The View Entry Panel, which is selected from the ISPF Primary Options Menu by option 1, allows you to either view or browse a data set.

View allows you to display source data or output listings. With View, members of partitioned data sets or DASD-resident sequential data sets can be displayed and updated using editor commands. These changes cannot be saved to the original data set, but can be saved to another data set using Create or Replace.

Browse also allows you to display data or output listings. With Browse, members of partitioned data sets, or DASD-resident sequential data sets can be displayed, and can be scrolled forward, backward, left, or right. You cannot alter the data sets displayed. The Browse mode is selected from the View Entry Panel.


Menu RefList RefMode Utilities Workstation Help--------------------------------------------------------------------------

View Entry Panel

ISPF Library:Project . . . AUES100Group . . . . TSOE . . . . . . . . .Type . . . . EXECMember . . . (Blank or pattern for member selection list)

Other Partitioned, Sequential or VSAM Data Set:Data Set Name . . . 'AUES100.TEST.EXEC'Volume Serial . . . (If not cataloged)

Workstation File:File Name . . . . .

OptionsInitial Macro . . . . / Confirm Cancel/Move/ReplaceProfile Name . . . . . _ Browse ModeFormat Name . . . . . _ View on WorkstationData Set Password . . / Warn on First Data Change

Mixed Mode

Command ===>F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=SwapF10=Actions F12=Cancel

Option 1: View a data set

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-15. Option 2: Edit data set ES1011.0

Notes:

When you select option 2 from the ISPF Primary Options Menu, the Edit Entry Panel is displayed. Edit is very similar to View, except in this case the Save function is enabled. Changes to the edited data set or member can therefore be saved.


Menu RefList RefMode Utilities LMF Workstation Help-------------------------------------------------------------------------

Edit Entry Panel

ISPF Library:Project . . . AUES100Group . . . . TSOE . . . . . . . . .Type . . . . EXECMember . . . (Blank or pattern for member selection list)

Other Partitioned, Sequential or VSAM Data Set:Data Set Name . . . 'AUES100.TEST.EXEC'Volume Serial . . . (If not cataloged)


OptionsInitial Macro . . . . / Confirm Cancel/Move/ReplaceProfile Name . . . . . Mixed ModeFormat Name . . . . . Edit on WorkstationData Set Password . . / Preserve VB record length

Command ===>F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=SwapF10=Actions F12=Cancel

Option 2: Edit data set

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-16. Option 3: Utilities ES1011.0

Notes:

The Utilities Selection Panel, option 3 of the ISPF Primary Option Menu, offers a collection of tools and utilities to work with data sets and ISPF.

Here is a brief overview of the choices of the Utilities Selection Panel:

Library Print an index or data set, work with data set members, compress a data set, or display data set information.

Data Set Allocate, rename, delete, catalog, or uncatalog a data set and display data set information. It also offers some VSAM functions.

Move/Copy Move or copy data sets.

Dslist Display and/or print a list of data set names according to their catalog or VTOC entry.

Reset Delete or reset ISPF library statistics.

Hardcopy Print a data set.


Menu Help ------------------------------------------------------------------------------

Utility Selection Panel

1 Library Compress or print data set. Print index listing. Print rename, delete, browse, edit or view members

2 Data Set Allocate, rename, delete, catalog, uncatalog, or display information of an entire data set

3 Move/Copy Move, copy, or promote members or data sets 4 Dslist Print or display (to process) list of data set names.

Print or display VTOC information 5 Reset Reset statistics for members of ISPF library 6 Hardcopy Initiate hardcopy output 7 ISPF C/S Install ISPF C/S workstation code from MVS to your workstation. 8 Outlist Display, delete, or print held job output 9 Commands Create/change an application command table * Reserved This option reserved for future expansion. 11 Format Format definition for formatted data Edit/Browse 12 SuperC Compare data sets (Standard Dialog) 13 SuperCE Compare data sets Extended (Extended Dialog) 14 Search-For Search data sets for strings of data (Standard Dialog) 15 Search-ForE Search data sets for strings of data Extended (Extended Dialog)16 Tables ISPF Table Utility17 Udlist Print or Display (to process)z/OS UNIX Directory list

Option ===> F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap F10=Actions F12=Cancel

Option 3: Utilities

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

ISPF C/S Install the ISPF C/S workstation code from z/OS or OS/390 on your workstation.

Outlist Handling of held jobs, that is, functions to list, delete, print, or requeue held job output.

Commands Create/change application command table.

Reserved Reserved for future releases.

Format Provided for support of the IBM 5550 terminal using the Double-byte Character Set (DBCS).

SuperC Tool to quickly compare the contents of two data sets.

SuperCE An extended version of the SuperC dialog.

Search-For Lets you search data sets for strings of data.

Search-ForE An extended version of the Search-For dialog.

Tables Functions for processing ISPF tables.

Udlist Displays a list of files and directories in a scrollable format.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-17. Option 6: ISPF Command Shell ES1011.0

Notes:

The ISPF Command Shell, ISPF/PDF option 6, allows TSO commands, CLISTs, and REXX execs to be executed under ISPF. Commands entered on the ISPF command shell are appended to a list of most recent issued commands from where they can be retrieved.

Note

ISPF allows TSO commands to be entered in the command input field of any panel. The commands have to be prefixed with TSO.

Example:

Command ===> TSO LISTC

When issuing a command from a panel's command line, you are limited to the length of the command line. The ISPF command shell allows you to enter commands wrapping to the next lines.


Menu List Mode Functions Utilities Help--------------------------------------------------------------------------

ISPF Command Shell

Enter TSO or Workstation commands below:

===> listds es10.cntl

Place cursor on choice and press enter to Retrieve command

=> lista st h=> printds dataset(jcl.cntl) members=> profile=> submit jcl(test)=>=>=>=>=>=>

ISPF Command ===>F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=SwapF10=Actions F12=Cancel

Option 6: ISPF Command Shell

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-18. Option S: System Display and Search Facility ES1011.0

Notes:

The ISPF Primary Option Menu selection SD displays the System Display and Search Facility (SDSF), an optional product that lets you display active users and job input queues, browse job output, show logs, check printers, and so forth.


Display Filter View Print Options Help ------------------------------------------------------------------------------------------------------- SDSF PRIMARY OPTION MENU -------------------------

Type an option or command and press Enter.

DA Active users INIT InitiatorsI Input queue PR PrintersO Output queue PUN PunchesH Held output queue RDR ReadersST Status of jobs LINE Lines

NODE NodesLOG System log SO Spool offloadSR System requests SP Spool volumesJC Job classesSE Scheduling environments ULOG User session logRES WLM resourcesENC EnclavesPS Processes

END Exit SDSF

Licensed Materials - Property of IBM

5694-A01 (C) Copyright IBM Corp. 1981, 2006. All rights reserved.US Government Users Restricted Rights - Use, duplication ordisclosure restricted by GSA ADP Schedule Contract with IBM Corp.

COMMAND INPUT ===> SCROLL ===> PAGEF1=HELP F2=SPLIT F3=END F4=RETURN F5=IFIND F6=BOOK

Option S: System Display and Search Facility

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Name the components of ISPF• Describe the general layout of ISPF/PDF panels• Identify the main ISPF/PDF options• Be able to run a simple TSO session:


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-20. Exercise ES1011.0

Notes:


Tasks:1. Log on to TSO2. Try some options3. View a data set4. Log off

Exercise

System familiarization

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

2.2. Security in a z/OS environment

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-21. Security in a z/OS environment ES1011.0

Notes:





Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Identify the main functions of Security Server (RACF) and the

role it plays in controlling user access to the system• Describe the contents of RACF user, group, and resource

profiles• Describe how RACF profiles are used to authorize user access

to a data set resource

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-23. Security in a z/OS environment ES1011.0

Note

The z/OS Security Services tower includes all the security product software that is shipped with the z/OS system. Some products in this tower are optional, others are standard. Security services software is categorized into three component groups.

The z/OS Security Server component group is an z/OS optional feature. It contains only one software component – Resource Access Control Facility (RACF). RACF provides a high degree of data security for both local users in a single z/OS installation as well as remote networked users using z/OS applications.

The second component group in security services, Cryptographic Services, is a standard part of z/OS. It groups together a number of software products that perform encryption and decryption services on application data and system authentication data on behalf of other z/OS applications and security products.

The third component group is Integrated Security Services (also standard). These products are used to interface z/OS with other security environments that might be used by clients or applications on other networked hosts (typically non-z/OS systems). When you activate these products on z/OS, they talk to the remote host or application using the appropriate



Resource Access Control Facility (RACF)

Cryptographic Services:ICSFOpen Cryptographic Services FacilitySystem SSLPKI Services

Integrated Security Services:

DCE Security ServerEnterprise Identity MappingFirewall TechnologiesLDAP serverNetwork Authentication ServiceOpen cryptographic enhanced plug-ins (OCEPs)

Security Server

Standard Standard

Optional z/OS Security Services

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

security protocol on the one hand, while on the other hand, they interface with the local RACF security environment in order to control the remote user’s access to z/OS resources in the same way as local users might access them.

The scope of the whole z/OS security is an immense area, and this topic only deals with selected parts of the security environment. Note that the prefix Secureway was associated with the z/OS security products in the past, so you might still see references to Secureway Security Server RACF or Secureway Security Server DCE Security Server, which refer to the same products.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-24. Data security is ES1011.0

Notes:

• Note that data security is concerned with unauthorized access to information resources, whether intentional or accidental.

• Note also that this definition says nothing about the form in which the information resources exist – printed, hand-written, typed, graphs, magnetic tape or disk, or other electronic media.

• Unauthorized access could be performed by either insiders or outsiders.


The protection of data from unauthorized

• Destruction

• Modification

• Disclosure

• Use

Whether accidental or intentional

Data security is

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-25. Security Server RACF overview ES1011.0

Notes:

The Security Server Resource Access Control Facility (RACF) controls access to information stored within a z/OS installation.

It provides this security through:

• User Authentication: Identifies and verifies users

• User Authorization: Controls a user's access to resources

• Records and Reports: Keeps track of access attempts

• Administration: Implements and maintains the security environment

We look at each of these major functions in more detail.


Security Server RACF overview

• IMS/CICS transactions

• Programs• User-defined

resources

Userz/OSRACF RACF

Data sets

DASD volumes

Tapevolumes

Terminals

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-26. Security in a distributed environment ES1011.0

Notes:

In the e-business environment, there are multiple security threats not addressed by central security products like RACF. Some of these are eavesdropping, impersonation, and forgery. The other problem is that a separate logon, often with a different user identity, has to be performed for each system that a user client intends to use. RACF can interact with three other security environments in a multi-host network.

The Kerberos security environment

A client asks the Kerberos security server to dynamically create a security token for a service request containing client user identity. The client then passes the Kerberos token with any network request sent to a remote server application. The remote server extracts the client user identity from the token and uses it to authorize access to local resources.

A Distributed Computing Environment (DCE)

DCE is a middleware program that supports client-server interactions between host systems that run the DCE platform software. The DCE security environment uses a specialized adaptation of the Kerberos environment. A trusted DCE security provides the


Security in a distributed environment

Public key infrastructure

Kerberos infrastructure

DCE infrastructure

RACF

RACF resources

• http/s clients• Use X509

certificates to authenticate

• DCE clients• Use DCE

tokens to authenticate

• Wintel and UNIX clients

• Use Kerberos tokens to authenticate

DCE securityserver Kerberos

securityserver

Certificateauthority Certificate

authority

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

security tokens containing the requester’s identity. DCE and Kerberos environments cannot interact successfully.

A Public Key Infrastructure

This type of infrastructure applies to web clients using browsers interacting with Web-based applications. A web client requests a trusted Certificate Authority (CA) to construct a signed client certificate file that contains the client true identity. When the client issues an HTTPS web request, the client certificate is attached to the request. The remote web server extracts the user identity from the certificate, and passes it to the local security package on the server system, which uses the identity to control access to resources.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-27. Distributed signon ES1011.0

Notes:

Distributed users can also be authenticated by a z/OS system.

A local TSO z/OS client supplies a RACF user ID and password to do a LOGON. If RACF validates the user ID/password, the TSO session is authorized by RACF based on this user ID.

When a DCE client uses a Remote Procedure Call (RPC) to call a DCE service application on z/OS, it supplies a DCE security token with the call. The DCE security server extracts the user identity (principal) from the token and authenticates it using the DCE Security Server database. If successful, the DCE principal name is mapped to an existing RACF user ID. The DCE service application then accesses local resources using this RACF user ID, which is used to authorize any access by the application to z/OS resources.

A Kerberos client RPC is processed similarly. The security function that authenticates the Kerberos token passed on the RPC is network authentication service (NAS). NAS uses the Kerberos key database to authenticate the identity of the principal in the Kerberos token and then assigns a mapped RACF user ID to the resulting service request.


z/OS RACF

Key database

NAS *

System SSL

DCE security server

RACFdatabase

RACF user ID

TSO logonUSERID

PASSWORD

User identity

Map

Map

DCE RPC DCE token

http requestcertificate

Kerberos token

RPC

TSO user

DCE client

Web client

Wintel, UNIX client * Network authentication service

PRINCIPAL

PKI key ring

PRINCIPAL

Security database

PRINCIPAL

Map

Distributed signon

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

A web client can send an HTTPS request to the Web server (IBM HTTP server) on z/OS and attach to this request a client certificate. System SSL on z/OS validates the client certificate, and uses a public key infrastructure (PKI) key ring to check that the signing CA is a trusted CA. If this is successful, system SSL extracts the client user name from the certificate and maps it to the name of a RACF user ID. The Web server associates the web request with the mapped-to RACF user ID and uses that to authorize access to resources made by the web request.

The big message: All work arriving in z/OS must be associated with a RACF user ID before it can successfully start execution.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-28. System without RACF ES1011.0

Notes:

• We have several general users of our system. These users have multiple job functions and therefore need access to various resources to do their jobs.

• Without an access control mechanism, they can access any resources they want. There are no restrictions on data access.

• Resources could be accessed accidentally or intentionally.


General users Resources

CICStransaction

IMStransaction

Dataset

Tape

VMminidisk

System without RACF

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-29. System with RACF: User authentication ES1011.0

Notes:

Security Server RACF has four major functions. The first of these is the identification and verification of users.

• Is user defined to Security Server RACF?

• Is the password valid?

• Is the user a member of a Security Server RACF group?

• Has the user been suspended (revoked)?

• Is user authorized for that terminal?

• Is user authorized for that application?

• Is user authorized to log on at this time-of-day or day-of-week?

• Can this terminal be logged onto at this time-of-day or day-of-week?


General usersUser

identificationand

verificationLogonUser1

User3

User2

RACF database

User2

Resources

CICStransaction

IMStransaction

Dataset

Tape

VMminidisk

z/OS RACF

System with RACF: User authentication

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-30. Password and password phrase ES1011.0

Notes:

RACF will allow you to specify a password or a password phrase for a user. Passwords 1-8 characters long are assumed to be passwords. Passwords 9-100 characters long are assumed to be password phrases.

A password is a string of up to eight characters.

A password phrase is a string consisting of mixed case letters, numbers, and special characters, including blanks, that is used to control access to data and systems.

• Nine to 100 characters in length • Mixed-case, including alphabetic, numeric, and a large selection of special characters

including blanks • Basic syntax rules: User ID cannot appear in phrase; must contain at least two

alphabetic and at least two non-alphabetic characters; must not contain more than two consecutive identical characters

• Can provide better interoperability with other systems that allow longer passwords • Can provide better security than 8-character passwords


Password and password phrase• Users can have both a password phrase and a password.• You can log on with either:

– Password or – Password phrase

• If a user enters a password of eight characters or less, it is passed to the security product as a password.

• If a user enters a password of nine or more characters, it is passed to the security product as a password phrase.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

.

Figure 2-31. User profile ES1011.0

Notes:

• A Security Server RACF user profile is defined for all valid users of the system.

• The name of a user profile is the user ID.

• The owner of a profile (can be a user or a group) has complete control over the profile.

• The password or password phrase entry is encrypted.

- The encrypted password entry is unable to be read by listing the user profile entry.

- If a user forgets or otherwise has problems with a password, the administrator cannot tell the user the password. The administrator can reset the password to an agreed-upon temporary password that the user must change at the next logon.


Userid OwnerPassword /phrase

AttributesSecurityclassification

GroupsSegments

TSO DFP

Encrypted

CICS

User profile

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

• Most users do not possess any user attributes.

- The security administrator possesses the SPECIAL user attribute, which allows almost all Security Server RACF commands to be issued.

- The AUDITOR attribute allows a user to look at all RACF profiles and specify any logging.

- The OPERATIONS attribute allows a user to access all z/OS data sets and zVM resources.

- The PROTECTED attribute defines a protected user. A protected user cannot enter the system by any means that would normally require a password / phrase to be specified, such as a TSO or CICS logon.

• Security classification is optional and is an additional way to control a user's authority to access sensitive resources.

• Each user is connected to at least one group. Users can be connected several groups. One of these groups is designated as the user's default group.

• The RACF user profile is made up of a base segment, and can have several other segments, such as a TSO, DFP, CICS, OPERPARM, WORKATTR, OMVS, NETVIEW, DCE, or LANGUAGE segment.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-32. Groups ES1011.0

Notes:

Every user is a member of a group. A user can be an active member of any number of additional groups. A user is said to be connected to these groups. One of these groups has been defined as the user's default group.

Logically, groups are likely to fall into the following types:

• Functional groups

• Resource control groups

• Administrative groups

We consider only the functional group, which is named because all of the members of the group perform the same job function and therefore need access to the same resources.


Administrativegroup

Functional group Resource groupFunctional group

Clerks Analysts Data

Groups

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-33. Security Server RACF group terminology ES1011.0

Notes:

• Each group, with the exception of SYS1, has a superior, or owning, group. In the visual, the group DIVA is the superior group of group DIVASALE.

• DIVA has two subgroups, DIVASALE and DIVAUADM. • DIVASALE has two subgroups, DIVACUSR and DIVAORDE. • The superior group of DIVACUSR is DIVASALE. • Note that each group profile has an owner. The owner can be either a Security Server

RACF-defined user or group. • When a user is a member of a group, we say that user is connected to the group. • A Security Server RACF user must be connected to at least one group and might be

connected to several groups. • In the diagram, users TOM, SUE, JOE, and ANN are all connected to the DIVAUADM

group. TOM and SUE are also connected to the DIVACUSR group. JOE and ANN are also connected to the DIVAORDE group.

• One of a user's connect groups is designated as the user's default group.


Security Server RACF group terminology

Owner=DIVASALE

DIVAORDE

TOMSUE

JOE

ANN

Superiorgroup

Subgroup

User-to-groupconnection User

Owner=SECADMIN

DIVA

Owner=DIVA Owner=DIVA

DIVASALE DIVAUADM

DIVACUSR

Owner=DIVASALE

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-34. Resource authorization checking ES1011.0

Notes:

The second of Security Server RACF's primary tasks is resource authorization checking:

• When a user attempts to access a specific resource, Security Server RACF is called to determine whether this user should be allowed to access the resource.

• Security Server RACF can be used to control access to many types of resources, such as z/OS data sets, CICS and IMS transactions, and zVM minidisks.

• When a user attempts to access a resource, Security Server RACF is called to determine whether this user should be allowed to access the resource.

• Security Server RACF refers to a resource profile to determine access.


General users

RACF Database

Resource

Access Request

User1

User3

User2

Useridentification

andverification

Resourceauthorization

checking

z/OS RACF Resources

CICStransaction

IMStransaction

Dataset

Tape

VMminidisk

Resource authorization checking

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-35. Resource managers and RACF ES1011.0

Notes:

• Security Server RACF provides a generalized authorization service that can be invoked with the RACROUTE macro.

• The user requests access to a resource that is protected by Security Server RACF.

• A resource manager issues a Security Server RACF macro (RACROUTE REQUEST=AUTH) to find out whether the user should be allowed to access the resource.

• Security Server RACF refers to the Security Server RACF database or in-storage Security Server RACF tables to make a decision to allow or deny access to the resource.

• Security Server RACF passes its decision back to the resource manager which then actually allows or denies the access.

SAF: System Authorization Facility


Responseto user

ResourceManager

SAF Security Server RACF

processing

RACFdatabase

RACROUTEUserrequest

Resource managers and RACF

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-36. RACF resource profile ES1011.0

Notes:

• Here we see the schematic of a resource profile.

• The name of a resource profile can be either the exact resource name or a generic resource name.

• The owner of a profile has complete control over the profile.

• The universal access authority (UACC) is the level of access (such as NONE or READ) that most of the users are allowed to this resource. This is sometimes called the default level of access.

• The Access List contains the names of users who are exceptions to the UACC.

• Security classification is optional.

• Auditing specifies the types of accesses, whether successful accesses or access violations, that are to be recorded.


Profilename Owner UACC

Accesslist

Securityclassification Auditing

RACF resource profile

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-37. Access authorities for data sets ES1011.0

Notes:

ALTER For generic profiles, the specified user or group has full access to the resource and can create new data sets covered by this generic profile. Only the profile owner, the SPECIAL user, and group-SPECIAL users have the ability to administer the profile to give access to other users. For discrete profiles, the specified user has full access to the resource and can authorize other users and/or groups to access the resource.

CONTROL For VSAM data sets, this is the same access as the VSAM control interval password. Same as UPDATE for non-VSAM data sets.

UPDATE The specified user or group is allowed to access the resource for the purpose of reading or writing.

READ The specified user or group is allowed to access the resource for the purpose of reading only.


ALTER

CONTROL

UPDATE

READ

EXECUTE

NONE

Access authorities for data sets

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

EXECUTE This access level has meaning only for z/OS load libraries. This access level allows a user to open the data set for the purpose of loading a program from the library.

NONE The specified user or group is not allowed to access the resource.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-38. Example: Authorization checking ES1011.0

Notes:

For this resource:

• Clerks have READ access. • All other users, including analysts, have the default access NONE.


Example: Authorization checking

Owner UACC Auditing

NONE Clerks(READ)

Clerks Analysts

User1 User5User2 User3

User4

GROUP GROUP

Profilename

Accesslist

Securityclassification

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-39. Protecting catalogs example ES1011.0

Notes:

Catalogs are VSAM data sets that need to be protected. Different catalog types need different universal and specific access controls.

• Master catalog:

- System programmers who have the responsibility of maintaining the master catalog require ALTER access.

- People responsible for defining aliases in the master catalog require UPDATE access.

- All users need READ access to the master catalog.

• User catalogs:

- Persons who have the responsibility of maintaining user catalogs require ALTER access to the appropriate catalogs.

- Users update the user catalog when they allocate new data sets and should, therefore, be given UPDATE access to the appropriate user catalogs.


System maintenance• Access = ALTER

Data Manager• Access = UPDATE

Other users• Access = READ

System maintenance• Access = ALTER

Users• Access = UPDATE

Mastercatalog

Usercatalogs

Protecting catalogs example

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-40. PROTECTALL (Protect - all) ES1011.0

Notes:

• When PROTECTALL is activated, it prevents any access to a data set not covered by either a discrete or generic data set profile.

• The exceptions to PROTECTALL are SPECIAL users and privileged or trusted started tasks which are allowed to access unprotected data sets. These exceptions allow recovery if a critical data set profile is accidentally deleted.

• PROTECTALL is activated by the SETROPTS command. It can be initially implemented in WARNING mode to allow for a smooth transition to a PROTECTALL environment.

• By activating PROTECTALL, an installation can enforce data set naming conventions and ensure that all data sets are covered by a Security Server RACF data set profile.


Trusted orprivileged

started task

Users

Protected data sets

Unprotected data setsSPECIAL

AccessAccess

Acces

sAccess

SPECIAL

PROTECTALL (Protect – all)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-41. Logging and reporting ES1011.0

Notes:

The third major function Security Server RACF performs is logging and reporting of attempts to access resources.

• After Security Server RACF has made the decision to allow or deny access to the requested resource, it checks to see if any logging was requested. Auditing can be specified by the security administrator or the auditor.

• If logging is requested, then the access event is written to System management Facilities (SMF).

• Additionally, a message is sent to the system console when a violation occurs. Optionally, a notification can be sent to a specific user.

• The SMF data can be processed to produce reports.


Resources

Useridentification and

verification


checking

z/OS RACF

Accessviolation RACF database

Resource

Logging andreporting SMF Report

General users

User1

User3

User2 Accessrequest

Accessevent

CICStransaction

IMStransaction

Dataset

Tape

VMminidisk

Violation

Logging and reporting

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-42. RACF major functions ES1011.0

Notes:

This visual summarizes the major functions of Security Server RACF:

• When a user attempts to enter the system, Security Server RACF verifies the user's identity by checking the user profile in the Security Server RACF database. This process is called user identification and verification or user authentication.

• When a user attempts to access a resource, Security Server RACF performs access authorization checking.

• Access events are logged to SMF based upon the auditing specified in the resource profile and the Security Server RACF options.

• The security administrator (SPECIAL) defines user, group, and resource profiles and sets the system options by using either Security Server RACF commands or ISPF panels.

• The AUDITOR is responsible for auditing the security system and does this by looking at the profiles, specifying logging, and running reports.

• The user with the OPERATIONS attribute can access data in order to maintain the volumes on the system.

• The profiles are stored in the Security Server RACF database.


Useridentification and

verification


checking

z/OS RACF

Accessviolation

RACF database

Resource

Logging andreporting

SMF Report

General users

User1

User3

User2 Accessrequest

Accessevent

ResourcesCICS

transactionIMS

transaction

Dataset

Tape

VMminidisk

Violation

SPECIAL Security Administration

AdministrationAUDITOR Look at Profiles and Set Logging

Access

RACF major functions

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-43. RACF - Services Option Menu ES1011.0

Notes:

• This is the main menu for the Security Server RACF panels.

• Here we choose option 3 to get to the group panels.


RACF - SERVICES OPTION MENU OPTION ===>

SELECT ONE OF THE FOLLOWING:

1 DATA SET PROFILES

2 GENERAL RESOURCE PROFILES

3 GROUP PROFILES AND USER-TO-GROUP CONNECTIONS

4 USER PROFILES AND YOUR OWN PASSWORD

5 SYSTEM OPTIONS

6 REMOTE SHARING FACILITY

7 DIGITAL CERTIFICATES, KEY RINGS, AND TOKENS 99 EXIT

Licensed Materials - Property of IBM 5647-A01 (C) Copyright IBM Corp. 1983, 2000 All Rights Reserved - U.S. Government Users Restricted Rights, Use, Duplication or Disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

RACF - Services Option Menu

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-44. RACF - Group Profile Services panel ES1011.0

Notes:

• To display a group profile, we begin by selecting the DISPLAY option from this panel.

• The group name is entered at the GROUP NAME ===> prompt.


RACF - GROUP PROFILE SERVICESOPTION ===> d

SELECT ONE OF THE FOLLOWING.

1 ADD Add a group profile2 CHANGE Change a group profile3 DELETE Delete a group profile4 CONNECT Add or change a user connection5 REMOVE Remove users from the group

D or 8 DISPLAY Display profile contentsS or 9 SEARCH Search the RACF data base for profiles

ENTER THE FOLLOWING INFORMATION.

GROUP NAME ===> divasale

RACF - Group Profile Services panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-45. RACF - Display for Group Profile panel ES1011.0

Notes:

We did not specify any items on this panel since we did not want to display the DFP or OMVS segments.


RACF - DISPLAY FOR GROUP PROFILE

COMMAND ===>

To select the following options, enter any character.

_ Include DFP information

_ Include OMVS information

_ Include OVM information

_ Exclude basic RACF information

RACF - Display for Group Profile panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-46. Display of a group profile ES1011.0

Notes:

• Here is the output of the display for a group profile.

• Note that it shows the superior group and all subgroups.

• No users are connected to this group.

• If any users are connected to a group, those user IDs are listed on this display.


BROWSE - RACF COMMAND OUTPUT---------------------- LINE 00000000 COL 080

COMMAND ===> SCROLL ===> PAGE

********************************* Top of Data **************************

INFORMATION FOR GROUP DIVASALE

SUPERIOR GROUP=DIVA OWNER=DIVA

INSTALLATION DATA=FUNCTIONAL GROUP FOR DIVISION A SALES DEPT.

NO MODEL DATA SET

TERMUACC

SUBGROUP(S)= DIVACUSR DIVAORDE

NO USERS

******************************** Bottom of Data ************************

Display of a group profile

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-47. RACF - User Profile Services panel ES1011.0

Notes:

• To display a user profile with the panels, we use Option D or 8 on the Security Server RACF - USER PROFILE SERVICES panel.

• The User ID is entered on the bottom line at the prompt (===>).


RACF - USER PROFILE SERVICESOPTION ===> 8

SELECT ONE OF THE FOLLOWING:

1 ADD Add a user profile2 CHANGE Change a user profile3 DELETE Delete a user profile4 PASSWORD Change your own password or interval5 AUDIT Monitor user activity (Auditors only)

D or 8 DISPLAY Display profile contentsS or 9 SEARCH Search the RACF data base for profiles

ENTER THE FOLLOWING INFORMATION:

USER ===> tom Userid

RACF - User Profile Services panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-48. RACF - Display for User Profile panel ES1011.0

Notes:

• Here you can select to list any of the segments of the user profile.


RACF - DISPLAY FOR USER PROFILECOMMAND ===>

To select the following options, enter any character.

To select the following options, enter any character._ TSO_ NETVIEW_ DFP_ DCE_ OPERPARM_ OVM_ CICS_ LNOTES_ NATIONAL LANGUAGE_ NDS_ WORK ATTRIBUTES_ KERBEROS_ LDAP PROXY_ OMVS_ EIM

_ Exclude basic RACF information

RACF - Display for User Profile panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-49. RACF display user ES1011.0

Notes:

The display of a user profile shows information about the user, including any groups to which the user is connected. In this display, we did not ask for any segments to be displayed.


BROWSE - RACF COMMAND OUTPUT---------------------- LINE 00000000 COL 080COMMAND ===> SCROLL ===> PAGE********************************* Top of Data **************************USER=TOM NAME=TOM SMITH OWNER=DIVAUADM CREATED=00.180 DEFAULT-GROUP=DIVAUADM PASSDATE=00.271 PASS-INTERVAL=90 ATTRIBUTES=NONE REVOKE DATE=NONE RESUME DATE=NONE LAST-ACCESS=00.280/11:52:21 CLASS AUTHORIZATIONS=NONE INSTALLATION-DATA=TOM SMITH, DEPARTMENT 32E, DIVISION A NO-MODEL-NAME LOGON ALLOWED (DAYS) (TIME) ---------------------------------------------ANYDAY ANYTIME GROUP=DIVAUADM AUTH=USE CONNECT-OWNER=DIVAUADM CONNECT-DATE=00.180CONNECTS= 144 UACC=NONE LAST-CONNECT=00.280/11:52:21 CONNECT ATTRIBUTES=NONE REVOKE DATE=NONE RESUME DATE=NONE

SECURITY-LEVEL=NONE SPECIFIED CATEGORY-AUTHORIZATION NONE SPECIFIED SECURITY-LABEL=NONE SPECIFIED ******************************** Bottom of Data *************************

RACF display user

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-50. User and group data sets ES1011.0

Notes:

Types of data • Data can come in many forms. Not all of those forms can be protected by Security

Server RACF. • While paper, paper tape, punched cards, and the like do not come under the control of

Security Server RACF, items such as DASD and TAPE do. Types of data sets • There are three types of data sets:

USER The high-level qualifier (HLQ) for the data set name is the same as a Security Server RACF-defined user.

GROUP The HLQ for the data set name matches the name of a Security Server RACF-defined group.

OTHER All others. The HLQ does not match a Security Server RACF-defined user ID or group. Security Server RACF does not allow you to define data set profiles unless the HLQ is either a Security Server RACF user or group.


BILL.DATA

PAY .SAL.MAR2000

A.B.C

User profileBill

Group profilePAY

User data set

Group data set

Other data set

User and group data sets

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-51. Data set profile ES1011.0

Notes:

• The key information that Security Server RACF stores in the data set profile is:

- The data set profile name. - The profile owner, which can be either a Security Server RACF-defined user or

group. - The universal access authority (UACC), which is the level of access that is allowed

to anyone on the system. Also known as the default access. - The access list, which specifies those users and/or groups who can access the

resource at a level different from the UACC. - Security classifications (levels, categories and security labels). - Auditing, which specifies what access attempts will be logged. - User ID to notify if an access violation occurs. - Warning indication. - The DFP segment can be used to specify a resource owner. This does not pertain to

security. It is used to provide input to DFSMS when a new data set is allocated.


Data set profile

Data setprofilename

Owner UACC Accesslist

Securityclassification

Auditing

Notify Warning DFPsegment

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 2-52. Discrete and generic profiles ES1011.0

Notes:

Discrete data set profile:

• The profile is mapped one-to-one with the resource. • The name of the profile is the same as the name of the data set. • The profile contains volume and unit information. • For a discrete data set profile, the Security Server RACF indicator bit is set in the VTOC

for a non-VSAM data set or the catalog for a VSAM data set.

Generic data set profile:

• A generic profile can cover several data sets. • The three data sets in the picture are all covered by the one generic profile. • The %, *, and ** are generic characters. If they appear in a profile name, the data set

profile is considered to be a generic profile. • It is possible to define a fully qualified generic data set profile. The name of a fully

qualified generic data set profile does not have a generic character in the profile name.


HLQ.X.DATA

HLQ.Y.DATA

HLQ.Z.DATA

HLQ.*.DATA

Discrete profile Generic profile

HLQ.X.DATA

HLQ.Y.DATA

HLQ.Z.DATA

HLQ.X.DATA

HLQ.Y.DATA

HLQ.Z.DATA

Discrete and generic profiles

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-53. Generic versus discrete profiles ES1011.0

Notes:

• This visual summarizes the differences between generic and discrete profiles.

• Because of the advantages of generic profiles, we generally avoid the use of discrete profiles in z/OS.

• In a shared DASD environment, the Security Server RACF database should also be shared. This is especially important with generic profiles. Otherwise, a system that is sharing the data could have a Security Server RACF database with different data set profiles. Thus, the data set could have different access depending upon which system a user was logged onto when accessing the data set.

• A Security Server RACF-indicated data set cannot be accessed unless a data set profile exists that protects it. When the Security Server RACF indicator bit is set but a discrete profile does not exist, this is known as an out-of-sync condition.

• The Security Server RACF indicator bit is set on and a discrete profile is created when:

- A user who has the automatic data set protection (ADSP) attribute allocates a new data set.


DiscreteGeneric

Generic versus discrete profiles

• Many data sets can be protected with one profile

• Profile exists even if all data sets are deleted

• Covers data sets on any volume

• No RACF indicator bit on• Easier to administer

• One profile for each data set• Profile automatically deleted

when data set is deleted• Specific to a volume and unit• RACF indicator bit set on

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

- A batch job is submitted that has PROTECT=YES coded on a DD statement in the JCL.

- An administrator uses the ADDSD command (or Security Server RACF panels) and specifies a fully qualified name (no generic characters) for the data set profile name.

• The Security Server RACF indicator bit is set on in the VTOC for Non-VSAM data sets. The Security Server RACF indicator bit is set on in the catalog entry for VSAM data sets.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 2-54. PERMIT command ES1011.0

Notes:

• Use the PERMIT command to build and maintain the lists of users and groups that are authorized to access a particular resource.

• To use PERMIT, one of the following conditions must be met: - You have the SPECIAL attribute. - The profile is within the scope of a group in which you have the group-SPECIAL

attribute. - You are the owner of the resource. - If the resource is a DATASET, the high-level qualifier of the profile is your user ID. - For a discrete profile:

• You are on the access list with ALTER authority. • Your group to which you are connected is on the access list with ALTER

authority. • The UACC is ALTER.


PERMIT command

To grant or revoke access to resources we own

PAY.SAL.** NONEPRUSER(UPDATE)

WHEN(PROGRAM(PAYUPD))PRUSER(READ)

PERMIT 'PAY.SAL,**' ID(PRUSER) ACCESS(READ)

PERMIT 'PAY.SAL.** ' ID(PRUSER) ACCESS(UPDATE) WHEN(PROGRAM(PAYUPD))

PAY.SAL.DATA

Read

Update

PRUSER PAYUPD

StandardProfile name UACC access list Conditional access list

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Identify the main functions of Security Server (RACF) and the

role it plays in controlling user access to the system• Describe the contents of RACF user, group, and resource

profiles• Describe how RACF profiles are used to authorize user access

to a data set resource

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (1 of 2)1. Which one of the following is not a major task of the Security Server

RACF? a. User identification and verification b. Resource authorization checking c. System access facility d. Logging and reporting e. Administration

2. True or False: Security Server RACF protects data sets with generic and discrete profiles. If a data set does not have a discrete profile, a generic profile protects it.

3. True or False: If the universal access authority (UACC) PROTECTALL entry in a user's profile is set to Control or higher, the user has full access to all resources.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (2 of 2)4. Which of these is not a method of navigating through the

ISPF dialogs?a. Action barb. TSO commandsc. Point-and-shootd. Option numbers

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Unit summaryHaving completed this unit, you should be able to:• Name the components of ISPF• Describe the general layout of ISPF/PDF panels• Identify the main ISPF/PDF options• Be able to run a simple TSO session:



• Describe the contents of RACF user, group, and resource profiles• Describe how RACF profiles are used to authorize user access to a

data set resource

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Unit 3. Working with ISPF/PDF


This unit teaches students how to perform the essential data set management tasks using ISPF/PDF dialogs. In this unit students learn how to allocate, copy, move, rename, and delete a data set or member, as well as how to use the ISPF/PDF editor.



• Allocate a new sequential or partitioned data set • Edit a data set using the ISPF/PDF editor

- Display and modify the edit profile, control scrolling, and manage multiple screens

- Use commands such as FIND, BOUNDS, CHANGE, CREATE, and MOVE when working with a data set member

• Use ISPF/PDF line commands in the prefix area • Copy or move an entire data set or selected members • Rename a data set or member • Delete an entire data set or a single member • Work with data set lists (ISPF/PDF option 3.4)



References

SC26-7410 DFSMS Using Data Sets

SC34-4822 ISPF User’s Guide Vol I

SC34-4820 ISPF Edit and Edit Macros

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 3. Working with ISPF/PDF 3-1

Student Notebook

.


Notes:


Unit objectivesAfter completing this unit, you should be able to:• Allocate a new sequential or partitioned data set• Edit a data set using the ISPF/PDF editor

– Display and modify the edit profile, control scrolling, and manage multiple screens

– Use commands such as FIND, BOUNDS, CHANGE, CREATE, and MOVEwhen working with a data set member

• Use ISPF/PDF line commands in the prefix area• Copy or move an entire data set or selected members • Rename a data set or member • Delete an entire data set or a single member • Work with data set lists (ISPF/PDF option 3.4)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3.1. Allocating data sets

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-2. Allocating data sets ES1011.0

Notes:


Allocating data sets


Editing data sets: The ISPF/PDF editor

Editing data sets: Line commands

Copying, moving, renaming, deleting data sets and data set members

Working with data set lists

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Allocate a new sequential or partitioned data set

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-4. Allocating data sets ES1011.0

Notes:

Data sets in z/OS do not only differ in their content, name, length, and data set type, but also vary internally in the length and format of their records.

z/OS data sets can have both logical records and physical records.

• A logical record is the unit of data that the program wants to process. It usually consists of a number of fields concatenated together.

• A physical record describes the amount of data transferred in an I/O operation.

Combining multiple logical records in a single physical record (called blocking) has certain advantages over storing and retrieving a logical record as a physical record. These include a more efficient space usage as well as an improved performance when transferring data.


Physical recordLogical record

How the data isheld

Unit of datatransfer fromdevice

What the program wants to process

Data set

Allocating data setsLogical and physical records

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-5. Record format and blocking ES1011.0

Notes:

Upon allocation of a new data set, users have to specify a record format. The most commonly used record formats are the fixed-length record format and the variable-length record format.

A fixed-length record format tells the system that all records within the data set are of the same length, that is, they all require the same amount of space, whether they contain only a single character or many characters.

The variable-length record consists of records that vary in length according to their content. This means records that hold little data require less storage than those containing a lot of data. The actual length of a record is specified within it as part of the record.

Both fixed as well as variable format records are commonly grouped in blocks, thus saving space and requiring fewer I/O operations than unblocked record storage. Blocking is the process of storing multiple data set records in a single block. Whenever an I/O operation takes place, an entire block rather than a single record is transferred.


BLOCKSIZE BLOCKSIZE + GAPUTILIZATION

Fixed-length recordunblocked

Fixed-length recordblocked

Variable-length recordunblocked

Variable-length recordblocked

Record format and blocking

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-6. z/OS data set types (1 of 2) ES1011.0

Notes:

Sequential data set

In a sequential data set, also referred to as physical sequence (PS), records are arranged sequentially in the order in which they are written. New records are appended at the end of the data set. In sequential data sets, data is organized for sequential access. To retrieve the fifth record of the data set, the system first has to read the preceding four. Sequential data sets can be stored on DASD or on tape. They are required for the use of magnetic tape devices or printed output.


Emp# Name Dept Salary

A logical record: The unit of data that the program will process

Record 1 EOFRecord nRecord ...Record 4Record 3Record 2

z/OS data set types (1 of 2)

• A sequential data set:– Records in the sequence they were entered, with an End of File

marker at the end.– Records cannot be deleted and can only be inserted at the end.– Records must be read in sequence.

• For example, to read record 3, records 1 and 2 must be read first.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-7. z/OS data set types (2 of 2) ES1011.0

Notes:

Partitioned data set

A partitioned data set (PDS) is divided into sequentially organized members, each of which can have one or more records. Each member has a unique name, stored in a directory that is part of the data set. The directory is located at the beginning of the data set and contains an entry for each member. Each directory entry contains the member name and the starting location of the member within the data set. The directory entries are arranged by name in alphanumeric collating sequence. The main advantage of using a partitioned data set is that, without searching the entire data set, you can retrieve any individual member after the data set is opened. Individual members can be added or deleted as required. A deleted member is removed from the directory. Its space cannot be reused until the data set is reorganized using a system utility.

Partitioned data set extended

In appearance, a partitioned data set extended (PDSE) is very similar to a partitioned data set. For accessing a partitioned data set directory or member, most PDSE interfaces are


Directory entries forA, B, C, D

Member C

Member A

Member B

Member D

Member D

Directory entries forE, X

Member E

Member X

Free space ofdeleted member

Free space

Free Space Free space

Free space

Partitioned data set extended

(Directory entries)

Member A

Member A Free space

Member D

Member B

Space of deleted member

Member C

Member D

A B C D Free space

Space of deleted member

Partitioned data set

z/OS data set types (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

indistinguishable from PDS data set interfaces. However, PDSEs have a different internal format, which gives them increased usability.

The main advantage of using a PDSE over a PDS is that PDSEs use DASD space much more efficiently. The size of a PDS directory is fixed regardless of the number of members in it, while the size of a PDSE directory is flexible and expands to fit the members stored in it. Also, the system reclaims space automatically whenever a member is deleted or replaced and returns it to the pool of space available for allocation to other members of the same PDSE. The space can be reused without having to reorganize the data set.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-8. VSAM data set types ES1011.0

Notes:

VSAM supports the following types of data sets:

ESDS An entry-sequenced data set is comparable to a sequential (non-VSAM) data set. Records are sequenced by the order of their entry in the data set, rather than by a key field in the logical record. Records are only added at the end of the data set. Existing records cannot be deleted, only flagged as inactive.

KSDS In a key-sequenced data set, logical records are placed in the data set in ascending collating sequence by a field, called the key. The key contains a unique value, such as an employee number or part number, which determines the record's collating position in the data set. The key must be in the same position in each record, the key data must be contiguous, and each record's key must be unique. After it is specified, the value of the key cannot be altered, but the entire record can be erased or deleted. When a new record is added to the data set, it is inserted in its collating sequence by key.


Entry-sequenced data setRecord 1 Record 2 Record 3 Record n...............

Linear data set...Unstructured bit-stream...

Key-sequenced data set

Key KeyKeyData Data Data.......Record 1 Record 2 Record n

Index

Relative record data setRecord Empty Record Record...............Slot 1 Slot 3Slot 2 Slot n

Record 1 Record 2 Record n...........Empty

Fixed

Variable

VSAM data set types

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

A key-sequenced data set always has an index that relates key values to the relative locations of the logical records in a data set. This index is called the prime index, or simply index. It has two uses:

• To locate the collating position when inserting records

• To locate records for retrieval

LDS A linear data set is a VSAM data set with a control interval size of 4096 bytes to 32768 bytes in increments of 4096 bytes. A linear data set has a block size of 4096 bytes and does not have embedded control information. All linear data set bytes are data bytes. A linear data set is processed as an entry-sequenced data set, with certain restrictions. Because a linear data set does not contain control information, it cannot be accessed as if it contained individual records.

RRDS A fixed-length relative record data set consists of several fixed-length slots. Each slot has a unique relative record number, and the slots are sequenced by ascending relative record number. Each record occupies a slot and is stored and retrieved by the relative record number of that slot. The position of a data record is fixed; its relative record number cannot change. Because the slot can either contain data or be empty, a data record can be inserted or deleted without affecting the position of other data records in the fixed-length RRDS.

A variable-length RRDS is similar to a fixed-length RRDS, except that it contains variable-length records. Each record has a unique relative record number and is placed in ascending relative record number order. Each record is stored and retrieved using its relative record number. Unlike a fixed-length RRDS, a variable-length RRDS does not have slots. The relative record number of a record cannot change. When that record is erased, the relative record number can be reused for a new record.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-9. Data set naming rules ES1011.0

Notes:

Before allocating a new data set, we briefly discuss the data set naming rules.

• A data set name consists of one or more parts, called qualifiers. They are connected by periods (.).

• Each qualifier must be a simple name. - A simple name is up to eight characters long. - The first character of a simple name can be alphabetic (A-Z) or a national

character (@, #, ¢). - The second through eighth character of a simple name can be alphabetic

(A-Z), a national character (@, #, ¢), or a numeric (0-9). • The maximum length of a data set name is 44 characters (including the

connecting periods). Qualifiers must be simple names. The leftmost qualifier is known as the high-level qualifier (hlq), and the rightmost qualifier is known as the low-level qualifier (llq).


Examples: ASYS1.PROCLIBPETE.TESTACCT.B100.DATAPAYROLL.DAILY.BACKUP.G0012V00

Qualifier_1.qualifier_2.qualifier_3. ...... Qualifier_n

Maximum 44 characters

Simple name

What is the maximum number of qualifiers?

Data set naming rules• Data set name:

– Simple names joined by periods(.), with a maximum of 44 characters

• Simple name:– One to eight characters long– First character is A thru Z @ # $– Second through eighth characters

are A thru Z @ # $ and/or 0-9

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

N

A partitioned data set (PDS) or a partitioned data set extended (PDSE) is also referred to as a library. System libraries usually have a two-level (two qualifier) data set name. TSO user libraries usually have a three-level (three qualifier) data set name.

The maximum number of qualifiers is _________.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-10. Partitioned data set naming rules ES1011.0

Notes:

The PDS and PDSE data sets are named exactly the same as other z/OS data sets.

PDSs and PDSEs are host to members, which are really just (small) sequential data sets.

To allocate a member of a PDS or PDSE, we add the membername (enclosed in parentheses) to the end of the data set name.

The maximum length of a data set name including the member name and parentheses is 54 characters.


Examples: SYS1.PROCLIB(COB2UCLG)TSOFS20.PAYROLL.COBOL(CALCTAX)

Dataset.Name.Up.To.Forty.Four.Char.Acters(Membname)

Dataset Name - max. 44 Characters

Member Name - max 8 charactersTo reference a member of a partitioned data set:

Dataset.Name.Up.To.Forty.Four.Char.Acters

Dataset Name - max. 44 Characters

To reference the whole partitioned data set:

Examples: SYS1.PROCLIBTSOFS20.PAYROLL.COBOL

Partitioned data set naming rules

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-11. Data set naming conventions ES1011.0

Notes:

In addition to the rules for the naming of data sets, certain conventions, especially for ISPF/PDF, apply. These conventions are:

• Sequential as well as partitioned data sets have a name consisting of three qualifiers, PROJECT, GROUP, and TYPE.

• PROJECT is the common identifier for all ISPF data sets belonging to the same programming project. PROJECT usually equals your user ID, unless a specific name has been defined.

• GROUP defines a particular set of ISPF data sets belonging to the same project. GROUP could reflect the application the data set belongs to or perhaps the name of the programmer who owns it. In any case, it is usually a meaningful name.

• TYPE identifies the kind of information stored in the data set, whether it is code, data, or text.


Examples: TSOFS20.TEST.CNTL

SAM.ISPF.EXEC

Data set naming conventions• Conventions:

– Data set names can consist of up to 22 qualifiers but are usually a lot less.

– TSO user data set names usually consist of three qualifiers, known as PROJECT.GROUP.TYPE.

– The PROJECT field reflects your TSO profile prefix or a valid user ID.– The GROUP field is a user-defined, meaningful name, for example, JOB, TEST, ISPF.

– The TYPE field describes the type of data stored, for example, CNTL, DATA, EXEC, ASM, PLI.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-12. Entering data set and library names ES1011.0

Notes:

Any cataloged data set with a three-level name can be entered in the PROJECT, GROUP, and TYPE fields. If a data set name with more or less than three qualifiers is to be specified, the name must be entered in the Other Partitioned or Sequential Data Set field.

N

If you specify the full data set name, known as the fully qualified name, enclose it in single quotes: 'data set name'. If you omit the quotes (and a TSO prefix is defined), that prefix is added as the data set name's first qualifier.

To refer to a member, add its name enclosed in parentheses at the end of the data set name, for example, TSOFS20.ISPF.PANELS(PANEL01). If both an ISPF Library name and an Other Partitioned or Sequential Data Set name are specified on the same panel, the Other Partitioned or Sequential Data Set name takes precedence.


ISPF Library:

Project . . . TSOF0_Group . . . . TSOE . . . . . . . . .

Type . . . . CNTLMember . . . _ (Blank or pattern for member selection list)

Other Partitioned or Sequential Data Set:

Data Set Name . . . ‘TSOFS20.TEST.CNTL'Volume Serial . . . (If not cataloged)

ISPF Library:

Project . . . TSOFS20_Group . . . . TSOE . . . . . . . . .

Type . . . . CNTLMember . . . _ (Blank or pattern for member selection list)

Other Partitioned or Sequential Data Set:

Data Set Name . . . TEST.CNTL(JOB23)__ _______________________Volume Serial . . . (If not cataloged)

- - - - - - - - - - - - - - - - - - - - - - - -

Entering data set and library names

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-13. Entering member names ES1011.0

Notes:

On almost every panel that allows for the specification of a data set, a member entry field is available.

To select a single member, enter the member name, and the action (edit and so forth) will be performed for that member only. If you leave the member field blank, ISPF displays a member list, from which you select a member.

Instead of a complete member name, you can enter a pattern made up of a partial member name plus pattern characters. The pattern characters are % and *. The character % represents a single character and * represents zero to multiple characters. ISPF then displays all member names that match the pattern.

Here is another example: Project . . . TSOFS20 Group . . . . TEST Type . . . . EXEC Member . . . A*

This will select all members starting with the character A.


- - - - - - - - - - - - - - - - - - - - - - - -

ISPF Library:


Type . . . . CNTLMember . . . JOB23 (Blank or pattern for member selection list)

Other Partitioned or Sequential Data Set:Data Set Name . . . _______________________ Volume Serial . . . (If not cataloged)

ISPF Library:


Type . . . . CNTLMember . . . J%B2 (Blank or pattern for member selection list)

Other Partitioned or Sequential Data Set:Data Set Name . . . _____________________ _______________________Volume Serial . . . (If not cataloged)

Entering member names

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-14. ISPF Primary Option Menu ES1011.0

Notes:

To get to the Utility Selection panel, choose option 3 from the ISPF Primary Option Menu.


Menu Utilities Compilers Options Status Help------------------------------------------------------------------------------


Option ===> 30 Settings Terminal and user parameters User ID . : TSOFS201 View Display source data or listings Time. . . : 16:122 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processing Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: AUES1008 LM Facility Library administrator functions System ID : SYS19 IBM Products IBM program development products MVS acct. : ACCNT#10 SCLM SW Configuration Library Manager Release . : ISPF 5.811 Workplace ISPF Object/Action Workplace

S SDSF System Display and Search Facility


Licensed Materials - Property of IBM 5694-A01 (C) Copyright IBM Corp. 1980, 2001.All rights reserved. US Government Users Restricted Rights -Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-15. Utility Selection Panel ES1011.0

Notes:

Now that we have clarified the rules and conventions for naming ISPF data sets as well as their specification on ISPF panels, let us move on to the allocation of a new data set.

There are several ways to allocate a new data set. Data sets can, for example, be created using job control language (JCL), TSO commands, or ISPF panels. Since we have not discussed job control language nor TSO commands yet, we will use the latter approach, that is, use ISPF panels.

To allocate a new data set, select the Utility Selection panel, that is, option 3 from the ISPF Primary Option Menu. Once the Utility Selection panel is displayed, select option 2 (Data Set).


Menu Help----------------------------------------------------------------------------

Utility Selection PanelOption ===> 21 Library Compress or print data set. Print index listing. Print

rename, delete, browse, edit or view members2 Data Set Allocate, rename, delete, catalog, uncatalog, or display

information of an entire data set3 Move/Copy Move, copy, or promote members or data sets4 Dslist Print or display (to process) list of data set names.

Print or display VTOC information5 Reset Reset statistics for members of ISPF library6 Hardcopy Initiate hardcopy output7 ISPF C/S Install ISPF C/S workstation code from MVS to your workstation.8 Outlist Display, delete, or print held job output9 Commands Create/change an application command table* Reserved This option reserved for future expansion.11 Format Format definition for formatted data Edit/Browse12 SuperC Compare data sets (Standard Dialog)13 SuperCE Compare data sets Extended (Extended Dialog)14 Search-For Search data sets for strings of data (Standard Dialog)15 Search-ForE Search data sets for strings of data Extended (Extended Dialog)16 Tables ISPF Table Utility17 Udlist Print or Display (to process) z/OS UNIX directory list


Utility Selection Panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-16. Data Set Utility panel ES1011.0

Notes:

As you can see, the Data Set Utility panel offers a variety of data set-related functions.

To allocate a new data set, select option A (Allocate new data set) by entering A on the command line. Also enter the name of the new data set or library in one of the following fields:

ISPF Library: Project . . ________ Group . . . ________ Type . . . . ________ Other Portioned, Sequential or VSAM Data Set: Data Set Name . . . _____________________________________________

To continue the allocation process and specify the data set characteristics on the next panel, press Enter.


Menu RefList Utilities Help ----------------------------------------------------------------------------

Data Set Utility Option ===> a

A Allocate new data set C Catalog data set R Rename entire data set U Uncatalog data setD Delete entire data set S Data set information (short)

blank Data set information V VSAM Utilities

ISPF Library: Project . . TSOFS20Group . . . TESTType . . . . DATA

Other Partitioned, Sequential or VSAM Data Set: Data Set Name . . . Volume Serial . . . (If not cataloged, required for option "C")

Data Set Password . . (If password protected)


Data Set Utility panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-17. Allocate New Data Set panel ES1011.0

Notes:

After you have entered the data set name on the Data Set Utility panel, ISPF shows the Allocate New Data Set panel, which is used to specify the type, size, location, and so forth of the new data set. Several input fields might have been pre-entered. ISPF remembered these values from your most recent data set allocation or display of data set information. You can leave these values as displayed or specify your own values. Here is a brief overview of all fields:

Data Set Name The name of the data set to be allocated as entered on the previous Data Set Utility panel.

Volume serial The name of the volume that is to contain the newly allocated data set. This field overrides the volume serial specification on the Data Set Utility panel.

Generic unit Used to restrict the allocation volume to a specific type, such as, 3380, 3390, and so forth. The value entered in this field overrides the value entered in the Data Set Utility panel.


Menu RefList Utilities Help

Allocate New Data SetMore: +

Command ===>Data Set Name . . . : TSOFS20.TEST.DATA

Volume serial . . . . (Blank for authorized default volume) *Generic unit. . . . . (Generic group name or unit address) *Space units . . . . . TRKS (BLKS, TRKS, CYLS, KB, MB or BYTES)Primary quantity. . . 5 (In above units)Secondary quantity. . 1 (In above units)Directory blocks. . . 5 (Zero for sequential data set)Record format . . . . FBRecord length . . . . 80Block size . . . . . 0Expiration date . . . (YY/MM/DD, YYYY/MM/DD

YY.DDD, YYYY.DDD in Julian formEnter "/" to select option DDDD for retention period in daysAllocate Multiple Volumes or blank)

F1=Help F3=Exit F12=Cancel

Option ===>F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

Allocate New Data Set panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Do not specify Volume serial and Generic unit to have ISPF select an eligible volume.

Space units Specification of the units used to measure the amount of primary and secondary space allocated for the new data set (in blocks, tracks, cylinders, kilobytes, megabytes, or bytes).

Primary quantity The primary allocation quantity in units as specified in the Space units field.

Secondary quantity The secondary allocation quantity in units as specified in the Space units field. Secondary space is only allocated if the primary amount specified is not sufficient.

Directory blocks Number that determines whether the new data set is sequential or partitioned. For a sequential data set, enter 0, and for a partitioned data set, enter an integer value greater than 0.

Record format Enter a combination of the following:

F Fixed length records V Variable length records U Undefined format records B Blocked records A ASA printer control characters M Machine code printer control characters S Standard (for F) or spanned (for V) - sequential data sets

only t Track-overflow feature For a data set with fixed-length records that is to be stored in blocks, specify FB, for a blocked data set with variable-length records and ASA control records, enter VBA, and so on. You have to specify at least F, V, or U.

Record length The logical length, in bytes, of the records to be stored in the data set.

Block size The block size (or actual physical record length), in bytes, of the new data set. The block must be equal to or a multiple of the Record length.

Expiration date Specification of date when the data set might be deleted. If you try to delete an unexpired data set, ISPF prompts you to confirm your delete request.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Allocate Multiple Volumes By selecting this option you are allowed to allocate sequential data sets that span up to 20 volumes.

Once you have entered all requested data set characteristics, confirm the data set allocation request by pressing Enter.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-18. Data set allocation panel ES1011.0

Notes:

Once you have issued your data set allocation request, ISPF redisplays the Data Set Utility panel as well as a message indicating the result of the allocation request.

In case of a successful data set allocation, the message should read Data Set allocated.

In any other case, ISPF displays a message indicating the data set allocation failure and its probable cause.


Menu RefList Utilities Help--------------------------------------------------------------------------

Data Set Utility Data Set allocatedOption ===>

A Allocate new data set C Catalog data setR Rename entire data set U Uncatalog data setD Delete entire data set S Data set information (short)

blank Data set information V VSAM Utilities

ISPF Library:Project . . TSOFS20Group . . . TESTType . . . . DATA

Other Partitioned, Sequential or VSAM Data Set:Data Set Name . . . Volume Serial . . . (If not cataloged, required for option "C")



Data set allocation panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-19. Data Set Information ES1011.0

Notes:

To confirm whether the data set has been allocated according to your specifications, select the blank option from the Data Set Utility panel, enter the name of the data set that has been allocated, and press Enter. ISPF now displays the actual characteristics of the specified data set in its Data Set Information panel.


Data Set InformationCommand ===>Data Set Name . . . : TSOFS20.TEST.DATA

General Data Current AllocationManagement class . . : STANDARD Allocated tracks . : 5Storage class . . . : BASE Allocated extents . : 1Volume serial . . . : USER09 Maximum dir. blocks : 5Device type . . . . : 3390Data class . . . . . :Organization . . . : PO Current UtilizationRecord format . . . : FB Used tracks . . . . : 1Record length . . . : 80 Used extents . . . : 1Block size . . . . : 27920 Used dir. blocks . : 11st extent tracks . : 5 Number of members . : 0Secondary tracks . : 1Data set name type : PDS

Creation date . . . : 2008/10/27Expiration date . . : ***None***


Data Set Information

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Allocate a new sequential or partitioned data set

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Tasks:1. Log on to TSO.2. Allocate three data sets.

• Sequential, PDS, and PDSE

3. Log off.

Exercise

Allocate new data sets

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3.2. Editing data sets: The ISPF/PDF editor

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-22. Editing data sets: The ISP/PDF editor ES1011.0

Notes:


Editing data sets: The ISP/PDF editor






Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Edit a data set using the ISPF/PDF editor



xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-24. Editing data sets: The ISPF/PDF editor ES1011.0

Notes:

To edit a data set or member of a data set, select option 2 (Edit) from the ISPF Primary Option Menu. Enter the name of the data set or library in the following fields:

Project . . . ________ Group . . . . ________ Type . . . . ________

Alternately, specify the data set name or library here:

Other Partitioned or Sequential Data Set: Data Set Name . . . _____________________________________________ Volume Serial . . . ______

If the data set you are about to edit is partitioned organized and you know the member name, you can specify the name in the area labeled as follows:

Member . . . ________



Menu RefList RefMode Utilities LMF Workstation Help --------------------------------------------------------------------------

Edit Entry PanelCommand ===>ISPF Library:

Project . . . TSOFS20Group . . . . TSOE . . . . . . . . .Type . . . . CNTLMember . . . (Blank or pattern for member selection list)

Other Partitioned or Sequential Data Set:Data Set Name . . . ‘TSOFS20.TEST.CNTL'Volume Serial . . . (If not cataloged)


Initial Macro . . . . OptionsProfile Name . . . . . / Confirm Cancel/Move/ReplaceFormat Name . . . . . Mixed ModeData Set Password . . Edit on Workstation


Edit Entry Panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

If you know only part of the name, you can specify only that part followed by an asterisk (*), as shown in the following example:

Member . . . A*______

Once you have entered all required information, press Enter to continue.

What is the third way to specify a data set name on this panel?

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-25. Edit member selection panel ES1011.0

Notes:

If you are editing a partitioned data set and did not specify a member name or only a pattern in the Edit Entry Panel, ISPF prompts you with a member list for this data set. You can scroll through the list using the Up and Down scroll commands and select one member at a time by placing the cursor or an s in the column on the left of the member name or by entering s membername (select member name) on the command line. To continue, press Enter.


Menu Functions Utilities HelpCommand ===> select ams Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL Row 00001 of 00014

Name VV MM Created Changed Size Init Mod IDs AMS 01.03 98/06/07 08/05/17 18:23 10 10 0 TSOFS20. AMS1 01.00 98/06/07 08/02/06 14:39 12 12 0 TSOFS20. AMS2 01.00 98/06/08 07/11/18 10:32 12 12 0 TSOFS20. AU1 01.00 98/11/19 07/11/19 10:21 7 7 0 TSOFS20. AU2 01.05 98/11/19 07/11/19 11:25 11 7 0 TSOFS20. EREP 01.02 94/05/25 08/06/09 16:22 17 17 0 TSOFS20. EREP1 01.00 94/05/25 08/05/25 15:30 11 11 0 TSOFS20. JOB14. JOB19 01.00 99/09/21 07/09/21 17:18 10 10 0 TSOFS20. JOB21 01.00 97/02/19 08/02/19 20:49 18 18 0 TSOFS20. JOB23. PRINT 01.00 93/11/19 07/11/19 10:35 6 6 0 TSOFS20. REXXCOMP. TESTA**End**


Edit member selection panel

Select using one of threemethods only.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-26. ISPF/PDF editor ES1011.0

Notes:

After having specified a sequential data set or the member of a partitioned data set, ISPF now displays the data set or member contents in the ISPF/PDF editor. You can now add, alter, delete, sort, and so forth, the displayed data.

ISPF displays the name of the data set (and member) you are editing at the top of the screen. In this case it is TSOFS20.TEST.CNTL(AMS). The field titled Columns indicates which part of the data set or member you are editing. The editor allows you to change your view by scrolling up and down as well as left and right. Columns lists the columns you are currently editing.

More scrolling to follow. Let us look at profile first.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> profile Scroll ===> PAGE-------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ***************************** Top of Data **************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* ************************** Bottom of Data **************************


ISPF/PDF editor

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-27. ISPF/PDF profile ES1011.0

Notes:

Each user has at least one edit profile. An edit profile is a set of characteristics that defines the way you can edit a data set. For example, a profile can be set up to edit data that is all in capital letters or to edit data that is in mixed-case letters.

ISPF generates a default edit profile based on the library type of the data set you are editing. Usually, the default profile is suitable for the kind of data you want to put in the data set. Sometimes, however, it is not. To display the edit profile for a data set, type profile on the command line and press Enter.

ISPF now displays the default profile settings in the five =PROF> lines at the top of the screen.

Edit automatically remembers the current setting for each mode in the profile. If you, for example, change from NUMBER OFF to NUMBER ON, you are telling edit to start generating sequence numbers. Edit then automatically remembers that NUMBER mode is on, so the next time that you edit with the same profile, NUMBER mode is on.


ISPF/PDF profileFile Edit Confirm Menu Utilities Compilers Test Help

------------------------------------------------------------------------Command ===> RESET Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(AMS) - 01.04 Columns 00001 00072****** **************************** Top of Data *************************=PROF> ....CNTL (FIXED - 80)....RECOVERY OFF WARN....NUMBER OFF...........=PROF> ....CAPS ON....HEX OFF....NULLS OFF....TABS OFF....................=PROF> ....AUTOSAVE ON....AUTONUM OFF....AUTOLIST OFF....STATS ON.........=PROF> ....PROFILE UNLOCK....IMACRO NONE....PACK OFF....NOTE ON...........=PROF> ....HILITE OFF CURSOR FIND.........................................000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* ************************ Bottom of Data ***************************


Profile

Command => PROFILE (can be used to display profile)Command => RESET (can be used to delete profile lines from display)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

When a new profile is defined, default values are used for the initial mode settings. You can either accept the defaults or change them with edit commands. Once you have changed them, your values are remembered.

Notice that RECOVERY is off. It is recommended you turn it on for each member so that you get both automatic edit RECOVERY and the UNDO function.

Profile lines are deleted from the display when you enter RESET on the command line or by overtyping the =PROF> at the start of each profile line with a d for delete.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-28. Scrolling ES1011.0

Notes:

The editor allows you to change your view by scrolling up and down as well as left and right. Columns lists the columns you are currently editing.

To scroll up and down, use the function keys F7 and F8 or enter up or down with or without a numeric value, indicating the number of lines to scroll. If you do not specify a value or use the function keys to scroll, ISPF scrolls by the amount indicated in the Scroll ===> field. You can change its setting to PAGE, HALF, CSR, MAX, DATA, or to a numeric value. Accordingly, ISPF scrolls by the page, half page, to the current cursor position, to the top/bottom of the data set or member, by a page minus a line, or by number of lines specified, respectively.

Most people prefer CSR. You should try PAGE and HALF.

The settings of MAX, DATA, or a numeric value are not very useful in the scroll field.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> _______ Scroll ===> PAGE--------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ***************************** Top of Data *************************000001 //TSOFA20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1),000004 // NOTIFY=TSOFS20,000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* ************************** Bottom of Data *************************


Press F7 to move UP the data (that is, towards the first record)Press F8 to move DOWN the data (that is, towards the last record)The useful scroll amounts are:

Cursor Page HalfTo change move cursor to scroll area and enter first character of the amount. For example, C or P or H

Scrollamount

Scrolling

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-29. More scrolling ES1011.0

Notes:

The scroll amount can be adjusted for the next move by coding M for MAX, or a numeric value on the command line.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> M Scroll ===> PAGE-------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** *************************** Top of Data **************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* ************************ Bottom of Data **************************


Press F7 to move UP the data (that is, towards the first record)Press F8 to move DOWN the data (that is, towards the last record)Alternatively, override scroll amount for the next action but entering an M (for Maximum) or an number you choose (for example, 8) in the command area.

More scrolling

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-30. Scrolling left and right ES1011.0

Notes:

The scroll amount can be adjusted for the next move by coding M for MAX, or a numeric value on the command line.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGE--------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** *************************** Top of Data ***************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* ************************ Bottom of Data ***************************


Press F10 to move RIGHTPress F11 to move LEFT

Scrolling left and right

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-31. Split screen (1 of 2) ES1011.0

Notes:

Note the position of the cursor.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGE------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ************************** Top of Data **************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390)000010 /******* *********************** Bottom of Data **************************

_


Press F2 to split the screen into TWO screens

Note the cursor position.

Split screen (1 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-32. Split screen (2 of 2) ES1011.0

Notes:

To change the split, position the cursor to the new split line and press F2.

You can change the split position at any time.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGE-----------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** *************************** Top of Data *************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Menu Utilities Compilers Options Status Help

-------------------------------------------------------------------------ISPF Primary Option Menu

Option ===> _0 Settings Terminal and user parameters User ID . : TSOFS201 View Display source data or listings Time. . . : 16:572 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processing Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: TSOFS208 LM Facility Library administrator functions System ID : SYS1F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

Originalscreen

Newscreen

Split screen (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-33. Resplit screen ES1011.0

Notes:

Resplit screen with the divider periods between screens removed.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> _ Scroll ===>PAGE------------------------------------------------------------------------

Menu Utilities Compilers Options Status Help ------------------------------------------------------------------------

ISPF Primary Option MenuOption ===>0 Settings Terminal and user parameters User ID . : TSOFS201 View Display source data or listings Time. . . : 16:572 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processing Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: TSOFS208 LM Facility Library administrator functions System ID : SYS19 IBM Products IBM program development products MVS acct. : 582010 SCLM SW Configuration Library Manager Release . : ISPF 5.811 Workplace ISPF Object/Action Workplace

S SDSF System Display and Search Facility



Resplit screen

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-34. Swap the screen ES1011.0

Notes:

F9 swaps the cursor from one screen to the other.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> _ Scroll ===> PAGE-------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** *************************** Top of Data **************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Menu Utilities Compilers Options Status Help ------------------------------------------------------------------------

ISPF Primary Option MenuOption ===>0 Settings Terminal and user parameters User ID . : TSOFS201 View Display source data or listings Time. . . : 16:572 Edit Create or change source data Terminal. : 32783 Utilities Perform utility functions Screen. . : 14 Foreground Interactive language processing Language. : ENGLISH5 Batch Submit job for language processin Appl ID . : ISR6 Command Enter TSO or Workstation commands TSO logon : LOGON7 Dialog Test Perform dialog testing TSO prefix: TSOFS20F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

Swap the screen

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-35. SWAPBAR system command ES1011.0

Notes:

The SWAPBAR system command is used to enable or disable the display of the point-and-shoot fields for each logical screen on the physical screen.

The point-and-shoot fields are displayed across the line at the bottom of the physical screen.

Display on the physical screen point-and-shoot fields associated with each logical screen for the session.

Use the point-and-shoot field to invoke the associated logical screen:

• User can readily identify each of the logical screens for the session

- No need to display a pop-up (SWAP LIST) to see a list of logical screens.

• Easy to swap logical screens

- Many terminal emulators allow the mouse to be configured to simulate cursor placement and pressing Enter.


SWAPBAR system command• SWAPBAR system command

– The command enables or disables the display of point-and-shoot fields for each logical screen on the physical screen.• Syntax:SWAPBAR [ON|OFF]

ONThe point-and-shoot fields for each logical screen are displayed across the line at the bottom of the physical screen

OFFThe point-and-shoot fields for each logical screen are removed from the physical screen display

– The current logical screen changed by placing the cursor on SWAPBAR field and pressing Enter.

– Each point-and-shoot field can be up to eight characters in length.• Displays screen name or panel name for logical screen.• * (asterisk) in first character indicates current logical screen.• - (dash) In first character indicates the opposite logical screen.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-36. SWAPBAR example (1 of 2) ES1011.0

Notes:

This slide shows using the SWAPBAR system command display the SWAPBAR list.

The current or active logical session is changed by positioning the cursor on the related SWAPBAR point-and-shoot field and pressing Enter.

The SWAPBAR point-and-shoot fields use the same physical attribute as the action bar choices. If the Tab to action bar choices option is selected, then tabbing to SWAPBAR entries is enabled.

The point-and-shoot field for each logical screen can be up to 8 characters in length.

The field will display the screen name if assigned otherwise it displays the name of the current panel for the logical screen.

The entry for the current or active logical session will have an * in the first character position and if the name is 8 bytes long the last character will not be displayed.

The entry for the screen opposite the current logical screen will have a - in the first position and the 8th character will not be displayed.


SWAPBAR example (1 of 2)• Note:

– SWAPBAR list might be longer than the width of the physical screen:• Cursor sensitive

LEFT/RIGHT scrolling enabled

• > (greater than) displayed at the right of the list to indicate RIGHT scrolling possible

• < (less than) displayed at the left of the list to indicate LEFT scrolling possible

SWAPBAR list

Menu Utilities Compilers Options Status Help

ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss ISPF Primary Option Menu

Option ===> swapbar

0 Settings Terminal and user parameters User ID . : PRICHAR 1 View Display source data or listings Time. . . : 14:25 2 Edit Create or change source data Terminal. : 3278A 3 Utilities Perform utility functions Screen. . : 4 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : PDF 6 Command Enter TSO or Workstation commands TSO logon : IKJACCNT 7 Dialog Test Perform dialog testing TSO prefix: 8 LM Facility Library administrator functions System ID : X9 9 IBM Products IBM program development products MVS acct. : V21 10 SCLM SW Configuration Library Manager Release . : ISPF 6.0 11 Workplace ISPF Object/Action Workplace 12 Subsystems DB/DC Subsystems 13 DB2 SWAT SWAT team tools


SWAPBAR command


ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssISPF Primary Option Menu

Option ===>

0 Settings Terminal and user parameters User ID . : PRICHAR 1 View Display source data or listings Time. . . : 14:25 2 Edit Create or change source data Terminal. : 3278A 3 Utilities Perform utility functions Screen. . : 4 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : PDF 6 Command Enter TSO or Workstation commands TSO logon : IKJACCNT 7 Dialog Test Perform dialog testing TSO prefix: 8 LM Facility Library administrator functions System ID : X9 ……

12 Subsystems DB/DC Subsystems 13 DB2 SWAT SWAT team tools


DSLIST ISFPCU41 -ISR@PRI *ISR@PRI

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-37. SWAPBAR example (2 of 2) ES1011.0

Notes:

This slide shows using the SWAPBAR to change the current screen from the ISPF Settings panel to SDSF.


Display Filter View Print Options Help

------------------------------------------------------------------------------HQX7750 ----------------- SDSF PRIMARY OPTION MENU -------------------------COMMAND INPUT ===> SCROLL ===> CSR

DA Active users INIT Initiators I Input queue PR Printers O Output queue PUN Punches H Held output queue RDR Readers ST Status of jobs LINE Lines

NODE Nodes LOG System log SO Spool offload SR System requests SP Spool volumes RES WLM resources ENC Enclaves ULOG User session log PS Processes

END Exit SDSF

DSLIST *ISFPCU4 -ISR@PRI ISR@PRIM


ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssISPF Primary Option Menu

Option ===>

0 Settings Terminal and user parameters User ID . : PRICHAR 1 View Display source data or listings Time. . . : 14:25 2 Edit Create or change source data Terminal. : 3278A 3 Utilities Perform utility functions Screen. . : 4 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : PDF 6 Command Enter TSO or Workstation commands TSO logon : IKJACCNT 7 Dialog Test Perform dialog testing TSO prefix: 8 LM Facility Library administrator functions System ID : X9 ……

12 Subsystems DB/DC Subsystems 13 DB2 SWAT SWAT team tools


DSLIST ISFPCU41 -ISR@PRI *ISR@PRI

SWAPBAR example (2 of 2)

Place cursor on SWAPBAR field for SDSF screen andpress ENTER

SDSF becomes current logical screen

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-38. Save and cancel ES1011.0

Notes:

To save the contents of an altered data set or member enter the Save primary command on the command line and press Enter. ISPF saves the contents of the edited data set or member but remains in Edit mode.

To save the contents of an edited data set or member while quitting the editor, press F3. ISPF saves the changes and displays the previously shown panel.

To quit the ISPF editor without saving any changes since the last save, press F12 or enter cancel or can on the command line and press Enter. ISPF returns to the previous panel.


Save and cancel

• Data set changes are not saved• Returns to previous panel

Type cancel/canor press F12 (if it is set to cancel)

• Saves data set• Returns to previous panel

Press F3

• Saves data set• Remains in edit mode

Type save

ActionCommand

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

FIND characterstring

NEXT | PREV | FIRST | LAST

NEXT Locates and displays the next occurrence of characterstring starting from the current cursor position. NEXT is the default for FIND.

PREV Starts a search for the previous occurrence of characterstring starting at the line preceding the first line being displayed. If the FIND command reaches the top of the data displayed, it wraps around to the bottom.

FIRST Locates and displays the first occurrence of characterstring starting from the top of the data being edited.

LAST Locates the last occurrence of characterstring within the data set or member.

RFIND Repeats the action of the previous FIND command.

N

For additional parameters of the FIND command, refer to ISPF User’s Guide Vol I.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.




Uempty

E

Figure 3-42. BOUNDS and EXCLUDE commands (2 of 2) ES1011.0

Notes:

Use the BOUNDS primary command to specify the range of columns to which other commands such as, FIND, EXCLUDE, CHANGE and so on apply. Columns outside the specified area remain unaffected.

Here are some examples of BOUNDS:

BOUNDS leftcolumn rightcolumn Sets the boundaries for all following editor commands to columns leftcolumn and rightcolumn.

BOUNDS leftcolumn * Sets the left boundary for all following editor commands to column leftcolumn.

BOUNDS Resets the boundaries to their default setting.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGE

EDIT AUES100.OS390.DATA(REQ) - 01.01 4 CHARS 'ACF'****** ***************************** Top of Data ******************************000100 MINIMUM VERSION AND RELEASE REQUIREMENTS FOR IBM PRODUCTS THAT RUN WITH 000110 000120 +---------------------------+-----------+-----------+-----------+-------000130 | PRODUCT AND PRODUCT NUMBER| MVS/ESA | Z/OS | Z/OS | Z/OS000140 | | SP 5.2.2 | V1 R1 | V1 R2 | V1 R3000150 +---------------------------+-----------+-----------+-----------+-------- - - - - - - - - - - - - - - 1 Line(s) not Displayed000170 | PROGRAM (ACF/NCP) | RENTLY | RENTLY | RENTLY | RENTLY000180 | (5668-854, 5668-738, | SUPPORTED | SUPPORTED | SUPPORTED | SUPPOR000190 | 5668-231, AND 5648-063) | RELEASE | RELEASE | RELEASE | RELEAS000191 +---------------------------+-----------+-----------+-----------+-------- - - - - - - - - - - - - - - 1 Line(s) not Displayed000193 | PROGRAM (ACF/SSP) | RENTLY | RENTLY | RENTLY | RENTLY000194 | (5665-338 AND 5665-041) | SUPPORTED | SUPPORTED | SUPPORTED | SUPPOR000195 | | RELEASE | RELEASE | RELEASE | RELEAS000196 +---------------------------+-----------+-----------+-----------+-------- - - - - - - - - - - - - - - 1 Line(s) not Displayed000198 | ACCESS METHOD (ACF/TCAM) | PTFS | PTFS | PTFS | PTFS 000199 | (5735-RC3) | UY51381, | UY51381, | UY51381, | UY5138000200 | | UY99771, | UY99771, | UY99771, | UY9977000201 | | UZ42855, | UZ42855, | UZ42855, | UZ4285000202 | | AND | AND | AND | AND 000203 | | UW16886 | UW16886 | UW16886 | UW1688000204 +---------------------------+-----------+-----------+-----------+-------- - - - - - - - - - - - - - - 1 Line(s) not Displayed000206 | ACCESS METHOD (ACF/TCAM) | PTFS | PTFS | PTFS | PTFS F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

BOUNDS and EXCLUDE commands (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

N

For additional parameters of the BOUNDS command, refer to ISPF Edit and Edit Macros.

The EXCLUDE primary command (or X for short) excludes specific lines of the data set or member being edited from display. Here are some examples of the EXCLUDE command:

EXCLUDE characterstring Excludes the line containing the next occurrence of the specified characterstring starting from the current cursor position.

EXCLUDE characterstring startcolumn endcolumn

Excludes the next line containing an occurrence of the specified characterstring within the columns entered with the command.

EXCLUDE characterstring ALL Excludes all lines containing the specified characterstring from display.

EXCLUDE 'characterstring' Locates and displays the next occurrence of characterstring but allows characterstring to contain blanks, commas, or keywords of the EXCLUDE command, for example, EXCLUDE 'x ALL'.

EXCLUDE “*” column Excludes all lines containing any character in column column from display.

N

For additional parameters of the EXCLUDE command, see ISPF User’s Guide Vol I.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-43. CHANGE command (1 of 2) ES1011.0

Notes:

The CHANGE primary command is used to locate the occurrence of a specified character string within the data set or member you are currently editing and to replace it with another character string.

CHANGE findstring replacestring ALL locates all occurrences of findstring and replaces them with replacestring.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> C TSOFS2X TSOFS20 ALL Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(JOB19) - 01.00 Columns 00001 00072 ****** ***************************** Top of Data ******************************000001 //TSOFS20A JOB TSOFS2X, 000002 // TIME=(,15), 000003 // CLASS=E, 000004 // MSGLEVEL=(1,1), 000005 // NOTIFY=TSOFS2X, 000006 // MSGCLASS=T000007 //STEP1 EXEC PGM=IEBGENER000008 //SYSUT1 DD DSN=TSOFS2X.TEST.EXEC,DISP=SHR000009 //SYSUT2 DD DSN=TSOFS2X.TEST.EXEC1,LIKE=TSOFS2X.TEST.EXEC,000010 // DISP=(NEW,CATLG,CATLG)000011 //SYSIN DD DUMMY000012 //SYSPRINT DD SYSOUT=T****** **************************** Bottom of Data ****************************


CHANGE command (1 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-44. CHANGE command (2 of 2) ES1011.0

Notes:

The CHANGE primary command is used to locate the occurrence of a specified character string within the data set or member you are currently editing and to replace it with another character string. Here are some examples of the CHANGE command:

CHANGE findstring replacestring Locates the next occurrence of findstring and replaces it with replacestring.

CHANGE findstring replacestring ALL Locates all occurrences of findstring and replaces them with replacestring.

CHANGE 'findstring' 'replacestring' Locates the next occurrence of findstring and replaces it with replacestring, but allows findstring and replacestring to contain blanks, commas, or keywords of the CHANGE


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(JOB19) - 01.00 CHARS ‘TSOFS2X' changed****** ***************************** Top of Data ******************************==CHG> //TSOFS20A JOB TSOFS20, 000002 // TIME=(,15), 000003 // CLASS=E, 000004 // MSGLEVEL=(1,1), ==CHG> // NOTIFY=TSOFS20, 000006 // MSGCLASS=T000007 //STEP1 EXEC PGM=IEBGENER==CHG> //SYSUT1 DD DSN=TSOFS20.TEST.EXEC,DISP=SHR==CHG> //SYSUT2 DD DSN=TSOFS20.TEST.EXEC1,LIKE=TSOFS20.TEST.EXEC,000010 // DISP=(NEW,CATLG,CATLG)000011 //SYSIN DD DUMMY000012 //SYSPRINT DD SYSOUT=T****** **************************** Bottom of Data ****************************


CHANGE command (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

command, for example, CHANGE 'ALL' 'ONE'.

CHANGE findstring replacestring leftcolumn rightcolumn

Locates the next occurrence of findstring within the two specified columns and replaces it with replacestring.

CHANGE x'hexfindstring' x'hexreplacestring'

Locates the next occurrence of the hexadecimal hexfindstring and replaces it with the hexadecimal hexreplacestring.

RCHANGE Repeats the action of the previous CHANGE command.

N

For additional parameters of the CHANGE command, refer to ISPF Edit and Edit Macros.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-45. CREATE command (1 of 2) ES1011.0

Notes:

The CREATE macro command creates a member of a partitioned data set from the data you are editing. This command cannot be used to create a sequential data set. CREATE adds a member to a partitioned data set only if a member with the same name does not already exist. Use REPLACE if the member already exists.

CREATE membername creates a new member from the data set you are editing. Use cc in the numeric prefix area of a line to mark the start and the end of the data to be copied into the new member.


Note the CCs

File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> CREATE JOBCARD Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(JOB19) - 01.0 Columns 00001 00072****** *********************** Top of Data*************************CC0001 //TSOFS20A JOB TSOFS20, 000002 // TIME=(,15), 000003 // CLASS=E, 000004 // MSGLEVEL=(1,1), 000005 // NOTIFY=TSOFS20, CC0006 // MSGCLASS=T000007 //STEP1 EXEC PGM=IEBGENER000008 //SYSUT1 DD DSN=TSOFS20.TEST.EXEC,DISP=SHR000009 //SYSUT2 DD DSN=TSOFS20.TEST.EXEC1,LIKE=TSOFS20.TEST.EXEC,000010 // DISP=(NEW,CATLG,CATLG)000011 //SYSIN DD DUMMY000012 //SYSPRINT DD SYSOUT=T****** ********************** Bottom of Data************************

F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=CursorNew member JOBCARD

CREATE command (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-46. CREATE command (2 of 2) ES1011.0

Notes:

The CREATE macro command creates a member of a partitioned data set from the data you are editing. This command cannot be used to create a sequential data set. CREATE adds a member to a partitioned data set only if a member with the same name does not already exist. Use REPLACE if the member already exists.

Enter the command in one of the following forms:

CREATE membername Creates a new member from the data set you are editing. Use cc in the numeric prefix area of a line to mark the start and the end of the data to be copied into the new member.

CREATE membername startline endline Creates a new member from the data set you are editing and copies the data in lines startline to endline into the new data set.


CREATE command (2 of 2)

File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGEEDIT AUES100.TEST.CNTL(JOBCARD) - 01.00 Columns 00001 00072****** *************************** Top of Data *************************000001 //AUES100A JOB AUES100, 000002 // TIME=(,15), 000003 // CLASS=E, 000004 // MSGLEVEL=(1,1), 000005 // NOTIFY=AUES100,000006 // MSGCLASS=T****** *********************** Bottom of Data **************************

F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=C

New memberJOBCARD created

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Note: For additional information on the CREATE command, refer to ISPF Edit and Edit Macros.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-47. COPY command (1 of 2) ES1011.0

Notes:

The COPY command imports records into your edit session at the point you choose. Use A or B to indicate where the imported records are positioned.

The MOVE command does the same as the COPY command, except that MOVE deletes the original data after the records have been imported.

This example imports the whole member, and the member must be in the same PDS. There are options which allow you to import from other sources. Refer to ISPF HELP for details.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> COPY JOBCARD Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(JOB29) - 01.0 Columns 00001 00072****** *********************** Top of Data*************************00b007 //STEP1 EXEC PGM=IEBGENER000008 //SYSUT1 DD DSN=TSOFS20.TEST.EXEC,DISP=SHR000009 //SYSUT2 DD DSN=TSOFS20.TEST.EXEC1,LIKE=TSOFS20.TEST.EXEC,000010 // DISP=(NEW,CATLG,CATLG)000011 //SYSIN DD DUMMY000012 //SYSPRINT DD SYSOUT=T****** ********************** Bottom of Data************************

F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=CursorNew member

JOBCARD

COPY command (1 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-48. COPY command (2 of 2) ES1011.0

Notes:

The COPY command imports the records you choose.

There are options which allow you to select the records to be imported. Use ISPF HELP for details.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(JOB29) - 01.0 member JOBCARD copied****** *********************** Top of Data *************************000001 //TSOFS20A JOB TSOFS20, 000002 // TIME=(,15), 000003 // CLASS=E, 000004 // MSGLEVEL=(1,1), 000005 // NOTIFY=TSOFS20, 000006 // MSGCLASS=T000007 //STEP1 EXEC PGM=IEBGENER000008 //SYSUT1 DD DSN=TSOFS20.TEST.EXEC,DISP=SHR000009 //SYSUT2 DD DSN=TSOFS20.TEST.EXEC1,LIKE=TSOFS20.TEST.EXEC,000010 // DISP=(NEW,CATLG,CATLG)000011 //SYSIN DD DUMMY000012 //SYSPRINT DD SYSOUT=T****** ********************** Bottom of Data ***********************


COPY command (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-49. SORT command (1 of 2) ES1011.0

Notes:

The SORT macro command rearranges records in the sequence you choose, based on the contents of one or more selected fields.

SORT startcolumn endcolumn sequence sorts the records into ascending (A) or descending (D) order as required. The startcolumn and endcolumn parameters specify the part of the record to use as the sort field or fields.


File Edit Confirm Menu Utilities Compilers Test Help

Command ===> SORT 1 2 A Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(PRINT)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************000006 06 XX XX XX XX XX XX XX XX XX 000005 05 XXXXXX XX XX XXXXXXX XX XXXXXX XX XX 000004 04 XXXXXX XX XX XXXXXXX XX XXXXXX XX XX000008 08 XXXXXXX XXXXXX XX XX XX XXXXXXXX XXXXXXX 000001 01 XXXXXXX XXXXXX XXXXXXX XXXXXXXX XXXXXXXX XXXXXXX000003 03 XX XX XX XX XX XX XX XX XX 000002 02 XX XX XX XX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX 000007 07 XX XX XX XX XX XX XX XXXXXXXX XXXXXXXX ****** ************************** Bottom of Data *****************************

_


SORT command (1 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-50. SORT command (2 of 2) ES1011.0

Notes:

Enter the command in one of the following forms:

SORT startcolumn endcolumn sequence Sorts the records into ascending (A) or descending (D) order as required. The start and end columns specify the part of the record to use as the sort field.

SORT major1 major2 seq1 minor1 minor2 seq2 Sorts the records into the order required. The major1 and major2 columns define the major sort field, and the minor1 and minor2 columns define the minor sort field. Up to five sort fields can be specified, with a sequence specified for each.

Note: For additional information on the SORT command, refer to ISPF Edit and Edit Macros.


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> ______ Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(PRINT)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************000001 01 XXXXXXX XXXXXX XXXXXXX XXXXXXXX XXXXXXXX XXXXXXX 000002 02 XX XX XX XX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX000003 03 XX XX XX XX XX XX XX XX XX000004 04 XXXXXX XX XX XXXXXXX XX XXXXXX XX XX000005 05 XXXXXX XX XX XXXXXXX XX XXXXXX XX XX000006 06 XX XX XX XX XX XX XX XX XX000007 07 XX XX XX XX XX XX XX XXXXXXXX XXXXXXXX000008 08 XXXXXXX XXXXXX XX XX XX XXXXXXXX XXXXXXX****** ************************** Bottom of Data *****************************

_


SORT command (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-51. Additional primary commands ES1011.0

Notes:

Locate The LOCATE primary command allows you to scroll up or down to a specified line, which is then displayed as the first line.

Reset The RESET primary command can restore line numbers in the line command area when those line numbers have been replaced by labels pending line commands, error flags, and change flags. RESET can also delete special lines from the display, redisplay excluded lines, and temporarily disable the highlighting of FIND strings.

Submit The SUBMIT primary command submits the member or data set you are editing or a part of the member or data set as a batch job.

Renum RENUM activates the number mode and renumbers all lines, usually in increments of 100.


Additional primary commands• Locate: Displays a particular line in the data.• Reset: Resets the editor display.• Submit: Submits the edited data as a job stream for background

execution.• Renum: Switches NUMBER mode on and renumbers the data.• Unnum: Switches NUMBER mode off and blanks out sequence

numbers.• Move: Moves a member or data set into this edit session.• Edit: Causes a recursive entry into edit.• Undo: Undoes the changes of the last command.• Recovery: Enables undo and automatically backs up ever time you

press Enter. Highly recommended.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Unnum The UNNUM primary command sets all sequence fields to blanks, turns off number mode, and positions the data so that column 1 is the first column displayed.

Move MOVE specifies a member of the partitioned data set being edited to be moved into the data being edited.

Edit The EDIT primary command allows you to edit another sequential data set or partitioned data set member during your current edit session.

Undo If you enter an edit primary, line or macro command, or type over existing data by mistake, you can restore your data with the UNDO primary command. To use the UNDO command, you must have either RECOVERY ON or SETUNDO ON.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-52. More primary commands ES1011.0

Notes:

COLS The COLS line differs from that displayed by the COLS line command in that the line command field is protected. This means that it can not be moved, copied, or deleted with line commands. This line does not scroll with the data.

Hide x The Hide primary command removes each n Line(s) not displayed message from the display where lines have been hidden from display by the EXCLUDE command. Instead, the line-number field of the preceding line is underscored (if the terminal supports underscoring) to indicate that part of the data is not being displayed.

RESet Hide The Hide operand of the RESet command redisplays n Line(s) not displayed messages that were previously excluded through the Hide command.


More primary commands•COLS: Displays a protected non-scrollable line on

the EDIT screen.

•Hide: Removes each n Lines(s) not displayed message from the screen.

•RESet Hide: Redisplays all n Line(s) not displayed messages on the screen.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Edit a data set using the ISPF/PDF editor

– Display and modify the edit profile, control scrolling, and manage multiple screens,


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Use ISPF primary commands.

• BOUNDS, FIND, CHANGE• Execute a REXX program

3. Log off.

ExerciseISPF editor primary commands

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3.3. Editing data sets: Line commands

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-55. Editing data sets: Line commands ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Use ISPF/PDF line commands in the prefix area

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-57. Editing data sets: The ISPF/PDF editor line commands ES1011.0

Notes:

Apart from the command line, the ISPF editor features another area to be used for command entry, the prefix area. The prefix area is the six-digit field at the beginning of each line. It is used to process so-called line commands. To enter a line command, overtype the sequence number at the beginning of a line. The following pages discuss the various line commands and their effects in more detail.

While some line commands apply to a single line only, other line commands apply to a block of lines. Usually, when the action code of a command, for example, c, d, r, and so forth, is entered twice, for example, cc, dd, or rr, it marks the beginning of the block of lines to which the command applies. The end of the block is indicated by a repetition of the same action code. If only a single-character action code is entered, then the command affects only the line on which it was entered.


Pre

fix

area

File Edit Confirm Menu Utilities Compilers Test Help ------------------------------------------------------------------------------Command ===> Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(MEMBER)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T 000006 //STEP1 EXEC PGM=IDCAMS 000007 //SYSPRINT DD SYSOUT=T 000008 //SYSIN DD * 000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390) 000010 /* ****** ************************** Bottom of Data *****************************


Prefix area

Editing data sets: The ISPF/PDF editor line commands

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-58. Prefix area commands: Copy, move, and repeat a single line ES1011.0

Notes:

The line commands c and m mark a single line for copy or move, respectively. The target line for the copy or move operation has to be identified by:

a The copied line is inserted after this line.

b The copied line is inserted before this line.

o The copied line overlays this line. All blank positions of the target line are overlaid with the data of the source line. All non-blank positions remain unchanged. See the next visual.

The line command r repeats a single line, that is, it inserts a line directly after the repeated line and copies the contents of the repeated line into it.


Prefix area commands:Copy, move, and repeat a single line

Copy line:

Move line:

Repeat line:

0c0007 AAAA00a008 BBBB000009 CCCC000010 DDDD

000007 AAAA0m0008 BBBB000009 CCCC0b0010 DDDD

000007 AAAA 000r08 BBBB000009 CCCC000010 DDDD

Copies line 000007after line 000008

Moves line 000008before line 000010

Repeats line 000008once

000007 AAAA000008 BBBB000009 AAAA000010 CCCC000011 DDDD

000007 AAAA000008 CCCC000009 BBBB000010 DDDD

000007 AAAA 000008 BBBB000009 BBBB000010 CCCC000011 DDDD

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-59. Prefix area commands: Copy and move over ES1011.0

Notes:

The line commands c and m mark a single line for copy or move, respectively. The target line for the copy or move operation has to be identified by:

o The copied line overlays this line. All blank positions of the target line are overlaid with the data of the source line. All non-blank positions remain unchanged.


Copy line:

Move line:

0c0007 123456

00o008 B B B

000009 CCCCCC

000010 DDDDDD

Copies line 000007

over line 000008000007 123456

000008 B2B4B6

000009 CCCCCC

000010 DDDDDD

0m0007 123456

00o008 B B B

000009 CCCCCC

000010 DDDDDD

Copies line 000007

over previous line 000008000007 B2B4B6

000008 CCCCCC

000009 DDDDDD

Prefix area commands: Copy and move over

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-60. Prefix area commands: Copy, move, and repeat multiple lines ES1011.0

Notes:

To copy, move or repeat entire blocks of lines, use the cc, mm, and rr line commands. Enter the appropriate line command twice, that is, on the first and the last line of the block of lines that you want to copy, move, or repeat. As with the line commands discussed on the previous visual, the target for the copy or move operation is specified by a, b or o.

N

When specifying an overlay, oo has to be entered on the first and last line of the block that is to be overlaid.

Repeated lines are always inserted right after their source lines. To repeat a line or block of lines multiple times, specify r or rr...rr and an integer value, as shown on the example in this visual.


Prefix area commands: Copy, move, and repeat multiple lines

Copy lines:

Move lines:

Repeats lines:

0cc007 AAAA0cc008 BBBB000009 CCCC0000a0 DDDD

000007 AAAA0b0008 BBBB000mm9 CCCC0000mm DDDD

0rr207 AAAA 0rr008 BBBB000009 CCCC000010 DDDD

000007 AAAA000008 BBBB000009 CCCC000010 DDDD000011 AAAA000012 BBBB

000007 AAAA000008 CCCC000009 DDDD000010 BBBB

000007 AAAA 000008 BBBB000009 AAAA000010 BBBB000011 AAAA000012 BBBB000013 CCCC000014 DDDD

Copies lines 000007 and

000008 after line 000010

Moves lines 000009 and 000010 before line 000008

Repeats lines 000007

and 000008 twice

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-61. Prefix area commands: Insert or delete a single line ES1011.0

Notes:

To add or delete a line, use the i (insert) and d (delete) ISPF editor line commands. The line command i inserts a line after the line in which it was specified, and d deletes the line on which it is entered.


Prefix area commands: Insert or delete a single line

Insert line:

Delete line:

0i0007 AAAA

000008 BBBB

000009 CCCC

000010 DDDD

000007 AAAA

0d0008 BBBB

000009 CCCC

000010 DDDD

000011 EEEE

Inserts a single lineafter line 000007

Deletes line 000008

000007 AAAA

......

000008 BBBB

000009 CCCC

000010 DDDD

000007 AAAA

000008 CCCC

000009 DDDD

000010 EEEE

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-62. Prefix area commands: Insert or delete multiple lines ES1011.0

Notes:

To add more than a single line to the data set or member you are editing, enter i and an integer value in its prefix area. The line command i tells the ISPF editor to insert lines and the integer value how many.

To delete a block of lines either enclose them by dds, that is, enter dd in the first and last lines of the block to be deleted, or enter dd and an integer value in the first line of the block. The number specified in conjunction with the dd line command reflects the number of lines to be deleted. If this value is greater than the number of lines remaining in the data set or member, ISPF deletes all lines up to the end of the data set or member and ignores the rest.


Prefix area commands: Insert or delete multiple lines

Insert lines:

Delete line:

0i3007 AAAA

000008 BBBB

000009 CCCC

000010 DDDD

0dd007 AAAA

000008 BBBB

0dd009 CCCC

000010 DDDD

000011 EEEE

000012 FFFF

000013 GGGG

Inserts three lines afterline 000007

Deletes lines 000007through 000009

000007 AAAA

......

......

......

000008 BBBB

000009 CCCC

000010 DDDD

000007 DDDD

000008 EEEE

000009 FFFF

000010 GGGG

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-63. COLS command ES1011.0

Notes:

The COLS line command is used to display a column identification line. This column identification line contains a numeration of all columns within the edited data set or member. Displaying the column identification line can be very useful when setting tabs and boundaries.

To remove the Cols line from display, enter reset on the command line or delete the =COLS> line using the d line command.

Additional information about Flagged Lines

Flagged lines are lines that contain highlighted flags in the line command area. They can be divided into the following categories:

• Changed lines

• Error lines

• Special lines


File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> _ Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(AMS2) - 01.00 Columns 00001 00072****** ***************************** Top of Data *****************************cols //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *000009 DELETE TSOFS20.RRDS PURGE

File Edit Confirm Menu Utilities Compilers Test HelpCommand ===> Scroll ===> PAGEEDIT TSOFS20.TEST.CNTL(AMS2) - 01.00 Columns 00001****** ***************************** Top of Data ************************=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+-000001 //AUES100A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=T000008 //SYSIN DD *

COLS command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

=CHG> Shows lines that were changed by a CHANGE or RCHANGE command.

=ERR> Shows lines in which PDF finds an error when you enter a line, primary, or macro command. For example, when you enter a CHANGE command and there is not enough room on the line to make the change.

Special Lines Special lines can be divided into two categories:

• Edit profile lines (values are stored in your edit profile)

=PROF> Contains the settings of the individual edit modes. This line is not saved as part of your data set or member.

=TABS> Defines tab positions. This line is not saved as part of your data set or member.

=MASK> Can contain data to be inserted into your data set or member when you use the I (insert) line command. This line is not saved as part of your data set or member.

=BNDS> Specifies left and right boundaries that are used by other commands. This line is not saved as part of your data set or member.

=COLS> Identifies the columns in a line. The column identification line can be saved as part of the data set or member if you use the md (make dataline) line command to convert it to a data line.

• Message, note, and information lines:

=MSG> Message lines inform you of changes to the edit profile. These changes are caused by inconsistencies between the data to be edited and the edit profile settings. Message lines are not saved as part of your data set or member unless you use the md (make dataline) line command to convert them to data lines.

=NOTE= Note lines display information when you insert edit models. However, these lines do not appear if the edit profile is set to NOTE OFF. Note lines are not saved as part of the data set or member unless you use the md (make dataline) line command to convert them to data lines.

====== Temporary information lines are lines you can add to provide temporary information that is not saved with the data. Information lines are not saved a part of the data set or member unless you use the md (make dataline) line command to convert them to data lines.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-64. Cut and paste (1 of 2) ES1011.0

Notes:

CUT and PASTE are used to copy lines from one member or data set to another.

The lines to be copied are marked with a cc copy block, and then cut is entered on the command line. Then switch to the member or data set and enter an a or b where you want the lines to go. Type paste on the command line and press Enter.

This visual shows the cut.


File Edit Confirm Menu Utilities Compilers Test Help Command ===> _cut Scroll ===> PAGE------------------------------------------------------------------------------EDIT AUES100.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************00cc01 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000cc5 // MSGCLASS=T 000006 //STEP1 EXEC PGM=IDCAMS 000007 //SYSPRINT DD SYSOUT=T 000008 //SYSIN DD * F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .File Edit Confirm Menu Utilities Compilers Test Help

Command ===> _ Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS1)- 01.01 Columns 00001 00072****** ***************************** Top of Data *****************************000001 //STEP1 EXEC PGM=IDCAMS 000002 //SYSPRINT DD SYSOUT=T 000003 //SYSIN DD * 000004 LISTDATA STATUS VOLUME(USER11) UNIT(3390) 000005 /* ****** ***************************Bottom of Data *****************************


Cut and paste (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-65. Cut and paste (2 of 2) ES1011.0

Notes:

Enter an a or b where you want the lines to go. Type paste on the command line and press Enter.


File Edit Confirm Menu Utilities Compilers Test Help Command ===> Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T 000006 //STEP1 EXEC PGM=IDCAMS 000007 //SYSPRINT DD SYSOUT=T 000008 //SYSIN DD * F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor


Command ===> paste Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS1)- 01.01 Columns 00001 00072****** ***************************** Top of Data *****************************000b01 //STEP1 EXEC PGM=IDCAMS 000002 //SYSPRINT DD SYSOUT=T 000003 //SYSIN DD * 000004 LISTDATA STATUS VOLUME(USER11) UNIT(3390) 000005 /* ****** ***************************Bottom of Data *****************************


Cut and paste (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-66. Cut and pasted result ES1011.0

Notes:


File Edit Confirm Menu Utilities Compilers Test Help Command ===> __________ Scroll ===> PAGE------------------------------------------------------------------------------EDIT T0.TEST.CNTL(AMS)- 01.04 Columns 00001 00072****** ***************************** Top of Data *****************************000001 //TSOFS20A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T 000006 //STEP1 EXEC PGM=IDCAMS 000007 //SYSPRINT DD SYSOUT=T 000008 //SYSIN DD * F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor


Command ===> __________ Scroll ===> PAGE------------------------------------------------------------------------------EDIT TSOFS20.TEST.CNTL(AMS1)- 01.01 Columns 00001 00072****** ***************************** Top of Data *****************************000001 //T0A JOB TSOFS20, 000002 // CLASS=E, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=T 000006 //STEP1 EXEC PGM=IDCAMS 000007 //SYSPRINT DD SYSOUT=T 000008 //SYSIN DD * 000009 LISTDATA STATUS VOLUME(USER11) UNIT(3390) F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor

Cut and pasted result

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-67. Additional line commands ES1011.0

Notes:

()<> Use ) or )) to shift columns right on one or more lines. ) identifies a line on which columns are to be shifted right by 2. )n specifies that the columns of this line are to be shifted right by n positions.

Use )) to mark the first and the last line of a block that is to be shifted right by 2. If you want the columns to be shifted by a value other than 2, enter ))n, where n is the number of positions.

Use ( or (( to shift columns left on one or more lines. The same rules as for ) and )) apply. Line commands >, >>, <, and << work in a similar manner as ), )), (, and (( but does not shift data beyond boundaries or truncate data when shifting it.

x The x (exclude) line command excludes one or more lines of data from display. You can exclude multiple lines from display by specifying x in conjunction with an integer value or by entering xx on the first and last line of the block to be excluded.


Additional line commands• copy: Copies lines from another member or data set.• move: Moves lines from another member or data set.• () <> : Shifts the characters in a line to the left or right.• x: Excludes a line from display.• s: Redisplays an excluded line.• fn: Redisplays the first(n) excluded line(s).• ln: Redisplays the last(n) excluded line(s).• ts: Splits a line at the current cursor position.• tf: Moves the data of the next line to the current line.• lc: Converts the characters of the specified line to lowercase.• uc: Converts the characters of the specified line to uppercase.• mask: Defines a model line to be applied to all inserted lines.• tabs: Allows the definition of software tabs for data entry.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

s The s (show line) line command causes one or more lines in a block of excluded lines to be redisplayed. If you want to redisplay more than one line, type a number greater than 1 after the s command.

ts ts (text split) lets you split a line at a specified position. To do so, enter ts in the line's prefix area, move the cursor to the position where the split is to occur, and press Enter.

tf tf (text flow) reformats the lines of a paragraph. Remaining space on the first line is filled with data from the second line. The second line is then filled with data from the third line, and so on.

lc Use the lc line command to convert single or multiple lines into lowercase characters. To convert a single line, enter lc, to convert multiple lines, enter lc and the number of lines to be converted, or mark the first and last of a block of lines with either lcc or lclc.

uc The uc command is the reverse of the lc command and converts lowercase characters to uppercase. The same rules apply.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Use ISPF/PDF line commands in the prefix area

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Tasks:1. Log on to TSO.2. Use Edit Primary and

line commands.3. Log off.

Exercise

ISPF editor line command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3.4. Copying, moving, renaming, deleting data sets and data set members

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-70. Copying, moving, renaming, deleting data sets and data set members ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Copy or move an entire data set or selected members • Rename a data set or member • Delete an entire data set or a single member

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-72. Copying and moving data sets ES1011.0

Notes:

To copy or move an entire data set, sequential or partitioned, select option 3.3 from the ISPF Primary Option Menu. On the Move/Copy Utility panel, type c for copy or m for move as your selection on the command line. Enter the name of the source data set, that is, the name of the data set to be copied or moved. If the source data set is partitioned and you want to copy or move all members, enter an asterisk (*) in the Member field. If your entries are correct, press Enter to proceed.


Copying and moving data sets

Menu RefList Utilities Help----------------------------------------------------------------------------

Move/Copy UtilityOption ===> c or mC Copy data set or member(s) CP Copy and printM Move data set or member(s) MP Move and printL Copy and LMF lock member(s) LP Copy, LMF lock, and printP LMF Promote data set or member(s) PP LMF Promote and print

Specify "From" Data Set below, then press Enter key

From ISPF Library:Project . . . TSOFS200 (--- Options C, CP, L, and LP only ----)

Group . . . . SAMPLE . . . . . . . . .

Type . . . . DATAMember . . . * (Blank or pattern for member list,

"*" for all members)

From Other Partitioned or Sequential Data Set:Data Set Name . . . Volume Serial . . . (If not cataloged)



Move/Copy Utility: Specifying the from data set

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-73. Move/copy utility: Specifying the “to” data set ES1011.0

Notes:

After having entered the source data set of the copy/move operation on the previous panel, ISPF now displays the panel for the specification of the target data set. Enter the name of the target data set. Select Replace like-named members if you are copying or moving a partitioned data set and want already existing members of the target data set to be overlaid by those of the source data set in case their names match.

To perform the copy/move operation, press Enter.


Move/copy utility: Specifying the “to” data set

Menu RefList Utilities Help----------------------------------------------------------------------------COPY From AUES100.SAMPLE.DATACommand ===>Specify "To" Data Set Below

To ISPF Library:Project . . TSOFS20 Replace option:

Group . . . TEST Enter "/" to select option

Type . . . . SAMPLE Replace like-named members

To Other Partitioned or Sequential Data Set:Data Set Name . . . Volume Serial . . . (If not cataloged)


To Data Set Options:Sequential Disposition Pack Option SCLM Setting1 1. Mod 3 1. Yes 3 1. SCLM

2. Old 2. No 2. Non-SCLM3. Default 3. As is


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-74. Copy/move complete ES1011.0

Notes:

ISPF now copies the data set or member as specified to their new destination. In case of a move, ISPF deletes the source after a successful copy operation. The completion of the copy/move is indicated by a message. It should read Data set copied or Data set moved.


Menu RefList Utilities Help------------------------------------------------------------------------------

Move/Copy Utility Data set copiedOption ===> CC Copy data set or member(s) CP Copy and printM Move data set or member(s) MP Move and printL Copy and LMF lock member(s) LP Copy, LMF lock, and printP LMF Promote data set or member(s) PP LMF Promote and print


From ISPF Library:Project . . . TSOFS20 (--- Options C, CP, L, and LP only ----)Group . . . . SAMPLE . . . . . . . . . Type . . . . DATAMember . . . (Blank or pattern for member list,





Copy/move complete

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-75. Copy/move member: Specifying the “from” data set ES1011.0

Notes:

To copy or move one or more members of a partitioned data set, enter the name of the source data set as well as the proper panel selection on the Move/Copy Utility panel. You might want to specify a pattern in the Member field to narrow down the list of eligible members, or, in case of a single member, specify its name. If you enter a pattern, ISPF displays a member list of all members meeting the selection criteria. Without pattern, ISPF lists all members. If you enter a member name, ISPF omits the member list.


Copy/move member: Specifying the “from” data set


Move/Copy UtilityOption ===>C Copy data set or member(s) CP Copy and printM Move data set or member(s) MP Move and printL Copy and LMF lock member(s) LP Copy, LMF lock, and printP LMF Promote data set or member(s) PP LMF Promote and print


From ISPF Library:Project . . . TSOFS20 (--- Options C, CP, L, and LP only ----)Group . . . . TEST . . . . . . . . . Type . . . . CNTLMember . . . A* (Blank or pattern for member list,





xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-76. Copy/move member: Specifying the “to” data set ES1011.0

Notes:

After having entered the source data set of the copy/move operation on the previous panel, ISPF now displays the panel for the specification of the target data set.

Enter the name of the target data set. Select Replace like-named members if you want to overlay existing members through the ones to be copied.


Copy/move member: Specifying the “to” data setMenu RefList Utilities Help

---------------------------------------------------------------------------COPY From AUES100.TEST.CNTLCommand ===>Specify "To" Data Set Below

To ISPF Library:Project . . TSOFS20 Replace option:

Group . . . TEST Enter "/" to select option

Type . . . . DATA Replace like-named members

To Other Partitioned or Sequential Data Set:Data Set Name . . . Volume Serial . . . (If not cataloged)


To Data Set Options:Sequential Disposition Pack Option SCLM Setting1 1. Mod 3 1. Yes 3 1. SCLM

2. Old 2. No 2. Non-SCLM3. Default 3. As is


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-77. Member selection panel ES1011.0

Notes:

In case of a missing member name or a pattern specification, ISPF displays a member list as shown above.

To select a member for the copy/move operation, enter an s in its prefix area.

To browse the contents of a member prior to making any selection, use the b line command.

To select a member for the copy/move and rename it in the target data set, select this member, and enter the new member name in the Prompt field after its current name.

Press Enter to continue.


Menu Functions Utilities HelpCommand ===> Scroll ===> PAGECOPY TSOFS20.TEST.CNTL TO TSOFS20.TEST.DATA Row 00001 of 00005

Name VV MM Created Changed Size Init Mod ID. AMS 01.03 98/06/07 08/05/17 18:23 10 10 0 TSOFS20

s AMS1 01.00 98/06/07 08/02/06 14:39 12 12 0 TSOFS20

s AMS2 01.00 98/06/08 07/11/18 10:32 12 12 0 TSOFS20

s AU1 01.00 98/11/19 07/11/19 10:21 7 7 0 TSOFS20

s AU2 01.05 98/11/19 07/11/19 11:25 11 7 0 TSOFS20**End**


Member selection panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-78. Copy/move complete ES1011.0

Notes:

After a successful copy/move, ISPF displays a *COPIED, *MOVED, or *REPL next to each member.

*COPIED - The member was copied or copied/locked successfully

*MOVED - The member was moved successfully

*REPL - The member was replaced in the output library (Moved or Copied)

In any other case, ISPF displays an error message.


Menu Functions Utilities HelpCommand ===> Scroll ===> PAGECOPY AUES100.TEST.CNTL TO AUES100.TEST.DATA Row 00001 of 00005

Name VV MM Created Changed Size Init Mod ID. AMS 01.03 98/06/07 08/05/17 18:23 10 10 0 TSOFS20

s AMS1 COPIED 01.00 98/06/07 08/02/06 14:39 12 12 0 TSOFS20

s AMS2 NO-REPL 01.00 98/06/08 07/11/18 10:32 12 12 0 TSOFS20

s AU1 COPIED 01.00 98/11/19 07/11/19 10:21 7 7 0 TSOFS20

s AU2 COPIED 01.05 98/11/19 07/11/19 11:25 11 7 0 TSOFS20**End**


Copy/move complete

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-79. Renaming a data set or member ES1011.0

Notes:

To rename a data set, select ISPF/PDF option 3.2, the Data Set Utility panel. Enter the old data set name and specify r as your selection on the command line. To enter the new data set name, press Enter.


Renaming a data set or member

Menu RefList Utilities Help------------------------------------------------------------------------------

Data Set Utility Option ===> r

A Allocate new data set C Catalog data set R Rename entire data set U Uncatalog data setD Delete entire data set S Data set information (short)

blank Data set information M Enhanced data set allocation V VSAM Utilities

ISPF Library:

Project . . TSOFS20Group . . . TESTType . . . . CNTL




Data Set Utility panel: Specifying the old data set name

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-80. Data Set Utility panel: Specifying the new data set name ES1011.0

Notes:

To complete the information needed for a data set rename, ISPF/PDF now prompts you for the new data set name, that is, the name under which it will be cataloged after the change. Fill in the required information and confirm it by pressing Enter.


Data Set Utility panel: Specifying the new data set name

Menu RefList Utilities Help- Rename Data Set

OData Set Name: AUES100.TEST.CNTLVolume . . . : USER11

b Enter new name below: (The data set will be recataloged.)

ISPF Library:I Project. . . TSOFS20

Group. . . . TESTType . . . . NEWCNTL

Other Partitioned or Sequential Data Set:O Data Set Name . . .

D

Command ===>F1=Help F3=Exit F12=Cancel


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-81. Data Set Utility panel: Successful data set rename ES1011.0

Notes:

After ISPF/PDF has performed the data set rename, it will notify you in any case of its outcome by issuing a message on the Data Set Utility panel. In case of a successful rename of the data set, the message Data set renamed is issued.


Data Set Utility panel: Successful data set rename


Data Set Utility Data set renamedOption ===>


blank Data set information M Enhanced data set allocationV VSAM Utilities

ISPF Library:Project . . TSOFS20Group . . . TESTType . . . . CNTL



F1=Help F2=Split F3=Exit F4= F5=RFind F6=RChangeF7=Up F8=Down F9=Swap F10=Right F11=Left F12=Cursor1

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-82. Library Utility panel: Specifying the old member name ES1011.0

Notes:

To rename a single member rather than an entire data set, select ISPF/PDF option 3.1, the Library Utility panel. Specify the name of the data set containing the member to be renamed as well as the current member name and the new member name. Enter the selection r on the command line, and proceed with the member rename operation by pressing Enter.


Library Utility panel:Specifying the old member name


Library UtilityOption ===> rblank Display member list E Edit member

C Compress data set V View memberX Print index listing B Browse memberL Print entire data set D Delete memberI Data set information R Rename memberS Short data set information P Print member

ISPF Library:Project . . . TSOFS20Group . . . . TEST . . . . . . . . .

Type . . . . NEWCNTLMember . . . TESTA (If B, D, E, P, R, V, or blank selected)

New name . . TESTB (If R selected)

Other Partitioned or Sequential Data Set:Data Set Name . . . Volume Serial . . . (If not cataloged)

Enter "/" to select optionData Set Password . . / Confirm Member Delete


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-83. Rename member complete ES1011.0

Notes:

After the member rename operation has been performed, ISPF/PDF issues a message, which case should read Member member_name Renamed.



Library Utility Member TESTA RenamedOption ===>blank Display member list E Edit member


ISPF Library:

Project . . . TSOFS20Group . . . . TEST . . . . . . . . .

Type . . . . NEWCNTLMember . . . (If B, D, E, P, R, V, or blank selected)New name . . (If R selected)




Rename member complete

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-84. Deleting a data set or member ES1011.0

Notes:

To delete an entire data set, choose the Data Set Utility panel, that is, ISPF/PDF option 3.2, and enter the name of the data set to be deleted as well as the command line selection d. Before the data set is now actually deleted, ISPF/PDF will prompt you for your delete confirmation.


Deleting a data set or member


Data Set Utility

Option ===> dA Allocate new data set C Catalog data setR Rename entire data set U Uncatalog data setD Delete entire data set S Data set information (short)


ISPF Library:

Project . . TSOFS20Group . . . SAMPLEType . . . . DATA




Data Set Utility panel: Specifying the data set to be deleted

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-85. Confirm Delete pop-up window ES1011.0

Notes:

You are now prompted to confirm the data set delete. Since data set deletion is an irrevocable process, ISPF requires you to confirm that you really want the data set deleted. If you want to delete the data set, press the Enter key. If you made a mistake and do not want to delete the data set, enter the END command.

If the data set you are deleting has an expiration date that has not expired, you will also be shown the Confirm Purge panel. If you want to delete the data set, enter a forward slash (/) in the PURGE DATA SET field. If you made a mistake and do not want to delete the data set, press Enter or enter the END command.

N

You cannot delete VSAM data sets nor password protected data sets with this utility.



- Confirm Delete ------

OData Set Name. : TSOFS20.SAMPLE.DATA Volume . . . . : USER07 Creation Date. : 2000/03/19 t)

b on

Instructions: I

Press ENTER key to confirm the delete request. (The data set will be deleted and uncataloged.)

Press CANCEL or EXIT to cancel the delete request. O

"C")

D

Command ===> F1=Help F2=Split F3=Exit F9=Swap F12=Cancel


Confirm Delete pop-up window

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-86. Data set deleted message ES1011.0

Notes:

If you confirmed the data set deletion request, the message issued by ISPF/PDF should be Data set deleted. If you did not confirm the delete, it should read Data set not deleted. Any other message indicates an error.



Data Set Utility Data set deletedOption ===>



ISPF Library:

Project . . TS0FS20Group . . . SAMPLEType . . . . DATA




Data set deleted message

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-87. Library Utility panel: Specifying the member to be deleted ES1011.0

Notes:

To delete only selected members of a data set, choose the Library Utility panel, ISPF/PDF option 3.1. Enter the name of the data set containing the member to be deleted and the member name and specify d for delete on the command line. Press Enter.


Library Utility panel:Specifying the member to be deleted


Library UtilityOption ===> dblank Display member list E Edit member


ISPF Library:Project . . . TSOFS20Group . . . . TEST . . . . . . . . .

Type . . . . NEWCNTLMember . . . TESTA (If B, D, E, P, R, V, or blank selected)New name . . (If R selected)




xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-88. Confirm Member Delete pop-up window ES1011.0

Notes:

Depending on your settings, ISPF/PDF now either performs the member delete or prompts you to confirm the member delete. If your settings contain Set member delete confirmation off, ISPF/PDF does not prompt you for your confirmation. If your settings do not contain Set member delete confirmation off, ISPF/PDF prompts you for your confirmation by displaying the Confirm Member Delete window as shown above.

To confirm the delete, press Enter. To cancel the delete, press either CANCEL or EXIT. You might also want to change the setting for the confirmation prompting in case of a member delete. This change does not apply until the next member delete request.


Menu RefList Utilities HelpISPF Utilities

Confirm Member DeleteO

Data Set Name:b TSOFS20.TEST.NEWCNTL

Member to be Deleted:TESTA

Set member delete confirmation off

I Press ENTER to confirm delete. Press CANCEL or EXIT to cancel delete.

elected)New name . . (If R selected)




Confirm Member Delete pop-up window

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-89. Member deleted message ES1011.0

Notes:

In case of a successful member deletion, ISPF/PDF now issues the Member member_name Deleted message.



Library Utility Member TESTA DeletedOption ===>blank Display member list E Edit member


ISPF Library:Project . . . TSOFS20_Group . . . . TEST . . . . . . . . .

Type . . . . NEWCNTLMember . . . (If B, D, E, P, R, V, or blank selected)New name . . (If R selected)




Member deleted message

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Copy or move an entire data set or selected members • Rename a data set or member • Delete an entire data set or a single member

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Allocate new data sets.3. Create, change, and

delete members.4. Copy, rename, and

delete data sets.5. Log off.

Exercise

Copy/move/rename/delete data sets and members

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

3.5. Working with data set lists

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-92. Working with data set lists ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Work with data set lists (ISPF/PDF option 3.4)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-94. Working with data set lists ES1011.0

Notes:

One way to display a data set list is to use ISPF/PDF option 3.4, which displays the Data Set List Utility panel. A list can be created by either specifying a data set name level, that is, one or more qualifiers, by specifying a volume serial or a combination of both data set name level and volume serial. Do not enter any selection on the command line. In the example in this visual, a data set name level of TSOFS20 is entered. The result is a list of all catalog entries that contain TSOFS20 as their first qualifier, as displayed on the following visual. You might want to use *, **, or % to narrow down your search results. * acts a placeholder for at least one qualifier, ** stands for zero or more qualifiers, and % stands for a single character within a data set name. When no Volume serial is specified, the list is created through a catalog search, otherwise through a search of the VTOC. The Initial view field specifies which view of the data set list information you would like to be displayed first with the data set list. Alternate views are available using the LEFT and RIGHT scroll commands, and the View action bar choice. The Confirm Data Set Delete and Confirm Member Delete options let you choose whether you want to be prompted for your confirmation if a data set or member delete request is issued.


Menu RefList RefMode Utilities Help

Data Set List UtilityOption ===>

blank Display data set list P Print data set listV Display VTOC information PV Print VTOC information

Enter one or both of the parameters below:

Dsname Level . . . TSOFS20Volume serial . .

Data set list optionsInitial View . . . 1 1. Volume Enter "/" to select option

2. Space / Confirm Data Set Delete3. Attrib / Confirm Member Delete4. Total

The following actions will be available when the list is displayed:Enter a "/" on the data set list command field for command prompt pop-up.Enter TSO commands, CLIST, REXX execs, or "=" to execute previous command.


Working with data set listsData Set List Utility panel

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-95. DSLIST display panel ES1011.0

Notes:

You now see a typical data set list as created with ISPF/PDF option 3.4. If the list exceeds the displayable area, you can use the UP and DOWN commands to scroll through the list. You can also use the LEFT and RIGHT commands to perform a horizontal scroll, which displays other data set characteristics, such as device type, data set organization, record size, expiration date, and so on.

To work with data sets from the list, enter one of the following line commands in the Command field that precedes the data set name.

This list is not comprehensive. See the ISPF literature for a complete listing.

b Browse data set e Edit data set v View data set r Rename data set d Delete data set c Catalog data set co Copy data set


Menu Options View Utilities Compilers HelpDSLIST - Data Sets Matching TSOFS20 Row 1 of 12Command ===> Scroll ===> PAGECommand - Enter "/" to select action Message Volume-------------------------------------------------------------------------------

TSOFS20 *ALIASTSOFS20.BRODCAST USER06TSOFS20.ISPF.PROFILE USER02TSOFS20.OS390.REQS USER04 TSOFS20.SPFLOG1.LIST USER05TSOFS20.TEST.DATA USER05TSOFS20.TEST.NEWCNTL USER05TSOFS20.TEST.SAMPLE USER03TSOFS20.TEST1.TEST USER04

/ TSOFS20.TSOE.CNTL USER08TSOFS20.TSOE.EXEC USER02TSOFS20.UNIT2LAB.TEXT USER02

***************************** End of Data Set list ****************************


DSLIST display panel

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

mo Move data set i|s Data set information p Print data set z Compress data set

In addition a forward slash (/) next to the data set name can be used to display a pop-up window that will list the available commands.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-96. Data Set List Actions pop-up window ES1011.0

Notes:

Instead of entering the command in the Command field before the data set name, you can also enter a forward slash (/) to bring up with a Data Set List Action window, from which the desired operation can be selected.


Menu Options View Utilities Compilers HelpData Set List

D Data Set List Actions Row 1 of 12C ===> PAGEC Data Set: TSOFS20.TSOE.CNTL Volume - -----------

DSLIST Action *ALIAS 1 1. Edit 12. Compress USER06

2. View 13. Free USER02 3. Browse 14. Print Index USER04 4. Member List 15. Reset USER05 5. Delete 16. Move USER05

/ 6. Rename 17. Copy USER05 7. Info 18. Refadd USER03 8. Short Info 19. Exclude USER04

* 9. Print 20. Unexclude 'NX' USER08 10. Catalog 21. Unexclude first 'NXF' USER02 11. Uncatalog 22. Unexclude last 'NXL' USER02

************Select a choice and press ENTER to process data set action.F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap F12=Cancel


Data Set List Actions pop-up window

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 3-97. Block commands in Data Set List ES1011.0

Notes:

Starting with z/OS V1R10, ISPF DSLIST now allows you to issue commands against a block of data sets grouped together in the list. A block of line commands is marked by entering two forward slash characters (//) at the start and end of the block.

For the ISPF Data Set List Utility, line commands can now be entered in block command format to execute the same line command for several data sets at once. The block is marked by typing a // at the beginning and another // at the end of a block of rows.

The line command must follow the // immediately on the first or last row of the block.

All line commands, including TSO commands, Clists and REXX execs can be executed as block commands.

Several blocks of commands can be entered at the same time, but they cannot be nested.

Single line commands are not allowed within a block command.

Benefit: Removes the need to enter the line command against each data set when they are grouped together in the list


Block commands in Data Set List• A block of line commands is marked by entering two forward

slash characters (//) at the start and end of the block.• The required line command is entered on the first or last line of

the block, immediately following the two forward slash characters.

• All line commands, including TSO commands, clists, and REXX execs can be executed as block commands.

• Several blocks of commands can be entered at the same time, but only serially.

• Single line commands are not allowed within a block command.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 3-98. Block commands in Data Set List: Usage ES1011.0

Notes:

ISPF DSLIST now allows you to issue commands against a block of data sets grouped together in the list. A block of line commands is marked by entering two forward slash characters (//) at the start and end of the block.

You must type the line command either immediately after the // on the first row of the block, or immediately after the // on the last row of the block. Figure 3-98, "Block commands in Data Set List: Usage," on page 3-121 shows an example of entering a delete command against 7 data sets in the list.

You can enter several blocks of commands at the same time, but you cannot nest them.

Single line commands are not allowed within a block command. You can execute all line commands, including TSO commands, Clists and REXX execs as block commands. If you have selected the DSLIST settings option Execute Block Commands for excluded data sets, all applicable excluded rows are unexcluded before the block commands are executed.


Block commands in Data Set List: Usage

Menu Options View Utilities Compilers Help

ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss DSLIST - Data Sets Matching PRICHAR Data set not deleted Command ===> Scroll ===> CSR

Command - Enter "/" to select action Message Volume -------------------------------------------------------------------------------

PRICHAR.DDIR.D MOXSM1 PRICHAR.DDIR.I MOXSM1 PRICHAR.DDIR.REPROED MOXWK0 PRICHAR.DDIR.REPROED.DECRYPTD MOXTM1 PRICHAR.DDIR.REPROED.ENCRYPTD MOXWK1 PRICHAR.DEPMGR.CERTBIN MOXWK1 PRICHAR.DLIB.CSI *VSAM* PRICHAR.DLIB.CSI.DATA MOXSMP PRICHAR.DLIB.CSI.INDEX MOXSMP PRICHAR.DUMP.ES68V7 MOXWK1 PRICHAR.DUMP.SMPE.BEFORE.PORTED.TOOLS MOXWK1 PRICHAR.EBIZ.BASE.CNTL MOXTMP PRICHAR.EBIZ.BASE.DATA MOXTMP PRICHAR.EPST.LOAD MOXTMP

//d PRICHAR.ES10.T1 MOXTM2 PRICHAR.ES10.T2 MOXTMP PRICHAR.ES10.T3 MOXTMP PRICHAR.ES10.T4 MOXTM2 PRICHAR.ES10.T5 MOXTMP PRICHAR.ES10.T6 MOXTM2

// PRICHAR.ES10.T7 MOXTMP PRICHAR.ES6501.XMT MOXTM2 PRICHAR.ES66.CNTL COMMS1 PRICHAR.ES680.JOBLIB MOXTM2

*DSLIST -ISFPCU4 DSLIST ISR@PRIM

Menu Options View Utilities Compilers Help

ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssDSLIST - Data Sets Matching PRICHAR Data set deletedCommand ===> Scroll ===> CSR

Command - Enter "/" to select action Message Volume------------------------------------------------------------------------------

PRICHAR.DDIR.D MOXSM1PRICHAR.DDIR.I MOXSM1PRICHAR.DDIR.REPROED MOXWK0PRICHAR.DDIR.REPROED.DECRYPTD MOXTM1PRICHAR.DDIR.REPROED.ENCRYPTD MOXWK1PRICHAR.DEPMGR.CERTBIN MOXWK1PRICHAR.DLIB.CSI *VSAM*PRICHAR.DLIB.CSI.DATA MOXSMPPRICHAR.DLIB.CSI.INDEX MOXSMPPRICHAR.DUMP.ES68V7 MOXWK1PRICHAR.DUMP.SMPE.BEFORE.PORTED.TOOLS MOXWK1PRICHAR.EBIZ.BASE.CNTL MOXTMPPRICHAR.EBIZ.BASE.DATA MOXTMPPRICHAR.EPST.LOAD MOXTMPPRICHAR.ES10.T1 Deleted PRICHAR.ES10.T2 Deleted PRICHAR.ES10.T3 Deleted PRICHAR.ES10.T4 Deleted PRICHAR.ES10.T5 Deleted PRICHAR.ES10.T6 Deleted PRICHAR.ES10.T7 Deleted PRICHAR.ES6501.XMT MOXTM2PRICHAR.ES66.CNTL COMMS1PRICHAR.ES680.JOBLIB MOXTM2

*DSLIST -ISFPCU4 DSLIST ISR@PRIM

1

2

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Work with data set lists (ISPF/PDF option 3.4)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (1 of 3)1. Which are the standards for naming partition data sets? (Mark all that

apply.)a. Simple names connected with periodsb. Simple name must be eight characters in lengthc. Data set name can be a maximum of 54 characters in lengthd. Data set names can have up to 22 qualifiers

2. True or False: The records in a sequential data sets can be processed randomly.

3. A partitioned data set (PDS) is divided into sequentially organized (blank).a. Directoriesb. Membersc. Charactersd. Partitions

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (2 of 3)4. What is an edit profile?

a. Set of characteristics that define the way you can edit a data setb. Description of the ISPF userc. Definition of the way you can edit a data setd. Definition of the data attributes

5. True or False: In edit mode, to scroll up and down use F10 and F11.

6. The CREATE macro command creates a (blank) of a partitioned data set from the data you are editing.a. Sequential data setb. Recordc. Memberd. Volume

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (3 of 3)7. The prefix area is the six-digit field at the beginning of each line. It is

used to process so-called (blank).a. Proceduresb. Clistc. Shell scriptsd. Line commands

8. True or False: CUT and PASTE is used to copy lines from one member or data set to another.

9. To browse the contents of a member prior to making any selection, use which line command?a. s

b. b

c. r

d. e

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:

Data set allocation:

• Data set naming rules and conventions

• How to specify a data set name

ISPF/PDF Editor:

• Primary and line commands

• Function keys

Copying/Moving data sets or members

Renaming data sets or members

Deleting data sets or members

Data set lists


Tasks:1. Log on to TSO.2. Work with data set lists.3. Move, rename, and

delete members.4. Compress and delete

data sets.5. Log off.

Exercise

Data set lists

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Unit summaryHaving completed this unit, you should be able to:• Allocate a new sequential or partitioned data set• Edit a data set using the ISPF/PDF editor



• Use ISPF/PDF line commands in the prefix area• Copy or move an entire data set or selected members • Rename a data set or member • Delete an entire data set or a single member • Work with data set lists (ISPF/PDF option 3.4)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Unit 4. Working with TSO/E


This unit describes the basic layout of TSO/E commands as well as their commonly used notation, and introduces the students to a number of TSO/E commands.



• Describe the general structure of TSO/E commands • Read the notation of TSO/E commands • Describe and use a series of important TSO/E commands

HELP ALLOCATE DELETE LISTDS LISTCAT LISTALC FREE PRINTDS PROFILE SUBMIT SEND TRANSMIT RECEIVE



References

SA22-7784 TSO/E General Information (GIM)

SA22-7787 TSO/E Primer

SA22-7782 TSO/E Command Reference xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 4. Working with TSO/E 4-1

Student Notebook

.


Notes:


Unit objectives After completing this unit, you should be able to:• Describe the general structure of TSO/E commands• Read the notation of TSO/E commands• Describe and use a series of important TSO/E commands:

HELP ALLOCATE

DELETE LISTDS

LISTCAT LISTALC

FREE PRINTDS

PROFILE SUBMIT

SEND TRANSMIT

RECEIVE

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

4.1. TSO/E commands

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-2. TSO/E commands ES1011.0

Notes:

A command consists of a command name usually followed by one or more operands. Operands provide the specific information required to perform the requested operation. TSO distinguishes two types of operands with the commands:

Positional operands Positional operands follow the command name in a certain order. In the command descriptions within this topic, the positional operands are shown in lowercase characters. When you enter a positional operand that is a list of several names or values, you must enclose the list within parentheses, for example,

LISTDS (PARTS.DATA TEST.DATA)

Keyword operands Keyword operands are specific names or symbols that are recognized by the system. Therefore, keyword operands can be entered in any order following the positional operands. In the upcoming command descriptions, keyword operands are shown in uppercase characters. You can specify values with


Command name

Positionaloperand

Keywordoperand

LISTDS ‘TSOFS20.TEST.DATA’ MEMBERS

TSO/E commandsGeneral layout of a TSO/E command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

some keyword operands. Enclose the values in parentheses following the operand:

LINESIZE(integer)

If you enter conflicting, mutually exclusive keywords, the last keyword operand overrides the previous ones.

You can enter the full name of keyword operands or use an acceptable abbreviation. Any keyword can be abbreviated by entering only as much of its name as is necessary to distinguish it from other keywords of the same command or subcommand. (Some commands, like DELETE and LISTCAT, provide additional abbreviations for their operands.)

When you type a command, you must separate the command name from the first operand by one or more blanks. You must separate operands by one or more blanks or a comma.

When it is necessary to continue a command to the next line, use a plus (+) or minus (-) sign as the last character of the line you want to continue, for example:

ALLOCATE DATASET('AUES100.TEST.EXEC') NEW REUSE DSORG(PO) SPACE(10,10) + LRECL(80) BLKSIZE(3120) DIR(5) RECFM(F,B)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-3. General notation of a TSO/E command ES1011.0

Notes:

How to read the notation of a TSO/E command from the visuals in this unit and other TSO/E documentation: • Double arrows indicate the beginning and ending of a statement. • If a statement syntax requires more than one line to be shown, single arrows indicate

their continuation. • Required items appear on the horizontal line (the main path). • Optional items appear below the main path. • If you can choose from two or more items, they are stacked vertically. • If you must choose one of the items, an item of the stack appears on the main path. • If choosing one of the items is optional, the entire stack appears below the main path. • An arrow returning to the left above main line indicates an item that can be repeated. • A repeat arrow above a stack indicates that you can make more than one choice from

the stacked items, or repeat a single choice. • Default values appear either underlined or above the main path in the diagrams. • A dotted arrow indicates that only a subset of the entire command syntax is shown.

(This notation is used in this course only, as we explain only a subset of all parameters.)


COMMANDCMD

( )positionaloperand

KEYWORDOPERAND

1 2

2

3

4 5

6

7

8

9

10

additional parameter

11

KEYWORDOPERANDKEYWORDOPERAND

KEYWORDOPERAND

KEYWORDOPERAND

KEYWORDOPERAND

KEYWORDOPERAND

General notation of a TSO/E command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 4-4. The HELP command ES1011.0

Notes:

Use the HELP command to obtain information about the function, syntax, and operands of commands and subcommands, as well as information about certain messages. The reference information is contained within the system and is displayed at your terminal in response to your request for help. The scope of available information ranges from general to specific. When entering the HELP command with no operands, TSO/E displays a list of all the TSO/E commands grouped by function. If you require more information about a specific command or subcommand, use HELP with the selected command or subcommand name as an operand. You then receive:

• A brief description of the function of the command or subcommand

• The format and syntax for the command or subcommand

• A description of each operand


READY

help listds operands

OPERANDS -'DSLIST' - NAMES OF DATA SETS FOR WHICH INFORMATION IS REQUESTED. STATUS - DDNAME AND DATA SET DISPOSITION ARE DISPLAYED. HISTORY - CREATION AND EXPIRATION DATES, DATA SET ORGANIZATION AND

SECURITY STATUS ARE DISPLAYED. MEMBERS - MEMBER AND ALIAS NAMES OF PARTITIONED DATA SETS ARE DISPLAYED.LABEL - THE CHAIN OF DSCB'S FOR THE DATA SET ON A DIRECT ACCESS

DEVICE ARE LISTED ....

Example:

SYNTAX

HHELP

command_nameALL

POSITIONAL(nn)

MSGID( identifier )

subcommand_name

HHELP

SYNTAX

HHELP

command_nameALL

FUNCTION

OPERANDSoperand

POSITIONAL(nn)

MSGID( identifier )

subcommand_name

)(

The HELP command

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

If you do not want to have all of the detailed information, you can request only the portion that you need. The following is a brief description of the command's parameters:

command_name/subcommand_name

The name of the command/subcommand about which to obtain information.

ALL Displays all information available concerning the command or subcommand.

FUNCTION Shows information about the purpose and operation of the command or subcommand.

SYNTAX Displays information about the syntax of a command.

OPERANDS(operand) Explains the operands of a command or subcommand. Unless you specify a specific operand in parentheses, all operands are described.

POSITIONAL(nn) Shows information on a particular positional operand of the command or subcommand. The variable nn indicates the position of the positional operand that you want described.

MSGID(identifier) Requests additional information about the messages whose identifiers are specified.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 4-5. The ALLOCATE command ES1011.0

Notes:

Use the ALLOCATE command to dynamically allocate VSAM, non-VSAM, and hierarchical file system (HFS) data sets. You can specify data set attributes for the allocation of non-VSAM data sets in several ways:

• Describe all attributes of a new data set explicitly on the ALLOCATE command. • Use the LIKE operand to obtain the attributes from an existing model data set. You can

override model data set attributes by explicitly specifying the desired attributes on the ALLOCATE command.

• Use the ATTRIB command to build a list of attributes. During the remainder of your terminal session, you can have the system refer to this list when allocating new data sets.

• With the storage management subsystem (SMS) installed and active, use the DATACLAS operand. Your storage administrator might provide default data set attributes through the automatic class selection (ACS) routine.


Example:READY

alloc dsn(test.data) dd(test) new space(1,1) tra reulrecl(80) recfm(v,b)READY

(name)ALLOCATE

ALLOC

DATASET

DSNAME

( * )

dsnameFILE

DDNAME

OLDSHRMODNEW

DATACLAS(name) MGMTCLAS(name) VOLUME(volser)STORCLAS(name)

BLKSIZE(value) DIR(n) REUSESPACE(quantity) )increment BLOCK(value)

AVBLOCK(value)

TRACKSCYLINDERS

UNIT(type) LRECL(n) RECFM( )FV

, additional ParameterLIKE(dsn)

B

The ALLOCATE command

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Here is a list of the ALLOCATE command operands:

DATASET(dsname | *) | DSNAME(dsname | *)

Specifies the name or a list of names of the data sets to be allocated.

FILE(name) | DDNAME(name)

Specifies the name to be associated with the data set. It can contain up to eight characters.

Note: If you omit this operand, the system assigns an available file name (DDname).

OLD | SHR | MOD | NEW OLD indicates the data set currently exists and you require exclusive use of the data set.

SHR indicates the data set currently exists, but you do not require exclusive use of the data set. Others can use it concurrently.

MOD indicates you want to append data to the end of the sequential data set.

NEW (non-VSAM only) indicates the data set does not exist and it is to be created. If you specify a data set name, a new data set is kept and cataloged. If you do not specify a data set name, it is deleted when you free it or log off. SMS only manages data sets that were allocated with a disposition of NEW while SMS was active.

DATACLAS(data_class_name)

Specifies the name of the data class for the data set. Using the DATACLAS operand to define the data class makes specifying all the attributes for a data set unnecessary.

MGMTCLAS(management_class_name)

Specifies the name of the management class for a new data set.

STORCLAS(storage_class_name)

Specifies the storage class. The storage class replaces the storage attributes on the UNIT and VOLUME operand for non-SMS-managed data sets.

VOLUME(serial_list) Specifies the volume on which a new data set is to reside or on which an existing data set is located. If you omit the VOLUME operand, new data sets are allocated to any eligible direct access volume.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

SPACE(quantity,increment)

Specifies the amount of space to be allocated for a new data set. The variable quantity specifies desired primary space, increment the desired secondary space quantity. If you omit the SPACE operand, the system uses the IBM-supplied default.

BLOCK(value) | AVGBLOCL(value) | TRACKS | CYLINDERS

BLOCK(value) specifies the average length of the blocks written to the data set. AVGBLOCK(value) specifies the average length (in bytes) of the records that are written to the data set. TRACKS specifies the unit of space is to be a track. CYLINDERS specifies the unit of space is to be a cylinder.

BLKSIZE(blocksize) Specifies the data control block (DCB) block size for the data set.

DIR(integer) Specifies the size of a data set directory. DIR must be specified if you are allocating a new partitioned data set.

REUSE Specifies the file name being allocated is to be freed and reallocated if it is currently in use.

UNIT(type) Specifies the type of the unit to which a file or data set is to be allocated.

LIKE(dsn) References a model data set for the allocation of a new data set.

LRECL(n) Specifies the length, in bytes, of the largest logical record in the data set.

RECFM(F|V|B) Specifies the format and characteristics of the records in the data set. Use the following values with the RECFM operand:

• F indicates the records are of fixed-length. • V indicates the records are of variable-length. • B indicates the records are blocked.

(The operands listed here represent only a subset of all operands of this command. For additional information, refer to TSO/E Command Reference.) xc

lusivo

form

ación

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-6. The DELETE command ES1011.0

Notes:

Use the DELETE command to delete one or more data set entries or one or more members of a partitioned data set.

Here is a list of the command operands:

name/password Names the entries to be deleted. In case of a password-protected entry, you also have to provide the password to delete the entry.

CATALOG(catalog_name/password)

Specifies the name of the catalog that contains the entries to be deleted and the catalog's password.

FILE(ddname) Name of the DD statement that identifies the volume containing the data set to be deleted or identifies the entry to be deleted.


Example:READY

delete test.dataENTRY (A) TSOFS20.TEST.DATA DELETED

READY

DELETEDEL

( )name/password CATALOG(catalog_name

/password

FILE(ddname) PURGEPRG

SCRATCH

NSCR

additional parameter

NOPURGENPRG

NOSCRATCH

)

The DELETE command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

PURGE | PRG | NOPURGE | NPRG

PURGE or PRG specifies the entry is to be deleted even if the retention period has not yet expired. NOPURGE or NPRG specifies the entry is not to be deleted if the retention period has not yet expired.

SCRATCH | NOSCRATCH | NSCR

SCRATCH specifies a non-VSAM data set is to be erased from the VTOC. NOSCRATCH or NSCR specifies a non-VSAM data set is not to be erased from the VTOC.

(The operands listed here represent only a subset of all operands of this command. For additional information, refer toTSO/E Command Reference.)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-7. The LISTDS command ES1011.0

Notes:

Use the LISTDS command to have the attributes of specific data sets displayed at your terminal. The LISTDS command works differently for VSAM than for non-VSAM data sets. A VSAM data set causes the LISTDS command to display only the data set organization, which is VSAM. Use the LISTCAT command to obtain more information about a VSAM data set. For non-VSAM data sets, you can obtain:

• Volume identification • Logical record length • Block size • Record format • Data set organization • Directory information for members of partitioned data sets • Creation date, expiration date, and, for non-VSAM only, security attributes. • File name and disposition • Data set control blocks


Example:READY

listds ‘TSOFS20.test.data'TSOFS20.TEST.DATA

--RECFM-LRECL-BLKSIZE-DSORG

FB 80 27920 PO

--VOLUMES--

USER04

READY

LISTDS STATUS

CATALOG ( catalog_name )

HISTORY MEMBERS LABEL

data_set( )

LEVEL

The LISTDS command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

This is a list of LISTDS command operands:

(data_set) Name of the data sets you want to obtain data about. You can use a single asterisk as a wild card in place of any level except the first.

STATUS Specifies that you want the following additional information:

• The DDname currently associated with the data set. • The termination dispositions of the data set.

HISTORY Obtains the creation and expiration dates for the specified data sets and find out whether the non-VSAM data sets are password-protected or if the data set is RACF-protected.

MEMBERS Displays a list of all the members of a partitioned data set, including aliases.

LABEL Lists the entire data set control block (DSCB) at your terminal.

CATALOG(catalog_name)

Names the user catalog that contains the names in the data set list.

LEVEL Specifies names in the data set list are to be high-level qualifiers. All cataloged data sets whose names begin with the specified qualifiers are listed.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-8. The LISTCAT command (1 of 2) ES1011.0

Notes:

Use the LISTCAT command to list entries from a catalog. The entries listed can be selected by name or entry type, and the fields to be listed for each entry can additionally be selected.

The original TSO LISTCAT command has been replaced by an Access Method Services command of the same name. The operand descriptions that follow provide the information required to use these services for normal TSO/E operations. The TSO/E user who wants to manipulate VSAM data sets or use the other Access Method Services from the terminal should refer to z/OS DFSMS Access Method Services for Catalogs, SC26-7394.

The LISTCAT command supports unique operand abbreviations in addition to the usual abbreviations produced by truncation. The syntax and operand explanations show these unique cases.


DATA INDEXIX

NONVSAMCLUSTERNVSAM

USERCATALOGUCAT

PAGESPACEPGSPC

CREATION (days)GENERATIONDATAGROUP

GDGALIAS

LISTC CATALOG ( catalog_name )LISTCAT

/password

OUTFILEOFILE

(ddname)ENTRIES ( entry_name )

LEVELLVL

( level )/password

The LISTCAT command (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

This is a list of LISTCAT command operands for this visual:

CATALOG(catalog_name/password)

Specifies the name of the catalog that contains the entries to be listed. When CATALOG is coded, only entries from that catalog are listed. The variable catalog_name is the name of the catalog. The variable password specifies the read level or higher-level password of the catalog that contains entries to be listed.

OUTFILE(ddname) | OFILE(ddname)

Specifies a data set other than the terminal to be used as an output data set. The DDname can correspond to the name specified for the FILE operand of the ALLOCATE command. The data can be listed when the file is freed. The DDname identifies a DD statement that in turn identifies the alternate output data set. If OUTFILE is not specified, the entries are displayed at the terminal.

ENTRIES(entry_name/password)

Specifies the names of the entries to be listed. If neither ENTRIES nor LEVEL operand is used, only the entries associated with the user ID are listed. For more information about the ENTRIES operand, refer to DFSMS Access Method Services for VSAM, SC26-4905. The variable entry_name specifies the names or generic names of entries to be listed. The variable password specifies a password when the entry to be listed is password protected and a password was not specified through the CATALOG operand.

LEVEL(level) | LVL(level) Specifies the level of entry_names to be listed. If neither LEVEL nor ENTRIES operand is used, only the entries associated with the user ID are listed.

CLUSTER Specifies cluster entries are to be listed. When the only entry type specified is CLUSTER, entries for data and index components associated with the clusters are not listed.

DATA Specifies entries for data components, excluding the data component of the catalog, are to be listed. If a cluster's name is specified on the ENTRIES operand and DATA is coded, only the data component entry is listed.

INDEX | IX Specifies entries for index components, excluding the index component of the catalog, are to be listed. When a cluster's name is specified on the ENTRIES operand and the INDEX operand is used, only the index component entry is listed.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

SPACE | SPC Specifies entries for volumes containing data spaces defined in this catalog are to be listed. Candidate volumes are included. If entries are identifies by entry name or level, SPACE can be coded only when no other entry type restriction is specified.

NONVSAM | NVSAM Specifies entries for non-VSAM data sets are to be listed. When a generation data group's name and NONVSAM are specified, the generation data sets associated with the generation data group are listed.

USERCATALOG | UCAT Specifies entries for user catalogs are to be listed. USERCATALOG is applicable only when the catalog that contains the entries to be listed is the master catalog.

GENERATIONDATAGROUP | GDG

Specifies entries for generation data groups are to be listed.

PAGESPACE | PGSPC Specifies entries for page spaces are to be listed.

ALIAS Specifies entries for alias entries are to be listed.

CREATION(days) Specifies entries are to be listed only if they were created no later than that number of days ago.

The LISTCAT command is continued on the next visual.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 4-9. The LISTCAT command (2 of 2) ES1011.0

Notes:

When LISTCAT is invoked and no operands are specified, the user ID or the prefix specified by the PROFILE command becomes the highest level of entry name qualification. Only those entries associated with the user ID are listed.

The list of LISTCAT command operands continued:

EXPIRATION(days) Specifies entries are to be listed only if they expire no later than the number of days from now.

NAME | VOLUME | ALLOCATION | HISTORY

ALL | Specifies the fields to be included for each entry listed. If no value is coded, NAME is the default. ALL specifies names of the entries are to be listed.

VOLUME Specifies the name, owner identification, creation date, expiration date, entry type, volume serial numbers and device types allocated to the entries are to be listed. Volume information is not listed for cluster entries (although it is for the


Example:READY

listcat level(aues100)

NONVSAM-------TSOFS20.TEST.DATA

IN-CAT---CATALOG.USERCAT1

NONVSAM-------TSOFS20.PROJ1.DATA

IN-CAT---CATALOG.USERCAT1

READY

MGMTCLASDATACLAS

NAME

ALLVOLUMEALLOCATIONHISTORY

EXPIRATION (days)

STORCLAS

The LISTCAT command (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

cluster's data and index entries), aliases, or generation data groups.

ALLOCATION Specifies the information provided by specifying VOLUME and detailed information about the allocation are to be listed. The information about allocation is listed only for data and index component entries.

HISTORY Specifies the name, owner identification, creation date, and expiration date of the entries are to be listed.

DATACLAS With storage management subsystem, indicates that the data class of the catalog is to be listed.

MGMTCLAS With storage management subsystem, indicates that the management class of the catalog is to be listed.

STORCLAS With storage management subsystem, indicates that the storage class of the catalog is to be listed.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 4-10. The LISTALC command ES1011.0

Notes:

Use the LISTALC command to obtain a list of the currently allocated data sets. LISTALC without operands displays a list of all currently allocated data set names. Here is a list of parameters: STATUS Displays information about the status of each data set. This

operand provides you with: • The DDname for the data set allocated and information

about attribute lists. • The termination dispositions of the data set

HISTORY Specifies that you want to obtain information about the history of each data set. This operand provides information on: • Creation date. • Expiration date. • Data set protection

MEMBERS Lists the member names of each of your partitioned data sets. SYSNAMES Specifies that you want to obtain a list of all allocated data sets,

including temporary data sets.


LISTALCLISTA STATUS HISTORY MEMBERS SYSNAMES

Example:READY

lista st h--DSORG--CREATED---EXPIRES---SECURITY--DDNAME---DISP--

ISPF.SYSPROG.CLIST.EDUCMVS.FB

PO 07/09/00 00/00/00 NONE SYSPROC KEEP

IAS.COURSE.CLIST.FB

PO 11/14/00 00/00/00 NONE KEEP

SYS1.AZE1CLIB

PO 08/24/00 00/00/00 NONE KEEP

ISPF.MAIN.CLIST.FB

PO 07/12/00 00/00/00 NONE KEEP

ISPF.MAIN.MSGS

PO 07/12/00 00/00/00 NONE ISPMLIB KEEP

...

The LISTALC command

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-11. The FREE command ES1011.0

Notes:

Use the FREE command to release (deallocate) previously allocated data sets or hierarchical file system (HFS) files that you no longer need. You can also use this command to change the output class of SYSOUT data sets, to delete attribute lists, and to change the data set disposition specified with the ALLOCATE command. There is a maximum number of data sets that can be allocated to you at any one time. The allowable number must be large enough to accommodate:

• Data sets allocated by the LOGON and ALLOCATE commands • Data sets allocated dynamically by the system's command processors

The data sets allocated by the LOGON and ALLOCATE commands are not freed automatically. To avoid the possibility of reaching your limit and being denied necessary resources, you should use the FREE command to release these data sets when they are no longer needed.

When you enter the LOGOFF command, all data sets allocated to you and attribute lists created during the terminal session are freed by the system.


DEST(station_id)FREE ALL

ATTRLIST attr_list_name )

DSNAMEDATASET

(

(

data_set_name )

DDNAMEFILE

( file_name )

OUTDES ( output_descriptor_name )

SPINHOLDNOHOLD

( UNALLOC )NO

DELETECATALOGUNCATALOGSYSOUT(class)

KEEP

)PATH ( /pathname PATHDISP ( DELETE )KEEP

The FREE command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

UNALLOC is the alias of FREE and is intended for use under TEST because FREE is an alias for the FREEMAIN subcommand.

Note

Data sets that are dynamically allocated by a command processor are not automatically freed when the command processor terminates. You must explicitly free dynamically allocated data sets.

Following is a list of the FREE command operands:

ALL Requests deallocation of all dynamically allocated data sets, files, and attribute lists that are not marked in-use.

DSNAME(data_set_name) | DATASET(data_set_name)

Specifies one or more data set names that identify the data sets that you want to free. The data set name must include the descriptive (rightmost) qualifier and can contain a member name in parentheses. If you omit this operand, you must specify either FILE, DDNAME, or the ATTRLIST operand.

DDNAME(file_name) | FILE(file_name)

Specifies one or more file names that identify the data sets to be freed. If you omit this operand, you must specify either the DATASET or DSNAME or the ATTRLIST operand.

OUTDES(output_descriptor_name)

Specifies a list of output descriptor names, previously defined by the OUTDES command, that are to be freed. Only output descriptors defined by the OUTDES command are freed. You cannot free output descriptors defined in the LOGON procedure.

ATTRLIST(attr_list_names)

Specifies the names of one or more attribute lists that you want to delete. If you omit this operand, you must specify either the DATASET or DSNAME or the FILE or DDNAME operand.

DEST(station_id) Specifies a name of a remote workstation to which the SYSOUT data sets are directed when ready for deallocation. The station ID is a 1 to 8-character name. If this operand is omitted on the FREE command for SYSOUT data sets, the data sets are directed to the workstation specified at the time of allocation.

HOLD | NOHOLD HOLD specifies the data set is to be placed on the HOLD queue. HOLD overrides any HOLD/NOHOLD specification made when the

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

data set was originally allocated, and it also overrides the default HOLD/NOHOLD specification associated with the particular SYSOUT class specified.

NOHOLD specifies the data set is not to be placed on the HOLD queue. NOHOLD overrides any HOLD/NOHOLD specification made when the data set was originally allocated and it also overrides the default HOLD/NOHOLD specification associated with the particular SYSOUT class specified.

KEEP | DELETE | CATALOG | UNCATALOG | SYSOUT(class)

• KEEP specifies the data set is to be retained by the system after it is free. KEEP is the defaault value for the FREE command.

• DELETE specifies the data set is to be deleted by the system after it is freed. DELETE is not valid for data sets allocated with SHR or for members of a partitioned data set. Only DELETE is valid for SYSOUT data sets.

• CATALOG specifies the data set is to be retained by the system in a catalog after it is freed.

• UNCATALOG specifies the data set is to be removed from the catalog after it is freed. The data set is still retained by the system.

• SYSOUT(class) specifies an output class which is represented by a single character. All of the system output (SYSOUT) data sets specified in the DATASET or DSNAME and FILE or DDNAME operands are assigned to this class and placed in the output queue for processing by an output writer. To free a file to SYSOUT, the file must have previously been allocated to SYSOUT. A concatenated data set that was allocated in a LOGON procedure or by the ALLOCATE command can be freed only by entering the DDname on the FILE or DDNAME operand. It can also be freed by entering FREE ALL.

SPIN(UNALLOC | NO) Specifies when the system should make the SYSOUT data set available for printing. UNALLOC specifies that the system should make the SYSOUT data set available for printing immediately after deallocation. NO specifies that the system should make the SYSOUT data set available for printing at the end of the step.

PATH(/pathname) Identifies a hierarchical file system (HFS) file. A path name consists of the names of the directories from the root to the file being identified, and then the name of the file. The form is /name1/name2/.../namen. A pathname begins with a slash (/). The system treats any consecutive slashes like a single

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

slash. The path name can be 2 to 250 characters, including the slash. A path name is case sensitive. Thus, /usr/joe and /usr/Joe define two different files.

PATHDISP(KEEP | DELETE)

Modifies the disposition of an HFS file as part of DEALLOCATION or FREE processing. KEEP is the default and specifies that the file should be kept after processing. DELETE specifies that the file should be deleted after processing.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-12. The PRINTDS command ES1011.0

Notes:

Use the PRINTDS command to format and print data sets on any printer defined to the Job Entry Subsystem (JES). PRINTDS allows you to:

• Print data sets or members. • Reference output descriptors. • Format the data and either print it or copy it to a data set. • Print data sets that contain DCF data.

PRINTDS command operands:

DATASET(dsname) | DSNAME(dsname)

Names the data set(s) or member(s) to be printed.

FILE(file_name) | DDNAME(file_name)

The name of the file to be printed. All data sets within the concatenation are printed.


Example:READY

printds da(test.data)sysout(a)READY

PRINTDS

PR

DATASET

DSNAME

( dsname )

FILE

DDNAME

( file_name )CLASSSYSOUT

( class )

,( group_value ),COPIES (nnn MEMBERS

ALL

DIRECTORY

additional Parameter

The PRINTDS command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

CLASS(output_class) | SYSOUT(output_class)

Specifies the output class JES is to use for processing the specified data set. SYSOUT is an alias for CLASS.

COPIES(nnn,(group_value,...))

The number of copies to be printed for the data set. If you specify group values, the system ignores the nnn value. The group values describe how the printed copies are to be grouped (3800 printer only).

ALL | MEMBERS | DIRECTORY

Determines which portion of a partitioned data set is to be printed. MEMBERS causes the system to print only the data contained in the members of the data set. DIRECTORY specifies that the system is to print only the directory. ALL prints both the members as well as the directory.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-13. The PROFILE command ES1011.0

Notes:

The PROFILE command establishes, changes, or lists your user profile. The information in your profile tells the system how you want to use your terminal. The profile contains information on the following:

• Prefixing • Prompting • Message display • Message number display • Primary and secondary languages • And so forth

To display the current user profile, enter the PROFILE command without operands. Change your profile by using the PROFILE command with the appropriate operands. The changes remain valid from session to session.


Example:READY

profCHAR(0) LINE(0) PROMPT INTERCOM NOPAUSE NOMSGID NOMODE NOWTPMSG

NORECOVER PREFIX(TSOFS20) PLANGUAGE(ENU) SLANGUAGE(ENU)

DEFAULT LINE/CHARACTER DELETE CHARACTERS IN EFFECT FOR THIS TERMINAL

READY

prof nopref

additional ParameterSLANGUAGE(slanguage)

PREFIX(prefix)NOPREFIX

PLANGUAGE(planguage)MSGIDNOMSGID

PROFILEPROF

NOPROMPT NOINTERCOMPAUSENOPAUSE

PROMPT INTERCOM

The PROFILE command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Here is a list of PROFILE operands:

PROMPT | NOPROMPT PROMPT specifies that you want the system to prompt you for missing information. NOPROMPT specifies no prompting is to occur.

INTERCOM | NOINTERCOM

INTERCOM lets you receive messages from other terminal users. NOINTERCOM prohibits you from receiving messages from other users.

PAUSE | NOPAUSE PAUSE enables you to obtain additional information when a message is issued at your terminal while a CLIST or an in-storage command list is executing. During execution, TSO/E displays PAUSE and waits for you to enter? or press Enter. NOPAUSE causes no prompting during execution.

MSGID | NOMSGID MSGID includes message identifiers in diagnostic messages identifiers. NOMSGID specifies diagnostic messages are not to include message identifiers. This is the default.

PREFIX(dsname_prefix) | NOPREFIX

PREFIX(dsname_prefix) specifies a prefix that is to be appended to all non-fully-qualified data set names. NOPREFIX disables the prefixing of data set names.

PLANGUAGE(planguage)

Is the primary language to be used in displaying translated information (messages, help information, and so forth).

SLANGUAGE(slanguage)

The secondary language to be used in case the primary language fails.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-14. The SUBMIT command ES1011.0

Notes:

Use the SUBMIT command to submit one or more batch jobs for background processing.

The SUBMIT operands at a glance:

(data_set) | * The names of the data sets or data set members that contain the job control language (JCL). An asterisk (*) specifies that the job stream is to be obtained from the current source of input (for example, the terminal). TSO/E commands can be entered directly without creating and editing a data set.

PAUSE | END(nn) PAUSE lets you decide, after the job stream has been read in, whether to continue or terminate the SUBMIT process. END(nn) defines a 1- or 2-character string to indicate the end of the job stream. If not specified, a null or blank line is used as delimiter.

HOLD | NOHOLD HOLD specifies SUBMIT is to have job output held for use with the OUTPUT command. Output directed to DD statements is held


Example:READY

submit 'aues100.tsoe.cntl(iefbr14)'JOB TSOFS20A(JOB04970) SUBMITTED

READY

SUBMITSUB

*

( data_set ) END(nn)

NOHOLD

HOLDPAUSE

NONOTIFY

NOJOBCHAR NOTIFY

additional ParameterJOBCHAR(char)

The SUBMIT command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

if SYSOUT=* or HOLD=YES is specified on the DD statement. NOHOLD specifies job output is not to be held.

JOBCHAR(characters) | NOJOBCHAR

JOBCHAR(characters) appends specified job characters to the job name on every JOB statement.

NOJOBCHAR causes TSO to prompt you for job name characters whenever the job name is the user ID. If prompting is not possible, TSO uses X as a default.

NOTIFY | NONOTIFY NOTIFY specifies that you are to be notified when your batch job terminates, if a JOB statement has not been provided. If a JOB statement is generated, NOTIFY is the default. (When you supply your own JOB statement, use the NOTIFY=user_id keyword on the JOB statement if you want to be notified when the job terminates.)

NONOTIFY specifies a termination message is not to be issued.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-15. The SEND command ES1011.0

Notes:

Use the SEND command to send messages to other users. To receive the messages, the recipient's profile setting must include INTERCOM. Installations can use security enhancements to customize how the SEND command works.

SEND command operands:

'text' The text of the message to be sent enclosed in apostrophes ('). The message is limited to 115 characters.

USER(user_id | *) user_id specifies the recipients of the message. If used with the SEND command at a terminal, * causes the message be sent to the same terminal.

NOW | LOGON | SAVE NOW specifies that you want the message to be sent immediately. If the recipient is not logged on or is not receiving messages, you are notified and the message is deleted.

LOGON specifies that you want the message retained in the SYS1.BRODCAST data set or the user log data set, if the


Example:READY

send 'Hello' user(aues100)Hello TSOFS20

READY

SENDSE

'text 'USER( * )

user_id

NOWAIT

additional ParameterWAITLOGON

SAVE

NOW

The SEND command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

recipient is not logged on, or is not receiving messages. If the recipient is currently using the system and receiving messages, the message is sent immediately. Otherwise, the message is saved and can be retrieved by the recipient. SAVE specifies the message text is to be stored in the mail section of SYS1.BRODCAST or the user log data set without being sent to any user. Messages stored in the broadcast data set or the user log data set can be retrieved by using either LISTBC or LOGON commands.

NOWAIT | WAIT NOWAIT specifies that you do not want to wait if system output buffers are not immediately available for all specified logged-on terminals. You are notified of all specified users who did not receive the message.

WAIT specifies that you want to wait until system output buffers are available for all specified logged on terminals.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-16. The TRANSMIT command ES1011.0

Notes:

Use the TRANSMIT command to send messages, data sets, or both, to another user. The TRANSMIT command converts this data into a special format so that it can be transmitted to other users in the network. TRANSMIT command operands:

(addressee) Specifies the target users.

TERMINAL | DATASET(dsname) | DSNAME(dsname) | DDNAME(ddname) |FILE(ddname)

TERMINAL specifies data input is to be taken from the terminal. You are prompted to enter data to be transmitted.

DATASET or DSNAME specifies the name of a data set to be transmitted.

DDNAME or FILE specifies the file name of a file to be transmitted.


Example:READY

xmit system1.hugo dataset(tsoe.exec) notify

READY

MEMBERS( member ) NOTIFY

NONOTIFY(ALL)

SEQUENTIALadditional Parameter

,

PDS

TRANSMITXMIT

addressee

( addressee ) DATASET (dataset)DSNAMEDDNAMEFILE

(ddname)

, TERMINAL

The TRANSMIT command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

MEMBERS(member) Transmits a list of members from the specified partitioned data set. If you transmit a member of a preallocated partitioned data set, you must specify the MEMBERS operand.

NOTIFY | NOTIFY(ALL) | NONOTIFY

NOTIFY notifies the sender when the data has been received.

NOTIFY(ALL) notifies the sender when the data has been received by all addressees.

NONOTIFY suppresses the notify function.

PDS | SEQUENTIAL PDS unloads a member or members of a partitioned data set (PDS) before transmission. This method preserves the directory information.

SEQUENTIAL sends a member of a partitioned data set or a sequential data set as a sequential data set. This method does not preserve directory information.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-17. The RECEIVE command ES1011.0

Notes:

The RECEIVE command is used by the addressee of a file transmission to retrieve transmitted files and to restore them to their original format.

RECEIVE command operands:

USERID(user_id) Specifies the user ID by which the transmitted files are received. USERID(user_id) allows the RECEIVE to be performed by a user different than the addressee of the file transmission.

INDDNAME(ddname) | INFILE(ddname) | INDSNAME(dsname) | INDATASET(dsname)

Allows you to receive the transmitted files in a preallocated data set.

DISPLAY | NODISPLAY DISPLAY specifies that the transmitted data or message is to be displayed at the terminal. NODISPLAY suppresses the display.


Example:READY

receive inds(tsoe.test) nodisplay

READY

RECEIVEUSERID(user_id) INDDNAME (ddname)

INFILEINDSNAME (dsname)INDATASET

NODISPLAY

DISPLAY

additional Parameter

The RECEIVE command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 4-18. How to issue TSO/E commands ES1011.0

Notes:

TSO/E commands can be issued from various places, including the TSO/E command line editor, ISPF panels, and ISPF option 6, the ISPF Command Shell. If you are in PDF and would like to issue TSO/E commands, you can either enter them in any command line or select ISPF option 6. To enter the commands in the TSO command line editor, leave PDF until READY appears on your screen. READY indicates that you are now in TSO/E mode and can enter any TSO/E command. When you enter TSO/E commands from a panel's command line, make sure to prefix them with TSO to signal ISPF/PDF to pass it on to TSO/E. When using the ISPF Command Shell to issue TSO/E commands, enter them here:

Enter TSO or Workstation commands below: ===> __________________________________________________________________

Commands that are entered here must not be prefixed. Any issued command appears in the list of recently used commands. To retrieve a command from this list, place the cursor on its line and press Enter. The selected command is now displayed on the command line and can be reissued, with or without modifications.


From TSO command line editor:

From ISPF/PDF panels:

From ISPF command shell:ISPF Command Shell

Enter TSO or Workstation commands below:

===> printds da(test.data)sysout(a)

Place cursor on choice and press enter to Retrieve command

=> lista st h => printds dataset(jcl.cntl) members

READY

printds da(test.data) sysout(a)READY

Option ===>

F1=Help F3=Exit F10=Actions F12=Cancel

TSO printds da(test.data)sysout(a)

How to issue TSO/E commands

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 4-19. Checkpoint ES1011.0

Notes:


Checkpoint1. True or False: The TSO ALLOCATE command can be used to allocate

new and existing data sets for use.

2. True or False: You can use the SUBMIT command to submit one or more batch jobs for foreground processing.

3. True or False: You can issue TSO commands from SDSF.

4. Text messages can be sent to other TSO users using the (blank)command.a. TRANSMIT

b. CALL

c. SEND

d. MESSAGE

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Use ALLOCATE to create new

data sets.3. Verify the create.4. Use the LISTDS command.5. Exercise the PROFILE command.6. Use DELETE with data sets.7. Modify an ISPF panel and CLIST.8. Reallocate data sets and start

ISPF.9. Log off.

Exercise

Using TSO/E commands

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:

The following have been covered in this unit:

• General layout of a TSO command:

- Command name - Positional operands - Keyword operands

• TSO commands:

HELP ALLOCATEDELETE LISTDSLISTCAT LISTALCFREE PRINTDSPROFILE SUBMITSEND TRANSMIT / RECEIVE


Unit summaryHaving completed this unit, you should be able to:• Describe the general structure of TSO/E commands• Read the notation of TSO/E commands• Describe and use a series of important TSO/E commands:

HELP ALLOCATE

DELETE LISTDS

LISTCAT LISTALC

FREE PRINTDS

PROFILE SUBMIT

SEND TRANSMIT

RECEIVE

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E
xclus
ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Unit 5. Working with JCL


This unit reviews the job processing phases in JES2 in detail, introduces the students to the basic concepts and rules of jobs and job control language (JCL), and explains how job output can be viewed using ISPF/PDF's Outlist Utility or the System Display and Search Facility.



• Identify JES2 and JES3 job processing phases • Explain the JES2 job processing phases in detail • Describe the basic rules for coding JCL • Code JOB/EXEC/DD statements • Submit a job and display its output • Define the term utility • Name and explain the different kinds of utilities • Describe the function and use of the following utilities:

- IEFBR14 - IEBCOPY - IEBGENER - IDCAMS

• Describe the function and use of DFSORT • Work with z/OS procedures:

- Explain the concept of a procedure - Distinguish the different procedure types - List the advantages of procedures - Code and use a procedure - Override procedure statements - Name the standard procedure search order - Specify private procedure libraries - Describe the concept of symbolic variables - Explain the use of INCLUDE groups



xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 5. Working with JCL 5-1

Student Notebook

.

References

SA22-7670 SDSF Operation and Customization

SA22-7597 MVS JCL Reference

SA22-7782 TSO/E Command Reference

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-1. Unit objectives (1 of 2) ES1011.0

Notes:


Unit objectives (1 of 2) After completing this unit, you should be able to:• Identify JES2 and JES3 job processing phases• Explain the JES2 job processing phases in detail• Describe the basic rules for coding JCL• Code JOB/EXEC/DD statements• Submit a job and display its output• Define the term utility• Name and explain the different kinds of utilities• Describe the function and use of the following utilities:

– IEFBR14

– IEBCOPY

– IEBGENER

– IDCAMS

• Describe the function and use of DFSORT

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-2. Unit objectives (2 of 2) ES1011.0

Notes:


Unit objectives (2 of 2)After completing this unit, you should be able to:• Work with z/OS procedures:

– Explain the concept of a procedure– Distinguish the different procedure types– List the advantages of procedures– Code and use a procedure– Override procedure statements– Name the standard procedure search order– Specify private procedure libraries– Describe the concept of symbolic variables– Explain the use of INCLUDE groups

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

5.1. JES2 job processing phases

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-3. JES2 job processing phases ES1011.0

Notes:


JES2 job processing phases


Introduction to job control language

The Outlist Utility and SDSF

JCL Utility overview

Introduction to JCL procedures

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Identify JES2 and JES3 job processing phases• Explain the JES2 job processing phases in detail

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-5. Job entry subsystem (JES2 and JES3) overview ES1011.0

Notes:

z/OS use a Job Entry Subsystem (JES) to receive jobs into the operating system, schedule them for processing, and to control their output processing. IBM provides two JESs: JES2 and JES3. The management of jobs and resources in z/OS is handled between JES and the base control program (BCP). In this manner, JES manages jobs before and after execution; the base control program manages them during processing.

Within JES2, each processor controls its own job input, job scheduling, and job output processing, while sharing the spool and checkpoint data sets.

In contrast, JES3 exercises centralized control over its processing functions through a single global JES3 processor.

This global processor provides all job selection, scheduling, and device allocation functions for all the other JES3 systems. The centralized control that JES3 exercises provides increased job scheduling control, deadline scheduling capabilities, and increased control by providing its own device allocation.

In an installation that has only one processor, JES2 and JES3 perform similar functions.


Job entry subsystem (JES2 and JES3) overview

z/OS +

JES2Processor

SPOOL

JES2:

JES2dev

JES2dev

z/OS +

JES2Processor

Loosely coupled

JES3dev

z/OS + JES3Processor

Global processor

z/OS +

JES3 LocalProcessor

z/OS +

JES3 LocalProcessorSPOOL

JES3:

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:

The process of job processing in JES2 can be divided into the following five stages:

Input phase After JES2 reads the job input which can be local or remote, a unique job number is assigned to each job. Then the job and its in-stream data (often called SYSIN data) are written to the SPOOL.

Conversion phase This phase determines whether the JCL contains procedure calls. If this is the case, the procedure code is added to the job's JCL. The result is called internal text. During this phase, a syntax check takes place. In case of an error, the job branches directly to the output phase.

Execution phase When an initiator requests work, JES2 selects a job from the job queue for execution. During the execution phase, the programs of a job are executed.


Input

Conversion

Execution

Output

Purge

JCL

Spool

Printout

Print

PROCLIB

In stream data


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Output phase After the completion of a job's processing, JES analyzes the output characteristics of a job. According to these specifications, the job is now queued in an output queue.

Purge phase Now that the job has been fully processed, JES frees all allocated SPOOL areas and signals the job completion to the operator.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:

Job management in JES3 can be divided into six stages. These are:

Input phase After JES3 reads the job input, which can be local or remote, a unique job number is assigned to each job. Then the job and its in-stream data (often called SYSIN data) are written to a SPOOL volume.

Conversion phase This phase determines whether the JCL contains procedure calls. If this is the case, the procedure code is added to the job's JCL. The result is called internal text. During this phase a syntax check takes place. In case of an error, the job branches directly to the output phase. Based on the internal text, the conversion phase also creates control blocks, which are used for the resource allocation during the next phase.

Resource Allocation Unlike JES2, where the resource allocation takes place during job execution, JES3 requires the allocation of all resources requested by a job prior to its execution. This prevents a job


Input

Conversion

Execution

Output

Purge

JCL

Resource allocation

In stream data

Printout

Print

Spool

PROCLIB


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

from being requeued in the JES queue due to the unavailability of a resource.

Execution phase Whenever an initiator requests work, JES3 selects a job from the job queue for execution. In a multiprocessor JES3 environment, this is handled by the global processor. During the execution phase, the programs of a job are executed.

Output phase After the completion of job processing, JES analyzes the output characteristics for a job. According to the specifications, the job is now queued in an output queue.

Purge phase Now that the job has been fully processed, JES frees all allocated SPOOL areas and signals the job completion to the operator.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-8. Job input phase ES1011.0

Notes:

JES2 jobs can be entered on input devices such as card readers, remote terminals, or other programs. Jobs can also come from other nodes in a job entry network and from internal readers. (An internal reader is a program that other programs can use to submit jobs, control statements, and commands to JES2.)

As JES2 reads the input stream, it assigns a job identifier to each job and places each job's JCL, optional JES2 control statements, and data within the job (SYSIN data) onto DASD data sets called spool data sets. The term simultaneous peripheral operations online (spool) refers to the direct access device that contains the spool data sets. Spooling provides simultaneous processing and a temporary storage area for work that is not yet completed.

Later on, JES2 selects jobs from the spool data sets for processing and subsequent running.


JCL

JES2

Spool• JCL• DATA

Job Class

101218541096

.

.

.

TZBA...

Job queue

Job input phase

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-9. Job conversion phase ES1011.0

Notes:

JES2 uses a converter program to analyze each job's JCL statements and to perform a syntax check. It also determines if the JCL includes any procedure calls. If so, the converter takes the job's JCL and merges it with the JCL from the procedure library (for example, SYS1.PROCLIB) and converts the composite JCL into internal text.

The internal text is stored in the spool data set. If during the job conversion any JCL errors are detected, JES2 issues the proper error messages and queues the job for output processing. If JES2 detects no errors, it queues the job for further processing according to its priority within its job class.


CONVERSION

PROCLIB

Spool• JCL• DATA

Spool• Internal text

Job conversion phase

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-10. Job execution phase ES1011.0

Notes:

Before work can be processed on an z/OS system, initiators have to be started. An initiator is started either by an operator or automatically by JES2 when the system is initialized. If an initiator is ready to process work, it requests a job from JES2. JES2 selects jobs based on the job classes that are assigned to the initiator and the priority order in which the job classes should be searched. When JES2 selects a job, it passes it to the initiator. The initiator then invokes the interpreter to build control blocks from the internal text that the converter created for the job. The initiator allocates the resources specified in the JCL for the first step of the job. This allocation ensures that the devices are available before the job step starts running. The initiator then starts the program requested in the JCL EXEC statement. JES2 and the base control program communicate constantly to control system processing. The communication mechanism, known as the subsystem interface, allows z/OS to request services of JES2. For example, a requester can ask JES2 to find a job, do message or command processing, or open (access) a SYSIN or SYSOUT data set. Further, the base control program notifies JES2 of events such as messages, operator commands, the end of a job, or the end of a task.


JES2

INITIATOR1

INITIATOR2

INITIATOR3

INITIATORn

....

Request

PGMAddress spaces

Job Class

101218541096

.

.

.

TZBA...

Job queue

Spool

Job execution phase

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-11. Job output and purge phases ES1011.0

Notes:

JES2 controls all output processing, that is, system messages that must be printed, as well as data sets requested by the user that must be printed or punched. After a job finishes, JES2 analyzes the characteristics of the job's output in terms of its output class and device setup requirements; then JES2 groups data sets with similar characteristics. JES2 queues the output for print or punch processing.

JES2 selects output for processing from the output queue. It can contain output that is to be processed locally or output to be processed at a remote location (either a remote job entry (RJE) workstation or another node known as network job entry (NJE)). After processing all the output for a particular job, JES2 puts the job on the purge queue.

When all processing for a job completes, JES2 releases the spool space assigned to the job, making the space available for allocation to subsequent jobs. JES2 then issues a message to the operator indicating that the job has been purged from the system.


JES2

Message

Before

After

Spool• JCL• DATA• Results

Spool• JCL• DATA• Results

Job output and purge phases

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Identify JES2 and JES3 job processing phases• Explain the JES2 job processing phases in detail

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

5.2. Introduction to job control language

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-13. Introduction to job control language ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Describe the basic rules for coding JCL• Code JOB/EXEC/DD statements

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-15. Introduction to job control language ES1011.0

Notes:

The origins of job control language (JCL) lay back in the 1960s. At that time, programmers used punched cards rather than terminals to enter their jobs into the system. To code a job, you actually had to punch the cards, which were then read by a local card reader. The cards that made up a job were referred to as a batch. Each card contained one JCL statement or part of a JCL statement, and the terms JCL statement and JCL card are still used synonymously.

The basic structure of JCL statements has not changed since its beginnings. Even today, JCL is coded on 80 positions per line, a limitation that has its roots in the use of 80-column punched cards.


//... JOB ...

//... EXEC ...

//... DD ...

//... DD ...

******* ***** Top of Data ************

000100 //TSOFS20A JOB (TSOFS20),'REXX',

000200 // MSGCLASS=T,CLASS=L,NOTIFY=TSOFS20

000300 //** * * * * * * * * * * * * * * * * * *

000400 //** DELETE DATASET

000500 //** * * * * * * * * *

000600 //STEP1 EXEC PGM=IDCAMS

000700 //SYSPRINT DD SYSOUT=*

000800 //SYSIN DD *

000900 DELETE TSOFS20.OUTPUT.DATA

001000 //** * * * * * * * * * * * * * * * * * *

001100 //** ALLOCATE AND COPY INTO DATASET

001200 //** * * * * * * * * *

001300 //STEP2 EXEC PGM=IEBGENER


001500 //SYSUT1 DD DSN=TSOFS20.INPUT.DATA,DISP=OLD

001600 //SYSUT2 DD DSN=TSOFS20.OUTPUT.DATA,

001700 // DISP=(NEW,CATLG),LIKE=TSOFS20.INPUT.DATA

001800 //SYSIN DD DUMMY

****** *****Bottom of Data ***********

Introduction to job control languageJCL history

• Each card could contain one JCL statement

• JCL is coded 80 positions per line

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-16. General layout of a job ES1011.0

Notes:

A job can be thought of as a logical description of work to be processed on a z/OS system. A job tells z/OS where to find the appropriate input, how to process that input (that is, what program or programs to run), and what to do with the resulting output. JCL statements are used to convey this information to z/OS.

Within each job, the control statements are grouped into job steps. A job step consists of all the control statements needed to run one program. It contains the program call and all the necessary allocations to execute this particular program. A job that needs to run more than one program contains a different job step for each one of those programs. The use of multiple job steps allows a programmer to implement dependencies between steps, for example, to make the execution of a job step dependent on the result of another job step.


Job

Jobstep

Jobstep

******* ***** Top of Data ************

000100 //TSOFS20A JOB (AUES100),'REXX',


000300 //** * * * * * * * * * * * * * * * * * *

000400 //** DELETE DATASET

000500 //** * * * * * * * * *

000600 //STEP1 EXEC PGM=IDCAMS


000800 //SYSIN DD *

000900 DELETE TSOFS20.OUTPUT.DATA

001000 //** * * * * * * * * * * * * * * * * * *

001100 //** ALLOCATE AND COPY INTO DATASET

001200 //** * * * * * * * * *

001300 //STEP2 EXEC PGM=IEBGENER


001500 //SYSUT1 DD DSN=TSOFS20.INPUT.DATA,DISP=OLD

001600 //SYSUT2 DD DSN=TSOFS20.OUTPUT.DATA,

001700 // DISP=(NEW,CATLG),LIKE=TSOFS20.INPUT.DATA

001800 //SYSIN DD DUMMY

****** *****Bottom of Data ***********

General layout of a job

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-17. General layout of a JCL statement ES1011.0

Notes:

A JCL statement consists of one or more 80-byte records. Each JCL statement is logically divided into the following five fields:

Identifier Tells the system what kind of statement this line contains. Possible statement types are JCL statements, JES statements, comments, and so forth.

Name Assigns a name to a particular JCL statement, which enables other statements to refer to it.

Operation Identifies the type of JCL statement, for example, JOB, EXEC, DD, and so forth.

Parameter Enables you to pass information along with the JCL statement. Parameters in a JCL statement follow the operation field and must be separated by commas.

Comments Serves documentary purposes only. It can contain any information you deem helpful when coding the statement.


****** ************************ Top of Data **************************

=COLS>----+----1----+----2----+----3----+----4----+----5----+----6----+----7

000100 //NAME OPERATION OPERANDS COMMENT

000200

000300

000400 //INPUT DD DSN=TSOFS20.TEST.DATA,DISP=SHR CONTAINS DATA TO BE TESTED

000500

000600

General layout of a JCL statement

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Except for the identifier field, which must begin in column 1, and the name field, which follows it with no intervening blanks, all other fields can be entered in free form, that is, they need not begin in a particular column. Between fields leave at least one blank, which serves as the delimiter between fields.

Do not code fields, except on the comment statement, past column 71. If the total length of the fields would exceed 71 columns, continue the fields onto one or more following statements.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-18. The identifier field ES1011.0

Notes:

The identifier field at the beginning of each line indicates to the system what kind of statement is contained in that line.

All JCL statements, start with // in positions 1 and 2 of each line. The only exception is the delimiter statement, which begins with /*. To mark a line as a comment statement, add an asterisk (*) in column 3 after the preceding // in columns 1 and 2.

Apart from JCL statements, jobs can also contain JES2 and JES3 control statements. JES2 control statements contain /* in columns 1 and 2. JES3 control statements, with a few exceptions, begin with //* in columns 1 through 3.


****** ******************************************

000100 //...

000200

000300 //*...

000400

000500 /*...

000600

Identifies a JCL statement

Identifies a comment or JES3 control statement

Identifies a delimiter or JES2 control statement

The identifier field

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-19. The name field ES1011.0

Notes:

The name field identifies a particular control statement therefore allowing other statements to reference it. For JCL statements the following naming rules apply:

• The name must begin in column 3.

• The name must not exceed eight alphanumeric or national (¢, #, @) characters in length.

• The first character must be alphabetic or national.

• The name must be followed by at least one blank.




000300 //** * * * * * * * * * * * * * * * * * * * * * * * *

000400 //** EXECUTE TSO-COMMANDS IN BACKGROUND

000500 //** * * * * * * * * * * * * * * * * * * * * * * * *

000600 //STEP1 EXEC PGM=IKJEFT01

000700 //SYSEXEC DD DUMMY

000800 //SYSTSPRT DD SYSOUT=*

000900 //SYSTSIN DD *

001000 LISTDS TSOE.CNTL

001100 /*

The name field

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-20. The operation field ES1011.0

Notes:

The operation field specifies the type of statement. Code the operation field of a JCL statement as follows:

• The operation follows the name field.

• The operation must be preceded and followed by at least one blank.

• The operation field must contain one of the following:

- //... CNTL... - //... DD... - //... ENDCNTL... - //... EXEC... - //... IF... THEN...

//... ELSE... //... ENDIF...

- //... INCLUDE... - //... JCLLIB...


000100 //TSOFS20A JOB(TSOFS20),'REXX',

000200 // MSGCLASS=T,CLASS=L,NOTIFY=AUES100

000300 //** * * * * * * * * * * * * * * * * * * * * * * * *


000500 //** * * * * * * * * * * * * * * * * * * * * * * * *






001100 /*

The operation field

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

- //... JOB... - //... OUTPUT... - // (Null Statement) - //... PEND... - //... PROC... - //... SET... - //... XMIT...

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-21. The parameter field ES1011.0

Notes:

The parameter field consists of two types of parameters: positional parameters and keyword parameters.

Positional parameters must precede all keyword parameters.

Keyword parameters can be added to a statement in any order in the parameter field after the positional parameters.

The parameters are separated by commas. The parameter field:

• Follows the operation field with at least one blank.

• Must not contain any blanks in between parameters.




000300 //** * * * * * * * * * * * * * * * * * * * * * * * *


000500 //** * * * * * * * * * * * * * * * * * * * * * * * *






001100 /*

The parameter field

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-22. Positional parameters ES1011.0

Notes:

When entering parameters, code positional parameters first. Code them in the order indicated by the syntax for this JCL statement. If you omit a positional parameter and code a following positional parameter, code a comma to indicate the omitted parameter. Do not code the replacing comma if:

• The omitted positional parameter is the last positional parameter.

• All following positional parameters are also omitted.

• Only keyword parameters follow.

• All positional parameters are omitted.


Examples:JCL statement syntax:

//name OPERATION P1,P2,P3,K1=n,K2=n

Omitting a positional parameter://name OPERATION P1,,P3,K1=4,K2=9

Omitting the last positional parameter://name OPERATION P1,P2,K1=4,K2=9

Omitting the leading positional parameter://name OPERATION ,,P3,K2=9

Omitting all positional parameters://name OPERATION K1=4,K2=9

Positional parameters

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-23. Keyword parameters ES1011.0

Notes:

Since keyword parameters are recognized by their names. Keyword parameters for a statement can be coded in any order after the positional parameters. No comma is necessary to indicate the absence of a keyword parameter.

A positional parameter or the variable information in a keyword parameter sometimes consists of more than one item, called a subparameter list. A subparameter list can consist of both positional and keyword subparameters. These subparameters follow the same rules as positional and keyword parameters.

When a parameter contains more than one subparameter, separate the subparameters by commas and enclose the subparameter list in parentheses or, if indicated in the syntax, by apostrophes. If the list is a single keyword subparameter or a single positional subparameter with no omitted preceding subparameters, omit the parentheses or apostrophes.


Examples:

Statement syntax://name OPERATION P1,P2,P3,K1=n,K2=n

Free flow://name OPERATION P1,,P3,K2=9,K1=4

Omitting a keyword parameter://name OPERATION P1,,P3,K2=9

Keyword parameters

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-24. Comment field ES1011.0

Notes:

The comment field contains any documentary information that might be helpful for understanding the JCL.

The comment field:

• Follows the parameter list.

• Must be preceded by at least one blank.

• Is always optional.

• Is different from the comment statement.




000300 //** * * * * * * * * * * * * * * * * * * * * * * * * *


000500 //** * * * * * * * * * * * * * * * * * * * * * * * * *

000600 //STEP1 EXEC PGM=IKJEFT01 STARTS TSO IN BACKGROUND



000900 //SYSTSIN DD * TSO COMMANDS TO BE EXECUTED in BATCH


001100 /*

Comment field

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-25. Statement continuation ES1011.0

Notes:

When coding JCL, the maximum length of a control statement must not exceed 71 characters on a single line. To code statements that exceed 71 characters in length, the statements have to be continued on the succeeding lines.

Note

The command statement, the comment statement, the delimiter statement, and the null statement are limited to a single line only. They cannot be continued. All other JCL statements can be continued either in the parameter field or the comments field.

Continuing the Positional and Keyword Parameter Fields

To continue the parameters of a statement on the following line, end the statement before column 72 with a complete parameter or subparameter followed by a comma, for example:

//DD1 DD DSNAME=SWITCH.LEVEL18.GROUP12,UNIT=3350,


****** ********************************************

=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7--

000100 //TSOFS20A JOB (TSOFS20),000200 // 'REXX',000300 // MSGCLASS=T,000400 // CLASS=L,000500 // NOTIFY=TSOFS20

000600 //STEP1 EXEC PGM=CHECK,PARM='THIS IS A VERY LONG PARAMETER LIST IN

000700 // APOSTROPHES, CONTINUED IN COLUMN 16'

000800 //DATA DD DSN=ATSOFS20.TEST.DATA,DISP=SHR THIS IS A CONFUSING METHOD OF C

00900 // CONTINUING A COMMENT, BETTER TO START A NEW COMMENT STATEMENT

Statement continuation

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Continue the statement on the next line. This line must start with // in columns 1 and 2, continued by at least one blank.

Continue the interrupted field beginning in any column from 4 through 16.

Example:

// VOLUME=335023,SPACE=(TRK,(80,15)),DISP=(,PASS)

Continuing Parameter Fields enclosed in apostrophes

The parameter must be extended to column 71. Do not code an apostrophe in column 71 of a JCL statement as the system interprets it as the final character in the statement and ignores the continuation.

| Col 71 V // COMMAND 'R0 MVSA,S GTF.RLW,,,MBR=UNITTEST,SPC=(CYL,(100,100)),VLSR=' // VOL=SER=VOL001,'',ODSN-W123456'

To avoid this, split the statement differently. Continue the parameter in column 16 of the following statement even if this splits the parameter.

Example: | Col 71 V // COMMAND 'R0 MVSA,S GTF.RLW,,,MBR=UNITTEST,SPC=(CYL,(100,100)),VLSR= // 'VOL=SER=VOL001,'',ODSN-W123456'

Continuing a comment

To continue a comment, interrupt it at any location before column 72, and code any nonblank character in column 72. After entering // and a blank on the following line, you can continue with the comment.

// COND.BILL=((20,GE),(30,LT,CHGE)) THIS STATEMENT CALLS X // THE BILLING PROCEDURE AND SPECIFIES RETURN CODE TESTS X // FOR THREE PROCEDURE STEPS.

Note

Comment continuation is very confusing, and might lead to JCL errors or the comment not being seen. It is recommended that you use several comment statements entered in sequence, because this is much easier to read.

// COND.BILL=((20,GE),(30,LT,CHGE)) //********************************************************************* //* THIS STATEMENT CALLS THE BILLING PROCEDURE AND SPECIFIES RETURN //* CODE TESTS FOR THREE PROCEDURE STEPS. //*********************************************************************

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-26. Three major types of JCL statements ES1011.0

Notes:

Every job must contain at least a JOB and an EXEC statement. A DD statement is optional.

//... JOB ... The JOB statement marks the beginning of a job and assigns a name to the job. The JOB statement is also used to provide administrative information, such as security, accounting, and identification information.

//... EXEC ... The execute (EXEC) statement indicates the beginning of a job step. It assigns a name to the step and identifies the program or procedure to be executed. The EXEC statement can contain program or procedure parameters to customize the way the program executes.

//... DD ... A data definition (DD) statement defines and describes the input and output data to be used in a job step. The DD statement can be used to allocate an existing data set, to create a new data set, to define a temporary data set, or to specify output characteristics.


Three major types of JCL statements•//... JOB ...

•//... EXEC ...

•//... DD ...

•...

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-27. The JOB statement ES1011.0

Notes:

Use the JOB statement to mark the beginning of a job and to tell the system how to process the job. Also, when jobs are stacked in the input stream, the JOB statement marks the end of the preceding job.

jobname The job name must be a unique 1-8 character long identifier of the job. The name must start in column 3 with an either alphabetic or national character (¢, #, @). All following characters can be alphanumeric or national.

JOB The operation field of a JOB statement consists of the characters JOB and must be preceded and followed by at least one blank. It can begin in any column.


//jobname JOB pos-parms [,keyw-parms]

Positional parameter:Accounting information Programmer's name

Keyword parameter:CLASS

COND

MSGCLASS

MSGLEVEL

NOTIFY

PASSWORD

PRTY

REGION

RESTART

SCHENV

USER

And so on

The JOB statement

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Positional parameter A JOB statement can contain the following two positional parameters:

Accounting information

Contains an account number and other accounting information as required by the installation.

Programmer's name

Identifies the owner of the job.

They must precede all keyword parameters. You must code the accounting parameter first, followed by the programmer's name parameter.

Keyword parameter A JOB statement can contain the following keyword parameters. You can code any of the keyword parameters in any order in the parameter field after the positional parameters.

CLASS Specifies the job class to which the job is to be assigned.

COND Determines whether a job will continue processing based on return code tests.

MSGCLASS Specifies the output class assigned to the job's log.

MSGLEVEL Specifies the information to be printed in the job log.

NOTIFY Requests notification of the specified user when the job completes.

PASSWORD Specifies the current or new RACF password.

PRTY Assigns the job's queue selection priority.

REGION Specifies the amount of storage required by the job

RESTART Allows a job to be restarted at the beginning of a job step or at a checkpoint.

SCHENV Identifies the Workload Manager (WLM) scheduling environment associated with a job. This is JES2 only in a non-APPC scheduling environment.

USER Identification of the job's owner to RACF, SRM, and other system components.

Note

The parameter list is not comprehensive. Refer to the MVS JCL Reference for a complete list of parameters.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-28. Examples of JOB statements ES1011.0

Notes:

Here we see several examples of the use of the JOB statement.


//TSOFS20X JOB 1249,SMITH,CLASS=M,MSGCLASS=Q,// NOTIFY=ATSOFS20

//TSOFS33X JOB 3ES10G000012,CLASS=A,MSGLEVEL=(1,1),// NOTIFY=TSOFS33,MSGCLASS=V

//EXMP1 JOB ,HUGO,MSGCLASS=F,MSGLEVEL=(2,0)

//JOB1 JOB 1511,BYRD,CLASS=T,MSGCLASS=A,// MSGLEVEL=(2,0),NOTIFY=BYRD,// PASSWORD=ABCDE

//WORK JOB ,PORTER,RESTART=(PROCESS,CHKPT3)

Examples of JOB statements

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-29. The EXEC statement ES1011.0

Notes:

Use the execute (EXEC) statement to identify the program or cataloged or in-stream procedure that this job step is to execute and to tell the system how to process the job step.

The EXEC statement marks the beginning of each step in a job or a procedure. A job can have up to 255 job steps, including all steps in any procedures the EXEC statements call.

stepname A step name is generally optional. It is required only when later JCL statements refer to it, the EXEC statement is used to override or add parameters of procedures, and so forth.

If coded, the step name must be a unique 1-8 character long identifier of the step within the job. The name must start in column 3 with either an alphabetic or national character (¢, #, @). All following characters can be alphanumeric or national.

EXEC The operation field consists of the characters EXEC and must be preceded and followed by at least one blank. It can begin in any column after column 3.


Positional parameter:PGM

procedure-name | PROC

Keyword parameter:ACCT

COND

PARM

REGION

TIME

And so forth

//stepname EXEC pos-parms [,keyw-parms]

The EXEC statement

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Positional parameter An EXEC statement must contain one of the following positional parameters:

PGM Names the program to be executed.

PROC | procedure_name

Names the procedure to be executed.

These positional parameters must precede all keyword parameters.

Keyword parameter An EXEC statement can contain the following keyword parameters. You can code any of the keyword parameters in any order in the parameter field after the positional parameters.

ACCT Specifies accounting information for the step.

COND Specifies that return code testing is to take place to determine whether the step is to be executed or not.

PARM Passes variable information to the executed program.

REGION Defines the amount of space required by the step.

Note

The parameter list is not comprehensive. Refer to the MVS JCL Reference for a complete list of parameters.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-30. Examples of EXEC statements ES1011.0

Notes:

Here we see several examples of the use of the EXEC statement.


//STEP2 EXEC PGM=DFSORT,ACCT=(SALES)

//STEP5 EXEC JP5,COND=(4,GT,STEP4)

//TESTA EXEC PLIXCLG,PARM.PLI='NOOBJ',

// PARM.LKED='LIST,LET,NODECK'

//STP13 EXEC PGM=PAYROLL,TIME=(12,15),

// REGION=0M

Examples of EXEC statements

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-31. The DD statement ES1011.0

Notes:

Use the data definition (DD) statement to describe a data set (existing or new) and to specify the input and output resources needed for the data set. A DD statement is required for each data set. The maximum number of DD statements per job step is 3273.

ddname Each DDname should be unique within the job step. If duplicate DDnames appear in a job step, all references might be directed to the first DDname in the step.

A DDname is 1-8 character long. It starts in column 3 with an either alphabetic or national character (¢, #, @). All following characters can be alphanumeric or national.

Note: Certain DDnames such as SYSIN, SYSABEND, STEPLIB, and so forth, are reserved for specific purposes.

DD The operation field consists of the characters DD and must be preceded and followed by at least one blank. It can begin in any column.


//ddname DD pos-parms[,keyw-parms]

Positional parameter:* | DATADUMMYDYNAM

Keyword parameter:DCBDDNAMEDISPDSNDSNTYPELRECLRECFMRETPDSPACESYSOUTUNITVOLUMEAnd so forth

(SMS-only)AVGRECDATACLASLIKEMGMTCLASRECORGREFDDSTORCLASAnd so forth

The DD statement

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Positional parameter A DD statement can contain only one of the following positional parameters:

* | DATA Begins an in-stream data set.

DUMMY Specifies no space allocation and disposition processing is to take place.

DYNAM (For compatibility with older system.)

These positional parameters must precede all keyword parameters.

Keyword parameter A DD statement can contain the following keyword parameters. You can code any of the keyword parameters in any order in the parameter field after the positional parameters.

DCB Specifies the information for the data control block, for example, record length, record format, block size, and so on.

DDNAME Names the DDname under which a resource is to be allocated.

DISP Describes the status of a data set and specifies the actions to be taken after normal or abnormal termination of the job step.

DSN The name of the data set to be allocated.

DSNTYPE Tells the system what type of data set is to be allocated.

LRECL Specifies the length of the records in the data set.

RECFM Defines the format and characteristics of the records in a data set, for example, whether they are fixed or variable in length and so on.

RETPD Specifies the number of days that the data set is to be kept.

SPACE Requests space for a new data set.

SYSOUT Allocates an output class.

UNIT Requests allocation to a specific device, type or group of devices.

VOLUME Names the volumes on which a data set resides or will reside.

Use the following parameters with SMS only. If SMS is not installed or is not active, the system syntax checks and then ignores any of these parameters.

AVGREC Specifies the quantity of primary and secondary space on the SPACE parameter.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

DATACLAS Names the data class to be used for the allocation of a new data set.

LIKE Specifies, that a new data set is to be allocated with the same attributes as the specified model data set.

MGMTCLAS Names the management class for a new data set.

RECORG Specifies whether a VSAM data set is a key-sequenced data set (KSDS), entry-sequenced data set (ESDS), relative record data set (RRDS), or linear data set (LDS).

REFDD Specifies the attributes of a new data set by referring to a previous DD statement.

STORCLAS Specifies the storage class for a new data set.

Note

This parameter list is not comprehensive. Refer to the MVS JCL Reference for a complete list of parameters.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-32. Examples of DD statements (1 of 2) ES1011.0

Notes:

Here we see several examples of the use of the DD statement.


//INPUT DD DSN=T0.TEST.DATA,DISP=OLD

//DCBINFO DD DSN=TSOFS20.TEST.RESULTS,// DISP=(NEW,CATLG), // UNIT=SYSDA,SPACE=(TRK,(1,1)),// LRECL=80,RECFM=FB,BLKSIZE=0

//EXPDT DD DSN=TSOFS20.BACKUP.COPY,// DISP=(NEW,CATLG),// DATACLAS=DCLAS02,// LRECL=256,EXPDT=2002/180

//LIKE DD DSN=TSOFS20.LIKE.TEST.RESULTS,// DISP=(NEW,DELETE,DELETE),// LIKE=TSOFS20.TEST.RESULTS, // SPACE=(4096,(10,2)),AVGREC=K

Examples of DD statements (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-33. Examples of DD statements (2 of 2) ES1011.0

Notes:

Several more examples of the use of the DD statement.


//CONCAT DD DSN=TSOFS20.TEST.LIB1,DISP=SHR

// DD DSN=TSOFS20.TEST.LIB2,DISP=SHR

//NULLIFY DD DUMMY

//SPOOL DD SYSOUT=T

Examples of DD statements (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-34. In-stream data (1 of 2) ES1011.0

Notes:

DD statements offer you the possibility to supply a job's input data within the job stream. This kind of data is referred to as in-stream data. A DD statement that contains in-stream data uses * or DATA as a positional parameter to indicate the beginning of an in-stream data set. The data records immediately follow the DD * or DD DATA statement.

When DD * is coded, the end of the data records is marked by:

• /* in the input data

• // at the beginning of another JCL statement

• End of data

• Any two-character delimiter defined by the DLM parameter on this DD statement. Usually only used for DD DATA.


000100 //MYJOB JOB...

000200 //STEP1 EXEC PGM=ANYPGM

000300 //OUTPUT DD DSN=...

000400 //INPUT DD *

000500 xxxxxybbb1123

000600 ABC something

000700 123 456 789

000800 /*

000900 // on next statement

In-stream data

Indicates begin of in-stream data

Explicit delimiter of in-stream dataImplicit delimiter of in-stream data

In-stream data (1 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-35. In-stream data (2 of 2) ES1011.0

Notes:

When DD DATA is coded, the end of the data records is marked by:

• /* in the input data

• End of data

• Any two-character delimiter defined by the DLM parameter on this DD statement.

As noted, when you use the DD DATA statement a // does not mark the end of data. This enables you to have JCL statements in your data stream. If you require /* in columns 1 and 2 of your input, you cannot use the first option.


000100 //MYJOB JOB... 000200 //STEP1 EXEC PGM=ANYPGM000300 //OUTPUT DD DSN=... 000400 //INPUT DD DATA000500 xxxxxybbb1123000600 //ABC DD something000700 //* Comment000800 /*000900

In-stream Data

Indicates begin of in-stream data that contains // in columns 1 and 2

Explicit delimiter of in-stream data

000100 //MYJOB JOB... 000200 //STEP1 EXEC PGM=ANYPGM000300 //OUTPUT DD DSN=... 000400 //INPUT DD DATA,DLM=$$000500 xxxxxybbb1123000600 /*000700 //ABC DD something000800 $$000900

In-stream Data

Indicates begin of in-stream data that contains // and /* in columns 1 and 2

Selected delimiter of in-stream data

In-stream data (2 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-36. IF/THEN/ELSE/ENDIF statements ES1011.0

Notes:

The IF/THEN/ELSE/ENDIF statement is used to specify the conditions for a job step's execution. If these conditions are not met, the job step is not executed. The THEN clause specifies the job steps to be processed when the conditions in the IF clause are met. If they are not met, then the specifications on the ELSE clause apply.

Up to 15 levels of IF/THEN/ELSE/ENDIF statement nesting are supported, that is, an IF/THEN/ELSE/ENDIF statement might contain another IF/THEN/ELSE/ENDIF statement and so on. Names and comments are optional on IF/THEN/ELSE/ENDIF statements. If no names are used, leave column 3 blank. An IF/THEN/ELSE/ENDIF statement can be used at any position within a job following the JOB statement.


//name IF (expression) THEN [comment]

JCL Statement(s)

//name ELSE [comment]

JCL Statement(s)

//name ENDIF [comment]

IF/THEN/ELSE/ENDIF statements

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-37. Keywords, operators of IF/THEN/ELSE/ENDIF ES1011.0

Notes:

Keywords RC Indicates a return code. ABEND Indicates an abend condition occurred. ¬ABEND Indicates no abend condition occurred. ABENDCC Indicates a system or user completion code. RUN Indicates the specified step started execution. ¬RUN Indicates the specified step did not start execution.

Comparison operators Comparison operators are used to compare the value behind a keyword with another numeric value, for example:

IF RC GT 12 THEN ... NOT operators Negates the expression that follows it, for example,

IF RC ¬=4 THEN In this case, the expression is true if RC does not equal 4.

Logical operators Logical operators are used to combine two or more expressions to a single logical expression, for example,

IF RC GT 4 AND RC LT 12 THEN...


Comparison operatorsGT | > LT | <NG | >NL | <EQ | =NE | =GE | >=LE | <=

Logical operatorsAND | &OR | |

Greater than

Less than

Not greater than

Not less than

Equals

Not equals

Greater than or equal to

Less than or equal to

KeywordsRC

ABEND

ABEND

ABENDCC

RUN

RUN

NOT operatorNOT |

Keywords, operators of IF/THEN/ELSE/ENDIF

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-38. IF/THEN/ELSE/ENDIF example ES1011.0

Notes:

Q1. Check off the steps that run if Step S1 returns a 0000 COND CODE (return code).

( ) Step S2 ( ) Step S3 ( ) Step S4

Q2. Check off the steps that run if step S1 returns a 0000 COND CODE and step S2 returns a 0004 COND CODE.

( ) Step S3 ( ) Step S4

Q3. Check off the steps that run if step S1 returns a 0004 COND CODE and step S2 returns a 0000 COND CODE.

( ) Step S3 ( ) Step S4


//S1 EXEC PGM=MERGE

//TEST1 IF S1.RC=0 THEN [comment]

//S2 EXEC PGM=PROCESS

//TEST2 IF S2.RC<=8 THEN [comment]

//S3 EXEC PGM=PRINT

//TEST2 ELSE [comment]

//S4 EXEC PGM=CLEANUP

//TEST2 ENDIF [comment]

//TEST1 ENDIF [comment]

IF/THEN/ELSE/ENDIF example

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Describe the basic rules for coding JCL• Code JOB/EXEC/DD statements

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

5.3. The Outlist Utility and SDSF

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-40. The Outlist Utility and SDSF ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Submit a job and display its output

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-42. The Outlist Utility and SDSF ES1011.0

Notes:

To submit a job, you can either use the TSO/E command SUBMIT, as introduced in the previous unit, or the ISPF/PDF primary command SUBMIT.

To submit a job using the TSO/E SUBMIT command, enter submit followed by the data set and member name on any command line or in basic TSO/E line mode. (Do not forget to prefix the command with TSO.)

To use the ISPF/PDF primary command SUBMIT just enter submit on the command line while editing the data set or member containing the JCL.

Note

SUBMIT can be abbreviated to SUB.


ISPF/PDF editorFile Edit Confirm Menu Utilities Compilers Test Help

Command ===> submit Scroll ===> PAGEEDIT TSOFS20.TSOE.CNTL(AMS2) - 01.00 ****** *************************** Top of Data ***************************000001 //TSOFS20A JOB 3ES10G10000012, 000002 // CLASS=A, 000003 // MSGLEVEL=(1,1), 000004 // NOTIFY=TSOFS20, 000005 // MSGCLASS=Q000006 //STEP1 EXEC PGM=IDCAMS000007 //SYSPRINT DD SYSOUT=*000008 //SYSIN DD *000009 DELETE TSOFS20.RRDS PURGE

F1=HELP F2=SPLIT F3=END F4=RETURN F5=IFIND F6=BOOKF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


READY

submit 'tsofs20.tsoe.cntl(iefbr14)'JOB TSOFS20A(JOB04970) SUBMITTED READY

TSO command lineSubmit a job

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-43. ISPF/PDF option 3.8: Outlist Utility ES1011.0

Notes:

The ISPF/PDF option 3.8, the Outlist Utility, allows you to browse, print, delete, or requeue job output that is in a held SYSOUT queue. When you select the Outlist Utility, ISPF/PDF displays the panel above. To display a job's held output, enter at least its job name and, if two or more jobs of the same job name exist, its jobID. You can also enter a job class in addition to the job name to identify the job whose output is to be displayed.

Note

The specification of a job name is required for all Outlist Utility options except option L.


Menu Utilities HelpOption ===>________________________________________________________________

Outlist Utility

L List job names/id(s) via the TSO STATUS commandD Delete job output from SYSOUT hold queueP Print job output and delete from SYSOUT hold queueR Requeue job output to a new output class

blank Display job output

For Job to be selected:Jobname . . Class . . . JobID . . .

For Job to be requeued:New Output class . .

For Job to be printed:Printer Carriage Control . . (A for ANSI )

(M for machine )(Blank for none)


ISPF/PDF option 3.8: Outlist Utility

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-44. Displaying job names and job IDs ES1011.0

Notes:

If two or more jobs of the same job name exist, the specification of a job name is no longer sufficient to uniquely identify the job output to be displayed. Upon submission of a job, each job assigned is a unique jobID. This jobID has to be supplied by the user in case of multiple jobs with the same name.

To display the jobIDs for the job submitted under the same name, enter option L on the Outlist Utility panel. You can also specify a job name. If you leave the job name blank or if the job name is your user ID plus one identifying character, the status is listed for all jobs having job names consisting of your user ID and an additional character. In case you specify a job name, the status for that exact job is displayed.

Once the list of jobs is displayed, find out the jobID of the job you want to work with and enter its ID in addition to its name and the desired panel selection on the Outlist Utility panel.


JOB TSOFS20A(JOB07025) ON OUTPUT QUEUE JOB TSOFS20A(JOB07033) ON OUTPUT QUEUE ***

Listing the job names

Outlist utilityMenu Utilities Help

Option ===> L________________________________________________________________Outlist Utility

L List job names/id(s) via the TSO STATUS commandD Delete job output from SYSOUT hold queueP Print job output and delete from SYSOUT hold queueR Requeue job output to a new output class

blank Display job output

For Job to be selected:


Displaying job names and job IDs

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-45. Display job output with PDF option 3.8 ES1011.0

Notes:

To display a job's output using the Outlist Utility, supply its name on the Outlist Utility panel. If the job name is not unique, also enter the proper jobID, but do not enter any selection on the option input line. ISPF/PDF displays the output of the job that you specified in Browse mode.

To return to the Outlist Utility panel, enter END or RETURN. If you want to delete the job output, select panel option D.


Menu Utilities Compilers Help Command ===> Scroll ===> PAGEBROWSE TSOFS20.SPF105.OUTLIST Line 00000000 Col 001 080********************************* Top of Data **********************************1 J E S 2 J O B L O G -- S Y S T E M S Y S 1 -- N O D 0 19:02:37 JOB07033 ---- TUESDAY, 06 NOVEMBER 2008 ----19.02.37 JOB07033 IRR010I USERID TSOFS20 IS ASSIGNED TO THIS JOB. 19.02.37 JOB07033 ICH70001I TSOFS20 LAST ACCESS AT 18:57:21 ON TUESDAY, MAY 619.02.37 JOB07033 $HASP373 TSOFS20A STARTED - INIT 5 - CLASS B - SYS SYS1 19.02.37 JOB07033 IEF403I TSOFS20A - STARTED - TIME=19.02.37 19.02.38 JOB07033 - --TIMINGS (MINS.)-19.02.38 JOB07033 -JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOC19.02.38 JOB07033 -TSOFS20A STEP1 00 19 .00 .00 .19.02.38 JOB07033 IEF404I TSOSF20A - ENDED - TIME=19.02.38 19.02.38 JOB07033 -TSOFS20A ENDED. NAME-TSOFS20 TOTAL CPU TIME= 19.02.38 JOB07033 $HASP395 TSOFS20A ENDED0------ JES2 JOB STATISTICS ------- 06 NOVEMBER 2000 JOB EXECUTION DATE- 14 CARDS READ- 50 SYSOUT PRINT RECORDS- 0 SYSOUT PUNCH RECORDS- 3 SYSOUT SPOOL KBYTES- 0.01 MINUTES EXECUTION TIME

1 //TSOFS20A JOB (5820),‘TSOFS20',MSGCLASS=X,MSGLEVEL=(1,1),// NOTIFY=TSOFS20,CLASS=B,REGION=6M//* SUBMITTED BY AUES100 AT 19:02:36 ON 00.126 FROM CVCPG010 ON SYS1//********************************************************************//* JOB SUBMITTED FROM TSOFS20.ES10.CNTL(LAB5#21) ***

F1=HELP F2=SPLIT F3=END F4=RETURN F5=IFIND F6=BOOK F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Display job output with PDF option 3.8

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-46. System Display and Search Facility ES1011.0

Notes:

The System Display and Search Facility (SDSF) lets you control job processing (hold, release, cancel, purge), monitor job execution, display job output, control printers and initiators, check network lines, work with spools, issue JES2 and z/OS commands, and so forth.

To work with SDSF, select option SD from the ISPF Primary Option Menu. This results in the display of the SDSF Primary Option Menu, as shown above.

To browse a job's output, choose option H. This selection displays a list of all jobs in the JES2 held output queue.

The next chart shows an example of such a list.


Display Filter View Print Options Help------------------------------------------------------------------------------------------------------ SDSF PRIMARY OPTION MENU ------------------------COMMAND INPUT ===> SCROLL ===> PAGE Type an option or command and press Enter.

LOG - Display the system logDA - Display active users in the sysplexI - Display jobs in the JES2 input queueO - Display jobs in the JES2 output queueH - Display jobs in the JES2 held output queueST - Display status of jobs in the JES2 queuesPR - Display JES2 printers on this systemINIT - Display JES2 initiators on this systemMAS - Display JES2 members in the MASLINE - Display JES2 lines on this systemNODE - Display JES2 nodes on this systemSO - Display JES2 spool offload for this systemULOG - Display user session log

TUTOR - Short course on SDSF (ISPF only)END - Exit SDSF


System Display and Search Facility

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-47. Display the JES2 held output queue with SDSF ES1011.0

Notes:

Now, with all the jobs in the JES2 held output queue on display, you can select from a number of actions to be performed on the job's held output, including the following:

A Release a job's output.

C Purge a job's output.

H Hold a job's output.

L List a job's output in the log.

O Release output for printing.

P Purge a job's output.

S Display a job's held output.

X Print output data sets.

Enter S as an action character in the NP column of your selected job while the list of held output for all jobs is displayed.


Display the JES2 held output queue with SDSFDisplay Filter View Print Options Help

-------------------------------------------------------------------------------SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 403 LINE 1-3 (3) NP JOBNAME JOBID OWNER PRTY C ODISP DEST TOT-REC TOT-

TSOFS20A JOB07025 TSOFS20 128 X HOLD LOCAL 45 TSOFS20A JOB07033 TSOFS20 128 X HOLD LOCAL 68 TSOFS20 TSU07032 TSOFS20 128 T HOLD LOCAL 290

COMMAND INPUT ===> SCROLL ===> PAGEF1=HELP F2=SPLIT F3=END F4=RETURN F5=IFIND F6=BOOKF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Note

To browse all jobs output using SDSF, select the Option O (Display jobs in the JES2 output queue) from the SDSF PRIMARY OPTION MENU. This displays the JES2 output queue instead of the JES2 held output queue.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-48. Display job’s held output with SDSF ES1011.0

Notes:

To browse a job's held output using SDSF, select (Display jobs in the JES2 held output queue) from the SDSF Primary Option Menu and then enter an S as an action character. When you place an S in our selected job's NP column, SDSF displays the job's held output. To return to the previous panel, enter END.

Note

To delete a job's output, enter the P action character in a job's NP column or prefix area.


SDSF OUTPUT DISPLAY DEES10ZA JOB07025 DSID 2 LINE 0 COLUMNS 02- 81COMMAND INPUT ===> SCROLL ===> PAGE********************************* TOP OF DATA **********************************

J E S 2 J O B L O G -- S Y S T E M S Y S 1 -- N O D E17:27:56 JOB07025 ---- TUESDAY, 06 NOVEMBER 2008 ----17.27.56 JOB07025 IRR010I USERID AUES100 IS ASSIGNED TO THIS JOB.17.27.56 JOB07025 ICH70001I TSOFS20 LAST ACCESS AT 14:33:48 ON TUESDAY, NOVEMBE17.27.56 JOB07025 $HASP373 TSOFS20A STARTED - INIT 5 - CLASS B - SYS SYS1 17.27.56 JOB07025 IEF403I TSOFS20A - STARTED - TIME=17.27.56 17.27.57 JOB07025 - --TIMINGS (MINS.)--17.27.57 JOB07025 -JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK17.27.57 JOB07025 -TSOFS20A STEP1 FLUSH 0 .00 .00 .017.27.57 JOB07025 IEF453I TSOFS20A - JOB FAILED - JCL ERROR - TIME=17.27.57 17.27.57 JOB07025 -TSOF0A ENDED. NAME-AUES100 TOTAL CPU TIME= 17.27.57 JOB07025 $HASP395 TSOFS20A ENDED ------ JES2 JOB STATISTICS ------06 NOVEMBER 2000 JOB EXECUTION DATE

14 CARDS READ27 SYSOUT PRINT RECORDS0 SYSOUT PUNCH RECORDS2 SYSOUT SPOOL KBYTES

0.00 MINUTES EXECUTION TIME1 //TSOFS20A JOB (5820),‘TSOFS20',MSGCLASS=X,MSGLEVEL=(1,1),// NOTIFY=TSOFS20,CLASS=B,REGION=6M//* SUBMITTED BY TSOFS20 AT 17:27:56 ON 00.126 FROM CVCPG089 ON SYS1 //********************************************************************//* JOB SUBMITTED FROM AUES100.ES10.CNTL(LAB5#21) ***//* DOC: ALLOCATE TSOFS20.ES10.PROC AND COPY ENTIRE DATA SET ***//* TSOFS20.ES10.PROC. ***


Display job’s held output with SDSF

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Submit a job and display its output

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on on to TSO.2. Allocate a PDS and copy

a member in.3. Edit the member and

then submit it.4. Examine the job's output

using SDSF.5. Optional: Examine the

job’s output using Outlist.6. Delete as required.7. Log off.

Exercise

Submit a job

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

5.4. JCL Utility overview

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-51. JCL Utility overview ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Define the term utility• Name and explain the different kinds of utilities• Describe the function and use of the following utilities:

– IEFBR14

– IEBCOPY

– IEBGENER

– IDCAMS


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-53. JCL Utility overview ES1011.0

Notes:

A utility can be understood as a program that performs one or more functions useful for the operation, organization and maintenance of a system. One distinguishes three types of utility programs:

System utility programs System utility programs are used to list or change information related to data sets and volumes, such as data set names, catalog entries, and volume labels.

IEHINITT Write standard labels on tape volumes. IEHLIST Lists all kinds of control data. IEHMOVE Moves and copies collections of data. IEHPROGM Builds and maintains system control data. IFHSTATR Selects, formats, and writes information about tape errors from

the IFASMFDP tape. IDCAMS Defines VSAM data sets, deletes all data sets and performs a

vast array of functions for both data set and volume maintenance as well as hardware management functions for advanced devices.


System utility programs:

IEHINITT

IEHLIST

IEHMOVE

IEHPROGM

IFHSTATR

IDCAMS

Data set utility programs:IEBCOMPR

IEBCOPY

IEBDG

IEBEDIT

IEBGENER

IEBIMAGE

IEBPTPCH

IEBUPDTE

z/OS feature: Licensed program

DFSORT

JCL Utility overviewTypes of utilities

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Data Set Utility Programs You can use data set utility programs to reorganize, change, or compare data at the data set or record level. These utilities allow you to manipulate partitioned, sequential, or indexed sequential data sets or partitioned data sets extended (PDSEs), which are provided as input to the programs. You can manipulate data ranging from fields within a logical record to entire data sets.

IEBCOMPR Compares records in sequential or partitioned data sets, or PDSEs.

IEBCOPY Copies, compresses, or merges partitioned data sets or PDSEs; selects or excludes specified members in a copy operation; renames or replaces selected members of partitioned data sets or PDSEs.

IEBDG Creates a test data set consisting of patterned data. IEBEDIT Selectively copies job steps and their associated JOB

statements. IEBGENER Copies records from a sequential data set or converts a data

set from sequential to partitioned. IEBIMAGE Modifies, prints, or links modules for use with the IBM 3800

Printing Subsystem, the IBM 3262 Model 5, or the 4248 printer IEBISAM Unloads, loads, copies, or prints an ISAM data set. IEBPTPCH Prints or punches records in a sequential or partitioned data

set. IEBUPDTE Incorporates changes to sequential or partitioned data sets or

PDSEs. zOS Feature - Licensed Program

Data Facility Sort (DFSORT) is a member of the IBM Data Facility family of products. It is a high-performance data arranger.

DFSORT With DFSORT, you can sort, merge, and copy data sets. You can use DFSORT to do simple tasks such as alphabetizing a list of names, or you can use it to aid complex tasks such as taking inventory or running a billing system. You can also use the DFSORT record-level editing capability to perform data management tasks.

Most utility programs have been available for a long time, and therefore some of the utility program functions are nowadays better performed by newer applications. The main reason why IBM continues to ship these utility programs is to provide compatibility with systems running previous versions of the operating system.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-54. IEFBR14 ES1011.0

Notes:

IEFBR14 is a dummy program that does not perform any real function. It consists of two program statements. The first clears register 15, which passes a return code of 0. The second branches to the address in register 14, which returns control to the system. If a step requests IEFBR14, the system does the following:

• Checks all the job control statements in the step for syntax. • Allocates direct access space for data sets. • Performs data set disposition processing.

To test with IEFBR14, substitute IEFBR14 for the name of the program the JCL actually supports, as follows:

//stepname EXEC PGM=IEFBR14,...

Even though IEFBR14 does not serve any real function, it allows JCL statements to be grouped in job steps. Its typical use is the allocation and deletion of data sets required for following job steps.


Address spaces

....

Initiator

IEFBR14 CSECTSR R15,R15BR R14

Registers... 14 15 ...

... ...

Clears register 15returns RC=0

Branches to addressin register 14

IEFBR14

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-55. Common utility DDnames ES1011.0

Notes:

Most utilities require the use of the DDnames SYSUT1, SYSUT2, SYSIN, and SYSPRINT to define their input and output and to pass control information to the executed program.

SYSUT1 Specifies the input source for the program, which is usually a sequential data set, a PDS or PDSE, or a member of a PDS or PDSE.

SYSUT2 Defines where the output of the program is to be stored. SYSUT2 usually specifies a sequential data set, a member of a PDS or PDSE, or a PDS or PDSE as the target for the performed function.

SYSIN Specifies the control data, which is usually supplied with the input stream or specifies DUMMY.

SYSPRINT Defines a sequential data set for messages. The data set can be written to a system output device, a tape volume, or a DASD volume.


//SYSUT2 DD ...

//SYSPRINT DD

PGM=IEBCOPYIEBGENER

//SYSUT1 DD ...

//SYSIN DD *

Common utility DDnames

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Here is an example:

//PRINT JOB... //STEP1 EXEC PGM=IEBGENER //SYSUT1 DD DSNAME=AUES100.IN.DATA,DISP=SHR //SYSUT2 DD DSNAME=AUES100.OUT.DATA,DISP=OLD //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //...

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-56. IEBCOPY ES1011.0

Notes:

IEBCOPY is a data set utility for the management of partitioned data sets. It allows you to:

• Make a copy of a partitioned data set or PDSE.

• Merge partitioned data sets.

• Unload (back up) and load (restore) a partitioned data set or PDSE.

• Select or exclude specific members of a partitioned data set or PDSE when copying, merging, loading, or unloading.

• Replace members of a partitioned data set or PDSE.

• Rename selected members of a partitioned data set or PDSE.

• Compress a partitioned data set in place.

• Convert a partitioned data set to a PDSE or a PDSE to a partitioned data set.

• And so forth


IEBCOPY

PDS PDS

PDSE PDSE

PDS PDSE

PDSPDSE PDSU

PDSPDSEPDS

PDSE

PDS

Copy

Copy

Convert

Load/unload

Merge

Compress

IEBCOPY

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-57. Copying using IEBCOPY ES1011.0

Notes:

Copying data sets

IEBCOPY can be used to create a complete or partial copy of a partitioned data set. The data set can be copied to the same volume (under a different name) or to another volume. Members copied into a partitioned data set are not physically reordered; members are copied in the physical order in which they occur in the original data set.

IEBCOPY job control statements

The JCL specific to the IEBCOPY utility program is as follows:

• input/output DD - defines input/output partitioned datasets

• SYSUT3 and SYSUT4 DD - can be used to define a spill (work area) utility dataset on a direct access device if needed.

• SYSIN DD - defines the control dataset which normally resides in the input stream.

Utility control statements

IEBCOPY uses three control statements:


PDS orPDSE

PDS orPDSE

Copy

Unload Load

PDSU

Copying using IEBCOPY

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

• COPY - Specifies output and input DD names that correspond to the partitioned datasets to be copied to and from respectively.

• SELECT - Specifies the members to be selected from the input partitioned dataset(s) and to be copied into an output PDS. This statement is also used to rename and/or replace selected members in the output PDS.

• EXCLUDE - Specifies members to be excluded from the copy step.

Most of the utility control statements mentioned have several parameters which can be specified. Some of the parameters are mandatory while others are optional.

Here is an example of how to copy an entire data set:

//DSCOPY JOB ... //STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSNAME=AUES100.IN.DATA,UNIT=3390,VOL=SER=USER05, // DISP=SHR //SYSUT2 DD DSNAME=AUES100.OUT.DATA,UNIT=3390,VOL=SER=USER12, // DISP=(NEW,KEEP),SPACE=(TRK,(3,1,2)) /*

Note

Because the input and output data sets are identified as SYSUT1 and SYSUT2, SYSIN is not required.

To copy only selected members, add the following SYSIN statement:

//SYSIN DD * COPYMEM COPY OUTDD=SYSUT2 INDD=SYSUT1 SELECT MEMBER=(member1,member2,...)

Unloading and loading data sets

IEBCOPY can be used to create a backup copy of a partitioned data set by copying (unloading) it to a sequential data set on DASD, tape, or other device supported by QSAM. The generated sequential data set is referred to as PDS unloaded (PDSU).

IEBCOPY creates an unload data set when you specify physical sequential organization (DSORG=PS) for the output data set. (To create a partitioned data set, specify DSORG=PO and DSNTYPE=PDS or DSNTYPE=LIBRARY.)

Multiple data sets cannot be unloaded in one operation or to one sequential data set. Each data set unload requires its own step and target data set.

IEBCOPY can copy a PDSU to a PDSU directly without the need to reload it to a PDS and then unload the PDS to create the new PDSU.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Example of a data set unload:

//UNLOAD JOB ... //STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //INDS DD DSNAME=AUES100.TEST.DATA,UNIT=disk,VOL=SER=USER10, // DISP=OLD //OUTDS DD DSNAME=AUES100.SAVE.DATA,UNIT=tape,VOL=SER=TAPE03, // DISP=(NEW,KEEP),LABEL=(,SL) //SYSIN DD * COPY OUTDD=OUTDS,INDD=INDS /*

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-58. Renaming and replacing data set members with IEBCOPY ES1011.0

Notes:

IEBCOPY examples

In the following examples, replace infile and outfile with any unique input and output DD names, and replace inpds with the name of the PDS to be copied and outpds with the name of the output PDS.

To copy only particular members of one PDS to be new members of another PDS, where mbr1, mbr2,..., mbrn are the names of the members to be copied:

// EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=A//infile DD DSN=inpds,DISP=SHR//outfile DD DSN=outpds,DISP=SHR//SYSIN DD *COPY OUTDD=outfile,INDD=infileSELECT MEMBER=(mbr1,mbr2,...,mbrn)/*


Renaming and replacing data set members with IEBCOPY

//ATSOFS20A JOB ...

//S1 EXEC PGM=IEBCOPY

//SYSPRINT DD SYSOUT=*

//IN DD DSN…

//OUT DD DSN…

//SYSIN DD *

COPY OUTDD=OUT,INDD=IN(To copy and rename a member)

SELECT MEMBER=(member,new member name)

PDS/E member

CopyRename / replace

PDS/E member

(To copy and replace an existing member)

SELECT MEMBER=(member,R)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

To copy all members of a PDS to another PDS, replacing all duplicate-named members in the output PDS (the “R” in the INDD parameter implies that replace mode is to be used):

// EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=A//infile DD DSN=inpds,DISP=SHR//outfile DD DSN=outpds,DISP=SHR//SYSIN DD *COPY OUTDD=outfile,INDD=(infile,R)/*

Here is an example where mbri is to replace any member in the output PDS by the name of newnamei, the following control statements can be used:

COPY OUTDD=outfile,INDD=infileSELECT MEMBER=(mbr1,mbr2,...,(mbri,newnamei,R),...,mbrn)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-59. Compressing a PDS with IEBCOPY ES1011.0

Notes:

Unlike a PDSE, a partitioned data set cannot reuse the directory of deleted members unless the data set is compressed in place or the data set is copied to another data set.

The simplest way to request a compress-in-place operation is to specify the same DDname for both the OUTDD and INDD parameters of a COPY statement.

However, a compress is actually performed when both the input and output are the same data set on the same volume. For example, this job step will compress the data set AUES100.DATA:

//COMPRESS EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //A DD DSNAME=AUES100.DATA,DISP=OLD //B DD DSNAME=AUES100.DATA,DISP=OLD //SYSIN DD * COPY OUTDD=B,INDD=A


IEBCOPY

DDname A DDname B

...A B C

Directory

MemberC

MemberB

MemberA

...A B C

Directory

MemberC

MemberA

MemberB

Compressing a PDS with IEBCOPY

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

In this example, the data set allocated under DDname A is copied to the data set allocated under DDname B and they are the same data set, so B is compressed.

It is recommended that a backup copy be made of a data set prior to compressing it.

A partitioned data set can be destroyed if IEBCOPY is interrupted during processing, for example, by a power failure, abend, TSO attention, or I/O error.

Also, do not compress a partitioned data set currently being used by more than one user.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-60. IEBGENER ES1011.0

Notes:

IEBGENER is a program used to:

• Create a backup copy of a sequential data set or a member of a PDS or PDSE.

• Produce a PDS or PDSE or a member of a PDS or PDSE from a sequential data set.

• Expand an existing PDS or PDSE by creating partitioned members and merging them into the existing data set.

• Print sequential data sets or members of PDSs or PDSEs.

• Reblock or change the logical record length of a data set.

• And so forth


SEQ.DSMEMBER

Backup

IEBGENER

SEQ.DSCreate

SEQ.DSAdd MEMBER

Create/editSEQ.DSPDSPDSE

SEQ.DSMEMBER

Print

Data SetReblock/change

PDSPDSEMEMBER

PDSPDSEMEMBER

IEBGENER

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-61. Creating a backup copy with IEBGENER ES1011.0

Notes:

IEBGENER can be used to create a backup copy of a sequential data set or a member of a partitioned data set or PDSE. The sequential data set or member can be copied to any supported output device, such as tape or DASD. A data set that resides on a direct access volume can be copied to its own volume, provided that you change the name of the data set. The following is an example of a sequential data set being copied from one volume to another:

//COPYSEQ JOB ... //STEP1 EXEC PGM=IEBGENER //SYSUT1 DD DSNAME=AUES100.TESTIN.DATA,DISP=SHR //SYSUT2 DD DSNAME=AUES100.NEW.OUT,DISP=(,KEEP), // VOLUME=SER=USER10,SPACE=(TRK,(5,1,0)), // RECFM=FB,LRECL=80,BLKSIZE=3120 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY

(DUMMY is specified for SYSIN as the output is sequential and no editing is required.)


IEBGENERSequentialdata set Member ofPDS/PDSE

Creating a backup copy with IEBGENER

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-62. Deleting data sets with IDCAMS ES1011.0

Notes:

IDCAMS can be used for perform multiple functions for both data set and volume maintenance as well as hardware management functions for advanced devices.

In this example IDCAMS is being used to delete a data set.


//ATSOFS20A JOB ...

//S1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DELETE TSOFS20.DELETE.THIS.DATASET

DELETE TSOFS20.DELETE.THAT.DATASET

..

IDCAMSControlstatements

Deleting data sets with IDCAMS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-63. DFSORT ES1011.0

Notes:

A data set contains the information that you want to sort, merge, or copy. For most processing done by DFSORT, the whole data set is affected. Data sets can be cataloged, which permits the data set to be referred to by name without specifying where the data set is stored. A cataloged data set should not be confused with a cataloged procedure. A cataloged procedure is a named collection of JCL stored in a data set, and a cataloged data set is a data set whose name is recorded by the system.

Sorting data sets Sorting is arranging records in either ascending or descending order within a file. To run DFSORT with the JCL EXEC statement, write a SORT control statement to describe the control fields and the order in which you want them sorted. The control statements you write are part of the input stream read by the SYSIN DD statement in the JCL.


Data sets

DFSORT

Sorted

Merged

Copied

DFSORT

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

SORT FIELDS=(110,5,CH,A) | | | |______Sort Order = Ascending | | |________Data Type = Character | |___________Column count |______________Start Column

To sort the records in descending order, specify D instead of A.

Records can be sorted by specifying multiple control fields. When you specify two or more control fields, you specify them in the order of greater to lesser priority.

SORT FIELDS=(110,5,CH,A,115,6,CH,A,1,40,CH,A) | | |_________Lowest priority | |___________________Second priority |______________________________Highest priority

DFSORT can also be called from a program. We do not cover that in this overview.

Merging data sets Generally, the reason for merging data sets is to add more records to a data set that is already sorted. To merge data sets, you write a MERGE control statement and several JCL statements. Whenever you merge data sets, you must make sure that their records have the same format and that they have been previously sorted by the same control fields. Up to 16 data sets can be merged at a time.

MERGE FIELDS=(110,5,A,1,40,A),FORMAT=CH

The format of the MERGE statement is similar to that of the SORT statement, except for the data type, which is input with FORMAT=.

Instead of the SORTIN DD statement, you use SORTINnn DD statements to define the input data sets. The SORTINnn DD statements name the input data sets and tell how many data sets are merged. You need one SORTINnn DD statement for each data set being merged. The value nn in SORTINnn is a number from 01 to 16.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Copying data sets With DFSORT, you can copy data sets directly without performing a sort or merge. You write a copy statement by specifying COPY on the SORT, MERGE, or OPTION control statement of the SYSIN DD statement.

SORT FIELDS=COPY MERGE FIELDS=COPY

OPTION COPY

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-64. DFSORT utility DDnames ES1011.0

Notes:

The DFSORT utility uses these DDnames:

SORTIN The data to be sorted.

SORTOUT The data after sorting.

SORTWKnn Work files: usually only one required; check DFSORT manual.

SYSOUT The report from the sort program.

SYSIN Control statement input.

//SORTJOB JOB ... //SORTSTEP EXEC PGM=ICEMAN //SYSOUT DD SYSOUT=* //SORTIN DD DSN=AUES100.SORT.INPUT,DISP=OLD //SORTOUT DD DSN=AUES100.SORT.OUTPUT,DISP=OLD //SYSIN DD * SORT FIELDS=...


//SORTOUT DD ...

//SYSOUT DD

PGM=DFSORT

//SORTIN DD ...

//SYSIN DD *

//SORTWK.. DD

DFSORT utility DDnames

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-65. The SORT process ES1011.0

Notes:

This shows the basic sort process using one field of 7 bytes. The subparameters indicate:

• Sort the field starting in column 1 • The sort field is 7 bytes long • Data type is character • Sort order is ascending

What would the order be if the control statement was:

SORT FIELDS=(2,6,CH,A)


BAKER

ABLE

ECHO

DELTA

CHARLIE

KILO

LIMA

INDIA

GOLF

HOTEL

FOXTROT

JULIET

ABLE

BAKER

CHARLIE

DELTA

ECHO

FOXTROT

GOLF

HOTEL

INDIA

JULIET

KILO

LIMA

SORT


The SORT process

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-66. SORT JCL example ES1011.0

Notes:

Note there is only one SORTWKnn statement. This is usually enough.


//TSOFS20A JOB ...

//S1 EXEC PGM=DFSORT

//SYSOUT DD SYSOUT=*

//SORTIN DD DSN=TSOFS20.UNSORTED.DATA,DISP=OLD

//SORTOUT DD DSN=TSOFS20.SORTED.DATA,DISP=OLD

//SORTWK01 DD SPACE=(CYL,(1,1)),UNIT=SYSDA

//SYSIN DD *


SORT JCL example

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Define the term utility• Name and explain the different kinds of utilities• Describe the function and use of the following utilities:

– IEFBR14

– IEBCOPY

– IEBGENER

– IDCAMS


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Copy a data set.3. Sort a data set.4. Log off.

Exercise

JCL exercise

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

5.5. Introduction to JCL procedures

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-69. Introduction to JCL procedures ES1011.0

Notes:








Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Work with z/OS procedures:


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-71. Introduction to JCL procedures ES1011.0

Notes:

A procedure is a set of frequently used JCL statements that have been grouped together and named so that they can be invoked via their name. Most JCL procedures perform a general function which allows them to be called from a variety of jobs.

Procedures are usually stored in system data sets, so called procedure libraries or proclibs for short. By storing procedures in system proclibs, they can be made available to a wide audience. Procedures, however, can also be stored in private procedure libraries or within a job, restricting their use to authorized users or a single job only.



JOB___________________________________

_______________________________________

PROCEDURE____________________________________

PROCEDURE_______________________PROCEDURE

_________

What is a procedure?

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-72. Types of procedures ES1011.0

Notes:

One distinguishes two types of procedures, cataloged procedures and in-stream procedures. Both types are invoked by either one of the following JCL statements:

//[stepname] EXEC PROC=procedure_name //[stepname] EXEC procedure_name

Cataloged procedure A procedure that is stored as a member of a PDS or PDSE is a cataloged procedure. The data set containing the procedure can either be a private or system data set. The system procedure library is SYS1.PROCLIB.

The name of a cataloged procedure is its member name. When calling a cataloged procedure, the calling step receives a copy of the procedure, and therefore a cataloged procedure can be used simultaneously by multiple jobs.


Other PROCLIB

......

SYS1.PROCLIB

PROC1 PROC2 PROC3

PROC4 PROC5 PROC6

PROC7 PROC8

Cataloged proceduresIn-stream procedures

JOB

PROC IPROC

In-stream Procedure

EXEC IPROC

EXEC PROC3

PEND

Types of procedures

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

PROC and PEND statements marking the start and end of a procedure are optional for cataloged procedures. If a PROC statement is coded, however, it must be the first in the procedure.

A cataloged procedure can consist of SET, EXEC, DD, OUTPUT JCL, INCLUDE, IF/THEN/ELSE/ENDIF, CNTL, ENDCNTL, and JCL comment statements. JES2 and JES3 control statements cannot be part of a cataloged procedure.

In-stream procedure In-stream procedures are procedures whose JCL statements are placed within the job executing them. The beginning of an in-stream procedure must be marked by a PROC statement, its ending by a PEND statement. In-stream procedures must be defined before they can be used, meaning the procedure definition must precede its invocation.

An in-stream procedure can consist of SET, EXEC, DD, OUTPUT JCL, INCLUDE, IF/THEN/ELSE/ENDIF, CNTL, ENDCNTL, and JCL comment statements. JES2 and JES3 control statements cannot be part of an in-stream procedure.

Note: An In-stream procedure cannot be coded within another procedure, that is, nested.

Cataloged and in-stream procedures can invoke other procedures. Up to 15 levels of nesting are allowed.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-73. Procedure usage ES1011.0

Notes:

The use of procedures has many advantages. A procedure allows a programmer to group a set of JCL statements under one name and to execute them by calling the procedure name. This way redundant coding is avoided and the job becomes more programmer-friendly as the use of procedures drastically reduces the amount of JCL statements within a job.

Since cataloged procedures are stored in private or system-wide procedure libraries, they can be made available to a greater group of users. This way, programmers have access to a great variety of procedures, making them more productive. The use of cataloged procedures also eases procedure maintenance since they can be stored and maintained at a central location. Before procedures are placed in a procedure library, they are often tested as in-stream procedures, which simplifies procedure testing.


Procedure usage

JOB1

JOB2

JOBn

...

...

PROCLIB

PROC1 PROC2 PROC3

PROC4 PROC5 PROC6

PROC7 PROC8

Cataloged procedures In-stream procedures

//TEST PROC...// PEND//... EXEC TEST...//... EXEC TEST..

....

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-74. Example of an in-stream procedure ES1011.0

Notes:

The visual shows an example of an in-stream procedure. In-stream procedures are part of the job that executes them. To distinguish the in-stream procedure's JCL statements from the other JCL statements, they are enclosed by:

//name PROC

and

// PEND

statements. //name PROC marks the beginning, and // PEND the end of an in-stream procedure.

Cataloged procedures do not require the coding of //name PROC and // PEND statements as they are stored in their own member.

If, however, a //name PROC statement is coded in a cataloged procedure, it has to be the procedure's first statement.


//TSOFS20A JOB (1234),CLASS=A,// NOTIFY=TSOFS20,MSGLASS=T,// MSGLEVEL=(1,1)//.....//INPROC PROC//STEP1 EXEC PGM=APGM//IN DD DSN=DATA.SET,DISP=SHR//......// PEND

//STEP2 EXEC INPROC

In-streamprocedure

Example of an in-stream procedure

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-75. Calling procedures ES1011.0

Notes:

When you call a procedure you can use it as is, add additional DD statements, override or nullify the procedure's EXEC and/or DD statements, or use JCL symbols to set variable values for the execution of the procedure.

All additions or alterations on a procedure's invocation are only temporary, valid only for the current job step. The actual procedure code remains unchanged.


Calling procedures• When calling a procedure you can:

– Use the procedure as is.

– Code additional DD statements.

– Override EXEC and DD statements explicitly.

– Use symbolic parameters for a temporary change of the procedure.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-76. Procedure search order ES1011.0

Notes:

To call a procedure, code the EXEC statement in either one of the following forms:

//name EXEC PROC=procname

or

//name EXEC procname

The system then retrieves the procedure using the following search order:

1. If the called procedure is an in-stream procedure, the system retrieves it from the job input stream. (Remember to place the in-stream procedure before the EXEC statement calling it.)

2. If the procedure is a cataloged procedure stored in a private procedure library, the system retrieves it from the library specified on the job's JCLLIB statement. (The JCLLIB statement has to appear before the EXEC statement.)

3. If the called procedure is cataloged in a system library, it is retrieved from SYS1.PROCLIB or other defined procedure library.


//jobname JOB...

//name PROC

.

.

// PEND

.

//step EXEC PROC=name

or

//step EXEC name

PrivateProclib(s)

SystemProclib(s)

12

3

Procedure search order

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-77. Specifying private proclibs ES1011.0

Notes:

When working with private procedure libraries, the JCLLIB statement is used to identify the names of the private data sets to be searched. Apart from specifying the names of the data sets to be searched in case of a procedure call, the JCLLIB statement also determines the order in which they are searched. The system searches private procedure libraries in the order they are entered on the JCLLIB statement prior to searching any default system procedure library.

The JCLLIB statement syntax is: //[name] JCLLIB ORDER=(library[,library]...)

Note

If a private procedure library is to be used, a JCLLIB statement must appear after the JOB statement and before the first EXEC statement in the job.

Only one JCLLIB statement is allowed per job.


...

MY.PROC1

PRC17 PRC18

PRC11 PRC12 PRC13

PRC14 PRC15 PRC16

...

MY.PROC2

PRC27 PRC28

PRC21 PRC22 PRC23

PRC24 PRC25 PRC26

//MYJOB JOB .....//MYLIB JCLLIB ORDER=(MY.PROC1,// MY.PROC2)..//STEP1 EXEC PROC=PRC23...

Specifying private proclibs

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-78. Overriding procedure statements ES1011.0

Notes:

Overriding a parameter modifies only that parameter; the system uses all other parameters on the original statement. For example, if you override the data set name on a DD statement that includes UNIT and VOL=SER parameters, the system will still use the UNIT and VOL=SER parameters. Invalid parameters in a procedure cannot be corrected through overrides. Before processing overrides, the system scans the original procedure statements for errors and issues error messages. A cataloged or in-stream procedure can be modified by:

Changing EXEC statement parameters

A keyword parameter can override a parameter or be added to all EXEC statements in the procedure, for example,

//STEPn EXEC PROC=INPROC,ACCT=5670

Note: In this example, the ACCT parameter applies to all steps in the procedure.


.

.//INPROC PROC//STEP1 EXEC PGM=APGM//IN DD DSN=TESTA.DATA,DISP=SHR..// PEND..//STEPn EXEC INPROC//STEP1.IN DD DSN=TESTB.DATA//....

Overrides

Overriding procedure statements

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

If the keyword parameter is to override the parameter or be added to only one EXEC statement in the procedure, add the name of the procedure step immediately following the keyword, for example,

//STEPn EXEC PROC=INPROC,ACCT.STEP1=5670

Note: In this example, .procstepname was added to the ACCT parameter. The ACCT=5670 will only apply to step STEP1.

Changing OUTPUT JCL and DD statements

Overriding or added statements can appear in any order when they explicitly specify the step to which they apply. If no step is specified, then they apply to the previously named step. If no step has been named previously, the changes apply to the very first step.

Example:

//STEPn EXEC INPROC //STEP1.IN DD DSN=TESTB.DATA

This kind of procedure modification is only temporary, valid only for the current execution. Invalid parameters in a procedure cannot be corrected through overrides.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-79. JCL symbols ES1011.0

Notes:

JCL symbols allow you to easily modify JCL statements in a job through the use of variables. JCL symbols are valid only for the current job. When you code JCL symbols within a job, you must define or override them every time the job runs. A JCL symbol can be set by:

PROC statements A PROC statement marks the beginning of an in-stream procedure, but can also be used in a cataloged procedure.

Use the PROC statement to define a JCL symbol's default value. If no other value is assigned, this value is used instead of a user-specified value.

Example:

//MYPROC PROC DSNAME='DEES100.DEFAULT.DATA'


Example:

000100 //MYPROC PROC DATASET=‘TSOFS20.DEFAULT.DATA’,000200 // OUTCLASS=A000300 //STEP1 EXEC PGM=PRNTDATA000400 //INPUT DD DSN=&DATASET,... 000500 //OUTPUT DD SYSOUT=&OUTCLASS000600 // PEND000700 //S1 EXEC MYPROC,000800 // DATASET=‘TSOFS20.OVERRIDE.DATA'

JCL symbols • Allow the use of predefined or variable values

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

EXEC statements calling procedures

The value assigned to the JCL symbol on the EXEC statement overrides the called procedure's default value.

Example:

//STEP1 EXEC PROC=MYPROC,DSNAME='DEES100.MY.DATASET'

SET statements Code the SET statement in the JCL before the first use of the JCL symbol. You can use the SET statement to define JCL symbols that are used on:

• JCL statements in the JCL stream

• Statements in a procedure (when neither the EXEC statement calling the procedure nor its PROC statement define JCL symbols).

Example:

//DATA SET DATASET='DEES100.DEFAULT.DATASET'

Note

A value assigned to a JCL symbol that contains special characters ( /, &, *, -, +, (, ), = ) must be enclosed in apostrophes.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-80. INCLUDE groups ES1011.0

Notes:

An INCLUDE statement specifies the name of a member of a PDS or PDSE that contains a set of JCL statements. The set of JCL statements referred to by the INCLUDE statement is called an INCLUDE group. The INCLUDE group statements replace the INCLUDE statement. The system processes the JCL statements of the INCLUDE group as part of the JCL stream.

The INCLUDE statement has the following syntax:

//[name[ INCLUDE MEMBER=name

The member storing the INCLUDE group must be part of a procedure library. The same search order as for procedures applies.

An INCLUDE statement:

• Can appear anywhere in the job after the JOB statement, with one exception: if there is a JCLLIB statement, the INCLUDE statement must follow the JCLLIB statement

• Can appear within an INCLUDE group. INCLUDE groups can contain INCLUDE statements and can be nested up to a maximum of 15 levels of nesting


//TESTJOB JOB ...//LIBSRCH JCLLIB ORDER=MY.PROC//STEP1 EXEC PGM=PRINT//OUTPUT INCLUDE MEMBER=SYSOUT2//STEP2.....

//* BEGIN OF INCLUDE GROUP//SYSOUT2 DD SYSOUT=A//OUT1 OUTPUT DEST=POK,COPIES=3//OUT2 OUTPUT DEST=KINGSTON,// COPIES=10//OUT3 OUTPUT DEST=LAB,COPIES=5//* END OF INCLUDE GROUP

INCLUDE groups

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

INCLUDE groups cannot contain the following statements:

• JOB statements • PROC/PEND statements • JCLLIB statements • JES2/JES3 statements • DD */DD DATA statements

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Work with z/OS procedures:


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (1 of 4)1. Which one of the following is not a JES2 job processing phase?

a. Input phase b. Conversion phase c. Linking phase d. Execution phase e. Output phase f. Purge phase

2. True or False: An internal reader is a program that can be used by programs to submit jobs or control statements to JES2.

3. True or False: During the conversion phase, the JCL of any called procedure is added to the job’s JCL. The result is called external text.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (2 of 4)4. What is the purpose of a procedure library?

a. Contains frequently used JCL statements.b. To enable procedures to be imbedded in a job through a JCL procedure call.c. Both contains frequently used JCL statements and to enable procedures to be

imbedded in a job through a JCL procedure call.

5. True or False: The job processing phases are also referred to as job steps.

6. Is this job card correct? If not, what is incorrect? //EDUCATION JOB 4824789,

// CLASS=A,

// MSGLEVEL=(1/1),

// NOTIFY=USERID,

// MSGCLASS=T,

___________________________________________________________________________________________________________________________________________________________________________________________________

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (3 of 4)7. What is wrong with the following JCL statements?

//step1 EXEC PGM=MYPGM,

//PARM='ABC'

//data DD DSN=USERID.TEST.DATA,DISP=SHR THIS IS THE INPUT DATA SET

//FOR THE MYPGM PROGRAM

______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (4 of 4)8. Which JCL statement allows to define and describe a job’s

input and output data?a. EXEC

b. JOB

c. DD

d. IF/THEN/ELSE/ENDIF

9. Which JCL statement marks the beginning of a job’s step and identifies the program / procedure to be executed?a. EXEC

b. JOB

c. DD


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Override a procedure.3. Create and execute

procedures.4. Log off.

Exercise

Procedures

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 5-87. Unit summary (1 of 2) ES1011.0

Notes:


Unit summary (1 of 2)Having completed this unit, you should be able to:• Explain the JES2 job processing phases in detail• Describe the basic rules for coding JCL• Code JOB/EXEC/DD statements• Submit a job and display its output• Define the term utility• Name and explain the different kinds of utilities• Describe the function and use of the following utilities:

– IEFBR14

– IEBCOPY

– IEBGENER

– IDCAMS


Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 5-88. Unit summary (2 of 2) ES1011.0

Notes:


Unit summary (2 of 2)Having completed this unit, you should be able to:• Work with z/OS procedures:


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Unit 6. Working with UNIX System Services


This unit introduces the students to UNIX System Services. It briefly describes UNIX System Services under z/OS, its main features, file types and access, how to access the shell, and how work is handled.



• Describe the main features of UNIX System Services in z/OS • Describe briefly the UNIX shell and utilities • Identify the various interfaces available to access Unix System

Services and how they can be invoked • Describe the hierarchical file system (HFS)

- Identify the file types and use • Define how processes are created and used in UNIX • Describe the application services provided in UNIX System

Services • Describe how security is handled in UNIX System Services

- Types and classes of users - Use of permission bits



References

GA22-7800 UNIX System Services Planning

SA22-7801 UNIX System Services User’s Guide

SA22-7806 Using REXX and z/OS UNIX System Services

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Unit 6. Working with UNIX System Services 6-1

Student Notebook

.


Notes:


Unit objectivesAfter completing this unit, you should be able to:• Describe the main features of UNIX System Services in z/OS • Describe briefly the UNIX shell and utilities• Identify the various interfaces available to access Unix System

Services and how they can be invoked• Describe the hierarchical file system (HFS)

– Identify the file types and use• Define how processes are created and used in UNIX• Describe the application services provided in UNIX System

Services• Describe how security is handled in UNIX System Services

– Types and classes of users– Use of permission bits

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

6.1. UNIX System Services overview

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-2. UNIX System Services overview ES1011.0

Notes:


UNIX System Services overview


UNIX System Services files

UNIX System Services: Program support and security

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Describe the main features of UNIX System Services in z/OS• Describe briefly the UNIX shell and utilities

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-4. UNIX System Services: Overview ES1011.0

Notes:

z/OS is IBM's integrated solution for an open system platform that provides broad functionality for almost every aspect of computing.

The following is a list of z/OS services.

System Services A set of basic functions and services that are provided through the Base Control Program (BCP), often referred to as MVS, the Job Entry Subsystem (JES), and UNIX base services, as well as other related elements and features. These functions support storage, workload and data management.

Systems Management Services With its Systems Management Services, z/OS delivers products that assist you in installing, configuring and maintaining software as well as in managing system performance.


Communications services

Security services

CICS IMS/TM

System services• TSO • Batch• UNIX• APPC• STC

Application enablement


Applications

non-VSAM VSAM HFS

DB2 IMS/DB

Sof

tcop

y se

rvic

es

Sys

tem

s m

anag

emen

t

LAN services

Distributedcomputing

e-Business services

UNIX System Services: Overview

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Security Services Security Services provides all the necessary functions to ensure a high degree of security within a local or distributed environment.

Application Enablement Services z/OS delivers a language-independent service platform supporting traditional and object-oriented application programs and enabling 3270 terminal applications to exploit workstation graphics and dialogs.

Distributed Computing Services Support for distributed applications based on common industry solutions such as Distributed Computing Environment (DCE), Distributed File Service (DFS), and Network File System (NFS).

Communications Server z/OS supports common programming interfaces such as Advanced Program-to-Program Communication (APPC), IP sockets, Remote Procedure Call (RPC), Systems Network Architecture (SNA or 3270) and wide area network (WAN) protocols including SNA, Transmission Control Protocol/Internet Protocol (TCP/IP), and asynchronous transfer mode (ATM).

e-Business Services Provides secure Internet access and enables z/OS to act as an Internet server. Allows Internet access to IMS, DB2, and CICS transactions.

LAN Services Enables z/OS to actively participate in a local area network (LAN) as data or print server, thus making z/OS resources accessible to LAN users and LAN resources to z/OS users.

UNIX System Services z/OS meet open system standards as specified in the X/Open Company's Single UNIX Specification, also known as UNIX 95 or XPG4.2. This feature allows your UNIX programmers and other users to interact with z/OS as a UNIX system without necessarily having to learn the z/OS command language or other interactive interfaces.

Softcopy Services z/OS provide the necessary services which allow you to manage, display, and search books online.

Note that CICS and IMS/TM are transaction managers, and IMS/DB and DB2 are database managers.

The referenced applications are customer-provided programs.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-5. UNIX applications ES1011.0

Notes:

z/OS provides traditional MVS programming services plus the UNIX System Services, the UNIX shell and utilities feature, the IBM Language Environment for z/OS and zVM, and the C/C++ for z/OS Compiler.

The services that support UNIX application programming make it possible to develop and run C application programs that provide XPG4.2 defined function. The C program source can be developed on an z/OS system using UNIX System Services or on a programmable workstation (PWS). Creation of an application executable file must be done using UNIX System Services through the shell.

UNIX applications that conform to XPG4.2 can be ported to z/OS, and XPG4.2 applications on z/OS can be ported to any XPG4.2 supported platform.

Many of the XPG4.2 function calls are available as callable services, which can be used in z/OS applications to exploit XPG4.2 functions. This provides the capability to access hierarchical files from an z/OS program. UNIX System Services programs can also invoke z/OS system services and access z/OS data sets. These types of applications are called mixed programs. None of these services affect existing z/OS applications.


UNIX System ServicesHFS files z/OS data sets

UNIX programs

Traditional z/OS

programs

Application programmerusing the shell

UNIXworkstation

Application programmerusing TSO/E and ISPF

z/OS services

Mixedprograms

UNIX applications

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-6. What are the benefits of UNIX services? ES1011.0

Notes:

UNIX System Services meet open system requirements. There are thousands of UNIX-based applications available today. Those applications, which conform to XPG4 standards, can be ported to z/OS. These can be vendor applications or self-developed applications.

Not all applications are meant for z/OS, but a UNIX application should be considered if it requires:

• Large DASD capacity • Access to high-speed printers • Support for a large number of users than traditionally on a LAN • Shared applications • High reliability • Large batch jobs • High security

A benefit of z/OS UNIX System Services is scalability. Resources like DASDs, CP power, CPC storage, network, and peripherals can be scaled up for a UNIX system.


Applications People

Skills

PortabilityScalabilty

Interoperability

What are the benefits of UNIX services?

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-7. Access to shell and utilities ES1011.0

Notes:

The UNIX System Services Shell is a command interpreter that accepts commands defined in XPG4.2 standards. To perform some command requests, the shell calls other programs, known as utilities. The shell can be used to:

• Invoke shell scripts and utilities. • Write shell scripts (a named list of shell commands using the shell programming

language). • Run shell scripts and C language programs interactively in the TSO background or in

batch.

IBM has licensed Mortice Kern System's InterOpen XPG4.2 Shell and Utilities source code so that z/OS is XPG4.2 compliant. It is a popular compliant shell based on the Korn shell.

With z/OS, the shell environment can be accessed directly from workstations using rlogin and telnet commands from ASCII terminals attached to a communication server or from a TSO session.


Access to shell and utilities

• Read input

• Interprets command

• Creates process

• Executes process

Built-in commands

InputUser

InterpretShell Process

Utilities

aryaccmakec89printflocateawkgrepdifffindmkdir

Script

"CLIST""EXEC"

od

kill

wait

continue

unset

sort

Shell overview

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-8. Network access to the shell ES1011.0

Notes:

A user can invoke the shell:

• Through TSO/E from 3270 displays or workstations using 3270 emulators. (The workstations can attach to UNIX System Services via SNA or TCP/IP networks.)

• From a TCP/IP-attached terminal.

A user invokes the shell from TSO/E by issuing the OMVS command.

When the INETD daemon is set up and active on the host, rlogin to the shell from a TCP/IP connected workstation can occur.


XPG4.2 shell

TCP/IP

3270 Emulator

SNA

3270 data stream

3270 Terminal3270 Emulator

Channelor LAN

Communicationsserver

telnet

rlogin

ASCII

Workstations

UNIX full screenapplication

rloginUNIX workstation

(ASCII appearance)

(ASCII appearance)

Network access to the shell

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-9. TSO/E and the shell ES1011.0

Notes:

UNIX System Services offers TSO interactive users the choice and ability to switch between the UNIX-like interface of the UNIX System Services shell and command interpreter, and the traditional TSO/E panel or command interface. An installation can customize TSO/E logon so that users who prefer a UNIX-like interface are put directly into the UNIX System Services shell. From there, the users can choose to switch to TSO/E when desired or required.

Examples of interaction between TSO/E and the shell:

• Move data between z/OS data sets and the hierarchical file system. • Use TSO/E commands, the ISPF panel interface with UNIX System Services support,

or shell commands to work with HFS files. • Issue TSO/E commands from the shell command line. • Write z/OS JCL that includes shell commands. • Use the ISPF/PDF full-screen editor or the shell line editor to edit HFS files.



z/OS data sets

HFS files

TSO/E Shell

Traditional z/OS-likeinterface UNIX-like

interface

TSO/E and the shell

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-10. Shell and utilities ES1011.0

Notes:

The shell is the interactive interface to UNIX System Services. The shell is part of the UNIX System Services base element of z/OS. Although some functions can be performed by TSO/E, it is recommended that you use the shell.

The network connection to the shell via TSO/E can be either VTAM (SNA) or TCP/IP. This includes:

• Real and emulated 3270 terminals in an SNA network.

• UNIX systems and other workstations that in a TCP/IP network support the TELNET 3270 (TN3270) client function. The TN3270 client communicates with the TELNET server (TN-S) in TCP/IP on z/OS.

UNIX System Services supports block mode and canonical mode 3270-type terminals. Character asynchronous terminals and non-canonical (raw) mode terminals are not supported.


Commands andutilities

awkgrep

difffind

mkdir

SNAnetwork TCP/IP

network

TSO/E Shell

VTAM TCP/IP

OMVS

z/OS

Shell and utilities

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-11. OMVS TSO/E command ES1011.0

Notes:

The OMVS command is a TSO command which is used to invoke the shell.


---TSO Command Processor ---

Enter TSO command...

===> OMVS SESSIONS(3) CONVERT((BPXFX111))

ESCAPE(^)

OMVS TSO/E command

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

The following parameters can be specified for OMVS:

ALARM | NOALARM Used by some applications to alert the user of an event.

AUTOSCROLL | NOAUTOSCROLL Automatic scrolling of input and output, or turn off automatic scroll.

CONVERT Specifies a conversion table to be used.

DBCS | NODBCS For support of Double Byte Character Set (DBCS).

DEBUG() Controls the collection and output of debugging information.

ECHO | NOECHO Controls the visibility of the input area.ENDPASSTHROUGH Specifies a 3270 key that end

TSO/3270 passthrough mode and forces OMVS to return to the shell session

ESCAPE() Specifies the escape character, which is the EBCDIC equivalent to an ASCII control character.

LINES(n) Amount of output data the OMVS command keeps for scrolling default = four screens, can specify 25 to 3000 lines.

PFn() Customizes the setting of PF keys.PFSHOW | NOPFSHOW Displays the PF keys or turn off the

display. SESSIONS() Starts multiple shell sessions.SHAREAS | NOSHAREAS Shares the same address space for

TSO/E and the shell. WRAPDEBUG(n) Controls how many lines of debug data

OMVS writes out before wrapping around to the top of the debug data set.xc

lusivo

form

ación

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-12. The shell screen ES1011.0

Notes:

This is the screen that is displayed when a user invokes the shell. At the bottom of the screen you see: • The command line (===>) used for input. • The default function key settings and the default escape character assignment. The

function keys can be customized, or they can be turned off. • The status indicator in the right-hand corner. When you first enter the shell, the status is

RUNNING.

The $ prompt is an indication from the shell that it is ready to accept input from the command line. For a superuser, the default prompt is #. A user can decide to use a different prompt than $.

The shell works in 3270 mode, and everything typed on the command line is processed in line mode (canonical mode). This means the input is not processed until the user presses the Enter key.

The shell screen for the non-TSO user looks the same except for the absence of the bottom section.


IBMLicensed Material - Property of IBM5655-A01 (C) Copyright IBM Corp. 1993, 2006(C) Copyright Mortice Kern Systems, INC., 1985, 1996.(C) Copyright Software Development Group, University of Waterloo, 1989.

All Rights Reserved.

U.S. Government users - RESTRICTED RIGHTS - Use, Duplication, orDisclosure restricted by GSA-ADP schedule contract with IBM Corp.

IBM is a registered trademark of the IBM Corp.

$===>

RUNNING <1>ESC=^ 1=Help 2=SubCmd 3=HlpRetrn 4=Top 5=Bottom 6=TSO

7=BackScr 8=Scroll 9=NextSess 10=Refresh 11=FwdRetr 12=Retrieve

The shell screen

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-13. Asynchronous terminal access to shell ES1011.0

Notes:

The rlogin or telnet commands used by the end user are in the syntax of the remote system. The picture shows only some examples.

The rlogin command names the z/OS system that you want to connect to and a user name if you are logging onto z/OS with a different user identity. The telnet command may name the terminal type, the host name or IP address, and the port number if different from the well-known ports used by TCP/IP daemons. In either case, z/OS asks the user for a password.

On the UNIX System Services system, the INETD system daemon must be running to receive these requests. It creates an address space for each user which contains the appropriate server daemon (rlogind or otelnetd). The shell is started by this daemon after it validates the user identity. The daemon is also responsible for ASCII to EBCDIC conversion as data flows from the terminal to the host.

Once the shell is started, the user's profile or individual commands are used to set up the user's shell environment. A user can start multiple shells by issuing multiple rlogin or telnet commands.


1. TCP/IPlogin or telnet port

2. INETDfork an address space

3. Rlogind or otelnetdvalidate user and spawn new process

4. Shell

$rlogin ZOS1$rlogin -l jane ZOS1enter password:

$telnet -t vt220 ZOS1 $telnet -t vt220 -p 623 9.24.104.126 Enter userid:Enter password:

Asynchronous terminal access to shell

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-14. The shell screen for the async user ES1011.0

Notes:

This is the screen that is displayed when a user invokes the shell after logging on with rlogin or telnet.

The $ prompt is an indication from the shell that it is ready to accept input from the command line. For a superuser the default prompt is #. A user can decide to use a different prompt than $, as this example shows.

The shell works in line mode and everything typed on the command line is processed in line mode (canonical mode). This means the input is not processed until the user presses the Enter key.

When an application that requires character mode (or raw mode) support is invoked, the shell runs the application as defined. For example, the vi editor executes in character mode, and when you exit this editor the shell returns to line mode.

In this mode, the ASCII control key on the terminal works as it should. For instance, to interrupt an application use <Ctrl-C>, and to end the shell session use <Ctrl-D>.


IBMLicensed Material - Property of IBM5655-A01 (C) Copyright IBM Corp. 1993, 2006(C) Copyright Mortice Kern Systems, INC., 1985, 1996.(C) Copyright Software Development Group, University of Waterloo, 1989.

All Rights Reserved.

U.S. Government users - RESTRICTED RIGHTS - Use, Duplication, orDisclosure restricted by GSA-ADP schedule contract with IBM Corp.

IBM is a registered trademark of the IBM Corp.

JANE:/u/jane > _

The shell screen for the async user

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-15. Accessing files from the shell ES1011.0

Notes:

UNIX System Services provides commands for the shell user to create and work with directories and files.

• mkdir creates a directory, ed creates or edits a file, mkfifo creates a FIFO, mknod creates a character special file or a FIFO, and ln creates a hard link or symbolic link to a file.

• cp copies a file, ls lists files in a directory, mv moves or renames a file, rm deletes a file, and rmdir deletes an empty directory.

• cd changes a working directory, and pwd displays the working directory for a user.

• chaudit, chgrp, chmod, and chown are commands used to change audit information, group name, permission bits, and owner of a file or directory, respectively.


Shell

cdchauditchgrpchmodchowncpedlnlsmkdirmknodmkfifomvpwdrmrmdir

HFS/zFSfile

Accessing files from the shell

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-16. Shell command example ES1011.0

Notes:

The UNIX System Services shell is, above all, a programmer's interface. The shell has many general tools that can help any programmer, and, in addition, there are several commands designed especially for the C programmer.

Shell commands are entered on the command line (===>) and processed when the user presses the Enter key. Shell command options are usually specified by a minus (-) sign followed by a single character, for example, ls -l. Some commands accept options that have accompanying arguments, for example, ls -l /usr/lib. The argument may be a number, a string, a file name, or something else.

A shell command can be interrupted and stopped by typing <EscChar-C>. Entering a command with -? or entering it incorrectly result in the command syntax being displayed. A user can create an alias for a command, for example alias renam=”mv”. Whenever the user enters the command renam, it is replaced by the command mv.

A user can substitute a command in another command, for example, echo There are ¢(ls | wc -l) files in this dir.


$ ls -l /usr/lib

total 237

drwxr-xr-x 2 ELVIS SYS1 0 Jul 29 20:14 IBM

-rw-r--r-- 2 ELVIS SYS1 5200 Jul 29 20:12 lib.b

-rw-r--r-- 2 ELVIS SYS1 12076 Jul 29 20:12 libl.a

-rw-r--r-- 2 ELVIS SYS1 4706 Jul 29 20:12 liby.a

drwxr-xr-x 5 ELVIS SYS1 0 Jul 29 19:52 nls

-r-sr-xr-x 2 ELVIS SYS1 98304 Jul 29 20:08 tsmail

$

Shell command example

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-17. TSO/E interface to UNIX services ES1011.0

Notes:

TSO/E supports access to UNIX System Services in the following ways:

• The user enters the TSO command OMVS to enter the shell environment • The TSO command ISHELL supports file handling for HFS files via ISPF dialogs • Select the z/OS UNIX directory list utility by either:

- Selecting option 3.17 from the Primary Option menu, or - Selecting option 17 from the Utility selection menu.

• The installation uses the above ISPF panels

After entering the shell environment, the user can toggle between TSO and UNIX. The user can also issue TSO commands from the shell.


z/OS Applications

Option ===>

1 Book Build BookManager/Build

2 Read Doc BookManager/Read Online Documentation

3 Read Index BookManager/Read Bookshelf Index Creation

4 DFSMSrmm DFSMSrmm/ISMF

5 DFSMSdfp DFSMSdfp/ISMF

7 BDT BDT File-to-File Feature

8 IPCS IPCS for dump reading

9 Unix Browse z/OS Unix Browse Files

10 Unix Edit z/OS Unix Edit Files

11 Unix Shell z/OS Unix Shell

12 Security Security Server

13 TSO/E ICF TSO/E Information Center Facility

14 SDSF SDSF

TSO/E interface to UNIX services

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-18. ISPF shell ES1011.0

Notes:

The UNIX System Services ISPF shell provides the ability for users and system administrators to use ISPF dialogs instead of shell commands to perform many tasks related to file systems and files. A regular user can use the ISPF shell to work with:

• Directories • Regular files • FIFO special files • Symbolic links

A system administrator can use the ISPF shell to:

• Work with files and directories as a regular user • Mount and unmount a file system • Set up UNIX System Services users and groups • Change attributes for UNIX System Services users • Create character special files • Set up the root file system


File Directory Special_file Tools File_systems Options Setup Help----------------------------------------------------------------------------

UNIX System Services ISPF Shell

Enter a pathname and do one of these:

- Press Enter. - Select an action bar choice. - Specify an action code or command on the command line.

Return to this panel to work with a different pathname. More: +

/________________________________________________________________________________________________________________________________________________________________________________________________

EUID=0

Command ===> ____________________________________________________________*CMD -HELP

ISPF shell

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-19. ISHELL directory menu ES1011.0

Notes:

This shows the directory pull-down menu.


File Directory Special_file Tools File_systems Options Setup Help------ ----------------------------------

1. List directory(L)... ISPF Shell2. New(N)...

Enter 3. Attributes(A)... 4. Delete(D)...

- 5. Rename(R)... - 6. Copy to PDS(C)... - 7. Copy from PDS(I)... n the command line.

8. Print(P)Retur 9. Compare(M)... rent pathname.

10. Find strings(F)... More: +/ 11. Set working directory(W)__ 12. File system(U)... ____________________________ __________________________________________________________________________________________

EUID=21

Command ===> ____________________________________________________________F1=Help F3=Exit F5=Retrieve F6=Keyshelp F7=Backward F8=Forward

F10=Actions F11=Command F12=Cancel

ISHELL directory menu

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-20. z/OS UNIX directory list ES1011.0

Notes:

Support has been added to ISPF for the processing of z/OS UNIX files. This support includes the ability to edit, browse, create, delete, rename, copy, and replace z/OS UNIX files. This new support is implemented as a directory list utility (known as the z/OS UNIX Directory List Utility), available as option 17 on the ISPF Utilities menu.

This initial implementation of the directory list utility provides a subset of the functions supported by ISHELL. The set of functions supported by the directory list facility are aimed to assist with basic tasks undertaken by users such as programmers. This utility is not aimed at users such as z/OS UNIX file system administrators.

As far as possible, the directory list utility is designed to behave and support commands similar to the data set list utility (ISPF option 3.4). This is done to assist users who are familiar with the operation of the data set list utility but have little experience working with z/OS UNIX files through utilities such as OMVS or ISHELL.


z/OS UNIX directory list• Provides support within ISPF/PDF to process z/OS UNIX files• Provide ability to edit, browse, create, delete, rename, copy,

and replace z/OS UNIX files• Implemented as a directory list utility

– Referred to as the z/OS UNIX Directory List Utility• Invoked through option 17 on ISPF Utilities Menu (option 3)• Provides a subset of the functions supported by ISHELL• Designed to behave and support functions similar to the ISPF

data set list utility (Option 3.4)• Benefit:

– Allows user to process z/OS UNIX files directly from ISPF/PDF

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-21. z/OS UNIX Directory List Utility entry panel ES1011.0

Notes:

When option 17 on the ISPF Utility Selection panel (that is, ISPF option 3.17) is entered, the z/OS UNIX Directory List Utility entry panel is displayed.

This panel supports the following options:

• Blank - display (to process) a list of files in a directory

• P - print a list of files in a directory to the ISPF list data set

For either option, the user must enter in the Pathname field the pathname of the directory they want to display or print. If a path name is not entered, the user’s home path is assumed.


z/OS UNIX Directory List Utility entry panel

Menu RefList RefMode Utilities Options Help ------------------------------------------------------------------------------

z/OS UNIX Directory List Utility Option ===> Time zone GMT-1 is used to calculate the displayed date and time values.

blank Display directory list P Print directory list

Pathname . . . / +

Enter "/" to select option / Confirm File Delete / Confirm Non-empty Directory Delete

When the directory list is displayed, enter either: "/" on the directory list line command field for the command prompt pop-up, an ISPF line command, the name of a TSO command, CLIST, or REXX exec, or "=" to execute the previous command.

-CMD *UDLIST

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-22. z/OS UNIX Directory List panel ES1011.0

Notes:

The z/OS UNIX Directory List panel is displayed when the option field is left blank and enter is pressed on the entry panel.

This panel lists all the files in a directory.

The information for each entry in the directory is displayed in column fields across the screen.

The number of columns displayed depends on the available screen width.

The above example shows the initial directory list display on a terminal with a screen width of 85 and a screen depth of 31.


z/OS UNIX Directory List panel

Menu Utilities View Options Help sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

z/OS UNIX Directory List Row 1 to 22 of 31 Command ===> Scroll ===> PAGE

Pathname . : /SYSTEM/etc

Command Filename Message Type Permission -------------------------------------------------------------------------------

. Dir rwxr-xr-x

.. Dir rwxrwxrwt auto.master File rwxr-xr-x bpa Dir rwxr-xr-x cmx Dir rwxr-xr-x dce Dir rwxr-xr-x dfs Dir rwxr-xr-x httpd.conf File rwxr-xr-x httpd.envvars File rw-r--r--ics_pics.conf File rw-r--r--init.options File rwx------mvsds.conf File rw-r--r--osnmpd.data File rwxrwxrwx pkiserv Dir rwxr-xr-x profile File rwxr-xr-x rc File rwx------recover Dir rwxrwxrwx

-CMD *UDLIST

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-23. Horizontal scrolling through RIGHT and LEFT commands/column order and size ES1011.0

Notes:

Horizontal scrolling is supported using the RIGHT and LEFT primary commands (or function keys 11 and 10). The example in this visual shows the directory list display after entering the command RIGHT 5 on the directory list shown on the previous visual.

Note: The Filename and Message columns are not included in the set of columns that scroll when the RIGHT or LEFT primary commands are entered. These columns are fixed as the left-hand columns of the directory list display.

The order in which columns appear in the directory list display, and these size of the fields can be customized using the z/OS UNIX Directory List Column Arrangement panel.

This panel is accessed via the pull-down menu displayed when the Options choice is selected from the action bar on the z/OS UNIX Directory List entry and display panels.

Here the user can change the order in which the columns are displayed and the width of the column fields.

If a column field’s width is set to zero, the column is not displayed in the directory list.


Horizontal scrolling through RIGHT and LEFT commands/column order and size• Horizontal scrolling through the RIGHT and LEFT primary commands:

Menu Utilities View Options Help -------------------------------------------------------------------------------

z/OS UNIX Directory List Row 1 to 22 of 31 Command ===> Scroll ===> PAGE

Pathname . : /SYSTEM/etc

Command Filename Message Owner Group Links Size -------------------------------------------------------------------------------

. DFS 14 8192

.. DFS OMVSGRP 52 237568 auto.master DFS 1 29 bpa DFS 2 8192 cmx DFS 2 8192 dce DFS 9 8192 dfs DFS 8 8192 httpd.conf WEBADM 1 162841 httpd.envvars WEBADM 1 476 ics_pics.conf WEBADM 1 2943 init.options DFS 1 2588 osnmpd.data DFS 1 1218 pkiserv DFS 2 8192 profile DFS 1 9983 rc DFS 1 3079 recover DFS 2 8192

-CMD *UDLIST

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-24. Line commands available ES1011.0

Notes:

The following line commands are available on the z/OS UNIX Directory List panel: • E: The E (edit) line command can be entered against a regular file. The z/OS UNIX

OEDIT command is invoked, enabling the use of the ISPF editor to change the data in the file.

• B: The B (browse) line command can be entered against a regular file. The z/OS UNIX OBROWSE command is invoked, enabling the use of the ISPF browse facility to display the data in the file.

• N: The N (new) line command is used to create a new file and can be entered against any directory entry. This command causes the Create New z/OS UNIX File panel to be displayed.

• L: The L (list directory) line command can be entered against a directory. This command causes the causes a new z/OS UNIX Directory List panel to be displayed., showing the entries for the selected directory. This new directory list display is nested so entering the END or EXIT command on this panel will return the user to the previous directory list.


Line commands available

E - Edit a file EA - Edit an ASCII fileV - View a file VA - View an ASCII fileB - Browse a file CO - Copy data outN - Create new entry CI - Copy data inL - List a directory I - Display attributesD - Delete an entry R - Rename an entryMM - Modify mode fields MX - Modify extended attributesMO - Modify owner MG - Modify group MF - Modify format X - Execute a z/OS UNIX or TSO cmdUA - User auditing AA - Auditor auditingFS Display file system RA - Refadd to Reflist

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

• D: The D (delete file) line command can be entered against any directory entry. Options are available for confirmation panels to be displayed when the D line command is entered.

• R: The R (rename file) line command can be entered against any directory entry. This line command causes the Rename z/OS UNIX File panel to be displayed.

• CO: The CO (copy out) line command can be entered against a regular file or directory. When entered against a regular file, this command allows the user to copy the data from that file to another z/OS UNIX file, a sequential data set, or a member of a partitioned data set. When entered against a directory, this command allows the user to copy regular files from the directory into members in an existing PDS/E.

• CI: The CI (copy in) line command can be entered against a regular file or directory. When entered against a regular file, this command allows the user to have data from another z/OS UNIX file, a sequential data set, or a member of a partitioned data set replace the data in the selected file. When entered against a directory, this command allows the user to have the members from a PDS/E copies as regular files into the selected directory.

• I: The I (information) line command can be entered against any directory entry. This line command causes a panel to be displayed showing information and attributes for the selected file.

• MM: The MM (modify mode) line command can be entered against any directory entry except a symbolic link. This line command causes the Modify z/OS UNIX File Mode Fields panel to be displayed. This panel allows the permissions, and the set UID, set GID, and sticky bits to be modified.

• MX: The MX (modify extended) line command can be entered against a regular file. This line command causes the Modify z/OS UNIX File Extended Attributes panel to be displayed. This panel allows the extended attributes for the file to be modified.

• X: The X (execute) line command can be entered against a regular file or directory. This line command causes the Execute Command for z/OS UNIX File panel to be displayed. This panel allows you to run the selected file in z/OS UNIX or enter a z/OS UNIX command, TSO command, CLIS T, or REXX exec which is passed the pathname of the of the selected file as a parameter. xc

lusivo

form

ación

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-25. Create New z/OS UNIX File ES1011.0

Notes:

The Create New z/OS UNIX File panel allows a user to create a file and is invoked using the N line command.

The user must enter the pathname and permissions for the new file, and identify the file type.

When creating a symbolic or external link, the user must identify the file the link refers to.

Options are available to have data copied from another file or data set into the new file and to edit the new file. The sticky bit can also be set on for the new file.


Create New z/OS UNIX File

Create New z/OS UNIX File Command ===>

Pathname . . . . /u/prichar/file1 +

Permissions . . (Octal)

Link . . . . . . +

Options File Type . . . 2 1. Directory Set sticky bit

2. Regular file Copy... 3. FIFO Edit... 4. Symbolic Link 5. External Link 6. Hard Link

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-26. Copy From z/OS UNIX File ES1011.0

Notes:

The Copy From z/OS UNIX File panel allows the data from a file to be copied to another file, sequential data set, or member of a partitioned data set and is invoked using the CO line command against a regular file.

The user must specify the name of the target z/OS UNIX file, sequential data set, or partitioned data set and member. When the data is to be copied to a z/OS UNIX file, the user can specify the permissions for this file.

Options are available to:

• Be warned if the data is being copied to a target that exists.

• When the target is an existing z/OS UNIX file, have its permissions updated.

• Cause a binary copy to occur when copying to a sequential data set or member.

• Cause data conversion to take place during the copy operation. An optional conversion table can be specified.


Copy From z/OS UNIX File

Copy From z/OS UNIX File Command ===>

From z/OS UNIX file: Name . . . : /u/prichar/automount

To z/OS UNIX file, data set, or member: Name . . . . + Permissions 700 (Octal)

Options / Confirm copy to existing target

Update permissions for existing target file Binary copy Convert

Conversion Table

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-27. Copy From z/OS UNIX Directory ES1011.0

Notes:

The Copy From z/OS UNIX Directory panel allows the data from regular files in a directory to be copied to member in a partitioned data set and is invoked using the CO line command against a directory.

The user must specify the name of the target partitioned data set. Options are available to:

• Have data in existing members overwritten with the data from the source file

• Display a selection list where the user can select the files in the directory that are to be copied.

• Allow files with names containing lowercase characters to be copied.

• Allow files with names containing suffixes to be copied by having the suffix removed.

• Cause a binary copy to occur when copying to the target member.



Copy From z/OS UNIX Directory

Copy From z/OS UNIX Directory Command ===>

From z/OS UNIX directory: Name . . . : /u/prichar/bin

To partitioned data set: Name . . . .

Options Replace like-named members Selection list...

/ Include lowercase names / Strip suffix (Suffix to strip)

Binary copy Convert

Conversion Table

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-28. Replace z/OS UNIX File ES1011.0

Notes:

The Replace z/OS UNIX File panel allows the data in a regular z/OS UNIX file to be replaced with the data from another file, sequential data set, or member of a partitioned data set and is invoked using the CI line command against a regular file.

Use CI (- Copy data in) line command.

The user must specify the name of the source z/OS UNIX file, sequential data set, or partitioned data set and member. Options are available to:

• Cause a binary copy to occur when copying from a sequential data set or member.



Replace z/OS UNIX File

Replace z/OS UNIX File Command ===>

Into z/OS UNIX file: Name . . . : /u/prichar/biorhytm.C

From z/OS UNIX file, data set, or member: Name . . . . +

Options Binary copy Convert

Conversion Table

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-29. Copy Into z/OS UNIX Directory ES1011.0

Notes:

The Copy Into z/OS UNIX Directory panel allows the data from members in a partitioned data set to be copied into regular files in a directory and is invoked using the CI line command against a directory. The user must specify the name of the source partitioned data set. The user can specify the permissions to apply to the files the members are copied into. The user can also specify a suffix which is appended to the member name to make the name of the regular file created/updated during the copy operation. Options are available to:

• Have data in existing files overwritten with the data from the source member. • Have the permissions for existing files overwritten during the copy operation updated

using the permissions value specified by the user. • Display a selection list where the user can select the members that are to be copied • Have the member name converted to lowercase before it is used to generate the

filename for the target regular file. • Cause a binary copy to occur when copying to the target file. • Cause data conversion to take place during the copy operation. An optional conversion

table can be specified.


Copy Into z/OS UNIX Directory

Copy Into z/OS UNIX Directory Command ===>

Into z/OS UNIX directory: Name . . . : /u/prichar/bin

From partitioned data set: Name . . . .

Permissions 600 Suffix . . . .

Options Replace like-named files Update permissions for replaced files Selection list...

/ Convert to lowercase Binary copy Convert

Conversion Table

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-30. z/OS UNIX File Information ES1011.0

Notes:

The z/OS UNIX File Information panel displays the attributes for a file or directory and is invoked using the I line command.

The Modify pull-down contains options to modify either the mode fields or the extended attributes for the file.


z/OS UNIX File Information

Modify Display---------------------------------------------------------------------------------

z/OS UNIX File Information Command ===>

Pathname . . : /u/prichar/biorhytm.C

General Data Mode Fields File Type . . : File Permissions . : 600File Size . . : 8774 Set User ID . : NO Links . . . . : 1 Set Group ID : NO Inode . . . . : 1617 Sticky Bit . : NO File Format . : nl Last Modified : 2000/04/05 12:02:50 Extended Attributes Last Changed : 2000/04/05 12:02:50 Shared AS . . : YESLast Accessed : 2006/02/20 19:35:52 APF Auth . . : NO Created . . . : 2000/03/13 19:07:57 Pgm Control . : NO CCSID . . . . : Shared Lib . : NO Text Convert : NO

Audit Owner Auditor . . . : ---File . . . . : DFS(0) User . . . . : fffGroup . . . . : OMVSGRP(0)

Device Data Device Number : 36 Major Device : Minor Device :

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-31. Modify z/OS UNIX File Mode Fields ES1011.0

Notes:

The Modify z/OS UNIX File Mode Fields panel allows the user to change the permissions, set UID bit, set GID bit, and the sticky bit for a file.

It is invoked using the MM line command or via the Modify pull-down on the z/OS UNIX File Information panel.


Modify z/OS UNIX File Mode Fields

Modify z/OS UNIX File Mode Fields Command ===>

Pathname . : /u/prichar/biorhytm.C Type . . . : File

Permissions 600 (Octal)

Enter "/" to select option Set UID bit Set GID bit Sticky bit

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-32. Execute Command for z/OS UNIX File ES1011.0

Notes:

The Execute Command for z/OS UNIX File panel allows the user to run a file, or execute a z/OS UNIX command, TSO command, CLIST, or REXX exec against a file.

It is invoked using the X line command against a regular file, directory, or symbolic link to a regular file.

For a command that runs in z/OS UNIX, the user has the option to run the command under the login shell or directly in z/OS UNIX.

To simply run the selected file, the user can leave the Command for file field blank. By default, the pathname of the selected file is appended to the end of the command entered by the user.

The panel on this visual shows a request to run the c89 command to compile, assemble, and link-edit the C program in /u/prichar/calc.c. The command is to run in the z/OS UNIX login shell.

When you press Enter, you get a message like: “Running shell command: /bin/sh -Lc /bin/c89 /u/prichar/calc.c PID=50397274 “.


Execute Command for z/OS UNIX File

Execute Command for z/OS UNIX File Command ===>

Pathname . . . . /u/prichar/calc.c

Enter the command below. Use the pathname substitution character ! to indicate where to have the pathname substituted. If not specified, the pathname will be appended to the end of the command.

Command for file: /bin/c89

Run method . . . 1 1. Direct 2. Login shell 3. TSO

z/OS UNIX command time limit . . .

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-33. Native ISPF edit and browse z/OS UNIX files ES1011.0

Notes:

z/OS 1.9 provides z/OS UNIX file support into native ISPF EDIT and BROWSE functions.

The Edit Entry, Browse/View Entry, Edit Copy, Edit Move, Edit Create, and Edit Replace panels are modified in z/OS 1.9 so that the “Other” data set name field is a scrollable field which accepts a z/OS UNIX pathname of up to 1023 characters in length.

ISPF assumes a z/OS UNIX path name is entered in this field when the first character is one of the following:

• / (forward slash) Identifies an absolute path name.

• ~ (tilde) Represents the path name for the user’s home or initial working directory.

• . (dot) Represents the path name for the current working directory.

• .. (dot dot) Represents the path name of the parent directory for the current working directory.


Native ISPF edit and browse z/OS UNIX files• Edit/view/browse other data set name fields support entry of

z/OS UNIX path names.– Scrollable field allows input of path names up to 1023 bytes in length.

• Path name assumed when first character is:– / (forward slash): Absolute path name– ~ (tilde): User’s home or initial working directory– . (dot): Current working directory– .. (dot dot): Parent of the current working directory

Other Partitioned, Sequential or VSAM Data Set, or z/OS UNIX file: Name . . . . . +Volume Serial . . (If not cataloged)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Some examples:

~/test/tst1.shIs equivalent to specifying absolute path name /u/jsmith/test/tst1.sh when the user’s home directory is defined as /u/jsmith.

./pgma.c Is equivalent to specifying absolute path name /u/proj1/dev/pgma.c when the user’s current working directory is set to /u/proj1/dev.

../test/pgma.c Is equivalent to specifying absolute path name /u/proj1/test/pgma.c when the user’s current working directory is set to /u/proj1/dev.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-34. Edit and browse z/OS UNIX files: Usage ES1011.0

Notes:

A z/OS UNIX directory selection list is displayed when the pathname for a directory is specified:

• On the View and Edit entry panels

• On a call to the BROWSE, EDIT and VIEW services

• With the edit/view MOVE, COPY, BROWSE, EDIT, and VIEW primary commands

• With the browse EDIT, VIEW, and BROWSE commands

The directory selection list is almost identical to the list displayed from the z/OS UNIX Directory List Utility (PDF option 3.17). The selection list supports the S (select) line command, allowing you to select the file to be processed with the function (for example, edit) that invoked the list.


Edit and browse z/OS UNIX files: Usage• z/OS UNIX Directory List displayed when path name for directory

entered in the Other data set name fieldEdit Entry Panel

Command ===> ISPF Library:

Project . . . Group . . . . . . . . . . . . . Type . . . . Member . . . (Blank or pattern for member selection list)

Other Partitioned, Sequential or VSAM Data Set, or z/OS UNIX file: Name . . . . . /usr +Volume Serial . . (If not cataloged)

z/OS UNIX Directory List Row 1 to 13 of 13 Command ===> Scroll ===> PAGE Time zone GMT-1 is used to calculate the displayed date and time values. Pathname . : /MOZ1CA/usr

Command Filename Message Type Permission -------------------------------------------------------------------------------

. Dir rwxr-xr-x

.. Dir rwxr-xr-x bin Dir rwxr-xr-x include Dir rwxr-xr-x lib Dir rwxr-xr-x local Dir rwxrwxr-x lpp Dir rwxr-xr-x

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-35. View Entry Panel ES1011.0

Notes:

The View Entry Panel, displayed via ISPF option 1, is changed to allow a z/OS UNIX file pathname to be entered in the Other data set name field.

Also the new Record Length field is added to allow a record length to be specified when browsing a z/OS UNIX. The value entered in this field is used by ISPF to display the data in the file as fixed-length records, rather than using the newline character to delimit each record. This is useful for browsing files which would otherwise have very large records if the newline character is used as the record delimiter.


View Entry Panel• View Entry panel modified for z/OS UNIX file support:

– Other data set name field supports z/OS UNIX pathnames– Record Length field used with the browse function to display z/OS

UNIX file data as fixed-length records

Menu RefList RefMode Utilities Workstation Help View Entry Panel

Command ===>

ISPF Library: Project . . . Group . . . . . . . . . . . . . Type . . . . Member . . . (Blank or pattern for member selection list)

Other Partitioned, Sequential or VSAM Data Set, or z/OS UNIX file: Name . . . . . +Volume Serial . . (If not cataloged)

Workstation File: File Name . .

Options Initial Macro . . . . / Confirm Cancel/Move/Replace Profile Name . . . . . Browse Mode Format Name . . . . . View on Workstation Data Set Password . . / Warn on First Data Change Record Length . . . . Mixed Mode

View ASCII data

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Note

The Record Length field can be used when editing a z/OS UNIX file. It allows you to specify a record length which is used by the editor to load the records from the file into the edit session as fixed-length records. When the file is saved, it is saved with fixed length records. So the Record Length field allows you to convert a variable length file to a fixed length file.

The value specified in the Record Length field must be able to accommodate the largest record in the file. If the editor finds a record that is larger than the length specified, an error message is displayed and the edit session does not proceed.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-36. Edit Entry Panel ES1011.0

Notes:

The Edit Entry Panel, displayed via ISPF option 2, is changed to allow a z/OS UNIX file pathname to be entered in the Other data set name field.

Also the new Record Length field is added to allow a record length to be specified when editing a z/OS UNIX.

ISPF normally treats z/OS UNIX file as having variable length records. This field allows you to specify a record length which is used by the editor to load the records from the file into the edit session as fixed-length records. When the file is saved it is saved with fixed length records. So the Record Length field allows you to convert a variable length file to fixed length.


Edit Entry Panel • Edit Entry panel modified for z/OS UNIX file support:

– Other data set name field supports z/OS UNIX path names.– Record Length field used to display and save data for a z/OS UNIX

file data as fixed-length records.

Menu RefList RefMode Utilities Workstation Help ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

View Entry Panel Command ===>

ISPF Library: Project . . . Group . . . . . . . . . . . . . Type . . . . Member . . . (Blank or pattern for member selection list)

Other Partitioned, Sequential or VSAM Data Set, or z/OS UNIX file: Name . . . . . /etc/ + Volume Serial . . (If not cataloged)

Workstation File: File Name . .

Options Initial Macro . . . . / Confirm Cancel/Move/Replace Profile Name . . . . . Browse Mode Format Name . . . . . View on Workstation Data Set Password . . / Warn on First Data Change Record Length . . . . Mixed Mode

View ASCII data

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-37. TSO and shell interaction ES1011.0

Notes:

This is an example of a possible interaction between TSO/E and the shell:

• A TSO/E user logs on to TSO/E and issues some TSO/E commands or uses the ISPF/PDF panels to do some work.

• The user issues the OMVS command to invoke the UNIX System Services shell.

• After issuing the OMVS command, the TSO/E user becomes a logged on shell user.

• The shell user is interactively communicating with the UNIX System Services environment through the shell and has all the facilities of the shell available.

• The user can jump or escape back to TSO/E, run a TSO/E command, and return to the shell. When jumping back and forth between TSO/E and the shell, the user remains logged on to both TSO/E and the UNIX System Services environment.

• The user issues an exit command to log off from the shell and return to TSO/E.


• Log on to TSO/E• Issue any TSO cmd• Issue the OMVS cmd

• Issue any TSO cmd• Return to the shell

• Issue any TSO cmd• Log off

• Become a logged-on shell user

• Run any shell cmd• Escape to TSO mode

• Continue shell cmds• Exit shell

TSO/E

Shell

TSO and shell interaction

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-38. Commands and utilities ES1011.0

Notes:

The UNIX commands and utilities are distributed with the UNIX system. There are over 100 UNIX commands and utilities.

A command is a UNIX program that is executed in the shell. Commands are sometimes referred to as tools. For some commands, the shell calls other programs called utilities. For the user, there is no difference between a command and a utility.

UNIX commands have very short names. This dates back from the time when teletypes were in use.

UNIX commands are usually very small programs designed to do one simple task. Commands can be combined together in a shell script, which then becomes a new powerful command.


Commands and utilities

Visual screen editorviSortsortRemovermPrint working directorypwdProcess statuspsMovemvMake directorymkdirShow online documentationmanSend/receive electronic mailmailListlsSend signalkillPrint first few linesheadSearch for patterngrepFindfindDifference between two filesdiffShow datedateCopycpChange directorycdC compilerccConcatenatecatPattern processing languageawk

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-39. Accessing files from TSO/E ES1011.0

Notes:

There are some TSO/E commands which support the hierarchical files:

• MKDIR creates a new directory, and MKNOD creates a character special file. • OEDIT creates or edits a file using ISPF editor, and OBROWSE browses a file using ISPF. • OCOPY copies a file from HFS to a z/OS data set, copies a z/OS data set to an HFS file,

copies an HFS file to an HFS file, or z/OS data set to z/OS data set. • OGET and OGETX are used to copy HFS files to z/OS data sets. • OPUT and OPUTX are used to copy z/OS data sets to HFS files. • MOUNT and UNMOUNT/UMOUNT are used to mount and unmount hierarchical file

systems. • ISHELL or ISH invoke the UNIX System Services ISPF shell. This is a panel interface

for performing user and administrator tasks.


HFSdata set

TSO/E

• MKDIR

• MKNOD

• MOUNT

• OBROWSE

• OCOPY

• OEDIT

• OGET,OGETX

• OPUT,OPUTX

• UNMOUNT/

UMOUNT

• ISHELL/ISH

TSO/E commands

Accessing files from TSO/E

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-40. File copy ES1011.0

Notes:

File copy between z/OS data sets and HFS files can be useful if you need to send and receive files between z/OS systems, for DFSMS backup and restore of HFS files, or to copy HFS files to tapes.

OGET: Copies an HFS file into a z/OS sequential file or a PDS/PDSE member. Code page conversion can be specified.

OGETX Copies an HFS directory into a z/OS PDS/PDSE. Code page conversion can be specified.

OPUT Copies a z/OS sequential file or a PDS/PDSE member into an HFS file. Code page conversion can be specified.

OPUTX Copies all members of a PDS/PDSE into an HFS directory. Code page conversion can be specified.

OCOPY Copies data in either direction between a z/OS data set and an HFS file using DD names. Can also copy between z/OS data sets, or between HFS files. Code page conversion can be specified.


OCOPY

OPUT/OPUTX

OGET/OGETX

TSO/EcommandsTSO/E

MVS data sets HFS files

File copy

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Describe the main features of UNIX System Services in z/OS• Describe briefly the UNIX shell and utilities

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

6.2. UNIX System Services files

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-42. UNIX System Services files ES1011.0

Notes:






Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Describe the hierarchical file system (HFS)

– Identify the file types and use

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-44. UNIX System Services files ES1011.0

Notes:

The UNIX System Services file system is hierarchical in structure in the same way as a UNIX file system. All files are members of a directory, and each directory is in turn a member of another directory at a higher level in the hierarchy. The highest level in the hierarchy is called the root directory.

A directory is a special kind of file which consists of the names of a set of files and other information about them. Usually the files in a directory are related to each other in some way. A directory can have subdirectories.

A UNIX System Services user has a directory defined as its home directory. After logon, the home directory becomes the working directory.

A regular file is a named unit of text or binary data information. A file can, for example, be C source code, a list of names or places, a printer formatted document, a string of numbers organized in a certain way, an employee record, or a memo. A user or application must understand how to access and use the individual increments of data within a file.



HFS / ZFS data set

Directory Directory

Directory

Directory

Directory

Directory

File

File

File

File

FileFile

FileFile

FileFile

File

File

File

Hierarchical file system structure

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

A file in the hierarchical file system is called an HFS file. HFS files are byte-oriented and there is no concept of a record structure.

A file system is contained in a z/OS data set type called HFS data set.

The hierarchical file system in UNIX System Services is similar to the file system in DOS and Windows systems.

The z/OS Distributed File Service zSeries File System (zFS) is a z/OS UNIX file system that can be used like the Hierarchical File System (HFS). zFS file systems contain files and directories.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-45. HFS and zFS as UNIX file systems in z/OS ES1011.0

Notes:

zFS is a physical file system (PFS) like HFS. It is not a HFS replacement, it is complimentary.

A zFS aggregate is a data set that contains zFS file systems. The aggregate is a VSAM linear data set (VSAM LDS) and is a container that can contain one or more zFS file systems.

An aggregate can only have one VSAM LDS, but it can contain an unlimited number of file systems. The name of the aggregate is the same as the VSAM LDS name.

A zFS aggregate that contains only a single zFS file system can be defined and is called a compatibility mode aggregate.

Compatibility mode aggregates are more like HFS.

Aggregates that contain multiple file systems are called multi-file system aggregates.


HFS and zFS as UNIX file systems in z/OS• zSeries File System (zFS):

– Complimentary to HFS– Improved performance– Improved recovery– Shared zFS across a sysplex– Disk space sharing between

file systems in the same data set

– File system cloning

Users

USS

Logical file systems (LFSs)

OtherPFSs zFSHFS

HFSVOLIP sockets,

NFS and so onzFSVOLVSAM LDS

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-46. File types ES1011.0

Notes:

The hierarchical file system contains the following types of files:

• Directories

• Regular files

• Named pipes (FIFO)

• Character special files

• Symbolic links

Users and programs create directories, regular files, pipes, and symbolic links; a system programmer creates character special files.


• Directories• Regular files• Named pipes (FIFO)• Character special files• Symbolic links

File types

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-47. Files and directories ES1011.0

Notes:

A directory is a special kind of file which consists of the names of a set of files and other information about them. Usually the files in a directory are related to each other in some way. A directory can have subdirectories.

A UNIX System Services user has a directory defined as its home directory. After logon, the home directory becomes the working directory.

A regular file is a named unit of text or binary data information. A file can, for example, be C source code, a list of names or places, a printer formatted document, a string of numbers organized in a certain way, an employee record, or a memo. A user or application must understand how to access and use the individual increments of data within a file.


JCL

u

jones

smithjones

smithprogabc ...ProgABC ...JCL ...

projecta ...projectb ...

progabc

ProgABCprojecta

projectb

Files and directories

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-48. HFS data set ES1011.0

Notes:

A hierarchical file system is contained in a data set type called HFS. An HFS data set is a single volume data set, which means that a file system cannot span more than one physical DASD volume.

HFS data sets must be SMS-managed, and they can reside with other z/OS data sets on SMS-managed volumes.

HFS data sets are PDSE-like data sets. They are allocated like any other z/OS data set. Although an HFS data set is a z/OS data set, a z/OS OPEN request fails.


F FF F F

/

/

Data set

HFS

HFS

Dataset

SMSVL1

F FF F F

/ HFSDataset

Data set

SMSVL2

HFS data set

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-49. HFS data set characteristics ES1011.0

Notes:

HFS data set characteristics:

• HFS data sets can be SMS managed.

• They allocated as z/OS data sets with TYPE=HFS.

• Multiple systems can share the data set in a sysplex environment or if the HFS is mounted in read-only mode on all systems.

• HFS data sets can be opened by UNIX System Services z/OS kernel operations, and some types can be processed by standard z/OS access methods.

• HFS data sets can reside on the same volumes as other z/OS data sets.


SMSVOL

/

F F F

F F

HFS

HFS data set characteristics

• SMS managed or non-SMS managed

•DSNTYPE=HFS

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-50. File system structure ES1011.0

Notes:

z/OS views an entire file system hierarchy as a collection of HFS and or z/OS file system (zFS) data sets. Each HFS or zFS data set is a mountable file system. Connecting one file system to another is called mounting. HFS or zFS data sets can be mounted onto each other in a hierarchy. The root file system is the first file system mounted. Subsequent file systems can be mounted on any directory within the root file system or on a directory within any mounted file system.

The place within a file system where another file system is mounted is called a mount point. A file system can be mounted only in one place at a time.

The command mount is used to mount a file system, and unmount is used for disconnecting a file system from another. Mount and unmount are authorized commands.

The root file system is the starting point of the overall file system. It consists of the root directory (/) and related directories and files.


F

F F F F F F

F

D1 D2

D3 D4

D5

/

/ /

HFSdata set

HFSdata set

HFSdata set

Root file system

File system structure

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

The system programmer defines the root file system. The root file system usually contains system-related files and files that belong to a program product. User files are usually located in other mountable file systems.

Altogether, the root file system and mountable file systems contain the file systems used by shell users and applications.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-51. Path name and file name ES1011.0

Notes:

The set of names required to specify a particular file in a hierarchy of directories is called the path to the file. The path is specified as a path name.

A path name can be absolute or relative. An absolute pathname is a sequence which begins with a slash for the root, followed by one or more directories, and ends with the file name. A relative path name is a path name which is relative to the working directory. A relative path name does not start with a slash.

A path name can be up to 1023 characters long including all directory names, separating slashes, and the file name.

A file name can be up to 255 characters long, and can consist of uppercase and lowercase letters. UNIX System Services is case sensitive, which means a file called ProgABC is different from progabc. File names can include extensions which identify the contents of a file, for example, proga.c, and name.lst.


bin dev etc usr

/

tmp lib u samples

sh

Path

smith jones

progabcProgABC

JCL projectb projecta

Path name and file name

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-52. File identification comparison ES1011.0

Notes:

In z/OS, a data set is identified by a data set name, and if the data set is a PDS or PDSE, the file has a member name. The characteristics of the data sets, such as DCB (RECFM, BLKSIZE) information or DSNTYPE, are kept in catalogs or the VTOC. Executable modules can have multiple names (ALIAS).

In the hierarchical file system, files are identified by pathnames, which consist of directory names and the file name. Files can have multiple names created by symbolic links and hard links. There is no concept of a defined record format or blocksize. An open file gets a file descriptor which is used as pointer to the file in C programs.


z/OS data sets

DCB= Data control block

UNIX files

File descriptor: 18=/a/b/c

DSCBA.B.C

dsnameA.B.C

/a/b/c

pathname

//DD1 DD DSN=A.B.C,DCB= path=/a/b/c

File identification comparison

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-53. File system structure comparison ES1011.0

Notes:

A traditional z/OS data set can be searched through the catalogs or through the VTOC if UNIT and VOLSER is specified. The z/OS master catalog contains ALIASes which are pointers to user catalogs. An ALIAS in the master catalog decides in which user catalog a data set should be cataloged and where to search for cataloged data sets. The user catalogs contain a list of data sets and some information about the data sets.

The POSIX file system is based on the root file system. All files are referenced by a pathname based on the root directory or relative to a working directory. There is no concept of catalogs in POSIX. All files are listed in directories, and directories are listed in a directory on a higher level in the hierarchy.


z/OS data sets

Master catalog

ALIAS IBMUSER

User catalog

IBMUSER.C

IBMUSER.C(PGMA)

Root /

/u/IBMUSER

/u/IBMUSER/c

/u/IBMUSER/c/pgma

IBMUSER

LIST(SEQ)

C(PDS)PGMAPGMB

DATA(VSAM)

UNIX files

IBMUSER

list data

pgma pgmbc

File system structure comparison

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-54. File access comparison ES1011.0

Notes:

z/OS data sets:

• z/OS uses an enqueue (ENQ) at allocation of a data set to guarantee data integrity. The correct disposition must be coded in the JCL or on the ALLOCATE command.

• There are multiple access methods which recognize data set characteristics and simplify programming.

Hierarchical Files:

• XPG4.2 does not have mandatory file locking but uses the concept of advisory locking to ensure data integrity. The programmer must decide when to use locking. Locking is done by the fcntl() function and can be used to lock parts of a hierarchical file.

• There are no access methods for hierarchical files. A file is a stream of bytes, and the application programmer defines how to manage the contents of the files.


File access comparison

AllocationOPENGETPUTENQCLOSE

Deallocation

Security throughdata set profiles

EXCPBDAMBSAMBPAMISAMVSAM: KSDS, ESDS

open()read()write()fcntl()close()

Permission bitson each file

Byte streamfile organizationis applicationresponsibility

z/OS data sets UNIX files

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-55. HFS / UNIX file creation ES1011.0

Notes:

• Hierarchical File System data sets: - Have partitioned organization - Have the same structure as a PDSE - might or might

not be SMS-managed. - Contain mountable file systems used by z/OS UNIX Services.

• z/OS UNIX Services supports UNIX applications. • To create an HFS data set, specify the usual DD statement parameters which are

necessary to create any z/OS data set. In addition, specify DSNTYPE=HFS to ask z/OS to create an HFS data set.

• The additional PATH____ parameters shown above must be specified to create an HFS file in the HFS data set: - PATH specifies the name of the HFS file to be created. - PATHMODE specifies the file access attributes. - PATHDISP specifies the file disposition at end of step. - PATHOPTS specifies the file access and status.


z/OS UNIX FILE CREATION//FILE DD PATH='/u/tsojdoe/adir/my.file',

// PATHMODE=(SIRWXU,SIWGRP),PATHDISP=(KEEP,DELETE),

// PATHOPTS=(OWRONLY,OCREAT,OEXCL)

HFS / UNIX file creationHFS CREATION//FS DD DSN=TSOJDOE.OMVS.HFS,

// DISP=(,CATLG),DATACLAS=SPDS,

// SPACE=(CYL,(80,40,1)),

// DSNTYPE=HFS

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-56. JCL support ES1011.0

Notes:

One way of using a file in the hierarchical file system is to refer to it by JCL. The following changes have been made to support hierarchical files:

DSNTYPE=HFS|PIPE Specify HFS to create a hierarchical file system data set, or PIPE to specify a named pipe (FIFO).

PATH Identifies a file in the hierarchical file system. The JCL support allows a path name to be up to 255 characters long, including the slashes. If the pathname contains lowercase letters, the name must be enclosed by single quotes.

PATHDISP Specifies the disposition of a hierarchical file after normal or abnormal end. It can be KEEP or DELETE.

PATHMODE Specifies the file access attributes when the file specified in the PATH parameter is created. The file access attributes define who has access to read, write, or execute the file.

PATHOPTS Specifies the access and status for a file. There are two file options groups, the access group and the status group.


DSNTYPE=HFS|PIPE

PATH=pathname

PATHDISP=(normal-termination-disp,abnormal-term-disp)

PATHMODE=(file-access-attribute,file-acc-attr, . . . )

PATHOPTS=(file-option,file-option,. . . )

JCL support

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-57. Allocate HFS (root file system) ES1011.0

Notes:

This shows an example of how to allocate an HFS data set for the root file system.

The important JCL keyword here is DSNTYPE=HFS.

Note that an HFS can be either SMS or non SMS managed, but must be cataloged for the mount to succeed.


// SET &SYSR1='OS3RS1' <== VOLSER OF SYSRES

//OMVSHFSA JOB (.......)

//STEP1 EXEC PGM=IEFBR14

//MKROOT DD DSNAME=OMVS.V&SYSR1..ROOT,

// SPACE=(CYL,(600,100,1)),

// UNIT=3390,

// DSNTYPE=HFS,

// DCB=DSORG=PO,

// DISP=(NEW,CATLG,DELETE),

// STORCLASS=STANDARD

OMVS.VOS3RS1.ROOT

ServerPac: Job ALLOCDS provided

Allocate HFS (root file system)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-58. Format a zFS aggregate ES1011.0

Notes:

The IOEAGFMT utility is used to format an existing VSAM LDS as a zFS aggregate. All zFS aggregates must be formatted before use (including HFS compatibility mode aggregates).

IOEAGFMT does not require the zFS physical file system to be active on the system. The size of the aggregate is as many as 8 KB blocks and fits in the primary allocation of the VSAM LDS. To extend it to its secondary allocation (assuming it has a secondary allocation), use the zfsadm grow command.


Example://USERIDA JOB ,'Compatibility Mode',// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)//DEFINE EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=H//SYSUDUMP DD SYSOUT=H//AMSDUMP DD SYSOUT=H//DASD0 DD DISP=OLD,UNIT=3390,VOL=SER=PRV000//SYSIN DD *

DEFINE CLUSTER (NAME(OMVS.PRV.COMPAT.AGGR001) -VOLUMES(PRV000) -LINEAR CYL(25 0) SHAREOPTIONS(2))

/*//CREATE EXEC PGM=IOEAGFMT,REGION=0M,// PARM=('-aggregate OMVS.PRV.COMPAT.AGGR001 -compat')//SYSPRINT DD SYSOUT=H//STDOUT DD SYSOUT=H//STDERR DD SYSOUT=H//SYSUDUMP DD SYSOUT=H//CEEDUMP DD SYSOUT=H//*

IOEAGFMT

Format a zFS aggregate

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-59. JCL example ES1011.0

Notes:

This JCL example shows a program in an z/OS data set being relinked to reside in the hierarchical file system.

• PATH defines the path name of the directory where the program payroll will reside when link-edited. The path name is in lowercase letters and therefore enclosed by single quotes.

• PATHOPTS:

- OWRONLY specifies the file is opened for write. - OCREAT specifies that if the file does not exist, it is created. If it exists, it is reused. - OTRUNC specifies that the file length is truncated to zero if the file already exists.

• PATHMODE:

- SIRWXU specifies that the file owner has read, write, and execute permission. - SIRWXG specifies that file group has read, write, and execute permission. - SIRWXO specifies that all other users have read, write, and execute permission.


//LINK JOB (XX,YY,ZZ),MSGCLASS=H,CLASS=A,// MSGLEVEL=(1,1)//LKED EXEC PGM=IEWBLINK,// PARM='LIST,REUS,RENT,LET,CASE=MIXED'//SYSPRINT DD *//INLIB DD DSN=POSIX.LOADLIB,DISP=SHR//*//SYSLMOD DD PATH='/u/posix/llib',// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),// PATHMODE=(SIRWXU,SIRWXG,SIRWXO)

//SYSLIN DD *INCLUDE INLIB(PAYRLL)ENTRY CEESTARTNAME payrll(R)

/*

JCL example

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Topic summaryHaving completed this topic, you should be able to:• Describe the hierarchical file system (HFS)

– Identify the file types and use

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

6.3. UNIX System Services: Program support and security

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-61. UNIX System Services: Program support and security ES1011.0

Notes:






Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic objectivesAfter completing this topic, you should be able to:• Define how processes are created and used in UNIX• Describe the application services provided in UNIX System



xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-63. UNIX System Services program support ES1011.0

Notes:

Processes are used in UNIX to allocate resources to users and programs. They are equivalent to address spaces in z/OS.

A process is created by a fork() system call, and it is terminated by executing an exit() system call, or by a kill() signal from another process. Each process has a unique identifier called process id (pid).

The fork() system call creates a new process with identical characteristics as the process that issued the fork(). The new process is called the child process, and the process that created it is called the parent process. After the fork(), the two processes are running exactly the same program. However, the return code from the fork() is different for the parent and child. The two processes also have different process IDs. The child inherits the file descriptors of the parent process, which means it has access to the same files, including pipes, as its parent.

The exec() system call is used to start a new program in a process. The sequence of fork() followed by exec() is used very often in UNIX to create a new process and start a new program.


UNIX System Services program support

PID 18 PID 20 PID 20

after fork() after exec()

...fork()

...exec(progB,.........

...fork()

...exec(progB,.........

.....

.....

.....

.....

.....

Parentprocess

Childprocess

Childprocess

Program A Program A Program B

Processes

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-64. Program file operations ES1011.0

Notes:

The ANSI C standard defines the functions fopen(), fclose(), fread(), and fwrite() to access files. This enables C language programs to access z/OS data sets. These functions are included in the POSIX standard, and, with UNIX System Services, they can be used to access hierarchical files as well.

The POSIX/XPG4.2 standard also provides the I/O functions open(), close(), read(), write(), and fcntl() for accessing hierarchical files.

open() or fopen()

Opens a file. Name of file is required as a parameter, as well as information on how the file is to be opened (for read, write, or both).

read() or fread()

Reads a given number of bytes from a file.

fcntl() Used to lock out other users from a part of a file, so that the user can read or write to that part of the file without interference from others.

write() or fwrite()

Writes a given number of bytes to a file.

close() or fclose()

Closes a file.


C language program

fopen()

fclose()

fread()

fwrite()

open()

close()

read()

write()

fcntl()

HFS files

Only for z/OS

z/OS data sets

Program file operations

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-65. NFS support for UNIX System Services ES1011.0

Notes:

Network File System (NFS) is the most widely used solution for distributed files in a network. The DFSMS Network File System Server (NFSS) feature implements the NFS protocols of SUN Microsystems, Inc.

NFSS enables the host processor to act as a file server to authorized NFS clients in a TCP/IP network. NFSS allows remote access to data on the z/OS host from workstations, personal computers, or any other system in the network that is using NFS client software. A client system can be OS/2, DOS, AIX/2, AIX/6000, AIX/ESA, SUN/OS 3 and 4, any UNIX system with NFS client software, and z/OS.

The NFS server allows access to z/OS data sets and HFS files on the z/OS host as if they were local files on the client system. A workstation can mount a part of the hierarchical file system on the local file system (LFS), and thereafter create, delete, read, write, and otherwise treat that part of the file system as an extension to the local file system.

z/OS can be an NFS client. The NFS client support can be used to access data on another system. This facility can be used to share HFS file systems between multiple z/OS processors.


TCP/IPnetwork

z/OS

DFSMSNFS server

UNIX system services

NFS clients

HFS files

z/OS

NFS client NFS server

z/OS DS

OS/390

UNIX

OS/2

z/OS DS

NFS support for UNIX System Services

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-66. UNIX pipes ES1011.0

Notes:

Pipes are used to communicate an array of data between processes. Conceptually, pipes are like a sequential file, and one process can write to the pipe while another process will read from the pipe. There are two types of pipes: unnamed pipes and FIFO (named) pipes.

• Unnamed pipes (also referred to as just pipes) are defined by a pseudo-device type, and the pipes are buffered in memory by the pipe device driver. Unnamed pipes have the restriction that they can only be used by processes which have the same parent process. The pipe system call is used to invoke an unnamed pipe. Processes use read and write system calls to access the data in a pipe.

• FIFO (named) pipes have names and reside in the UNIX file system. Because of this they can be used for communication between any two processes. A FIFO pipe must be opened by the open system call. Only one process can access a FIFO pipe for reading or writing at a time.


Process Process

open()

write()

read()

open()

read()

pipe()

write()

Namedpipe (FIFO)

Unnamedpipe

UNIX pipes

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-67. The BPXBATCH utility ES1011.0

Notes:

The BPXBATCH utility provides support to run shell scripts or UNIX System Services application programs as z/OS batch jobs. BPXBATCH can be invoked in the following ways: • By JCL as a z/OS batch job. • As a command in TSO/E: BPXBATCH SH shell_command to run shell commands or

scripts, or BPXBATCH PGM pgm_name to run C executable files. • From within a REXX exec to run shell commands or C executable files. • Invoked by the REXX exec OSHELL to run non-interactive shell commands from the

TSO/E READY prompt. UNIX System Services C programs require that stdin, stdout, and stderr be defined. Many C functions also use this to define input and output. For BPXBATCH, the default for sdtin and stdout is /dev/null, and stderr is the same as stdout. This can be changed to file names by using the DD names STDIN, STDOUT, and STDERR. When using BPXBATCH to run shell commands in batch, redirection can be used, for example, BPXBATCH SH ps -el >>/tmp/ps.out. Environment variables can be specified by using the STDENV DD card, which can point to a hierarchical file, a z/OS data set, or the variables can be defined in JCL as in-stream data.


//SHELLJOB JOB (KARYN),MSGCLASS=A,MSGLEVEL=(1,1)//SHSTEP EXEC PGM=BPXBATCH//STDIN DD PATH='/u/smith/bin/myscript.in',PATHOPTS=(ORDONLY)//STDOUT DD PATH='/u/smith/bin/mystd.out',// PATHOPTS=(OWRONLY,OCREAT),PATHMODE=SIRWXU//STDERR DD PATH='/u/smith/bin/mystd.err',// PATHOPTS=(OWRONLY,OCREAT),PATHMODE-SIRWXU//STDENV DD *path=/bin:/u/usr/joeuser/*

Shell script in batch

Shell command/script as a TSO/E command

BPXBATCH SH rm -ir /u/smith/testdir/dbtest.c

OSHELL rm -ir /u/smith/testdir/dbtest.cor

The BPXBATCH utility

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-68. Submitting jobs: The submit command ES1011.0

Notes:

• /bin/submit has the same limitations as the REXX submit() function.

• UNIX files have a line limit of 1024 characters.

• The JCL itself still follows all JES conventions, including line limits of 71 characters.

• Multiple jobs can be submitted from one file, however, only the last jobID will be displayed.

• Data sets should not contain ANSI control characters.

Standard Input examples:

cat file.jcl | submit -jJOB32419

cat file2.jcl | submit file1.jcl - file3.jclJOB JOB32497 submitted from path 'file1.jcl'JOB JOB32499 submitted from stdinJOB JOB32504 submitted from path 'file2.jcl'


Submitting jobs: The submit command• Submit jobs to JES using REXX submit() function•Submit [-jq] [filename ...]

-j Only display jobID (when successful)-q Suppress error messages

– filename contains JCL input stream• unix/path/file

• Standard input• “//'full.PDS.name(member)'”

• “//'full.dataset.name'”

• Output contains both the job ID and the file name

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-69. Standard input, output, and error ES1011.0

Notes:

Once a shell command begins running, it has access to three files:

A shell user can redirect the input, output, and error files.

• To redirect output to a file, enter >filename at the end of a command, for example, sort -u file1 >outfile. If the file does not exist, it is created, and if it does exist, the output writes over any information in the file. If >>filename is specified, output is appended to the existing file.

Standard inputBy default, standard input is the keyboard. In the shell, the name for this file is stdin, and the file descriptor or identifier is 0.

Standard outputBy default, standard output is the screen. In the shell, the name for this file is stdout, and the file descriptor or identifier is 1.

Standard errorBy default, standard error is the screen. In the shell, the name for this file is stderr, and the file descriptor or identifier is 2.


Shellcommands

stdinfd=0

stdoutfd=1

stderrfd=2

read write write

Standard input, output, and error

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

• A command which normally takes input from the keyboard can be redirected to take input from a file. For example, mailx DEEJ <file where file is input to command mailx and is sent to the user DEEJ.

• Error messages can be redirected from the screen to a file using 2> (2 is the file descriptor). For example, sort -u >file1 2>errfile directs the output from the sort to file1 and the error messages to errfile.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-70. TSO and shell comparison ES1011.0

Notes:

• Command processing in the shell is similar to command processing for CLISTs. In combination with the shell utilities, the shell provides a programming environment as rich as the REXX environment in z/OS.

• Hierarchical files can be edited from z/OS using ISPF menus. The ISPF menus can be invoked by the TSO commands OEDIT/OBROWSE. In the shell, the ed editor can be used to edit HFS files.

• In z/OS, SDSF is used to monitor and control batch jobs. The TSO/E commands STATUS, CANCEL, and OUTPUT can also be used. In the shell, there are multiple commands to control jobs: ps, jobs, kill, fg, bg, and wait.

• Background jobs are submitted with the TSO/E command SUBMIT in a z/OS environment. In the shell, a command ended with an ampersand (&) runs in the background.


TSO and shell comparisonz/OS environment Activity Shell environment

Clist and REXX

ISPF

SDSF

Submit job

DFSMShsmTSM

Scan files and manipulate strings

Editing

Job control

Background job

Character conversion

Data management

Shell scriptsand REXX

ed/sed/vi/ispf

ps, jobs, kill

command and

tar, cpio, pax,TSM UNIX Client

CONVERT chcpEditing

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-71. What is a socket? ES1011.0

Notes:

In TCP/IP, sockets are used as communication end-points. A socket has a name and a network address. Sockets allow a program to communicate with another program across a TCP/IP network using file-like semantics.

A system connected to a TCP/IP network is identified by its Internet address. The Internet address is a unique 32-bit address consisting of a network number and a local address. Internet addresses are represented in dotted-decimal notation.

A port is an end point for communication between applications, generally referring to a logical connection. A port provides queues for sending and receiving data. Each port has a port number for identification. When a port number is combined with an Internet address, a socket address results.

A program accesses a socket by using functions like read(), write() and close() in the same way as I/O accesses to a hierarchical file. However, communicating in a network is more complex than dealing with file I/O. Because of this, the network I/O operations do not use the same I/O functions as used for files. When a socket is created, an integer called a socket descriptor (sd) is returned. The sd is used by the application to reference the socket.


Socket

IP address,Port ID

IP address9.12.1.38

IP address9.12.13.69TCP/IP TCP/IP

ApplicationA

Port2001

ApplicationB Port 2002

ApplicationC Port 2003

ApplicationD Port 2004

Port21

ApplicationA

Port 623

ApplicationB

Port 1003 ApplicationC

Port 1004 ApplicationD

What is a socket?

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-72. Sockets example ES1011.0

Notes:

Here is an example of a communication scenario using sockets:

1. Both the client and the server program use the socket() function to create a socket returning socket descriptor.

2. bind() assigns a name to a socket and makes it known in the network.

3. The server uses the listen() function to show that it is willing to receive communication. The bind() call defines the size of the queue for incoming requests.

4. The client uses the connect() function to initiate a connection to the server. On a successful return, the client socket is associated with the server.

5. The server uses the accept() function to accept a connection request. The server creates a new socket which is connected to the client socket. The original server socket is available to receive requests from other clients.

6. The write() function sends data from the client to the server.

7. The server uses the read() function to receive data from the client.


Server

Clientsocket()

bind()

listen()

accept()

read()

write()

close()

TCP/IPconnection

socket()

connect()

write()

read()

close()

Sockets example

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

8. The server uses the write() function to send data to the client.

9. The client uses the read() function to receive data from the server.

10.The close() function ends the conversation between the client and the server. Both the client and server must terminate their session.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-73. UNIX System Services security ES1011.0

Notes:

Security in a UNIX system is based on file access security, data encryption, and user logon security.

UNIX files and directories are protected by permission bits. Access is granted on three levels: owner, group, and world. World is all users in the system. Owner and group are defined when a file is created, and it can be changed by commands later. Users with common access permissions can be gathered in a group. File permission is defined for read, write, and execute access. The system checks a user's user ID for permission to access a file or directory.

Most UNIX systems provide capabilities to encrypt data stored in a file.

UNIX has two categories of users: user and superuser. Users must use a password to log in to a UNIX system. The users are defined in a file called /etc/passwd. The superuser bypasses all security checking and has access to all files. Only the superuser can perform authorized functions or commands, such as mounting a file system.


UNIX System Services security

uid=0uid=45 uid=60

uid=0

Security

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-74. UNIX System Services users and groups ES1011.0

Notes.

There are two categories of UNIX System Services shell users: superuser and user.

The superuser has special authority to perform certain tasks such as mounting and unmounting a file system. The superuser can also access all UNIX System Services services and all files in the hierarchical file system.

UNIX System Services users have a numerical user identifier. The superuser has a UID=0, while all other users have UIDs between 1 and 2147483647. The UNIX System Services users are z/OS users defined to SecureWay Security Server RACF with a new user segment containing their:

• UID (user identification number) • HOME (user's initial working directory in the HFS) • PROGRAM (the program pathname for the shell).

These users might or might not have TSO/E privileges.


BPX.SUPERUSER

SU

GreeneWhite

SmithUID=0

JonesUID=0

BrownUID=10

GreeneUID=35

WhiteUID=45

GreeneUID=0

WhiteUID=0

Group=sysGID=0

Group=prog1GID=25

Superusers

UNIX System Services users and groups

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

All users should have a unique UID, although multiple users with the same UID are supported. Superusers should have their own UID and then they can switch into superuser status when they need to perform authorized functions.

UNIX System Services users belong to groups similar to z/OS groups in SecureWay Security Server RACF. The z/OS groups defined in SecureWay Security Server RACF can be defined as UNIX System Services groups by adding a group identifier number (GID).

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E

Figure 6-75. File security ES1011.0

Notes:

In UNIX System Services, each user has a user ID (UID) and a group ID (GID). When a user creates a directory or a file, it is automatically associated with the user's UID, and the GID is set to the GID of the parent directory. A user's UID and GID can be defined in SecureWay Security Server RACF or an equivalent security product. The system verifies that a user or a program has access to a file by comparing the UID and GID in SecureWay Security Server RACF with the definitions in the hierarchical file system. There are three classes of users: • Owner: The user's UID must match the UID for the file. • Group: A member of any group whose GID matches the GID of the file. • Other: Anyone else. Access to files and directories is controlled by permission bits. Each file gets its permission bits set when it is created. The permission bits can be changed by the chmod command. There are three types of permissions that can be granted the owner, group, and others: • read: notated by r • write: notated by w • execute: notated by x


UID=103GID=42


UID=103GID=42

RACF

/usr/lib/lib.a

Hierarchicalfile system

UID=75 GID=42

Owner Group Otherrwx rwx r-x

Data..............

open()

Access OK

Check filepermission bits

VerifyUID/GID

File security

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure 6-76. Permission bits ES1011.0

Notes:

The permission bits have different meanings when related to files and directories, as this chart shows.

If you want to put a new file in a directory, you need both search and write access to the directory. The system needs to search the directory to determine if the entry is already there.

As you create files and directories, there are default permission bits defined. These differ depending on the method used to create the entity.


Directories

Read

Write

Execute

FilesRead or printcontents of file

Change/add/deletecontents of file

Execute file

Read (not search)directory

Change/add/deleteentries in directory

Search a directory

Permission bits

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Topic summaryHaving completed this topic, you should be able to:• Define how processes are created and used in UNIX• Describe the application services provided in UNIX System



xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (1 of 3)1. True or False: The shell is the interactive interface to UNIX System

Services.

2. What are the two TSO commands that invoke a UNIX shell? (Mark all that apply.)a. UNIX Callb. ISHELL

c. OMVS

d. TSOSTART

3. True or False: With z/OS, the shell environment can be accessed directly from workstations using rlogin and telnet commands, from ASCII terminals attached to a communication server, or from a TSO session.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Checkpoint (2 of 3)4. On the UNIX System Services system, the INETD system daemon

must be running to receive which of these requests? (Mark all that apply.)a. rloginb. ishellc. telnetd. mkdir

5. True or False: The UNIX System Services file system is hierarchical in structure in the same way as a UNIX file system.

6. A (blank) is a special kind of file which consists of the names of a set of files and other information about them.a. PIPEb. Filec. Directoryd. HFS data set

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Checkpoint (3 of 3)7. True or False: z/OS views an entire file system hierarchy as a

collection of HFS or zFS data sets.

8. A (blank) is a named unit of text or binary data information.a. Pipeb. Indexc. Mapd. Regular file

9. The two categories of UNIX System Services shell users are (blank). (Mark all that apply.)a. Privileged usersb. Superusersc. Usersd. Regular users

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




Uempty

E


Notes:


Tasks:1. Log on to TSO.2. Invoke the ISHELL.3. Display directories and

files.4. Create new files and

customize the ISHELL screen.

5. Log off.

Exercise

ISHELL and hierarchical file system

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.


Notes:


Unit summaryHaving completed this unit, you should now be able to:• Describe the main features of UNIX System Services in z/OS • Describe briefly the UNIX shell and utilities• Identify the various interfaces available to access Unix System

Services and how they can be invoked• Describe the hierarchical file system (HFS)

– Identify the file types and use• Define how processes are created and used in UNIX• Describe the application services provided in UNIX System



Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Appendix A. Checkpoint solutions

Unit 1, "Review of the z/Architecture and z/OS"

Solutions for Figure 1-37, "Checkpoint (1 of 3)," on page 1-60Yes, it's in a slightly different place... If you select the anchored frame and right click on the frame, select "Anchored Frame" ... The window that opens has the Object Attributes button

Solutions for Figure 1-37, "Checkpoint (1 of 3)," on page 1-60


Checkpoint solutions (1 of 3)1. Which operating systems are supported by the System z hardware?

(Mark all that apply.) a. OS/400 b. UNIX c. Windows NT d. zLinuxe. z/OSThe answers are zLinux and z/OS.

2. Which of the following are valid ways to partition z/Architecture system? (Mark all that apply.) a. Partitioned data sets b. Partitioned data sets extended c. Partitioning through VMd. N-way partitioning e. Virtual partitioning f. Logical partitioningThe answers are partitioning through VM and logical partitioning.xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Appendix A. Checkpoint solutions A-1

Student Notebook

.



Checkpoint solutions (2 of 3)3. Which of the following are functional groups of z/OS?

a. Systems management services b. Application enablement services c. UNIX System Services d. Communications server e. Distributed computing services f. All of the aboveThe answer is all of the above.

4. True or False: Virtual storage consists of 4 KB blocks called pages.The answer is true.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


A-2 z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


AP

E



Checkpoint solutions (3 of 3)5. True or False: z/OS must run on z/Architecture in 64 bit mode.

The answer is true.

6. True or False: The z/Architecture is a trimodal architecture capable of executing in 24-bit, 32-bit, or 64-bit addressing modes.The answer is false. In 24-bit, 31-bit, and 64-bit (not 32-bit).

7. True or False: A program cannot execute in the space storage between 2 GB and 16 EB.The answer is true. Programs cannot execute in this storage area, therefore it is limited to storing user data for programs that are loaded in the address space below 2 GB.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Unit 2, "An introduction to ISPF, ISPF/PDF, and RACF"



Checkpoint solutions (1 of 2)1. Which one of the following is not a major task of the Security Server RACF?

a. User identification and verification b. Resource authorization checking c. System access facilityd. Logging and reporting e. Administration

The answer is system access facility.

2. True or False: Security Server RACF protects data sets with generic and discrete profiles. If a data set does not have a discrete profile, a generic profile protect s it.The answer is false. It is protected only if a generic profile is defined or PROTECTALL is on.

3. True or False: If the universal access authority (UACC) PROTECTALL entry in auser's profile is set to Control or higher, the user has full access to all resources. The answer is false; data set profile, not user.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E



Checkpoint solutions (2 of 2)4. Which of these is not a method of navigating through the

ISPF dialogs?a. Action barb. TSO commandsc. Point-and-shootd. Option numbersThe answer is TSO commands.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Unit 3, "Working with ISPF/PDF"



Checkpoint solutions (1 of 3)1. Which are the standards for naming partition data sets? (Mark all that

apply.)a. Simple names connected with periodsb. Simple name must be eight characters in lengthc. Data set name can be a maximum of 54 characters in lengthd. Data set names can have up to 22 qualifiersThe answers are simple names connected with periods, simple name must be eight characters in length, and data set names can have up to 22 qualifiers.

2. True or False: The records in a sequential data sets can be processed randomly. The answer is false.

3. A partitioned data set (PDS) is divided into sequentially organized members.a. Directoriesb. Membersc. Charactersd. PartitionsThe answer is members.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E



Checkpoint solutions (2 of 3)4. What is an edit profile?

a. Set of characteristics that define the way you can edit a data setb. Description of the ISPF userc. Definition of the way you can edit a data setd. Definition of the data attributesThe answer is set of characteristics that define the way you can edit a data set.

5. True or False: In edit mode, to scroll up and down use F10 and F11.The answer is false.

6. The CREATE macro command creates a member of a partitioned data set from the data you are editing.a. Sequential data setb. Recordc. Memberd. Volume The answer is member.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.



Checkpoint solutions (3 of 3)7. The prefix area is the six-digit field at the beginning of each line. It is

used to process so-called line commands.a. Proceduresb. Clistc. Shell scriptsd. Line commandsThe answer is line commands.

8. True or False: CUT and PASTE is used to copy lines from one member or data set to another.The answer is true.

9. To browse the contents of a member prior to making any selection, use which line command?a. sb. bc. rd. e

The answer is b.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Unit 4, "Working with TSO/E"

Solutions for Figure 4-19, "Checkpoint," on page 4-38


Checkpoint solutions1. True or False: The TSO ALLOCATE command can be used to allocate

new and existing data sets for use.The answer is true.

2. True or False: You can use the SUBMIT command to submit one or more batch jobs for foreground processing.The answer is false.

3. True or False: You can issue TSO commands from SDSF. The answer is false.

4. Text messages can be sent to other TSO users using the SENDcommand.a. TRANSMIT

b. CALL

c. SEND

d. MESSAGE

The answer is SEND.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Unit 5, "Working with JCL"



Checkpoint solutions (1 of 4)1. Which one of the following is not a JES2 job processing phase?

a. Input phase b. Conversion phase c. Linking phased. Execution phase e. Output phase f. Purge phaseThe answer is linking phase. (Reference job entry subsystem visual.)

2. True or False: An internal reader is a program that can be used by programs to submit jobs or control statements to JES2.The answer is true. (Reference input phase visual.)

3. True or False: During the conversion phase, the JCL of any called procedure is added to the job’s JCL. The result is called external text.The answer is false. (Reference conversion phase visual.)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E



Checkpoint solutions (2 of 4)4. What is the purpose of a procedure library?

a. Contains frequently used JCL statements.b. To enable procedures to be imbedded in a job through a JCL procedure call.c. Both contains frequently used JCL statements and to enable procedures to be imbedded in a

job through a JCL procedure call.The answer is both contains frequently used JCL statements and to enable procedures to be imbedded in a job through a JCL procedure call. A procedure library contains frequently used JCL statements stored as procedures. The JCL of these procedures can be imbedded in a job through a procedure call. (Reference conversion phase visual.)

5. True or False: The job processing phases are also referred to as job steps.The answer is false. (Reference general layout of a job visual.)

6. Is this job card correct? If not, what is incorrect? //EDUCATION JOB 4824789, // CLASS=A, // MSGLEVEL=(1/1), // NOTIFY=USERID, // MSGCLASS=T,

The answer is no, the job card is not correct. EDUCATION exceeds the limit of eight characters for name fields. MSGLEVEL=(/)must be specified as MSGLEVEL=(1,1). No comma after MSGCLASS=T, as the job card does not continue. (Reference name field visual).

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.



Checkpoint solutions (3 of 4)7. What is wrong with the following JCL statements?

//step1 EXEC PGM=MYPGM,

//PARM='ABC'

//data DD DSN=USERID.TEST.DATA,DISP=SHR THIS IS THE INPUT DATA SET

//FOR THE MYPGM PROGRAM

The answer is JCL always must be in uppercase (STEP1 and DATA). A continued JCL statement must start with //followed by at least one blank // PARM. The continuation of a comment must be indicated by a character in position 72 or the next line should. (Reference statement continuation visual.) Note: The data set name is not in quotes for batch JCL DDstatements.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E



Checkpoint solution (4 of 4)8. Which JCL statement allows to define and describe a job’s input and

output data?a. EXEC

b. JOB

c. DD


The answer is DD.

9. Which JCL statement marks the beginning of a job’s step and identifies the program / procedure to be executed?a. EXEC

b. JOB

c. DD


The answer is EXEC. (Reference types of JCL statements and IF/THEN/ELSE/ENDIF statements visuals.)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Unit 6, "Working with UNIX System Services"



Checkpoint solutions (1 of 3)1. True or False: The shell is the interactive interface to UNIX System

Services.The answer is true.

2. What are the two TSO commands that invoke a UNIX shell? (Mark all that apply.)a. UNIX Callb. ISHELL

c. OMVS

d. TSOSTART

The answer are ISHELL and OMVS.

3. True or False: With z/OS, the shell environment can be accessed directly from workstations using rlogin and telnet commands, from ASCII terminals attached to a communication server, or from a TSO session.The answer is true.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E



Checkpoint solutions (2 of 3)4. On the UNIX System Services system, the INETD system daemon

must be running to receive which of these requests? (Mark all that apply.)a. rloginb. ishellc. telnetd. mkdirThe answers are rlogin, ishell, and telnet.

5. True or False: The UNIX System Services file system is hierarchical in structure in the same way as a UNIX file system.The answer is true.

6. A directory is a special kind of file which consists of the names of a set of files and other information about them.a. PIPEb. Filec. Directoryd. HFS data setThe answer is directory.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.



Checkpoint solutions (3 of 3)7. True or False: z/OS views an entire file system hierarchy as a

collection of HFS or zFS data sets.The answer is true.

8. A regular file is a named unit of text or binary data information.a. Pipeb. Indexc. Mapd. Regular fileThe answer is regular file.

9. The two categories of UNIX System Services shell users are superusers and users. (Mark all that apply.)a. Privileged usersb. Superusersc. Usersd. Regular usersThe answers are superusers and users.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Appendix B. z/OS documentation and information center

This is an optional topic on where to gather information and documentation on z/OS.

You will also learn more about the BookManager product and the lookat facility.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Appendix B. z/OS documentation and information center B-1

Student Notebook

.

Figure B-1. ISPF Primary Option Menu ES1011.0

Notes:

The option to select BookManager might be different at your installation.

On our system (ESSMVS1), the option to select Bookmanager on the primary option is: E.G (E= ITS menu, then G=BookManager/Read).


Menu Utilities Compilers Options Status Help ------------------------------------------------------------------------------

ISPF Primary Option Menu Location : Option ===> E

0 Settings Terminal and user parameters User ID . : TSOFT98 1 View Display source data or listings Time. . . : 10:20 2 Edit Create or change source data Terminal. : 3278 3 Utilities Perform utility functions Screen. . : 1 4 Foreground Interactive language processing Language. : ENGLISH 5 Batch Submit job for language processing Appl ID . : ISR 6 Command Enter TSO or Workstation commands TSO logon : STUDENT 7 Dialog Test Perform dialog testing TSO prefix: TSOFT98 8 LM Facility Library administrator functions System ID : MVS1 C Classes Menus for specific Classes MVS acct. : 1ES10G12 E ITS Menu ITS extended menu Release . : ISPF 5.9 S ITS Schedule ITS schedules SD SDSF Syslog Display and Search Facility 10 SCLM SW Configuration Library Manager 11 Workplace ISPF Object/Action Workplace



Menu Utilities Compilers Options Status Help --------------------------------------------------------

I/T Extended Option Menu Option ===> G

4 IPCS Interactive Problem Control System 5 RACF Resource Access Control Facility 6 ISMF Interactive Storage Management Fac. 7 ISHELL OpenEdition Shell 8 SDSF Syslog Display and Search Facility 9 SMP/E System Modification Program Extended A APPC APPC/MVS Administration B OMVS OpenEdition OMVS G Bookshelves BookManager/Read H HCD Hardware Configuration Dialogs R RMF Resource Measurement Facility W WLM GOAL Work Load Manager

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


B-2 z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


AP

E

Figure B-2. What is BookManager READ? ES1011.0

Notes:

BookManager is available on many platforms.

We look at the implementation on z/OS.


What is BookManager READ?• Application to manage, display, and search online books• Download online books to your workstation• Advantages:

– Flexibility– Always up to date– Indexed for fast search

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-3. Softcopy information ES1011.0

Notes:


• Hypertext linking• Internet access to pubs

• Online searching and viewing• High quality softcopy printing

SystemInformation

Library

ffffkjfjkfjfkdkfsdfdsfdfsd







Print

View

ViewLoad

z/OS IBMz/OSHomePage

Internet

z/OS

http://www.s390.ibm.com/os390

Softcopy information

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-4. Softcopy publications ES1011.0

Notes:

It is easy to follow an information trail from one book to another.


FRONT_2.2 Where to Find More Information Copyright IBM Corp. 1994, 2006Topic lines 1 to 34 of 52

The following table lists books that contain information related to the information in this book.

When this book references information in other books, the softcopy version of the book title is used. The following table shows the softcopy titles, complete titles, and order numbers of the books you might need while you are using this book.

Short Title Used in This Title Order Number Book

z/OS MVS Initialization OS/390 MVS Initialization SC28-1751 and Tuning Guide and Tuning Guide

z/OS MVS Initialization OS/390 MVS Initialization SC28-1752 and Tuning Reference and Tuning Reference

z/OS MVS JCL Reference OS/390 MVS JCL Reference GC28-1757

z/OS MVS JCL User's OS/390 MVS JCL User's GC28-1758 Guide Guide

Books GoTo Search Notes Services Options Help ------------------------------------------------------------------------

Command ===> __________________________________________ SCROLL ===> PAGE Linked to another book; close this book to return. CONTENTS Table of Contents Copyright IBM Corp. 1988, 2006

Topic lines 1 to 34 of 97 COVER Book Cover NOTICES Notices EDITION Edition Notice CONTENTS Table of Contents FIGURES Figures FRONT_1 Notices FRONT_1.1 Programming Interface Information FRONT_1.2 Trademarks PREFACE About This Book PREFACE.1 Who Should Use This Book PREFACE.2 Where to Find More Information PREFACE.3 Elements and Features in z/OS CHANGES Summary of Changes 1.0 Chapter 1. Storage Management Overview 1.1 Initialization Process 1.1.1 System Address Space Creation

Softcopy publications

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-5. Softcopy print ES1011.0

Notes:

BookManager allows you to print part or all of a book, and a series of services are provided.


z/OS softcopy print

Softcopy print

• Subset of:– AFP Font Collection– BookMaster– Document Composition Facility– Print Services Facility/MVS

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-6. Bookshelves ES1011.0

Notes:

Bookshelves are just a collection of logically related books.


Bookshelves• BookManager online books are organized into bookshelves.

• A single copy of a book can be part of as many bookshelves as you need.

• A bookshelf can be tailored to support your primary responsibility.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-7. What is familiar about online books? ES1011.0

Notes:


What is familiar about online books?• Online books viewed with the BookManager can contain all of

the parts you normally expect in a printed book, including:– Title page– Preface– Table of contents– Chapters– Tables, charts, and examples– Appendixes– Glossary– Bibliography– Index

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-8. And just like printed books ES1011.0

Notes:


And just like printed books • Online books allow you to:

– Open to a specific place.– Find the information you need by using the table of contents or the

index.– Turn directly to any topic.– Move forward and backward.– Make copies of parts of the book.– Save your place and return to it.– Consult a book while performing another task.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-9. What extras do you get with online books? ES1011.0

Notes:


What extras do you get with online books?• With online books, you can also:

– Search for any word or phrase.– Search for all the synonyms for the word you want.– Search through all the books on a bookshelf at one time.– View additional information for words in the text (for example, a word's

definition in the glossary).– Change the appearance of a book on your screen using color and

highlighting.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-10. What about IBM manuals? ES1011.0

Notes:


What about IBM manuals?• The soft-copy manuals for the BookManager products are

included with their products.

• IBM offers many other product manuals in soft-copy form. Most of these soft-copy product manuals can be found in collection kits. Collection kits are multiple, related soft-copy libraries usually distributed on CD-ROM.

• If you have product manuals in soft-copy form, you can use BookManager READ to display them instead of using printed copies.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-11. Getting around in BookManager READ ES1011.0

Notes:


Getting around in BookManager READ• BookManager READ/MVS provides easy-to-use panels to help

you access the information you need. You use panels to display, search, and manage your bookshelves and books. BookManager READ provides three primary types of panels.

• On entry you will:– Display a bookshelf list to work with the bookshelves available to you. – Display a bookshelf to work with all or selected books on a bookshelf. – Display a book to look at the contents of a single book.

• You can search at the bookshelf and book levels.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-12. From a bookshelf, you can: ES1011.0

Notes:


From a bookshelf, you can:• View a description of a book.• Open a book.• Create a new bookshelf.• Update a bookshelf by adding or deleting books.• Select a default bookshelf.• Search the bookshelf for specific words or phrases.• Select books to view or search.• Sort the books by name, date, title, or document number.• Open a different bookshelf.• Set display, search, print, edit, and copy options for books.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-13. Using panels ES1011.0

Notes:


Using panels• Each BookManager READ panel contains several areas:

– An action bar– A scroll field– A command line– A status line– A function key area

• You can select any action bar item by placing the cursor on the item and pressing Enter. Additional choices for Action bar items are displayed in pull-down menus.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-14. ISPF Primary Option Menu ES1011.0

Notes:

Remember, your installation might use different options.

The MOP CLP system (ESSMVS1) has BookManager on a subordinate panel. (E;G)


ISPF Primary Option MenuMenu Utilities Compilers Options Status Help

------------------------------------------------------------------------------

ISPF Primary Option Menu Location :

Option ===> E

0 Settings Terminal and user parameters User ID . : TSOFT98

1 View Display source data or listings Time. . . : 10:20

2 Edit Create or change source data Terminal. : 3278

3 Utilities Perform utility functions Screen. . : 1

4 Foreground Interactive language processing Language. : ENGLISH

5 Batch Submit job for language processing Appl ID . : ISR

6 Command Enter TSO or Workstation commands TSO logon : STUDENT

7 Dialog Test Perform dialog testing TSO prefix: TSOFT98

8 LM Facility Library administrator functions System ID : MVS1

C Classes Menus for specific Classes MVS acct. : 1ES10G12

E ITS Menu ITS extended menu Release . : ISPF 5.9

S ITS Schedule ITS schedules


10 SCLM SW Configuration Library Manager

11 Workplace ISPF Object/Action Workplace


xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-15. Go to BookManager in ISPF ES1011.0

Notes:


Go to BookManager in ISPF


--------------------------------------------------------

I/T Extended Option Menu

Option ===> G

4 IPCS Interactive Problem Control System

5 RACF Resource Access Control Facility

6 ISMF Interactive Storage Management Fac.

7 ISHELL OpenEdition Shell

8 SDSF Syslog Display and Search Facility

9 SMP/E System Modification Program Extended

A APPC APPC/MVS Administration

B OMVS OpenEdition OMVS

G Bookshelves BookManager/Read

H HCD Hardware Configuration Dialogs

R RMF Resource Measurement Facility

W WLM GOAL Work Load Manager

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-16. Copyright notice ES1011.0

Notes:

We are IN.

Take a few moments now to read the Copyright notice.


BookManager(*) READ/MVS Release 3.0

Licensed Materials - Property of IBM (*) 5695-046 (C) Copyright IBM Corp. 1990, 1994. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Materials displayed or reproduced by this program may be protected by copyright or contract restrictions of IBM and/or others. The user is responsible for having permission to display or reproduce such materials and for including applicable copyright notices and legends.

If any IBM machine-readable documentation is accessed or reproduced by or through this program, IBM grants limited permission to licensees of the IBM machine-readable documentation to make hardcopy or other reproductions thereof, provided that each such reproduction shall carry the IBM copyright notice and, where applicable, the IBM proprietary legends and use of the reproduction shall be governed by the applicable license for IBM machine-readable documentation.

*BookManager is a trademark of International Business Machines Corporation and IBM is a registered trademark of International Business Machines Corporation.

Press ENTER to continue, F1 for help, or F3 to exit the program.

F1=Help F2=Split F3=Exit F9=Swap F12=Cancel

Copyright notice

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-17. Unordered Bookshelf List ES1011.0

Notes:


Books View Options Help

------------------------------------------------------------------------------

Command ===> ________________________________________________ SCROLL ===> CSR

Bookshelf List

Shelves 1 to 22 of 170

Shelf Name Description

__ EZ2VM11B All-VM Disc 1 Bookshelf (z/VM V4R4, System Control)

__ EZ2VM21B All-VM Disc 2 Bookshelf (Software Products)

__ EZ2VM306 All-VM Disc 3 Bookshelf (z/VM V3R1, z/VM V4R2, z/VM V4R3)

__ EZ2ZO10K All-z/OS Disc 1 Bookshelf (V1R9.0 Base Elements, Optional Featur

__ EZ2ZO20E All-z/OS Disc 2 Bookshelf (V1R9.0 Base Elements and Optional Fea

__ AITS An ITS Install

__ IPH0BK06 AnyNet Workstation Products

__ EZ2VMS33 Booklet for VM Collection, August 2003 Bookshelf

__ EOXEOY07 BookManager READ/MVS and BUILD/MVS V1.3.0

__ DFHPUSH0 CICS Transaction Server for z/OS 2.2

__ IGYSH208 COBOL for OS/390 & VM V2.1 (VisualAge)

__ IGYSH210 COBOL for OS/390 & VM V2.2

__ DM1SH000 Data Management Tools for DB2 March 2002

__ DMTSH000 Data Management Tools for OS/390

__ HA3BKS10 Data Stream and Object Architectures

__ DB2BS001 DB2 Administration Tools

__ DSNSHH10 DB2 UDB for OS/390 and z/OS V7

__ DSNSHJ10 DB2 UDB for z/OS V8 Licensed

Unordered Bookshelf List

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-18. Select sort order ES1011.0

Notes:


Books View Options Help ------ EsssssssssssssssssssssssssssssssssN -----------------------------------

e 4 1. All e Comman e 2. Some... e __________________ SCROLL ===> CSR

e 3. Sort by name e e 4. Sort by description e ist e 5. Refresh F5 e Shelves 1 to 22 of 170

She DsssssssssssssssssssssssssssssssssM __ EZ2VM11B All-VM Disc 1 Bookshelf (z/VM V4R4, System Control) __ EZ2VM21B All-VM Disc 2 Bookshelf (Software Products) __ EZ2VM306 All-VM Disc 3 Bookshelf (z/VM V3R1, z/VM V4R2, z/VM V4R3) _ EZ2ZO10K All-z/OS Disc 1 Bookshelf (V1R9.0 Base Elements, Optional Featur

__ EZ2ZO20E All-z/OS Disc 2 Bookshelf (V1R9.0 Base Elements and Optional Fea__ AITS An ITS Install __ IPH0BK06 AnyNet Workstation Products __ EZ2VMS33 Booklet for VM Collection, August 2003 Bookshelf__ EOXEOY07 BookManager READ/MVS and BUILD/MVS V1.3.0 __ DFHPUSH0 CICS Transaction Server for z/OS 2.2 __ IGYSH208 COBOL for OS/390 & VM V2.1 (VisualAge) __ IGYSH210 COBOL for OS/390 & VM V2.2 __ DM1SH000 Data Management Tools for DB2 March 2002 __ DMTSH000 Data Management Tools for OS/390 __ HA3BKS10 Data Stream and Object Architectures __ DB2BS001 DB2 Administration Tools __ DSNSHH10 DB2 UDB for OS/390 and z/OS V7 __ DSNSHJ10 DB2 UDB for z/OS V8 Licensed __ EQN0BK03 DCAF V1R3.1 __ DSM0PA03 DCF V1R4.0

Select sort order

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-19. Sorted Bookshelf List ES1011.0

Notes:


Books View Options Help ------------------------------------------------------------------------------Command ===> ________________________________________________ SCROLL ===> PAGE

Bookshelf List Shelves 1 to 20 of 135

Shelf Name Description __ ADSM ADSM ADSTAR Distributed Storage Manager __ ADSM ADSM ADSTAR Distributed Storage Manager - Data Access Service __ ADSM ADSM ADSTAR Distributed Storage Manager V2 <=== new __ ADSM ADSM V2R1 MVS Bookshelf __ A_MSG Alle Messages __ ASM Assembler-H V2 __ BOOKMGR BOOKMANAGER BUILD __ BOOKMGRR BOOKMANAGER READ __ BKMAST4 BOOKMASTER R4 __ DCF Bookshelf for DCF 4.0 on Printing a __ CANDLE Candle Computer Report for IBM __ CICS CICS/ESA V4R1 Bookshelf __ COBOL COBOL and CICS/VS CCA Release 2.0 Bookshelf __ COBOL COBOL for MVS & VM Bookshelf __ IGYSH202 COBOL for OS/390 & VM V2.1 Book Shelf __ COBOL COBOL/SF V3R1 Bookshelf __ DSNSH0F2 DB2 for z/OS V5 Bookshelf __ DSNSH0N1 DB2 for z/OS V5 Server Bookshelf __ DGO15A02 DB2 PM FOR z/OS V5 __ DFDSS DFDSS 2.5.0 F1=Help F2=Split F3=Exit F5=Refresh F6=Describe F7=Bkwd F8=Fwd F9=Swap F10=Actions F11=Retrieve F12=Cancel

Sorted Bookshelf List

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-20. Select a bookshelf ES1011.0

Notes:


Books View Options Help ------------------------------------------------------------------------------


Bookshelf List Shelves 1 to 22 of 170

Shelf Name Description __ EZ2VM11B All-VM Disc 1 Bookshelf (z/VM V4R4, System Control) __ EZ2VM21B All-VM Disc 2 Bookshelf (Software Products) __ EZ2VM306 All-VM Disc 3 Bookshelf (z/VM V3R1, z/VM V4R2, z/VM V4R3) /_ EZ2ZO10K All-z/OS Disc 1 Bookshelf (V1R9.0 Base Elements, Optional Featu__ EZ2ZO20E All-z/OS Disc 2 Bookshelf (V1R9.0 Base Elements and Optional Fe__ AITS An ITS Install __ IPH0BK06 AnyNet Workstation Products __ EZ2VMS33 Booklet for VM Collection, August 2003 Bookshelf__ EOXEOY07 BookManager READ/MVS and BUILD/MVS V1.3.0 __ DFHPUSH0 CICS Transaction Server for z/OS 2.2 __ IGYSH208 COBOL for OS/390 & VM V2.1 (VisualAge) __ IGYSH210 COBOL for OS/390 & VM V2.2 __ DM1SH000 Data Management Tools for DB2 March 2002 __ DMTSH000 Data Management Tools for OS/390 __ HA3BKS10 Data Stream and Object Architectures __ DB2BS001 DB2 Administration Tools __ DSNSHH10 DB2 UDB for OS/390 and z/OS V7 __ DSNSHJ10 DB2 UDB for z/OS V8 Licensed

Select a bookshelf

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-21. Bookshelf displayed ES1011.0

Notes:


Books View Search Group Options Help ------------------------------------------------------------------------------


EZ2ZO10K Bookshelf

Books 1 to 21 of 296 Book Name Book Title Date

__ DGT2J103 z/OS DFSMS Software Support for IBM System Storage TS 06/10/24 __ DGT2E100 z/OS DFSMS Software Support for IBM TotalStorage Tape 02/06/28 __ IEA2UN71 z/OS Support for Unicode: Using Unicode Services 08/01/18 __ BPXBB100 z/OS V1R1.0 C Curses 01/01/19 __ FCXD2A00 z/OS V1R1.0 Distributed File Service Customization 02/01/13 __ DGT2M510 z/OS V1R1.0 Distributed FileManager Guide and Referen 05/07/15 __ EUVA2A00 z/OS V1R1.0 DCE Administration Guide 01/01/19 __ EUVA3A00 z/OS V1R1.0 DCE App Dev Gde: Core Comp 01/01/15 __ EUVA4A00 z/OS V1R1.0 DCE App Dev Gde: Dir Svces 01/01/19 __ EUVA5A00 z/OS V1R1.0 DCE App Dev Gde: Intro & Style 01/01/15 __ EUVA6A00 z/OS V1R1.0 DCE App Dev Ref Vols 1 & 2 01/01/15 __ EUVA7A00 z/OS V1R1.0 DCE Command Reference 01/01/12 __ EUVA8A00 z/OS V1R1.0 DCE Configuring and Getting Started 01/01/12 __ EUVA1A00 z/OS V1R1.0 DCE Introduction 01/01/12 __ EUVA9A00 z/OS V1R1.0 DCE Messages and Codes 01/01/12 __ EUVB4A00 z/OS V1R1.0 DCE Planning 01/01/12 __ EUVB1A00 z/OS V1R1.0 DCE User's Guide 01/01/12 __ IEA2I810 z/OS V1R1.0 MVS JES Common Coupling Services 06/06/20

Bookshelf displayed

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-22. Book selected ES1011.0

Notes:


Books View Search Group Options Help ------------------------------------------------------------------------------


EZ2ZO10K Bookshelf

Books 211 to 231 of 296Book Name Book Title Date

__ IEA2G281 z/OS V1R9.0 MVS System Management Facilities (SMF) 08/01/22__ IEA2M181 z/OS V1R9.0 MVS System Messages, Vol 1 (ABA-AOM) 08/01/24__ IEA2MA81 z/OS V1R9.0 MVS System Messages, Vol 10 (IXC-IZP) 08/01/24__ IEA2M281 z/OS V1R9.0 MVS System Messages, Vol 2 (ARC-ASA) 08/01/25__ IEA2M381 z/OS V1R9.0 MVS System Messages, Vol 3 (ASB-BPX) 08/01/25__ IEA2M481 z/OS V1R9.0 MVS System Messages, Vol 4 (CBD-DMO) 08/01/24__ IEA2M581 z/OS V1R9.0 MVS System Messages, Vol 5 (EDG-GFS) 08/01/24__ IEA2M681 z/OS V1R9.0 MVS System Messages, Vol 6 (GOS-IEA) 08/01/25/_ IEA2M781 z/OS V1R9.0 MVS System Messages, Vol 7 (IEB - IEE) 08/01/25__ IEA2M881 z/OS V1R9.0 MVS System Messages, Vol 8 (IEF-IGD) 08/01/24__ IEA2M981 z/OS V1R9.0 MVS System Messages, Vol 9 (IGF-IWM) 08/01/24__ IEA2F250 z/OS V1R9.0 MVS Using the Subsystem Interface 07/05/03__ CDSA1A10 z/OS V1R9.0 OCSF Application Programming 07/05/04__ E0Z1P160 z/OS V1R9.0 System z Platform Test Report for z/OS an 07/12/05__ GSKA1A50 z/OS V1R9.0 System SSL Programming 07/05/08__ CBCMG160 z/OS V1R9.0 XL C/C++ Compiler and Run-Time Migration 07/06/20__ CBCLR170 z/OS V1R9.0 XL C/C++ Language Reference 07/06/01__ CBCDG150 z/OS V1R9.0 XL C/C++ Messages 07/05/25

Book selected

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-23. Book displayed ES1011.0

Notes:


Books GoTo Search Notes Services Options Help ------------------------------------------------------------------------------

Command ===> ________________________________________________ SCROLL ===> PAGE

CONTENTS Table of Contents © Copyright IBM Corp. 1988, 2008Topic lines 1 to 23 of 43

COVER Book Cover NOTICES Notices EDITION Edition Notice CONTENTS Table of Contents PREFACE About this document PREFACE.1 Who should use these MVS System Messages documents PREFACE.2 How to use these documents PREFACE.3 Where to find more information PREFACE.3.1 Where to find the most current message information PREFACE.3.2 Information updates on the web PREFACE.3.3 Using LookAt to look up message explanations PREFACE.3.4 Using IBM Health Checker for z/OS CHANGES Summary of changes 1.0 Chapter 1. Introduction 1.1 Message format 1.1.1 Format of the message body 1.1.2 Messages sent to MCS/SMCS consoles 1.1.3 Messages sent to hardcopy log in JES2 system 1.1.4 Messages sent to hardcopy log in JES3 system 1.1.5 Messages sent to the job log, to other data sets, and to dis1.1.6 Truncated data in multi-line messages 1.2 Message description 1.2.1 Description items F1=Help F2=Split F3=Exit F4=Unlink F5=Notes F6=Review F7=Bkwd F8=Fwd F9=Swap F10=Actions F11=Retrieve F12=Cancel

Book displayed

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-24. Scroll down ES1011.0

Notes:




CONTENTS Table of Contents © Copyright IBM Corp. 1988, 2008 Topic lines 24 to 43 of 43

1.2.2 Routing codes 1.2.3 Descriptor codes 1.3 Message directory 1.4 Building your own message library 1.4.1 Basic documents 1.4.2 Optional documents 1.4.3 CD-ROM collection 1.5 Translating messages 1.6 Finding changes to system message texts 2.0 Chapter 2. IEB Messages 3.0 Chapter 3. IEC Messages 4.0 Chapter 4. IEE Messages A.0 Appendix A. Accessibility A.1 Using assistive technologies A.2 Keyboard navigation of the user interface A.3 z/OS information BACK_1 Notices BACK_1.1 Trademarks BACK_2 Communicating Your Comments to IBM COMMENTS Reader's Comments -- We'd Like to Hear from You

F1=Help F2=Split F3=Exit F4=Unlink F5=Notes F6=Review F7=Bkwd F8=Fwd F9=Swap F10=Actions F11=Retrieve F12=Cancel

Scroll down

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-25. Cursor select ES1011.0

Notes:

Move the cursor to the topic number, and press Enter.




CONTENTS Table of Contents © Copyright IBM Corp. 1988, 2008Topic lines 24 to 43 of 43

1.2.2 Routing codes 1.2.3 Descriptor codes 1.3 Message directory 1.4 Building your own message library 1.4.1 Basic documents 1.4.2 Optional documents 1.4.3 CD-ROM collection 1.5 Translating messages 1.6 Finding changes to system message texts 2.0 Chapter 2. IEB Messages 3.0 Chapter 3. IEC Messages 4.0 Chapter 4. IEE Messages A.0 Appendix A. Accessibility A.1 Using assistive technologies A.2 Keyboard navigation of the user interface A.3 z/OS information BACK_1 Notices BACK_1.1 Trademarks BACK_2 Communicating Your Comments to IBM COMMENTS Reader's Comments -- We'd Like to Hear from You

Cursor select

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-26. Topic displayed ES1011.0

Notes:




2.0 Chapter 2. IEB Messages © Copyright IBM Corp. 1988, 2008 Topic lines 1 to 23 of 576

Subtopics 2.1 IEBA01I 2.2 IEBA02I 2.3 IEBA03I 2.4 IEBA04I 2.5 IEBA05I 2.6 IEBA06I 2.7 IEBA07I 2.8 IEBA08I 2.9 IEBA09I 2.10 IEBA10I 2.11 IEBA11I 2.12 IEBA12I 2.13 IEBA13I 2.14 IEBA14I 2.15 IEBA15I 2.16 IEBA16I 2.17 IEBA17I 2.18 IEBA18I 2.19 IEBA19I 2.20 IEBA20I 2.21 IEBA21I


Topic displayed

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-27. Go back to table of contents ES1011.0

Notes:

Move your cursor to the action bar choice, and press Enter.


Books GoTo Search Notes Services Options Help ------ EssssssssssssssssssssssssssssssssssN ----------------------------------

e 2 1. Topic... e Comman e 2. Table of contents e _________________ SCROLL ===> PAGE

e 3. *ndex e 2.0 C e 4. *igure list e © Copyright IBM Corp. 1988, 2008

e 5. *able list e Topic lines 1 to 23 of 576 e 6. Revisions... e

Sub e 7. Previous link or reference e 2.1 e 8. Topics seen list... e 2.2 e 9. Retrace topic path e 2.3 e 10. *ookmark list... e 2.4 DssssssssssssssssssssssssssssssssssM 2.5 IEBA05I 2.6 IEBA06I 2.7 IEBA07I 2.8 IEBA08I 2.9 IEBA09I 2.10 IEBA10I 2.11 IEBA11I 2.12 IEBA12I 2.13 IEBA13I 2.14 IEBA14I 2.15 IEBA15I 2.16 IEBA16I 2.17 IEBA17I 2.18 IEBA18I 2.19 IEBA19I 2.20 IEBA20I 2.21 IEBA21I


Go back to table of contents

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-28. Select exit (1 of 2) ES1011.0

Notes:


Books GoTo Search Notes Services Options Help EsssssssssssssssssssssssssssssssssssssN --------------------------------------e 8 1. Open a book... e e 2. Open a bookshelf... e _____________________ SCROLL ===> PAGE e 3. List books... e e 4. List bookshelves... e © Copyright IBM Corp. 1988, 2008 e 5. Describe... e Topic lines 22 to 43 of 43 e 6. Send... e e 7. Close book... F3 e e 8. Exit BookManager... e DsssssssssssssssssssssssssssssssssssssM 1.3 Message directory 1.4 Building your own message library 1.4.1 Basic documents 1.4.2 Optional documents 1.4.3 CD-ROM collection 1.5 Translating messages 1.6 Finding changes to system message texts 2.0 Chapter 2. IEB Messages 3.0 Chapter 3. IEC Messages 4.0 Chapter 4. IEE Messages A.0 Appendix A. Accessibility A.1 Using assistive technologies A.2 Keyboard navigation of the user interface


Select exit (1 of 2)

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-29. Select exit (2 of 2) ES1011.0

Notes:


Books GoTo Search Notes Services Options Help

------------------------------------------------------------------------------

C EsssssssssssssssssssssssssssssssssssssN ___________________ SCROLL ===> PAGE

e Exit BookManager e

C e e © Copyright IBM Corp. 1988, 2008

e Do you want to exit BookManager? e Topic lines 22 to 43 of 43

1 e 1 1. Yes e

1 e 2. No e

1 e e

1 e CAUTION: e

1 e There are open books. Existing e

1 e closing bookmarks will be saved. e library

1 e No new closing bookmarks will be e

1 e set. e

1 e e

1 e e

1 e F1=Help F2=Split F9=Swap e message texts

2 e F12=Cancel e

3 DsssssssssssssssssssssssssssssssssssssM

4.0 Chapter 4. IEE Messages

A.0 Appendix A. Accessibility

A.1 Using assistive technologies

F1=Help F2=Split F3=Exit F4=Unlink F5=Notes F6=Review

F7=Bkwd F8=Fwd F9=Swap F10=Actions F11=Retrieve F12=Cancel

Select exit (2 of 2)

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-30. z/OS Basics Skills Info Center ES1011.0

Notes:

With the Information Center, users can view, browse, and search online information. The Information Center is built upon open source software developed by the Eclipse Project (www.eclipse.org). It can display content that has been packaged as an Eclipse documentation plug-in.

The Information Center uses an embedded web application server to handle content requests in the system. This embedded web server uses a random port to avoid port conflicts between applications.

Product or application developers can create their own documentation plug-ins and integrate them in the information center for viewing by their users. To learn about creating and packaging documentation plug-ins, see the Eclipse Project's website: www.eclipse.org.


z/OS Basics Skills Info Center• Information for on-the-job training:

– z/OS basics– Application development basics– Systems programmer basics– Networking basics– Security basics– Security basics

• Interactive exercises to reinforce learning and test knowledge

http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-31. z/OS Info Center ES1011.0

Notes:

From this page, you can learn about:

z/OS Concepts: Introduction to z/OS and the mainframe environment.

Application Programming: Introduce the tools and utilities for developing a simple program to run on z/OS. The topics that follow guide the student through the process of application design, choosing a programming language, and using a runtime environment.

Networking on z/OS: In this course, we use simplified examples and focus mainly on basic system functions. Hands-on exercises are provided throughout the course to help students explore the mainframe style of computing.

• At the end of this course, you will know: - Concepts of mainframe-based data communications - Methods for implementing TCP/IP on the z/OS operating system - Methods for implementing SNA on the z/OS operating system - Basic skills in network problem determination


z/OS Info Center

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

z/OS Security: In this part, we examine the mechanisms in z/OS that provide security for its users and applications.

Systems Programming on z/OS: In this part, we reveal the inner workings of z/OS with discussions of system libraries, change management, and procedures for starting (IPLing) and stopping a z/OS system. This part also includes topics on hardware details and virtualization, and the clustering of multiple z/OS systems in a sysplex.

The Introduction to JCL course consists of several units to help you learn about and use JCL on the job.

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-32. IBM Education Assistant ES1011.0

Notes:

The website is: http://www-306.ibm.com/software/info/education/assistant

IBM Education Assistant is a collection of multimedia educational modules designed to help you gain a better understanding of IBM software products. Online education on z/OS performance, tuning, installation, and best practices tips.

Clicking the z/OS IEA link will take you to the z/OS IEA web site, select z/OS operating systems.

http://publib.boulder.ibm.com/infocenter/ieduasst/stgv1r0/topic/com.ibm.iea.zos/zos_coverpage.html

V1R11 Theme View:

• V1R11 Installation and migration • Simplified monitoring and management - Ease of use - Availability -Simplification • Storage management • Application enablement • Security


IBM Education Assistant• IBM Education Assistant provides narrated presentations, flash

simulations, tutorials, and resource links to help you use IBM software products more successfully and effectively.

• On-line education on z/OS performance,tuning, and best practices tips.

Go to ibm.com/software/info/education/assistant/.Click on Systems and Servers.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-33. z/OS Internet Library and Library Center ES1011.0

Notes:

z/OS Library Centers have been replaced by z/OS Information Centers starting with z/OS V1R11. Information Centers are indexed by Google and other search engines which make finding z/OS documentation even easier.

Internet Library http://www-03.ibm.com/systems/z/os/zos/bkserv and LibraryCenter

LookAt http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat

Softcopy Website http://www.ibm.com/servers/eserver/zseries/softcopy

Softcopy Reader http://www.ibm.com/software/office/bkmgr/softcopyread.html V3.7 for Windows

Softcopy http://www.ibm.com/support/docviewss?doc=4000251&org=SW&rs=4Reader V3.7 for Linux


z/OS Internet Library and Library Center• http://www-03.ibm.com/systems/z/os/zos/bkserv/

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-34. Online Message Lookup ES1011.0

Notes:

LookAt is an online facility that allows you to look up explanations for z/OS messages, system abends, and some codes. Using LookAt to find information is faster than a conventional search because in most cases LookAt goes directly to the message explanation.

You can access LookAt from the Internet at:

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html

or from anywhere in z/OS where you can access a TSO command line (for example, TSO prompt, ISPF, z/OS UNIX System Services running OMVS).

Why LookAt?

• Message information is hard to find

• Messages are scattered across large product libraries

• zOS alone has 420 manuals in the base

• Over 2000 manuals across IBM applications


Online Message Lookup

http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

• Systems Programmers had to “know” product message prefixes

• Wanted EASY access to information that is both current and accurate

What is LookAt?

• A Free Message LookUp Facility

• LookAt provides fast access to IBM supplied zSeries message information

• LookAt currently supports Message Information for OS/390, zOS, zVM, VSE

• Over 600,000 IBM messages

• Provides an overall index to Message explanations

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Figure B-35. LookAt for messages and abend codes ES1011.0

Notes:

In the message ID field, you enter one of the following:

• The complete message ID for a message to see a specific message. • Part of a message ID with an asterisk (*) as a wildcard character if you do not know the

entire ID or if you want to see a set of related message IDs. The “*” can represent zero or more character positions. You can place a wildcard character at the beginning, in the middle, or at the end of a message ID.

• When you are looking for various codes, if you usually prefix the code with the letters S, ABEND, WSC, or WAIT, LookAt will still attempt to locate the code for you. - IEA200I: LookAt opens directly to this message. - IEA21*: LookAt finds 12 messages that match this pattern in three different books. - IEA21*A: LookAt finds 3 messages that match this pattern in tw0 different books. - +012: LookAt opens directly to the return code. - EQA1000I: I LookAt opens directly to the message. - 0072: LookAt opens to this ABEND code. - 9004: Opens a book to the top of the chapter that contains this code. - 0123: Gets a list of books that contain this code.


LookAt for messages and abend codes

IEA200I ???

IMS?

CICS DB2

Base z/OS

LookAt

Explanation: During system initialization, thesystem could not use adata set member that

was to contain analternate version of the master scheduler JCL.?

??

IEA200I

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




AP

E

Figure B-36. Exercise ES1011.0

Notes:


Tasks:1. Log on to TSO2. In the BookManager online

manuals, read:• Function Key Settings• Going to a Particular Topic

or Book Part• Reviewing Topics You Have

Seen• Placing a Temporary Bookmark• Placing a Closing Bookmark• Going to a Bookmark• Copying a Topic or Topics• Printing a Topic or Topics

3. Log off

Exercise

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.



Student Notebook

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C




bibl

E

Bibliography

Booklets:

None.

Manuals:

SC26-7397 z/OS V1R11.0 DFSMS Introduction

GA22-7502 z/OS Introduction and Release Guide

GA22-7504 z/OS Planning for Installation

SA22-7500 z/OS V1R11.0 Information Roadmap

SA22-7597 z/OS V1R11.0 MVS JCL Reference

SA22-7598 z/OS V1R11.0 MVS JCL User’s Guide

SA22-7535 z/OS V1R11.0 JES2 Introduction

SA22-7551 z/OS V1R11.0 JES3 Introduction

SA22-7661 z/OS V1R11.0 Parallel Sysplex Overview: An Introduction to Data Sharing

SA22-7784 z/OS V1R11.0 TSO/E General Information (GIM)

SA22-7787 z/OS V1R11.0 TSO/E Primer

SA22-7782 z/OS V1R11.0 TSO/E Command Reference

GC35-0033 Device Support Facilities R17 (ICKDSF r17) Guide and Reference

SA22-7832 z/Architecture Principles of Operation

SA22-7670 z/OS V1R11.0 SDSF Operation and Customization

SC26-7527 z/OS DFSORT Getting Started

SC26-7409 z/OS V1R11.0 DFSMS Managing Catalogs

SA22-7643 z/OS V1R11.0 MVS Program Management: User’s Guide and Reference

SC26-7414 z/OS V1R11.0 DFSMSdfp Utilities

SC26-7410 z/OS V1R11.0 DFSMS Using Data Sets

SC34-4822 z/OS V1R11.0 ISPF User’s Guide Vol I

SC34-4823 z/OS V1R11.0 ISPF User’s Guide Vol II

SC34-4820 z/OS V1R11.0 ISPF Edit and Edit Macros

SA22-7801 z/OS V1R11.0 UNIX System Services User’s Guide

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Bibliography X-1

Student Notebook

.

SA22-7806 z/OS V1R11.0 Using REXX and z/OS UNIX System Services

SC38-2034 BookManager READ/MVS Displaying Online Books

SA22-7637 z/OS V1R11.0: MVS System Messages Volume 7 (IEB - IEE)

SA22-7638 z/OS V1R11.0: MVS System Messages Volume 8 (IEF - IGD)

SA22-7626 z/OS V1R11.0: MVS System Codes

Technical Bulletins:

SG24-7516 IBM System z10 Enterprise Class Technical Guide

SG24-7832 IBM zEnterprise System Technical Introduction

SG24-7333 IBM System z Strengths and Values

SG24-6366 Introduction to the New Mainframe: z/OS Basics

SG24-7834 z196 Configuration Setup

SG24-7832 z196 Technical Introduction

SG24-7833 z196 Technical Guide

SG24-5444 IBM System z Connectivity Handbook

Web URLs:

z/OS Web site http://www.ibm.com/systems/z/os/zos/

General Q & A http://www.ibm.com/systems/z/faq/

Previously announced statements of direction

http://www.ibm.com/systems/z/os/zos/zos_sods.html

z/OS Internet Library http://www.ibm.com/systems/z/os/zos/bkserv/

z/OS Basic Skills Information Centerhttp://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp

z/OS 1.12 information center

http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp

IBM Open Class Library Transition Guide http://publibz.boulder.ibm.com/epubs/pdf/cbcit100.pdf

Online version of z/OS V1.12 reference manuals in PDF format http://www-03.ibm.com/systems/z/os/zos/bkserv/r12pdf/

z/OS V1R12 publications http://www-03.ibm.com/systems/z/os/zos/bkserv/v1r12books.html

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C


X-2 z/OS Fundamentals © Copyright IBM Corp. 2001, 2013


bibl

E

Installation information for z/OS V1.12 http://www.ibm.com/servers/eserver/zseries/zos/installation/

z/OS V1R12 Introduction and Release Guide

http://publibz.boulder.ibm.com/cgi-bin/

Descriptions of courses worldwide

http://www.ibm.com/services/learning

z/OS downloads http://www.ibm.com/servers/eserver/zseries/zos/downloads/

CustomPac http://www.ibm.com/ca/custompac

ShopzSeries http://www.ibm.com/software/shopzseries

z/OS Communications Server

http://www.ibm.com/software/network/commserver/zos/

Hot Topics ibm.com/servers/eserver/zseries/zos/bkserv/hot_topics.html

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.


© Copyright IBM Corp. 2001, 2013 Bibliography X-3

V8.0

backpg

E

Back page

xclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C.

.

Exclus

ivo fo

rmac

ión

proy

ecto

C.F.T.I.C

CONTACTO

Teléfono91 761 21 78Póngase en contacto con nuestro equipo y le informaremos de cualquier duda o cuestión que pueda surgirle.

[email protected]ándenos un email y le atenderemos enseguida.

Online@Arrow_Edu_ESO bien puede contactarnos a través de nuestro perfil en Twitter.

VisítenosArrow ECS Education ServicesAvenida de Europa 21, Parque Empresarial La Moraleja28108 Alcobendas, Madrid

EDUCATIONS E R V I C E S

es10bstud

Documents