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

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

523.0. "Redefine operator classes OPER1 - OPER12" by COMICS::JUDD (Geoff Judd. UK TSC. Viables, Basingstoke) Thu Apr 24 1997 14:01

Hi,
  I have a customer who wants to be able to change the names of the OPER1 to
OPER12 operator classes. He can obviously define a logical name to be used in a
Reply command but the original class names still come out in the Opcom messages.
I have looked through the source code for Opcom and the names of the operator
classes are defined as messages in the system message file. Opcom and Reply use
sys$getmsg to get the messages and then build a table of class names. 
Therefore if the message file could be modifed to change the text of the
messages, the class names could be changed. This could be done by creating a
message file and then using SET MESSAGE to define the new messages. However this
will not work for the OPCOM process because it runs as a detached process
without DCL mapped. 

Can anyone think of anyway I can change the classes in Opcom ? 

Thanks in advance,

Geoff Judd.

T.R	Title	User	Personal Name	Date	Lines
523.1		AUSS::GARSON	DECcharity Program Office	`Sun Apr 27 1997 23:06`	8
	re .0 >Can anyone think of any way I can change the classes in Opcom ? Not in this conference. (-: If the customer is not running the latest version of VMS perhaps check release notes in case such a feature has appeared.
523.2	No Supported Mechanism	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Apr 28 1997 10:35`	11
	There is no supported way to do this. The customer would need to patch the particular message file used by OPCOM, and re-patch it after OpenVMS upgrades -- I'd recommend patching an OPCOM-private version of the message file, and not the real one. (This may also mean patching OPCOM, or at least tweaking some logical names around the OPCOM startup.) If the customer wishes to pursue this, I'd recommend a suggestion QAR or IPMT.