System Error Message

[Nahmad_1]

Hi There

I am getting a Error message on rge Console as under:

Reply received on CMBUR1 from user System at CMBUR1 Batch 03:38:27
OWL-I-MSG, CMBUR1-%System-F-IVCHAN, invalid I/O channel
Module WSC-SND-NICE_REQ _rel PC-0000006B Abs PC-26C4D8F
Module WSC-BLD-MSG

Where CMBUR1 is our node and OWL is the release build procedure.

I have already rebooted the system but it is not gowing away. How can I get ridof it anyway ?

Thanks in adavance

Nahamd

[Steven Schweda]

> OWL-I-MSG [...]

Whose software is that? Yours?

> How can I get ridof it anyway ?

First find the cause. Then fix the problem.

[Nahmad_1]

Hi

Owl is our local s/w but this is a false message as there is no batch running for owl. There is no reason at to send this message for each and every 5 minutes which is enoying. I want to just get rid of it.

Nahmad

[Steven Schweda]

> There is no reason at to send this message
> [...]

Apparently the software has a different
opinion.

> Owl is our local s/w [,,,]

So how much help did you expect from people
who know absolutely nothing about it? (Well,
I suppose that we can guess its name, so
that's not _absolutely_ nothing.)

> but this is a false message [...]

That's one opinion.

> as there is no batch running for owl.

Again, that's one opinion, and I see no
evidence one way or another. How do you
know?

[Hoff]

Nahmad, use the OpenVMS debugger on the code involved (assuming it's a program), and investigate and report the exact details of the particular error.

Prove the location of the error is outside of your OWL code.

Rule of thumb: it's always going to be a bug in your code until and unless you can provide justification or proof tjhat it's not a bug in your code. One of the best ways to prove that it's not your bug is to debug your own code, and to create a reproducer for the error.

An IVCHAN error can have a variety of triggers. Given the frequency with which the OpenVMS I/O system is used, bugs are comparatively rare. There can certainly be bugs, but these are rare and usually unique. (Which also means a reproducer can really help.) Bugs in site-specific application code are far more common.

[Jon Pinkley]

Nahmad,

I think you will have much more luck asking the developers of your software than asking here.

This message is most likely coming from a reply command running in the context of a detached process. I.e. a process created with a command something like the following:

$ run sys$system:loginout -
/privilege='privs' -
/detached -
/input='input_command' -
/output='logfile' -
/process='procname'

Either this message has always been sent every 5 minutes, or someone has broken something, probably due to their lack of understanding of how the software works.

When did this start, and what changes were made around that time?

The developers would be the most likely to know what the proper fix is.

Good luck,

Jon

[Willem Grooters]

[quote]
I have already rebooted the system but it is not gowing away.
[/quote]
Duh. What would you expect? VMS <> Windows.
The problem is in your software, not in VMS.
(Not that it would be solved that way when it were a Windows environment, but stanger things seem to happen there)

(Sorry, I couldn't resist)

It would be easier if you pasted the message in a text file and uploaded that.
For a more positive edge, this may ring a bell:
I've seen the same error (Invalid channel) when interrupting (CTRL-Y) a PIPE command sequence. It's not impossible that your software sends a command to JobControl to be executed in batch (hence the message).

Indeed - you should talk to the developers