Introduction to ZOS

6/17/2015

1

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)

Introductiontoz/OS


z/OSservices

6/17/2015

2


z/OSandz/OS.e


Hardwarerequirements

6/17/2015

3


z/Seriesserver:BasicandLPARmode


z/OSBaseControlProgram(BCP)

6/17/2015

4


z/OSbaseelement


z/OSoptionalfeatures

6/17/2015

5


DataFacilityStorageManagementSubsystem(DFSMS)


z/OSCommunicationsServer:TCP/IP

6/17/2015

6


ResourceManagementFacility(RMF)


SystemManagementFacility(SMF)

6/17/2015

7

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) TimeSharingOption/Extended

(TSO/E)


LibraryLookaside (LLA)

6/17/2015

8


WorkloadManager(WLM)


z/OSoperations

6/17/2015

9


Basicaspectsofz/OSimplementation


MVSConsoleConfiguration

6/17/2015

10


MVSConsoleConfiguration(Cont.) Generally, operators on an MVS system receive messages and enter

commands on Multiple Console Support (MCS) consoles. Operators can useother consoles like NetView consoles or System Display and Search Facility(SDSF) consoles or Resource Measurement Facility (RMF) consoles to interactwith MVS but we will focus on MCS consoles.

MCS consoles are devices that are locally attached to an MVS system andprovide the basic communication between operators and MVS

One MCS console is designated as the master console and has full capabilityto view messages and to enter all MVS commands.

Other MCS consoles can be defined so that the message traffic can be spreadacross multiple consoles.

There is also a system console. An operator uses the system console toinitialize MVS. The system console is not defined to MVS and is not underMCS control


MVSSysplex ConsoleConfiguration

6/17/2015

11


MCSConsole


MCSConsole(Cont.)

6/17/2015

12


HARDCOPYLOG


SystemDatasets

6/17/2015

13


SYS1.PARMLIB


Rulesforparmlib memberdefinitions

6/17/2015

14


Systemsymbols


Systemsymbols:Types

6/17/2015

15


UsingSystemSymbolsinParmlib


WheretoUsetheSystemSymbols

6/17/2015

16


ExampleofSystemSymbolsSYSDEF LPARNAME(P390)

SYSNAME(P390) SYSCLONE(P1)

SYSDEF LPARNAME(Q390) SYSNAME(Q390) SYSCLONE(Q1)


Logicalparmlib

6/17/2015

17


Parmlib concatenation


STARTINGTHEIPL

6/17/2015

18


STARTINGTHEIPL


STARTINGTHEIPL(CONT.) The initialization process begins from the system console.

The system console is the one that communicates with thehardware 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 programthat is fundamental to the operation of the system in ourcase it's MVS.

6/17/2015

19


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 isknown as the system residence (SYSRES) volume.

The SYS1.SVCLIB data set must also be located on the SYSRESvolume. SYSl.SVCLIB contains error recovery routines that maybe required during the IPL process.

The SYSRES volume must also contain the IPL text a specializedprogram that resides on cylinder 0, head 0 of the volume. It isthe first thing read into central storage during the IPL processand is used to begin the transfer of data from the SYSRESvolume into central storage.

Other system data sets may, and usually do, reside on thesystem residence volume.

6/17/2015

20


LOADPARAMETER


LOADPARAMETER(CONT.) With MVS systems beginning with MVS/SP Version A, theI/O configuration information may be in an IODF, and thatIODF may reside on a volume other than the systemresidence volume. The Load Parameter field points to thevolume that contains the IODF and a LOADnn member of asystem library either SYS1.PARMLIB or SYSn.IPLPARM.

The last position of the Load Parameter provides a way ofpointing to an alternate nucleus member of theSYS1.NUCLEUS data set.

The second last position of the Load Parameter controlsmessage suppression during the IPL process.

6/17/2015

