Worldwide Securities Services Project Code(s): 261140

ACCE Program-Story#2029

Worldwide Securities Services

Technical Design Document

ACCE Program-Story#2029
CSD Trade files purging
Document Version 1.21
Project (PAR) Code(s): 62784
SR Number: <SR Number>
JIRA Reference: <JIRA Ref>
DRAFT VERSION

Date Created: 01/08/2015

Date Revised: 01/08/2015
Last Saved By:JPMorgan Chase & Co.

2011 JPMorgan Chase & Co. All Rights Reserved.

Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.11
Page: 1 of 11

Worldwide Securities Services Project Code(s): 261140

ACCE Program-Story#2029

Table of Contents
TABLE OF CONTENTS.............................................................................................................................. 2
1

INTRODUCTION.................................................................................................................................. 4
1.1
1.2
1.3
1.4

ARCHITECTURE................................................................................................................................. 4
2.1
2.2
2.3
2.4
2.5
2.6

PURPOSE........................................................................................................................................ 4
BACKGROUND................................................................................................................................. 4
OUT OF SCOPE............................................................................................................................... 4
OUTSTANDING QUESTIONS............................................................................................................... 4
HARDWARE ENVIRONMENT............................................................................................................... 4
SOFTWARE ENVIRONMENT............................................................................................................... 5
DESIGN ASSUMPTIONS AND CONSTRAINTS........................................................................................ 5
DESIGN DEPENDENCIES................................................................................................................... 5
DESIGN METHODS AND TOOLS......................................................................................................... 5
CONFIGURATION RECORDS.............................................................................................................. 5

PROPOSED SOLUTION...................................................................................................................... 6
3.1
CURRENT PROCESSING................................................................................................................... 6
3.1.1
Process Flow......................................................................................................................... 6
3.1.2
Process Description............................................................................................................... 6
3.1.3
Issues with current Business Processes................................................................................6
3.2
PROPOSED PROCESSING................................................................................................................. 6
3.2.1
Process Flow (high level)....................................................................................................... 6
3.3
SCREEN CHANGES.......................................................................................................................... 7
3.3.1
Retired Screens..................................................................................................................... 7
3.3.2
New Screens......................................................................................................................... 7
3.3.3
Amended Screens................................................................................................................. 7
3.4
PROGRAMS / PROCESS CHANGES.................................................................................................... 8
3.4.1
Retired Programs/Processes................................................................................................. 8
3.4.2
New Programs/Processes..................................................................................................... 8
3.4.3
Amended Programs/Processes............................................................................................. 8
3.5
DATABASE CHANGES....................................................................................................................... 8
3.5.1
New Files............................................................................................................................... 8
3.5.2
Amended Files....................................................................................................................... 8

IMPLEMENTATION OVERVIEW.......................................................................................................... 8
4.1
4.2
4.3

UAT IMPLEMENTATION ADDITIONAL CONSIDERATIONS.....................................................................8

PSG IMPLEMENTATION ADDITIONAL CONSIDERATIONS.....................................................................8
PROD IMPLEMENTATION ADDITIONAL CONSIDERATIONS...................................................................8

POST PRODUCTION IMPLEMENTATION.......................................................................................... 9

5.1

LIST IN THIS TABLE ALL DOCUMENTS AND MATERIALS REFERENCED IN OR USED WHILE PREPARING THIS
DOCUMENT. LOCATION IDENTIFIES WHERE THIS REFERENCED ITEM MAY BE FOUND. THIS MIGHT BE A PHYSICAL
LOCATION, AN ELECTRONIC STORAGE LOCATION, OR AN INTERNET ADDRESS.................................................9
5.2
SUPPORT DOCUMENTS.................................................................................................................... 9
5.3
BAU PROCESSING.......................................................................................................................... 9
tbc........................................................................................................................................................ 9
6

REFERENCE DOCUMENTS............................................................................................................... 9

Date Created: 01/08/2015

Date Revised: 01/08/2015
Last Saved By:JPMorgan Chase & Co.

2011 JPMorgan Chase & Co. All Rights Reserved.

Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.11
Page: 2 of 11

