------DB2------

1.Difference between Z/Os and LUW

Lets see in different prespective:

Installation : there is basically one choice for z/OS. For the LUW
environments, there are several editions to choose from. The
Enterprise Server Edition (ESE) is the most common. The installation of DB2
in the z/OS environment is known as a subsystem. When a subsystem is
created, four system databases are created, 80 bufferpools (BPs) are
defined, and there is one configuration file called DSNZPARM. There are
typically many databases defined within a subsystem. All applications
running in this subsystem share the system resources such as catalog,
databases, BPs etc. The installation of DB2 on the distributed platforms is
called an instance.
System Catalog: The system catalogs are very similar between the
platforms; however, where they reside and how they are accessed are quite
different. To extract information from the z/OS catalog, you typically run
queries directly against the appropriate tables.
In distributed environments, there are a series of views defined with the
schema of SYSCAT for retrieving catalog information and a series of
updateable views with a schema of SYSSTAT for updating optimizer-related
stats in the catalog.
Accessing DB2:
Accessing DB2 z/OS is done through a supplied application called DB2
Interactive (DB2I). This facility provides basic functionality for running
queries, issuing commands, generating utilities and preparing programs. DB2
on distributed platforms comes with a graphical user interface (GUI) toolset
called Control Center and Health Center. Control Center provides basic
functionality for doing rudimentary tasks within DB2. Health Center
allows you to set up monitoring parameters for autonomic computing

Z/OS
One common system catalog for all databases defined within a subsystem • DSNDB06 –
This catalog contains the metadata for all objects defined within
Catalog database
the subsystem.
LUW
Three system tablespaces are created by default for every database 1. SYSCATSPACE –
Contains system catalog tables 2. TEMPSPACE – Holds temp tables used by UDB 3. USERSPACE1 –
Contains user tables unless tablespace specified (like DSNDB04)

StorAge management:
The physical devices for z/OS are known as volumes. The physical devices for
distributed platforms are known as containers. A container in itself is not a
physical device but a representation of how the space is defined.
LBAC:
A security label is composed of one or more security label components. There
are
three types of security label components that you can use to build your
security
labels:
• Sets. A set is a collection of elements where the order in which those
elements appear is not important. All elements are deemed equal.
• Arrays. An array is an ordered set that can be used to represent a simple
hierarchy. In an array, the order in which the elements appear is
important. For example, the first element ranks higher than the second
element and the second higher than the third.
• Trees. A tree represents a more complex hierarchy that can have multiple
nodes and branches. For example, trees can be used to represent
organizational charts. You use a security policy to define the security label
components that make up a particular security label.

1. create a security label component that contains a tree/set/array

2. Create a security policy, Security policies determine exactly how a
table is to be protected by LBAC
3. Create a security labels, Security labels describe a set of security
criteria and are used to protect data against unauthorized access or
modification. Security labels are granted to users who are allowed to
access or modify protected data;

Page no. 54-55 of 5090_exp

Recommendations on when to use Label-Based Access

Control
(LBAC)
The following guidelines help determine when you should use LBAC to protect your
data.
Use row-level LBAC for:
• Government applications that manage classified information
• Other applications, where all of the following apply:
o Data classification is known
o Data classification can be represented by one or more LBAC security
label components
o Authorization rules can be mapped to the security label components
Use column-level LBAC for:
• Protecting sensitive columns from table owners and DBAs
• Tables that contain data which you want to protect from access by the table
owner or the DBA. To protect this data, follow these steps:
1. Assign a security label to all columns in the table.
2. Assign that security label to a role.
3. Assign that role to all users who need access to the table. Only users who
are members of that role are able to access data in that table.
Physical database design is the single most important factor that impacts database
performance. Physical database design covers all of the design features that relate to
the
physical structure of the database such as datatype selection, table normalization
and
denormalization, indexes, materialized views, data clustering, multidimensional data
clustering, table (range) partitioning, and database (hash) partitioning.

MDC is done by dimension value

Database design is performed in three stages:

1. Logical database design: includes gathering of business requirements, and entity
relationship modeling.
2. Conversion of the logical design into table definitions (often performed by an
application developer): includes pre-deployment design, table definitions,
normalization, PK and FK relationships, and basic indexing.
3. Post deployment physical database design (often performed by a database
administrator): includes improving performance, reducing I/O, and streamlining
administration tasks.

Physical database design includes the following attributes:

• Datatype selection
• Table normalization
• Table denormalization
• Indexing
• Clustering (create index vibhaw cluster)
• MDC
• Database partitioning
• Range partitioning
• UAV partitioning
• MQTs
• Memory allocation
• Database storage topology
• Database storage object allocation

A high-quality physical database design is one that meets the following goals:
• Minimizes I/O
• Balances design features that optimize query performance concurrently with
transaction performance and maintenance operations
• Improves the efficiency of database management, such as roll-in and roll-out of
data
• Improves the performance of administration tasks, such as index creation or
backup and recovery processing
• Minimizes backup and recovery elapsed time

Star schema and snowflake models

The star schema and snowflake models have become quite popular for data
warehousing BI
systems. The basis of star schema is the separation of the facts of a system from its
dimensions. Dimensions are defined as attributes of the data, such as the location, or
customer name, or part description, and the facts refer to the time-specific events
related
to the data.

• Perform an infrastructure analysis

• Use separate, high performing disks or file systems for the

database logs

• Make the location of archived logs accessible by both the

primary and standby databases

• Use a dedicated network for the HADR primary-standby

connection

• Use multiple network adaptors

• Consider using a virtual IP address for the database server or

using automatic client reroute

• Choose the appropriate hadr_syncmode

• Tune DB2_HADR_BUF_SIZE, hadr_timeout,

hadr_peer_window, and DB2_HADR_PEER_WAIT_LIMIT

• Tune DB2TCP_CLIENT_RCVTIMEOUT, DB2_HADR_SOSNDBUF, and

DB2_HADR_SORCVBUF

• Tune logfilsiz and softmax

• Set logindexbuild to ON

• Set indexrec to RESTART

• Set DB2_MAX_CLIENT_CONNRETRIES and

DB2_CONNRETRIES_INTERVAL for client reroute

• Perform an online reorganization if you want to maintain

availability of the affected tables and indexes

• Perform an offline reorganization if it is not necessary to

maintain the availability of the affected tables and indexes
 • Perform a nonrecoverable load only if the load operation does
not need to be replicated on the standby

• Ensure that the load copy is available to the standby when it

replays the load

Set the DB2_LOAD_COPY_NO_OVERRIDE to COPY YES if there will be frequent

load operations

The digital certificate contains specific pieces of information about the identity of the
certificate owner and about the certificate authority, these being:
• The owner's distinguished name. A distinguished name is the combination of the
owner's common name and its context (position) in the directory tree. In the simple
directory tree shown in Figure 1, for example, LaurenA is the owner's common
name (CN), the organization unit (OU) is Engnring and the Organization (O) is
XYZCorp; therefore, the distinguished name is:
.CN=LaurenA.OU=Engnring.O=XYZCorp
• The owner's public key.
• The date the digital certificate was issued.
• The date the digital certificate expires.
• The issuer's distinguished name. This is the distinguished name of the issuing CA.
• The issuer's digital signature
The iKeyman utility is a tool you can use to manage your digital certificates. With
iKeyman, you can:
Create a new key database
Create a test digital certificate,
Add CA roots to your database,
Copy certificates from one database to another,
Request and receive a digital certificate from a CA,
Set default keys,
Change passwords

Jan works for a medium-size company that has just purchased another smaller organization.
Jan has been asked to import the certificates from the smaller company's OpenSSL keystore
into the company standard CMS format. Jan decides to create a new CMS keystore and add
the certificates from the OpenSSL store to it. Jan does not like to use a GUI tool and
decides to use the IKEYCMD command line tool to perform the operation. In order to
import the OpenSSL certificates into a new CMS keystore Jan must:
• Create a new CMS keystore.
• Add the root certificate from OpenSSL.
• Export the certificates from the OpenSSL key store.
 • Import the OpenSSL certificates into the CMS keystore.

DB2 workload
Serves as the primary point of control, based on the source of submitters of
work, and routes work to service classes via connection attributes
DB2 service class
Serves as the primary point of resource control for all executing work activities
DB2 threshold
Provides limits to control behaviors of database activities based on predictive
and reactive elements for all activities occurring in a database or service class
DB2 work action set (work action > work class set > work class)
Provides ability to discriminate between different types of database activities
(read, write, call, DML, DDL and load) occurring in a database or service class
DB2 WLM monitor and control capabilities
db2pd utility, table functions, stored procedures and event monitors provide
real-time as well as historical monitoring capabilities
SET WORKLOAD TO SYSDEFAULTADMWORKLOAD;

---------------------------------------------------------------
-- create service classes
---------------------------------------------------------------

CREATE SERVICE CLASS "CLP_Serv_Admin_HI"

UNDER "CLP_Serv_Admin"
PREFETCH PRIORITY HIGH
AGENT PRIORITY 6
BUFFERPOOL PRIORITY HIGH
DISABLE;

-- create workloads and assign to service classes

---------------------------------------------------------------

CREATE WORKLOAD "CLP_Workload_User1"

APPLNAME('db2bp.exe')
CURRENT CLIENT_USERID('db2user*')
DISABLE
SERVICE CLASS "CLP_Serv_User"
COLLECT ACTIVITY METRICS
COLLECT ACTIVITY DATA ON ALL DATABASE PARTITIONS
COLLECT AGGREGATE ACTIVITY DATA BASE
POSITION AT 2;
---------------------------------------------------------------
-- create thresholds (both database and workload types)
---------------------------------------------------------------

CREATE THRESHOLD "MAX_Activities"

FOR WORKLOAD "CLP_Workload_User1" ACTIVITIES
ENFORCEMENT WORKLOAD OCCURRENCE
WHEN CONCURRENTWORKLOADACTIVITIES > 5
STOP EXECUTION;

---------------------------------------------------------------
-- create work class sets
---------------------------------------------------------------

CREATE WORK CLASS SET "DML_Usage"

(WORK CLASS "Read_Work" WORK TYPE read,
WORK CLASS "Write_Work" WORK TYPE write);

---------------------------------------------------------------
-- create work action sets
---------------------------------------------------------------

CREATE WORK ACTION SET "Admin_Actions" FOR SERVICE CLASS

"CLP_Serv_Admin"
USING WORK CLASS SET "DML_Usage"
(WORK ACTION "Map_Writes" ON WORK CLASS "Write_Work"
MAP ACTIVITY TO "CLP_Serv_Admin_HI",
WORK ACTION "Map_Reads" ON WORK CLASS "Read_Work"
MAP ACTIVITY TO "CLP_Serv_Admin_MED");

---------------------------------------------------------------
-- grant usage of workloads
---------------------------------------------------------------

GRANT USAGE ON WORKLOAD "CLP_Workload_Admin" TO PUBLIC;

The IEHLIST utility is used to list a partitioned data set directory or a disk volume
VTOC.
The IEHINITT utility is used to write standard labels on tapes. It can be used, as
needed, to label a single tape or it can be used to label large batches of tapes
The IEHPROGM utility is almost obsolete. It is used primarily to manage
catalogs, rename data sets, and delete data sets by a program instead of by JCL
actions. It was primarily used during system installation or the installation of a
major program product
The IEBDG utility is used to create records in which fields can be generated with
various types of data
//LOAD EXEC PGM=IDCAMS
//SYSPRINT DD *
//DATAIN DD DISP=OLD,DSN=OGDEN.SORTOUT
//SYSIN DD *
DEFINE CLUSTER (NAME (OGDEN.DATA.VSAM) -
VOLUMES(WORK02) CYLINDERS(1 1) -
RECORDSIZE (72 100) KEYS(9 8) INDEXED)
REPRO INFILE(DATAIN) OUTDATASET(OGDEN.DATA.VSAM) ELIMIT(200)

D NET,VTAMOPTS Displays VTAM startup options.

D NET,CSM[,OWNERID=ALL]
Displays communication storage usage.
D NET,APPLS Displays status of defined applications (ACBs).
D NET,MAJNODES Displays status of will display all major nodes that have
been activated by VTAM.
D NET,TOPO,LIST=SUMMARY
Displays APPN topology information.
D NET,CPCP Displays status of APPN CP-CP sessions.
D NET,SESSIONS Displays status of subarea SSCP-SSCP sessions,
LU-LU sessions (including CP-CP sessions),
SSCP-LU sessions and SSCP-PU sessions.
D NET,CDRMS Displays status of subarea cross domain resource
managers.
D NET,EXIT Displays status of VTAM exit routines.

SMP/E is the z/OS tool for managing the installation of software products on a
z/OS system and for tracking modifications to those products. SMP/E controls
these changes at the component level by:
_ Selecting the proper levels of code to be installed from a large number of
potential changes.
_ Calling system utility programs to install the changes.
_ Keeping records of the installed changes by providing a facility to enable you
to inquire on the status of your software and to reverse the change if
necessary.
All code and its modifications are located in the SMP/E database called the
consolidated software inventory (CSI), which is comprised of one or more VSAM
data sets.

Multiprocessor means several processors (and that these processors

are used by the operating system and applications). What does
multiprogramming mean?
Multiprogramming means several programs are run at the same time on a
uniprocessor. The operating system executes part of one program for some
time, then another program for some time and so on. This way, to the user, it
appears that all programs are running at the same time.
2. Usually, each read or write operation on a non-shared DASD device is
one I/O operation. How many I/O operations will be involved when the
DASD is in a shared mode?
When the DASD is shared, each read or write will essentially involve three
operations since the operating system will have to issue the RESERVE and
RELEASE commands in addition to the read or write command.
3. What is the role of PR/SM?
PR/SM contains the functions that are used to create and manage the LPARs
on the hardware.
4. What changes are needed for z/VM applications to work in an LPAR?
No changes are required.

11.4.9 CICS programming roadmap

Typical steps for developing a CICS application that uses the EXEC CICS
command level programming interface are as follows:
1. Design the application, identifying the CICS resources and services you will
use. See the chapter on Application Design of CICS Application Programming
Guide.
2. Write the program in the language of your choice, including EXEC CICS
commands to request CICS services. See CICS Application Programming
Reference for a list of CICS commands.
One of the needed components for online transactions is the screen
definition, that is, the layout of what is displayed on the screen (such as a Web
page); in CICS we call this a map.
3. Depending on the compiler, you might only need to compile the program and
install it in CICS, or you might need to define translator options for the
program and then translate and compile your program. See CICS Application
Programming Guide for more details.
4. Define your program and related transactions to CICS with PROGRAM
resource definitions and TRANSACTION resource definitions, as described in
CICS Resource Definition Guide.
5. Define any CICS resources that your program uses, such as files, queues, or
terminals.
6. Make the resources known to CICS using the CEDA INSTALL command
described in CICS Resource Definition Guide.
 Customize
Find an
the existing
AMI
AMI Launch the
Bundle
instance
the AMI
AMI
Build from
scratch

Use your
AMI

Create a Root Prepare for

Create File System Mount the
the
a File File
Inside the File Installation

------------------------
cloud defination :
Common, Location-independent,Online Utility on Demand where Common implies
multi-tenancy, not single or isolated tenancy; Utility implies pay-for-use pricing ; on
Demand implies ~infinite, ~immediate, ~invisible scalability

Alternatively, a “Zero-One-Infinity” definition

0 On-premise infrastructure, acquisition cost, adoption cost,support cost
1 Coherent and resilient environment – not a brittle “software stack”
? Scalability in response to changing need,Integratability/ Interoperability with legacy
assets and other services
Customizability/Programmability from data, through logic, up into the user
interface without compromising robust
multi-tenancy

------------------------------------------------------------------------
Multitenancy refers to a principle in software architecture where a single instance of the
software runs on a server, serving multiple client organizations (tenants).
------------------------------------------------------------------------
Cloud Software as a Service (SaaS)
Use provider’s applications over a network
Cloud Platform as a Service (PaaS)
Deploy customer-created applications to a cloud
Cloud Infrastructure as a Service (IaaS)
Rent processing, storage, network capacity, and other fundamental computing resources
-------------------------------------------------------------------------

Challenges to application modernization

There are challenges to application modernization, which we can broadly
categorize into three areas:
_ Malleability of existing applications
_ Extensibility and availability of skills
_ Multitude of platforms and middleware

The SOA lifecycle is the framework of the IBM SOA strategy. As Figure 2-1
shows, the SOA lifecycle consists of four stages:
_ Model: Use modeling tools to define the business process at a business level
and model the actual services that will be part of an assembled, composite
application.
_ Assemble: Assemble the individual services and write the code that is
needed to implement the business rules for the application. Preexisting
services can be reused, and new services can be developed, or both.
_ Deploy: Deploy the services to runtime environments, such as transaction
management engines, such as WebSphere Application Server, CICS, IMS,
and so forth. Use integration components primarily and enterprise service bus
(ESB) to link together the various services that are needed for the composite
application.
_ Manage: Implement the management infrastructure for monitoring and
managing the services and the service infrastructure, which includes not only
IT management tools, but also business management and monitoring tools to
measure actual business activities.

WAS is based on open standards is very important because it helps understand how
“WAS is WAS” yet also have platform exploitation. That’s possible because the open
standards represent application interfaces. That’s where the commonality takes place.
But the implementation of the function below the interfaces is handled in some places on
a platform-specific basis. Most of the code is common … but a small bit is platform
specific, and that all takes place under the open standard specification line.

1. Start Rational Application Developer V7.x

2. Create a new Project
3. Create a DB2 connection
– The easiest is to have a live connection with the z/OS DB2 tables that you
will be using in your code
4. Create an entity EJB from the DB2 table
– In our case the ITSO0C.EOTCUS contains the customer info
5. Create a session Bean façade
 – You need to do this because we will later generate the WS out of this
session Bean
6. Add the necessary Java code for the session Bean
7. Generate a WS out of the session Bean
– Using the “bottom-up” approach
8. Inspect and customize the WSDL
– Mandatory is to specify the endpoints correctly.
9. Customize the EJB deployment descriptor
– Datasources, security etc.
10. Deploy the .ear file to the local WAS server for testing
11. Export and deploy the .ear file to the WAS server on z/OS
– Using the WAS Admin console