21


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 volume0250 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 beprompted during the IPL process for any overrides to the values specifiedin the LOAD00 member or in SYS1.PARMLIB.

The "1" in the last position indicates that IEANUC01 is to be used for thisIPL. II would override the specification in LOAD00.

6/17/2015

22


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 relevantLOADnn member.

In this example, the "Load Parm(A/N)" field will be used to locate the LOADnnmember as well as to point to the volume containing the production IODF.

Device number 0260 is to be searched for the LOAD01 member ofSYSN.IPLPARM. Device number 0260 also contains the production IODF.

The "M" in the seventh position indicates that messages during the IPL processare 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 theSYS1.NUCLEUS data set is to be selected for this IPL. This overrides thespecification in the NUCLEUS statement of LOAD01

6/17/2015

23


INTIALPROGRAMLOAD(IPL)


INTILAPROGRAMLOAD(IPL) (CONT.) The IPL program loads the selected nucleusmember of SYS1.NUCLEUS.

The IPL program also selects the appropriate I/Oconfiguration from either the SYS1.NUCLEUS dataset (if MVSCP was used to define the I/Oconfiguration) or from the production IODF (if HCDwas used to define the I/O configuration).

A Nucleus Initialization Program (NIP) resides inthe lEANUC0n member and receives control fromthe IPL program to complete the nucleusinitialization process.

6/17/2015

24

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) IPLonz/OS


IPLonz/OS(CONT.) Initial program loading (IPL) provides a manual meansfor causing a program to be read from a designateddevice and for initiating execution of that program.When the system hardware is ready, you can use thesystem console to load the system software.

During initialization of a z/OS system, the operatoruses the system console, which is connected to theprocessor controller or support element.

The LOADxx parmlib member allows your installationto control the initialization process. For example, inLOADxx, you specify IEASYSxx or IEASYMxx membersthat the system is to use.

6/17/2015

25


TYPESofIPLs


TYPESofIPLs(CONT.) Cold Start: Any IPL that loads or reloads thePageable Link Pack Area (PLPA) and does notpreserve VIO data sets. The first IPL after systeminstallation is always a cold start because thePLPA must be initially loaded. The PLPA needs tobe reloaded: At the first IPL after system initialization, when thesystem loads it automatically.

After modifying one or more modules in the LPALSTconcatenation.

At the time of Cold Start, Its bring all the subsystemsautomatically.

6/17/2015

26


TYPESofIPLs(CONT.) Warm Start: Any IPL that does not reload thePLPA and preserves journaled VIO data sets. Theoperator does not enter CLPA or CVIO at theSPECIFY SYSTEM PARAMETERS prompt. Anydefinitions of existing page data sets as nonVIOlocal page data sets are preserved.

At the time of Warm Start, Its bring all thesubsystems except DB2, CICS and IMS.


TYPESofIPLs(CONT.) Quick Start Any IPL that does not reload the PLPAand does not preserve VIO data sets. The systemrecreates page and segment tables to match theinuse PLPA. You would normally perform a QuickStart IPL after a power up.

At the time of Quick Start, Its bring only threesubsystems like JES2, RACF and TSO.

6/17/2015

27


WhathappenDuringtheIPLLOAD SUCCESSFUL is a message fromthe IPL hardware/microcode. IPL does:1) Hardware system reset2) Optional memory clear3) SPOOL Memory will be cleared4) System Dataset will be compressed5) System will be reset to Current Stage


LibrariesandMembersatIPLtime An number of libraries must be presentfor the system to load at IPL time.SYS1.PARMLIB contains the requireddefinitions

SYSn.IPLPARM searched for LOADxxSYS1.LPALIBSYS1.PROCLIBSYS1.NUCLEUS

6/17/2015

28


LOADxx LOADPARM defines the address of theIODF and the suffix of the LOADxxmember

At IPL the system searches for LOADxx in:SYS0.IPLPARM SYS9.IPLPARM on IODFvolume

