Name: ajaya21 Date: December 22, 2003 at 02:26:45 Pacific Subject: ip print que OS: VMS CPU/Ram: VAX
Comment:
I am trying to print normal txt file through a VAX C prog using SYS$SNDJBCW system service. I have TCPIP print que set on the node. The job gets printed successfully on the remote node. But the problem is when i say "sh que <que_name>/full" i get errors for each of the job that was completed successfully. Can anyone help me out?? The eaxct error maessage that i get is
Printer queue <que_name>, idle, on <node_name>::"IP_addr:port", mounted form VAR_1 (stock=DEFAULT) <TCP/IP-telnet printer on <ip_addr:port_num>
Entry Jobname Username Blocks Status ------- 6996 <file_name> <user_name> 1 Retained on error %PSM-E-OPENIN, error opening !AS as input -RMS-E-FNF, file not found -SYSTEM-W-NOSUCHFILE, no such file Completed 18-DEC-2003 08:24:24.97 on queue <que_name>
when i tried finding the reason for this error it says the file you are trying to print is not on the same node of the vms cluster. But that really is not the case.....
Does anyone have any idea about this kind of scenario??
- Do you delete the file yourself after printing ? - Is the protection of the file good ? - Does the form VAR_1 exists ? - Does the library with setup modules for the queue exists ?
First of all thank you very much for the reply. I must admit that i really know very little about the IP printing on VMS. So there are further doubts.....
1) No, I do not delete those files manually. The sytem services which i use, delete those files once they are sent to proper Printer. (In my case instead of printer I have another process listening which basically collects the data in those file and parse it)
2)No problems with protection of the file. But still can you please explain me this point further. What kind of protections you are pointing to??
3)Form VAR_1 exists otherwise, it would not allow me to initialise the que with that form. But i would like to know more about the TLB files which are refered for these forms?? I do not have sys$library:sysdevctl.TLB. But there are many other TLB files, Do you have any idea about these TLB files???
4) Does the library with setup modules for the queue exists?? Sorry.. ut i have really no idea as to how do you check that?? Can you please explain.....
2) The specific message is possible if the system cannot find or does not have permission to read the file. But since you can print it I do not see a scenario thta this is the case, although it is always good to check.
3) you can define setup module(s) in a form. These are textfiles with escape sequences that are stored in a text library (.TLB). Every time that you print a file, the specific module will be sent to the printer before the actual job is sent. You can see if you have a setup module connected to the form with : $ SHOW QUEUE /FORM /FULL <form-name> You can see if there is a text-library attached to the queue with the command : $ SHOW QUEUE /FULL <queue-name> You can see which modules are defined in a library with the LIBRARY command : $ LIBR /LIST SYS$LIBRARY:<libname> If you have a setup module defined in your form, but there is no library attached to the queue, or the module does not exists in the library, you have a problem.
More information about device control libraries is at : http://h71000.www7.hp.com/doc/73final/6017/6017pro_062.html#devctl
I checked whether the problem is due to from and the device libraries.. But that is not the case.....
Can you think any other reason for that error???
In case the job is properly sent on the VMS IP queue....does it (UCX processor) get any response back from the device indicating whether the job is properly printed
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE