TradeCapRep Tag Question

, ,
1

Imported from previous forum

2

Hi all,

I’m a newbie here…plz excuse if this is wrong place for my question.

I am in the process of defining data-area(COBOL copybook) for TradeCaptureReport(MsgType=‘AE’).
Now I have a peculiar situation where i need to use TAG ‘751’(TradeReportRejectReason), which is a valid tag for TradeCaptureReportAck [type ‘AR’] and not defined in the spec for TradeCaptureReport [type ‘AE’].
So, Is it valid to define/use this ‘751’ TAG in my ‘AE’ messagetype layouot?
If it is not valid,
How do i define/use TAG ‘751’?
What is process of defining a custom(user) tag similar to ‘751’?

Appreciate you help in advance!! :slight_smile:

Thanks!!

3

This sounds like a potential mis-use of the TCR message. The reason that 751 is only in the TCRAck is that only TCRAck should be used to accept or reject a TCR. You want to have 751 in the TCR and thus I assume you want to use TCR to reject a TCR, right?

User-defined fields are supposed to enhance the standard message with additional attributes without changing the semantic of the entire message. Key fields such as XXXStatus, XXXReason should be used as intended and not substituted by UDFs.

So, what is your business requirement that makes you want to use 751 in the TCR? Maybe one can solve the problem from that end and give you some advice that lets you remain compliant with the standard.

Hi all,

I’m a newbie here…plz excuse if this is wrong place for my question.

I am in the process of defining data-area(COBOL copybook) for
TradeCaptureReport(MsgType=‘AE’). Now I have a peculiar situation where
i need to use TAG ‘751’(TradeReportRejectReason), which is a valid tag
for TradeCaptureReportAck [type ‘AR’] and not defined in the spec for
TradeCaptureReport [type ‘AE’]. So, Is it valid to define/use this ‘751’
TAG in my ‘AE’ messagetype layouot? If it is not valid, How do i
define/use TAG ‘751’? What is process of defining a custom(user) tag
similar to ‘751’?

Appreciate you help in advance!! :slight_smile:

Thanks!!

4

Hi Hanno Klein,

Thanks for the reply!!
Currently i dont have answer to your questions, however i will get back to again when i get the answers from the bussiness person.
Yes, you are correct looks like we are using TCR to reject/accept a TCR.

This sounds like a potential mis-use of the TCR message. The reason that
751 is only in the TCRAck is that only TCRAck should be used to accept
or reject a TCR. You want to have 751 in the TCR and thus I assume you
want to use TCR to reject a TCR, right?

User-defined fields are supposed to enhance the standard message with
additional attributes without changing the semantic of the entire
message. Key fields such as XXXStatus, XXXReason should be used as
intended and not substituted by UDFs.

So, what is your business requirement that makes you want to use 751 in
the TCR? Maybe one can solve the problem from that end and give you some
advice that lets you remain compliant with the standard.

Hi all,

I’m a newbie here…plz excuse if this is wrong place for my question.

I am in the process of defining data-area(COBOL copybook) for
TradeCaptureReport(MsgType=‘AE’). Now I have a peculiar situation
where i need to use TAG ‘751’(TradeReportRejectReason), which is a
valid tag for TradeCaptureReportAck [type ‘AR’] and not defined in the
spec for TradeCaptureReport [type ‘AE’]. So, Is it valid to define/use
this ‘751’ TAG in my ‘AE’ messagetype layouot? If it is not valid, How
do i define/use TAG ‘751’? What is process of defining a custom(user)
tag similar to ‘751’?

Appreciate you help in advance!! :slight_smile:

Thanks!!

5

Hi Hanno Klein,

Thanks for the reply!! Currently i dont have answer to your questions,
however i will get back to again when i get the answers from the
bussiness person. Yes, you are correct looks like we are using TCR to
reject/accept a TCR.

This sounds like a potential mis-use of the TCR message. The reason
that 751 is only in the TCRAck is that only TCRAck should be used to
accept or reject a TCR. You want to have 751 in the TCR and thus I
assume you want to use TCR to reject a TCR, right?

User-defined fields are supposed to enhance the standard message with
additional attributes without changing the semantic of the entire
message. Key fields such as XXXStatus, XXXReason should be used as
intended and not substituted by UDFs.

So, what is your business requirement that makes you want to use 751
in the TCR? Maybe one can solve the problem from that end and give you
some advice that lets you remain compliant with the standard.

Hi all,

I’m a newbie here…plz excuse if this is wrong place for my
question.

I am in the process of defining data-area(COBOL copybook) for
TradeCaptureReport(MsgType=‘AE’). Now I have a peculiar situation
where i need to use TAG ‘751’(TradeReportRejectReason), which is a
valid tag for TradeCaptureReportAck [type ‘AR’] and not defined in
the spec for TradeCaptureReport [type ‘AE’]. So, Is it valid to
define/use this ‘751’ TAG in my ‘AE’ messagetype layouot? If it is
not valid, How do i define/use TAG ‘751’? What is process of
defining a custom(user) tag similar to ‘751’?

Appreciate you help in advance!! :slight_smile:

Thanks!!

Hi Hanno,

Hope you had good holiday season.
Looks like the bussiness want this field(similar to ‘751’) as part of the TCR we send. We(DTCC) get this from the fields from the exchange and then pass on this info to various participants(Brokerage firms).
So we agreed to you use ‘20001’ UDT in this regard. Please let us your thoughts.

Thanks!!