SYS1.PARMLIB on the IODF volumeSYS1.PARMLIB on the IPL volume


LOADxx The LOADxxmember specifies:

The IODF data set nameThe master catalog name and volumeThe parmlib concatenationThe IEASYSxx member to use

6/17/2015

29


IPLStartUp


Parmlib Commands The parmlib concatenation can bedisplayed using D PARMLIB

The parameters used at IPL can bedisplayed using D IPLINFO

The parmlib concatenation can bemodified dynamically using SETLOADxx,PARMLIB (Please dont try thisCommand)

6/17/2015

30


CommandstoDisplayParmlibD 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

6/17/2015

31

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)InitializationVIAAutomaticCommands

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)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)

6/17/2015

32

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)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

6/17/2015

33


IEASYSxx (Cont.)

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) IEASYMxx

6/17/2015

34


Catalog


Catalog(Cont.)Ensuring that your catalogs are effectively managed istherefore a crucial aspect of DASD management. Someof the most common catalog management tasks that asystem 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

6/17/2015

35


MasterCatalog

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) MasterCatalog(Cont.)

Every MVS system relies on the master catalog at IPL time to locate system datasets.

The LOADxx member of PARMLIB contains the SYSCAT statement, which identifiesthe 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 iscalled the multilevel alias facility.

The '3C' indicates the lower limit for the number of tasks started to service catalogrequests.

The master catalog is vital for the correct running of the system. To minimize itsexposure during normal running, updates are restricted to those users authorizedto do so. This should only be the systems programmers and the storageadministrators. User errors may easily cause attempted updates to the mastercatalog.

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).

6/17/2015

36


SeparatingofSoftware


SeparatingofSoftware(Cont.)Thekindsofdatayoushouldseparatefromz/OSsoftwareare: Customizationdata,includingmostsystemcontrolfiles

NonIBMsoftware IBMnonz/OSproducts,forexampleCICSandDB2

Userdefinedexits Userdata

6/17/2015

37


PlacingdatasetsonSpecificVolumes

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) PlacingofDatasetsonSpecific

Volumes(Cont.)Some SYSRES volume types, such as the 33903, are not bigenough to hold all the target libraries for a z/OS system.Therefore, you have to move some data sets to SYSRES logicalextension volumes (or overflow volumes). The considerations youshould take into account for placing data sets on specific volumesare: 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

6/17/2015

38


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

6/17/2015

39


TargetLIBVolumes(Cont.)Secondarytargetvolumes(TVOL2TVOLn)datasetsare: FixedblockCLISTandEXEClibraries SampleandJCLlibraries Sourcelibraries Macrolibraries Workstation SoftcopylibrariesintowhichSMP/Einstalls Fontandprintinglibraries FlatfilesthatSMP/Ecannotmanage SMP/EtargetCSI SMP/Etargetdatasets


TargetLIBVolumes(Cont.)Subsystem target volume The libraries on this volumeconsist of the subsystem product sets (for example,CISCS, DB2, IMS, or NCP). The recommended types ofdata 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 librariesincluding SMP/E CSIs are cataloged.

6/17/2015

40


DistributionLIBVolumes


ImageRelatedVolumes

6/17/2015

41


ImageRelatedVolumes(Cont.)Page data sets volume 1 PLPA (onecylinder allocation) COMMONPage 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

6/17/2015

42


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 DAEdatasetJEScheckpointvolume FormaximumperformanceandreducedcontentionJESspoolvolume


ClusterRelatedVolumes(Cont.)Sysplexrelatedvolume1 SYSPLEXprimary CFRMalternate ARMprimary WLMprimary LOGRprimary OMVSprimarySysplexrelatedvolume2 Sysplex alternate CFRMalternate ARMalternate WLMalternate LOGRalternate OMVSalternate SecondaryRACFdatabaseSoftcopyvolume Books Bookshelves Bookindexes

6/17/2015

43


