Platform Support Plan

System Name: DB2 Platform Support Plan

Document ID:
Document Revision: 1.0
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Approvals
TECHNICAL UNIT APPROVAL:
By affixing their signature, the individual below acknowledges that they have reviewed and approve the technical
contents of the Infrastructure Support Plan and attest that they are accurate.
Merck Wave Lead Name
{See Appended Electronic Signature Page}
James E. Fletcher, DB2, Database Services
BUSINESS UNIT APPROVAL:

By affixing their signature, the individual below acknowledges that they have reviewed and approve the technical
contents of the Infrastructure Support Plan and attest that they are accurate.
Merck Tower Lead
{See Appended Electronic Signature Page}
Chuck Denecke, Database Services

Revision History
ISSUE # DATE PERSON CHANGE
1.0 6-Feb-14 Chiali Tsai First issuance of document.
Document created to establish support plan for DB2 Database Services.

1.0 10-Apr-14 Chiali Tsai Updated Pre-Authorization Change

management

Page 2 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

TABLE OF CONTENTS
1 Introduction ................................................................................................................................ 6
1.1 Purpose ............................................................................................................................................6
1.2 Scope ...............................................................................................................................................6
1.3 Amendments to the Support Plan .....................................................................................................6
2 Support Strategy and Environment ............................................................................................. 6
2.1 Support Objective .............................................................................................................................6
2.2 Support Strategy ..............................................................................................................................7
2.3 Support Environment .......................................................................................................................7
2.4 Database Inventory ..........................................................................................................................8
3 Contact Information.................................................................................................................... 8
4 Abbreviations and Acronyms....................................................................................................... 8
5 Roles and Responsibilities ......................................................................................................... 10
6 Tools, Techniques and Methods ................................................................................................ 10
6.1 Support Tools ................................................................................................................................. 10
6.2 Vendor Support Details ................................................................................................................... 14
6.3 Communication Method ................................................................................................................. 15
7 IT Service Management Procedures........................................................................................... 15
7.1 Service Request Management ......................................................................................................... 15
7.2 Incident Management .................................................................................................................... 15
7.3 Problem Management .................................................................................................................... 16
7.4 Configuration Management ............................................................................................................ 16
7.5 Change Management ...................................................................................................................... 16
7.6 Service Knowledge Management .................................................................................................... 46
8 Service Manager Roles & Responsibilities .................................................................................. 46
8.1 Remedy Ticket Initiation and Assignment ........................................................................................ 46
8.2 Support Group Names .................................................................................................................... 47
8.3 Updating Resource Scheduling Calendar .......................................................................................... 47
9 DB2 Subsystem Details .............................................................................................................. 49
9.1 Mainframe Infrastructure ............................................................................................................... 49

Page 3 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

9.2 Host Names .................................................................................................................................... 49

9.3 JOBCARD Details............................................................................................................................. 50
9.4 DB2 PROCS ..................................................................................................................................... 50
9.5 Overflow Pack Approach................................................................................................................. 50
9.6 Database Roadmap......................................................................................................................... 52
9.7 DB2 Subsystem Logon Details ......................................................................................................... 53
9.8 Storage Groups ............................................................................................................................... 53
9.9 Datasets ......................................................................................................................................... 54
9.10 WLM ........................................................................................................................................... 55
9.11 DDF............................................................................................................................................. 55
9.12 Applications List .......................................................................................................................... 56
9.13 Service Request Management and Access Management Tool Understanding ................................ 57
9.14 Application Owners Contact Details ............................................................................................. 57
9.15 Service Window .......................................................................................................................... 57
9.16 On-call List .................................................................................................................................. 57
10 Security and Account Management - ...................................................................................... 58
10.1 DB2 Security Standards ............................................................................................................... 58
10.2 SYSA-Schering Plough LPAR ......................................................................................................... 59
10.3 Strong DB2 Passwords ................................................................................................................. 59
10.4 DB2 Account Administration........................................................................................................ 59
10.5 DB2 Account Validation Scripts .................................................................................................... 59
11 DB2 Operational Activities ..................................................................................................... 60
11.1 Periodic manual Activities ........................................................................................................... 60
11.2 Daily Activities ............................................................................................................................ 60
11.3 Database Objects Creation and Migration .................................................................................... 60
11.4 Decommission/Retirement .......................................................................................................... 61
11.5 Backup and Recovery .................................................................................................................. 64
12 Scheduled Activities ............................................................................................................... 65
12.1 Weekly/Monthly/Quarterly Procedures....................................................................................... 65
13 Impact ................................................................................................................................... 66
14 Disaster Recovery / BCP ......................................................................................................... 66
Page 4 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

14.1 Rahway /WestPoint .................................................................................................................... 66

14.2 SYSA (Schering Plough) ................................................................................................................ 73
15 Auditing ................................................................................................................................ 74
15.1 DB2 Audit Configuration .............................................................................................................. 74
15.2 DB2 Critical Table Auditing .......................................................................................................... 74
15.3 DB2 SOx account remediation ..................................................................................................... 75
15.4 Sox audit process, (update Sox tables pre Sox audit process) ........................................................ 78
16 SLA Management .................................................................................................................. 78
17 Database In-flight Projects ..................................................................................................... 78
18 Escalation Matrix ................................................................................................................... 79
19 General DOs and DON’Ts ....................................................................................................... 79
20 Training ................................................................................................................................. 80
21 References ............................................................................................................................. 80
22 Resources .............................................................................................................................. 80

Page 5 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

1 Introduction
1.1 Purpose
The objective of this document is to explain the DB2 Environment at Merck &Co., Inc. This document describes the
DB2 administration tasks performed within Merck. The audience of this document is primarily the HCL DB2 team,
who will be performing DB2 Administration from HCL’s Chennai facility and at on-site Merck facility.

This document defines the Merck & Co., Inc. procedures and policies and provides guidelines for its
implementation. All information was captured during the knowledge acquisition phase during face-to-face
discussions held at WestPoint.

Merck & Co’s DB2 applications are running on an IBM Mainframe. They have three Production LPARs and two
System Test LPARs.

1.2 Scope
The services include Database Administration and Application support for DB2. Additionally DR, SOX auditing
and ISV products are included. The environments are supported on a 24X7 basis. The scope of service includes, but
is not limited to:
• Providing all aspects of physical database administration (for example: object creation, image copies,
reorganization, recoveries) in the development, test and production environments, including the migration
of database objects between development, test and production.
• Providing support on a 24x7 basis for incidents or problems related to databases on WP, RY, and SYSA
LPARs.
• Performing reorganizations of databases to optimize performance when required at the direction of, and in
accordance with the specifications of Merck & Co.
• Providing continuous operation and availability of all in-scope databases.
• Providing and supporting database recovery (both on-site and off-site) for any supported application
databases according to the individual Application requirements for currency of the information after the
recovery.
• Providing Physical Database Management Support, including providing backups and restores of data in a
timely manner consistent with Application recovery requirements.

1.3 Amendments to the Support Plan

The content material contained within this document shall be in effective until the document is retired. Minimally,
the content of the document will be examined by platform subject matter experts and management on an annually
basis to ensure the content is reflective of current support processes and strategies.
Amendments to this support plan will be accomplished through the revision of this document with signature
approval by all original signatories, their delegates, or functional equivalents. A history of approved issues of this
document will be reflected in the Document Issue History section.

2 Support Strategy and Environment

2.1 Support Objective
The Platform Service provides server environments to host Merck applications. Specific support objectives are
identified following Operational Level Agreements.

Page 6 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

 GISLM-OLA-GEN-001413 – Database Services Operational Level Agreement

2.2 Support Strategy

DATABASE SERVICES Platform support is divided into three levels. Each level is supported by the HCL
Managed Service.

The different levels of support allow the DB2 Database Platform to be supported 24x7.

Issues to the platform are reported as follow:

 Data Center Technicians raise Remedy incidents cases about issues related to the
DATABASE_SERVICES RESOURCES reported by various sources: DB2 subsystems, application
groups, etc.
 Application groups submit helpdesk cases about issues they are experiencing with the platform.
 Monitoring tools generate alerts based on some pre-defined threshold. These events are managed by
DATABASE_SERVICES RESOURCES using the incident management process.

All requests for DB2 Database Support must first be initiated by a Remedy Work Order, Service Request, or an
Incident. The Requestor should include a detailed description of the request or problem, the database name if
applicable, and the LPAR’s name. The Remedy ticket should initially be submitted to the
“DATABASE_SERVICES RESOURCES” Remedy Group for initial service management.
HCL actively monitors these queues on a 24x7 basis to respond, manage, and complete the request according to
the SLA for the requests’ priority.

2.2.1 Queues Names *

The Remedy Provider Groups associated with the HCL team, Shared Services:
 Shared Services Queue Name: “Database_Services Resources”

Note: E-mails/IMs/Phone Calls will be responded to for Emergency Requests, but a Remedy ticket must be
submitted shortly thereafter.

2.3 Support Environment

The Mainframe that hosts DB2 Databases is located in the Data Center at Southbury, CT. Asset information is
tracked in Remedy (CMDB).
 All requests for DB2 Database Support must first be initiated by a Remedy Work Order, Service
Request, or an Incident. The Requestor should include a detailed description of the request or
problem, the database name, and the server’s name. The Remedy ticket should be submitted to the
“DATABASE_SERVICES RESOURCES” Remedy Group for HCL to manage.

 HCL actively monitors this queue on a 24x7 basis to respond, manage, and complete the request
according to the SLA for the requests’ priority

Page 7 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

2.4 Database Inventory

There are approximately 345 RY/WP/SYSA DB2 databases in the Test and Production subsystems.
Inventory of DB2 databases can be found at the below link:
https://remedy-web.merck.com/
For searching a database in Remedy, follow below sequence:
Login to Remedy Applications  Asset Management  Asset Management Console
 Manage CI CI Type  logical entity  database  Enter CI name

All database related detail like criticality, associated application, etc. can be found in Remedy. DB2 Subsystem
details:

Original LPAR SUBSYSTEM

Machine
Location PROD TEST DEVL Version

Merck - SYSA DSN DSNT - V7.1

Schering
Plough SYSF DSN DSNT - V7.1
Merck - RY DB2P DB2T DB2D V8.1*
Rahway
Merck – WP DB2P DB2T DB2D V8.1*
WestPoint
WT - - DB2D V8.1*
* Compatibility mode

3 Contact Information
All support requests must have a support case. A Consumer can call the Help Desk or the Charlotte Technology
Center (CTC) Command Center and a case will be created. If they cannot provide immediate support, they will
contact the Service Provider for assistance. Requests that are not initiated by the CTC Command Center will be
responded to by the Service Provider according to the support model detailed below.

If issues arise that cannot be resolved between the Client and the Support Lead, the following escalation procedure
should be followed.
 Contact the Help Desk and ask for your call to be routed to the Command Center.
 Ask the Command Center for details on escalation chains, which can be found in My Support Center and
AlarmPoint.

Automated alerts are generated by the different monitoring tools and reported through contact information.
Alarmpoint is also used by application groups and data center technicians to call a DBA about a problem or incident.

4 Abbreviations and Acronyms

Acronyms Description
AMSU Asset Management Search Utility

Page 8 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Acronyms Description
BCP Business Continuity Process
CM Change Management
DBA Database Administrator
DDF Distributed Data facility
DEVL Development
DR Disaster Recovery
IM Incident Management
ISV Independent Software Vendor
KPI Key performance Indicator
LPAR Logical partition
MIPS Million instructions per second
PROC Procedure
PROD Production
QW Quick Reference
RFC Request for change
RSVP CA product to manage z/OS DASD and data, report on DASD at the volume and
dataset level
RY Rahway
SMS System-Managed Storage
SOP Standard Operating Procedure
SOX Sarbanes Oxley
SYSA Schering Plough mainframe
SYSB Rahway mainframe
SYSC West Point mainframe
SYSF Schering Plough mainframe crash and burn
TSO Time sharing Option
WLM Work Load Manager
WP WestPoint
WT Whitehouse Test crash and burn

Page 9 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

5 Roles and Responsibilities

Role Role Responsibility
Build and Manage the DB2 Database objects, perform routine tasks and operational
Database Administrator
activities

6 Tools, Techniques and Methods

6.1 Support Tools
6.1.1 Alarmpoint for escalation and notification
AlarmPoint is an alerting tool that interacts with monitoring software to provide the following functions
to Merck:
 Alerting relevant personnel to critical IT events, and
 Escalating and acknowledging the events as required throughout the business enterprise --
application management, network / system monitoring, business continuity and information
security.

6.1.2 DB2 administration and monitoring tools

The following products are used for DB2 administration and monitoring activities:

6.1.2.1 QMF
WP/RY, access QMF from DB2 Products Menu,

Select option 2 to get in QMF

Page 10 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

6.1.2.2 CA-DB Tools: RC/Query, RC/Migrator, RC/Update, Insight, Space calculation

WP/RY, access CA database tools via d of ISPF main menu, as showed on figure 1, then Select option 3 to get in
CA DB tools

Follow the screen to get into different functions

At SYSA/SYSF CA DB2 tools is under the title of Platinum

Select option 2 Platinum, CA Unicenter DB2 tools will come up.

Page 11 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

6.1.2.3 Thread/STOPPER
Tool is installed at WP/RY; get into DB2 product menu via option d from ISPF main menu,

Select option 4 to get in THREAD/STOPPER, Pick the subsystem to monitor.

6.1.2.4 Erwin
Erwin is a licensed product and needs to be installed on your individual Laptop. The software is stored on the shared
drive \\wpccr04. To install the product:
Request access to the shared drive.
Download the software onto ones’ Laptop, and then install it.
\\wpccr04\Data Architecture\Tools\ ERWin 4.1.4.4415 (SP4)

The installation document is stored at

1. gdmsprd :/ /IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database
Shared Services/DB2/ERWin
2. \\wpccr04\Data Architecture\Tools Registering ERWin 4.doc

To be able to use Erwin for database change management, 2 more components are required;
CRDB, installation document is stored at shared drive \\wpccr04\Data Architecture\Tools\ CRDB Installation
Instructions.doc

Data Direct Shadow ODBC is documented on how to Install Shadow Direct ODBC Client 7_3 on Win7.doc in

Page 12 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

gdmsprd : //IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database

Shared Services/DB2/Shadowdirect

Any object creation/modification will go through Erwin, application group will request DA to make
change to Data Model. Once DBA gets the request from DA, copy the DDL into DDL library at
Mainframe, modify the source code per DB2 syntax standard.

DDL library
MSD.DBM.C9999.DB2DDL.CNTL, C9999 IS THE COMPLEX NUMBER

6.1.2.5 Optim
 The product used in FACTS to archive DB2 data.
 The document is saved as “FACTS – Manual Activity” in WebTop path :
gdmsprd :cabinets/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations

To access OPTIM, call Clist TSO PST then maneuver thru the menu. Input the password to gain the full function of
the product.
The DBA is responsible for installing and maintaining the product. The product database is PST.

Table SYSPST.ARCHIDX needs to be monitored for usage.

Customer Number/Site Id: 6248708
Product Details:
Product Family - Information Management
Product - Optim z/OS
Installed version - 5.5.3 Build 283
Platform - z/OS
Contact Number: 1-800-426-7378
Email id: [email protected]

6.1.3 My Support Center (Remedy)

BMC Software’s Remedy application is an enterprise wide, web based ticketing system for Business Service
Management. The following Remedy modules support Merck’s ITIL-based Service Management Processes:
 Change Management
 Incident Management
 Problem Management
 Configuration Management
 Service Level Management
 Knowledge Management

Page 13 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

 Service Request Management

6.2 Vendor Support Details

All of the ISV products are managed by IBM except for two. The contact details:

6.2.1 IBM-OPTIM (Princeton Softech)

The product used in FACTS to archive DB2 data.
The document is saved as “FACTS – Manual Activity” in WebTop path :
gdmsprd : IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations

To access OPTIM, call Clist TSO PST then maneuver thru the menu. Input the password to gain the full function of
the product.

The DBA is responsible for installing and maintaining the product. The product database is PST. Table
SYSPST.ARCHIDX needs to be monitored for usage.

Customer Number/Site Id: 6248708

Product Details:
Product Family - Information Management
Product - Optim z/OS
Installed version - 5.5.3 Build 283
Platform - z/OS
Contact Number: 1-800-426-7378
Email id: [email protected]

6.2.2 Shadow Direct(no contract)

The DBA needs to register at WWW.ROCKETSOFTWARE.COM/SUPPORT in order to acquire access and get the
required support from Rocket Software, the owner of the product.

6.2.3 IBM Contact Details

The Mainframe supplier for Merck is IBM. The below contact details are used to reach them in case of escalation:

Debra Kacor
Email : [email protected]
Service Delivery Manager
Merck

Batch Operations:
[email protected]
[email protected]

Page 14 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

[email protected]

DB2 system programmer email address: [email protected]

MVS Support

Tom Marsh - MVS Support and Security ([email protected])

Bill Ivery - MVS Support ([email protected])

6.3 Communication Method

Scheduled and unscheduled service disruptions will be communicated to clients by email notifications from My
Support Center. Scheduled downtime will be communicated at least one week in advance. Unscheduled downtime
will be communicated though the Command Center as soon as is practicable.

7 IT Service Management Procedures

7.1 Service Request Management
Datacenter Technician submits a service request/ Case to “Database_ Services Resources " inbox. Tier2 SA
monitors the support Group “Database Services Resources “inbox 24x7. Tier 2 SA investigates the case and if
within scope resolve incident using KM articles. If not then escalate incident to Tier3 on-call DBA.

The procedure to support Service Request Management is as follows

 SDLC-SOP-05-08: Global Services (GS) Service Request Fulfillment

7.2 Incident Management

Incident Management is the process responsible for managing the lifecycle of all incidents. Status of all incidents
can be obtained by calling the Help Desk or the Command Center.

Whenever an incident occurs, an alert is generated through the monitoring tools. Once alert is received, it is
registered in remedy tool by user or support team.

Once the incident is registered, a ticket is created and assigned to the concerned support team (here Database Team).
The person who is assigned the ticket to work upon is called assignee. Assignee will be owner of the ticket until it is
resolved or it is transferred to other person.

The remedy group name for Database Support team is “Database Services Resources”. The ticket is further
assigned to specific Database Team member who works on the incident ticket. The time between ticket assigned to
group and the assignation to assignee is measured as response time. Database Team must be careful about the ticket
response time to meet the agreed SLA.

The procedure to support Incident Management is as follows

 SDLC-SOP-05-01: IT Incident Management

Page 15 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

7.3 Problem Management

Database Administrators are trained on how to report and resolve problems. Problems are tracked using My Support
Center.

There are two scenarios where we need to review the incident in more depth. (1) When a major outage occurred and
(2) when there is repetitive incident. In both these scenarios, incident should be investigated in detail and a problem
ticket is created.

To resolve problem ticket, root cause of the incident needs to be identified. Generally 3 times “Why” is asked for the
reason of incident and the root cause is identified. However, in some case, you may need to dig it further.

Once the root cause is identified, it mostly comes with some recommendations / change in environment which is
then taken care of by Change Management system separately. The Problem ticket can be closed once the root cause
is identified

The procedure to support Problem Management is as follows:

 SDLC-SOP-05-02: IT Problem Management

7.4 Configuration Management

Configuration Management is the process that maintains information about Configuration Items required delivering
an IT Service, including their Relationships. Its primary objective is to provide accurate data to all IT Service
Management Processes when and where it is needed

The procedure to support Configuration Management is as follows:

 ITSM-SOP-GEN-000068 - GTS Configuration Management Process

7.5 Change Management

The objective of Change Management is to ensure that standardized methods and procedures are used for efficient
and prompt handling of all changes to control IT infrastructure, in order to minimize the number and impact of any
related incidents upon service. Changes in the IT infrastructure may arise reactively in response to problems or
externally imposed requirements, e.g., legislative changes, or proactively from seeking improved efficiency and
effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement
initiatives. Change Management can ensure standardized methods, processes and procedures which are used for all
changes, facilitate efficient and prompt handling of all changes, and maintain the proper balance between the need
for change and the potential detrimental impact of changes.

Source of a RFC (Request for Change): There are different sources for RFCs, such as the Engineering team
requesting to build a Server / Database Instance, Application Team requesting a release / deployment consisting a
new database, services or Objects in existing database, patching and upgrades as per schedules. In addition, problem
root cause analysis sometimes comes with Change recommendation.

7.5.1 Planned and Unplanned Changes

The purpose of this procedure is to establish a disciplined process for introducing Planned and Unplanned Changes
into the Merck IT environment with minimal disruption to on-going operations.

These changes have been classified into four Classes:

Page 16 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

1. Normal Change
2. Emergency Change
3. Latent Change
4. Pre-Authorized Change
 Standard
 Pre-Approved
 Administrative

7.5.2 Normal Changes

This is a planned change that may be initiated as soon as the need for a change is known to ensure proper planning
for change implementation. Pre-Approval and Post Approval is required.

7.5.3 Emergency Changes

This is an unplanned change that must be implemented immediately due to system or service failure. There must be
a documented Incident ticket related to the Change. Pre-Approval and Post Approval is required.

7.5.4 Latent Changes

This is an unplanned/unapproved change that is formally recorded after implementation. Latent Changes are not
considered Emergency Changes, which follow the defined Emergency Change process. Post Approval is required.

For additional detail on Normal, Emergency an Latent changes, refer to “IT Change Management Process - Planned
and Unplanned Changes”

7.5.5 Pre-Authorized Changes

The Change Management process ensures that standardized, consistent methods are used for efficient and prompt
handling of all changes to the Merck IT environment, in order to minimize the impact of change-related incidents
upon service quality, and consequently improve the day-to-day operations of the organization. IT Change
Management processes must not impact the regulatory business processes and products. This procedure defines the
three classes of Pre-Authorized Change sanctioned by the ETAS Change Management Authority and are contained
in a Common Catalog.
 Standard Change - A Pre-Authorized Change that is low risk, relatively common and may follow a
Procedure or Work Instruction. Pre-Approval and Post Approval are not required.

 Pre-Approved Change - A Pre-Authorized planned change that does not require Pre-Approval but
requires Post Approval.

 Administrative Change - A Pre-Authorized Change that can be implemented without the creation of an
RFC and without any signature events.

These types of changes must be logged manually or electronically. The database team records these
changes using the Change Log section located in the Asset Management Search Utility (AMSU).

Page 17 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

For additional detail on Pre-Authorized changes, refer to “IT Change Management Process - Pre-Authorized
Changes”.

7.5.5.1 Pre-Authorized CRQ Implementation Instructions

C01 Rebind Plan/package

C02 Reset Flag - check pending, copy pending by check data, image copy
C03 start objects in stop status
C04 Terminate Stopped Utility
C05 Cancel Hang thread

C01 Rebind plan/package

//XXXXXXRB JOB (8045,5221,4),'WP97-A237',CLASS=I,MSGCLASS=X,

// MSGLEVEL=(1,1),REGION=4096K,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//BIND1 EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB DD DSN=SOFT.DB2.T.DSNLOAD,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB2T)
REBIND PLAN (C5710C16)
END
/*
//SYSIN DD *
//*
*************************** Bottom of Data ************************

**************************** Top of Data *************************

//XXXXXXBI JOB (8045,5221,4),'WP97-A237',CLASS=I,MSGCLASS=X,
// MSGLEVEL=(1,1),REGION=4096K,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//BIND1 EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB DD DSN=SOFT.DB2.T.DSNLOAD,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB2T)
REBIND PACKAGE (T5710CL.C5710S16)
END
/*

Page 18 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//SYSIN DD *
//*
************************** Bottom of Data ***********************

C02 Reset Flag - check pending, copy pending by check data, image copy
When Check pending, or Copy pending flags turned on, some access of the table will be blocked.
To reset the flag, executes the Check data, or Image copy job.

DSNT360I - ***********************************
DSNT362I - DATABASE = T5227D STATUS = STOP
DBD LENGTH = 646100
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG
PIECE
-------- ---- ----- ----------------- -------- -------- --------
-----
SESA2 TS RW,COPY
SOTQD TS RW,COPY

//XXXXXXCK JOB (8676,5710,1),'WP97-06',MSGCLASS=X,NOTIFY=&SYSUID,

// MSGLEVEL=1,CLASS=E
/*ROUTE PRINT WP62
//* CHECK UTILITY (TEST)
//UTIL EXEC DSNUPROC,V='T',UID='CK5710',UTPROC=''
//DSNUPROC.SYSUT1 DD DSN=&&SYSUT1,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,250)),
// UNIT=SYSDA
//DSNUPROC.SORTOUT DD DSN=&&SORTOUT,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,250)),
// UNIT=SYSDA
//DSNUPROC.SYSERR DD DSN=&&SYSERR,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(75,25)),
// UNIT=SYSDA
//DSNUPROC.SYSIN DD *
CHECK DATA TABLESPACE T5710.T5710089 SCOPE ALL

Image copy to reset COPY pending flag.

//XXXXXXCA JOB (5710,P240,5),'WP97B106',CLASS=E,MSGCLASS=X,

// NOTIFY=&SYSUID

Page 19 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//***
//STEP01 EXEC DSNUPROC,V='T',UID='HCLDB1CA',UTPROC=''
//***
//DSNUPROC.SYSIN DD *
LISTDEF COPYLIST
INCLUDE TABLESPACE T5710.T5710036
INCLUDE TABLESPACE T5710.T5710045
INCLUDE TABLESPACE T5710.T5710047
TEMPLATE COPYDST
DSN 'MSD.DBM.T5710.&TS..ICR(+1)'
UNIT CTAPE DISP (NEW,CATLG,DELETE) GDGLIMIT 3 RETPD 35
VOLCNT 25 STACK YES MODELDCB MRK.MODDSCB TRTCH COMP
COPY LIST COPYLIST
COPYDDN(COPYDST) FULL YES
SHRLEVEL REFERENCE
/*
//***
//

C03 start objects in stop status

A stopped object is not accessible, it should be started to be available for use. By issuing command
from SPUFI or batch could change the status of the database.
Need to find out what caused the STOP afterward to prevent the interruption of production process.

DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* RESTRICTED
DSNT360I - ***********************************
DSNT362I - DATABASE = T5227R STATUS = STOP
DBD LENGTH = 16144
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG PIECE
-------- ---- ----- ----------------- -------- -------- -------- -----
******** NO SPACES FOUND
******* DISPLAY OF DATABASE T5227R ENDED **********************
DSN9022I - DSNTDDIS 'DISPLAY DATABASE' NORMAL COMPLETION
***

Cmd 1 ===> -START DB(T5227R)

Page 20 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* GLOBAL
DSNT360I - ***********************************
DSNT362I - DATABASE = T5227R STATUS = RW
DBD LENGTH = 16144
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG
PIECE
-------- ---- ----- ----------------- -------- -------- -------- ---
--
SBATMR TS RW
SBATMT TS RW
SITEMR TS RW
SITEMT TS RW
SLOCNR TS RW
SLOCNT TS RW
SORDRR TS RW
SORDRT TS RW
SRQMTR TS RW
SRQMTT TS RW
XBATMR01 IX RW
XBATMT01 IX RW
XITEMR01 IX RW
XITEMT01 IX RW
XLOCNR01 IX RW
XLOCNT01 IX RW
XORDRR01 IX RW
XORDRT01 IX RW
XRQMTR01 IX RW
XRQMTT01 IX RW
******* DISPLAY OF DATABASE T5227R ENDED **********************
DSN9022I - DSNTDDIS 'DISPLAY DATABASE' NORMAL COMPLETION
***

Start a STOPPED Tablespace

DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* GLOBAL
DSNT360I - ***********************************
DSNT362I - DATABASE = T5227R STATUS = RW
DBD LENGTH = 16144
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG PIECE
-------- ---- ----- ----------------- -------- -------- -------- -----
SBATMR TS STOP

Page 21 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

******* DISPLAY OF DATABASE T5227R ENDED **********************

DSN9022I - DSNTDDIS 'DISPLAY DATABASE' NORMAL COMPLETION
***

-START DB(T5227R)SP(SBATMR) ACCESS(FORCE)

DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* GLOBAL
DSNT360I - ***********************************
DSNT362I - DATABASE = T5227R STATUS = RW
DBD LENGTH = 16144
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG PIECE
-------- ---- ----- ----------------- -------- -------- -------- -----
SBATMR TS RW
******* DISPLAY OF DATABASE T5227R ENDED **********************
DSN9022I - DSNTDDIS 'DISPLAY DATABASE' NORMAL COMPLETION
***

C04 Terminate STOPPED utility

When an utility job abend, the tablespace is not accessible while TS is at utility access mode.
Once figure out the root cause, either terminate the utility ID or restart the utility job to reset the flag.

DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* RESTRICTED
DSNT360I - ***********************************
DSNT362I - DATABASE = TESTDBA STATUS = RW
DBD LENGTH = 12104
DSNT397I -
NAME TYPE PART STATUS PHYERRLO PHYERRHI CATALOG
PIECE
-------- ---- ----- ----------------- -------- -------- -------- ---
--
TESTTS2 TS UT
******* DISPLAY OF DATABASE TESTDBA ENDED
**********************

-TERM UTIL(util_id)

Page 22 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

C05 Cancel hung thread

Cancel a hanging thread to release the resource, each thread has a unique token for the DB2
subsystem. To get the token, issuing command –DISplay THREAD

DSNV401I @ DISPLAY THREAD REPORT FOLLOWS -

DSNV402I @ ACTIVE THREADS -
NAME ST A REQ ID AUTHID PLAN ASID TOKEN
SERVER RA * 26986 db2jcc_appli CUSFIND DISTSERV 006E 22538

After clarifying the thread to be canceled, use the command CANCEL to terminate the thread.

- CANCEL thread( 22538 )

To validate if the thread got canceled, by command below

- DIS thread(*)

7.5.5.2 Pre-Authorized CRQ Change tracking Method

Each Administrative change will be documented in the AMSU Change log.

http://uctvp615:7777/pls/apex/f?p=129:101:15111114570980

7.5.5.3 General Category Changes Implementation Instructions

1. Create or add new entry to database connectivity
2. Delete entry to database connectivity
3. Modify entry to database connectivity
4. Create new objects covered by application changes control
5. Create new objects covered without application changes control
6. Install of new database software
7. Maintain scheduler and execution of database jobs
8. Backup
9. Unload data from production
10. Creation of a new subsystem on a shared z/OS server
11. Create, add or Migrate an application to a shared/non-shared database
12. Creation of a new subsystem as a clone of existing database to non-production environment
13. Creation of a new schema, database to existing subsystem
14. Rebuild index
15. Additions of database space, (alter stogroup)Reorg

Page 23 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

16. Reorg
17. Modify backup job, update control card to include/exclude tablespace/database
18. Modify reorg job, update control card to include/exclude tablespace/database
19. Update database statistics
20. Modify Database Initialization Parameter
21. Enable data file auto extend/auto grow
22. Disable data file auto extend/auto grow
23. Adding new features to existing environment
24. Create a new database as a clone of an existing database to non-production environment
25. Create LINK RDBMS Systems – Gateways, DB links, Link servers
26. Granting security to users
27. Revoking security from users
28. Administration of Database Management tools

1. Create or add new entry to database connectivity

o Login to WPTSO/RYTSO using logon proc PRODDB2

o Edit SOFT.ORACLE.P.VX.PARMLIB(TNSNAMES)

GDXA=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=XM)
(SID=GDXA)
)
)
GDXA_TCP=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL = TCP)

Page 24 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

(HOST = wtibm)
(PORT = 1510)
)
(CONNECT_DATA=(SID=GDXA))
)

Back Out process

Recover the source code from the copy, which was made prior to the changes.
2. Modify entry to database connectivity

o Login to WPTSO/RYTSO using logon proc PRODDB2

o Make a copy of the source code, before modifying it.
o Edit SOFT.ORACLE.P.VX.PARMLIB(TNSNAMES)

GDXA=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=XM)
(SID=GDXA)
)
)
GDXA_TCP=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL = TCP)
(HOST = wtibm)
(PORT = 1510)
)
(CONNECT_DATA=(SID=GDXA))
)

Back Out process

Recover the source code from the copy, which was made prior to the changes.

3. delete entry to database connectivity

Page 25 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Login to WPTSO/RYTSO using logon proc PRODDB2

Edit SOFT.ORACLE.P.VX.PARMLIB(TNSNAMES)
Save a copy of the source code.
Delete the entry from the member.

GDXA=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=XM)
(SID=GDXA)
)
)
GDXA_TCP=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL = TCP)
(HOST = wtibm)
(PORT = 1510)
)
(CONNECT_DATA=(SID=GDXA))
)

Back Out process

Recover the source code from the copy, which was made prior to delete it.

4. Create new objects covered by application changes.

Following Erwin, CRDB change management process, communicate with application group, to
receive the approval of installing the changes. Once application agrees the changes, following JCL
below to create new objects.
***************************** Top of Data *************************
//HCLDB110 JOB (5710,P240,10),'WP97-B106',MSGLEVEL=(0,0),
// NOTIFY=&SYSUID,MSGCLASS=X,CLASS=I
/*ROUTE PRINT WP62
//*****************************************************************
//* THIS JCL SELECTS RECORD IN BATCH
//*****************************************************************
//*
//JOBLIB DD DSN=SOFT.DB2.P.DSNLOAD,DISP=SHR
//*

Page 26 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//CRETABLE EXEC PGM=IKJEFT01,DYNAMNBR=20

//*** STOP TABLESPACE
//*
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB2P)
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP2) -
LIB('SOFT.DB2.P.RUNLIB.LOAD')
/*
//SYSIN DD DISP=SHR,DSN=HCLDB1.DB2.SPUFI(CREATETB)
********************************* Top of Data **********************
--------------------------------------------------------------------
---- AUTHORIZED TRANSACTION TABLE
--------------------------------------------------------------------
CREATE TABLESPACE C5710001
IN C5710
USING STOGROUP DB2111
PRIQTY 2160 SECQTY 720
PCTFREE 10
SEGSIZE 40
BUFFERPOOL BP2
LOCKSIZE ANY
CLOSE NO
;
CREATE TABLE D5710.AUTH_TRAN
( USER_ID CHAR(08) NOT NULL ,
SYST_TRANS_ID CHAR(04) NOT NULL ,
SEC_LEVEL_CD CHAR(02) NOT NULL WITH DEFAULT,
LAST_UPDT_USER_ID CHAR(08) NOT NULL WITH DEFAULT,
LAST_UPDT_DT DATE NOT NULL WITH DEFAULT,
LAST_UPDT_TM TIME NOT NULL WITH DEFAULT,
PRIMARY KEY ( USER_ID,
SYST_TRANS_ID )
)
IN C5710.C5710001
;
CREATE UNIQUE INDEX C5710OWN.I001IX01
ON D5710.AUTH_TRAN
( USER_ID ,
SYST_TRANS_ID )
USING STOGROUP DB2112
PRIQTY 720 SECQTY 720
CLUSTER
PCTFREE 10
BUFFERPOOL BP3
PIECESIZE 2 G
CLOSE NO
;
GRANT SELECT ON TABLE D5710.AUTH_TRAN
TO C5710RD
;

Page 27 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

GRANT SELECT, UPDATE, DELETE, INSERT ON TABLE D5710.AUTH_TRAN

TO C5710UPD, C5710OWN
;
****************************** Bottom of Data ********************

5. Object level changes that are NOT covered by an Application change control process.
Following Database change process,(refer to section 6.1.2.4) go through ERWIN model, CRDB process,
then following change process, creating a RFC. Use the same JCL above to apply the changes.

6. Install of new database software

i. Create WO to schedule started tasks
ii. Create WO to request started tasks access
iii. Following product installation procedure to install the software
http://webtop.merck.com/webtop/drl/objectId/090030f980d95a8c

7. Maintain scheduler and execution of database jobs

o Issue a Remedy WO for mainframe PSA team, and email them the request as well, to reschedule
the existing jobs or setting up a new schedule.
o For product thread terminator schedule
 Logon to WPTSO/RYTSO
 Use command D.3 to get on CA Unicenter to pick the option of Thread terminator

r11.5 ------ Thread Terminator Automated Update Schedules ----- 14-0

COMMAND ==>

USERID ==> HCLDB1

Cur schedule d.s. ==> SOFT.DBTOOLS.P.PXMPARM(PTTSCHED)
New schedule d.s. ==> SOFT.DBTOOLS.P.PXMPARM(PTTSCHED)

Commands: EDITSCHD edit schedules STOPSCHD stop scheduler

REFRESH refresh schedules STRTSCHD start scheduler
Execution of database jobs
Annual database jobs to archive CCAS Chargeback data.
Document is saved in
http://webtop.merck.com/webtop/component/main?__dmfClientId=1397494639706&__dmfRequestId=
__client1~~2&__dmfJumpType=jump

Page 28 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared

Services/DB2/Operations/CCAS_Chargeback-archive.xls
Jobs of 2013 excutions are stored in SOFT.ORACLE.P.VX.PARMLIB(GPXAFPS)

8. Backup
Take image copy of a tablespace, or multiple tablespaces via LISTDEF

//XXXXXXIC JOB (8676,5698,1),'WP97-B106',MSGLEVEL=(1,1),

// MSGCLASS=X,CLASS=E,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//****************************************************************8
//*
//* COPY TABLESPACE
//*
//****************************************************************8
//COPY EXEC DSNUPROD,UID='IC5710',UTPROC='',SYSTEM='DB2P'
//DSNUPROD.SYSIN DD *
--LISTDEF COPYLSTD
-- INCLUDE TABLESPACES DATABASE C5710
-- INCLUDE TABLESPACE C5710.C5710092
LISTDEF COPYLSTT
-- INCLUDE TABLESPACES DATABASE C5710
-- EXCLUDE TABLESPACE C5710.C5710102
INCLUDE TABLESPACE C5710.C5710095
TEMPLATE COPYDSD
DSN MSD.DBM.C5710.&TS..IC.D11&MO.&DA.
UNIT 3390 DISP (NEW,CATLG,CATLG) SPACE (540,5) CYL
TEMPLATE COPYDST
DSN MSD.DBM.C5710.&TS..IC.D12&MO.&DA.B
UNIT CTAPE DISP (NEW,CATLG,CATLG) RETPD 30
VOLCNT 25 STACK YES MODELDCB MRK.MODDSCB TRTCH COMP
--COPY LIST COPYLSTD
-- COPYDDN(COPYDSD) FULL YES
-- SHRLEVEL REFERENCE
COPY LIST COPYLSTT
COPYDDN(COPYDST) FULL YES
SHRLEVEL REFERENCE
/*
//*
//
9. Unload data from production
Unload data from production table, load it into test schema

//XXXXXXU0 JOB (5710,P240,5),'WP97-B106',CLASS=E,

//*TYPRUN=SCAN,
// MSGCLASS=X,MSGLEVEL=(1,1),
//*** RESTART=UPDATE3,

Page 29 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

// NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//*************************************************************
//**
//** UNLD FROM IMAGE COPY YYMMDD
//** 1. SET FOR ICD CURRENTLY D131014 & GDG ICD(-4)!
//** 2. CHECK RETPD CURRENTLY SET TO 60
//** 3. UNCOMMENT UPDATE3 IF NEEDED
//** ONLY UNCOMMENT OUT FOR T5710
//** NEED TO UPDATE FOR G2/GC
//** UNLDS GOING TO TAPE LISTED FIRST (TS 039, 038, 037)
//** WHEN ADDING NEW TABLES TO JCL, CREATE UNLD MEMBER IN UTIL.CNTL
//**
//*************************************************************

//*************************************************************
//*--TAPE DATASETS START HERE -- *****************************
//*************************************************************
//UNLD039 EXEC DSNUPROC,SIZE=4M,V='P',
// UID='UIC5710',UTPROC=''
//*-----------------------------------------------------------
//* WORK FILES
//DSNUPROC.SYSPRINT DD SYSOUT=*
//DSNUPROC.SYSREC DD DSN=MSD.DBM.C5710.C5710039.UNLDIC.D131014A,
// UNIT=CTAPE,VOL=(,RETAIN,,99),LABEL=(1,SL,,,RETPD=60),
// DISP=(,CATLG,DELETE),DCB=BUFNO=30
//***UPROC.COPYIC DD DSN=MSD.MKT.U5710.P000.C5710039.ICD(-4),
//DSNUPROC.COPYIC DD DSN=MSD.MKT.U5710.P000.C5710039.ICW(0),
// DISP=SHR
//DSNUPROC.SYSPUNCH DD DSN=MSD.DBM.T5710.DB2UTIL.CNTL(I039LD),
// DISP=SHR
//DSNUPROC.SYSIN DD DSN=MSD.DBM.C5710.DB2UTIL.CNTL(UNLD039),
// DISP=SHR
//************************************************************
//*************************************************************
//*--DISK DATASETS START HERE -- *****************************
//*************************************************************
//UNLDPROC PROC TS=,NUMPCKS=1
//UNLDPROC EXEC DSNUPROC,SIZE=4M,V='P',
// UID='UIC5710',UTPROC=''
//*-----------------------------------------------------------
//* WORK FILES
//DSNUPROC.SYSPRINT DD SYSOUT=*
//DSNUPROC.SYSREC DD DSN=MSD.DBM.C5710.C5710&TS..UNLDIC.D131014A,
// SPACE=(CYL,(750,250),RLSE),DISP=(,CATLG,DELETE),
// UNIT=(3390,&NUMPCKS.)
//***DSNUPROC.COPYIC DD DSN=MSD.MKT.U5710.P000.C5710&TS..ICD(-4),
//DSNUPROC.COPYIC DD DSN=MSD.MKT.U5710.P000.C5710&TS..ICW(0),
// DISP=SHR
//DSNUPROC.SYSPUNCH DD DSN=MSD.DBM.T5710.DB2UTIL.CNTL(I&TS.LD),
// DISP=SHR
//DSNUPROC.SYSIN DD DSN=MSD.DBM.C5710.DB2UTIL.CNTL(UNLD&TS.),
// DISP=SHR

Page 30 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//*-----------------------------------------------------------
// PEND
//*************************************************************
//**TS 001,006,030,031,032,094,095,102 NOT IN JCL BELOW *******
//UNLD002 EXEC UNLDPROC,TS=002
//*************************************************************
//UNLD003 EXEC UNLDPROC,TS=003
//*************************************************************
//UNLD004 EXEC UNLDPROC,TS=004
//*************************************************************
//UNLD005 EXEC UNLDPROC,TS=005
//*************************************************************
//UNLD007 EXEC UNLDPROC,TS=007
//*************************************************************
//UNLD008 EXEC UNLDPROC,TS=008

10. Creation of a new subsystem on a shared z/OS server

i. Create pre-implementation plan, coordinate with DB2 Systems DBA, DB2 Application DBA's ,
Application Team, and z/OS operations
ii. Create WO for Batch support
iii. Create subsystem by DB2 system programmer, Operations automates the schedule, create WLM batch
jobs.
iv. Request MVS to set up any external connection to access the Db2 database
v. Create DB2 objects, Stogroup, database, tablespace, and tables, index etc objects by DBA, and do the
first level testing.
a. Logon to WPTSO/RYTSO with proc PRODDDB2
b. Using CA-unicenter, database administration option 2 RC/migrator to generate the DDL to
create database, tablespace, tables, indexes, views, alias, foreign keys, bind plan and
packages for the application, it’s the database in general at Merck.
c. Logoff, then Logon to TSO with PROC TESTDB2
d. Create Stogroup
e. Run the generated DDL from step b. at test DB2 subsystem to create the database
f. Submit batch job to unload data from production then load them at test
g. Grant the table access to respective IBMGROUP.
h. Install gateway or 3rd party software which are requested by the application.

vi. Application team does the post implementation testing and followed by Application sign off.
vii. Create maintenance jobs

Page 31 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Back out plan

i. Create WO for Production Support team
ii. Stop started task
iii. Remove APF libraries
iv. Drop database
v. Stop maintenance jobs

11. Create, add or Migrate an application to a shared/non-shared database

i. Analyze inventory of the application, database objects, batch jobs of both database, and application,
connections, external feeds, Space usage
ii. Request DASD, request APF library, vendor products
iii. Create database objects, migrate data, migrate applications, bind plan/package
a. Logon to WPTSO/RYTSO with proc PRODDDB2
b. Using CA-unicenter, database administration option 2 RC/migrator to generate the DDL to
create database, tablespace, tables, indexes, views, alias, foreign keys, bind plan and
packages for the application, it’s the database in general at Merck.
c. Logoff, then Logon to TSO with PROC TESTDB2
d. Create Stogroup
e. Run the generated DDL from step b. at test DB2 subsystem to create the database
f. Submit batch job to unload data from production then load them at test
g. Grant the table access to respective IBMGROUP.
h. Install gateway or 3rd party software which are requested by the application.
i. Request MVS to set up any external connection to access the DB2 data

iv. Create maintenance jobs

12. Creation of a new subsystem as a clone of existing database to non-production environment

i. Analyze inventory of the application, database objects, batch jobs of both database, and application,
connections, external feeds, Space usage
ii. Request DASD, request APF library, vendor products
iii. Create database objects, migrate data, migrate applications, bind plan/package
a. Logon to WPTSO/RYTSO with proc PRODDDB2
b. Using CA-unicenter, database administration option 2 RC/migrator to generate the DDL to
create database, tablespace, tables, indexes, views, alias, foreign keys, bind plan and
packages for the application, it’s the database in general at Merck.
c. Logoff, then Logon to TSO with PROC TESTDB2
d. Create Stogroup

Page 32 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

e. Run the generated DDL from step b. at test DB2 subsystem to create the database
f. Submit batch job to unload data from production then load them at test
g. Grant the table access to respective IBMGROUP.
h. Install gateway or 3rd party software which are requested by the application.

iv. Create maintenance jobs

v. Request MVS to create the connection from DB2 to external systems.

13. Creation of a new schema, database to existing subsystem

i. Request DASD
ii. Create database, grant access,
a. Logon to WPTSO/RYTSO with proc TESTDB2 for test schema
b. Using CA-unicenter, database administration option 2 RC/migrator to generate the DDL to
create database, tablespace, tables, indexes, views, alias, foreign keys, bind plan and
packages for the application, it’s the database in general at Merck.
c. Create Stogroup, if the new schema will be using new stogroup
d. Run the generated DDL from step b. at test DB2 subsystem to create the database
e. Submit batch job to unload data from production then load them at test
f. Grant the table access to respective IBMGROUP.
g. Install gateway or 3rd party software which are requested by the application.

iii. Request profile

iv. Create maintenance jobs

14. Rebuild Index, recreates indexes from current data.

//XXXXXXRI JOB (8045,5221,4),'WP97-B106',MSGLEVEL=(1,1),
// MSGCLASS=X,CLASS=E,NOTIFY=XXXXXX,REGION=6M
/*ROUTE PRINT WP62
//UTIL EXEC DSNUPROC,UID='RBX5710',UTPROC='',V='P'
//*
//DSNUPROC.SYSUT1 DD DSN=&&SYSUT1,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500),RLSE),
// UNIT=(SYSDA,2)
//DSNUPROC.SYSIN DD *
Page 33 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

LISTDEF RBLDLIST
INCLUDE INDEX C5710OWN.I095IX01
INCLUDE INDEX C5710OWN.I095IX02
INCLUDE INDEX C5710OWN.I095IX03
INCLUDE INDEX C5710OWN.I095IX04
INCLUDE INDEX C5710OWN.I095IX05
INCLUDE INDEX C5710OWN.I095IX06
REBUILD INDEX LIST RBLDLIST
15. Additions of Tablespace space
Adding volume to the Stogroup
Expand the STOPGROUP by altering, adding new packs. This does not affect the existing
datasets, until a reorg , load replace or recover utility gets executed.

ALTER STOGROUP DB2133 ADD VOLUMES(DB2130,DB2135) ;

Increase the size of tablespace, or indexspace, the object needs to be stopped, execute the command
when the table is not in use.
//XXXXXXAT JOB (5710,P240,10),'WP97-B106',MSGLEVEL=(0,0),
// NOTIFY=&SYSUID,MSGCLASS=X,CLASS=I
/*ROUTE PRINT WP62
//******************************************************************
//* THIS JCL WILL RUN A STREAM TO STOP A TABLESPACE, ALTER IT
//* FOR SIZE, RESTART IT
//******************************************************************
//*
//JOBLIB DD DSN=SOFT.DB2.P.DSNLOAD,DISP=SHR
//*
//STOPTS EXEC PGM=IKJEFT01,DYNAMNBR=20
//*** STOP TABLESPACE
//*
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB2P)
-STOP DB(C5710) SPACE(C5710092)
END
/*
//*** -STOP DB(C5710) SPACE(I092IX0*)
//***
//SYSIN DD *
/*
//ALTTS EXEC PGM=IKJEFT01
//STEPLIB DD DSN=SOFT.DB2.P.DSNLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *

Page 34 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DSN SYSTEM(DB2P)
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP2) -
LIB('SOFT.DB2.P.RUNLIB.LOAD')
/*
//SYSIN DD *
--
ALTER TABLESPACE C5710.C5710092
USING STOGROUP DB2118
PRIQTY 1296000
SECQTY 129600
;
ALTER INDEX C5710OWN.I092IX01
USING STOGROUP DB2133
PRIQTY 79920 SECQTY 3600
;
//****
//STARTRW EXEC PGM=IKJEFT01,DYNAMNBR=20
//*** START TABLESPACE FOR READ-WRITE ACCESS
//*
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DB2P)
-START DB(C5710) SPACE(C5710092)
END
/*
//*** -START DB(C5710) SPACE(I092IX0*)
//***
//SYSIN DD *
/*
//***
//
16. Reorg, is used to improve data access and reclaim fragmented space. Reorg could apply to tablespace or
Index. Prior to reorg a tablespace, make an image copy of the current tablespace, in case back out is
needed .
Reorg tablespace
********************************* Top of Data
************************
//XXXXXXR0 JOB (8045,5221,60),'WP97-B106',MSGLEVEL=(1,1),
// MSGCLASS=X,CLASS=E,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//***** CAN ALSO USE CLASS "F" IN LONG RUNNING JOBS
//REORG EXEC DSNUPROD,UID='RG5710',UTPROC='',SYSTEM='DB2P'
//*
//****************************************************
//*
//* GENERATING JCL FOR THE REORG TABLESPACE UTILITY
//*
//****************************************************
//*

Page 35 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//DSNUPROD.SORTWK01 DD DSN=&&SORTWK01,
// DISP=(NEW,DELETE,CATLG),
// SPACE=(CYL,(500,500)),
// UNIT=SYSDA
//DSNUPROD.SORTWK02 DD DSN=&&SORTWK02,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(500,500)),
// UNIT=SYSDA
//DSNUPROD.SORTWK03 DD DSN=&&SORTWK03,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(500,500)),
// UNIT=SYSDA
//DSNUPROD.SYSREC DD DSN=&&REORGOUT,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,3)
//DSNUPROD.SYSUT1 DD DSN=&&SYSUT1,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,3)
//DSNUPROD.SORTOUT DD DSN=&&SORTOUT,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,3)
//DSNUPROD.SYSIN DD *
LISTDEF RGLIST
INCLUDE TABLESPACE C5710.C5710092
TEMPLATE COPYDSD
DSN MSD.DBM.C5710.&TS..IC.D11&MO.&DA.B
UNIT 3390 DISP (NEW,CATLG,CATLG) SPACE (540,5) CYL
TEMPLATE COPYDST
DSN MSD.DBM.C5710.&TS..IC.D11&MO.&DA.B
UNIT CTAPE DISP (NEW,CATLG,CATLG) RETPD 30
VOLCNT 25 STACK YES MODELDCB MRK.MODDSCB TRTCH COMP
REORG TABLESPACE LIST RGLIST LOG NO SORTDATA
COPYDDN(COPYDSD) SHRLEVEL NONE
KEEPDICTIONARY
STATISTICS TABLE ALL INDEX ALL KEYCARD
/*
//

Reorg Index
//XXXXXXGX JOB (8045,5710,4),'WP97-B106',MSGLEVEL=(1,1),
// MSGCLASS=X,CLASS=E,NOTIFY=&SYSUID,REGION=6M
/*ROUTE PRINT WP62
//REORG EXEC DSNUPROD,UID='RGX5710',UTPROC='',SYSTEM='DB2P'
//*
//****************************************************
//*
//* GENERATING JCL FOR THE REORG TABLESPACE UTILITY
//* DATE: 09/05/89 TIME: 17:19:37
//*
//****************************************************
Page 36 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//*
//DSNUPROD.SYSREC DD DSN=&&REORGOUT,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,4)
//* UNIT=CTAPE
//DSNUPROD.SYSUT1 DD DSN=&&SYSUT1,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,4)
//* UNIT=CTAPE
//DSNUPROD.SORTOUT DD DSN=&&SORTOUT,
// DISP=(NEW,DELETE,DELETE),
// SPACE=(CYL,(750,500)),
// UNIT=(SYSDA,4)
//* UNIT=CTAPE
//DSNUPROD.SYSIN DD *
LISTDEF RGLISTIX
INCLUDE INDEX C5710OWN.I092IX01
REORG INDEX LIST RGLISTIX
-- STATISTICS KEYCARD
SHRLEVEL NONE
/*
//

Back OUT

To back out the Reorg, recover the tablespace with image copy taken prior to the Reorg.

17. Modify backup job, update control card to include/exclude tablespace/database

Logon to RYTSO/WPTSO/SYSA
Get on ISPF edit
Edit the control member MSD.MKT.U5710.DB2UTIL.CNTL(U5710ID2)

***************************** Top of Data *******************

LISTDEF COPYLIST
INCLUDE TABLESPACE C5710.C5710*
-- CHARGEBACK ARCHIVE TABLES SKIPPED
EXCLUDE TABLESPACE C5710.C5710094
EXCLUDE TABLESPACE C5710.C5710095
EXCLUDE TABLESPACE C5710.C5710102
TEMPLATE COPYDST
DSN 'MSD.MKT.U5710.P000.&TS..ICD(+1)'
UNIT CTAPE DISP (NEW,CATLG,CATLG) RETPD 16 BUFNO 30 GDGLIMIT 26
VOLCNT 25 STACK YES MODELDCB MRK.MODDSCB TRTCH COMP
COPY LIST COPYLIST
COPYDDN(COPYDST) FULL YES CHECKPAGE
SHRLEVEL REFERENCE

Page 37 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

**************************** Bottom of Data **********************

18. Modify reorg job, update control card to include/exclude

tablespace/database

-- REORG TABLES / INDEXES 1 THRU 199 + C5723M* RPMON* ALSO SEE

U5723RT

LISTDEF RGLISTTS1
INCLUDE TABLESPACE C5723.C5723001
INCLUDE TABLESPACE C5723M.C5723M00
-- WEEKLY REORGS
INCLUDE TABLESPACE C5723.C5723013
INCLUDE TABLESPACE C5723.C5723017
INCLUDE TABLESPACE C5723.C5723029
INCLUDE TABLESPACE C5723.C5723099
-- AS NEEDED REORGS
INCLUDE TABLESPACE C5723.C5723098
-- INCLUDE TABLESPACE C5723.C5723100
-- INCLUDE TABLESPACE C5723.C5723097
-- INCLUDE TABLESPACE C5723.C572308*

19. Update database statistics by executing RUNSTATS job.

The RUNSTATS utility gathers summary information about the

characteristics of data in table spaces, indexes, and partitions. DB2®
records these statistics in the DB2 catalog and uses them to select
access paths to data during the bind process.

The two formats for the RUNSTATS utility are RUNSTATS TABLESPACE and
RUNSTATS INDEX. RUNSTATS TABLESPACE gathers statistics on a table space
and, optionally, on tables, indexes or columns; RUNSTATS INDEX gathers
statistics only on indexes. RUNSTATS does not collect statistics for
index spaces.

Runstats Tablespace

//XXXXXXRS JOB (8045,5710,4),'WP97-A237',MSGLEVEL=(1,1),

// MSGCLASS=X,CLASS=I,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//UTIL EXEC DSNUPROD,UID='RSX5710',UTPROC='',SYSTEM='DB2P'
//*

Page 38 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

//DSNUPROD.SYSIN DD *
RUNSTATS TABLESPACE C5710.C5710090
INDEX (ALL) UPDATE (ALL) SHRLEVEL CHANGE
/*
//

Runstats Index
***************************** Top of Data ************************
//XXXXXXRS JOB (8045,5710,4),'WP97-A237',MSGLEVEL=(1,1),
// MSGCLASS=X,CLASS=I,NOTIFY=&SYSUID
/*ROUTE PRINT WP62
//UTIL EXEC DSNUPROD,UID='RSX5710',UTPROC='',SYSTEM='DB2P'
//*
//DSNUPROD.SYSIN DD *
RUNSTATS INDEX (C5710OWN.I090IX03) SHRLEVEL REFERENCE
/*
//
***************************** Bottom of Data **********************

20. Modify Database Initialization Parameter

o Logon to WPTSo/RYTSO/SYSA with proc testdb2 for test and proddb2 for prod
o Using ca-unicenter by D.3 to invoke the tool
o Select option TT to get on Dynam DSNZPARM, to make change to the initialization
PARM.

Changing the ZPARM via CA-Unicenter , option TT

Page 39 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

21. Enable data file auto extend/auto grow

Add overflow pack to the stogroup
In Merck,
ALTER STOGROUP FACTSA2 ADD VOLUMES (DBTFA6,DBTF01) ;
DB2 provided following procedure to manage the data file auto extend

Page 40 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

OPTIMIZE EXTENT SIZING field (MGEXTSZ subsystem parameter)

The MGEXTSZ subsystem parameter controls whether secondary extent allocations for DB2®-managed data sets
are to be sized according to a sliding scale. Sizing the secondary extents on a sliding scale optimizes the likelihood
of reaching the maximum data set size before secondary extents are exhausted.
Accetable values YES, NO
Default YES
Update option: 9 on panel DSNTIPB
DSNZPxxx DSN6SYSP:MGEXTSZ

YES

DB2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces
that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data
set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than
zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the
value that is derived from the sliding scale algorithm.

NO

Secondary extent allocations are managed manually. For nonpartitioned table spaces and nonpartitioned index
spaces, when all extents of the first data set are exhausted, the primary space allocation of each subsequent
data set is always the PRIQTY setting.

When the sliding scale is used, secondary extent allocations that are allocated earlier are smaller than those
allocated later, until a maximum allocation is reached. The maximum allocation is 127 cylinders for data sets with
a maximum size of 16 GB or less, and 559 cylinders for data sets with a maximum size of 32 GB or 64 GB.

Secondary extent allocations for data sets in implicitly created table spaces are not influenced by this setting
because they always use the sliding scale.

22. Disable data file auto extend/auto grow

Remove the overflow pack to the stogroup
ALTER STOGROUP FACTSA2 REMOVE VOLUMES (DBTF01) ;

Set DSNZPARM MGEXTSZ to NO

23. Adding new features to existing environment

o Logon to WPTSO/RYTSO with proc testdb2 or prodtdb2
o Modify DSNZPARM to activate the changes, after started task
recycled, will activate the attribute change
o changing the ZPARM via CA-Unicenter , option TT

Page 41 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

24. Create a new database as a clone of an existing database to non-production environment

i. Create a WO to
a. request DASD at target environment from Storage Management Support
b. request high level qualifier, if it’s not existing
ii. Create a set of DDL of the database to be cloned, with Stogroup, Database, tablespace, and all
the related objects

Page 42 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

a. Logon to WPTSO/RYTSO with proc PRODDDB2

b. Using CA-unicenter, database administration option 2 RC/migrator to generate the DDL
to create database, tablespace, tables, indexes, views, alias, foreign keys, bind plan and
packages for the application, it’s the database in general at Merck.
c. Logoff, then Logon to TSO with PROC TESTDB2
d. Create stogroup
e. Run the generated DDL from step b. at test DB2 subsystem to create the database
f. Submit batch job to unload data from production then load them at test
g. Grant the table access to respective IBMGROUP.
iii.
iv. Execute the DDL at target environment
25. Create LINK RDBMS Systems – Gateways, DB links, Link servers
i. create WO for Operations production support to schedule the started task
ii. Set up Oracle gateway mainframe components

http://webtop.merck.com/webtop/drl/objectId/090030f980ed93d8
http://webtop.merck.com/webtop/drl/objectId/090030f980ed93d9
http://webtop.merck.com/webtop/drl/objectId/090030f980ed93da
http://webtop.merck.com/webtop/drl/objectId/090030f980ed93db
http://webtop.merck.com/webtop/drl/objectId/090030f980ed93dc

26. Granting security to users

Logon to RYTSO/WPTSO with proc PRODDB2
Using SPUFI via D.1.1 or
SPUFI batch
MSD.DBM.C5710.DB2UTIL.JCL(BATSPUFI) - 01.04 Columns 00001 00072
***************************** Top of Data ******************************
//XXXXXXBS JOB (5710,P240,10),'WP97-B106',MSGLEVEL=(0,0),
// NOTIFY=&SYSUID,MSGCLASS=X,CLASS=I
/*ROUTE PRINT WP62
//********************************************************************
//*
//JOBLIB DD DSN=SOFT.DB2.P.DSNLOAD,DISP=SHR
//*
//BATSPUFI EXEC PGM=IKJEFT01
//STEPLIB DD DSN=SOFT.DB2.P.DSNLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *

Page 43 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DSN SYSTEM(DB2P)
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP2) -
LIB('SOFT.DB2.P.RUNLIB.LOAD')
/*
//SYSIN DD DISP=SHR,DSN=MSD.DBM.C5710.DB2DDL.CNTL(GRANTPMS)
**************************** Bottom of Data ****************************

i. Grant table access to ACCESS GROUP(IBMGROUP)

ii. Access group name is following the naming convention of
Complex number + RD for read
Complex number + UPD for update
With multiple schema for a complex in test environment,
the IBMGROUP will be varied.
iii. Create a WO with MRA(mainframe resource authorization) form to A&A, the later will create
profile for each of the IBMGROUP in TOP Secret, and grant the profile to individual user.

27. Revoking security from users

Create WO for A&A to remove users from profile, with an approved MRA form.
28. Administration of Database Management tools
Logon to RYTSO/WPTSO with proc PRODDB2
Logon to SYSA

Then follow the product installation procedure provided by Vendor.

7.5.6 Change Management – Implementation

7.5.6.1 Raising a RFC
A RFC can be raised by a Remedy User who has permission for the Change Management module. Below are the
important points to follow when you raise an RFC that should be taken care of.
1. The tasks and team involved should be identified and their availability should be agreed to in
advance.

2. Enter the correct information of risk, rollback effectiveness to calculate the Risk level properly

3. For pre-authorized changes, ensure that the change is registered in the Common Catalog.

Page 44 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

4. Tasks should be created and assigned to the respective team in the correct order based on the
dependency in Remedy. In case there is no dependency between two tasks, they (both tasks) should
have the same sequence number to enable both of the implementers to work in parallel, saving time.

5. If the implementation of a change requires down time, it (downtime) must be agreed to with the
application owner before submitting the RFC for approval.

6. The change request must be written clearly and should include any dependencies such as Pre-
implementation check, etc.

7. There should be a proper Test plan.

8. There should be a proper Rollback plan to fallback in case the test result fails.

9. Once submitted for approval, it goes through the approval process with the concerned service owner.

10. There is new feature of Future Approvers which will help you chase the approvers to approve if you
are short on time.

For additional detail, please refer the Change Management Job Aid document at:
http://webtop.merck.com/webtop/wdk/system/drl/redirecttomain.jsp

7.5.6.2 Scheduled Downtime Notification

In Remedy, scheduled down time is created to send the notification to all of the parties. To create it, go to Remedy >
Application >Quicklink> Scheduled Down Time.

7.5.6.3 Changes that Require an RFC and Their Change Status

All Production and Validated or GXP Formal Test Environment non-operational changes require an RFC (Request
for change) and CAB approvals prior to implementing the change. If you have any doubt about the Validated / GXP,
please refer the “Regulatory Indicator” in the CI of the Server/Instance.

7.5.6.4 RFC Timings

Productions changes are only permitted after 7 PM EST on Friday and must be completed by 6 PM EST on Sunday.
Exemption Requests to this procedure are submitted to Chuck Denecke.

Emergency RFCs:
Any exceptions to the above will require an Emergency Change Request. The Emergency Change Request must
follow the normal approval process with an additional approval — all Emergency Changes must be pre-approved by
an ETAS Leadership Team member.
 All Major RFCs must be submitted by 12 AM EST Tuesday for changes to be implemented for the
upcoming weekend.
 All Minor RFCs must be submitted by 2 PM EST Thursday for changes to be implemented for the
upcoming weekend.

Page 45 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

7.5.6.5 RFC Work Instructions

Here are some pre-defined questionnaires that are addressed before the RFC is raised.
1. What is the full name of the application impacted by the change?

2. Does this change impact an Oss application? If so, have you attached approval from the Oss CAB in
Work Info History?

3. What is the environment impacted by the change (database name & server name)?

4. What is the test environment where this change was previously implemented (database name & server
name) or explanation if N/A?

5. What is the business driver or reason for the change?

6. What are the before and after details of the proposed change?

7. If downtime is required what are the details if they are not stated in the Summary field?

8. If the change is listed as an emergency, what is the reason and urgency for the change?

7.5.7 Support Group Names

The following Remedy groups are used for database related changes.
IS Change_Management (RFC Change Manager)
GTS Inf_Database_Services (RFC Change Coordinator)

7.6 Service Knowledge Management

Knowledge Management is the process that governs the gathering, analyzing, storing and sharing of knowledge
information. Its primary objective is to improve efficiency by reducing the need to rediscover knowledge. All
operational tasks should be entered into a KM article. This information in KM articles is used to manage the
platform by each tier group; therefore, it is important that such information is up to date and accurate.

The procedure to support Knowledge Management is as follows:

 SDLC-SOP-05-07: Administration and Control of Service Knowledge Management Articles for Global
Services (GS)

8 Service Manager Roles & Responsibilities

The Service Manager gets requests from Merck clients in the service management queue that is “Database_Services
Resources”. For DB2 activities there is no Service Manager. The DBA performs the Service Manager role.

8.1 Remedy Ticket Initiation and Assignment

All requests for DB2 Database Support must first be initiated by a Remedy Work Order, Service Request, or
Incident. The Requestor should include a detailed description of the request or problem, the database name, and the
server’s name. The Remedy ticket should be submitted to the “DATABASE_SERVICES RESOURCES” Remedy
Group for HCL to manage.

Page 46 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

HCL actively monitors this queue on a 24x7 basis to respond, manage, and complete the request according to the
SLA for the requests’ priority.

8.2 Support Group Names

All requests/incidents are submitted through Remedy. The following groups are used for database related requests
and incidents.
1. Infrastructure DATABASE_SERVICES (Merck DBA WOs and Incidents)
2. Infrastructure DATABASE_SERVICES RESOURCES (HCL DBA WOs and Incidents)

Note: E-mails/IMs/Phone calls will be responded to for emergency requests, but a Remedy ticket must be submitted
shortly thereafter.

8.3 Updating Resource Scheduling Calendar

The Resource Scheduling Calendar is used to get the Service Manager, Escalation Manager and On-call resource
names for the current week and near future weeks.

We need to make changes before 3PM EST. (for the upcoming week); otherwise the changes will not be reflected in
the notification email.

Steps for adding names in the calendar:

1. Request Service Manager role access to Database Shared Services Portal http://ssdba-central-prd.merck.com from
Keith or any other relevant authority

2. Login to Database Shared Services Portal http://ssdba-central-prd.merck.com

3. Click on DBA Scheduling icon.

4. Click on Event Management icon

Page 47 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

5. Select Schedule Name as Database Shared Services and select Date Range

6. Select week in which you want to add/edit resource name

7. For adding resource click on green plus (+) symbol.

8. Select resource name, role and region and press Next button.

9. Press Ok button to confirm Service Manager Assignation or Cancel to cancel it.

10. For Editing Calendar, select week in which you want to make changes.
For editing existing resource, click Edit button under Action column. To add a new resource, click Green Plus icon.

Page 48 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

11. Make changes and then press Apply and Return button.

12. To see the existing Calendar, Schedule and Matrix report go to the Report section

9 DB2 Subsystem Details

9.1 Mainframe Infrastructure
Merck has two mainframes and five LPARs. The Hardware details:
The WT and SYSF LPARs are being used as a staging system for software installation and up-grades.

9.2 Host Names

Machine LPAR Hostname IP Address Remarks
SYSA SYSA.US.SCHP.COM 172.30.58.37 Production
Schering Plough
SYSF SYSF.US.SCHP.COM 172.30.58.13 Test
Merck-
RY RYIBM 172.30.58.143 Production
Rahway
Merck- WP WPIBM 172.30.58.144 Production
WestPoint WT WTIBM 172.30.58.145 Test
DR Site Will be identified prior Production

Page 49 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

to the drill

The WT and SYSF LPARs are being used as a staging system for software installation and up-grades.

9.3 JOBCARD Details

The following Job classes are used while submitting batch jobs:
Class “E” and “F” for general jobs
Class “J” is for quick running jobs

MSGCLASS X and Z are used.

The batch jobs submitted under MSGCLAS of X will be there in spool until manually purged but MSGCLASS of Z
will be cleaned up at midnight.

/*ROUTE PRINT WP/RY

Without Route card specified in the JCL at RY, the job log will be routed to WP.

9.4 DB2 PROCS

On West Point:
Production
DSNUPROD
//LOADDB2P EXEC DSNUPROD,SIZE=4M,
// UID='DB2LOAD',UTPROC='',PARM='DB2P’

Test
DSNUPROC
//LOADDB2T EXEC DSNUPROC,SIZE=4M,
// UID='LD5725',PARM='DB2T',UTPROC='',V='T'

On Rahway:
Production
//IBMCOPY EXEC DSNUPROD,SYSTEM='DB2P',UID='xxxxxxCP',UTPROC=''

Test
//STEP01 EXEC DSNUPROC,SYSTEM='DB2T',UID='xxxxxxCP',UTPROC=''

9.5 Overflow Pack Approach

Overflow packs are different on WP, RY
West Point Rahway #FACTS #FACTS Litigation
DBTF01, DBTF059, DBTF089,
DB2135 DBT145 DBTL01
PROD DBTF099
DBT*01,DBT*59,
DB2202 DBT244 DBTM01
TEST
DBT*89, DBT*99

#FACTS has its’ own overflow pack design.

Page 50 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

On LPAR - SYSA, DB2 space resource is managed by SMS, no overflow pack management is required.

Overflows pack maintenance:

1. Check overflow pack, if there are any DB2 underlying datasets allocated on the pack, and less 50% free, these
tablespace or index spaces need to be moved out by reallocating the space quantity and reorg.
2. Run the RSVP process to generate a report of the DB2 database underlying dataset space usage. It will display the
attributes depending on the parameters specified in the batch job. An example is listed below, and the JCL used to
generate the report follows.

DSNAME VOLUME ALLOC SECQ VEXT PCT USED UNUSED

CREDT
DB2RYT.DSNDBC.T5723D5.IL01IX01.I0001.A001 DBTB62 450 45 1 1 5 445
08/26/2013

//XXXXXXVP JOB (5723,5723,4),'WP97-B106',CLASS=E,MSGCLASS=Z,

//*** RESTART=STEP02,
// NOTIFY=XXXXXX
//***
/*ROUTE PRINT RY
//***
//* RUNS IN 20 TO 30 MIN
//***
//RSVPD5 EXEC PGM=$ASMBMON
//*
//ISPMLIB DD DSN=SOFT.CACOM.P.CAIISPM,DISP=SHR
//SYSIN DD *
$RSVP VOL (DB) -
CLUSTER -
BEGIN (DB2RYT.DSNDB) -
CONTAINING (T5723D5. T5723M5.) -
CYLS -
PRINT -
(NEW -
(DSNAME VOLUME -
ALLOC SECQ VEXTS -
PCT USED UNUSED CREDT))
/*
//SYSTSPRT DD SYSOUT=*
//$RSOUT DD DSN=HELO19.JCL.REPORTS(RSVPD5),DISP=SHR
//$RSTRANS DD DUMMY
//ABNLDUMP DD DUMMY
//SYSUDUMP DD DUMMY
//

3. List the tables to find out table name gap, e.g. between T5723204 and T5723208 below, for the next new
tablespace to be used.
DSNAME VOLUME ALLOC SECQ VEXT PCT
DB2RYT.DSNDBC.T5723D5.T5723201.I0001.A001 DBTB03 1 1 1 4
DB2RYT.DSNDBC.T5723D5.T5723202.I0001.A001 DBTB02 1 1 1 4
DB2RYT.DSNDBC.T5723D5.T5723203.I0001.A001 DBTB03 1 1 1 4
DB2RYT.DSNDBC.T5723D5.T5723204.I0001.A001 DBTB02 1 1 1 4
DB2RYT.DSNDBC.T5723D5.T5723208.I0001.A001 DBTB02 1 1 1 4
Page 51 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DB2RYT.DSNDBC.T5723D5.T5723209.I0001.A001 DBTB03 1 1 1 4
DB2RYT.DSNDBC.T5723D5.T5723210.I0001.A001 DBTB02 1 1 1 4
4. When you reallocate the space quantity, allow 20% freespace
5. Find the enabled volume in the System LOG
For example: for WP production volumes, use command /D SMS,SG(db23390),LISTVOL
6. Use QW to find out the available volume quantity
7. Alter the tablespace quantity allocation. Each application has its’ own job in its’ respective PDS .
e.g. MSD.DBM.C5725.DB2UTIL.JCL(ALTS411)
* make sure the volume assignment is correct, even tablespace on even volume,
odd index on odd volume
* select a volume with enough cylinders for the primary allocation
8. Run above job to alter the space
9. Manually schedule a reorganization job by modifying the Include statement to include
Tablespace name in LISTDEF
e.g. MSD.MKT.U5725.DB2UTIL.CNTL(U5725RG2)
10. Changes are validated, space allocation is sufficient, TS with 1 extent, and moved out of the overflow pack,
remove the TS name from the reorg job.

FACTS has its’ own Stogroups DBTF*, DB2F* and separate Stogroups for each schema

schema 4th char of DBT*99 total volumes mod 9

D1 E 111 4
D2 H 123 4
D3(obsolete) D 111 4
D4 A 111 4
D5 B 123 4
D6(obsolete) G 111 4
D7(obsolete) J 75 4
D8(obsolete) I 111 4
D9 K 49 4
QA Q 111 4
ST(obsolete) C 123 4
PS S 111 4
Prod F 121 9
Prod litigation L 113 0
Test litigation M 9 0

D3, D6, D8 and ST have been decommissioned as of 9/17/2013

9.6 Database Roadmap

Below is the database roadmap Link:
http://ssdba-central-prd.merck.com/pls/apex/f?p=100:22:0::NO:RP::

Page 52 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DB Platform Standards, see Appendix A

9.7 DB2 Subsystem Logon Details

The WP/RY logon procedures:
Logon
Environment
Proc

TEST TESTDB2

DEVL DEVDB2

PROD PRODDB2

The SYSA logon procedure: $CICUAF

The SYSF logon procedure: $CICUAF

9.8 Storage Groups

RY/WP and SYSA
All DASD volumes are initialized as SMS Managed. Volume initialization is performed by the Systems
Programmer (IBM). Each and every volume has been defined in a unique storage group in DB2. A number of
storage groups are defined with multi-volume disks.

RY/WP
For Production databases, the Production DB2 volumes are under the DB23390 SMS managed storage groups and
the Test DB2 volumes are under DBT3390.

To request additional volumes

IF extra volumes are required, get the approval from the Database manager and System Manager, then create a
Work Order for IBM Storage Management Support to add the volumes.
To move the volumes to a different SMS group, create a Work Order with the volumes’ from and to group listed,
send it to the Infrastructure>Mainframe team. Below is a screen shot of the request.

Page 53 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

RY/WP and SYSA

The volumes are initialized as MOD3 (3331 cylinders). A number of volumes are initialized as MOD9 (9993
cylinders). For large tables, MOD9 volumes are being used.

RY/WP
Disk Volume storage space, free space and its storage group names can obtained by invoking ‘QW’ from the TSO
option command line.

RY/WP
Tablespaces and index spaces are maintained in a different set of volumes. Even numbered tablespaces are allocated
to even number volumes and odd numbered tablespaces are allocated to odd numbered volumes. Indexes are
allocated opposite to their respective tablespace allocation. Larger tables and their indexes are organized in
multivolume storage groups.

9.9 Datasets
For RY and WP LPARs:

The system datasets and libraries are in:

‘SOFT.DB2.x.SDSNLOAD’
‘SOFT.DB2.x.SDSNEXIT’

Where x denotes the environment name. For production it is ‘P’, ‘T’ for test and ‘D’ for development.

Page 54 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

For SYSA LPAR:

The system datasets and libraries are in:

‘SYS1.DSN.SDSNLOAD’
‘SYS1.DSN.SDSNEXIT’
‘SYS1.DSNT.SDSNLOAD’
‘SYS1.DSNT.SDSNEXIT

The production database High Level Qualifier is DB2WPP/DB2RYP and for test database the HLQ is
DB2WPT/DB2RYT

SYSA VSAM HLQ – BDVP, IDVP, PDVP, SDVP, SPVP

BDVT, IDVT, PDVT, SDVT, SPVT
SYSV
Totally we have 65 Databases in SYSA. No QMF installed in the system. Only One SP CFRS615 user Stored
Procedure created in SYSA.
Using SDSF 3.4 ‘*.DSNDBD.*’ – resulted in 24,089 VSAM rows. 9,360 on volumes and 14,929 migrated.

To migrate JCL/Jobs to production, migrate them to the shared dataset OCS.OPS.TRANSFER.DATA

Then create a WO for Mainframe PSA team to migrate the changes to production.
9.10 WLM
Stored Procedures running under WLM address spaces:

Mainframe DB2 WLM Name Stored Procedure Load Library

Subsystem
RY DB2T WLMRTDEV SOFT.OPER.T.WLMDEV
RY DB2T WLMRTQA SOFT.OPER.T.WLMQA
RY DB2T WLMRTPS SOFT.OPER.T.WLMPS
RY DB2T WLMRTST SOFT.OPER.T.WLMST
RY DB2P WLMRP1 SOFT.OPER.P.WLMPROD
WP DB2T WLMWTDEV SOFT.OPER.T.WLMDEV
WP DB2T WLMWTQA SOFT.OPER.T.WLMQA
WP DB2P WLMWP1 SOFT.OPER.P.WLMPROD
SYSA DSN DSNBDC* SYS2.DSN.STPROC.RUNLIB.LOAD
SYSA DSNT DSNTBDC*, SYS2.DSNT.STPROC.RUNLIB.LOAD
DSNTFRS1

 1,2,3,4
Setup by IBM BD2 system support
9.11 DDF
WP Production
PORT: 5021
Location: WESTPOINT_PROD

Page 55 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

LU: MERCKNET.WPPDDF

WP Test
PORT: 446
Location: WESTPOINT_TEST
LU: MERCKNET.WPTDDF

RY Production
PORT: 5021
Location: RAHWAY_PROD
LU: MERCKNET.RYPDDF

RY Test
PORT: 446
Location: RAHWAY_TEST
LU: MERCKNET.RYTDDF

SYSA Production
PORT: 10446
Location: USSCHP01DSN
LU: USSCHP01.DSN

SYSA Test
PORT: 20446
Location: USSCHP01DSNT
LU: USSCHP01.DSNT

9.12 Applications List

This is a list of the major applications. All mainframe DB2 applications are in scope.
SYSA – (Formerly Schering –Plough)
CCC – Corporate Coding
DTQ – Data Quality
DIM – SP Drug Information Management
HCE – Health Care Entity
HCP – Health Care Practitioner
MCR – Managed Care Rebate
SJV – Merck Joint Venture
POS – Production Ordering System
PDB – Prescriber DB
PRM – Prescriber Maintenance
RAS – Royalty Accounting System
DBA, FLD – Roster or Sales Alignment
HFM – Sales Incentive
SAC – Sample Account
FRS – Financial Reporting System (SOX)
MCC – Audit and Validation
EDS – CHRIS Extract

Page 56 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

SYSB –Rahway (RY)

C2533 – CAPS(Sox)
C2536 – RDB
C2543 – SOAP
C5723, C5723M – FACTS
C5723L, C5723LM -- EDISCOVERY
C5752 – PIMS
C5787 – FACTS DSS
DATMIRPR – Change Data Capture (CDC, refer to 11.4.2)
PSTDB – OPTIM
RPMON – Replication Monitor

SYSC –WestPoint (WP)

C5227 – IMPACT (refer to 11.4.3)
C5710 – CCAS(SOX)
C5712 – MEDICAID
C5725 – CIMS
C5738 – PHUB(SOX)
C5769 – FIRS

9.13 Service Request Management and Access Management Tool Understanding

Requests are managed using Remedy. There are in-house learning courses available to understand the functionality
of Remedy.
Previously, all requests were handled through Emails, Lync and over the phone. As of August 1, 2013, all requests
will be made through a Remedy Work Order or an Incident.
9.14 Application Owners Contact Details
They are listed in Remedy Asset Management.

9.15 Service Window

RY/WP
IPL: Machine is normally IPLed every week on Sunday at 04:00PM ET.
DB2: Certain changes require DB2 in standalone mode during the Merck service window. For the mainframe, it is
between Sunday 04:00PM and 11:00PM ET.

SYSA-Schering Plough LPAR

IPL: Machine is normally IPLed every week on Sunday from 8:10 AM to 10:00 AM ET.
The DB2 maintenance window is between 8:05 AM to 10:30 AM ET on Sunday morning.
9.16 On-call List
The operations team refers to the following datasets to reach out to the DBAs for any Batch job failures.
For WP/RY:
“SOFT.OPER.P.PROSE.DATA”
To update the on-call information, migrate them to the shared dataset OCS.OPS.TRANSFER.DATA
Page 57 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

then create a WO for Mainframe PSA team to migrate the changes to this production dataset.

For SYSA:
“SPOPS.CALLLIST”, DB2 DBA has access to this dataset, could update it directly.

10 Security and Account Management -

Security and Account Management is the process responsible for controlling access to applications and systems
within the Merck IT environment; ensuring only appropriate access and privileges are provided and maintained.
Corporate policy 26 and its supporting Functional Policies outline the mandatory security requirements and elements
for enforcing Account Access and Security in the Merck IT environment.

The core procedure to support Security and Account Management is as follows

 ITSOP-0014: Account and Access Management for IRM&C Supported Applications and Systems

10.1 DB2 Security Standards

There are three IBMGROUPs (secondary Authorization Id) that are used for accessing databases.

XXXXXRD Prod/Test
XXXXXUPD Prod/Test
XXXXXOWN Prod only

Where XXXXX represents the database name

Variations of above when more than 1 test database exists for example;
Database
T5710G2 T5710G2 (update) T5710G2R (read)
T5710G3 T5710G3 (update) T5710G2R (read)
T5710GC T5710GC (update) T5710GCR (read)
T5769QA T5769UPQ (update) T5769RDQ (read)
Check existing access and you will see the pattern

Any other special access request should come through a Work Order. Once it is approved, the requested access will
be given to the Acid either by granting the IBMGROUP to it or granting a Profile that contains the IBMGROUP to
it.

The requestor will submit a “MAINFRAME RESOURCE AUTHORIZATION FORM” to Access & Administration
requesting a new IBMGROUP be added to one of their profiles or new profile created. Management approval is
required.

Once that is completed, the requestor submits an email with the form “IRNDB2/NATURAL/INQUIRE INTERNAL
PRODUCT AUTHORIZATION FORM” attached to it and copies their manager. DBAs process the request (grant
access to the IBMGROUP) and reply all to the email. Manager approval is implied since they are copied on the
request.

The reply email (with embedded form) is saved in WebTop folder “gdmsprd:IS/Global Infrastructure/GDS/Team
Folders/Database Services/Team Folders/Database Shared Services/DB2/IBMGROUPs –2013 (use correct year
folder). This is documentation for the auditors.

Page 58 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Sample name in WebTop –

T5710GC (S710UT) 31-Jan-2013 email/document.msg

Sample form, see Appendix B

SYSA – follow the pattern for existing access

10.2 SYSA-Schering Plough LPAR

SYSA has its own security product (Top-Secret), which maintains the user credentials and resource access. For RY
and WP, Top Secret maintains common profiles across the LPARs. It replicates the access between WP and RY, so
it keeps the user profiles and access in sync.

The database standards, application list and their contacts and related documents are in the SYSA folder of WebTop.
Gdmsprd:cabinet/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations/SYSA.

10.3 Strong DB2 Passwords

26-02-03 – Authentication Functional Policy is enforced for all IS personnel accounts on all DB2 databases
administered by Database Services that are currently within scope for Sarbanes-Oxley compliance.

The following are the DB2 password standards that will be enforced programmatically via a standard set of code
that will be deployed to all DB2 databases at Merck.

 The password must be different than the username.

 The length of the password must be at least 8 characters.
 The password must contain at least one alpha and one numeric character.
 The password must contain no more than two identical consecutive characters.

10.4 DB2 Account Administration

ITSOP-0014 establishes a disciplined process for fulfilling access requests for applications and systems within the
Merck IT environment.

The procedures to support Database account administration are as follows:

 ITSOP-0014 - Account and Access Management for IRM&C Supported Applications and Systems
 SDLC-SOP-05-08: Global Services (GS) Service Request Fulfilment

10.5 DB2 Account Validation Scripts

DB2 accounts that have privileged access will be reviewed annually, at a minimum, as outlined in ITSOP-0014.
The annual account validation process encompasses the compilation and review of account privileges and
permissions via verification reporting and auditing methods.

The DB2 accounts to be reviewed are as follows:

Page 59 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

DB2 Roles System Privileges Table (Object)

Privileges
SYSADM %ANY% Tables (objects)
owned by SYS
and SYSTEM
SYSOPR

11 DB2 Operational Activities

11.1 Periodic manual Activities
1. Monthly FIRS tablespace C5769058 reorg.
2. Monthly SOAP audit report.
3. Quarterly FACTS D9 runstats.
4. Annual CCAS Chargeback Aarchive, second quarter.
5. Annual FACTS reorg, first quarter
6. Product password renew,
SOFTBASE, annual
QW, quarterly
11.2 Daily Activities
1. Checking D*MSTR, see if there is any error message of space shortage, or frequent locking.
2. Review Job completion emails for any abends.
3. Check database underlying dataset space usage and extents to avoid extension failure.
4. Check overflow (spill) packs, so that they are less than 50% full to provide capacity for unplanned growth of data.
5. Check the database status.
a. Any outage of Production jobs, the Batch monitoring/Operations team will notify the DBA as per the
names mentioned in the on-call list.

11.3 Database Objects Creation and Migration

For FACTS Application: The database architect sends the data model (using Erwin) based on the application
requests. Once received, the DBA will generate DDL with the required amount of storage based on the cardinality
specified in the change request and create data objects in the Dev environment. Once DB2 objects are created, they
will be compared against the Erwin model to find out any discrepancy between the two (e.g. synchronize index and
foreign key names). Dev 2 (T5723D2) is normally the starting database for test FACTS.
The Data Architecture will send back for confirmation of the model built. After the DA agreed, the implementation
date will be provided to the DBA via a Work Order.

RY/WP
These DDL’s are placed under “MSD.DBM.XXXXX.DB2DDL.CNTL” where XXXXX represents the application
database name.
Examples of test:

Page 60 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

FACS
MSD.DBM.T5723.D1.DB2DDL.CNTL
MSD.DBM.T5723.D2.DB2DDL.CNTL
MSD.DBM.T5723.D3.DB2DDL.CNTL
MSD.DBM.T5723.D4.DB2DDL.CNTL
MSD.DBM.T5723.D5.DB2DDL.CNTL
MSD.DBM.T5723.D6.DB2DDL.CNTL
MSD.DBM.T5723.D8.DB2DDL.CNTL
MSD.DBM.T5723.D9.DB2DDL.CNTL
MSD.DBM.T5723.LI.DB2DDL.CNTL
MSD.DBM.T5723.PS.DB2DDL.CNTL
MSD.DBM.T5723.QA.DB2DDL.CNTL
MSD.DBM.T5723.ST.DB2DDL.CNTL

CCAS
MSD.DBM.T5710.DB2DDL.CNTL
MSD.DBM.T5710.GC.DB2DDL.CNTL
MSD.DBM.T5710.G2.DB2DDL.CNTL
MSD.DBM.T5710.G3.DB2DDL.CNTL
MSD.DBM.T5710.QA.DB2DDL.CNTL
MSD.DBM.T5710.TR.DB2DDL.CNTL

SYS A
SDIS.DBM.P.DBAFLD.DB2DDL.CNTL
SDIS.DBM.P.FRS.DB2DDL.CNTL
SDIS.DBM.P.MCR.DB2DDL.CNTL
SDIS.DBM.T.DBAFLD.DB2DDL.CNTL
SDIS.DBM.T.FRS.DB2DDL.CNTL
SDIS.DBM.T.HCP.DB2DDL.CNTL
SDIS.DBM.T.MCR.DB2DDL.CNTL
SDIS.DBM.T.PDBT08.DB2DDL.CNTL
SDIS.DBM.T.PRM.DB2DDL.CNTL

For further migrations from Dev to UAT to QA to PROD, the Data Architect will forward the data model to the
DBA, who in turn will create the database objects based on the DEV environment.

For other Applications like CCAS, FIRS, etc.: All procedures are the same as the FACTS application. But for
migrations, the DBA has to send the data model to the application team and data architect for approval. Once
approved, the same process will be followed like FACTS.

11.4 Decommission/Retirement
There is no official decommissioning schedule or process; therefore it will be addressed at a time a
decommissioning strategy is defined.

11.4.1 Change management

1. Application requests to decommission the DB2 related components via a WO under an existing CFR
2. Create WO for Mainframe PSA to remove the started tasks, and system parms
3. Save all the source code, original configurations and results

Page 61 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

11.4.2 Decommission CDC off FACTS @RY

RYTSO test
1. Stop backup these databases
2. stop scheduling (startup/shutdown during IPL) and monitoring the following started tasks.

DATMIRD6
DATMIRD8
DATMIRST
DATMIRQA
DATMIRD3

3. Remove the following from SYS1.PARMLIB(PROG00):

APF ADD DSNAME(SOFT.DATAMIRR.T.LOAD) SMS

APF ADD DSNAME(SOFT.DATAMIRR.T.QA.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.DS.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.DS.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.QA.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D3.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D6.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D3.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D6.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.V520.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.V520.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.V530.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.V530.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.EXIT.LOAD) SMS
APF ADD DSNAME(SOFT.DATAMIRR.T.D8.V620.LOAD) SMS
4. Stop test databases DATMIR*, RPM*
5.Drop test databases DTAMIR*, RPM*
Production
1. stop scheduling (startup/shutdown during IPL) and monitoring the following started task.
DATMIRPR

2. Stop scheduling jobs U5723AE, U5723CA(RPMON)

3. Remove the following from SYS1.PARMLIB(PROG00)
APF ADD DSNAME(SOFT.DATAMIRR.P.LOAD) SMS

Page 62 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

APF ADD DSNAME(SOFT.DATAMIRR.P.EXIT.LOAD)

4. Stop databases DATMIR*, RPM* for 4 week s

5. Drop databases DATMIR*, RPM* (05/14/2014)
6. Remove the following entries from SOFT.TCPIP.P.ETC.SERVICES:
repsrvnme 4000/tcp repsrvnme # datamirror trans srv
admsrvnme 4002/tcp admsrvnme # datamirror admin
admsrvnme 4002/udp admsrvnme # datamirror admin
repsrvnmp 4004/tcp repsrvnmp # datamirror trans srv
admsrvnmp 4006/tcp admsrvnmp # datamirror admin
admsrvnmp 4006/udp admsrvnmp # datamirror admin
repsrvnm3 4008/tcp repsrvnm3 # datamirror trans srv
admsrvnm3 4010/tcp admsrvnm3 # datamirror admin
admsrvnm3 4010/udp admsrvnm3 # datamirror admin
repsrvnm6 4012/tcp repsrvnm6 # datamirror trans srv
admsrvnm6 4014/tcp admsrvnm6 # datamirror admin
admsrvnm6 4014/udp admsrvnm6 # datamirror admin
repsrvnms 4016/tcp repsrvnms # datamirror trans srv
admsrvnms 4018/tcp admsrvnms # datamirror admin
admsrvnms 4018/udp admsrvnms # datamirror admin
repsrvnmq 4020/tcp repsrvnmq # datamirror trans srv
admsrvnmq 4022/tcp admsrvnmq # datamirror admin
admsrvnmq 4022/udp admsrvnmq # datamirror admin
datmird8 4102/tcp datmird8 # datamirror v5 srv
datmird8 4102/udp datmird8 # datamirror v5 srv
datmirpr 4106/tcp datmirpr # datamirror v5 srv
datmirpr 4106/udp datmirpr # datamirror v5 srv
datmird3 4110/tcp datmird3 # datamirror v5 srv
datmird3 4110/udp datmird3 # datamirror v5 srv
datmird6 4114/tcp datmird6 # datamirror v5 srv
datmird6 4114/udp datmird6 # datamirror v5 srv
datmirst 4118/tcp datmirst # datamirror v5 srv
datmirst 4118/udp datmirst # datamirror v5 srv
datmirqa 4122/tcp datmirqa # datamirror v5 srv
datmirqa 4122/udp datmirqa # datamirror v5 srv

7. Disable all those traps/recoveries once Start/Stop DATMIRPR on IPL stopped.

Several monitoring and recovery traps for DATAMIR* tasks on RYTSO;
they range from daily recycles to email monitoring solutions. Removing the task
DATMIRPR, would mean no more DATMIR* resources are active on the system.

After Start/Stop DATMIRPR on IPL stopped, the message traps will be no longer valid.
The traps are inside dataset SYS1.OPS.P.DATAMIR.RULES, and only include traps that
are relevant to DATAMIR messages (TSD*) and appropriate timed calls.

11.4.3 Decommission IMPACT @WPTSO

WPTSO test
WO0000000897545 Related to CRQ000000089839 was created to IMPACT System Retirement.
Decommission DB2 objects related to the TEST WP IMPACT system for the following test
databases:
T5227D is associated with test region T4

Page 63 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

T5227L is associated with test region T2

T5227LXC is associated test region T2 exception tables

T5227R is the test replication database

The databases at WPTSO test, were stopped on 4/7/2014,

The DDLs of the T5227* are saved in following dataset/members

DB2DBA.DDL.ARCHIVE(C5227DLX)
DB2DBA.DDL.ARCHIVE(C5227RXY)
DB2DBA.DDL.ARCHIVE(C5227TXC)

11.5 Backup and Recovery

Backup and recovery refers to the various strategies and procedures involved in protecting a database against data
loss and reconstructing the database after any kind of data loss. A well-designed backup and recovery strategy
maximizes data availability and minimizes data loss, while considering particular Merck business requirements.

11.5.1 DB2 Backup

Full image copies are taken daily for the DB2 Subsystem Catalog and Directory tablespaces. The image copy cycle
starts at 04:30 AM. The JCL is located in:

Start
SOFT.OPER.P.JCLLIB(C0134D02) – WP Production DB2
SOFT.OPER.P.JCLLIB(C0134D01) – WP Test DB2

SOFT.OPER.P.JCLLIB(C9900DBP) – RY Production DB2

SOFT.OPER.P.JCLLIB(C9900DBT) – RY Test DB2

Applications like FACTS, CCAS, CIMS, PHUM etc., have their own backup cycle which can be found in WebTop
(Documentum).

WP/RY application jobs are located in SOFT.OPER.P.APJCL

SYSA application jobs are located in SYS3.JOBTRAC.NJ.JCLLIB

Page 64 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

11.5.2 OFFLINE Backup

All physical volumes are backed up regularly over the weekend by the System Programmers. These tasks are carried
out by IBM.
Some applications also have offsite image copies
WP/RY include ‘.V.’ in data set name
SYS A defines ICBACKUP of ‘RP’

11.5.3 Restoration
Requests to restore tablespaces should be received from a Remedy ticket. For emergency Production requests, an
Email is acceptable to begin the restore, but a Remedy ticket must still be submitted. The restoration request will be
either to an image copy or a point of recovery. Change Control procedures must be followed.
 DI-SOP-00008 DB2 Recovery SOP
Tablespace Recovery section

11.5.4 Application Refresh

The backup created by IBM utility in production is used to refresh test schema. Data is unloaded from the backup,
then load into test. Before refreshing, verify the structure, allocation and partition key are in sync with those in
production.

There is a pair JCL created, one is to unload data at source subsystem and another is to load at target subsystem.
JCLs to unload/load data, e.g.

MSD.DBM.C5769.DB2UTIL.JCL(UNLDDBT), unloading FIRS data from production

MSD.DBM.T5769.DB2UTIL.JCL(LOADDB), loading FIRS data to test, based on the load control cards generated
during unload step.

The procedures to support Database Restore /Recovery using BRTOOLS are as follows:
 ITSOP-0011: System Administration and Use of Enterprise Backup and Recovery
Systems

12 Scheduled Activities
12.1 Weekly/Monthly/Quarterly Procedures
For certain applications, weekly, monthly and quarterly batch jobs are scheduled to do image copy, reorganization,
etc. Details are in WebTop.

For FACTS Application, the Daily, Weekly, and Monthly Schedulers are in:
Gdmsprd:cabinet/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations

For other applications, named UxxxxJobFlow_Master and special CCAS reorganizations are also documented.
Where xxxx refers the application name.
CCAS_Chargeback_Archive - Chargeback archiving data annually to relieve space usage

Page 65 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

All the Scheduled utilities are documented in Section 20.

For the FIRS application: There is a special procedure that is followed. The FIRS Special Monthly Maintenance
process is found in the below location:
gdmsprd: Schnaubelt, Tom/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database
Shared Services/DB2/

13 Impact
This is the MRPII application used by the Merck Manufacturing division at the West Point facility. There are
separate procedure needs to be followed for recovering the production database (P4) to a quiesce point after
production jobs have abended during the nightly cycle. Procedure details document is IMPACT-MMS-MAN-003-
DB-REC-ABND, see Appendix C.

It is expected that IMPACT will go to full Read-Only mode in the next month and subsequently the procedure will
go away.

14 Disaster Recovery / BCP

Disaster Recovery (DR) drills is conducted once per year. The preparation will start a month in advance and will
notify the participating application owners.

The DR plans and Work Instructions are located at both WebTop and Shared Drive.
WebTop: Gdmsprd:cabinet/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database
Shared Services/DB2/Operations/L5-Plan Dr DB2 Subsystes.doc

Shared Drive: \\WSSHARED:\IS\IT Service Continuity\Disaster Recovery (CTC, WHS)\DR PLANS\L5-PLAN IT

DR DB & Application Recovery Team\CLASS B & C\ETAS\DB2

14.1 Rahway /WestPoint

The connection and IP address to Rahway and WestPoint DR site is RDIBM and WDIBM.

The DR procedure for the RY or WP LPAR is documented in the following dataset:

Within a month of the planned disaster recovery exercise, execute following process at both WPTSO and RYTSO.
DB2DBA.DB2.BENCHMRK.CNTL($DOCPROD)

West Point
THIS MEMBER DOCUMENTS THE FOLLOWING TESTING PROCEDURES:

A) WEST POINT TEST (DB2P) BATCH

B) WEST POINT TEST (DB2P) ONLINE

***********************************************************************
THE NAMING CONVENTIONS FOR THE PDS MEMBER NAMES ARE AS FOLLOWS:
Page 66 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

1ST CHARACTER = LOCATION EX. R = RAHWAY

W = WEST POINT
2ND CHARACTER = SUBSYSTEM EX. D = DEVELOPMENT
T = TEST
P = PRODUCTION
3RD + 4TH = FUNCTION BEING TESTED EX. CR = CREATE
LD = LOAD
SE = SELECT
RE = REORG
IC = IMAGE COPY
GR = GRANT
5TH, 6TH 7TH = VENDOR EX. IBM
CA
DBA
SAS
8TH = SEQUENCE NUMBER OF SIMILAR MEMBERS

***********************************************************************

TESTDBA USERID REFERS TO: TESTD1 = CHIALI

TESTD2 = SURESH
TESTD3 = JIM / EKT

***********************************************************************
*************** A) WEST POINT PROD DB2P BATCH ***************
***********************************************************************

A.1) SUBMIT 'WPCRIBM1' TO (USING SYSADM USERID)

A) CREATE A DATABASE CALLED TESTDBA
B) GRANT DB LEVEL AUTH (LOADDB, STARTDB, ETC.) TO SECONDARY AUTHID
C) CREATE A PARTITIONED TABLESPACE CALLED TESTTS IN TESTDBA
D) CREATE A TABLE CALLED EMP IN TESTTS
E) CREATE A UNIQUE INDEX CALLED XEMP1 ON EMP
F) CREATE ANOTHER INDEX (NON-UNIQUE)CALLED XEMP2 ON EMP
G) CREATE A VIEW CALLED VEMP ON EMP
H) CREATE ANOTHER TABLESPACE CALLED USERTABS IN TESTDBA
I) CREATE ANOTHER TABLE CALLED PLAN_TABLE IN USERTABS
FOR EACH TEST ID
J) CREATE ANOTHER TABLE CALLED DEPT IN USERTABS
K) CREATE A UNIQUE INDEX CALLED XDEPT1 ON DEPT
L) GRANT SEL,DEL,INS,UPD WITH GRANT ON DEPT & EMP TO SECONDARY
AUTHIDS AND TEST IDS

A.2) SUBMIT 'WPIBM1' TO (USING TESTDBA USERID)

A) LOAD DATA INTO TABLE TESTDBA.EMP USING IBM'S UTILITY.
B) REORGANIZE TABLE TESTDBA.EMP USING IBM'S UTILITY.
C) IMAGE COPY TABLE TESTDBA.EMP USING IBM'S UTILITY.
D) UNLOAD TABLE TESTDBA.EMP USING IBM'S DSNTIAUL SAMPLE PROGRAM.
E) READ DATA IN TABLE TESTDBA.EMP USING IBM'S DSNTEP2 SAMPLE
PROGRAM.
F) GRANT/REVOKE SELECT AUTHORITY ON TABLE TESTDBA.EMP TO "TEST01"

Page 67 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

USING IBM'S DSNTIAD SAMPLE PROGRAM.

A.3) STEP REMOVED -- CA FAST LOAD NO LONGER INSTALLED

A.4) SUBMIT 'WPDBA1' TO (USING TESTDBA USERID)

A) READ DATA IN TABLE TESTDBA.EMP USING DATABASE ATTACH'S
VERSION OF IBM'S DSNTEP2 SAMPLE PROGRAM.
B) UNLOAD TABLE TESTDBA.EMP USING DATABASE ATTACH'S VERSION OF
IBM'S DSNTIAUL SAMPLE PROGRAM.
C) GRANT/REVOKE SELECT AUTHORITY ON TABLE TESTDBA.EMP TO "TESTDBA
USERID" USING DATABASE ATTACH'S VERSION OF IBM'S DSNTIAD SAMPLE
PROGRAM.

A.5) SUBMIT 'WPDCGEN1' TO (USING SYSADM USERID)

A) GENERATE A TABLES DECLARATION FOR A COBOL PROGRAM.
B) GENERATE A TABLES DECLARATION FOR A 'C' PROGRAM.

A.6) SUBMIT 'WPCOPRG1' TO (USING SYSADM USERID)

A) PRE-COMPILE, COMPILE, LINK, & BIND A COBOL PROGRAM USING PROC
TBCB3DB2.
B) GRANT EXECUTE ON PLAN TESTDBA TO IBMGROUP TESTDBAT SO
SECONDARY AUTHID'S CAN BE TESTED.

A.7) SUBMIT 'WPCOPRG2' TO (USING SYSADM USERID)

EXECUTE THE COBOL PROGRAM COMPILED ABOVE.

A.8) SUBMIT 'WPCCPRG1' TO (USING SYSADM USERID)

A) PRE-COMPILE, COMPILE, PRE-LINK, LINK, & BIND A C PROGRAM
USING PROC TBEDCDB2.
B) GRANT EXECUTE ON PLAN TESTDBAC TO IBMGROUP TESTDBAT SO
SECONDARY AUTHID'S CAN BE TESTED.

A.9) SUBMIT 'WPCCPRG2' TO (USING TESTDBA USERID)

EXECUTE THE C PROGRAM COMPILED ABOVE. PLEASE NOTE THAT THE
OUTPUT SHOULD BE THE SAME AS A.7) ABOVE.

A.10) SUBMIT 'WPCSP1' WITH PARM 'D21,S01' TO (USING TESTDBA USERID)

CALL (HARD-CODED CALL) COBOL STORED PROCEDURE THAT
USES PARAMETERS ONLY -- NO RESULT SET. VERIFY "EMPLOYEES
FOR DEPT NMBR: D21 - ADMINISTRATION SYSTEMS" IS PRODUCED.

A.11) SUBMIT 'WPCSP1' WITH PARM 'D21,S03' TO (USING TESTDBA USERID)

CALL (HARD-CODED CALL) 'C' STORED PROCEDURE THAT USES
PARAMETERS AND RETURNS A RESULT SET. VERIFY "EMPLOYEES FOR
DEPT NMBR: D21 - ADMINISTRATION SYSTEMS" IS PRODUCED
ALONG WITH A LIST OF EMPLOYEES IN THAT DEPT.

A.12) SUBMIT 'WPCSP2' WITH PARM 'C01,S02' TO (USING TESTDBA USERID)

CALL (HOST-VARIABLE CALL) COBOL STORED PROCEDURE THAT USES
PARAMETERS AND RETURNS A RESULT SET. VERIFY "EMPLOYEES FOR
DEPT NMBR: C01 - INFORMATION CENTER" IS PRODUCED ALONG WITH
A LIST OF EMPLOYEES IN THAT DEPT.

Page 68 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

A.13) SUBMIT 'WPSESAS1' TO (USING TESTDBA USERID)

READ DATA IN TABLE TESTDBA.EMP USING SAS SAMPLE PROGRAM

A.14) SUBMIT 'WPCLEAN ' TO (USING TESTDBA USERID)

TO DELETE THE FLAT FILES CREATED ABOVE

A.15) SUBMIT 'WPCLEAN' TO (USING SYSADM USERID)

A) DROP DATABASE TESTDBA
B) FREE PLANS CREATED ABOVE

***********************************************************************
*************** B) WEST POINT PROD DB2P ONLINE **************
*************** (TSO LOGON PROC PRODDB2) **************
***********************************************************************

B.1) EXECUTE 'WPCRIBM2' USING SPUFI TO (USING SYSADM USERID)

A) CREATE A DATABASE CALLED TESTDBA
B) CREATE A PARTITIONED TABLESPACE CALLED TESTTS IN TESTDBA
C) CREATE A TABLE CALLED EMP IN TESTTS
D) CREATE A UNIQUE INDEX CALLED XEMP1 ON EMP
E) CREATE ANOTHER UNIQUE INDEX CALLED XEMP2 ON EMP
F) CREATE A VIEW CALLED VEMP ON EMP
G) CREATE ANOTHER TABLESPACE CALLED USERTABS IN TESTDBA
H) CREATE ANOTHER TABLE CALLED PLAN_TABLE IN USERTABS
I) GRANT SEL,DEL,INS,UPD ON DEPT & EMP TO SECONDARY
AUTHID
J) GRANT SELECT ON EMP TABLE TO TEST01
K) REVOKE SELECT ON EMP TABLE FROM TEST01

*** NOTE: MAKE SURE THE SSID IS CORRECT AND CAN'T BE CHANGED.

B.2) SUBMIT 'WPLDIBM1' TO (USING TESTDBA USERID)

LOAD DATA INTO TABLE TESTDBA.EMP TO PREPARE FOR TESTING VIA
SPUFI.

B.3) EXECUTE 'WPSEIBM1' USING SPUFI TO (USING TESTDBA USERID)

SELECT ROWS FROM TABLE TESTDBA.EMP USING IBM'S UTILITY.

B.4) EXECUTE 'WPSEIBM2' USING SPUFI TO (USING TESTDBA USERID)

SELECT ROWS FROM VARIOUS CATALOG TABLES. REVIEW THE RESULTS
AS PER THE COMMENTS SUPPLIED IN THE QUERY.

B.5) VIA THE IBM COMMAND INTERFACE ISSUE (USING TESTDBA USERID)
A) -DIS THREAD(*) DISPLAY THREADS
B) -DIS UTIL(*) DISPLAY UTILITIES
C) -DIS TRACE(*) DISPLAY TRACES

B.6) USING QMF ISSUE (USING TESTDBA USERID)

A) SELECT * FROM TESTDBA.EMP
B) SELECT * FROM RAHWAY_PROD.SYSIBM.SYSTABLES
WHERE NAME LIKE 'CUST%'

Page 69 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

(VERIFY THAT DDF IS WORKING)

B.7) VIA CA COMMAND INTERFACE (D.3 OPTION C) (USING TESTDBA USERID)

-DIS CA UTIL(*)

B.8) VIA CA INTERACTIVE SQL (D.3 OPTION I) (USING TESTDBA USERID)

SELECT * FROM SYSIBM.SYSDATABASE
(OPTION E ALLOWS INPUT OF SQL
OPTION S RUNS SQL)

B.9) LOGON WPCICSP; CRTE SYSID=WPP3; CESN; (USING SYSADM USERID)

ISSUE THE FOLLOWING COMMANDS:
A) DSNC DISP STAT
B) DSNC -DISPLAY THREAD(*)
CANCEL; CESF LOGOFF

B.10) EXECUTE 'WPDRIBM1' USING SPUFI TO (USING SYSADM ID)

DROP DATABASE TESTDBA

RAHWAY
THIS MEMBER DOCUMENTS THE FOLLOWING TESTING PROCEDURES:

A) RAHWAY PROD (DB2P) BATCH

B) RAHWAY PROD (DB2P) ONLINE

***********************************************************************
THE NAMING CONVENTIONS FOR THE PDS MEMBER NAMES ARE AS FOLLOWS:

1ST CHARACTER = LOCATION EX. R = RAHWAY

W = WEST POINT
2ND CHARACTER = SUBSYSTEM EX. D = DEVELOPMENT
T = TEST
P = PRODUCTION
3RD + 4TH = FUNCTION BEING TESTED EX. CR = CREATE
LD = LOAD
SE = SELECT
RE = REORG
IC = IMAGE COPY
GR = GRANT
5TH, 6TH 7TH = VENDOR EX. IBM
CA
DBA
SAS
8TH = SEQUENCE NUMBER OF SIMILAR MEMBERS

***********************************************************************

TESTDBA USERID REFERS TO: TESTD1 = CHIALI

TESTD2 = SURESH
TESTD3 = JIM / EKT

Page 70 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

***********************************************************************
*************** A) RAHWAY PROD DB2P BATCH ***************
***********************************************************************

A.1) SUBMIT 'RPCRIBM1' TO (USING SYSADM USERID)

A) CREATE A DATABASE CALLED TESTDBA
B) GRANT DB LEVEL AUTH (LOADDB, STARTDB, ETC.) TO SECONDARY AUTHID
C) CREATE A PARTITIONED TABLESPACE CALLED TESTTS IN TESTDBA
D) CREATE A TABLE CALLED EMP IN TESTTS
E) CREATE A UNIQUE INDEX CALLED XEMP1 ON EMP
F) CREATE ANOTHER INDEX (NON-UNIQUE)CALLED XEMP2 ON EMP
G) CREATE A VIEW CALLED VEMP ON EMP
H) CREATE ANOTHER TABLESPACE CALLED USERTABS IN TESTDBA
I) CREATE ANOTHER TABLE CALLED PLAN_TABLE IN USERTABS
FOR EACH TEST ID
J) CREATE ANOTHER TABLE CALLED DEPT IN USERTABS
K) CREATE A UNIQUE INDEX CALLED XDEPT1 ON DEPT
L) GRANT SEL,DEL,INS,UPD WITH GRANT ON DEPT & EMP TO SECONDARY
AUTHIDS AND TEST IDS

A.2) SUBMIT 'RPIBM1' TO (USING TESTDBA USERID)

A) LOAD DATA INTO TABLE TESTDBA.EMP USING IBM'S UTILITY.
B) REORGANIZE TABLE TESTDBA.EMP USING IBM'S UTILITY.
C) IMAGE COPY TABLE TESTDBA.EMP USING IBM'S UTILITY.
D) UNLOAD TABLE TESTDBA.EMP USING IBM'S DSNTIAUL SAMPLE PROGRAM.
E) READ DATA IN TABLE TESTDBA.EMP USING IBM'S DSNTEP2 SAMPLE
PROGRAM.
F) GRANT/REVOKE SELECT AUTHORITY ON TABLE TESTDBA.EMP TO "TEST01"
USING IBM'S DSNTIAD SAMPLE PROGRAM.

A.3) STEP REMOVED -- CA FAST LOAD NO LONGER INSTALLED

A.4) SUBMIT 'RPDBA1' TO (USING TESTDBA USERID)

A) READ DATA IN TABLE TESTDBA.EMP USING DATABASE ATTACH'S
VERSION OF IBM'S DSNTEP2 SAMPLE PROGRAM.
B) UNLOAD TABLE TESTDBA.EMP USING DATABASE ATTACH'S VERSION OF
IBM'S DSNTIAUL SAMPLE PROGRAM.
C) GRANT/REVOKE SELECT AUTHORITY ON TABLE TESTDBA.EMP TO "TESTDBA
USERID" USING DATABASE ATTACH'S VERSION OF IBM'S DSNTIAD SAMPLE
PROGRAM.

A.5) SUBMIT 'RPDCGEN1' TO (USING SYSADM USERID)

A) GENERATE A TABLES DECLARATION FOR A COBOL PROGRAM.
B) GENERATE A TABLES DECLARATION FOR A 'C' PROGRAM.

A.6) SUBMIT 'RPCOPRG1' TO (USING SYSADM USERID)

A) PRE-COMPILE, COMPILE, LINK, & BIND A COBOL PROGRAM USING PROC
TBCB3DB2.
B) GRANT EXECUTE ON PLAN TESTDBA TO IBMGROUP TESTDBAT SO
SECONDARY AUTHID'S CAN BE TESTED.

A.7) SUBMIT 'RPCOPRG2' TO (USING TESTDBA USERID)

Page 71 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

EXECUTE THE COBOL PROGRAM COMPILED ABOVE.

A.8) SUBMIT 'RPCCPRG1' TO (USING SYSADM USERID)

A) PRE-COMPILE, COMPILE, PRE-LINK, LINK, & BIND A C PROGRAM
USING PROC TBEDCDB2.
B) GRANT EXECUTE ON PLAN TESTDBAC TO IBMGROUP TESTDBAT SO
SECONDARY AUTHID'S CAN BE TESTED.

A.9) SUBMIT 'RPCCPRG2' TO (USING TESTDBA USERID)

EXECUTE THE C PROGRAM COMPILED ABOVE. PLEASE NOTE THAT THE
OUTPUT SHOULD BE THE SAME AS A.7) ABOVE.

A.10) SUBMIT 'RPCSP1' WITH PARM 'D21,S01' TO (USING TESTDBA USERID)

CALL (HARD-CODED CALL) COBOL STORED PROCEDURE THAT
USES PARAMETERS ONLY -- NO RESULT SET. VERIFY "EMPLOYEES
FOR DEPT NMBR: D21 - ADMINISTRATION SYSTEMS" IS PRODUCED.

A.11) SUBMIT 'RPCSP1' WITH PARM 'D21,S03' TO (USING TESTDBA USERID)

CALL (HARD-CODED CALL) 'C' STORED PROCEDURE THAT USES
PARAMETERS AND RETURNS A RESULT SET. VERIFY "EMPLOYEES FOR
DEPT NMBR: D21 - ADMINISTRATION SYSTEMS" IS PRODUCED
ALONG WITH A LIST OF EMPLOYEES IN THAT DEPT.

A.12) SUBMIT 'RPCSP2' WITH PARM 'C01,S02' TO (USING TESTDBA USERID)

CALL (HOST-VARIABLE CALL) COBOL STORED PROCEDURE THAT USES
PARAMETERS AND RETURNS A RESULT SET. VERIFY "EMPLOYEES FOR
DEPT NMBR: C01 - INFORMATION CENTER" IS PRODUCED ALONG WITH
A LIST OF EMPLOYEES IN THAT DEPT.

A.13) SUBMIT 'RPSESAS1' TO (USING TESTDBA USERID)

READ DATA IN TABLE TESTDBA.EMP USING SAS SAMPLE PROGRAM

A.14) SUBMIT 'RPCLEAN1' TO (USING TESTDBA USERID)

TO DELETE THE FLAT FILES CREATED ABOVE

A.15) SUBMIT 'RPCLEAN' TO (USING SYSADM USERID)

A) DROP DATABASE TESTDBA
B) FREE PLANS CREATED ABOVE

***********************************************************************
*************** B) RAHWAY PROD DB2P ONLINE **************
*************** (TSO LOGON PROC PRODDB2) **************
***********************************************************************

B.1) EXECUTE 'RPCRIBM2' USING SPUFI TO (USING SYSADM USERID)

A) CREATE A DATABASE CALLED TESTDBA
B) CREATE A PARTITIONED TABLESPACE CALLED TESTTS IN TESTDBA
C) CREATE A TABLE CALLED EMP IN TESTTS
D) CREATE A UNIQUE INDEX CALLED XEMP1 ON EMP
E) CREATE ANOTHER UNIQUE INDEX CALLED XEMP2 ON EMP
F) CREATE A VIEW CALLED VEMP ON EMP
G) CREATE ANOTHER TABLESPACE CALLED USERTABS IN TESTDBA

Page 72 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

H) CREATE ANOTHER TABLE CALLED PLAN_TABLE IN USERTABS

I) GRANT SEL,DEL,INS,UPD ON DEPT & EMP TO SECONDARY
AUTHID
J) GRANT SELECT ON EMP TABLE TO TEST01
K) REVOKE SELECT ON EMP TABLE FROM TEST01

*** NOTE: MAKE SURE THE SSID IS CORRECT AND CAN'T BE CHANGED.

B.2) SUBMIT 'RPLDIBM1' TO (USING TESTDBA USERID)

LOAD DATA INTO TABLE TESTDBA.EMP TO PREPARE FOR TESTING VIA
SPUFI.

B.3) EXECUTE 'RPSEIBM1' USING SPUFI TO (USING TESTDBA USERID)

SELECT ROWS FROM TABLE TESTDBA.EMP USING IBM'S UTILITY.

B.4) EXECUTE 'RPSEIBM2' USING SPUFI TO (USING TESTDBA USERID)

SELECT ROWS FROM VARIOUS CATALOG TABLES. REVIEW THE RESULTS
AS PER THE COMMENTS SUPPLIED IN THE QUERY.

B.5) VIA THE IBM COMMAND INTERFACE ISSUE (USING TESTDBA USERID)
A) -DIS THREAD(*) DISPLAY THREADS
B) -DIS UTIL(*) DISPLAY UTILITIES
C) -DIS TRACE(*) DISPLAY TRACES

B.6) USING QMF ISSUE (USING TESTDBA USERID)

A) SELECT * FROM TESTDBA.EMP
B) SELECT * FROM WESTPOINT_PROD.SYSIBM.SYSTABLES
WHERE NAME LIKE 'CUST%'
(VERIFY THAT DDF IS WORKING)

B.7) VIA CA COMMAND INTERFACE (D.3 OPTION C) (USING TESTDBA USERID)

-DIS CA UTIL(*)

B.8) VIA CA INTERACTIVE SQL (D.3 OPTION I) (USING TESTDBA USERID)

SELECT * FROM SYSIBM.SYSDATABASE
(OPTION E ALLOWS INPUT OF SQL
OPTION S RUNS SQL)

B.9) LOGON RYCICSP; CRTE SYSID=RYP1; CESN; (USING SYSADM USERID)

ISSUE THE FOLLOWING COMMANDS:
A) DSNC DISP STAT
B) DSNC -DISPLAY THREAD(*)
CANCEL; CESF LOGOFF

B.10) EXECUTE 'RPDRIBM1' USING SPUFI TO (USING SYSADM ID)

DROP DATABASE TESTDBA

14.2 SYSA (Schering Plough)

The DR procedure is documented in WebTop in the SYSA folder.
gdmsprd : IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared

Page 73 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Services/DB2/Operations/SYSA/DR_Drill

The connection or IP address to Schering Plough DR site is 172.30.59.37.

15 Auditing
This will allow all Production DB2 databases within scope of Sarbanes-Oxley managed by Database Services to be
audited. This applies to all IS personnel accounts

15.1 DB2 Audit Configuration

This will allow the DBA to enable login/logoff auditing. The audit data will be maintained for a period of fifteen
(15) months.

1. Save updated critical data in database SOX, table CRITICAL_TBL_AUDIT for 15 months.
2. Save ACID with elevated privilege e.g. SYSADM and SYSOPR in ELVTD_PRIV_OWNER

15.2 DB2 Critical Table Auditing

At WP, Databases C5710 and C5738 are under Sarbanes-Oxley (Sox) control. Upon Auditor’s request, DBA
provides the following evidence, but is not limited to:
1. a user authorization list for the databases
2. elevate privilege ACIDs
3. access request
4. database change log

To generate the above audit report, logon with a special ACID – CRMT04 and logon proc DCA. The JCL is in
“CRMT04.JCL.CNTL(DBAA5710)” and “CRMT04.JCL.CNTL(DBAA5738)”. The detailed process is documented
in “DB2 Sox evidence gathering” found in WebTop:
Gdmsprd:cabinet/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/SOx

To be able to provide the audit report during an audit, the following requests or reports should be saved.
1. Any ACID access change or new addition request should be saved
2. Any elevated privilege change request should be saved
3. Daily database change log, any insert, update or delete change to the databases: CCAS (C5710) or Payment
Hub (C5738) should be reported to the application managers and DBA team. The reports should be saved.
4. Daily job logs should be archived, and saved in CA-DP for 475 days.
Job C0134AU is stored at DB2DBA.DB2.SOX.CNTL
Whenever the email recipient is requested to be changed, the email address in
MSD.DBM.C0134.SOX.CNTL(C0134AUC) is where to make the modification for CCAS (C5710).
MSD.DBM.C0134.SOX.CNTL(C0134AUE) is where to make the modification for PHUB (C5738).
MSD.DBM.C0134.SOX.CNTL(C0134AUG) is where to make the modification for IMPACT (C5727).

Page 74 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

The process document is kept in MSD.DBM.C0134.SOX.CNTL($C0134AU)

RY
CAPS – C2533 is under audit monitoring, the monthly job stored in MSD.DBM.C0134.SOX.CNTL(CAPSOX)
generates the report with of selected columns to show last update timestamp as evidence of no changes made to the
application.
Deliver the report along with Job Log to application.

SELECT ' ', NAME, CARD, CREATOR, OBID

, DATE(ALTEREDTS) AS ALTER_DT
, CREATEDBY
FROM SYSIBM.SYSTABLES
WHERE DBNAME = 'C2533'
AND TYPE = 'T'
ORDER BY ALTER_DT DESC, NAME
15.3 DB2 SOx account remediation
Infrastructure SOx Account Review

Request from SOx Audit group

Please find the Attached excel file. It contains the Results of the 2013 Infrastructure SOX Account reviews for DB2(C5710 and C5738).

The managers of the account owners have already requested the account deletion: no further authorization is required.

Mark the action taken for each account in the column "G" and if not deleted please mention in the Comments field why the account couldn't be
deleted.

Save and reattach the file to this remedy ticket when done.

This annual request is cleaning up the database access of listed ACIDs, not drop the ACIDs from mainframe.
To clean up the access, Mainframe Resource Authorization forms need to be filled out, with the ACID, Resource
type and Resource, which are attached to Remedy ticket, sent to ACCESS_ADMINISTRATON  INF_DATA to
process.

Page 75 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Resource type and Resource is generated by running job in CRMT04.JCL.CNTL, each complex has it’s respective
job setup, use the information in dataset , MSD.DBM.C0134.SOX.AUTH.C57*.OUT13.* to fill out the MRA form.
For 2014 Feb request, applications CCAS and PHUB are in scope, using following members to generate the report,
which is using the V suffix( it should be marked in the comments of the job). Verify the access has been removed,
the ACID won’t show up in the report. If any remain, you work with the assignee of Remedy ticket until verification
run is clean.
Get on WPTSO with CRMT04 procedure DCA,
Submit following jobs for CCAS or PHUB
CCAS - CRMT04.JCL.CNTL(DBAA5710)
PHUB - CRMT04.JCL.CNTL(DBAA5738)

Page 76 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

This report contains what profiles and/or IBMGROUPs caused ACID to show up on the report, the value is used to
fill out Resource column in Mainframe Resource Authorization form for the ACID.
On Mainframe Resource Authorization forms, the ACID is retrieved from the original excel spreadsheet, the
resource type and Resource are from report generated above, make sure the information are listed correctly, it might
have multiple forms to list all the ACID. Attach all the MRA forms to WO ticket, Assign to
ACCESS_ADMINISTRATON  INF_DATA . After A&A says they are done, you rerun the job that creates the
report using the V suffix, and verify that access has been removed. If any remain, repeat the process.
Turnaround time can be long, you may need to get on a list to be approved to send this directly to A&A instead of
through the Divisional Security Administrator because this is SOx process.

Notes:
Some ACIDs have access to more than one application, need to verify the ACIDs again with application.
Following ACIDs are not TSO ID but Process/Access ID, the owner might not stay at the application, but the ID
should not be revoked, could have application change the name via MRA form to transfer the name.

Page 77 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
 PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

ACID Application Ocntact person Email addr

ALGNETL Align ETL
CCAS Ranjith Pandian [email protected]
ALIGN Integration OPS [email protected]
PHUB Ranjith Pandian [email protected]
ALIGN Integration OPS [email protected]
TB5738 Align ETL PHUB Ranjith Pandian [email protected]
ALIGN Integration OPS [email protected]
MVDHQ1 Navigate ETL Teresa M Rooney [email protected]
Sasidharan Sengodan [email protected]

15.4 Sox audit process, (update Sox tables pre Sox audit process)
When Daylight savings time change, once in the Fall, another in Spring, the Sox Critical table Process needs to be
modified to reset the process time frame accordingly. The document is saved in
http://webtop.merck.com/webtop/component/main?__dmfClientId=1397047623249&__dmfRequestId=__client1
~~2&__dmfJumpType=jump

IS/Global Infrastructure/GDS/Team Folders/Database Services/team Folders/Database Shared Services/DB2/Sox

Sox Critical Table _ SYSADM Time adjustment Process, refer to section 15.2
DB2 Sox Critical Table/SYSADM Process Clearup

16 SLA Management
Below are the SLAs defined by Merck for resolving requests/incidents.

Incident Type Response Time Resolution Time

Critical 30 Minutes 4 Hours

High Priority 4 Hours 8 Hours

17 Database In-flight Projects

The DB2 product is frozen and it is out of support by the vendor. As per the database road map, the DB2 product
will be phased out by July 31, 2015.

There are planned revisions to the following applications (as of Sep 1, 2013). Refer to Section 20 for the release
schedule.
 CCAS
 FACTS
 FIRS

Page 78 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

18 Escalation Matrix
This team must be engaged for all the Major/ Critical Incidents (any unplanned disruption to an application, core
network outage, major infrastructure outage resulting in significant business impact, etc.) when the page is sent to
the on call technical team.

DB2 Contacts
Name Number Time Interval
Offshore Pager +1(979)092-6110
+1(950)000-4035
Vijay/Narayan 30
+1(/956)619-1392
Chiali Tsai +1(301)602-5824 45
Srini Damera +1(408)334-5555 60
Jim Fletcher +1(215)264-9345 90

Escalation Timelines: This timeline should be maintained for escalating to the next level if the previous level has not
acknowledged/ acted on the issue.

19 General DOs and DON’Ts

DOs:
 Get a Remedy ticket for all requests
 Get a Remedy ticket with Merck Manager Approval for DML or DDL tasks for all environments
 Get Merck Manager approval for Account Administration in the Production Environment
 Spool SQL output for all your DML activities
 Ensure to take backup prior to approved data deletion in all environments
 Make sure an RFC has been approved before making Production changes
 Ensure Application Manager Approval is obtained to grant access to non-standard IBMGROUPs in the Production
Databases.

DON’Ts:

 Don’t work on any request without a Remedy Case, unless it’s an emergency
 Don’t run any DML or DDL simultaneously in multiple environments
 Don’t perform any DML activity without a Merck Manager’s approval
 Don’t’ delete or truncate data from any table without manager approval (Production Environment)

Page 79 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

20 Training
MyLearning provide the list of required training based on the curriculum assigned to the individual’s role. HCL has
identified Non Merck Persons to play the myLearning Report Runner role across 3A Group. These individuals are
responsible to run myLearning reports & track course completions / overdue items.
Merck’s required training curriculum by role is maintain and updated by Merck Training Lead and is found at below
link:
IT Managed Services Partner Training Requirements

21 References
Reference Identification / Description Source / Location
SDLC-SOP-05-08: Global Services (GS) Service Request Fulfillment https://remedy-web.merck.com
SDLC-SOP-05-01: IT Incident Management https://sdlc.merck.com
SDLC-SOP-05-02: IT Problem Management https://sdlc.merck.com
SDLC-SOP-05-07: Administration and Control of Service Knowledge
https://sdlc.merck.com
Management Articles for Global Services (GS)
ITSM-SOP-GEN-000068 - GTS Configuration Management Process http://edms.merck.com
ITSOP-0006 - Qualification of Infrastructure Systems and Components http://edms.merck.com
ITSOP-0011: System Administration and Use of Enterprise Backup and
http://edms.merck.com
Recovery Systems
ITSOP-0014 - Account and Access Management for IRM&C Supported
http://edms.merck.com
Applications and Systems
ITSOP-0015 – IT Change Management Process – Pre-Authorized
http://edms.merck.com
Changes
ITSOP-0020 - IT Change Management Process – Planned and Unplanned
http://edms.merck.com
Changes
ITSOP-0018 - Information Security Threat and Vulnerability
http://edms.merck.com
Management
ITSOP-0019 - Information Security Investigation Management http://edms.merck.com
ITSOP-0021 - Information Security Incident Management http://edms.merck.com

22 Resources

Resource Identification / Source / Location

Description

Remedy https://remedy-web.merck.com

Documentum http://webtop.merck.com/

Page 80 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

Resource Identification / Source / Location

Description
http://projectsext.merck.com/sites/core_infr_transition/ProjectDocuments/Forms/All
Items.aspx?RootFolder=%2fsites%2fcore%5finfr%5ftransition%2fProjectDocument
Teamsite
s%2fKA%20Documentation%20%2dTemp%2fDatabase%2fDB2&FolderCTID=0x
0120005765ACD97B235541AEE16F2D43DF78F6

Location of SOPs for DBA Documentum\Docbases\gdmsprd\IS\Global Infrastructure\GI Document

Database Services Library\Departmental View\DBA-Database\DBA-SOP

http://webtop.merck.com/webtop/component/main?__dmfClientId=1384800321802
Database Backup Information
&__dmfRequestId=__client2~~2&__dmfJumpType=jump

http://webtop.merck.com/webtop/component/main?__dmfClientId=1384800321802
&__dmfRequestId=__client2~~2&__dmfJumpType=jump
Database Operations gdmsprd: Cabinets/IS/Global Infrastructure/GDS/Team Folders/Database
Services/Team Folders/Database Shared Services/DB2

http://webtop.merck.com/webtop/drl/objectId/090030f980ef74ce

On Boarding Document
(Runbook, etc.) http://projectsext.merck.com/sites/core_infr_transition/ProjectDocuments/Forms/All
Items.aspx?RootFolder=%2fsites%2fcore%5finfr%5ftransition%2fProjectDocument
s%2fKA%20Documentation%20%2dTemp%2fDatabase%2fDB2&FolderCTID=0x
0120005765ACD97B235541AEE16F2D43DF78F6

Online Course http://mylearning.merck.com

Egate https://egate.merck.com

AlarmPoint http://alerting.merck.com/alarmpoint/signOn.do

AMSU http://uctvp615:7777/pls/apex/f?p=129:1

Appendix A: DB Platform Standards

gdmsprd : Cabinets/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared

Services/DB2/Operations/Miscellaneous

http://webtop.merck.com/webtop/component/main?__dmfClientId=F5_Opener&__dmfRequestId=__client1~~2&__
dmfJumpType=jump

Appendix B: DB2 Access form

Page 81 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.
PLATFORM SUPPORT PLAN
DB2 Platform Support Plan, 1.0
DEPARTMENT/DIVISION/SERVICE AREA – TOPIC/SUBJECT/USE:
Infrastructure Engineering & Development – Database Services

gdmsprd : Cabinets/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared

Services/DB2/Operations/Miscellaneous

http://webtop.merck.com/webtop/component/main?__dmfClientId=F5_Opener&__dmfRequestId=__client1~~2&__
dmfJumpType=jump

Appendix C: DB Team Folders

gdmsprd : Cabinets/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations/IMPACT

http://webtop.merck.com/webtop/component/main?__dmfClientId=1385061529567&__dmfRequestId=__client1~~
3&__dmfJumpType=jump

Appendix D: Mainframe DB2 DBA Access

gdmsprd : Cabinets/IS/Global Infrastructure/GDS/Team Folders/Database Services/Team Folders/Database Shared
Services/DB2/Operations/Miscellaneous

http://webtop.merck.com/webtop/component/main?__dmfClientId=1394111638204&__dmfRequestId=__client2~~
2&__dmfJumpType=jump

Page 82 of 82
The information contained herein is the sole property of Merck and is PROPRIETARY. The recipient is
responsible for safekeeping, prevention of unauthorized appropriation, use or disclosure.