Discussion:
"NONAME-E-NOMSG" -- in TCPIP commands EXIT_STATUS
(too old to reply)
k***@gmail.com
2013-09-17 12:16:17 UTC
Permalink
I am facing some issue with OpenVMS Help message database. I'm unable to map the exit_status of commands through DCL scripting. receiving the error Eg: "%NONAME-E-NOMSG, Message number 0764D022"
Instead of "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation"

We are using SET MESSAGE ECTIP$MSG.EXE for temporary resolution for that particular session.
Can anyone help us how to load the TCPIP$MSG.EXE to the permanent HELP/MESSAGE database.

Please help us ASAP.Thanks in advance..
Simon Clubley
2013-09-17 17:02:03 UTC
Permalink
Post by k***@gmail.com
I am facing some issue with OpenVMS Help message database. I'm unable to map the exit_status of commands through DCL scripting. receiving the error Eg: "%NONAME-E-NOMSG, Message number 0764D022"
Instead of "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation"
We are using SET MESSAGE ECTIP$MSG.EXE for temporary resolution for that particular session.
Can anyone help us how to load the TCPIP$MSG.EXE to the permanent HELP/MESSAGE database.
Please help us ASAP.Thanks in advance..
What is the real root problem you are trying to fix here ?

A few days ago, the problem was that a file could not be transferred from
VMS to Linux. A number of suggestions were made in response to that query,
but we never heard anything back from the OP (you?).

Now, you seem to be focused on how to map the error message into text,
instead of focusing on removing the problem causing the error message
in the first place, and that seems to be a odd goal.

However, in answer to your direct question, the message descriptions are
held in sys$help:*.msghlp$data; however tcpip.msghlp$data does not seem to
have any ssh related entries in it on the system I am looking at.

Type "help help/message" at the DCL prompt for further information and
make sure you first make copies of any files you might change in case you
make a mistake.

Simon.
--
Simon Clubley, ***@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world
hb
2013-09-17 18:49:50 UTC
Permalink
Post by Simon Clubley
Post by k***@gmail.com
I am facing some issue with OpenVMS Help message database. I'm unable to map the
exit_status of commands through DCL scripting. receiving the error Eg:
"%NONAME-E-NOMSG, Message number 0764D022"
Post by Simon Clubley
Post by k***@gmail.com
Instead of "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation"
We are using SET MESSAGE ECTIP$MSG.EXE for temporary resolution for that particular session.
Can anyone help us how to load the TCPIP$MSG.EXE to the permanent HELP/MESSAGE database.
Please help us ASAP.Thanks in advance..
What is the real root problem you are trying to fix here ?
I dunno. The OP seems to use EXIT or f$message() with a message code.
The OP seems to think that its output "%NONAME-E-NOMSG, Message number
0764D022" (or "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer
operation") comes from or is constructed from a help file (HELP/MESSAGE
database). As we know, it comes from a message file. The OP doesn't know
that there are 3 types of message files, which hold the messages:
system, process an image specific ones. The system messages do not
contain the TCPIP messages. It seems the OP wants to add the TCPIP to
the system messages. That is to rebuild sys$message:sysmsg.exe to
include the messages from TCPIP$MSG.EXE. That may be possible. But I
don't think there is any supported way to do this. But if ASAP includes
some EURs or $$$ I could convince myself to hack something together.

SET MESSAGE is the supported way to change/add the process specific
messages. And that's all the OP can and has to do, although it seems the
OP knows this but is not happy with this solution. I dunno what the OP
expects, here.
Post by Simon Clubley
However, in answer to your direct question, the message descriptions are
held in sys$help:*.msghlp$data; however tcpip.msghlp$data does not seem to
have any ssh related entries in it on the system I am looking at.
The lack of ssh related entries looks like a different problem to me.
Simon Clubley
2013-09-17 19:20:24 UTC
Permalink
Post by k***@gmail.com
Post by Simon Clubley
Post by k***@gmail.com
I am facing some issue with OpenVMS Help message database. I'm unable to map the
"%NONAME-E-NOMSG, Message number 0764D022"
Post by Simon Clubley
Post by k***@gmail.com
Instead of "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation"
We are using SET MESSAGE ECTIP$MSG.EXE for temporary resolution for that particular
session.
Post by Simon Clubley
Post by k***@gmail.com
Can anyone help us how to load the TCPIP$MSG.EXE to the permanent HELP/MESSAGE
database.
Post by Simon Clubley
Post by k***@gmail.com
Please help us ASAP.Thanks in advance..
What is the real root problem you are trying to fix here ?
I dunno. The OP seems to use EXIT or f$message() with a message code.
The OP seems to think that its output "%NONAME-E-NOMSG, Message number
0764D022" (or "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer
operation") comes from or is constructed from a help file (HELP/MESSAGE
database). As we know, it comes from a message file.
Yes, the way that was written confused the hell out of me. The OP started
by asking about getting the error text for a specific message number and
then moved to asking about the descriptions database which explains what
might be causing the error.

I got the feeling the OP was trying to get the system to explain what is
wrong with the command procedure/script/program and then got massively
confused along the way.

To the OP, if that was your goal, then review the answers from a few
days ago. I, for one, gave you some specific network connectivity
test ideas to try out (assuming you are the same OP).
Post by k***@gmail.com
Post by Simon Clubley
However, in answer to your direct question, the message descriptions are
held in sys$help:*.msghlp$data; however tcpip.msghlp$data does not seem to
have any ssh related entries in it on the system I am looking at.
The lack of ssh related entries looks like a different problem to me.
Agreed; it looks like HP never updated the descriptions database when
ssh support was added. This was on a V8.3 Alpha system; I don't know if
it's different for V8.4.

Simon.
--
Simon Clubley, ***@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world
V***@SendSpamHere.ORG
2013-09-17 20:55:05 UTC
Permalink
Post by Simon Clubley
Post by k***@gmail.com
I am facing some issue with OpenVMS Help message database. I'm unable to map the exit_status of commands through DCL scripting. receiving the error Eg: "%NONAME-E-NOMSG, Message number 0764D022"
Instead of "%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation"
We are using SET MESSAGE ECTIP$MSG.EXE for temporary resolution for that particular session.
Can anyone help us how to load the TCPIP$MSG.EXE to the permanent HELP/MESSAGE database.
Please help us ASAP.Thanks in advance..
What is the real root problem you are trying to fix here ?
A few days ago, the problem was that a file could not be transferred from
VMS to Linux. A number of suggestions were made in response to that query,
but we never heard anything back from the OP (you?).
Now, you seem to be focused on how to map the error message into text,
instead of focusing on removing the problem causing the error message
in the first place, and that seems to be a odd goal.
However, in answer to your direct question, the message descriptions are
held in sys$help:*.msghlp$data; however tcpip.msghlp$data does not seem to
have any ssh related entries in it on the system I am looking at.
Type "help help/message" at the DCL prompt for further information and
make sure you first make copies of any files you might change in case you
make a mistake.
I think he's complaining about "$SET MESSAGE SYS$MESSAGE:TCPIP$MSG.EXE" not
returning the text of the message. Of course, he should continue to ask us
questions without providing us with any of the DCL code he's complaining to
us about.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.
Loading...