SystemDatasets


MVSMessagesDetails Messages have two parts

The message text provides information or describes anerror.

The message ID normally consists of a prefix, a serialnumber and a code.

6/17/2015

44


MVSMessagesDetails(Cont.) The message ID normally consists of a

Prefix Serial Number Code

IEA000I 590,INT REQ,D2,0200,,,SYS122A IEx MVS messages IST VTAM messages IGD SMS messages $HASP JES2 messages IAT JES3 messages


MVSMessagesDetails(Cont.) 000 A serial number to identify the individualmessage

I A code to indicate the type of message. Valid options are

A An operator action is required D An operator decision is required E Eventual operator action is required I Informational message; no action required W Processing is stopped until you perform an action

6/17/2015

45


MVSMessagesDetails(Cont.) Action messages are Highlighted and become nondeletable Prefixed with a symbol (* or @) that indicates anoperator action is expected

Ex: *IEF233A M 580,323947,,SYS122A,STEP01,SYS122.DATA

The * indicates that it is a systemissued messagethat requires operator action.

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


MVSMessagesDetails(Cont.) An action message prefixed with a two digit number isconsidered an outstanding reply, and you must respond.

*95IEF238D TF08QCPY REPLY DEVICE NAME,'WAIT' OR 'CANCEL Function:Torespondtosystemrequestsforinformation Syntax:id Description:RIndicatesamessagereply idThetwodigitreplynumberfromthemessagethatrequiresanoperatorreplytextTheresponsetothemessage

Afteryouperformtherequiredaction Theactioncharacterisreplacedwitha Themessagehighlightingiseliminated Themessagebecomesdeletable

6/17/2015

46


MVSMessagesDetails(Cont.)References MVSSystemCommands MVSSystemMessagesVolume1toVolume 10 MVSDataAreasVolume1toVolume 6


SystemDatasetsHousekeeping

6/17/2015

47

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)SystemDatasetsHousekeeping(Cont.)

SMF records The SMF records contain a variety of informationthat enables you to produce many types of analysis reports andsummary reports so that you can evaluate changes inconfiguration, workload, or job scheduling procedures bystudying the trends in the data.

LOGREC data The LOGREC data set contains statistical dataabout machine failures (processor failures, I/O device errors,channel errors).

SYSLOG data This data set resides in JES2's spool space. It canbe used by application and system programmers to recordcommunications about problem programs and system functions.It also contains a record of console messages and operatorcommands for audit and diagnosis purposes.

System DUMP data sets These are sequential data sets whichcontain system dumps that record areas system task failures.


SMFData

6/17/2015

48


SMFData(Cont.)How to collect SMF dataTo record SMF data, you have to allocate direct access space andcatalog the SMF data sets. You should allocate at least two datasets 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 willeventually 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 devicetype 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

6/17/2015

49


SMFPRMxx Parmlib Member(Cont.) Once you have allocated all the required SMF datasets, you have to update the SMFPRMxx inSYS1.PARMLIB to reflect the new SMF data sets. Inorder to enable SMF recording, make sure thatthe first parameter in SMFPRMxx is set to ACTIVE.

To activate the new changes to SMF parameters,you can use the SET command to make themeffective (assuming that you have addedSYS1.MAN3 to SMFPRM00) issuing the SETcommand.

SET SMF=00 (Please dont Try this Command)


SMFPRMxx Parmlib Member(Cont.)IEF196IIEF237I0800ALLOCATEDTOIEFPARMIEE252IMEMBERSMFPRM00FOUNDINSYS1.PARMLIBIEF196IIEF237I0802ALLOCATEDTOSYS00004IEE966ISYS1.MAN3ISBEINGFORMATTED1IEF196IIEF285ISYS1.PARMLIBKEPTIEF196IIEF285IVOLSERNOS=MPRES1.IEE949I03.01.03SMFDATASETS097

