topic VIQ problem in Operating System - OpenVMS

VIQ problem

UareTERMINATED — Tue, 13 Jul 2004 04:05:54 GMT

Hello

I got the follwing message
Event of class ERROR received from entity MD.
%MD-E-NORESPNSE, MD could not generate a response
-VIQ-E-NOSUCHCHAN, No such channel assigned.

PML> help VIQ-E-NOSUCHCHAN
VIQ-E-NOSUCHCHAN

No such channel assigned.

Facility: VIQ

Severity: Error

Explanation: A channel number has been specified which has not
been assigned.

User Action: Assign channel prior to any other I/O function calls
or supply the correct channel.

The problem is : I don't understand what i have to do in order to check what, and how to fix it.

Re: VIQ problem

Hein van den Heuvel — Tue, 13 Jul 2004 09:09:28 GMT

The messages and command you show certainly look like VMS, but there is not a single VMS native error or standard tool in the picture.

Even the NOSUCHCHAN is NOT an OpenVMS native message, but something from a layered product/applicaitons.

You need to work with the provider of the applicaition to create additional meaning to those words.

What is 'PML', what is 'MD', what is 'VIQ'?

Looks like a file was not found or something like that deep below. If this was happenign on my VMS box and if I had no other information to help me, then my tool of choice would be: SET WATCH FILE/CLA=MAJOR and re-run the program. Now carefully watch the status message come by and hope to recognize directories and files and stuff in there.

Next tool might be a RUN/DEBU and SET BREAK/EXCEPT, hoping to learn from routines names and stack context when and where the error happens (hoping it is signalled).

Finally, with the debugger, STEP IN and OVER routines to get closer and closer to a routine returning an error. Tedious!

hth,
Hein.

Re: VIQ problem

UareTERMINATED — Tue, 13 Jul 2004 09:15:18 GMT

huuummm!!!

That's quite not easy. but i'll try.

Thanks for your first approach

Re: VIQ problem

Peter Hofman — Tue, 13 Jul 2004 14:12:58 GMT

I think you posted your question in the wrong place. It is not an OpenVMS issue, but an application issue.

The solution of your problem is:

Contact the supplier of the system (and that is not the hardware vendor). You'll probably know which company.
They have a support desk.
They can check it and fix it (at least if you have a support contract).