topic Re: Error Code In Print Queue in Operating System - OpenVMS

Error Code In Print Queue

Ken Reighard — Thu, 02 Jun 2005 10:10:30 GMT

My client is printing to a Zebra 140XI Printer. A label is missing and this message appears when the print queue is examined?
Does anyone know what %NONAME-E-NOMSG, Message number 07649FA2 is? Is the code something from the printer?

Thanks

[WMS,W1BELLS]BELLS>sh que wms$cross/all/full
Server queue WMS$CROSS, idle, on EVIE::, mounted form DEFAULT
/BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[1,4] /PROCESSOR=TCPIP$LR

Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
620 LBLCROSSCTNSHIP4278650001
W1BELLS 4 Retained on error
%NONAME-E-NOMSG, Message number 07649FA2
Submitted 2-JUN-2005 07:19:56.36 /FORM=DEFAULT /PRIORITY=100
File: _$1$DKC2:[WMS.WELLS.W1BELLS.TRANS]LBLCROSSCTNSHIP4278650001.;1
Completed 2-JUN-2005 07:20:19.88 on queue WMS$CROSS

******************************************************************************************

Re: Error Code In Print Queue

Volker Halle — Thu, 02 Jun 2005 11:00:49 GMT

Ken,

07649FA2 does not seem to be a valid OpenVMS system service failure or status code.

Which processor is operating this queue ? I do not recognize the name: TCPIP$LR in your SHO QUE/FULL/ALL output. Does SYS$SYSTEM:TCPIP$LR.EXE exist on your system ?

Volker.

Re: Error Code In Print Queue

Karl Rohwedder — Fri, 03 Jun 2005 00:37:41 GMT

The error translates to:
Error 07649FA2 (%D124034978) located in SYS$COMMON:[SYSMSG]TCPIP$MSG.EXE;1
%TCPIP-E-LPD_FILERROR, file error !AS

Pls. check chapter 24 of the TCPIP mgmt. manual at: http://h71000.www7.hp.com/doc/732final/6526/6526pro.HTML
There are some hints on getting debug info and OPCOM messages to further analyze your problem.

regards Kalle

Re: Error Code In Print Queue

Edwin Gersbach_2 — Fri, 03 Jun 2005 00:48:20 GMT

Message %X07649FA2 is:
%TCPIP-E-LPD_FILERROR, file error !AS

The !AS indicates that this message is usually formatted with FAO system directive and some additional text is supplied there. Unfortunately this additional information is lost.

Anyway, it seems that the line printer daemon has problems with a file. If you have turned on auditing there might be something in there. Also check the error log for disk read errors.

Edwin