PI77577: MESSAGE "GETEOLCHAR: BROWSER OS NOT LISTED:AGENTNAME/0.1LIBWWW-PERL/5.803" REPORTED IN THE EVENT.LOG

APAR status

• Closed as program error.

Error description

• -The message "GetEolChar: Browser OS not
  listed:AgentName/0.1libwww-perl/5.803" is reported in the
  event.log each time a user is downloading a Synergy object
  (source) with a Perl script/trigger using the Change Perl API
  function DatabaseGetObject.
  -This message is NOT reported when the user is using the exact
  same script/trigger, and downloading a CR's attachment.
  
  
  To reproduce, use the following script (you can modify it to use
  as a trigger too):
  #######
  #!/usr/local/ccm/cs531/jetty/webapps/change/WEB-INF/perl/ratlper
  l -w
  use strict;
  my $username="admin";
  my $passwd="XXX";
  my $role="Admin";
  my $database="/usr/local/ccm/ccmdb/ccm7210";
  my $url="http://192.168.0.27:8600/change";
  use utf8;
  use ChangeSynergy::csapi;
  my $csapi = new ChangeSynergy::csapi();
  $csapi->setUpConnection($url);
  my $aUser = $csapi->Login($username, $passwd ,$role,$database);
  my $attachment_cvid = 11319; # use a CVID of a Synergy source to
  reproduce the message
  my $filename = "test.txt";
  my $file_attach  = $csapi->DatabaseGetObject($aUser,
  $attachment_cvid);
    open(OUTPUT, ">$filename");
    print(OUTPUT $file_attach->getResponseByteData());
    close(OUTPUT);
  print "ATTACHMENT number filename: \"$filename\"\n\n\n";
  #######
  (use your own values to adapt this script to your own
  environment)
  
  -If for "my $attachment_cvid", you use the CVID of a CR's
  attachment, then there is no message reported.
  -If for "my $attachment_cvid", you use the CVID of a standard
  Synergy source object, then the message is reported in the
  event.log.
  
  The message by itself is harmless, but if you use such a trigger
  very often, the event.log could be filled up with these
  messages.
  
  
  This APAR's goal is to move the message from normal logs to
  debug logs.
  So the message is displayed only when debug mode is turned on
  for the event log.
  

Local fix

• Workaround:
  Update the entry "BROWSER_OS" in the pt.cfg, and append below
  string to the existing values:
  perl:LF
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * -The message "GetEolChar: Browser OS not                     *
  * listed:AgentName/0.1libwww-perl/5.803" is reported in the    *
  * event.log each time a user is downloading a Synergy object   *
  * (source) with a Perl script/trigger using the Change Perl    *
  * API                                                          *
  * function DatabaseGetObject.                                  *
  * -This message is NOT reported when the user is using the     *
  * exact                                                        *
  * same script/trigger, and downloading a CR's attachment.      *
  *                                                              *
  *                                                              *
  * To reproduce, use the following script (you can modify it to *
  * use                                                          *
  * as a trigger too):                                           *
  * #######                                                      *
  * #!/usr/local/ccm/cs531/jetty/webapps/change/WEB-INF/perl/rat *
  * lper                                                         *
  * l -w                                                         *
  * use strict;                                                  *
  * my $username="admin";                                        *
  * my $passwd="XXX";                                            *
  * my $role="Admin";                                            *
  * my $database="/usr/local/ccm/ccmdb/ccm7210";                 *
  * my $url="http://192.168.0.27:8600/change";                   *
  * use utf8;                                                    *
  * use ChangeSynergy::csapi;                                    *
  * my $csapi = new ChangeSynergy::csapi();                      *
  * $csapi->setUpConnection($url);                               *
  * my $aUser = $csapi->Login($username, $passwd                 *
  * ,$role,$database);                                           *
  * my $attachment_cvid = 11319; # use a CVID of a Synergy       *
  * source to                                                    *
  * reproduce the message                                        *
  * my $filename = "test.txt";                                   *
  * my $file_attach  = $csapi->DatabaseGetObject($aUser,       *
  * $attachment_cvid);                                           *
  * Â  open(OUTPUT, ">$filename");                              *
  * Â  print(OUTPUT $file_attach->getResponseByteData());       *
  * Â  close(OUTPUT);                                           *
  * print "ATTACHMENT number filename: \"$filename\"\n\n\n";     *
  * #######                                                      *
  * (use your own values to adapt this script to your own        *
  * environment)                                                 *
  *                                                              *
  * -If for "my $attachment_cvid", you use the CVID of a CR's    *
  * attachment, then there is no message reported.               *
  * -If for "my $attachment_cvid", you use the CVID of a         *
  * standard                                                     *
  * Synergy source object, then the message is reported in the   *
  * event.log.                                                   *
  *                                                              *
  * The message by itself is harmless, but if you use such a     *
  * trigger                                                      *
  * very often, the event.log could be filled up with these      *
  * messages.                                                    *
  *                                                              *
  *                                                              *
  * This APAR's goal is to move the message from normal logs to  *
  * debug logs.                                                  *
  * So the message is displayed only when debug mode is turned   *
  * on                                                           *
  * for the event log.                                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This is fixed in Rational Change 5.3.1.1 ifix 11
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC CHANGE

• Fixed component ID

  5724V87CG

Applicable component levels

• R531 PSY

     UP