Conference vaxaxp::alphanotes

40.0. "Trying to disable an offline message in opa0..." by FORAT::JLS (Are we in the same ship?) Mon Feb 03 1997 14:29

	Hello,

	I'm trying to disable the message "Device LRA0 is offline" to
	appear in opa0 terminal.But after the following setup,although
	USUALLY it doesn't appear...it has appeared twice in the console
	terminal (scrolling down the terminal).Any idea about?

	Thanks in advance,
						/jls (josep lluis sole)

	data: alphastation 200 4/166 with openvms alpha v6.2
		
	sylogicals.com: 
	---------------
	$ define/system opc$opa0_enable "false"
	$ define/system opc$opa0_classes central,tapes,disks,cards,network,
	  cluster,security,license,oper1,oper2,oper3,oper4,oper5,oper6,oper7,
	  oper8,oper9,oper10,oper11,oper12

	systartup_vms.com
	-----------------

	$ deass/system/super opc$opa0_enable
	$ stop OPCOM
	$ �sys$system:startup opcom

	decw$private_apps_setup.com
	---------------------------

	decw$console_selection == "enable"	
	
	$ sho log opc*

	lnm$system_table

	opc$opcom_started="TRUE"

	opc$enable_opa0_classes ="central,tapes,disks,cards,network,
	  cluster,security,license,oper1,oper2,oper3,oper4,oper5,oper6,oper7,
	  oper8,oper9,oper10,oper11,oper12"

	opc$opa0_classes ="central,tapes,disks,cards,network,
	  cluster,security,license,oper1,oper2,oper3,oper4,oper5,oper6,oper7,
	  oper8,oper9,oper10,oper11,oper12"

	$ sho queue cua$hcopybw   => on LRA0 device.

	

	Problem: 

	Usually when the printer queue cua$hcopybw is "stalled" (missing 
	paper) it appears the corresponding message in the operator.log
	file ( device lra0 is offline) several times,untill it has paper
	again......WITHOUT ANY MESSAGE SCROLLING DOWN THE CONSOLE TERMINAL.
	But it has happened twice (in 2 different systems),instead it's 
	disabled,the message has appeared in opa0,scrolling down the 
	console terminal.....

   I will assume the message you are seeing is an OPCOM and not one of
   the various driver broadcast messages some drivers can send out...

   There is no need to STOP OPCOM in this fashion, and doing so is
   dangerous, undocumented, and unsupported practice. 

   The definition of the logical names in SYLOGICALS should be entirely
   sufficient for your purposes.  Set up the logicals, reboot, and you
   should be in business.

   If you want a fallback or if you want to shut off OPCOM output on
   the console on a running system, use the syntax:

	$ SET PROCESS/PRIV=ALL ! OPER is needed, not sure what else
	$ DEFINE/USER SYS$COMMAND OPA0:
	$ REPLY/DISABLE

   You'll also want to take a look at the sys$manager:DECW$CONSOLE.COM
   command procedure available on recent DECwindows releases.

   If you believe the logical names are set up correctly and have
   rebooted (or explicitly disabled OPA0: via REPLY/DISABLE), then
   please provide an example of the OPCOM message seen, and the contents
   of the SYLOGICALS.COM command procedure, and log a QAR or IPMT.

   A more appropriate notes conference for OpenVMS notes questions (and
   particularly for those questions not directly related to porting) is
   VAXAXP::VMSNOTES.

    
    Thanks Steve for your comments,
    
    						/jls.

    
    Well, OPA0: should be displaying in a Window Console Messages window,
    and NOT on the glass TTY pop up display...  Right?