Question

Do FX enquiries FXPOS and FXPOS.DDE exist in the recent R08 release?

Answer

1) ENQ FXPOS

The enquiry FXPOS is made obsolete and the enquiry PM.FXPOS is the replacement for the
same; so kindly use PM.FXPOS to serve the purpose.

2) ENQ FXPOS.DDE

Due to performance reasons the file PM.POSN.REAL.TIME has been made obsolete from
G132 onwards. The PM.DLY.POSN.CLASS file will be referred instead of PM.POSN.REAL.TIME
file.
All the PM enquiries are made to fetch values from PM.DLY.POSN.CLASS instead of
PM.POSN.REAL.TIME for better performance.

Since this enquiry FXPOS.DDE is based on the file PM.POSN.REAL.TIME, don’t use it. Instead
use the enquiry DPC4.

Similarly PM.CAS & PM.GAP are a replacement of CAS & GAP enquiries respectively.

Question

Why is the system not updating the TXN.REFERENCE field in PM.DLY.POSN.CLASS file for
any of the transaction?

Answer

From R08 release onwards, update of the field TXN.REFERENCE in PM.DLY.POSN.CLASS is

prevented on performance grounds. Instead PM.DRILL.DOWN file has been introduced to
know the PM.DLY.POSN.CLASS record generated for the corresponding transaction. The ID
format of PM.DRILL.DOWN is PM.DLY.POSN.CLASS.ID (excluding the value of DATE.SFX)-
<ID OF THE TRANSACTION>.

E.g. FTASC.1.00.TR.EUR.20080625-FT08177TLYMC*REAL

Kindly refer to the file PM.DRILL.DOWN in order to know the PM.DLY.POSN.CLASS and the
transaction updated for it.

Question

Why PM.POSN.REAL.TIME table and PM.NIGHT.POSN.CLASS table have not been updated
after COB? The FXREVAL SUMMARY is also wrong.

Answer

From G132 release onwards PM.POSN.REAL.TIME table updating is prevented on

performance grounds. All the PM enquiries are made to fetch values from
PM.DLY.POSN.CLASS for better performance. So, we are suggesting you to use PM enquiries
(say PM.CAS, PM.GAP, PM.FXPOS), which extract the data from PM.DLY.POSN.CLASS
record.

In order to generate FXREVAL summary report, kindly run the enquiry PM.FXREVAL &
PM.FXREVAL.SUMMARY.

Question

What is use of PM.MAX.PERIOD field in PM.LD.PARAM table?

Answer

In cases where it is common to enter long-term loans i.e. 10 years or more we may wish to
set this value to limit the updates sent to PM to a more reasonable period. For example if
we want to enter a 25 year term loan with monthly settlements of Interest and/or
Commission we can limit the number of months of information sent to PM. It is unlikely we
would use PM information (broken down on a monthly basis) that far in advance, and to
avoid the overhead at input time we can set this field to say 12 (representing 12 months).