|
HP OpenVMS Systemsask the wizard |
|
The Question is:
What does this mean "Message number 0078B5DB"?
It is in the output of SHOW DEV/FULL, which follows:
Printer NLP10:, device type LP11, is online, allocated, record-oriented device,
carriage control, device is spooled through an intermediate device.
Error count 0 Operations completed 0
Owner process "SYMBIONT_2" Owner UIC [SYSTEM]
Owner process ID 00000416 Dev Prot S:RWPL,O:RWPL,G,W
Reference count 1 Default buffer size 0
Page width 0 Page Length 66
No Carriage_return Formfeed Lowercase
No Passall No Wrap No Printall
No Fallback Tab Truncate
No Sixels No Bitmapped No Polled
Message number 0078B5DB
Intermediate device: DRA0:
Associated queue: CS
The nlp10 device is created by multinet 4.0C with the following command in a
command file:
$ SysMan IO Connect NLP10:/NoAdapter/Driver=NLPDriver
Since getting a new alpha with VMS7.2-1 using the same multinet procedures we
get the above message. The NLPDriver is identical from the old system to the
one that is on the newer system, I did a diff on them. VMS7.2 is running on
the older system.
The net effect is that SHOW PRINTER and SET PRINTER do not work. with SHOW
PRINTER I get the following error:
%CLI-F-SYNTAX, error parsing 'IDSTRING'
-CLI-E-ENTNF, specified entity not found in command tables
With SET PRINTER no matter the qualifier I get:
%CLI-F-SYNTAX, error parsing 'RESET'
-CLI-E-ENTNF, specified entity not found in command tables
Unfortunately those are the only printer devices we have so I can't try those
commands with other printer devices. And yes I have tried to redo the command
tables, the clds we have for set and show are from march 1999.
The Answer is : Please contact MultiNet support for assistance with MultiNet. As for the errors with SET PRINTER, it would appear your DCLTABLES are corrupt. One common cause of this is an errant version of the DCLTABLES.EXE file located in SYS$SPECIFIC, with a subset of the DCL command verbiage in it. If MultiNet is making changes to the DCLTABLES SET PRINTER, then the OpenVMS Wizard would encourage you reinstall MultiNet to see if that will reset the CLD problem, then to contact MultiNet support for any available update to the associated CLD file.
|