- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Stock Mismatch
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2009 07:20 AM
01-02-2009 07:20 AM
We are have some issues with forms after moving printer from another site. We are trying to use a couple of different forms. Not exactly sure how the forms work. Does the printer have to be able to recognize the form or does it check the Library for the form info?
Here is the print queue:
Printer queue HORLJET3, idle, on SERVER::"horljet3:9100", mounted form LJWIDE1
(stock=DEFAULT)
/AUTOSTART_ON=(NRCAVA::"horljet3:9100") /BASE_PRIORITY=4 /DEFAULT=(FEED,
FLAG=ONE,FORM=NRCCSD (stock=WHITE_PERF_NO)) /LIBRARY=SYSDEVCTL Lowercase
/OWNER=[1,4] /PROCESSOR=UCX$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)
/RETAIN=ERROR /SEPARATE=(RESET=(HPRESET))
Let me know what information you need and I will provide it. Thanks for your help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2009 07:33 AM
01-02-2009 07:33 AM
SolutionOpenVMS does not really 'know' (nor care) what kind of paper is installed in your printer. You have to tell the queue-manager by starting the queue with a form name, which is associated with the correct 'stock' (i.e. paper format and type).
Your HORLJET3 queue has been started with a form named 'LJWIDE1' which is associated with a stock named 'DEFAULT', but the default form name points to a form with a stock called 'WHITE_PERF_NO'. So if your print command does not include a /FORM= qualifier, the print-job will assume a default form called NRCCSD. As the stock for this form does not match the stock for the currently mounted form, the print job will hang (stock mismatch).
If you know, that the correct stock (i.e. paper) has been loaded, stop and start the queue with START/QUE/FORM=NRCCSD HORLJET3
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2009 07:40 AM
01-02-2009 07:40 AM
Re: Stock Mismatch
http://h71000.www7.hp.com/doc/82final/aa-pv5mj-tk/aa-pv5mj-tk.html
The printer does not care about forms, stock, queues or other constructs.
Printers do (as a general rule) what they're told to do. Depending on the model, printers themselves can (potentially) report printing and paper errors and such, but generally not anything related to OpenVMS itself.
Here, I'd expect you need to transfer the HPRESET module in the system device control library and the forms definitions over using SHOW QUEUE /FORM /FULL and DEFINE /FORM and such. The form definitions include margins, stock and other attributes.
Here's a high-level introduction to IP printing on OpenVMS and to some pointers to other printing-related topics including device control libraries:
http://64.223.189.234/node/129
I should add some stuff on forms to the site. But that's fodder for another time.
In the unlikely event that some knowledge of the configuration and operation of the queue manager and of printing on OpenVMS does not sort this out, then...
Specific version of OpenVMS?
Specific version of TCP/IP Services?
Specific error messages?
Specific device and form definitions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2009 09:11 AM
01-02-2009 09:11 AM
Re: Stock Mismatch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2009 02:45 AM
01-04-2009 02:45 AM
Re: Stock Mismatch
The "STOCK"-option is used to protect a printer with special paper from accidental usage.
Let's say you have PhotoPrinter. To protect the printer from accidental usage, you create a form with the option /STOCK=photopaper.
You mount this form on the queue by using
INIT/QUE......./FORM=my_special_form 'queue_name"
or
SET QUEUE /FORM=my_special_form 'queue_name'
When a user tries to use the queue, the supplied form has to match the STOCK on the allready mounted form. If not....the job will be pending with status "STOCK MISMATCH"
The mounted form can be changed by SET QUEUE/FORM=
( no need to reinit or restart the queue )
About moving printconfiguration between nodes.
When a queue or a form includes a SETUP-module, be sure the modules exists in the target libraries.
The targeted library is set on each queue by the parameter /LIBRARY= ( if not shown on the queue, SYSDEVCTL.TLB is used )
Check the contents using the command
LIB/LIST 'library'.TLB
It's a common mistake when moving queues and forms to forget the contents of the libraries.
Hakan Zanderau
HA-solutions