What technologies was TAPS built on?

TAPS was built on the Adabas database and Natural programming language. It utilized z/OS operating system features for transaction processing and data management.

What was the system architecture of TAPS?

TAPS used a mainframe architecture with dedicated servers for database management, application processing, and communication. Components communicated via internal protocols optimized for z/OS.

What business value did TAPS provide?

TAPS provided real-time trade processing and position updates, which enabled timely decision-making. It automated clearing and settlement processes, reducing manual effort and errors.

How did TAPS improve operational efficiency?

By automating trade processing and settlement, TAPS reduced operational costs and improved efficiency. It also provided a centralized platform for managing trading activities.

How did TAPS support regulatory compliance?

TAPS supported compliance with regulatory requirements by providing audit trails and reporting capabilities. It ensured that trading activities were properly recorded and monitored.

How was security handled in TAPS?

TAPS relied on z/OS security features for authentication and authorization. It supported RACF for user management and access control.

What access control model was used in TAPS?

TAPS used an access control list (ACL) model to manage permissions. Access to specific functions and data was controlled based on user roles and responsibilities.

How was data protected in TAPS?

Data within TAPS was protected using encryption at rest and in transit. Sensitive data was encrypted using industry-standard algorithms.

What administrative interfaces were available?

TAPS provided administrative interfaces through a character-based terminal. User management, system configuration, and monitoring were performed via these interfaces.

What monitoring and logging capabilities existed?

TAPS generated detailed logs of system activity and user actions. These logs were used for monitoring, auditing, and troubleshooting.

What network requirements existed for TAPS?

TAPS required specific network configurations to ensure proper communication between components. It used dedicated ports for database access and application processing.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

TAPS

Morgan Stanley Not Supported z/OS

Application - Banking/Finance

Vendor

Morgan Stanley

Product Overview

TAPS (Trading Analysis and Processing System) was a mainframe-based system utilizing Adabas and Natural. Its architecture comprised database management servers, application processing servers, and communication servers, all optimized for z/OS. Data storage relied on Adabas.

Communication between components used internal protocols. TAPS did not expose standard APIs; integration was achieved through custom interfaces or direct database access. Security relied on RACF for authentication and ACLs for access control.

Key administrative interfaces were character-based terminals. Migration requires a phased approach, focusing on data integrity and workflow validation. 0 and RBAC.

Frequently Asked Questions

What were the main functions of TAPS?

TAPS was primarily used for trade capture, order management, position keeping, and clearing and settlement processing. It facilitated real-time updates of trading positions and supported various financial instruments.

How did users interact with TAPS?

Users interacted with TAPS through a character-based interface using specific transaction codes and screen layouts. Data entry and retrieval were performed via these interfaces.

What types of financial instruments did TAPS support?

TAPS supported a range of financial instruments, including equities, fixed income securities, and derivatives. It managed the lifecycle of these instruments from trade execution to settlement.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

TAPS

Product Overview

Frequently Asked Questions

What were the main functions of TAPS?

How did users interact with TAPS?

What types of financial instruments did TAPS support?

What technologies was TAPS built on?

What was the system architecture of TAPS?

Did TAPS expose any APIs?

What business value did TAPS provide?

How did TAPS improve operational efficiency?

How did TAPS support regulatory compliance?

How was security handled in TAPS?

What access control model was used in TAPS?

How was data protected in TAPS?

What administrative interfaces were available?

What monitoring and logging capabilities existed?

What network requirements existed for TAPS?

Related Products

Similar Products

ACI Acquirer

ACI Communication Services

ACI Host Link

ACI Interchange

ACI Issuer

ACI Proactive Risk Manager

Help Improve This Directory

Share Your Product Experience