200662192157320

Introduction to Z/OS
Zhang Bo
IBM CSDL
© 2004 IBM Corporation

IBM China Software Development Lab
What to be gained from today’s session:

This session will focus on:
1. Knowledge
– Terms
– System Structure
– Z/OS Interface
– Data Storage
– Work Management
– Software and Programming
2. Resource
– Where to get the resource about Z/OS
2 Introduction to zSeries © 2006 IBM Corporation

Terms
Zhang Bo
IBM CSDL

Z/OS Terms – System
Term What it stands for What it means Closest analogy

RAS Reliability, Availability, The main considerations of all Service guarantees
Servicibility research, development and
support staff within the zSeries
family.
Address Space The isolation of applications by Process
creating a separate memory
space for each running job.
EBCDIC Ext. Binary Coded A format for encoding Code-page, also
Decimal Interchange characters. Most Unix and ASCII or UTF-8
Code Windows machines use ASCII
code page.
Batch/Interactive Jobs that run on the system to Background/
complete processing with or Foreground process
without user intervention.
*This is just an analogy, and not meant to indicate that the terms are equivalent.
They are the closest possible match

Z/OS Terms – Data Storage

DASD Direct Access A storage device which can be directly Hard drive
Storage Device access by the OS through a Control
Unit (CU).
Data Set Storage space on DASD to store Partitioned = Archive
information. Datasets can be either
partitioned (with internal members) or Sequential= File
sequential.
HFS/ZFS Hierarchical File An HFS is a representation of a A file system on a
System traditional Unix file system (with partition
directories and files) An HFS is
actually stored in a dataset.
VSAM Virtual Storage A sequentially indexed storage
Access Method method.
DFSMS Data Facility Storage The subsystem responsible for Any storage mgmt
Mgmt Subsystem allocating space on DASD. Now product
contains HSM (Hierarchical Storage
Manager).

Z/OS Terms – Job Management

JCL Job Control Code used to start jobs and Shell script
Language define required resources
JOBLIB/STEPL Job Library Indicate additional MVS Data PATH and LIBPATH
IB Sets which should be searched variables
Step Library for programs and/or libraries
Subsystem/ Jobs that run without Core operating system functions, Daemons
requiring user such as security, storage
Started task interaction management, servers
TSO Time Sharing Option
USS Unix System Unix environment running on top

Services of z/OS

Z/OS Terms – Workload Scheduling
JES Job Entry Subsystem The subsystem that manages work

on z/OS. This is a priority queuing
system.
SPOOL Storage mechanism used by JES

to manage work queues
SDSF Spool Display and Allows a user to manage events on process management
Search Facility the JES Spool commands
RMF Resource Monitor A subsystem that allows you to

Facility obtain detailed performance
information about your system

Z/OS Terms – Software Maintenance
PMR Problem A support ticket that has been Vendor specific term
Management Report opened with the IBM Support
Center to report a program problem
APAR Authorized Program A problem report recognized by IBM Vendor specific term
Analysis Report as a bug in an IBM product
PTF Program Temporary A software update released (usually patch, fix, support
Fix as a result of an APAR) by IBM to pack
resolve any product issues that may
arise
SMP/E System Modification Software installation and RPM (Linux), SMIT

Program/ Extended maintenance facility (AIX)

Z/OS Terms – Clustering
LPAR Logical Partition A logical division of a machine System Partition /

which acts as a unique physical
machine – each LPAR runs its own Domain (on Sun)
OS instance
Sysplex System complex Multiple LPARs which are able to A highly enhanced
share resources to process units of cluster
work and provide redundancy
CF Coupling Facility A device which enables inter-LPAR
communication in a Sysplex
WLM Workload Manager A subsystem that attempts to

optimize system performance
based on your requirements
IRD Intelligent Resource Technology that allows that
Director automatic tuning of resources
between LPARs –WLM for LPARs

Z/OS Terms – Miscellaneous Terms
Abend Abnormal program A program has terminated Software has crashed

END prematurely or in an error status or faulted
Dump All storage for an abended task has Core file