Worldwide Securities Services Project Code(s): 261140

ACCE Program-Story#2029

DOCUMENT CONTROL...................................................................................................................... 9
7.1
7.2
7.3

APPROVAL....................................................................................................................................... 9
DOCUMENT HISTORY....................................................................................................................... 9
DOCUMENT STORAGE...................................................................................................................... 9

APPENDIX......................................................................................................................................... 10
8.1
SYSTEM MESSAGES...................................................................................................................... 10
8.2
IFS DIRECTORIES.......................................................................................................................... 10
8.3
CCMS MENU OPTIONS................................................................................................................. 10
8.4
ROBOT JOB DEFINITIONS............................................................................................................. 10
8.5
CCMS STANDING DATA................................................................................................................. 10
8.5.1
Run time parameters IFS and file names etc....................................................................10
8.5.2
Email Functionality............................................................................................................... 11
8.6
TURNOVER WORKLIST................................................................................................................... 11
8.7
ESTIMATE OF EFFORT.................................................................................................................... 11

Date Created: 01/08/2015

Date Revised: 01/08/2015
Last Saved By:JPMorgan Chase & Co.

2011 JPMorgan Chase & Co. All Rights Reserved.

Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.11
Page: 3 of 11

INTRODUCTION

1.1

PURPOSE

The purpose of this document is to describe the detailed design for the requirements stated in the
Business Requirements Document. The document will indicate the system design to a moderate level of
detail, and describe which techniques and development approaches must be used to write the software.
The level of the detail within this specification document would be sufficient for detailed program
specifications to be produced for every software component.
This document will describe a summary of the implementation procedure required to install the changes
into production and the test environments.
A separate plan document will be produced to show the implementation steps in detail.
The document will also describe the post implementation support and BAU processes changed as a
result of the implementation. It will list the support documents which have been created or changed and
their storage location.

Mingle link:
http://tsnc5lvmappd248.svr.us.jpmchase.net:8080/projects/acce_project/cards/2029?referrer%5Bq
%5D=2029&referrer%5Bq_type%5D=&referrer%5Bquery_id%5D=q_637201007&referrer%5Brank
%5D=1&referrer%5Bsize%5D=1&referrer%5Bts%5D=06%2F15%2F15+08%3A38%3A04

1.2

BACKGROUND

To keep CCMS lean and tidy all transaction files should have a robust purging process.
CCMS XML parsers generates DFP/RFP trades for segregated accounts movements which are
processed via CCMS clearance engines. DFP/RFP pairs are stored in standard TRADE tables on CCMS.
There is new trade archive and purge routine is already in development under the Trade Quarantine
Project. This new archive and purge process is driven via configuration data setups in tables namely
AP002P and RGZLST.
CSD trades generated on back of allocation runs on CC can be archived and purged via this new
mechanism. Configuration data needs to be added in configuration table AP002P with entity as
TRADEARC and the reorganize files list need to be added in RGZLST file.

1.3

OUT OF SCOPE

None

1.4

OUTSTANDING QUESTIONS

None

2 ARCHITECTURE
2.1

HARDWARE ENVIRONMENT

Hardware
Components
iSeries

Hardware Vendors & Products

IBM

Version
#
V6R1

2.2

SOFTWARE ENVIRONMENT

Environment

DNS name

IP Address

CCMS Production
CCMS UAT
CCMS QAT
CCMS DR
CCMS Dev/Unit /System

CCMPRD.svr.emea.jpmchase.net
CCMUAT.rdc.uk.jpmorganchase.com
CCMQAT.rdc.uk.jpmorganchase.com
CCMDR.rdc.uk.jpmorganchase.com
CCMDEV.rdc.uk.jpmorganchase.com

169.93.42.50
169.95.143.203
169.95.143.225
169.95.143.199
169.95.143.221

Machine
Type
890 LPAR
890 LPAR

2.3

DESIGN ASSUMPTIONS AND CONSTRAINTS

This design document is currently providing the details of the CCMS changes required for the following
stories
Story #2029(Tech Task) - TT:CCMS CSD Trade files purging.
2.4

DESIGN DEPENDENCIES

Current design of the solution is strictly dependent on the Trade Quarantine Project of trade files
archiving and reorganizing. If there is any change in Trade Quarantine project design then our design also
may require changes. The TDD for the Trade Quarantine project is also attached here.

TDD TRADE
Quarantine Project (2).docx

2.5

DESIGN METHODS AND TOOLS

The coding and implementation will comply with the current standards and processes as detailed in the
following documents:
Document Title

Reference

Document Location

i-Series Technical Standards

ITS-TSD-012

Quality Assurance Technical

Audit checklists
Software Control Process

ITS-SQA-003

http://intraspectkm.jpmorganchase.com/gm/document1.9.2539865
http://intraspectkm.jpmorganchase.com/gm/document1.9.2539878
http://intraspectkm.jpmorganchase.com/gm/document1.9.2539894
http://intraspectkm.jpmorganchase.com/gm/document1.9.2564633

ITS-SCP-001

Technical Debt user guide

2.6

CONFIGURATION RECORDS

None.

3 PROPOSED SOLUTION
3.1
3.1.1

CURRENT PROCESSING
PROCESS FLOW

The current Trade file archive process designed under Trade Quarantine project are as followsArchiving From DTALIB to ARCLIB runs in MultiStreams :

TRDRCJB01

PITTRDARC
Job

DTALIB
ARCLIB
Deletes Data Writes
After Write
Data

Run until end time

or EndFlag

OM2:
TradeArcMaxStrm

TRDARCJB02
(N)
TRDARCJB(N)

In summary, it reads all the records from AP002P file for ENTITY = 'TRADEARC' AND FILEATR = 'S'
and the copy the file's data in ARCLIB and removes the file's data from DTALIB based on the OM2
configuration data.
And the current Reorganizing of file process is as under
Saturday ReOrg:List Of Files
in RGZLST

Result: Objects of DTALIB are

Reorgd

Run job
PITLON2461

In summary, it is reading records from RGZLST file and reorganizing the files mentioned in that list in the
sub jobs RGZMJOBxx where xx is the stream number mentioned against that filename in RGZLST file.

3.1.2

PROCESS DESCRIPTION

Please refer the section 3.1.1 and the attaches TDD of the Trade Quarantine project.

3.1.3

ISSUES WITH CURRENT BUSINESS PROCESSES

CSD trade files need to be archived and reorganized.

3.2
3.2.1

PROPOSED PROCESSING
PROCESS FLOW (HIGH LEVEL)

Configuration data needs to be added in configuration table AP002P(List of physical files to be Archived
and purged) with entity as TRADEARC and the reorganize files list need to be added in
RGZLST(Reorganize files list) file.

AP002P Insert the following records

ENTITY
TRADEAR
C

FIL
EA
TR
S

FILENM
CSDMIGT
AP

FIL
ET
YP
P

FLDNM
CURTRDI
D

FL
DT
YP
T

FSTR
EAM

JRN
YN

106 Y

PGM
NM

SELEC
TION

TRADEAR
C
TRADEAR
C
TRADEAR
C
TRADEAR
C

S
S
S
S

CSDTDAS
CP
CSDTDFL
RP
CSDTDQT
YP
CSDTDXR
FP

DFPTRDEI
D

107 N

TRDEID

108 Y

TRDEID
DFPTRDI
D

109 Y

110 Y

RGZLST Insert the following records

File
Name
CSDMIGTA
P
CSDTDAS
CP
CSDTDFLR
P
CSDTDQT
YP
CSDTDXRF
P

Strea
m
15
15
16
16
17

A new implementation script is required to add the above mentioned records in the mentioned files.

3.3
3.3.1

SCREEN CHANGES
RETIRED SCREENS

N/A

3.3.2

NEW SCREENS

N/A

3.3.3

AMENDED SCREENS

N/A

3.4
3.4.1
N/A

PROGRAMS / PROCESS CHANGES

RETIRED PROGRAMS/PROCESSES

3.4.2

NEW PROGRAMS/PROCESSES

A new implementation script is need to be created to add the entries in AP002P file and RGZLST file.

3.4.3

AMENDED PROGRAMS/PROCESSES

N/A

3.5
3.5.1

DATABASE CHANGES
NEW FILES

N/A

3.5.2

AMENDED FILES

N/A

4 IMPLEMENTATION OVERVIEW
This section describes a summary of the implementation process for each affected system or
environment for the solution described in this document. For implementations into UAT and above there
will be a full implementation plan completed with more detail for timings and tasks, when development
and system testing has completed.
The software will be promoted using Turnover.
Skeleton

4.1

UAT IMPLEMENTATION ADDITIONAL CONSIDERATIONS

ECMS required to promote Turnover forms

TM to define Robot Jobs, Environment team to assign to environment
Users to add required menu option definition

4.2

PSG IMPLEMENTATION ADDITIONAL CONSIDERATIONS

ECMS required to promote Turnover forms

TM to define Robot Jobs, Environment team to assign to environment
Users to add required menu option definition

4.3

PROD IMPLEMENTATION ADDITIONAL CONSIDERATIONS

ECMS required to promote Turnover forms
EURC required to add menu options
EURC rand ECMS required to create Robot jobs

5 POST PRODUCTION IMPLEMENTATION

5.1

LIST IN THIS TABLE ALL DOCUMENTS AND MATERIALS REFERENCED IN OR USED WHILE
PREPARING THIS DOCUMENT. LOCATION IDENTIFIES WHERE THIS REFERENCED ITEM MAY
BE FOUND. THIS MIGHT BE A PHYSICAL LOCATION, AN ELECTRONIC STORAGE
LOCATION, OR AN INTERNET ADDRESS.

5.2

SUPPORT DOCUMENTS

Reference Document

Location

Gateway Support Tracking Log

http://intraspectkm.jpmorganchase.com/gm/fold
er-1.11.408650
http://intraspectkm.jpmorganchase.com/gm/doc
ument-1.9.1966542

Environment Manager Manual

5.3

BAU PROCESSING

TBC

6 REFERENCE DOCUMENTS
Reference Document

Last
Amended

Location

7 DOCUMENT CONTROL
7.1

APPROVAL

The following groups and individuals have approved this document:

Name and Group

Date

Technology Manager:
Affected Groups/Stakeholders

Refer to PKS
Refer to PKS

7.2

DOCUMENT HISTORY

Version

Name

Date

Description

0.1

Praveen Parmar

13/07/2015

Initial Draft

7.3

DOCUMENT STORAGE

Where

Link

Intraspect
PKS
Shared Drive

https://intraspectkm.jpmorganchase.com/gm/document-1.9.3407790

8 APPENDIX
8.1

SYSTEM MESSAGES

MENU
OPTION

8.2

Purpose

MENU

DESCRIPTION

NEW
ADD
CHANGE

ROBOT JOB DEFINITIONS

JOB NAME

8.5

IFS path

CCMS MENU OPTIONS

MENU
OPTION

8.4

TYPE

IFS DIRECTORIES

Menu
Option

8.3

MESSAGE

DESC

FREQ/REACT

COMMAND

CCMS STANDING DATA

8.5.1

RUN TIME PARAMETERS IFS AND FILE NAMES ETC.

8.5.1.1 Common system parameters CMPARMP (OM2)

MODULE

KEY

VALUE

DESCRIPTION

8.5.1.2 Custody System Table entries CSTBEP (SD4)

FIELD

FIELD DESCRIPTION

INITIALISED
VALUE

COMMAND

MESSAGE
ID

FIELD

8.5.2

FIELD DESCRIPTION

INITIALISED
VALUE

EMAIL FUNCTIONALITY

NA

8.6

TURNOVER WORKLIST

The following work lists will be used for this development:

APPLICATION

WORKLIST

DESCRIPTION

CCMS

CSD 0020

2029-CSD Trade files purging

8.7

ESTIMATE OF EFFORT
The following estimate covers the delivery of the solution to QA:
DESCRIPTION

ESTIMATE
(DAYS)

Technical Design Document

Software Build
System Test
Total Effort