HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Autostart Queues and TELNETSYM VMS 8.3

 
Peter Katz
Occasional Advisor

Autostart Queues and TELNETSYM VMS 8.3

I need to make a few TELNETSYM queues as autostart failover queues for two cluster nodes. I'm using a Jetdirect 510x with Telnetsym and I can print just fine to two different printers on ports 1 & 2 but I can't get the autostart failover to set up. I'm using IP address and port: i.e. >> /on="65.202.165.222:9100" QNAME << and just can't get the syntax right which leads me to believe that TELNETSYM queues can't be autostart failover queues. IF so, what is the correct method for having autostart failover queues ? Relay queues ?

Please provide an example of autostart for telnetsym if possible or just please straighten me out.

Thanks much in advance,

Peter
9 REPLIES
John Gillings
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

Peter,

Could you please post the output of SHOW QUEUE/FULL of your target queue, and your attempted command that "just can't get the syntax right".
A crucible of informative mistakes
Jon Pinkley
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

Peter,

Don't user /on, instead use /autostart_on.

See help initialize /queue /autostart

Example:

$ sho que b37lp1/ful
Printer queue B37LP1, idle, on SIGMA::"172.30.37.10:9100", mounted form INVOICE

/AUTOSTART_ON=(SIGMA::"172.30.37.10:9100",OMEGA::"172.30.37.10:9100") /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=EPSLP
Lowercase /OWNER=[SYSTEM] /PROCESSOR=UCX$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S) /SCHEDULE=(NOSIZE)
(IDENTIFIER=B37MEM,ACCESS=MANAGE)
$
it depends
Jon Pinkley
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

Here ia an example of creating a queue with autostart

OT$ sho que itrcdemo
%JBC-E-NOSUCHQUE, no such queue
OT$ init/que/auto=("sigma::172.30.200.5:9100","omega::172.30.200.5:9100")/proc=tcpip$telnetsym itrcdemo /desc="DEMO of TELNETSYM autostart"/lib=epslp
OT$ sho que /ful itrcdemo
Printer queue ITRCDEMO, stopped, autostart inactive, on "sigma::172.30.200.5:9100", mounted form DEFAULT

/AUTOSTART_ON=("sigma::172.30.200.5:9100","omega::172.30.200.5:9100") /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /LIBRARY=EPSLP
/OWNER=[SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)
OT$
it depends
Jon Pinkley
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

The double quotes should be around the ipadddress, and not include the node name.

Like the following, not my previous example:

OT$ init/que/auto=(sigma::"172.30.200.5:9100",omega::"172.30.200.5:9100")/proc=tcpip$telnetsym itrcdemo /desc="DEMO of TELNETSYM aut
ostart"/lib=epslp/start
OT$ sho que itrcdemo
Printer queue ITRCDEMO, idle, on OMEGA::"172.30.200.5:9100", mounted form DEFAULT

OT$ sho que itrcdemo/ful
Printer queue ITRCDEMO, idle, on OMEGA::"172.30.200.5:9100", mounted form DEFAULT

/AUTOSTART_ON=(SIGMA::"172.30.200.5:9100",OMEGA::"172.30.200.5:9100") /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /LIBRARY=EPSLP
Lowercase /OWNER=[SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)
OT$
it depends
Peter Katz
Occasional Advisor

Re: Autostart Queues and TELNETSYM VMS 8.3

Hi John:

After spending 3 frustrating hours and then shooting off my request, I found this document in the KB which fixed my problems. The VMS doc is not clear in the syntax and this document has it right. Indeed just a matter of getting the () and " " right and it now works. Thanks for your quick reply and for caring enough to help. My brain was fried after a long day of trying to get a simple task to work correctly. Thanks, Peter.
Title: HP OpenVMS Operating Systems - How to Convert a Non-Autostart Queue to an Autostart Queue
Document ID: emr_na-c01392461-1
Submitted Date: 2008-03-11 23:49:03.0
Last Modified Date: 2008-03-21 19:45:03.0
Peter Katz
Occasional Advisor

Re: Autostart Queues and TELNETSYM VMS 8.3

This KB article has the solution and my issue is resolved. Thanks all for your help.

Title: HP OpenVMS Operating Systems - How to Convert a Non-Autostart Queue to an Autostart Queue
Document ID: emr_na-c01392461-1
Submitted Date: 2008-03-11 23:49:03.0
Last Modified Date: 2008-03-21 19:45:03.0
Hoff
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

I'd suggest submitting a problem report to HP to get the documentation fixed here, but that's been somewhat spotty lately.
Jon Pinkley
Honored Contributor

Re: Autostart Queues and TELNETSYM VMS 8.3

For future readers:

The following is the link to the referenced knowledgebase article. At a minimum you must be logged into ITRC to see it. You may need to have a support contract linked to your ITRC user (I don't know if this is a requirement or not).

http://www.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01392461

If you can't see this article, or it has moved, the answer given in post dated Dec 23, 2009 07:33:08 GMT has the correct syntax for the parameter to the /autostart_on qualifier, but the commands are abbreviated. In general:

$ initialize/queue/autostart_on=(node1::"ipaddress:tcp_port",node2::"ipaddress:tcp_port"[,...])/processor=tcpip$telnetsym queuename [/start]

Example: Create a autostart TELNETSYM queue that can be processed by either node ITRC01 or node ITRC02, using the network printer with ipaddress 192.168.10.10 listening on tcp port 9100, and using the user provided device control library sys$library:mydevctl.tlb
$ initialize/queue/autostart_on=(ITRC01::"192.168.10.10:9100",ITRC02::"192.168.10.10:9100")/processor=tcpip$telnetsym ITRCTNSYM /library=mydevctl/start

Then make sure autostart queues are enabled on at least on of the specified nodes.
it depends
Peter Katz
Occasional Advisor

Re: Autostart Queues and TELNETSYM VMS 8.3

Thanks John,for caring; you're a good man... :)

Indeed, the VMS doc set doesn't come close to what that KB article has and I'd still be pulling my hair out if I hand't found that article...

P