End-user functionality
Introduction
The SMB printing support is split into 3 functional groups:
• Access and define printer
• Submit jobs
• Manage spooled jobs
Access and define printer
The PRISMAsync controller is visible on the network when it is configured for SMB:
• As member of a specific workgroup
Note:
The controller cannot announce itself in a Windows Domain. Therefore it cannot take
benefit of the rights administration which is possible in a Windows Domain.
• As a specific computer
• As itself sharing a printer in the network environment of the host computer.
The controller shares only one printer. This means that the controller opens only one print queue
for SMB printing. For instance, for a controller configured with (<computer hostname> =
Controller) and (<share name> = PrintQueue), the complete print queue is: \\Controller
\PrintQueue.
The printer access depends on:
• If the SMB support is disabled, the printer is not visible or accessible at all.
• The controller can handle a maximum of 10 concurrent network connections.
Note:
Each connection is closed if an inactivity is detected of more than 30 seconds.
• When the SMB Job Reception is disabled, no new jobs are accepted.
Submit jobs
Use a printer driver, job submission application or print server to submit jobs. Jobs can also be
sent via the DOS print command. In this case a driver does not need to be installed. For example:
print /D:\\Controller\PrintQueue PostScriptJob.ps
For each submission, the controller receives the following information, which are called the
protocol job attributes:
Attribute
Description
Transported by SMB
Where it appears
Username
Name of the end-user. Always
• On the LUI
• In the print Manag-
er
Hostname
Always
• On the LUI *
Jobname
Name of the print job,
in most cases the
name of the submitted
file.
Sometimes **
If not, the controller
provides "unspeci-
fied_filename".
• On the LUI
• In the print Manag-
er
Legenda:
*: Optionally, jobname can be completed by hostname indication. This depends on the Settings
Editor settings.
**: Depends on the submission context. Jobname is often provided when the end-user submits
from Windows applications.
End-user functionality
298
Chapter 11 - SMB printing
imagePRESS C7010VPS series v2.2
Summary of Contents for imagePRESS C7010VPS series
Page 8: ...Contents 8 imagePRESS C7010VPS series v2 2...
Page 9: ...Chapter 1 Introduction...
Page 14: ...Supported media 14 Chapter 1 Introduction imagePRESS C7010VPS series v2 2...
Page 15: ...Chapter 2 PRISMAsync...
Page 29: ...Chapter 3 The LPD connection...
Page 45: ...Chapter 4 The socket connection...
Page 51: ...Chapter 5 Adobe PostScript 3...
Page 64: ...Bind 64 Chapter 5 Adobe PostScript 3 imagePRESS C7010VPS series v2 2...
Page 86: ...Staple 86 Chapter 5 Adobe PostScript 3 imagePRESS C7010VPS series v2 2...
Page 89: ...Trim Chapter 5 Adobe PostScript 3 89 imagePRESS C7010VPS series v2 2...
Page 99: ...Chapter 6 PDF...
Page 117: ...Chapter 7 Colour management...
Page 133: ...Chapter 8 Accounting...
Page 150: ...Implementation aspects 150 Chapter 8 Accounting imagePRESS C7010VPS series v2 2...
Page 151: ...Chapter 9 SNMP...
Page 159: ...Example in pseudo code Chapter 9 SNMP 159 imagePRESS C7010VPS series v2 2...
Page 222: ...ppmPortGroup 222 Chapter 9 SNMP imagePRESS C7010VPS series v2 2...
Page 223: ...Chapter 10 JDF interface specification...
Page 291: ...Basic JDF ticket Chapter 10 JDF interface specification 291 imagePRESS C7010VPS series v2 2...
Page 297: ...Chapter 11 SMB printing...
Page 303: ...Chapter 12 Hot folder printing...
Page 306: ...Hot folder 306 Chapter 12 Hot folder printing imagePRESS C7010VPS series v2 2...
Page 307: ...Chapter 13 Scan to file and scan to email...
Page 313: ...Chapter 14 SRA IPDS...
Page 361: ......