- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Server Que
Operating System - OpenVMS
1758616
Members
1985
Online
108874
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО08-30-2004 05:20 PM
тАО08-30-2004 05:20 PM
Re: Server Que
Yes, I know. I was trying to understand Antonio's response.
Here is the result from your suggestion:
$$ type prt.com
$ print/notify 'P1'
$ exit
$$ prt=="@prt"""
$$ prt/que=TCPIP$LPD_IN_ATHENA_1 login.com
%DCL-E-OPENIN, error opening prt" /que=TCPIP$LPD_IN_ATHENA_1 login.com as input
-RMS-F-SYN, file specification syntax error
$$ prt=="@prt """
$$ prt/que=TCPIP$LPD_IN_ATHENA_1 login.com
Job LOGIN (queue TCPIP$LPD_IN_ATHENA_1, entry 4) pending
pending status caused by queue stopped state
$$
Here is the result from your suggestion:
$$ type prt.com
$ print/notify 'P1'
$ exit
$$ prt=="@prt"""
$$ prt/que=TCPIP$LPD_IN_ATHENA_1 login.com
%DCL-E-OPENIN, error opening prt" /que=TCPIP$LPD_IN_ATHENA_1 login.com as input
-RMS-F-SYN, file specification syntax error
$$ prt=="@prt """
$$ prt/que=TCPIP$LPD_IN_ATHENA_1 login.com
Job LOGIN (queue TCPIP$LPD_IN_ATHENA_1, entry 4) pending
pending status caused by queue stopped state
$$
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-30-2004 06:10 PM
тАО08-30-2004 06:10 PM
Re: Server Que
Uwe,
The missing blank at the end was a typo. What hapens with the parameters? Probably you receive the rest of the line in P1. And what hapens if you have a quoted string in your line? I'm stil away from a VMS machine so I cant test.
About Joseph problem I think that writing a new symbiont will be the best solution. This symbiont could work as a multi printer symbiont (open connection to more printers and print simultaneously on all printers) or just do a requeue to other queues. But I think that this is not a simple task. How to solve the /delete qualifier? (This problem is also present in the simple command procedure).
Bojan
The missing blank at the end was a typo. What hapens with the parameters? Probably you receive the rest of the line in P1. And what hapens if you have a quoted string in your line? I'm stil away from a VMS machine so I cant test.
About Joseph problem I think that writing a new symbiont will be the best solution. This symbiont could work as a multi printer symbiont (open connection to more printers and print simultaneously on all printers) or just do a requeue to other queues. But I think that this is not a simple task. How to solve the /delete qualifier? (This problem is also present in the simple command procedure).
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-30-2004 06:16 PM
тАО08-30-2004 06:16 PM
Re: Server Que
Hello Bojan,
I wasn't trying to present a solution - I am glad I didn't ;-)
Your comment clearly shows this cannot easily solved with a DCL procedure, but I am not surprised, either.
I wasn't trying to present a solution - I am glad I didn't ;-)
Your comment clearly shows this cannot easily solved with a DCL procedure, but I am not surprised, either.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-30-2004 07:11 PM
тАО08-30-2004 07:11 PM
Re: Server Que
Hi Bojan and Uwe,
I posted a warning to avoid %DCL-W-IVQUAL error as you said.
As you mentioned there are two workarounds:
1) PRT="@PRT ""
with blank and two (or three) double quotes;
this passes a unique parameter P1 without uppercase conversion to procedure; it's difficult analyze the parameters
2) PRT="@PRT """"
with blank and four double quotes;
this passes a 1.st empty qualifier and other converting in uppercase;
in this case you have only 7 qualifier.
Antonio Vigliotti
I posted a warning to avoid %DCL-W-IVQUAL error as you said.
As you mentioned there are two workarounds:
1) PRT="@PRT ""
with blank and two (or three) double quotes;
this passes a unique parameter P1 without uppercase conversion to procedure; it's difficult analyze the parameters
2) PRT="@PRT """"
with blank and four double quotes;
this passes a 1.st empty qualifier and other converting in uppercase;
in this case you have only 7 qualifier.
Antonio Vigliotti
Antonio Maria Vigliotti
- « Previous
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP