Post by Simon ClubleyPost by k***@gmail.comI 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 ClubleyPost by k***@gmail.comInstead 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 ClubleyHowever, 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.