Introduction To ZOS

6/17/2015
( A group Company of Maintec Technologies Pvt. Ltd.)
S c o p e U n lim ite d
Introductiontoz/OS
z/OSservices
6/17/2015
z/OSandz/OS.e
Hardwarerequirements
6/17/2015
z/Seriesserver:BasicandLPARmode
z/OSBaseControlProgram(BCP)
6/17/2015
z/OSbaseelement
z/OSoptionalfeatures
6/17/2015
DataFacilityStorageManagement
Subsystem(DFSMS)
z/OSCommunicationsServer:TCP/IP
6/17/2015
ResourceManagementFacility(RMF)
SystemManagementFacility(SMF)
6/17/2015
TimeSharingOption/Extended
(TSO/E)
LibraryLookaside (LLA)
6/17/2015
WorkloadManager(WLM)
z/OSoperations
6/17/2015
Basicaspectsofz/OS
implementation
MVSConsoleConfiguration
6/17/2015
MVSConsoleConfiguration(Cont.)
Generally, operators on an MVS system receive messages and enter
commands on Multiple Console Support (MCS) consoles. Operators can use
other consoles like NetView consoles or System Display and Search Facility
(SDSF) consoles or Resource Measurement Facility (RMF) consoles to interact
with MVS but we will focus on MCS consoles.
MCS consoles are devices that are locally attached to an MVS system and
provide the basic communication between operators and MVS
One MCS console is designated as the master console and has full capability
to view messages and to enter all MVS commands.
Other MCS consoles can be defined so that the message traffic can be spread
across multiple consoles.
There is also a system console. An operator uses the system console to
initialize MVS. The system console is not defined to MVS and is not under
MCS control
MVSSysplex ConsoleConfiguration
10
6/17/2015
MCSConsole
MCSConsole(Cont.)
11
6/17/2015
HARDCOPYLOG
SystemDatasets
12
6/17/2015
SYS1.PARMLIB
Rulesforparmlib memberdefinitions
13
6/17/2015
Systemsymbols
Systemsymbols:Types
14
6/17/2015
UsingSystemSymbolsinParmlib
WheretoUsetheSystemSymbols
15
6/17/2015
ExampleofSystemSymbols
SYSDEF
SYSDEF
LPARNAME(P390)
SYSNAME(P390)
SYSCLONE(P1)
LPARNAME(Q390)
SYSNAME(Q390)
SYSCLONE(Q1)
Logicalparmlib
16
6/17/2015
Parmlib concatenation
STARTINGTHEIPL
17
6/17/2015
STARTINGTHEIPL
STARTINGTHEIPL(CONT.)
The initialization process begins from the system console.
The system console is the one that communicates with the
hardware rather than with MVS.
The operator provides the following information:
A1 device number of the system residence volume.
A2 a parameter field.
A3 begin system initialization.
A System Control Program (SCP) is an IBMsupplied program

that is fundamental to the operation of the system in our
case it's MVS.
18
6/17/2015
SYSTEMRESIDENCEVOLUME
SYSTEMRESIDENCEVOLUME(CONT.)
The DASD volume that contains the SYS1.NUCLEUS data set will
be used to IPL (Initial Program Load) the MVS system and is
known as the system residence (SYSRES) volume.
The SYS1.SVCLIB data set must also be located on the SYSRES
volume. SYSl.SVCLIB contains error recovery routines that may
be required during the IPL process.
The SYSRES volume must also contain the IPL text a specialized
program that resides on cylinder 0, head 0 of the volume. It is
the first thing read into central storage during the IPL process
and is used to begin the transfer of data from the SYSRES
volume into central storage.
Other system data sets may, and usually do, reside on the
system residence volume.
19
6/17/2015
LOADPARAMETER
LOADPARAMETER(CONT.)
With MVS systems beginning with MVS/SP Version A, the
I/O configuration information may be in an IODF, and that
IODF may reside on a volume other than the system
residence volume. The Load Parameter field points to the
volume that contains the IODF and a LOADnn member of a
system library either SYS1.PARMLIB or SYSn.IPLPARM.
The last position of the Load Parameter provides a way of
pointing to an alternate nucleus member of the
SYS1.NUCLEUS data set.
The second last position of the Load Parameter controls
message suppression during the IPL process.
20
6/17/2015
INITILIZATIONEXAMPLE1
INITILIZATIONEXAMPLE1(CONT.)
As in the previous example, the system residence volume has a device
number of 0250. Therefore, 0250 is specified in the Load Unit Addr"
field.
The "Load Parm(A/N)" field indicates that a LOAD00 member on volume
0250 should be used for this IPL.
The NUCLEUS statement in LOAD00 contains a pointer to the
appropriate lEANCU0n.
The SYSCAT statement in LOAD00 provides the master catalog information
for this IPL.
The "P" in the seventh position indicates that the operator is to be

prompted during the IPL process for any overrides to the values specified
in the LOAD00 member or in SYS1.PARMLIB.
The "1" in the last position indicates that IEANUC01 is to be used for this
IPL. II would override the specification in LOAD00.
21
6/17/2015
INITILIZATIONEXAMPLE2
INITILIZATIONEXAMPLE2(CONT.)
As we saw on the previous visual, the system needs lo know the device
number of the system residence volume and the location of the relevant
LOADnn member.
In this example, the "Load Parm(A/N)" field will be used to locate the LOADnn
member as well as to point to the volume containing the production IODF.
Device number 0260 is to be searched for the LOAD01 member of
SYSN.IPLPARM. Device number 0260 also contains the production IODF.
The "M" in the seventh position indicates that messages during the IPL process
are to be displayed, but the operator is not to be prompted for overrides.
The "1" in the eighth position indicates that the IEANUC01 member of the
SYS1.NUCLEUS data set is to be selected for this IPL. This overrides the
specification in the NUCLEUS statement of LOAD01
22
6/17/2015
INTIALPROGRAMLOAD(IPL)
INTILAPROGRAMLOAD(IPL) (CONT.)
The IPL program loads the selected nucleus
member of SYS1.NUCLEUS.
The IPL program also selects the appropriate I/O
configuration from either the SYS1.NUCLEUS data
set (if MVSCP was used to define the I/O
configuration) or from the production IODF (if HCD
was used to define the I/O configuration).
A Nucleus Initialization Program (NIP) resides in
the lEANUC0n member and receives control from
the IPL program to complete the nucleus
initialization process.
23
6/17/2015
IPLonz/OS
IPLonz/OS(CONT.)
Initial program loading (IPL) provides a manual means

for causing a program to be read from a designated
device and for initiating execution of that program.
When the system hardware is ready, you can use the
system console to load the system software.
During initialization of a z/OS system, the operator
uses the system console, which is connected to the
processor controller or support element.
The LOADxx parmlib member allows your installation
to control the initialization process. For example, in
LOADxx, you specify IEASYSxx or IEASYMxx members
that the system is to use.
24
6/17/2015
TYPESofIPLs
TYPESofIPLs(CONT.)
Cold Start: Any IPL that loads or reloads the
Pageable Link Pack Area (PLPA) and does not
preserve VIO data sets. The first IPL after system
installation is always a cold start because the
PLPA must be initially loaded. The PLPA needs to
be reloaded:
At the first IPL after system initialization, when the
system loads it automatically.
After modifying one or more modules in the LPALST
concatenation.
At the time of Cold Start, Its bring all the subsystems
automatically.
25
6/17/2015
TYPESofIPLs(CONT.)
Warm Start: Any IPL that does not reload the
PLPA and preserves journaled VIO data sets. The
operator does not enter CLPA or CVIO at the
SPECIFY SYSTEM PARAMETERS prompt. Any
definitions of existing page data sets as nonVIO
local page data sets are preserved.
At the time of Warm Start, Its bring all the
subsystems except DB2, CICS and IMS.
TYPESofIPLs(CONT.)
Quick Start Any IPL that does not reload the PLPA
and does not preserve VIO data sets. The system
recreates page and segment tables to match the
inuse PLPA. You would normally perform a Quick
Start IPL after a power up.
At the time of Quick Start, Its bring only three
subsystems like JES2, RACF and TSO.
26
6/17/2015
WhathappenDuringtheIPL
LOAD SUCCESSFUL is a message from
the IPL hardware/microcode. IPL does:
1) Hardware system reset
2) Optional memory clear
3) SPOOL Memory will be cleared
4) System Dataset will be compressed
5) System will be reset to Current Stage
LibrariesandMembersatIPLtime
An number of libraries must be present
for the system to load at IPL time.
SYS1.PARMLIB contains the required
definitions
SYSn.IPLPARM searched for LOADxx
SYS1.LPALIB
SYS1.PROCLIB
SYS1.NUCLEUS
27
6/17/2015
LOADxx
LOADPARM defines the address of the

IODF and the suffix of the LOADxx
member
At IPL the system searches for LOADxx in:
SYS0.IPLPARM SYS9.IPLPARM on IODF
volume
SYS1.PARMLIB on the IODF volume
SYS1.PARMLIB on the IPL volume
LOADxx
The LOADxx member specifies:

The IODF data set name
The master catalog name and volume
The parmlib concatenation
The IEASYSxx member to use
28
6/17/2015
IPLStartUp
Parmlib Commands
The parmlib concatenation can be
displayed using D PARMLIB
The parameters used at IPL can be
displayed using D IPLINFO
The parmlib concatenation can be
modified dynamically using SETLOAD
xx,PARMLIB (Please dont try this
Command)
29
6/17/2015
CommandstoDisplayParmlib
D PARMLIB
IEE251I 17.12.07 PARMLIB DISPLAY 377
PARMLIB DATA SETS SPECIFIED
AT IPL
ENTRY FLAGS VOLUME DATA SET
1
S TOTSY1 SYS1.SYSPROG.PARMLIB
2
D TOTSY1 SYS1.PARMLIB
3
S Z04CAT CPAC.PARMLIB
4
S Z04RE1 SYS1.IBM.PARMLIB
D IPLINFO
IEE254I 17.15.29 IPLINFO DISPLAY 379
SYSTEM IPLED AT 09.28.14 ON 07/23/2004
RELEASE z/OS 01.04.00 LICENSE = z/OS
USED LOADR2 IN SYS0.IPLPARM ON 3800
ARCHLVL = 2 MTLSHARE = N
IEASYM LIST = XX
IEASYS LIST = (R3,04) (OP)
IODF DEVICE 3800
IPL DEVICE 8038 VOLUME Z04RE1
ControllingPARMLIB
30
6/17/2015
InitializationVIAAutomaticCommands
SomemembersofSYS1.PARMLIB
(Notallmembersmaybelisted)
ALLOCxx (AllocationSystemDefaults)
CLOCKxx (TimeofDayParameters)
CNGRPxx (SpecifyAlternateConsoleGroups)
CNLcccxx (TimeandDateFormatforTranslatedMessages)
COMMNDxx (CommandsAutomaticallyIssuedatInitialization)
CONFIGxx (StandardConfigurationList)
CONSOLxx (ConsoleConfigurationDefinition)
DEVSUPxx (DeviceSupportOptions)
DIAGxx (ControlCommonStorageTrackingandGFSTrace)
EXITxx (AllocationInstallationExitList)
GRSRNLxx (GlobalResourceSerializationResourceNameLists)
IEAAPFxx (AuthorizedProgramFacilityList).
IEACMD00(IBMSuppliedCommands)
IEADMP00(ABDUMPWrittentoaSYSUDUMPDataSet)
IEADMR00(ABDUMPWrittentoaSYSMDUMPDataSet)
IEAFIXxx (FixedLPAList)
31
6/17/2015
SomemembersofSYS1.PARMLIB
(Notallmembersmaybelisted) (CONT.)
IEALPAxx (ModifiedLPAList)
IEAPAKxx (LPAPackList)
IEASVCxx (InstallationDefinedSVCs)
IEASYMxx (SymbolDefinitionsandIEASYSxx Members)
IEASYSxx (SystemParameterList)
IEFSSNxx (SubsystemDefinitions)
IKJTSOxx (TSO/ECommandsandPrograms)
IPCSPRnn (InteractiveProblemControlSystem)
LNKLSTxx (LNKLSTConcatenation)
MMSLSTxx (MVSMessageServiceList)
MSTJCLxx (MasterSchedulerJCL)
NUCLSTxx (CustomizingtheNucleusRegion)
PFKTABxx (ProgramFunctionKeyTableDefinition)
PROGxx (AuthorizedProgramList,Exits,LNKLSTSetsandLPA)
SMFPRMxx (SystemManagementFacilities(SMF)Parameters)ValueofJWT.
TSOKEY00(TSO/VTAMTimeSharingParameters)
VATLSTxx (VolumeAttributeList)
IEASYSxx
32
6/17/2015
IEASYSxx (Cont.)
IEASYMxx
33
6/17/2015
Catalog
Catalog(Cont.)
Ensuring that your catalogs are effectively managed is
therefore a crucial aspect of DASD management. Some
of the most common catalog management tasks that a
system programmer may have are:
Defining and maintaining the master catalog
Defining the alias and user catalog
Protecting the catalogs
Cleaning up catalogs
Backing up catalogs and performing catalog recovery
34
6/17/2015
MasterCatalog
MasterCatalog(Cont.)
Every MVS system relies on the master catalog at IPL time to locate system data
sets.
The LOADxx member of PARMLIB contains the SYSCAT statement, which identifies
the name of the master catalog and the volume where it resides.
The intervening 113C indicates the following:
The first '1' indicates the type of master catalog is an ICF catalog structure, and the
SYS% facility is not enabled
The second '1' indicates that only the first qualifier of the data set name (HLQ) is to be
used as an ALIAS pointer. Up to 4 qualifiers may be used to identify an ALIAS. This is
called the multilevel alias facility.
The '3C' indicates the lower limit for the number of tasks started to service catalog
requests.
The master catalog is vital for the correct running of the system. To minimize its
exposure during normal running, updates are restricted to those users authorized
to do so. This should only be the systems programmers and the storage
administrators. User errors may easily cause attempted updates to the master
catalog.
The master catalog should only contain when the Master Catalog got corrupted:
catalog pointers to system data sets (e.g. page data sets, and SYS1 data sets)
alternative names for user catalogs (called ALIAS pointers), and
pointers to user catalogs (CONNECT entries).
35
6/17/2015
SeparatingofSoftware
SeparatingofSoftware(Cont.)
Thekindsofdatayoushouldseparatefromz/OS
softwareare:
Customizationdata,includingmostsystem
controlfiles
NonIBMsoftware
IBMnonz/OSproducts,forexampleCICSand
DB2
Userdefinedexits
Userdata
36
6/17/2015
PlacingdatasetsonSpecificVolumes
PlacingofDatasetsonSpecific
Volumes(Cont.)
Some SYSRES volume types, such as the 33903, are not big
enough to hold all the target libraries for a z/OS system.
Therefore, you have to move some data sets to SYSRES logical
extension volumes (or overflow volumes). The considerations you
should take into account for placing data sets on specific volumes
are:
Your ability to use a system (or subsystem) replacement
Data set and system availability
System performance
System cloning and servicing techniques
Sysplex/multisystem operations
Sharing data sets
Backup and recovery
Disaster recovery
37
6/17/2015
TargetLIBVolumes
TargetLIBVolumes(Cont.)
Primary target volume (TVOL1) data sets are:
Load libraries
Change migration libraries
Help libraries
Panel libraries
Message libraries
Skeleton libraries
Table libraries
Fixedblock CLIST and EXEC libraries
Data libraries
SMP/Emanaged PARMLIB
SMP/Emanaged PROCLIB
38
6/17/2015
Secondarytargetvolumes(TVOL2TVOLn)datasets
are:
FixedblockCLISTandEXEClibraries
SampleandJCLlibraries
Sourcelibraries
Macrolibraries
Workstation
SoftcopylibrariesintowhichSMP/Einstalls
Fontandprintinglibraries
FlatfilesthatSMP/Ecannotmanage
SMP/EtargetCSI
SMP/Etargetdatasets
Subsystem target volume The libraries on this volume
consist of the subsystem product sets (for example,
CISCS, DB2, IMS, or NCP). The recommended types of
data sets for this volume are:
Subsystem target libraries.
Alternate subsystem SMP/E global CSI, if applicable.
SMP/E target CSI.
SMP/E target data sets: SMPLTS, SMPMTS, SMPSTS,
and SMPSCDS.
User catalog where the subsystem targets libraries
including SMP/E CSIs are cataloged.
39
6/17/2015
DistributionLIBVolumes
ImageRelatedVolumes
40
6/17/2015
ImageRelatedVolumes(Cont.)
Page data sets volume 1
PLPA (onecylinder allocation)
COMMON
Page data set volumes 2 to n
Local
SMF
RMF reporting
STGINDEX data set (if used)
Imagerelated LOGREC data set (if used)
HFS customization volume
HFS data sets that must be in write mode (for instance, /tmp,
/etc, /dev, /u) and that contain customized information.
User catalog where the HFS data sets are cataloged.
ClusterRelatedVolumes
41
6/17/2015
ClusterRelatedVolumes(Cont.)
Mastercatalogvolume
MasterCatalog
BROADCASTdataset
Customerparmlib concatenation(nottheSMP/EDDDEFed PARMLIB)
Customerproclib concatenation(nottheSMP/EDDDEFed PROCLIB)
UADSdataset(ifused)
VTAMLSTdataset
SMScontroldatasets(ACDS,SCDS,andCOMMDS),HSM,RMM,andsoforth
APPCVSAMdataset
Systemcontrolfiles(TCPI/Pconfigurationandsoforth)
PrimaryRACFdatabase
IODFdataset
SYS0.IPLPARM
UCATs
SYS1.DDIRsysplex dumpdirectorydataset
DAEdataset
JEScheckpointvolume Formaximumperformanceandreducedcontention
JESspoolvolume
ClusterRelatedVolumes(Cont.)
Sysplexrelatedvolume1
SYSPLEXprimary
CFRMalternate
ARMprimary
WLMprimary
LOGRprimary
OMVSprimary
Sysplexrelatedvolume2
Sysplex alternate
CFRMalternate
ARMalternate
WLMalternate
LOGRalternate
OMVSalternate
SecondaryRACFdatabase
Softcopyvolume
Books
Bookshelves
Bookindexes
42
6/17/2015
SystemDatasets
MVSMessagesDetails
Messages have two parts
The message text provides information or describes an
error.
The message ID normally consists of a prefix, a serial
number and a code.
43
6/17/2015
MVSMessagesDetails(Cont.)
The message ID normally consists of a
Prefix
Serial Number
Code
IEA000I 590,INT REQ,D2,0200,,,SYS122A

IEx
IST
IGD
$HASP
IAT
MVS messages
VTAM messages
SMS messages
JES2 messages
JES3 messages
000 A serial number to identify the individual
message
I A code to indicate the type of message.
Valid options are
A
D
E
I
W
An operator action is required

An operator decision is required
Eventual operator action is required
Informational message; no action required
Processing is stopped until you perform an action
44
6/17/2015
Action messages are
Highlighted and become nondeletable
Prefixed with a symbol (* or @) that indicates an
operator action is expected
Ex: *IEF233A M 580,323947,,SYS122A,STEP01,SYS122.DATA
The * indicates that it is a systemissued message

that requires operator action.
Ex: @02 ERB306D III: REPLY WITH OPTIONS OR GO
The @ indicates that it is a message from a program that

requires operator action.
An action message prefixed with a two digit number is
considered an outstanding reply, and you must respond.
*95IEF238D TF08QCPY REPLY DEVICE NAME,'WAIT' OR 'CANCEL
Function:Torespondtosystemrequestsforinformation
Syntax:<R>id<,text>
Description:RIndicatesamessagereply
idThetwodigitreplynumberfromthemessagethat
requiresanoperatorreplytextTheresponsetothemessage
Afteryouperformtherequiredaction
Theactioncharacterisreplacedwitha
Themessagehighlightingiseliminated
Themessagebecomesdeletable
45
6/17/2015
References
MVSSystemCommands
MVSSystemMessagesVolume1toVolume 10
MVSDataAreasVolume1toVolume 6
SystemDatasetsHousekeeping
46
6/17/2015
SystemDatasetsHousekeeping(Cont.)
SMF records The SMF records contain a variety of information

