The SWIFT data protocol performs the following actions:
For example, the data protocol converts the following SWIFT messages:
{1:F01BANKDEFMAXXX2039063581}{2:O1031609050901BANKDEFXAXXX89549829458949811609N}{3:{108:00750532785315}}{4:
:16R:GENL
:20C::SEME//YOUR REFERENCE
:16S:GENL
:16R:SETDET
:22F::SETR//TRAD
:16R:SETPRTY
:97A::SAFE//YYYY
:16S:SETPRTY
:16S:SETDET
-}
to the following XML:
<message> <block1> <applicationId>F</applicationId><serviceId>01</serviceId> <logicalTerminal>BANKDEFMAXXX</logicalTerminal> <sessionNumber>2039</sessionNumber> <sequenceNumber>063581</sequenceNumber> </block1> <block2 type=\"output\"> <messageType>103</messageType> <senderInputTime>1609</senderInputTime> <MIRDate>050901</MIRDate> <MIRLogicalTerminal>BANKDEFXAXXX</MIRLogicalTerminal> <MIRSessionNumber>8954</MIRSessionNumber> <MIRSequenceNumber>982945</MIRSequenceNumber> <receiverOutputDate>894981</receiverOutputDate> <receiverOutputTime>1609</receiverOutputTime> <messagePriority>N</messagePriority> </block2> <block3> <BLOCK3_108>00750532785315</BLOCK3_108> </block3> <block4> <GENL> <GENL_20C>:SEME//YOUR REFERENCE</GENL_20C> </GENL> <SETDET> <SETDET_22F>:SETR//TRAD</SETDET_22F> <SETPRTY> <SETPRTY_97A>:SAFE//YYYY</SETPRTY_97A> </SETPRTY> </SETDET> </block4> </message>
If some fields in the SWIFT message include a date, the data protocol reformats the date in a format that DevTest can identify as a magic date candidate.
The following example shows the fields that the data protocol checks for dates:
:98A::SETT//19911130
:98C::TRAD//20140117125901
:98E::PREP//20091107093238,02/N0230
:32A:870902JPY3520000,
:30:640123
The data protocol converts these lines to the following XML:
<BLOCK4_98A>:SETT//1991-11-30</BLOCK4_98A>
<BLOCK4_98C>:TRAD//2014-01-17 12:59:01</BLOCK4_98C>
<BLOCK4_98E>:PREP//2009-11-07T09:32:38.020-0230</BLOCK4_98E>
<BLOCK4_32A>1987-09-02 JPY3520000,</BLOCK4_32A>
<BLOCK4_30>2064-01-23</BLOCK4_30>
The service image contains the dates it represents as magic dates.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|