NAMEVOLSERSIZE(BLKS)%FULLSTATUS2PSYS1.MAN1MPCAT172009ACTIVE

SSYS1.MAN2MPCAT118000ALTERNATESSYS1.MAN3MPCAT118000ALTERNATE

IEE536ISMFVALUE00NOWINEFFECT1.SMFfoundthatSYS1.MAN3hasnotbeenformatted.Theformattingisnowtakingplace.2.ThenameoftheSMFdatasetprecededbyaPindicatesthatitistheprimarySMFdataset.IfthenameisprecededbyanS,thedatasetisasecondarySMFdataset.

6/17/2015

50

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)SMFPRMxx Parmlib Member(Cont.)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 allSMF records.

However, this can create considerable overhead and fill up the SMF data sets veryquickly.

The default SYS parameter is SYS(NOTYPE(14:19,62:69,99). This collects all SMFrecords 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

6/17/2015

51


LOGRECData(Cont.)How to create SYS1.LOGRECWhen an error occurs, the system records information aboutthe error in the LOGREC data set. The information provides youwith 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 errorBefore the system can record all this information, you mustfirst allocate the LOGREC data set and initialize it.Note: Whenever you allocate or reallocate the LOGREC dataset, the newly allocated data set will not be used until youinitialize 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 consolemessages appear requesting the operator to takeaction. Therefore, this data set needs to be clearedso that it can be reused. There is only one LOGRECdata set for z/OS.

As a system programmer have to set up a processto clear the LOGREC data set when the followingmessage appears:

IFB080ELOGRECDATASETISFULL,DSN=SYS1.LOGREC

6/17/2015

52


LOGRECData(Cont.)You can use the following sample JCL to clear theLOGREC 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

SYSUMACC=YZERO=Y

The job will copy the LOGREC data set to the data setspecified in the DDNAME ACCDEV, print a brief summaryof LOGREC data, and then clear the data set.


SYSLOGData

6/17/2015

53

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) SYSLOGData(Cont.)The SYSLOG on the MVS system actually consists of two separatelogs: 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 operatorThe SYSLOG is a SYSOUT data set provided by the JES2. SYSOUTdata sets are output spool data sets on DASD. An installationshould print the SYSLOG periodically to check for problems. TheSYSLOG consists of the following: All messages issued through Write To Log (WTL) macros &

entered by the LOG operator commands. Usually, the hardcopy log.


OtherAdministrationTasks

6/17/2015

54


OtherAdministrationTasks(Cont.) WorkwithMIH Addpagedatasets ChangeTSOtimeout Addspoolvolumes Deletespoolvolumes Verifysystemconfiguration ViewSYSOUTusingISPF ChangeyourTSOprofile Backupandrestorez/OS


WhyMainframeisnotdeadSTILL?OLDMAINFRAMERSWILLNEVERDIE

BECAUSETHEYJUSTTAKEDUMPANDReIPL

6/17/2015

55


Subsystems&SubsystemInterface(SSI)

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)Definingsubsystemsandsubsystem

interface

6/17/2015

56


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 theseinterfaces are the following: JES2, JES3, IMS, NetView etc.The master subsystem (MSTR) is a part of MVS and is not definedin any of these ways.


WhatisSubsystem?(Cont.)There are four types of subsystems: The master scheduler subsystem is used to establishcommunication between the operating system and theprimary job entry subsystem, which can be JES2 or JES3. Itis also used to initialize system services such as the systemlog and communications task.

The primary subsystem is the job entry subsystem thatMVS uses to do work. It can be either JES2 or JES3.

Secondary subsystems provide functions as needed by IBMproducts, vendor products, or the installation.

Functional subsystems: JES2/JES3 allows certain functionsto operate outside the JES2/JES3 address space.

6/17/2015

57


WhatisSubsystemInterface? The SSI is the interface used by routines (IBM,vendor, or installationwritten) to requestservices of, or to pass information to, subsystems.