been dumped to disk for debugging
purposes
IPL Initial Program Load The machine has been turned on Boot
and the operating system is loading
ISPF Interactive System An interactive panel driven (TN3270) SMIT (on AIX)
Panel Facility interface to TSO.
LinuxConf (on Linux)
RACF Resource Access A System Authorization Facility PAM (Linux) or any
Control Facility (SAF) compliant security subsystem other security tool

System Structure
Zhang Bo
IBM CSDL

Operating System in zSeries

How many operating systems in zSeries?
z/OS
– The major operating system in zSeries
– This session will focus on this!
z/VM
– “user” acts as it’s own virtual operating system
– VM “guests” can include any zSeries operating system
– Frequently used for independent development and testing facilities
– Now key to the “Scale Out” strategy for horizontal scaling of Linux servers on
zSeries
z/Linux
– A native zSeries operating environment, not a replacement for other IBM
zSeries operating systems
– Designed to support mixed work loads


There are also some other operating systems in zSeries:
VSE/ESA
– Small to mid-size 390 customers
– Most often used on very small 390 hardware
– Runs some common 390 components such as CICS, VTAM, etc.
AIX/ESA
– First IBM mainframe UNIX implementation
• Well, there was IX/370 in 1984, but virtually no one ever heard of it…
– Superceded by Unix System Services on MVS/ESA, OS/390, etc. and now
Linux
TPF
– Primarily for very high transaction rate, specialized applications (airline
scheduling)

14
CMS application application
CMS application application

…
Introduction to zSeries
z/VM
VSE application application
Linux application application

LIC (LPAR, etc) z/OS application application
z/OS application application

zSeries hardware, with optional IFLs
Linux application application

z/OS Concept – processor storage

370-XA until ESA/390 architecture, processor storage consisted of
central plus expanded storage. In z/OS architecture there is no
expanded storage.

z/OS Concept – virtual storage and address space

z/OS uses both types of physical storage (central and auxiliary) to enable
another kind of storage called virtual storage. In z/OS, each user has an
unique address space for its running programs.

z/OS Concept – system structure
User
DO
BM
R
P
User
BM
AO
R
P
System Task
Lotus Notes
WebSphere
Batch Job
Batch Job
Batch Job
TCP/IP
TOR
User
MP
VTAM
P
DB2
JES
User
MP
AO
Address Spaces
R
P
IMS CR
CICS
TSO
Base Operating System
LIC (LPAR, etc)
zSeries hardware
Address space addressability – 64-bit in z/OS
– 24 bit in MVS/370, 31 bit in MVS/XA –> OS/390
z/OS Component
z/OS is an integrated enterprise server operating system. It incorporates into one
product a leading-edge and open communication server, distributed data and file
services, Parallel Sysplex ,object-oriented programming, distribute computer
environment and open application interface.
Generally, z/OS consists of:

BCP
JES
TSO/ISPF
DFSMS
Other software required
In this session, we’ll look into everyone of them.

z/OS Component– Base Element

z/OS system consists of base elements that deliver essential operating
functions. In addition to the services provided by MVS/ESA, this means
such functions as communication support, online access, host graphic,
and online viewing of publications.
MVS/ESA
JES2
TSO/E
ISPF
DFSMSdfp
USS
SMP/E
…..

z/OS Component – Optional Element
In addition to the base, z/OS also has optional features that are closely
related to the base features. There are two types : one type is always
shipped with the system whether they are ordered or not, and another is
not shipped automatically.
JES3
RMF
RACF
SDSF
TCP/IP FOR MVS
DFSMSdss
…..

IPL
system is ready!
You can customize the system parameters upon
Initialization Programming Load.
There are three types of IPL: Start other Subsystem
Cold Start
Any IPL that loads (or reloads) the PLPA, but Start Master Scheduler
does not preserve VIO data set pages.
Warm Start
Load parameters and
Any IPL that doesn’t reload the PLPA , but does Initialize system
preserve VIO data set pages.
Quick Start
I/O configuration
Any IPL that doesn’t reload the PLPA and does
not preserve VIO data set pages.
Load MIC