that enables you to produce many types of analysis reports and
summary reports so that you can evaluate changes in
configuration, workload, or job scheduling procedures by
studying the trends in the data.
LOGREC data The LOGREC data set contains statistical data
about machine failures (processor failures, I/O device errors,
channel errors).
SYSLOG data This data set resides in JES2's spool space. It can
be used by application and system programmers to record
communications about problem programs and system functions.
It also contains a record of console messages and operator
commands for audit and diagnosis purposes.
System DUMP data sets These are sequential data sets which
contain system dumps that record areas system task failures.
SMFData
47
6/17/2015
SMFData(Cont.)
How to collect SMF data
To record SMF data, you have to allocate direct access space and
catalog the SMF data sets. You should allocate at least two data
sets for SMF use (with at least one on a highperformance device),
as follows:
1. A highperformance device is needed because, if the I/O rate
is too slow, data will have to be buffered. The buffers will
eventually fill up, which could result in lost data.
2. The naming convention used for SMF data sets is SYS1.MANx,
such as SYS1.MAN1, SYS1.MAN2, SYS1.MAN3.
3. Consider the following factors when determining which device
type to specify when allocating SMF data sets:
Your system configuration

The amount of SMF data to be written
The size of SMF buffers (the control interval size)
Your installation's report program requirement
SMFPRMxx Parmlib Member
48
6/17/2015
SMFPRMxx Parmlib Member(Cont.)

Once you have allocated all the required SMF data
sets, you have to update the SMFPRMxx in
SYS1.PARMLIB to reflect the new SMF data sets. In
order to enable SMF recording, make sure that
the first parameter in SMFPRMxx is set to ACTIVE.
To activate the new changes to SMF parameters,
you can use the SET command to make them
effective (assuming that you have added
SYS1.MAN3 to SMFPRM00) issuing the SET
command.
SET SMF=00 (Please dont Try this Command)

IEF196IIEF237I0800ALLOCATEDTOIEFPARM
IEE252IMEMBERSMFPRM00FOUNDINSYS1.PARMLIB
IEF196IIEF237I0802ALLOCATEDTOSYS00004
IEE966ISYS1.MAN3ISBEINGFORMATTED1
IEF196IIEF285ISYS1.PARMLIBKEPT
IEF196IIEF285IVOLSERNOS=MPRES1.
IEE949I03.01.03SMFDATASETS097
NAMEVOLSERSIZE(BLKS)%FULLSTATUS
2PSYS1.MAN1MPCAT172009ACTIVE
SSYS1.MAN2MPCAT118000ALTERNATE
SSYS1.MAN3MPCAT118000ALTERNATE
IEE536ISMFVALUE00NOWINEFFECT
1.SMFfoundthatSYS1.MAN3hasnotbeenformatted.Theformattingis
nowtakingplace.
2.ThenameoftheSMFdatasetprecededbyaPindicatesthatitisthe
primarySMFdataset.IfthenameisprecededbyanS,thedatasetisa
secondarySMFdataset.
49
6/17/2015
Types of SMF records

