Ricoh InfoPrint Pro C900AFP AIX Planning Guide - Page 45

Using an InfoPrint Manager actual destination, Using a PSF for z/OS or OS/390 defined printer

Get Ricoh InfoPrint Pro C900AFP PDF manuals and user guides View all Ricoh InfoPrint Pro C900AFP manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Manager actual destination or a PSF for OS/390 defined printer. All jobs are managed on either one InfoPrint Manager queue or one PSF for OS/390 defined printer. Using an InfoPrint Manager actual destination You can use these methods to submit jobs to one InfoPrint Manager queue: v MVS Download Receivers when jobs are received from Host MVS Download drivers v LPD when jobs are received from LPR clients on any platform v Hot Folder when jobs are received from a mapped network directory v InfoPrint Manager Select, Submit Express, and IPP clients when jobs are received directly from the Windows client v Command line using a pdpr command v IP Printway if you do not use DPF or MVS Download to submit jobs When you submit print jobs to the same queue, these apply: v There is a single point of control and auditing for all jobs printed. A single InfoPrint Manager interface can be used to determine all pending jobs for the printer. v There is automated job prioritization between jobs. Several methods of prioritization are available. v There is a single point of failure. Using a PSF for z/OS or OS/390 defined printer InfoPrint Manager for AIX provides the ability to upload AFP jobs to the JES spool through a TCP/IP communications link. Jobs can be submitted to InfoPrint Manager using any of the methods described in "Using an InfoPrint Manager actual destination." When the jobs are directed to a PSF Upload actual destination, the jobs are placed on the JES spool with existing host print jobs. Final control of the print jobs is performed on the z/OS or OS/390 system. You use the InfoPrint Manager system to control jobs that it sends to the z/OS or OS/390 system. When you upload jobs to the JES spool, these apply: v There is a single point of control and auditing for all jobs printed. An z/OS or OS/390 interface can be used to determine all pending jobs for the printer. v There is automated job prioritization between jobs. v There is a single point of failure. Sharing printers between host and LAN applications To get the most out of your printers, you can share them among your host and LAN applications. Printing from existing host applications There are several ways you can submit jobs from host applications to InfoPrint Manager: v MVS Download sends jobs to an MVS Download Receiver. v The LPR client sends jobs to the LPD utility on the InfoPrint Manager server. Chapter 5. Planning to share printers 29

  • 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
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
Manager actual destination or a PSF for OS/390 defined printer. All jobs are
managed on either one InfoPrint Manager queue or one PSF for OS/390 defined
printer.
Using an InfoPrint Manager actual destination
You can use these methods to submit jobs to one InfoPrint Manager queue:
v
MVS Download Receivers when jobs are received from Host MVS Download
drivers
v
LPD when jobs are received from LPR clients on any platform
v
Hot Folder when jobs are received from a mapped network directory
v
InfoPrint Manager Select, Submit Express, and IPP clients when jobs are received
directly from the Windows client
v
Command line using a
pdpr
command
v
IP Printway if you do not use DPF or MVS Download to submit jobs
When you submit print jobs to the same queue, these apply:
v
There is a single point of control and auditing for all jobs printed. A single
InfoPrint Manager interface can be used to determine all pending jobs for the
printer.
v
There is automated job prioritization between jobs. Several methods of
prioritization are available.
v
There is a single point of failure.
Using a PSF for z/OS or OS/390 defined printer
InfoPrint Manager for AIX provides the ability to upload AFP jobs to the JES spool
through a TCP/IP communications link. Jobs can be submitted to InfoPrint
Manager using any of the methods described in “Using an InfoPrint Manager
actual destination.” When the jobs are directed to a PSF Upload actual destination,
the jobs are placed on the JES spool with existing host print jobs. Final control of
the print jobs is performed on the z/OS or OS/390 system. You use the InfoPrint
Manager system to control jobs that it sends to the z/OS or OS/390 system.
When you upload jobs to the JES spool, these apply:
v
There is a single point of control and auditing for all jobs printed. An z/OS or
OS/390 interface can be used to determine all pending jobs for the printer.
v
There is automated job prioritization between jobs.
v
There is a single point of failure.
Sharing printers between host and LAN applications
To get the most out of your printers, you can share them among your host and
LAN applications.
Printing from existing host applications
There are several ways you can submit jobs from host applications to InfoPrint
Manager:
v
MVS Download sends jobs to an MVS Download Receiver.
v
The LPR client sends jobs to the LPD utility on the InfoPrint Manager server.
Chapter 5. Planning to share printers
29