You can price this strategy with the
PrcInverseLegObject() function.
The payoff for this leg is in fact the difference of two coupons.
The first a FIXED coupon rate, the second FLOAT rate.
Thus for each coupon period, the coupon rate computed will be either a FIXED INVERSE FLOATER LEG [X - N*L] or a FLOAT INVERSE FLOATER LEG [N*L - X], where N is a positive integer gearing amount.
N represents the 'FixingGearing' parameter within the function call.
X is the FIXED coupon rate and L is the Quanto in-arrears floating rate fixing.
rates are fixed in and currency at paid in another.
Rates are also fixed at the end of the rate fixing period (instead of at the start).
If you pass in a Swap Index instead of a Libor Index, the swap rate fixing will be adjusted for the unnatural payments via a constant maturity swap adjustment calculation.
This leg object can either be priced directly via the
PrcLegObject() function or passed to the
Swap2() function.
Finally there are numerous querying functions that can be applied to this leg (within the
CapeTools Query Legs category of functions).
This function requires the input of a Schedule object key, which must have been produced via a call to one of the following functions :
MakeSchedule() or
MakeSchedule2(). These functions would have returned a string 'KEY' which is to be passed to the 'ScheduleKey' parameter of this function.
This function requires the input of an Index object key, which must have been produced via a call to one of the Index creation functions present within the
CapeTools Indexes category of functions.
You can also execute the
CreateSwapIndex(),
IDXEURSwap(),
IDXGBPSwap(),
IDXJPYSwap(),
IDXCHFSwap() or
IDXUSDSwap() function in order to price a constant maturity swap leg, a CMS convexity adjustment will be applied to rate.
These functions would have returned a string 'KEY' which is to be passed to the 'IndexKey' parameter of this function.
This function requires the input of an optional FXVolCurve object key, which must have been produced via a call to the
FlatVolCurve() or
VectorVolCurve() functions.
These functions would have returned a string 'KEY' which is to be passed to the 'FXVolCurve' parameter of this function.
This function requires the input of an optional VOLFX correlation object key, which must have been produced via a call to the
FlatVolFXCorr(),
VectorVolFXCorr() or
VolFXCorrMatrix() functions.
These functions would have returned a string 'KEY' which is to be passed to the 'FXCorr' parameter of this function.
The latter two 'key' values are used for various convexity or Quanto adjustments that may be needed.
Please refer to the large number of enum functions present within the
CapeTools Enums category of functions.
The
CapeTools Enums category of functions return correct string codes that can be passed to parameters taking fixed string values defined by the library (ie - DayCount codes, frequency codes, currency codes, compounding codes, business day convention codes etc...).
You can thus execute these enum functions which return the proper code, instead of trying to remember the string code needed or making spelling mistakes which can be difficult to debug.
This function creates an object and returns a string-key value to represent this created object.
The TAG value of the string-key returned (second part of the key) is : "FIXQIALEG"
- Key parameter
Key value to use as a handle for the created object
- Reload parameter
When creating this object for the first time, set this parameter to a positive value. Within Excel, when recomputing a worksheet where you do not wish to recreate the object, set this parameter to zero (0).
- PayRec parameter
Whether you would like to PAY or REC this leg.
- InverseType parameter
Whether you would like to structure a FIXED INVERSE FLOATER LEG [X - N*L] or a FLOAT INVERSE FLOATER LEG [N*L - X], where N is a positive gearing amount, X is the FIXED coupon rate and L is the fixing rate.
- FixingGearing parameter
A positive factor value you wish to multiply the fixing (reset) rate by.
- Notional parameter
A positive valued Notional amount of the deal. Can pass an array of notional amounts for each period
- PrincipalPayments parameter
A positive valued Principal Payments array. Generally in the case where the 'Notional' parameter has been filled with amortised Notional values you indicate, within this array, the principal amounts that are to be paid to the holder of this contract during the life of the leg. In the case of amortised legs, this should be populated. The length of this array must equal the length of the 'Notional' parameter or be empty (if you are not concerned with providing Principal Payments).
- Ccy parameter
Currency of the Notional amount.
- ScheduleKey parameter
Schedule Key to an already generated schedule object.
- BusDayConv parameter
Payment Business Day Convention. Treatment of date calculations for (discounting).
- DayCount parameter
Payment DayCounter. Used for the calculation of year periods regarding payment (discounting).
- Coupon parameter
Coupon amount to be received/paid, can pass in an array of coupons, each coupon corresponds to a cashflow of the generated schedule..
- IndexKey parameter
KEY to an already constructed Index object. This index contains the fixing (reset) curve of another currency (Quanto adjustments will be applied to the leg).
- Margin parameter
Margin amount to add onto the computed fixing/forward rate, can pass in an array of margins.
- ExchangePrincipal parameter
Whether you wish to exchange the principal amount(s) at the start and termination of the leg contract.
- MKTKey parameter
Key to an already constructed MKT object that contains at least a discounting curve. The VolCurve should be present if pricing CMS or In-Arrear legs, deals. The curves contained within this object should all be of the same Currency of which must equal the value of the 'Ccy' parameter of this function.
- FXVolCurve parameter
Key to an already constructed FX VolCurve object (via a call to either the
FlatVolCurve() or the
VectorVolCurve() functions). Used for the Quanto correction term.
- FXCorr parameter
The C# example below contains all the sub-function calls leading up to this function call. As a result, the example can contain a lot of code.
The VB.NET, J#, C++.NET, Java, Excel VBA, Visual Basic 6 (via COM) and C++ examples below contain function code stubs for the calls leading up to this function call. However, the function call for this function is displayed.
You can easily reproduce the stub functions code from the
C# example.
Copyright (c) 2003-2007 CapeTools - All Rights Reserved.