Posted by Grant Foraker on January 26, 2007 at 07:18:03:
What does E30 mean these days?
I have a customer who tracks and expenses print jobs. When a printer is opened or maybe when the first print line is generated, the audit program pops up and asks for dept/user info. Once entered, the print jobs continues without any problems.
If the user cancels the print job in the pop up, Comet yields an E30. I think they cancel because they meant to print to SP1 instead of LP1.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
01/18/07 13:14:03 P65 GRL ERROR #: 30 DEVICE INOPERATIVE
VSN: 605.363 LUN: 1 FILE: LP5 . DIR:
KEY: 001€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€
SYS FUNC: 13 FORMATTED WRITE
DOS FUNC: 3E CLOSE A FILE HANDLE
DOS ERR : 00 NO DOS ERROR REPORTED
DOS HANDLE: 0019 PATH: \\NNJFPS01\PRNT07€
NODE NAME : FRAN
USER ADDR :05F7 05FC 05FF 060A 060F 0614 0619 061F 036E 0660 0664 0668 066B 0676
STACK ADDR:18F9 133E 2833 16AF 6520 7672 0000 0000 0000 0000 0000 0000 0000 0000
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'd like to change my error trapping logic for E30 so the user doesn't end up in QENDITOR.