Universe Consolidation

Universe Consolidation

This enhancement consists of the following modifications:

• Implemented a Recycle Bin for Deleted Blocks
• Changes to the block naming convention
• Changes to the Intraday Cash Adjuster

Recycle Bin for Deleted Blocks

Prior to this enhancement, when a block was accidentally deleted it typically could not be restored. To alleviate the risk of accidentally deleting blocks as more traders are manipulating more blocks in a single Windows universe, a new Recycle Bin has been created for manually deleted blocks.

The following changes were made to implement this enhancement:

1. Created a new EDSETUP variable
2. Users can restore a block from the Recycle Bin using a new option in Block Order Status
3. Added a utility to refresh the Recycle Bin
4. Added a new report to search for trades in the Recycle Bin

New EDSETUP Variable

A new variable DELBLOCKSFLG has been added. When this variable is set to 1 in a client’s directory, any manually deleted block will be copied to a Recycle Bin. The bin is stored in the new APL component file DELALOCAT. The file contains the following data elements:

• Orders and allocations from the original block
• Original SNAM of the block
• Original create date/time stamp
• Original Windows universe
• Original block title
• User that deleted the block
• Date/time stamp of when the block was deleted

Note: Blocks that are deleted automatically, such as during the overnight Windows build process, will not be stored in the Recycle Bin.

This option is available for uncommitted blocks to users that do NOT have supervisor status. Users WITH supervisor status can also access this option for committed blocks.

When restoring deleted blocks, you are prompted for a beginning and ending date. You also have the option to filter blocks by the user that deleted them.

All blocks that were deleted that meet the input criteria, that were deleted from the current Windows universe, and that correspond to the current user’s manager code (i.e.: value in the TRDMGR variable), if present, will be presented. The original block name, deletion date, deletion time, user that deleted the block and original block title will be shown.

You can select any number of blocks to be restored. Each restored block will be moved out of the recycle bin and in to the current Block Order Status view. A new block name will be automatically generated for the restored block. If the user has run SETSUPERVISOR then the new block name will begin with “AIS” since a block prefix is no longer defined. The original block title will be carried over to the new block.

Refresh Recycle Bin

Over time, the deleted block recycle bin may start to grow large. The new utility ΔREFRESHDELBLOCKS is used to remove older deleted blocks. The utility is run in a batch job and will prompt for a date. Any block that was deleted prior to the entered date will be deleted from the recycle bin.

Searching for Trades in the Recycle Bin

Since users will not have direct visibility in to the deleted block recycle bin, the new report SEARCHDELBLOCK can be used to display trades in the recycle bin. This function prompts you for a beginning and ending date, an account selection and a security selection. Blocks that were deleted within the entered date range for the accounts and securities selected will be displayed in the report.

A sample SEARCHDELBLOCK output file is shown below:

Block Naming by Product and Trader

Prior to this enhancement, block names began with the same first three characters for a given universe. This could lead to trade errors as more users are accessing more blocks in a single universe.

To ensure that traders see only their individual blocks, this enhancement modifies the block naming prefix. Block name prefixes will be defined based on the trader and the product being traded.

This enhancement consists of the following modifications:

• Two new tables have been added: one for Trader ID mapping and one for Product mapping
• A change to the Windows retrieval process
• A change to blocks that can be viewed in Block Order Status
• Modified the Autotrading Account Rebalancer

Trader ID Mapping Table

A table has been added to map a trader’s APL ID to a two character code. These codes will be the first two characters in the block name prefix. The mapping table, which can be accessed from the APL utility EDITTRADERID, will allow a home office user to link the two character code to an APL ID.

The user will be prompted with two columns: the APL ID and the two character code linked to the given ID. Only valid APL IDs can be entered in the first column. The second column must contain exactly two alpha-numeric characters. Special characters are not allowed. Only upper case letters will be allowed for alpha characters.

An example of the EDITTRADERID table is shown below:

Product Mapping Table

The product mapping table is accessed by the APL utility EDITPRODUCTID. It defines a product, or group of products, based on an account’s RR field. This table contains the following fields:

• A list of RR codes that defines a product, or defines an aggregate product view. An aggregate product view is a collection of products that span multiple RR codes. The same RR code can be in multiple rows in this table since the same product can be rolled up in to different aggregate product views
• A product description
• A product Symbol. This will be the third character in the block name prefix. This field will be a single alpha-numeric character. This character does not need to be unique in the table
• Auto Trading Account Adjuster settings, which are: round lot size, minimum lot size, and rounding method. These settings need to be applied at the product level or the aggregate product level. Round lot size and minimum lot size fields should be numeric with two decimal places. Round lot size must be greater than 0. The rounding method column should be restricted to either “UP,” “DOWN” or “NEAREST”
• Auto Trading Account Rebalancer settings, which are: round lot size, minimum lot size and rounding method. These settings need to be applied at the product level or the aggregate product level. Round lot size must be greater than 0. The rounding method column should be restricted to either “UP”, “DOWN” or “NEAREST”.

There are three input screens in EDITPRODUCTID, examples are shown below:

New Product Sub-Select in Windows

Once the trader ID and product tables are defined, traders can sub-select accounts based on product. A new sub-select prompt will be presented upon entering Windows for any trader that is included in the trader table. All other users, such as non-trader IDs and external users, will not receive this prompt.

The prompt will display the RR codes in a given product and the product name from the product table. The user needs to select a product in order to continue. Once a product is selected, the user will be restricted to seeing only those accounts meeting the RR criteria associated with the product. The block name prefix (TRDMGR) will be defined as the combination of the trader ID and the product symbol, as defined in the trader ID mapping table and product mapping table, respectively. Additionally, the auto-trading parameters will be set as defined in the product mapping table.

A sample of the prompt is shown below:

Change to Blocks Displayed in Block Order Status

Prior to this enhancement, when a trader was in a UMA universe, all blocks within the universe, regardless of any defined block prefix, was displayed. With this enhancement, Block Order Status only displays blocks with the defined block prefix, if a block prefix exists. If a block prefix does not exist, such as when a user runs SETSUPERVISOR, all blocks found in the given Windows universe are displayed.

Hard Coded Block Prefix in Autotrading Account Rebalancer

Prior to this enhancement, the Autotrading Account Rebalancer (AUTOWINDΔREBALΔAIS) used a hard-coded block naming convention. With this enhancement, the tool uses the block prefix as defined by the trader and product tables.

Intraday Cash Adjustment Modifications

The restriction that prevents the Intra Day Cash Adjuster from being accessed from outside of the MSP Master Manager and MSP Sub-Manager menus has been removed. As a result, the Intra Day Cash Adjuster is accessible from any APL menu within a UMA universe, similar to how this tool works in a non-UMA universe. Additionally, the Intra Day Cash Adjuster has been enhanced to allow adjustments for non-UMA accounts when called from within a UMA universe.