Update: My earlier answer (preserved below) was written in haste on the phone. Back where I can type now, and I see that the two answers provided in the meantime, focusing on setting the record delimiter variable $/, both fail to meet the specs you gave, if I understand them. I'm taking

I want to parse the complete file in perl and print out time and only those entries that have ESME_RTHROTTLED.

to mean that you only want to print the time, and only for the records that have 'ESME_RTHROTTLED'. If I'm wrong about that, sorry.

This should do what you want: 

$/ = 'Time: ';
while (<DATA>) {
  print( (split "\n")[0] ) if /ESME_RTHROTTLED/;
}

[download]
Output: 
$ perl 1140724.pl
There were RTHROTTLED incidents at:
  2015-09-01T09:02:43.010
  2015-09-17T09:03:43.634
  2015-09-22T09:05:17.007
$

[download]
Complete program: 
#!/usr/bin/perl
use strict;
use warnings;
use feature qw/ say /;
use DateTime::Format::Strptime qw/ strptime /;

$/ = 'Time: ';

say 'There were RTHROTTLED incidents at:';

while (<DATA>) {
  say '  ' . strptime('%d/%m/%Y-%T.%3N', (split "\n")[0])->strftime('%
+FT%T.%3N') if /ESME_RTHROTTLED/;
}

__END__
Time: 1/9/2015-09:01:43.010
Protocol: SMPP
ESME: ehttp_rknoe
Direction: Outgoing
From: 10.247.231.212/2775
To: 10.247.231.212/35173
PDU Type: Full PDU
PDU Length: 16
PDU Data: 00000010800000040000005800029a92
Decode Error 0x00000000
Decoded PDU:
[ smpp hdr 16 octets ]
00000000: 00 00 00 10              command_length: 16
00000004: 80 00 00 04              command_id: 0x80000004 submit_sm_re
+sp
00000008: 00 00 00 58              command_status: 0x00000058
0000000C: 00 02 9A 92              sequence_number: 170642
Time: 1/9/2015-09:02:43.010
Protocol: SMPP
ESME: ehttp_rknoe
Direction: Outgoing
From: 10.247.231.212/2775
To: 10.247.231.212/35173
PDU Type: Full PDU
PDU Length: 16
PDU Data: 00000010800000040000005800029a92
Decode Error 0x00000000
Decoded PDU:
[ smpp hdr 16 octets ]
00000000: 00 00 00 10              command_length: 16
00000004: 80 00 00 04              command_id: 0x80000004 submit_sm_re
+sp
00000008: 00 00 00 58              command_status: 0x00000058 ESME_RTH
+ROTTLED
0000000C: 00 02 9A 92              sequence_number: 170642
Time: 17/9/2015-09:03:43.634
Protocol: SMPP
ESME: ehttp_rknoe
Direction: Outgoing
From: 10.247.231.212/2775
To: 10.247.231.212/35173
PDU Type: Full PDU
PDU Length: 16
PDU Data: 00000010800000040000005800029a92
Decode Error 0x00000000
Decoded PDU:
[ smpp hdr 16 octets ]
00000000: 00 00 00 10              command_length: 16
00000004: 80 00 00 04              command_id: 0x80000004 submit_sm_re
+sp
00000008: 00 00 00 58              command_status: 0x00000058 ESME_RTH
+ROTTLED
0000000C: 00 02 9A 92              sequence_number: 170642
Time: 1/9/2015-09:04:43.987
Protocol: SMPP
ESME: ehttp_rknoe
Direction: Outgoing
From: 10.247.231.212/2775
To: 10.247.231.212/35173
PDU Type: Full PDU
PDU Length: 16
PDU Data: 00000010800000040000005800029a92
Decode Error 0x00000000
Decoded PDU:
[ smpp hdr 16 octets ]
00000000: 00 00 00 10              command_length: 16
00000004: 80 00 00 04              command_id: 0x80000004 submit_sm_re
+sp
00000008: 00 00 00 58              command_status: 0x00000058
0000000C: 00 02 9A 92              sequence_number: 170642
Time: 22/9/2015-09:05:17.007
Protocol: SMPP
ESME: ehttp_rknoe
Direction: Outgoing
From: 10.247.231.212/2775
To: 10.247.231.212/35173
PDU Type: Full PDU
PDU Length: 16
PDU Data: 00000010800000040000005800029a92
Decode Error 0x00000000
Decoded PDU:
[ smpp hdr 16 octets ]
00000000: 00 00 00 10              command_length: 16
00000004: 80 00 00 04              command_id: 0x80000004 submit_sm_re
+sp
00000008: 00 00 00 58              command_status: 0x00000058 ESME_RTH
+ROTTLED
0000000C: 00 02 9A 92              sequence_number: 170642

[download]

Earlier answer: It depends on what you have for"record" delimiters. If the first line is always the time, you could store that in a variable and print it out if you hit your token before the next record starts, or reload the variable with the new time if you hit that first.

The way forward always starts with a minimal test.

In reply to Re: Parsing text string in Perl by 1nickt
in thread Parsing text string in Perl by gbwien

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.