- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Printer via Print server with tcp/ip
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
Discussions
Discussions
Forums
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
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
тАО03-17-2008 09:32 AM
тАО03-17-2008 09:32 AM
Printer via Print server with tcp/ip
I have a ovms 8.3 integrity server.
I was creating a queue acceso
Printer queue acceso, idle, on Norus1::"acceso:9100", mounted form DEFAULT
/BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) Lowercase /OWNER=[PLAN,*]
/PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)
I have ping continuos at this queue.
when the user send 2 jobs o more, the system sent this jobs to print server inmediatly.
the queue turns to Stalled.
Probably because print server don't have enought memory for keep more two jobs.
the jobs it lose when the users reset the print server without start the queue.
Some one knows how I can fix the issue for not have more stalled when send two o more jobs..?
Assign Memory in tcp/ip..?
Any command that dont send the job to the print server if this is busy..?
Thanks for your comments
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 10:20 AM
тАО03-17-2008 10:20 AM
Re: Printer via Print server with tcp/ip
$ reply/enable=printer
throw your 2 jobs to the printer, and post the messages that display on your terminal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 10:54 AM
тАО03-17-2008 10:54 AM
Re: Printer via Print server with tcp/ip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 10:57 AM
тАО03-17-2008 10:57 AM
Re: Printer via Print server with tcp/ip
Without the logical TCPIP$TELNETSYM_IDLE_TIMEOUT the queue will disconnect the link and try to connect again when starting then next job in the queue.
regards,
Hakan Zanderau
HA-solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 11:22 AM
тАО03-17-2008 11:22 AM
Re: Printer via Print server with tcp/ip
Tally 6212 and tally 6215
the queues are equals
I don't have the logical TCPIP$TELNETSYM_IDLE_TIMEOUT defined.
But the estalled is inmediatly after was sending the second big job.
The first job finish but the second one are stalled.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 11:25 AM
тАО03-17-2008 11:25 AM
Re: Printer via Print server with tcp/ip
>>>
The "stalled" state is a normal behavior for a queue running TCPIP$TELNETSYM.
<<<
Hardly. 100's of queues running TCPIP$TELNETSYM; but Stalled means something like paper-out, or (physical-) printer powered-down, or paper-jam, or...; whatever, but the printer hardware is NOT accepting printjobs.
This on various types of HP; Kyocera, and Nashua printers, all with ethernet connections, all via IP protocol (and in a former life, with LAT protocol as well)
fwiw.
Proost.
Have one on me.
jpe
fwiw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 11:55 AM
тАО03-17-2008 11:55 AM
Re: Printer via Print server with tcp/ip
I used to support all the symbionts when I worked at the VMS Support Team at Digital/Compaq/HP.
Here some extracts from my (old) documentation:
Print queue frequently in "stalled" state:
When you print a job to a Telnetsym queue and it doesn't already have a link
to the printer it needs to establish one before it can print the job. In
cases where there is high contention for the printer there is a good chance
that the printer is occupied and that the link establishment will fail the
first time around. This will cause Telnetsym to keep trying to establish a
link periodically according to the retry interval logical. (See sections on
configuration of Telnetsym and on link establishment for more information.)
When the Telnetsym is waiting to establish the link the execution queue will
eventually go into a "stalled" state. When the link does come up the job will
be printed. A Telnetsym queue in the stalled state is not necessarily an
error.
If the queue goes stalled in the middle of a print job chances are the
printer is out of paper.
UCX$TELNETSYM_IDLE_TIMEOUT -
This logical defines the length of time after which Telnetsym is to terminate
an inactive link. The value for this logical is a VMS delta time. If this
logical is defined then Telnetsym will disconnect the link only when a period
of inactivity on the link equal to the time specified has passed. If this
logical is not defined then Telnetsym will release the link immediately after
the completion of each print job. For example, to define a link idle timeout
of ten minutes do:
$ DEFIN/SYS UCX$TELNETSYM_IDLE_TIMEOUT "0 00:10:00.00"
regards,
Hakan Zanderau
HA-solutions
I'm backing down from this case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 12:11 PM
тАО03-17-2008 12:11 PM
Re: Printer via Print server with tcp/ip
Seeing a network printer listed as stalled is normal and expected for telnetsym printing.
In addition to the various out-of-paper errors and other such triggers mentioned earlier, the stalled state can (also) point to access contention.
Typical settings for telnetsym aimed at the raw port (9100) are:
$ DEFINE /SYSTEM /EXECUTIVE TCPIP$TELNETSYM_RAW_TCP 1
$ DEFINE /SYSTEM TCPIP$TELNETSYM_RETRY_INTERVAL "0 00:00:30"
$ DEFINE /SYSTEM TCPIP$TELNETSYM_IDLE_TIMEOUT "0 00:01:00"
Circa TCP/IP Services V5.1 and later, see the TCPIP$TELNETSYM_SYSTARTUP.COM site-specific procedure for customizations.
Users resetting a printer and the resulting lost print jobs tends to be a self-correcting problem. That, or indicative of the need for a sticker near the power switch listing "press to eat print jobs" or some such.
You might also ring up TallyGenicom support, as (given the Genicom side of the house had some familiarity with DIGITAL printers) they may well have specific recommendations here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 12:14 PM
тАО03-17-2008 12:14 PM
Re: Printer via Print server with tcp/ip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 12:24 PM
тАО03-17-2008 12:24 PM
Re: Printer via Print server with tcp/ip
Printer queue LTA120, busy, on YIRE2::"lta120:9100", mounted form DEFAULT
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
660 PMCLOS ICORDOBA 15 Printing
663 EMPALP ICORDOBA 21 Pending
661 DEERPT ICORDOBA 31 Pending
---------------------------------
when change to execute entry 663 inmediatly stalled.
the paper is continous, the printer is idle and ping is continuos also.
------------------
Printer queue LTA120, stalled, on YIRE2::"lta120:9100", mounted form DEFAULT
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
663 EMPALP ICORDOBA 21 Stalled