[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:NAS Message Queuing Bus
Notice:KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:PAMSRC::MARCUSEN
Created:Wed Feb 27 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2898
Total number of notes:12363

2887.0. "Message Operation error, Status -255 " by NNTPD::"[email protected]" (Farhad Ghavami) Thu May 22 1997 12:33

Does somebody knows, what error with Status -255 means ? I could not find
anything about it.

This error is seen on DEC UNIX platform. The group running on this machine
communicates with another group running on a OpenVMS platform.

Thanks and regards,
Farhad
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
2887.1XHOST::SJZKick Butt In Your Face Messaging !Thu May 22 1997 12:446
    
    where are you seeing the -255 ?  is this returned from a
    pams function ?   all of our error messages are even num-
    bers.  there is no -255.
    
    _sjz.
2887.2Error status -255NNTPD::"[email protected]"Farhad GhavamiFri May 23 1997 05:0822
I know. That why I was wondering and lost!

The exact error message logged in the group log file is as the following:
*************** dmqjourn (13346) timestamp ***************
jrn, message operation error status -255
*************** dmqjourn (13346) timestamp ****************
jrn, journal process for group 38 has exited

I customer could give me more significative info concerning the error. The
customer told me that they had a problem with login on the system that obliged
them to reboot the system some weeks ago. The error has manifested itself
after the reboot!

Today, I talked with the customer. Yesterday, they have moved all DQF files
elsewhere and since then the system works without problem. Perhaps DQF files
are corrupted oncemore!

Farhad.

PS: The customer is the last one with corrupted journal files last year in
Germany.
[Posted by WWW Notes gateway]
2887.3XHOST::SJZKick Butt In Your Face Messaging !Fri May 23 1997 09:088
    
    -255 is definitely corrupt journal files.  however,  their
    journal files are probably just fine.  there was a problem
    in V3.2A which was not fixed in the ECO where the  journal
    process thinks the file is corrupt even though it  is  not.
    the problem is fixed in V4.0.
    
    _sjz.