Top Banner
CATALOG MANAGEMENT
91
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Catalog v 2.0 Day1

CATALOG MANAGEMENT

Page 2: Catalog v 2.0 Day1

CATALOGCATALOG

What is catalog?What is catalog?

It describes data set attributes and indicate It describes data set attributes and indicate the volumes on which a data set is located.the volumes on which a data set is located.

It is simply a data set, which contains the It is simply a data set, which contains the above description. above description.

Page 3: Catalog v 2.0 Day1

CATALOGCATALOG

What happen when a data set is What happen when a data set is cataloged?cataloged?

When a data set is cataloged, it can be When a data set is cataloged, it can be referred to by name without the user needing referred to by name without the user needing to specify where the data set is stored to specify where the data set is stored

Page 4: Catalog v 2.0 Day1

Catalog….Catalog…. Data sets can be cataloged, Uncataloged, or Data sets can be cataloged, Uncataloged, or

recataloged recataloged

All system managed DASD data sets are All system managed DASD data sets are cataloged automatically in a catalog.cataloged automatically in a catalog.

Cataloging on Magnetic tape is not required. Cataloging on Magnetic tape is not required.

Page 5: Catalog v 2.0 Day1

CatalogCatalog To find a data set that you have requested , To find a data set that you have requested ,

z/OS must know three pieces of informationz/OS must know three pieces of information DATA SET NAMEDATA SET NAME VOLUME NAMEVOLUME NAME UNITUNIT

3390 – DASD3390 – DASD 3590 - TAPE3590 - TAPE

Page 6: Catalog v 2.0 Day1

Types of CatalogsTypes of Catalogs

Integrated Catalog Facility CatalogsIntegrated Catalog Facility Catalogs

VSAM CatalogsVSAM Catalogs

OS CVOL (Control volume) CatalogsOS CVOL (Control volume) Catalogs

Page 7: Catalog v 2.0 Day1

ICF Catalog Structure ICF Catalog Structure

A catalog consists of two separate kinds of data A catalog consists of two separate kinds of data sets: sets:

A basic catalog structure (BCS)A basic catalog structure (BCS) A VSAM volume data set (VVDSA VSAM volume data set (VVDS))

Page 8: Catalog v 2.0 Day1

Basic catalog structure Basic catalog structure The BCS can be considered The BCS can be considered the the catalogcatalog

It is a VSAM key-sequenced data setIt is a VSAM key-sequenced data set

It uses the data set name of entries to store and retrieve It uses the data set name of entries to store and retrieve data set information.data set information.

For VSAM data sets, the BCS contains volume, security, For VSAM data sets, the BCS contains volume, security, ownership, and association information.ownership, and association information.

For non-VSAM data sets, the BCS contains volume, For non-VSAM data sets, the BCS contains volume, ownership, and association information. ownership, and association information.

Page 9: Catalog v 2.0 Day1

VSAM volume data set VSAM volume data set VVDS can be considered an extension of the VVDS can be considered an extension of the

volume table of contents (VTOC). It  is a VSAM volume table of contents (VTOC). It  is a VSAM entry-sequenced data set.entry-sequenced data set.

A VVDS resides on every volume that contains a A VVDS resides on every volume that contains a catalog or an SMS-managed data set that is catalog or an SMS-managed data set that is cataloged.cataloged.

It contains the data set characteristics, extent It contains the data set characteristics, extent information, and the volume-related information information, and the volume-related information of the VSAM data sets cataloged in the BCS. of the VSAM data sets cataloged in the BCS.

Page 10: Catalog v 2.0 Day1

Volume Table of Contents Volume Table of Contents z/OS uses a catalog and volume table of z/OS uses a catalog and volume table of

contents on each DASD to manage the storage contents on each DASD to manage the storage and the placement of data sets.and the placement of data sets.

z/OS requires a particular format of disks ,record z/OS requires a particular format of disks ,record 1 on the first track of the first cylinder provides 1 on the first track of the first cylinder provides the label for the disk, it contains the volume the label for the disk, it contains the volume serial number(6 characters) and a pointer to the serial number(6 characters) and a pointer to the VTOC. VTOC.

Page 11: Catalog v 2.0 Day1

VTOC….VTOC….

What VTOC should list?What VTOC should list? The data set that resides on its volumeThe data set that resides on its volume Meaning, the information about the Meaning, the information about the