You can control which SMF record types are recorded by using the SYS parameter in
the SMFPRMxx parmlib member. You can specify SYS(TYPE(0:255)) to record all
SMF records.
However, this can create considerable overhead and fill up the SMF data sets very
quickly.
The default SYS parameter is SYS(NOTYPE(14:19,62:69,99). This collects all SMF
records except the following:
Record type 14 is written for input nonVSAM direct access, tape data sets, or VIO data
sets.
Record type 15 is written for output nonVSAM direct access, or VIO data sets.
Record type 16 is written to record information about events and operations of the
sorting program.
Record type 17 is written when a nontemporary data set or temporary data set is
scratch.
Record type 18 is written when a nonVSAM data set is renamed.
Record type 19 is written for a list of online devices with specific IPL time frame.
Record types 62 to 69 are written for various VSAM data sets and catalog activities.
Record type 99 is written by the System Resource Manager (SRM) component when
running in goal mode.
LOGRECData
50
6/17/2015
LOGRECData(Cont.)
How to create SYS1.LOGREC
When an error occurs, the system records information about
the error in the LOGREC data set. The information provides you
with a history of all hardware failures, selected software errors,
and selected system conditions.
Print reports about the system records
Determine the history of the system
Learn about a particular error
Before the system can record all this information, you must
first allocate the LOGREC data set and initialize it.
Note: Whenever you allocate or reallocate the LOGREC data
set, the newly allocated data set will not be used until you
initialize it and IPL the system on which it is to be used.
LOGRECData(Cont.)
How to clear SYS1.LOGREC
The LOGREC data set will eventually become full,
the same as the SMF data set, and console
messages appear requesting the operator to take
action. Therefore, this data set needs to be cleared
so that it can be reused. There is only one LOGREC
data set for z/OS.
As a system programmer have to set up a process
to clear the LOGREC data set when the following
message appears:
IFB080ELOGRECDATASETISFULL,DSN=SYS1.LOGREC
51
6/17/2015
LOGRECData(Cont.)
You can use the following sample JCL to clear the
LOGREC data set:
//CLRLOG JOB (),'MVSSP',NOTIFY=&SYSUID,CLASS=A,MSGLEVEL=(1,1),
//STEP EXEC PGM=IFCEREP1,PARM='CARD'
//SERLOG DD DSN=SYS1.LOGREC,DISP=OLD
//ACCDEV DD DSN=SYS1.LOGREC.TEMPSTOR,DISP=MOD
//TOURIST DD SYSOUT=*
//EREPPT DD SYSOUT=*
//SYSIN DD DUMMY
SYSUM
ACC=Y
ZERO=Y
The job will copy the LOGREC data set to the data set
specified in the DDNAME ACCDEV, print a brief summary
of LOGREC data, and then clear the data set.
SYSLOGData
52
6/17/2015
SYSLOGData(Cont.)
The SYSLOG on the MVS system actually consists of two separate

logs: System log and the Hardcopy log.
The hardcopy log is a record of all system message traffic,
specifically:
Messages to and from all consoles
Commands and replies entered by the operator
The SYSLOG is a SYSOUT data set provided by the JES2. SYSOUT
data sets are output spool data sets on DASD. An installation
should print the SYSLOG periodically to check for problems. The
SYSLOG consists of the following:
All messages issued through Write To Log (WTL) macros &
entered by the LOG operator commands.
Usually, the hardcopy log.
OtherAdministrationTasks
53
6/17/2015
OtherAdministrationTasks(Cont.)
WorkwithMIH
Addpagedatasets
ChangeTSOtimeout
Addspoolvolumes
Deletespoolvolumes
Verifysystemconfiguration
ViewSYSOUTusingISPF
ChangeyourTSOprofile
Backupandrestorez/OS
WhyMainframeisnotdeadSTILL?
OLDMAINFRAMERSWILLNEVERDIE
BECAUSE
THEYJUSTTAKEDUMPANDReIPL
54
6/17/2015
Subsystems&SubsystemInterface(SSI)
Definingsubsystemsandsubsystem
interface
55
6/17/2015
WhatisSubsystem?
A subsystem is a service provider that performs one function or
many functions, but does nothing until it is requested.
Processing the IEFSSNxx Parmlib member during IPL.
You can use either the keyword format or positional format of
the IEFSSNxx parmlib member.
The keyword format, which allows you to define and
dynamically manage your subsystems.
Issuing the IEFSSI macro
Issuing the SETSSI system command
Some examples of IBMsupplied subsystems that use these

interfaces are the following:
JES2, JES3, IMS, NetView etc.
The master subsystem (MSTR) is a part of MVS and is not defined
in any of these ways.
WhatisSubsystem?(Cont.)
There are four types of subsystems:
The master scheduler subsystem is used to establish
communication between the operating system and the
primary job entry subsystem, which can be JES2 or JES3. It
is also used to initialize system services such as the system
log and communications task.
The primary subsystem is the job entry subsystem that
MVS uses to do work. It can be either JES2 or JES3.
Secondary subsystems provide functions as needed by IBM
products, vendor products, or the installation.
Functional subsystems: JES2/JES3 allows certain functions
to operate outside the JES2/JES3 address space.
56
6/17/2015
WhatisSubsystemInterface?
The SSI is the interface used by routines (IBM,
vendor, or installationwritten) to request
services of, or to pass information to, subsystems.
The SSI is a way for one routine to call another
routine. There are a number of other ways that a
routine can call another routine, such as:
Link register
LINK or LINKX macro
Program call (PC)
SVC
SubsystemInitialization
57
6/17/2015
SubsystemInitialization(Cont.)
MVS requires that at least one subsystem be defined as JES to bring jobs
into the system. The JES is also called the primary subsystem. You can
select either JES2 or JES3. If you do not specify an IEFSSNxx member in
SYS1.PARMLIB, MVS attempts to use the system default member,
IEFSSN00. IEFSSN00, as supplied by IBM, contains the definition for the
default primary JES2.
If you attempt to IPL without specifying an IEFSSNxx member, and
IEFSSN00 is not present or does not identify the primary subsystem, the
system issues message IEFJ005I and prompts the operator for the
primary subsystem.
If we didnt define a subsystem more than once in a combination of
IEFSSNxx members that can be used together or within a single member.
The same subsystem can appear in two different IEFSSNxx members
when the members will not be used together. In general, if MVS detects
a duplicate name, both of the following are true:
MVS does not define the duplicate subsystem
MVS does not give control to the initialization routine.
The system issues the following message:

IEFJ003I: DUPLICATE SUBSYSTEM subname NOT INITIALIZED
SubsystemInitialization(Cont.)
How to initialize your subsystem

There are two ways to initialize your subsystem:
Specifying an initialization routine
Using the START command
Specifying an initialization routine
You can optionally specify the name of your subsystem
initialization routine when you define your subsystem. If the
functions the subsystem supplies might be needed during the
IPL process, define your initialization routine in IEFSSNxx.
Using the START command
If the subsystem functions are not needed until a later time,
you can use the START command to initialize your subsystem.
58
6/17/2015
SubsystemDefinitions
SubsystemDefinitions(Cont.)
Statements and parameters for IEFSSNxx

The storage management subsystem (SMS) is the only subsystem that can
be defined before the primary subsystem.
The statements and parameters for IEFSSNxx are:
SUBSYS The statement that defines a subsystem that is to be added to the
system. If more than one SUBSYS statement appears for the same
subsystem name, the duplicate statements will be rejected with a failure
message that is sent to the console.
SUBNAME(subname) The subsystem name. The name can be up to four
characters long; it must begin with an alphabetic or special character (#, @,
or $), and the remaining characters (if any) can be alphanumeric or special.
CONSNAME(consname) The name of the console to which any messages
that the SSI issues as part of initialization processing are to be routed. The
default is to issue messages to the master console.
INITRTN(initrtn) The name of the subsystem initialization routine. This
name is optional and can be one to eight characters long. The first character
can be either alphabetic or special. The remaining characters can be either
alphanumeric or special.
59
6/17/2015
SubsystemDefinitions(Cont.)
INITPARM(initparm) Input parameters to be passed to the

subsystem initialization routine. The input parameters are optional
and are variable in length for a maximum of 60 characters. If
blanks, commas, single quotes, or parentheses are included in the
input parameters, the entire parm field must be enclosed in single
quotes.
PRIMARY({NO|YES}) This parameter indicates whether this is the
primary subsystem. The primary subsystem is typically a JES2. This
parameter is optional. Initialize the primary subsystem before any
secondary subsystem(s) except SMS. The IEFSSNxx parmlib
member is the only place you can define the primary subsystem. It
cannot be defined using the dynamic SSI services IEFSSI
REQUEST=ADD macro or the SETSSI ADD command. The default is
NO.
START({YES|NO}) This parameter indicates whether an automatic
START command should be issued for the primary subsystem.
JES2supportedSSIfunctions
60
6/17/2015
LPA,LNKLST&APFLibraries
LinkPackArea(LPA)
61
6/17/2015
LinkPackArea(LPA) (Cont.)
Link pack area (LPA) modules are loaded in common
storage, shared by all address spaces in the system.
Modules found in LPA do not need to be brought into
virtual storage because they are already in virtual
storage.
Modules placed anywhere in LPA are always in virtual
storage, and modules placed in FLPA are also always in
central storage.
LPA pages are only stolen, and never paged out,
because there are copies of all LPA pages in the LPA
page data set.
LPASubAreas
The link pack area (LPA) is a section of the common area of an address
space. It exists below the system queue area (SQA) and consists of the
pageable link pack area (PLPA), then the fixed link pack area (FLPA) if one
exists, and finally the modified link pack area (MLPA).
Each component of the LPA has a counterpart in the extended common area
(that is above the 16 megabyte line) as follows:
FLPA The FLPA exists only for the duration of an IPL.
PLPA During initialization, both primary and secondary (or duplexed)
PLPAs are established. On the PLPA page data set, ASM maintains
records that have pointers to the PLPA and extended PLPA pages.
MLPA This area may be used to contain reenterable routines from
APFauthorized libraries that are to be part of the pageable extension
to the link pack area during the current IPL. The MLPA exists only for
the duration of an IPL.
Note: FLPA & MLPA has to be specified during the WARM & Quick Start.
62
6/17/2015
LPAParmlib Definition
LPAParmlib Definition(Cont.)
Specifying LPA parameters in Parmlib
The two characters (A through Z, 0 through 9, @, #, or $)
represented by aa (or bb and so forth) in Figure, are
appended to LPALST to form the name of the LPALSTxx
parmlib members.
If the L option is specified, the system displays the contents
of the LPALSTxx parmlib members at the operator's console
as the system processes the members.
The LPA parameter is only effective during cold starts. The
LPA parameter does not apply to modules requested
through the MLPA option.
63
6/17/2015
CodingaLPALSTxx Member
CodingaLPALSTxx Member(Cont.)
Some important syntax rules for the creation of
LPALSTxx are:
On each record, place a string of data set names
separated by commas.
If a data set is not cataloged in the system master
catalog, but is cataloged in a user catalog, specify in
parentheses immediately following the data set name
the one to six character VOLSER of the pack on which
the data set resides.
Indicate continuation by placing a comma followed by
at least one blank after the last data set name on a
record.
64
6/17/2015
DynamicLPAFunctions
DynamicLPAFunctions(Cont.)
How to perform dynamic LPA functions
The PROGxx parmlib member includes the LPA
statements, which are used to define what modules
can be added to or deleted from LPA after the IPL.
You use the SET command to validate the PROGxx
parmlib member; for example, SET PROG=xx.
The SETPROG LPA command may be used to initiate a
change (add or delete) to the LPA.
The DISPLAY PROG,LPA command may be used to
display information about modules that have been
added to LPA.
The CSVDYLPA macro allows an authorized program
to initiate dynamic LPA services.
65
6/17/2015
LinkedList(LNKLST)
LinkedList(LNKLST) (Cont.)
The LNKLST begins with these system data sets:

SYS1.LINKLIB
SYS1.MIGLIB
SYS1.CSSLIB
It is important to understand the relationship
between the LNKLST and LLA/VLF.
All LLAmanaged libraries must be cataloged. This
includes LNKLST libraries. The benefits of LLA
apply only to modules that are retrieved through
the following macros: LINK, LINKX, LOAD, ATTACH,
ATTACHX, XCTL, and XCTLX.
66
6/17/2015
DynamicLNKLSTFunctions
DynamicLNKLSTFunctions(Cont.)
How to perform dynamic LPA functions

You can create a PROGxx parmlib member with the
new changes to the LNKLST set, then issue the SET
PROG=xx operator command to activate the changes.
You can simply use the SETPROG LNKLST operator
command to update the LNKLST directly.
You can also use the D PROG,LNKLST command to
display information about the LNKLST set.
Finally, you can use CSVDYNL macro programming
service in an authorized program to change the
LNKLST concatenation for associated jobs and
address spaces.
67
6/17/2015
AuthorizedLibraries
AuthorizedLibraries(Cont.)
z/OS offers a mechanism called the authorized program
facility (APF) to restrict the access to sensitive system
functions or user programs. APF was designed to avoid
integrity exposures. The installation identifies what libraries
contain those special functions or programs. Those libraries
are then called APF (authorized program facility) libraries.
The modified link pack area (MLPA) may be used to contain
reenterable routines from APFauthorized libraries that are
to be part of the pageable extension to the link pack area
during the current IPL.
The MLPA exists only for the duration of an IPL. Therefore,
if an MLPA is desired, the modules in the MLPA must be
specified for each IPL (including quick start and warm start
IPLs).
68
6/17/2015
AuthorizedLibraries(Cont.)
APFauthorizedprogramsmustresideinoneofthe
followingauthorizedlibraries:
SYS1.LINKLIB
SYS1.SVCLIB
SYS1.LPALIB
Anauthorizedlibraryspecifiedbyyourinstallation
DynamicAPFFunctions
69
6/17/2015
DynamicAPFFunctions(Cont.)
Managing dynamic APF
Use PROGxx Parmlib member which includes the
appropriate APF statement to define the change.
The SETPROG AFP operator can also initiate a
change to the APF table.
The DISPLAY AFP command can be used to display
the list of libraries authorized by APF.
THANKYOU!!!
70

Introduction To ZOS

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Introduction To ZOS

Încărcat de

Drepturi de autor:

Formate disponibile

6/17/2015

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

A System Control Program (SCP) is an IBMsupplied program

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

The "P" in the seventh position indicates that the operator is to be

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

Initial program loading (IPL) provides a manual means

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

( A group Company of Maintec Technologies Pvt. Ltd.)

LOADPARM defines the address of the

( A group Company of Maintec Technologies Pvt. Ltd.)

The LOADxx member specifies: