Lexmark MX6500e 6500e IPDS Printer and Host Setup Guide - Page 35

Intervention Required messages, Remote output queue name clash

Get Lexmark MX6500e 6500e PDF manuals and user guides View all Lexmark MX6500e 6500e manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

IPDS Printer and Host Setup Guide Printer Messages and Problems requirements on each supported printer, refer to the appendix on memory requirements and recommendations in the IPDS Emulation User's Guide. D. The host may be downloading more IPDS resources than can be held in the printer's memory. Add more memory to the printer. Requirements vary greatly according to type of printing and types of resources being used. For information on the minimum recommended installed memory for various printing requirements on each supported printer, refer to the appendix on memory requirements and recommendations in the IPDS Emulation User's Guide. Problem 5: Large or complex PostScript or PCL jobs do not print after installing IPDS emulation Before installing the IPDS emulation, my PostScript and PCL jobs printed correctly. Now some large PostScript and PCL jobs do not print. Solution to Problem 5 A. If you have set host and printer settings to temporarily store IPDS resources when printing non-IPDS jobs, change these settings to allow the host to delete the IPDS resources before printing non-IPDS jobs. Refer to IPDS Timeout in the IPDS Emulation User's Guide for more information on setting printer values and see the appropriate host installation section in this guide to change the host timeout value. B. Add more memory to the printer. This will allow IPDS resources to be temporarily stored and more complex non-IPDS jobs to print. Requirements vary greatly according to type of printing and types of resources being used. For information on the minimum recommended installed memory for various printing requirements on each supported printer, refer to the appendix on memory requirements and recommendations in the IPDS Emulation User's Guide. Problem 6: Remote output queue (name clash) I'm trying to set up a remote printer with the Standard Network port or a MarkNet internal LAN print server (named IPDSPRT) from my AS/400. When I try to print to it, I get an error message such as: • "All sessions ended for device IPDSPRT" • "Bind sense code ... received for mode QSPWTR device IPDSPRT" • "Writer...did not end normally" Solution to Problem 6 A remote output queue created using CRTOUTQ and a PSFCFG device created using WRKAFP2 or CRTPSFCFG have the same user defined name. You must use a unique name for the remote output queue for an ASCII device using TCP/IP and the AS/400 Host Print Transform. This cannot be the same name used to define the printer as an IPDS printer with WRKAFP2 or CRTPSFCFG. Problem 7: Intervention Required messages Intervention Required messages (printer offline, out of paper, and cover open) from the printer are causing problems on the IPDS host. Solution to Problem 7 You can suppress this message reporting by selecting the value Do Not Report for the option Intervention 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
35
IPDS Printer and Host Setup Guide
Printer Messages and Problems
requirements on each supported printer, refer to the appendix on memory requirements and
recommendations in the IPDS Emulation User’s Guide.
D.
The host may be downloading more IPDS resources than can be held in the printer's memory. Add more
memory to the printer. Requirements vary greatly according to type of printing and types of resources being
used. For information on the minimum recommended installed memory for various printing requirements on
each supported printer, refer to the appendix on memory requirements and recommendations in the IPDS
Emulation User’s Guide.
Problem 5:
Large or complex PostScript or PCL jobs do not print after installing IPDS
emulation
Before installing the IPDS emulation, my PostScript and PCL jobs printed correctly. Now some large Post-
Script and PCL jobs do not print.
Solution to Problem
5
A.
If you have set host and printer settings to temporarily store IPDS resources when printing non-IPDS jobs,
change these settings to allow the host to delete the IPDS resources before printing non-IPDS jobs. Refer
to
IPDS Timeout
in the IPDS Emulation User’s Guide for more information on setting printer values and see
the appropriate host installation section in this guide to change the
host timeout
value.
B.
Add more memory to the printer. This will allow IPDS resources to be temporarily stored and more complex
non-IPDS jobs to print. Requirements vary greatly according to type of printing and types of resources being
used. For information on the minimum recommended installed memory for various printing requirements on
each supported printer, refer to the appendix on memory requirements and recommendations in the IPDS
Emulation User’s Guide.
Problem 6:
Remote output queue (name clash)
I'm trying to set up a remote printer with the Standard Network port or a MarkNet internal LAN print server
(named IPDSPRT) from my AS/400. When I try to print to it, I get an error message such as:
•
"All sessions ended for device IPDSPRT"
•
"Bind sense code ... received for mode QSPWTR device IPDSPRT"
•
"Writer...did not end normally"
Solution to Problem
6
A remote output queue created using CRTOUTQ and a PSFCFG device created using WRKAFP2 or CRTPS-
FCFG have the same user defined name. You must use a unique name for the remote output queue for an
ASCII device using TCP/IP and the AS/400 Host Print Transform. This cannot be the same name used to
define the printer as an IPDS printer with WRKAFP2 or CRTPSFCFG.
Problem 7:
Intervention Required messages
Intervention Required
messages (printer offline, out of paper, and cover open) from the printer are caus-
ing problems on the IPDS host.
Solution to Problem
7
You can suppress this message reporting by selecting the value
Do Not Report
for the option
Intervention