location , size and other data set location , size and other data set attributesattributes

z/OS utility program ICKDSF, is used to z/OS utility program ICKDSF, is used to create the label and the VTOC.create the label and the VTOC.

Page 12: Catalog v 2.0 Day1

Volume Table of Contents Volume Table of Contents The VTOC index are system data sets that The VTOC index are system data sets that

maintain extent and allocation information for a maintain extent and allocation information for a volume. volume.

The VTOC is used to find empty space for new The VTOC is used to find empty space for new allocations and to locate non-VSAM data sets.allocations and to locate non-VSAM data sets.

For all VSAM data sets, and for SMS-managed For all VSAM data sets, and for SMS-managed non-VSAM data sets, the VTOC is used to non-VSAM data sets, the VTOC is used to obtain information not kept in the VVDS. obtain information not kept in the VVDS.

Page 13: Catalog v 2.0 Day1

VVDS EntriesVVDS Entries

VVRVVR

VVDS records for VSAM data sets are called VVDS records for VSAM data sets are called “VSAM volume records” (VVRs).“VSAM volume records” (VVRs).

NVRNVR

Those for SMS-managed non-VSAM data sets Those for SMS-managed non-VSAM data sets are called “non-VSAM volume records” (NVRs). are called “non-VSAM volume records” (NVRs).

Every catalog consists of one BCS and one or Every catalog consists of one BCS and one or more VVDSs. more VVDSs.

Page 14: Catalog v 2.0 Day1

Relationship of the BCS and the VVDSRelationship of the BCS and the VVDS

Page 15: Catalog v 2.0 Day1

Relationship of the BCS and the VVDSRelationship of the BCS and the VVDS

In the above figure shows a possible relationship In the above figure shows a possible relationship between two BCSs and three VVDSs on three disk between two BCSs and three VVDSs on three disk volumes. volumes.

““BCS.A” has entries for data sets residing on each BCS.A” has entries for data sets residing on each of the three volumes.of the three volumes.

“ “BCS.C” has entries for data sets residing on BCS.C” has entries for data sets residing on volumes B and C. Because each volume has data volumes B and C. Because each volume has data sets cataloged, each volume contains a VVDS. sets cataloged, each volume contains a VVDS.

  BCS.A resides on volume A with VVDS.A. Both the BCS.A resides on volume A with VVDS.A. Both the VVDS and the BCS have entries for each other. VVDS and the BCS have entries for each other.

Page 16: Catalog v 2.0 Day1

Relationship of the BCS and the VVDSRelationship of the BCS and the VVDS

All three VVDSs are cataloged in BCS.A. All three VVDSs are cataloged in BCS.A. BCS.C, residing on volume C, contains entries BCS.C, residing on volume C, contains entries for VVDS.C and VVDS.B. for VVDS.C and VVDS.B.

Notice that a VVDS has entries for Notice that a VVDS has entries for all all VSAM and VSAM and SMS-managed data sets on its volume, whereas SMS-managed data sets on its volume, whereas a BCS can have entries for data sets residing on a BCS can have entries for data sets residing on any volume. any volume.

Page 17: Catalog v 2.0 Day1

Using Access Method ServicesUsing Access Method Services

Using Access Method Services Using Access Method Services You use access method services to define and You use access method services to define and

maintain catalogs. maintain catalogs.

Access method services commands can also be Access method services commands can also be used to define and maintain catalog and non-used to define and maintain catalog and non-catalog data sets. catalog data sets.

Page 18: Catalog v 2.0 Day1

ACCESS METHOD SERVICE COMMANDS ACCESS METHOD SERVICE COMMANDS FOR CATALOGSFOR CATALOGS

ALTERALTER Alters previously defined catalog entries or Alters previously defined catalog entries or

certain catalog attributes, including entries for certain catalog attributes, including entries for tape volume catalogs. tape volume catalogs.

CREATECREATE Creates tape library or tape volume entriesCreates tape library or tape volume entries. .

DEFINEDEFINE Defines catalog entries. Defines catalog entries.

Page 19: Catalog v 2.0 Day1

ACCESS METHOD SERVICE COMMANDS ACCESS METHOD SERVICE COMMANDS FOR CATALOGSFOR CATALOGS

DEFINE CLUSTERDEFINE CLUSTER Defines VVDSs and catalog entries. Defines VVDSs and catalog entries.

DEFINE USER CATALOGDEFINE USER CATALOG Defines user catalogs including tape volume catalogs Defines user catalogs including tape volume catalogs

(DEFINE USERCATALOG VOLCATALOG). (DEFINE USERCATALOG VOLCATALOG).

DELETEDELETE Deletes catalog and VVDS entries, data sets, catalogs, Deletes catalog and VVDS entries, data sets, catalogs,

VVDSs, and data set control blocks in the VTOC. VVDSs, and data set control blocks in the VTOC.

Page 20: Catalog v 2.0 Day1

ACCESS METHOD SERVICESCOMMANDS ACCESS METHOD SERVICESCOMMANDS FOR CATALOGSFOR CATALOGS

DIAGNOSEDIAGNOSE Determines whether the content of BCS or VVDS records is invalid Determines whether the content of BCS or VVDS records is invalid

or unsynchronized. Diagnose recognizes tape library and tape or unsynchronized. Diagnose recognizes tape library and tape volume record types. It checks the cell structure of the volume volume record types. It checks the cell structure of the volume catalog. catalog.

EXAMINEEXAMINE Determines whether structural errors exist in the index or data Determines whether structural errors exist in the index or data

component of a BCS. component of a BCS.

EXPORT EXPORT Creates a backup copy of a catalog or copy that can be moved to Creates a backup copy of a catalog or copy that can be moved to

another system or volume another system or volume

Page 21: Catalog v 2.0 Day1

ACCESS METHOD SERVICESCOMMANDS ACCESS METHOD SERVICESCOMMANDS FOR CATALOGSFOR CATALOGS

EXPORT DISCONNECT EXPORT DISCONNECT  Disconnects the catalog from the master catalog. Disconnects the catalog from the master catalog.

IMPORTIMPORT Restores an exported backup copy of a catalog, or makes a catalog Restores an exported backup copy of a catalog, or makes a catalog

that was previously exported from one system available for use in that was previously exported from one system available for use in another system. another system.

Page 22: Catalog v 2.0 Day1

Catalog search orderCatalog search order The Catalog Search OrderThe Catalog Search Order When an application or user refers to a cataloged data set or When an application or user refers to a cataloged data set or

creates a data set that is to be cataloged, the configuration of creates a data set that is to be cataloged, the configuration of catalogs must be searched to find the appropriate catalog.catalogs must be searched to find the appropriate catalog.

The catalog is chosen according to a search order determined The catalog is chosen according to a search order determined by the aliases defined for the catalogs, the names of the by the aliases defined for the catalogs, the names of the catalogs, and the multilevel alias search level. catalogs, and the multilevel alias search level.

Two types of search order areTwo types of search order are

The Standard Search Order The Standard Search Order The Multilevel Alias Facility The Multilevel Alias Facility

Page 23: Catalog v 2.0 Day1

Catalog search orderCatalog search order The Standard Search Order The Standard Search Order

Most catalog searches should be based on catalog aliases.Most catalog searches should be based on catalog aliases.

When appropriate aliases are defined for catalogs, the high-When appropriate aliases are defined for catalogs, the high-level qualifier of a data set name is identical to a catalog alias level qualifier of a data set name is identical to a catalog alias and identifies the appropriate catalog to be used to satisfy the and identifies the appropriate catalog to be used to satisfy the request. request.

However, some alternatives to catalog aliases are available However, some alternatives to catalog aliases are available for directing a catalog request, specifically the CATALOG for directing a catalog request, specifically the CATALOG parameter of access method services and the name of the parameter of access method services and the name of the catalog. catalog.

Page 24: Catalog v 2.0 Day1

Master CatalogMaster Catalog Based on functionality, we have two types of CatalogsBased on functionality, we have two types of Catalogs

1. Master Catalog1. Master Catalog 2. User Catalog2. User Catalog

MASTER CatalogMASTER Catalog

The master catalog has the same structure as any other integrated The master catalog has the same structure as any other integrated catalog facility catalog. catalog facility catalog.

What makes it a master catalog is that all BCSs are cataloged in it, What makes it a master catalog is that all BCSs are cataloged in it, as well as certain data sets called "system data sets" (for instance, as well as certain data sets called "system data sets" (for instance, SYS1.LINKLIB and other "SYS1" data sets).SYS1.LINKLIB and other "SYS1" data sets).

Page 25: Catalog v 2.0 Day1

Master CatalogMaster Catalog

All other catalogs are called USER catalogs.All other catalogs are called USER catalogs.

Each system has its own master catalog. You identify Each system has its own master catalog. You identify

the master catalog in the SYSCATxx member of the master catalog in the SYSCATxx member of

SYS1.NUCLEUS, or the LOADxx member of SYS1.NUCLEUS, or the LOADxx member of

SYS1.PARMLIB.SYS1.PARMLIB.

Page 26: Catalog v 2.0 Day1

Master CatalogMaster Catalog

Contents of the Master CatalogContents of the Master Catalog

The master catalog for a system must contain entries for The master catalog for a system must contain entries for all user catalogs, and their aliases, which the system all user catalogs, and their aliases, which the system uses. uses.

The only other data sets which you should catalog in the The only other data sets which you should catalog in the master catalog are the system, or "SYS1," data sets.master catalog are the system, or "SYS1," data sets.

Page 27: Catalog v 2.0 Day1

The Master Catalog during system The Master Catalog during system initializationinitialization

During a system initialization, the master catalog is read so During a system initialization, the master catalog is read so

that system data sets and catalogs can be located. that system data sets and catalogs can be located.

Their catalog entries are placed in the cache that is selected Their catalog entries are placed in the cache that is selected

by the user for the master catalog as they are read. by the user for the master catalog as they are read.

Catalog aliases are also read during system initialization, but Catalog aliases are also read during system initialization, but

they are placed in an alias table separate from the cache that they are placed in an alias table separate from the cache that

is used for the master catalog. is used for the master catalog.

Thus, if the master catalog only contains entries for system Thus, if the master catalog only contains entries for system

data sets, catalogs, and catalog aliases, the entire master data sets, catalogs, and catalog aliases, the entire master

catalog is in main storage by the completion of the system catalog is in main storage by the completion of the system

initialization. initialization.

Page 28: Catalog v 2.0 Day1

Factors Affecting Catalog Performance Factors Affecting Catalog Performance

The main factors affecting catalog performance are The main factors affecting catalog performance are the amount of I/O required for the catalog and the the amount of I/O required for the catalog and the subsequent amount of time it takes to perform the I/O. subsequent amount of time it takes to perform the I/O.

Sharing a catalog between systems also affects Sharing a catalog between systems also affects performance. performance.

The use of JOBCAT and STEPCAT DD statements The use of JOBCAT and STEPCAT DD statements impacts the performance of a job, since job and step impacts the performance of a job, since job and step catalogs are searched before other catalogs.catalogs are searched before other catalogs.

These factors can be reduced by caching catalogs in These factors can be reduced by caching catalogs in special caches used only by catalogs. special caches used only by catalogs.

Page 29: Catalog v 2.0 Day1

Caching Catalogs Caching Catalogs

The simplest method of improving catalog performance is to use The simplest method of improving catalog performance is to use cache to maintain catalog records within main storage or data cache to maintain catalog records within main storage or data space. space.

Using cache reduces the I/O required to read records from catalogs Using cache reduces the I/O required to read records from catalogs on DASD. on DASD.

Two kinds of cache are available exclusively for catalogs.Two kinds of cache are available exclusively for catalogs.

The in-storage catalog (ISC) cache is contained within the catalog The in-storage catalog (ISC) cache is contained within the catalog address space (CAS) in main storage. address space (CAS) in main storage.

The catalog data space cache (CDSC) is separate from CAS and The catalog data space cache (CDSC) is separate from CAS and uses the MVS VLF component that stores the cached records in a uses the MVS VLF component that stores the cached records in a data space. data space.

Both types of cache are optional, and each can be cancelled and Both types of cache are optional, and each can be cancelled and restarted without an IPL. restarted without an IPL.

Page 30: Catalog v 2.0 Day1

ICF structureICF structure

Page 31: Catalog v 2.0 Day1

BCSBCS

Page 32: Catalog v 2.0 Day1

CATALOG FUNCTIONCATALOG FUNCTION

Page 33: Catalog v 2.0 Day1

Classification of BCSClassification of BCS By function BCSs can be classified into By function BCSs can be classified into

MASTER and USER CatalogMASTER and USER Catalog No structural difference between Master and No structural difference between Master and

User catalogUser catalog The same catalog can be master in one z/OS The same catalog can be master in one z/OS

and user in the other z/OS and user in the other z/OS What makes a Master catalog difference?What makes a Master catalog difference?

How it is used?How it is used? What data sets are cataloged in it? What data sets are cataloged in it?

Page 34: Catalog v 2.0 Day1

Master CatalogMaster Catalog One active master catalog per systemOne active master catalog per system It can be sharable between different MVS It can be sharable between different MVS

imagesimages Not necessary to reside on the system Not necessary to reside on the system

residence volumeresidence volume Master catalog for a system haveMaster catalog for a system have

Entries for all user catalogs and their aliases Entries for all user catalogs and their aliases that the system usesthat the system uses

Page 35: Catalog v 2.0 Day1

Master catalog….Master catalog….

Most recommendable in the master Most recommendable in the master catalogcatalog Only SYS1 data setsOnly SYS1 data sets User catalog connector recordsUser catalog connector records Aliases pointing to those connectorsAliases pointing to those connectors

Page 36: Catalog v 2.0 Day1

User CatalogUser Catalog

It should be used to contain information It should be used to contain information about your installation cataloged data sets about your installation cataloged data sets other than sys1 data setsother than sys1 data sets

Page 37: Catalog v 2.0 Day1

Using AliasesUsing Aliases Aliases are used to tell catalog management Aliases are used to tell catalog management

which user catalog your data set is cataloged in. which user catalog your data set is cataloged in.

It can be also used with NON-VSAM data sets in It can be also used with NON-VSAM data sets in order to create alternate names to the same order to create alternate names to the same data set. Those aliases are not related to the data set. Those aliases are not related to the user cataloguser catalog

Page 38: Catalog v 2.0 Day1

Using AliasesUsing Aliases

Page 39: Catalog v 2.0 Day1

Splitting CatalogSplitting Catalog

Page 40: Catalog v 2.0 Day1

When you need to split the catalog?When you need to split the catalog? If the catalog is unacceptably large , then you If the catalog is unacceptably large , then you

spilt the catalog in to two catalogsspilt the catalog in to two catalogs

If the catalog is of an acceptable size but If the catalog is of an acceptable size but contains entries for too many critical data sets contains entries for too many critical data sets

Page 41: Catalog v 2.0 Day1

How do you split?How do you split? To split a catalog or move group of entries use To split a catalog or move group of entries use

REPRO MERGECAT command.REPRO MERGECAT command.

What happened when you don’t split the What happened when you don’t split the catalog?catalog? Catalog failure would leave too many entries Catalog failure would leave too many entries

inaccessible. So you should split the catalog inaccessible. So you should split the catalog

Page 42: Catalog v 2.0 Day1

Splitting CatalogSplitting Catalog

Page 43: Catalog v 2.0 Day1

Splitting catalogSplitting catalog

Step1 :Step1 : Use ALTER LOCK to lock the existing Use ALTER LOCK to lock the existing

catalogcatalog//LOCKCAT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

ALTER ICFCAT.USER.VSYS303 LOCK

/*

////

Page 44: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Step2 Step2 Define new catalog with DEFINE Define new catalog with DEFINE

USERCATLOG LOCK USERCATLOG LOCK

Page 45: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Page 46: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Page 47: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Step 3Step 3 Get the catalog aliases your are going to Get the catalog aliases your are going to

move to the new catalogmove to the new catalog Use LISTCAT command with OUTFILE Use LISTCAT command with OUTFILE

optionoption

Page 48: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Page 49: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Step 4:Step 4: Ensure the status of catalog is error freeEnsure the status of catalog is error free Check the status by using EXAMINE & Check the status by using EXAMINE &

DIAGNOSE DIAGNOSE //DIAGNOSE EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//DIAGDD DD DISP=SHR,DSN=your.user.catalog

//SYSIN DD *

DIAGNOSE ICFCATALOG INFILE(DIAGDD)

Page 50: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

//EXAMINE1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

EXAMINE NAME(your.user.catalog) -

INDEXTEST NODATATEST ERRORLIMIT(1000)

//EXAMINE2 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

EXAMINE NAME(your.user.catalog) -

NOINDEXTEST DATATEST ERRORLIMIT(1000)

Page 51: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Step 5Step 5

Use REPRO MERGECAT without specifying Use REPRO MERGECAT without specifying the ENTRIES or LEVEL parameterthe ENTRIES or LEVEL parameter

OUTDATASET parameter specifies the OUTDATASET parameter specifies the catalog that you are keeping after the two catalog that you are keeping after the two catalogs are mergedcatalogs are merged

Page 52: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Page 53: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog…. Step 6Step 6

Use DELETE ALIAS & DEFINE ALIAS Use DELETE ALIAS & DEFINE ALIAS commands to delete the aliases of the commands to delete the aliases of the obsolete catalog and redefine the aliases for obsolete catalog and redefine the aliases for the new catalog you definedthe new catalog you defined. .

Page 54: Catalog v 2.0 Day1

Splitting catalog….Splitting catalog….

Step 7Step 7 Release the lock from the remaining Release the lock from the remaining

catalog by using ALTER UNLOCKcatalog by using ALTER UNLOCK

Page 55: Catalog v 2.0 Day1

Merging CatalogsMerging Catalogs

Page 56: Catalog v 2.0 Day1

Merging CatalogsMerging Catalogs Step 1 Step 1

Use ALTER LOCK to lock both catalogsUse ALTER LOCK to lock both catalogs Step 2Step 2

Get the aliases list , where you want to delete Get the aliases list , where you want to delete after the mergerafter the merger

Use LISTCAT commandUse LISTCAT command Step 3Step 3

Ensure the status of the catalog which are Ensure the status of the catalog which are error free by EXAMINE & DIAGONSEerror free by EXAMINE & DIAGONSE

Page 57: Catalog v 2.0 Day1

Merging catalogs….Merging catalogs…. Step 4 Step 4

Run the job of Merge by using REPRO Run the job of Merge by using REPRO MERGECAT MERGECAT

Step 5Step 5 Delete the aliases for the obsolete and Delete the aliases for the obsolete and

redefine the aliases for the new one by using redefine the aliases for the new one by using DELETE ALIASE & DEFINE ALIASE DELETE ALIASE & DEFINE ALIASE

Page 58: Catalog v 2.0 Day1

Merging catalogs….Merging catalogs…. Step 6Step 6

Delete the obsolete user catalog by using Delete the obsolete user catalog by using DELETE USERCATALOG with RECOVERYDELETE USERCATALOG with RECOVERY

STEP 7STEP 7 Remove the unwanted catalog connector Remove the unwanted catalog connector

entries , suppose your catalog is shared entries , suppose your catalog is shared So, use EXPORT DISCONNECT command So, use EXPORT DISCONNECT command

on each shared system on each shared system

Page 59: Catalog v 2.0 Day1

Merging CatalogsMerging Catalogs

Step 8Step 8 Release the lock from the remaining catalog by Release the lock from the remaining catalog by

using ALTER UNLOCKusing ALTER UNLOCK

Page 60: Catalog v 2.0 Day1

How to resize the catalog?How to resize the catalog? Step 1Step 1

Lock the catalogLock the catalog

Step 2Step 2 Issue the command to check the catalog is Issue the command to check the catalog is

shared with which systemsshared with which systems F CATALOG,NOVLF(ICFCAT.USER.VSYS303)

Page 61: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 2….Step 2…. If the catalog is shared with other systems and

those other systems do not all share the same master catalog, then EXPORT DISCONNECT the catalog on all other systems other than the system you are running the jobs to resize the catalog on.

Page 62: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 2….Step 2….//EXPDISC EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

EXPORT ICFCAT.USER.VSYS303 DISCONNECT

Page 63: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?.... step 3 Export the BCS with the EXPORT command.

The aliases of the catalog are saved with the exported copy, and can be used in later steps to redefine the aliases.

You must create a sequential data set for the catalog export, if one does not already exist.

Page 64: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 3….Step 3….//EXPORT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//EXPDD DD DSN=CATBACK.ICFCAT.USER.VSYS303,DISP=OLD

//SYSIN DD *

EXPORT ICFCAT.USER.VSYS303 -

OUTFILE(EXPDD) -

TEMPORARY

/*

Page 65: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 4Step 4 Delete the user catalog with RECOVERY Delete the user catalog with RECOVERY

optionoption//DELCAT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

DELETE ICFCAT.USER.VSYS303 -

RECOVERY -

USERCATALOG

/*

Page 66: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 5Step 5 Redefine the BCS (USER CATALOG) with Redefine the BCS (USER CATALOG) with

the desired space and performance the desired space and performance attributes.attributes.

Page 67: Catalog v 2.0 Day1

Step5 …. Step5 …. //DFNEWCAT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

DEFINE USERCATALOG -

(NAME(ICFCAT.USER.VSYS303) -

VOLUME(SYS303) -

MEGABYTES(15 5) -

ICFCATALOG -

LOCK -

FREESPACE(20 20) -

STRNO(3) -

) -

DATA( CONTROLINTERVALSIZE(4096) -

BUFND(4) ) -

INDEX( CONTROLINTERVALSIZE(4096) -

 

BUFNI(4) )

/*

Page 68: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 6Step 6

Import the BCS using the IMPORT command. Specify INTOEMPTY on the IMPORT command.

Also, specify ALIAS, so that the aliases exported with the catalog are redefined.

Page 69: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

//IMPORT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

IMPORT INDATASET(CATBACK.ICFCAT.USER.VSYS303) -

OUTDATASET(ICFCAT.USER.VSYS303) -

ALIAS -

LOCK -

INTOEMPTY

/*

Page 70: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?.... Step 7 If the catalog is shared with other systems that do

not share the same master catalog then you will need to IMPORT CONNECT on all other systems that share the catalog.

//IMPRTCON EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

IMPORT CONNECT -

OBJECTS((ICFCAT.USER.VSYS303) -

DEVICETYPE(3390) -

VOLUMES(SYS303)))

Page 71: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?.... Step 8 If the catalog is shared with other systems that

do not share the same master catalog then you will need to define the aliases for that catalog on the other systems that do not share the same master catalog.

Run DIAGONSE & EXAMINE commands and, if there are any errors, make the required corrections before unlocking the catalog.

Page 72: Catalog v 2.0 Day1

How to resize the catalog?....How to resize the catalog?....

Step 9Step 9 If there were no errors in the previous step , you

can now unlock the catalog:

//LOCKCAT EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

ALTER ICFCAT.USER.VSYS303 UNLOCK

/*

Page 73: Catalog v 2.0 Day1

How to Rename the catalog?How to Rename the catalog? You cannot directly rename a catalog with the ALTER

command.

To rename a catalog, you must define a new catalog with the desired name and copy the old catalog into it.

You can do this with the REPRO NOMERGECAT command.

REPRO NOMERGECAT is used to copy a catalog into an empty target catalog

Page 74: Catalog v 2.0 Day1

Catalog search order for locate Catalog search order for locate requestrequest

Page 75: Catalog v 2.0 Day1

Search order for locating data setSearch order for locating data set

Page 76: Catalog v 2.0 Day1

IPL IntroductionIPL Introduction

Page 77: Catalog v 2.0 Day1

Data set consideration IPL….Data set consideration IPL….

Page 78: Catalog v 2.0 Day1

Load Parameters IPL….Load Parameters IPL….

Page 79: Catalog v 2.0 Day1

IMSI CharacterIMSI Character

Page 80: Catalog v 2.0 Day1
Page 81: Catalog v 2.0 Day1

Hardware IPL FlowHardware IPL Flow

Page 82: Catalog v 2.0 Day1

Types of IPL….Types of IPL…. DEPENDING ON THE LEVEL OF CUSTOMIZATION, A DEPENDING ON THE LEVEL OF CUSTOMIZATION, A

SYSTEM IPL CAN BRING UP MANY DIFFERENT SYSTEM IPL CAN BRING UP MANY DIFFERENT CONFIGURATIONS, BUT THERE ARE ONLY THREE CONFIGURATIONS, BUT THERE ARE ONLY THREE BASIC TYPES OF IPL:BASIC TYPES OF IPL:

COLD START COLD START

QUICK STARTQUICK START

WARM STARTWARM START

Page 83: Catalog v 2.0 Day1

COLD STARTCOLD START ANY IPL THAT LOADS OR RELOADS THE PAGEABLE ANY IPL THAT LOADS OR RELOADS THE PAGEABLE

LINK PACK AREA (PLPA) AND DOES NOT PRESERVE LINK PACK AREA (PLPA) AND DOES NOT PRESERVE VIO DATA SETS.VIO DATA SETS.

THE FIRST IPL AFTER SYSTEM INSTALLATION IS THE FIRST IPL AFTER SYSTEM INSTALLATION IS ALWAYS A COLD START BECAUSE THE PLPA MUST ALWAYS A COLD START BECAUSE THE PLPA MUST BE INITIALLY LOADED.BE INITIALLY LOADED.

Page 84: Catalog v 2.0 Day1

COLD START ….COLD START …. AT THE FIRST IPL AFTER SYSTEM INSTALLATION AT THE FIRST IPL AFTER SYSTEM INSTALLATION

THE PLPA WILL AUTOMATICALLY BE LOADED FROM THE PLPA WILL AUTOMATICALLY BE LOADED FROM THE LPALST CONCATENATION.THE LPALST CONCATENATION.

THE PAGE DATA SETS FOR THIS IPL WILL BE THOSE THE PAGE DATA SETS FOR THIS IPL WILL BE THOSE SPECIFIED IN IEASYSXX, PLUS ANY ADDITIONAL SPECIFIED IN IEASYSXX, PLUS ANY ADDITIONAL ONES SPECIFIED BY THE OPERATOR.ONES SPECIFIED BY THE OPERATOR.

SUBSEQUENT IPLS NEED ONLY BE COLD STARTS IF SUBSEQUENT IPLS NEED ONLY BE COLD STARTS IF THE PLPA HAS TO BE RELOADEDTHE PLPA HAS TO BE RELOADED

Page 85: Catalog v 2.0 Day1

COLD START….COLD START…. ANY IPL THAT LOADS OR RELOADS THE ANY IPL THAT LOADS OR RELOADS THE

PAGEABLE LINK PACK AREA (PLPAPAGEABLE LINK PACK AREA (PLPA) )

CLPACLPA

DOES NOT PRESERVE VIO DATA SETS.DOES NOT PRESERVE VIO DATA SETS.

CVIO CVIO

Page 86: Catalog v 2.0 Day1

Quick StartQuick Start ANY IPL THAT DOES ANY IPL THAT DOES NOT RELOAD THE PLPANOT RELOAD THE PLPA

AND AND DOES NOT PRESERVE VIO DATA SETS.DOES NOT PRESERVE VIO DATA SETS.

THE SYSTEM WILL RE-CREATE PAGE AND THE SYSTEM WILL RE-CREATE PAGE AND SEGMENT TABLES TO MATCH THE IN-USE SEGMENT TABLES TO MATCH THE IN-USE PLPA.PLPA.

YOU WOULD NORMALLY PERFORM A QUICK YOU WOULD NORMALLY PERFORM A QUICK START IPL AFTER A POWER UP. START IPL AFTER A POWER UP.

Page 87: Catalog v 2.0 Day1

Quick Start….Quick Start…. THE PLPA FROM THE PREVIOUS SESSION THE PLPA FROM THE PREVIOUS SESSION

CAN BE USED WITHOUT RELOADING IT CAN BE USED WITHOUT RELOADING IT FROM THE LPALST CONCATENATION.FROM THE LPALST CONCATENATION.

A QUICK START CAN BE INITIATED BY A QUICK START CAN BE INITIATED BY REPLYING CVIO (CLEAR VIO) TO THE REPLYING CVIO (CLEAR VIO) TO THE SPECIFY SYSTEM PARAMETERS PROMPT.SPECIFY SYSTEM PARAMETERS PROMPT.

Page 88: Catalog v 2.0 Day1

WARM StartWARM Start ANY IPL THAT ANY IPL THAT DOES NOT RELOADDOES NOT RELOAD THE THE

PLPA AND PLPA AND PRESERVES JOURNALED VIO PRESERVES JOURNALED VIO DATA SETS.DATA SETS.

THE THE OPERATOR DOES NOT ENTER CLPA OPERATOR DOES NOT ENTER CLPA OR CVIOOR CVIO AT THE SPECIFY SYSTEM AT THE SPECIFY SYSTEM PARAMETERS PROMPT.PARAMETERS PROMPT.

Page 89: Catalog v 2.0 Day1

Hardware IPL SummaryHardware IPL Summary

Page 90: Catalog v 2.0 Day1

IPL Resource InitializationIPL Resource Initialization

Page 91: Catalog v 2.0 Day1

Thank YouThank You