10.0 Using Delayed Activation

10.1 What is Delayed Activation?

10.2 Delayed Activation Parameters in Input Message

10.3 Types of Delayed Activation

10.4 Testing Delayed Activation

10.5 Examples for Delayed Activation

10.1 What is Delayed Activation?

Using the Delayed Activation feature, an input message can be stored in a Message Pending buffer at the NE for final execution at some later time. The input message in the Message Pending buffer at the NE can be executed either automatically (Timed Delayed Activation) or by a subsequent message from the OS (Manual Activation).

For each delayed activation message, first agent will send DELAY response then it will send the actual response.

10.2 Delayed Activation Parameters in Input Message

The Delayed Activation function is provided by a set of parameters within the GB of an input message and is of the form shown below.

Here,

ON parameter value is an activation order number assigned by you. This number is used by the NE to internally identify the delayed input message.

DATE parameter value is the date when the delayed activation is scheduled to occur and is of the form as shown below :

Here,

<yy>  is the last two characters of the year.
<mm> is a value in the range from 01 to 12 identifying the month.
<dd> is the day of the month in the range from 01 to 31.

The TIME parameter value is the time within the specified date when the delayed activation is scheduled to occur and is of the form as shown below :

Here,

<hh>  is a value from 00 to 23 identifying the hour.
<mm> is a value in the range from 00 to 59 identifying the minute within the specified hour.
 <ss> is a value in the range from 00 to 59 identifying the second within the specified minute.

10.3 Types of Delayed Activation

There are three ways in which the input command can specify its action to be executed
at the NE. They are as follows:

1. An input command can be specified to be immediately executed following parsing and interpretation of the message. This is considered to be the default situation.

2. It can be specified to be held in a pending buffer at the NE and executed at some later date and time. This is called Timed Delayed Activation or Automatic Delayed Activation.

3. It can be specified to be held in a pending buffer in the NE until another input command is received to execute the command. This is called Delayed Manual Activation.

For each delayed activation message (whether it is manual or timed ), first agent will send DELAY response then it will send the actual response.

Delayed Activation Truth Table

10.4 Testing Delayed Activation

Before testing the examples for Delayed Activation function, make sure you do the following.

1. Run a simple TL1 Agent at a specified Port.

2. Connect to the Agent using the TL1Browser.

3. Load the TCS for which the Agent was created say  tl1sample.tcs, tl1security.tcs, and tl1builtincommands.tcs in the TL1Browser.

4. Deselect the Edit->Setting ->Parser Option -> Enable parsing of entire message option to receive response messages for the delayed input message in the TL1 Browser .

5. Expand the tl1security.tcs tree and select ACT-USER command.

6. Authenticate into the TL1 Agent by sending the  Input command "ACT-USER::root:1::public;". Here the user is the "root" ( the administrator) and the password is "public". For more information about Authentication please refer to "Testing the TL1 Agent" Chapter

7. Expand the tl1sample.tcs file and choose the ALW-LPBK command for which you will be running the Delayed Activation examples.

10.5 Examples for Delayed Activation

Following are the some examples for using the Delayed Activation function. Please note that Delayed Activation is session specific. Once the user terminates the session, the Delayed Activation will be deactivated.

1. Immediate Activation

ALW-LPBK: : : 1 : : ;

This command will be executed and the response will be sent immediately.

2. Delayed Manual Activation

ALW-LPBK: : : 2 : 1, , , : ;

You will receive the following response :

This command with Order Number as 1 has been delayed its activation and can be manually activated by following the steps below:

1. Expand the tl1builtincommands.tcs file tree.

2. Choose ACT-DA command

3. Send the command with AID as 1. For example ACT-DA::1:2::;. Here, 1 given as AID is the order number.

4. You will find the command executed and the Agent will send a response as "COMPLD".

3. Activation at the Next Occurrence of the Specified  Time  (11-22-40 in the same day)

ALW-LPBK: : : 2 : 1, , 11-22-40, : ;

This command will automatically get processed at the specified time and the appropriate response will be sent to the TL1Browser.

4. Activation on the Specified Date (2002- March - 17)

ALW-LPBK: : : 2 : 1,01-03-17 ,, : ;

This command will automatically get processed at the specified date and the appropriate response will be sent to the TL1Browser.

5. Activation at the Specified Date ( 2002 - March - 17) and Time(11-22-40)

ALW-LPBK: : : 2 : 1,01-03-17 , 11-22-40, : ;

This command will automatically get processed at the specified date and time and the appropriate response will be sent to the TL1Browser.

6. Retrieving Delayed Activation Commands.

By using the command RTRV-DA which is also available in the tl1builtincommands.tcs file all or any of the Delayed Activation messages pending at NE can be retrieved.

RTRV-DA::ALL:2::;

This command will retrieve all the Delayed Activation commands from the message pending buffer.

You can also cancel any delayed activation messages from the message pending buffer using the CANC-DA command (Explained in Chapter 11.). This command is also available in the tl1builtincommands.tcs.