📄 lpsmsg.msg
字号:
NONETMBX <Remote Server Management requires NETMBX privilege>!++! Used by RSM - RD! GENERATED BY: Remote Server Management! DISPLAYED TO: remote server manager! CAUSE: RSM was run without NETMBX privilege! USER ACTION: set proc/priv=netmbx then try again! Author: RJD!--UNDERLEN <The minimum required terminal page length is 24 lines>!++! Used by RSM - RD! GENERATED BY: Remote Server Management! DISPLAYED TO: remote server manager! CAUSE: Terminal page length is less than 24 lines! USER ACTION: Increase the page length then try again! Author: RJD!--.SEVERITY ERRORNOACTJOB <No job currently active on print server>!++! Generated By: Server management ( In Client )! Displayed To: Server Manager! Cause: User issued SHOW ACTIVE JOB CHARACTARISTICS! When no job was active! User Action: None! Author: J.Z.W.!--.SEVERITY ERRORRSMDISC <Error occurred - connection to print server lost>!++! Generated By: Remote Server management ! Displayed To: Server Manager! Cause: The connection to the print server was broken. This! could be because the print server was turned off or! the network link was broken.! User Action: Check if the print server is still operating, if so! try starting up a remote management process. If this! fails, it is probably a network problem. If the print! server has halted then reboot.! Author: RJD!--.SEVERITY ERRORDECNETOFF <DECnet is off - Server management requires DECnet be on>!++! GENERATED BY: Network service! DISPLAYED TO: Server Manager! CAUSE: DECnet is off on supporting host! USER ACTION: Startup DECnet then try again! AUTHOR: RJD 10/20/86!--RSMNETERR <Unexpected network error>!++! GENERATED BY: Remote Server Management! DISPLAYED TO: Server manager! CAUSE: Unexpected network error received during initial connect! to print server! USER ACTION: try again - if condition persists submit an SPR! AUTHOR: RJD 10/20/86!--.SEVERITY WARNINGATOPMN <Attempting to open menu file>!++! GENERATED BY: Server Management! DSIPLAYED TO: Server Manager! CAUSE: Current inability to open lpsmnu.eng file! USER ACTION: User must identify the underlying problem and then rectify it! 1) If the server's node number is not in the supporting! hosts network database, add it! 2) If the lpsmnu.eng file is missing, get it! 3) Use remote server management to point the server to a! supporting host whose environment is more favorable ! Once the problem is rectified, the menu will come up! Author: JZW 02/05/87!--.SEVERITY WARNINGEVTLOGDISAB <Event logging disabled - event log not initialized>!++! GENERATED BY: Server Management! DISPLAYED TO: Server Manager! CAUSE: Event logging was disabled when user attempted ! to initialize event log.! USER ACTION: Enable event log and then re-try Initialize Event log command.! Author: MJD; 03/13/87!--.SEVERITY FATAL.SEVERITY FATALLJCEXPERR <Laps-Interrupt Process error, reason = !AS>/FAO_COUNT=1!++! GENERATED BY: LAPS Job Controller! DISPLAYED TO: Server Manager! CAUSE: LAPS Job Controller's Interrupt component encountered ! an error during startup or while processing a client's ! DELETE/ENTRY request.! USER ACTION: Reboot the PrintServer. Please submit an SPR. ! AUTHOR: MJD, 3/16/86!--!**********! The following message codes are generated by PostScript!**********.BASE LPS$$LPS__POST__BASE .SEVERITY INFORMATIONALIDLE <Idle>!++! GENERATED BY: Postscript! DISPLAYED TO: Server management! CAUSE: Request for status of Print engine! USER ACTION: None! AUTHOR: J. Z. Wolf!--ACTIVE <Active>!++! GENERATED BY: Postscript! DISPLAYED TO: Server management! CAUSE: Request for status of print controller! USER ACTION: none! AUTHOR: J. Z. Wolf!--.SEVERITY WARNINGEXITSRVR <exitserver has been executed - permanent state may be changed>!++! GENERATED BY: PostScript! DISPLAYED TO: Operator, User! CAUSE: exitserver operator has been successfully invoked! USER ACTION: Unauthorized users of this operator could change! the state of the print server in such a way as to have a! negative impact on following jobs.! AUTHOR: WEM!--.SEVERITY ERRORFLUSHING <Rest of Job (to EOJ) will be ignored>!++! GENERATED BY: PostScript! DISPLAYED TO: User! CAUSE: Some error or other event has occurred which is causing! PostScript to ignore the rest of the job.! USER ACTION: None. The message(s) which precede this message should! provide clues as to why the job is being flushed.! AUTHOR: WEM!--.SEVERITY WARNING!++! POSTSCRIPT MESSAGES: THIS APPLIES TO THE FOLLOWING MESSAGES!! GENERATED BY: PostScript! DISPLAYED TO: User! CAUSE: An error has occurred within the PostScript job.! USER ACTION: If this error occurs while printing a file of a data-type! other than PostScript, It indicates an error in the translation! process; in this case, an SPR should be submitted. If! the error occurs while printing a PostScript file, the! PostScript program (or the program which generated the! PostScript program) is in error; the problem should be! fixed and the job resubmitted.! AUTHOR: WEM!--DICTFULL <dictfull: No more room in dictionary - offending command is !AS>/FAO_COUNT=1DICTSTKOV <dictstackoverflow: Too many begins>DICTSTKUF <dictstackunderflow: Too many ends>EXECSTKOV <execstackoverflow: exec nesting is too deep - offending command is !AS>/FAO_COUNT=1INTERUPT <interrupt: The job has been interrupted>INVACC <invalidaccess: Attempt to access restricted object or capability - offending command is !AS>/FAO_COUNT=1INVEXIT <invalidexit: exit not in loop>INVFILACC <invalidfileaccess: Bad file access string - offending command is !AS>/FAO_COUNT=1INVFONT <invalidfont: Bad font name or dictionary - offending command is !AS>/FAO_COUNT=1INVREST <invalidrestore: Improper restore - offending command is !AS>/FAO_COUNT=1IOERROR <ioerror: System I/O error occurred - offending command is !AS>/FAO_COUNT=1LIMCHK <limitcheck: Implementation limit exceeded - offending command is !AS>/FAO_COUNT=1NOCURPT <nocurrentpoint: Path is empty - offending command is !AS>/FAO_COUNT=1RANGECHK <rangecheck: Argument out of bounds - offending command is !AS>/FAO_COUNT=1STKOFLO <stackoverflow: Operand stack overflow - offending command is !AS>/FAO_COUNT=1STKUFLO <stackunderflow: Operand stack underflow - offending command is !AS>/FAO_COUNT=1SYNERR <syntaxerror: Input ended in string or procedure body - offending command is !AS>/FAO_COUNT=1TIMOUT <timeout: Time limit exceeded>TYPCHK <typecheck: Argument of wrong type - offending command is !AS>/FAO_COUNT=1UNDEF <undefined: Name not known - offending command is !AS>/FAO_COUNT=1UNDFILNAM <undefinedfilename: File not found - offending command is !AS>/FAO_COUNT=1UNDEFRES <undefinedresult: Number overflow or underflow - offending command is !AS>/FAO_COUNT=1UNMATCH <unmatchedmark: Expected mark not on stack - offending command is !AS>/FAO_COUNT=1UNREGIST <unregistered: PostScript has encountered a system error - offending command is !AS>/FAO_COUNT=1VMERROR <VMerror: PostScript virtual memory exhausted - offending command is !AS>/FAO_COUNT=1CFGERROR <configurationerror: !AS - offending command is !AS>/FAO_COUNT=2PSINCONSIST <PostScript controller state is inconsistent>PSQUITOPER <PostScript quit operator has been executed>PSFATALSYS <PostScript fatal error at PC !UL>/FAO_COUNT=1!++! END OF POSTSCRIPT MESSAGES!--!**********! The following codes are all the printer (print engine) conditions!**********.BASE LPS$$LPS__ENG__BASE!++! ENGINE MESSAGES: THIS APPLIES TO THE FOLLOWING MESSAGES!! GENERATED BY: PostScript! DISPLAYED TO: Operator! CAUSE: An engine-related event has been detected.! USER ACTION: Correct the problem in one of the following ways:! (1) follow the instructions on the print engine.! (2) call the key operator (especially if key light is on).! (3) call field service (especially if wrench light is on).! (4) submit an SPR (if error is LPS$_PRTHDWERR).! NOTE: In General:! Informational (-I-) messages indicate the print server will! need normal servicing soon. Call the key! operator or field service.! Warning (-W-) messages can be handled simply by correcting! the problem. Excessive occurrence of one! of these conditions should be reported to! field service.! Error (-E-) messages may require the print server to be! powered off and back on - field service! should be notified. These errors may be! hardware or software.! Fatal (-F-) messages indicate the print server has had some! serious failure. Typically the print server! will have to be powered off. Sometimes! powering the server off then on will cause! the problem to go away. Field service! should be always be called when one of these! errors are seen.! AUTHOR: WEM!-- .SEVERITY SUCCESS ! codes which reflect normal operationPRNTREDY <Print Engine ready>!++! Used by RSM - Used by other components??? - RD! GENERATED BY:! DISPLAYED TO:! CAUSE: ! USER ACTION: ! Author:!--PRNTERRCORR <Print Engine error has been corrected>!++! GENERATED BY: PostScript! DISPLAYED TO: Operator! CAUSE: Previous printer condition has been cleared! USER ACTION: None! Author: WEM!--.SEVERITY INFORMATIONAL ! codes which reflect the printer may ! need attention soon.MAINT50K <Print Engine 50,000 page maintenance required>MAINT100K <Print Engine 100,000 page maintenance required>MAINT200K <Print Engine 200,000 page maintenance required>OILLOW <Print Engine oil supply low>TNRLOW <Print Engine toner supply low>WARMUP <Print Engine is in warmup state>!+++! Following codes are NOT used by the LPS-40 software!!future...!TRAYSWI <Switching to alternate paper source>!! Following conditions are NOT in the LN02-V print engine specification and are! therefore NOT reported by the LPS-40 software!!DEVREPL <Print Engine developer needs replacement>!DRMREPL <Print Engine drum needs replacement>!STPLSLOW <Print Engine staples supply low>!---.SEVERITY WARNING ! codes which reflect the printer needs ! normal servicingEJECTJAM <Print Engine paper eject section is jammed>TRANSJAM <Print Engine transport section is jammed>UPTRAYJAM <Print Engine upper paper tray is jammed> ! Text modified 29-Jun-1988 ! EDIT: ! PCO: 335 ! AUTHOR: ELLOTRAYJAM <Print Engine lower paper tray is jammed> ! Text modified 29-Jun-1988 ! EDIT: ! PCO: 335 ! AUTHOR: ELLCITJAM <Print Engine large capacity paper tray is jammed>UPTRAYEMP <Print Engine upper paper tray is empty> ! Text modified 29-Jun-1988 ! EDIT: ! PCO: 335 ! AUTHOR: ELLOTRAYEMP <Print Engine lower paper tray is empty> ! Text modified 29-Jun-1988 ! EDIT: ! PCO: 335 ! AUTHOR: ELLCITEMP <Print Engine large capacity paper tray is empty>COVOPN <Print Engine cover is open>TNRMALADJ <Print Engine toner cartridge setting is incorrect>TRNMALADJ <Print Engine transport path setting is incorrect>FUSMALADJ <Print Engine fusing unit setting is incorrect>FDSTAKJAM <Face down stacker is jammed>FDSTAKFULL <Face down stacker is full>FDSTAKOPEN <Face down stacker cover is open>LCSTAKJAM <Large capacity stacker is jammed>LCSTAKFULL <Large capacity stacker is full>LCSTAKOPEN <Large capacity stacker cover is open>!+! Do not use the following six messages [EL 29-Jun-1988]!-MBSTAKJAM <Mailbox stacker is jammed>MBSTAKFULL <Mailbox stacker is full>MBSTAKOPEN <Mailbox stacker cover is open>DUPSTAKJAM <Duplex stacker is jammed>DUPSTAKFULL <Duplex stacker is full>DUPSTAKOPEN <Duplex stacker cover is open>!+!-OFFLINE <Print Engine has gone off line>PRNOTRDY <Print Engine is not ready>TNREND <Print Engine toner supply is exhausted>LCITCOVOPEN <Large capacity tray cover is open>!+++! Following conditions are NOT in the LN02-V print engine specification and are! therefore NOT reported by the LPS-40 software!!STPLSEMP <Printer Out of Staples>!---.SEVERITY ERROR ! codes which reflect the printer needs ! professional help.PRHDWERR <Print Engine hardware error: !AS>/FAO_COUNT=1PRUNKERR <Print Engine unknown error status: !UL, !UL>/FAO_COUNT=2.SEVERITY FATAL ! codes which reflect the printer is ! in immed. need of professional helpPOWERERR <Print Engine power supply unit error - FATAL ERROR>DRIVEERR <Print Engine driving unit error - FATAL ERROR>FUSINGERR <Print Engine fusing error - FATAL ERROR>FEEDERR <Print Engine paper feed unit error - FATAL ERROR>OPTICERR <Print Engine optical unit error - FATAL ERROR>FDSTAKERR <Face down stacker unit error - FATAL ERROR>LCSTAKERR <Large capacity stacker unit error - FATAL ERROR>MBSTAKERR <Mailbox stacker unit error - FATAL ERROR>DUPSTAKERR <Duplexer unit error - FATAL ERROR> ! Text modified 29-Jun-1988 ! EDIT: ! PCO: 335 ! AUTHOR: EL.SEVERITY WARNING ! Stopgap LPS20 Service requestPRSERVICE <Printer requires service: code = !UL !UL>/FAO_COUNT=2!+! Following messages (through FSCALL inclusive) added in edit ________! for PCO 335.! DATE: 29-Jun-1988! AUTHOR: EL!-.SEVERITY INFORMATIONAL ! codes which reflect the printer may ! need attention soon.MAINT20K <Print Engine 20,000 page maintenance required> ![LPS20]MAINT40K <Print Engine 40,000 page maintenance required> ![LPS20]MAINT300K <Print Engine 300,000 page maintenance required> ![LPS20]ONLINE <Print Engine has gone online>.SEVERITY WARNING ! codes which reflect the printer needs ! normal servicingDUPJAM <Duplexer unit is jammed> ![LPS40E]DUPOPEN <Duplexer cover is open> ![LPS40E]DUPUNSEAT <Duplexer paper path is not properly seated> ![LPS20]FUSERUNSEAT <Fuser unit absent or improperly seated> ![LPS20]CLEANUNSEAT <Cleaning unit absent or improperly seated> ![LPS20]OPCUNSEAT <OPC drum absent or improperly seated> ![LPS20]DEVUNSEAT <Developer unit absent or improperly seated> ![LPS20]OUTCOVOPEN <Paper output cover is open> ![LPS20]SIDECOVOPEN <Print engine side cover is open> ![LPS20]UPTRAYOUT <Upper paper tray is missing or misaligned> ![LPS20]LOTRAYOUT <Lower paper tray is missing or misaligned> ![LPS20]LCSSHELFO
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -