AT&T DEFINITY Generic 3 Manuale Utente

Issue  4 September 1995

 

This appendix provides recommendations on how to write vectors that promote 
favorable performance practices. Two basic principles to follow are:

1. Minimize the amount of call processing

— Minimize the number of vector steps to process a call

— Use the lower cost steps when possible (refer to Table M-4 and 

2. Avoid vector steps which have a substantial probability of failure

— Calls made outside of business hours

— Queues to groups with less than desirable resources or 

characteristics

The most wasteful use of processing resources is frequently caused by 
inefficient looping. For example, performance could be compromised when a 
vector loops through steps too often. This is especially true with long queue 
times.

Some examples with looping are discussed and recommendations are given on 
how to maximize performance. They are:

■

Audible Feedback

■

Lookahead Interflow

■

Check Backup

Examples other than looping are also discussed. They are:

■

After Business Hours