The SSI is a way for one routine to call anotherroutine. There are a number of other ways that aroutine can call another routine, such as: Link register LINK or LINKX macro Program call (PC) SVC


SubsystemInitialization

6/17/2015

58


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 canselect either JES2 or JES3. If you do not specify an IEFSSNxx member inSYS1.PARMLIB, MVS attempts to use the system default member,IEFSSN00. IEFSSN00, as supplied by IBM, contains the definition for thedefault primary JES2.

If you attempt to IPL without specifying an IEFSSNxx member, andIEFSSN00 is not present or does not identify the primary subsystem, thesystem issues message IEFJ005I and prompts the operator for theprimary subsystem.

If we didnt define a subsystem more than once in a combination ofIEFSSNxx members that can be used together or within a single member.The same subsystem can appear in two different IEFSSNxx memberswhen the members will not be used together. In general, if MVS detectsa 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 subsystemThere are two ways to initialize your subsystem: Specifying an initialization routine Using the START command

Specifying an initialization routineYou can optionally specify the name of your subsysteminitialization routine when you define your subsystem. If thefunctions the subsystem supplies might be needed during theIPL process, define your initialization routine in IEFSSNxx.

Using the START commandIf the subsystem functions are not needed until a later time,you can use the START command to initialize your subsystem.

6/17/2015

59

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) SubsystemDefinitions

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)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 samesubsystem name, the duplicate statements will be rejected with a failuremessage that is sent to the console.

SUBNAME(subname) The subsystem name. The name can be up to fourcharacters 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 messagesthat the SSI issues as part of initialization processing are to be routed. Thedefault is to issue messages to the master console.

INITRTN(initrtn) The name of the subsystem initialization routine. Thisname is optional and can be one to eight characters long. The first charactercan be either alphabetic or special. The remaining characters can be eitheralphanumeric or special.

6/17/2015

60

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)SubsystemDefinitions(Cont.) INITPARM(initparm) Input parameters to be passed to the

subsystem initialization routine. The input parameters are optionaland are variable in length for a maximum of 60 characters. Ifblanks, commas, single quotes, or parentheses are included in theinput parameters, the entire parm field must be enclosed in singlequotes.

PRIMARY({NO|YES}) This parameter indicates whether this is theprimary subsystem. The primary subsystem is typically a JES2. Thisparameter is optional. Initialize the primary subsystem before anysecondary subsystem(s) except SMS. The IEFSSNxx parmlibmember is the only place you can define the primary subsystem. Itcannot be defined using the dynamic SSI services IEFSSIREQUEST=ADD macro or the SETSSI ADD command. The default isNO.

START({YES|NO}) This parameter indicates whether an automaticSTART command should be issued for the primary subsystem.

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) JES2supportedSSIfunctions

6/17/2015

61


LPA,LNKLST&APFLibraries

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) LinkPackArea(LPA)

6/17/2015

62


LinkPackArea(LPA) (Cont.) Link pack area (LPA) modules are loaded in commonstorage, shared by all address spaces in the system.Modules found in LPA do not need to be brought intovirtual storage because they are already in virtualstorage.

Modules placed anywhere in LPA are always in virtualstorage, and modules placed in FLPA are also always incentral storage.

LPA pages are only stolen, and never paged out,because there are copies of all LPA pages in the LPApage data set.

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.) LPASubAreasThe link pack area (LPA) is a section of the common area of an addressspace. It exists below the system queue area (SQA) and consists of thepageable link pack area (PLPA), then the fixed link pack area (FLPA) if oneexists, 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 maintainsrecords that have pointers to the PLPA and extended PLPA pages.

MLPA This area may be used to contain reenterable routines fromAPFauthorized libraries that are to be part of the pageable extensionto the link pack area during the current IPL. The MLPA exists only forthe duration of an IPL.

Note: FLPA & MLPA has to be specified during the WARM & Quick Start.

6/17/2015

63


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, areappended to LPALST to form the name of the LPALSTxxparmlib members.

If the L option is specified, the system displays the contentsof the LPALSTxx parmlib members at the operator's consoleas the system processes the members.

The LPA parameter is only effective during cold starts. TheLPA parameter does not apply to modules requestedthrough the MLPA option.

6/17/2015

64


CodingaLPALSTxx Member


CodingaLPALSTxx Member(Cont.)Some important syntax rules for the creation ofLPALSTxx are: On each record, place a string of data set namesseparated by commas.

If a data set is not cataloged in the system mastercatalog, but is cataloged in a user catalog, specify inparentheses immediately following the data set namethe one to six character VOLSER of the pack on whichthe data set resides.

Indicate continuation by placing a comma followed byat least one blank after the last data set name on arecord.

6/17/2015

65


DynamicLPAFunctions


DynamicLPAFunctions(Cont.)How to perform dynamic LPA functions The PROGxx parmlib member includes the LPAstatements, which are used to define what modulescan be added to or deleted from LPA after the IPL.You use the SET command to validate the PROGxxparmlib member; for example, SET PROG=xx.

The SETPROG LPA command may be used to initiate achange (add or delete) to the LPA.

The DISPLAY PROG,LPA command may be used todisplay information about modules that have beenadded to LPA.

The CSVDYLPA macro allows an authorized programto initiate dynamic LPA services.

6/17/2015

66


LinkedList(LNKLST)

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)LinkedList(LNKLST) (Cont.)The LNKLST begins with these system data sets: SYS1.LINKLIB SYS1.MIGLIB SYS1.CSSLIB It is important to understand the relationshipbetween the LNKLST and LLA/VLF.

All LLAmanaged libraries must be cataloged. Thisincludes LNKLST libraries. The benefits of LLAapply only to modules that are retrieved throughthe following macros: LINK, LINKX, LOAD, ATTACH,ATTACHX, XCTL, and XCTLX.

6/17/2015

67


DynamicLNKLSTFunctions

S c o p e U n l im i t e d( A group Company of Maintec Technologies Pvt. Ltd.)DynamicLNKLSTFunctions(Cont.)How to perform dynamic LPA functions You can create a PROGxx parmlib member with thenew changes to the LNKLST set, then issue the SETPROG=xx operator command to activate the changes.

You can simply use the SETPROG LNKLST operatorcommand to update the LNKLST directly.

You can also use the D PROG,LNKLST command todisplay information about the LNKLST set.

Finally, you can use CSVDYNL macro programmingservice in an authorized program to change theLNKLST concatenation for associated jobs andaddress spaces.

6/17/2015

68


AuthorizedLibraries


AuthorizedLibraries(Cont.) z/OS offers a mechanism called the authorized programfacility (APF) to restrict the access to sensitive systemfunctions or user programs. APF was designed to avoidintegrity exposures. The installation identifies what librariescontain those special functions or programs. Those librariesare then called APF (authorized program facility) libraries.

The modified link pack area (MLPA) may be used to containreenterable routines from APFauthorized libraries that areto be part of the pageable extension to the link pack areaduring 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 bespecified for each IPL (including quick start and warm startIPLs).

6/17/2015

69


AuthorizedLibraries(Cont.)APFauthorizedprogramsmustresideinoneofthefollowingauthorizedlibraries: SYS1.LINKLIB SYS1.SVCLIB SYS1.LPALIB Anauthorizedlibraryspecifiedbyyourinstallation


DynamicAPFFunctions

6/17/2015

70


DynamicAPFFunctions(Cont.)Managing dynamic APF Use PROGxx Parmlib member which includes theappropriate APF statement to define the change.

The SETPROG AFP operator can also initiate achange to the APF table.

The DISPLAY AFP command can be used to displaythe list of libraries authorized by APF.


THANKYOU!!!

Documents

Introduction to ZOS