Configuration
Most of the system configuration is
provided by data set
SYS1.PARMLIB.
SYS1.PARMLIB is read by the
system at IPL, and later by such
components as RMF.
This is the most important data
set in z/OS operating system!
There are the most important
parmlib members in this data set:
IEASYSxx
IEASYMxx
LOADxx

Lab 1
What would be gained from the lab 1 ?
Identify Address Spaces in system
Identify system initialization from the log
Know the critical system configuration

Reference
Where can you get the study resource?
z/OS structure
<<IBM eserver zSeries 900 Technical Guide>> SG24-5975-00
<<IBM z/Architecture Reference Summary>> SA22-7871-00
<<z/Architecture Principles of Operation>> SA22-7832-01
System initialization
<<z/OS V1R4.0 MVS Initialization and Tuning Reference>> SA22-7592-03
Sysplex
<<z/OS V1R4.0 MVS Sysplex Services Guide>> SA22-7617-03

<<z/OS V1R4.0 MVS Sysplex Services Reference>> SA22-7618-03

Interface
Zhang Bo
IBM CSDL

Processing type
There are three types of processing
available under z/OS:
Interactive processing
The most common type, is quick and ideally
suited for development and administration.
Batch processing
This is commonly used for running large
routine programs.
Transaction processing
This is used mainly in customer service
environment.

What’s the interface for z/OS

You can communicate with z/OS with either interactive method or batch
method. In this section, we’ll focus on the primary interface of z/OS – TSO and
the related interface that can help you operate z/OS.
ISPF
SMP/E
RMF
SMF
RACF
USS
……
Besides these facilities, TSO command and MVS command is also very
helpful for you to work with z/OS.
TSO command
MVS command

TSO/E
TSO/E is a base element of the z/OS operating system that allows users to
interactively work with the system. In general, TSO/E makes it easier for people
with all levels of experience to interact with the z/OS system.
You can use TSO/E in any of the

following three environments:
Line Mode
The quick and direct way to use TSO.
ISPF/PDF
The major way to use TSO. It provides
dialog management service to enable users
to navigate through panels.

ISPF
The Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) is a
set of panels that help you manage libraries of information on the MVS system.

ISPF
ISPF has four main components:
Dialog Manager (DM)
This provides services to dialogs and end users. PDF assist dialog or application developers
by providing development service.
Software Configuration Library Manager (SCLM)

This is a library facility that supports the software development cycle of an application from
the program design phase to release of final products.
Client/Server Component (C/S)

This enables users to run ISPF on a workstation, integrate workstation tools and data with
host tools and data.
Program Development Facility
This is the environment for programmers to develop programs, dialogs and documents.

SMP/E
System Modification Program Extended (SMP/E) is a tool designed to manage
the installation of software products on your z/OS system, and to track the
modifications applied to those products.

RMF
Many different activities are required to keep your z/OS running smoothly, and to
provide the best service on the basis of the available resources and workload
requirements. Resource Management Facility is the tool that helps people do this
effectively.

SMF
System Management Facility collects and records system and job-related
information that you use in billing users, analyzing the configuration, scheduling
jobs, maintain an auditing security, and so on.

RACF
z/OS Security Server integrates Resource Access Control Facility (RACF) on
local and distributed z/OS systems.
RACF controls authorized user access

by:
Identifying and authenticating users.
Authorizing users to access the
protected resources.
Logging and reporting attempts of
unauthorized access to protected
resources.
RACF includes encryption, data and

transaction integrity, individual
authentication, and transaction
accountability.

USS
Beginning with OS/390 V2R3, UNIX System Services has been merged with the
BCP, and is now part of the BCP FMID. In addition, OMVS address space is
started automatically. z/OS UNIX interacts with the following elements and
features of z/OS:
Two interfaces:
Shell interface
You can use shell in z/OS just
like what you do in other unix
system.
API
Through API, program can run
in any environment of z/OS,
and request both MVS service
and unix service.

TSO Line Command

In TSO/E line-mode you type TSO/E commands one line at a time. It is a quick and direct
way to use TSO/E and was the way programmers originally used to communicated
interactively with the z/OS operating system.
Example 1:
allocate da('zosinter.partds.s1') new dir(4) block(800) space(20,10) dsorg(po)
recfm(f,b) lrecl(80) blksize(3200) catalog
Example 2:
allocate da('zosinter.partds.s2') like('zosinter.partds.s1')
Reference:
z/OS TSO/E Primer, SA22-7787
z/OS TSO/E User's Guide, SA22-7794
z/OS TSO/E Command Reference, SA22-7782-04

MVS Command
If you want to learn and configure the system quickly, MVS command is the most
powerful way for you. Generally, you can execute MVS commands in SDSF and
get the system responses.
Some useful command:
D IPLINFO
D PARMLIB
D U,DASD,ONLINE
SETLOAD
SETPROG
…..
Reference:
z/OS MVS System Command, SA22-7787
z/OS MVS System Message, SA22-7631-05
z/OS MVS System Code, SA22-7626-04

Lab 2
How to logon z/OS?
How to create a data set using TSO command?
How to do the same action using ISPF?
How to identify a z/OS system using MVS command?

Resource
TSO reference
<<z/OS V1R1.0 TSO/E Primer>> SA22-7787-00
<<z/OS V1R3.0 TSO/E User's Guide>> SA22-7794-02
ISPF reference
<<z/OS V1R2.0 ISPF User's Guide Vol I>> SC34-4822-01
<<z/OS V1R2.0 ISPF User's Guide Vol II>> SC34-4823-01
SMP/E reference
<<SMP/E V3R1.0 Reference>> SA22-7772-02
<<SMP/E V3R1.0 User's Guide>> SA22-7773-02
RMF reference
<<z/OS V1R4.0 z/OS RMF User's Guide>> SC33-7990-02
<<z/OS V1R2.0 RMF Reference Summary>> SX33-9033-01

Resource
SMF reference
<<z/OS V1R4.0 MVS System Management Facilities (SMF) >> SA22-7630-05
RACF reference
<<z/OS V1R4.0 Security Server RACF Security Administrator's Guide>> SA22-7683-03
<<z/OS V1R4.0 Security Server RACF System Programmer's Guide>> SA22-7681-03
USS reference
<<z/OS V1R4.0 UNIX System Services User's Guide>> SA22-7801-03
MVS reference
<<z/OS V1R4.0 Introduction and Release Guide>> GA22-7502-04

Data Storage
Zhang Bo
IBM CSDL

Basic Concept
Some basic concept for data storage in
z/OS:
Data Record
Data Set
Access Method
Storage Device
- DASD
- TAPE
VTOC
DSCB

Non-VSAM Data Set

Data Set is the term IBM uses to refer to files. There are three basic non-VSAM
data set types in the MVS environment.
Sequential Data Set
Partitioned Data Set
Partitioned Data Set Extended

Non-VSAM Data Set

Sequential Data Set
Sequential Data Set records are arranged in the order in which they were written. New
records are added to the end of the data set and are stored on DASD or tape. To retrieve a
record, the system looks at each record in sequence until the required record is found.
Partitioned Data Set

Partitioned Data Sets (PDS) are divided into members containing one or more records and
identified by a unique name. A directory located at the beginning of the data set contain
each member name and its starting location within the data set. With a partitioned data set,
you can retrieve any member without searching the entire set. Members can be added or
deleted, but space cannot be reused until the data set is reorganized.
Partitioned Data Set Extended

Partitioned Data Set extended (PDSE) is similar to partitioned data sets, but makes more
efficient use of DASD space. Although the size of PDS directory is fixed, PDSE directories
expand to fit the members stored in it. Space is reallocated automatically when members
are deleted or added to use when needed, without having to reorganize the set.

VSAM Data Set
In addition to the three basic data set

types, z/OS also support Virtual
Storage Access Method (VSAM)
data sets. VSAM data sets use one
of four data organizations.
Entry-Sequenced Data Set (ESDS)
Key-Sequenced Data Set (KSDS)
Linear Data Set (LDS)
Relative Record Data Set (RRDS)

VSAM Data Set

ESDS
The Entry-Sequenced Data Set (ESDS) sequences records in the order they were entered
in the data set. New records appear only at the end of the set, and existing records can not
be deleted.
KSDS
The Key-Sequenced Data Set (KSDS) places logical records in the data set in ascending
collated sequence by a unique, contiguous key field. The key determins the record's
collating position in the data set.
LDS
The Linear Data Set (LDS) has a control interval size of 4096 bytes to 32768 bytes, with a
block size of 4096 bytes and no imbedded control information. These sets are processed
as a restricted ESDS. LDSs can not be accessed for individual records since they do not
contain control information. LDSs are used to contain data space and hiperspace data.
RRDS
Fixed-length Relative Record Data Sets (RRDS) consist of several fixed-length slots
sequenced by ascending relative record number. Data records are fixed in individual slots.
Variable-length RRDS are placed in order of their ascending relative record number. Unlike
fixed length data sets, they do not have slots.

Catalog
System tracks the locations of data sets through catalogs. Users can search for
data sets in the catalogs by name and move data to another device without
changing its references.
A master catalog contains pointers to all system data sets, which are used for
system initialization, and aliases or indirect pointers to user data sets. Aliases
point to a user catalog where user data sets are cataloged.
Master Catalog
User Catalog

DFSMS
The Data Facility Storage Management Subsystem (DFSMS) simplifies storage, data,
program, and device management as well as access to distributed data.
The Storage Management Subsystem (SMS) works with other components to help
automate and optimize storage management. As new data is created, the SMS
automatically assigns services and attributes to the data using values defined by the
installation.
Through SMS, user can establish policies for

the use of hardware resources and control how
these resources and control how these
resources are used and what service levels are
available; this includes data availability,
performance, space, and security.
Once these policies are established, the system

manages the complexities of optimizing the use
of expensive hardware to meet performance
criteria.

DFSMS
The Data Facility Storage Management Subsystem (DFSMS) simplifies storage, data
,program, and device management as well as access to distributed data.
DFSMSdfp: Data Management
DFSMSdss: Data Movement
DFSMShsm: Life Cycle management
DFSMSrmm: Tape Management

Lab 3:
View data sets
Edit data sets
Create data sets
Move/Copy data sets
Where to store the database data?
Identify the catalog

Resource
Data Sets
<<z/OS V1R3.0 DFSMS: Using Data Sets>> SC26-7410-02
VSAM
<<VSAM Demystified>> SG24-6105-01
DFSMS
<<z/OS V1R3.0 DFSMS Introduction>> SC26-7397-01
<<z/OS V1R3.0 DFSMSdss Storage Administration Guide>> SC35-0423-01
<<z/OS V1R3.0 DFSMSrmm Guide and Reference>> SC26-7404-01
<<z/OS V2R13.0 DFSMSdfp Utilities>> SC26-7414-02

Work Management
Zhang Bo
IBM CSDL

JCL – What is JCL?

Job Control Language (JCL) is used to tell the system what program to execute,
followed by a description of program inputs and outputs.
JCL consists of a seires of statements, each of which provides specific

instructions or information for batch processing jobs.
It provides the system with a source of information about the details :
the programs to execute
the location of required data set
the department to be billed for CPU processing time
the job priority

JCL – statement structure

There are three basic JCL statements:
JOB
Provides a name (job name) to the system for this batch workload. It can optionally include
accounting information and a few job-wide parameters.
EXEC
Provides the name of a program to execute. There can be multiple EXEC statements in a
job. Each EXEC statement within the same job is a job step.
DD
The Data Definition provides inputs and outputs to the execution program on the EXEC
statement. This statement links a data set or other I/O device or function to a DDNAME
coded in the program. DD statements are associated with a particular job step.

JCL – parameter
Parameter What it is for
JOB REGION Requests specific memory resources to be allocated to the job
CLASS Directs a JCL statement to execute on a particular input queue
NOTIFY Sends notification of job completion to a particular user, such as the submitter of
the job
MSGCLASS Directs job output to a particular output queue
….
EXEC PARM Parameters known by and passed to the program.
COND Boolean logic for controlling execution of other EXEC steps in this job
TIME Imposes a time limit.
DD DSN The name of the data set; this can include creation of temporary or new data
sets or a reference back to the data set name.
DISP Data set disposition, such as whether the data set needs to be created or
already exists, and whether the data set can be shared by more than one job.
SYSOUT Defines a print location (and the output queue or data set).
…

JCL - example
//UNLDTAPE JOB CLASS=A,MSGLEVEL=(1,1),MSGCLASS=A,

// NOTIFY=SYSPRG1,USER=WFSEUBE,PASSWORD=ABCD
//***************************************************************
//STEP1 EXEC PGM=IEBCOPY
//*
//IN1 DD DSN=IBM.HCMP120.F1,UNIT=TAPE,VOL=SER=CMP120,
// LABEL=(2,SL),DISP=(OLD,KEEP)
//OUT1 DD DSN=NETCOMM.HCMP120.JCL,DISP=(NEW,CATLG,DELETE),
// UNIT=SYSALLDA,DCB=*.STEP1.IN1,SPACE=(8800,(5,1,10))
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY INDD=IN1,OUTDD=OUT1
/*
//

JES - what is JES?

The system uses a job entry subsystem (JES) to receive jobs into the operating
system, schedule them for processing by MVS, and control their output
processing.
JES2 and the base control program

(BCP) provide the necessary functions to
get jobs into , and output out of the MVS
system.
Who will manage the jobs ?
Before processing --- JES
During processing --- BCP
After processing --- JES

JES – Job Life Cycle

The batch job processing cycle includes the following steps:
1. Job Submission
Users submit work to the operating system whenever it needs to be processed.
2. Job Reading
JES reads user jobs into the system.
3. Job Spooling
JCLs are stored by the JES on the spool data set awaiting selection for execution.
4. Job Selection
A job is selected from the spool for execution based on a job class, designating the type of work it is, and
its job priority, which specifies its relative importance.
5. Job Execution and Output Spooling
Application is performed and data is processed. The input data is processed and the output data is stored,
until it is needed. During execution, some of the job's output may be placed on the spool for later
transcription.
6. Output transcription
After the job has completed, the job output is retrieved from the spool transcribed, and usually printed.
7. Job Purging
The system deletes the job from the spool.

JES – how to process a job?

During the life of a job, both JES2 and BCP handle different phases of the overall
processing. Jobs go through six phases:
Input
Conversion
Processing
Output
Hard Copy
Purge

JES – the difference between JES2 and JES3

IBM provides two job entry subsystem from which to choose: JES2 and JES3.
If a system uses only one

processor, JES2 and JES3 perform
similar functions.
If there are several processors in a

configuration, each JES2 processor
controls its own job input,
scheduling ,and output processing,
while a single JES3 controls all job
selection, scheduling and device
allocation functions for all the other
JES3 systems.

SDSF
After submitting a job, it is common to use
System Display and Search Facility
(SDSF) to review the output for successful
completion or review and correct JCL
errors:
Viewing the system log and searching

for any literal string
Input system command
Controlling job processing (hold,
release, cancel, and purge jobs)
Monitoring jobs while they are being
processed
Displaying job output before deciding to
print it
Controlling the order in which jobs are
processed
Controlling the order in which output is
…

SDSF

Lab 4:
Create a simple JCL
Execute the JCL
View and analyze the log by SDSF

Resource
JES
<<z/OS V1R4.0 JES2 Introduction>> SA22-7535-02

<<z/OS V1R4.0 JES2 Commands>> SA22-7526-03
<<z/OS V1R4.0 JES2 Commands Summary>> SA22-7527-03
<<z/OS V1R4.0 JES2 Diagnosis>> GA22-7531-03
JCL
<<z/OS V1R2.0 MVS JCL User's Guide>> SA22-7598-01

<<z/OS V1R4.0 MVS JCL Reference>> SA22-7597-04

Software and Programming
Zhang Bo
IBM CSDL

Software on z/OS
Systems Data
Management Tools Management Tools
Performance
DB2
Tivoli
RMF
z/OS CICS Transaction

Collaboration Lotus Management
Tools z990
Tools
z/VM Linux
Key
zSeries H/W Rational WAS
& Firmware
Operating
Systems WebSphere
OS Features
Major SW
Subsystems
Perf. Monitor & Enterprise App. Dev. App. Deployment &
Analysis.
Customer/ISV & Modernization Integration
Applications. Tools Tools

Programming in z/OS
Language Environment provides a
common run-time environment for
C,C++,COBOL, Fortran, PL/I and
assembler programs.
With Language Environment , you

can develop new applications and
keep existing ones. You can
modularize and share code using
mixed programming languages to
develop applications that behave
consistently across different
operating systems.
Now, z/OS also supports Java

language.

Other Useful Resource
Zhang Bo
IBM CSDL

Redbook
Redbook provide PDF version for
most of the technical documents.
It is one of the most important study

resources in IBM.
Feel free to download the books

form this site:
http://www.redbooks.ibm.com/

Bookshelf
BookShelf collects most of the IBM books together. Although it takes a large space,
you can search any information in multiple books quickly.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr/library

LibraryCenter
http://publibz.boulder.ibm.com/bookmgr_OS390/libraryserver/zosv1r7/

Thanks!

200662192157320

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

200662192157320

Загружено:

Авторское право:

Доступные форматы

Introduction to Z/OS

© 2004 IBM Corporation

What to be gained from today’s session:

2 Introduction to zSeries © 2006 IBM Corporation

© 2004 IBM Corporation

Z/OS Terms – System

Term What it stands for What it means Closest analogy

4 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Data Storage

Term What it stands for What it means Closest analogy

5 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Job Management

Term What it stands for What it means Closest analogy

TSO Time Sharing Option

USS Unix System Unix environment running on top

6 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Workload Scheduling

Term What it stands for What it means Closest analogy

JES Job Entry Subsystem The subsystem that manages work

SPOOL Storage mechanism used by JES

RMF Resource Monitor A subsystem that allows you to

7 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Software Maintenance

Term What it stands for What it means Closest analogy

SMP/E System Modification Software installation and RPM (Linux), SMIT

8 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Clustering

Term What it stands for What it means Closest analogy

LPAR Logical Partition A logical division of a machine System Partition /

WLM Workload Manager A subsystem that attempts to

9 Introduction to zSeries © 2006 IBM Corporation

Z/OS Terms – Miscellaneous Terms

Term What it stands for What it means Closest analogy

Abend Abnormal program A program has terminated Software has crashed

Dump All storage for an abended task has Core file

10 Introduction to zSeries © 2006 IBM Corporation

© 2004 IBM Corporation

Operating System in zSeries

12 Introduction to zSeries © 2006 IBM Corporation

Operating System in zSeries

13 Introduction to zSeries © 2006 IBM Corporation

CMS application application

Linux application application

LIC (LPAR, etc) z/OS application application

z/OS application application

Linux application application

z/OS Concept – processor storage

15 Introduction to zSeries © 2006 IBM Corporation

z/OS Concept – virtual storage and address space

16 Introduction to zSeries © 2006 IBM Corporation

z/OS Concept – system structure

Generally, z/OS consists of:

18 Introduction to zSeries © 2006 IBM Corporation

z/OS Component– Base Element

19 Introduction to zSeries © 2006 IBM Corporation

z/OS Component – Optional Element

20 Introduction to zSeries © 2006 IBM Corporation

21 Introduction to zSeries © 2006 IBM Corporation

22 Introduction to zSeries © 2006 IBM Corporation

What would be gained from the lab 1 ?

 Identify Address Spaces in system

 Identify system initialization from the log

 Know the critical system configuration

Identify Address Spaces in system

Identify system initialization from the log

Know the critical system configuration

Software Configuration Library Manager (SCLM)

Client/Server Component (C/S)

How to logon z/OS?

How to create a data set using TSO command?

How to do the same action using ISPF?

How to identify a z/OS system using MVS command?

Partitioned Data Set

Partitioned Data Set Extended

Entry-Sequenced Data Set (ESDS)

Key-Sequenced Data Set (KSDS)

Linear Data Set (LDS)

Relative Record Data Set (RRDS)

DFSMSdfp: Data Management

DFSMSdss: Data Movement

DFSMShsm: Life Cycle management

DFSMSrmm: Tape Management

View data sets

Edit data sets

Create data sets

Move/Copy data sets

Where to store the database data?

Identify the catalog