You could redirect STDERR for the time you make calls into that module. 

package Foo;

sub foo { warn "blorf!" }
1;

[download]
#!/usr/bin/perl

use Foo;

use strict;
use warnings;

sub call (&);

call {
    Foo::foo();
};

if ($@) {
    warn "foo reported: '$@'\n";
}

## subs
#

sub call (&) {
    my $coderef = shift;
    my $message;
    open my $fh , '>&', \*STDERR;
    close STDERR;
    open  STDERR, '>',  \$message;
    $coderef->();
    open STDERR, ">&",  $fh;
    $@ = $message;
}
__END__
foo reported: 'blorf! at Foo.pm line 3.
'

[download]

That way all you have to do is wrap the places where you call into Sybase::CTlib into a block and dispatch that to the call() function.

In reply to Re: How can I catch a Server message displayed in Sybase::CTlib module by shmem
in thread How can I catch a Server message displayed in Sybase::CTlib module by goutam_monk

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.