Home · Articles · Downloads · Hobby Wear · Forums · Web Links · News CategoriesSunday, December 05, 2021
Navigation
Home
Articles
Downloads
Hobby Wear
FAQ
Forums
Web Links
News Categories
Contact Us
Photo Gallery
OpenVMS Bigot
Search
Users Online
Guests Online: 9
No Members Online

Registered Members: 7,607
Newest Member: phatoes
Sponsors
Island Computer
View Thread
OpenVMS Hobbyist Program | Alpha Systems Forums | Alpha Hardware Forum
Author problem sendin output to printer
Edgar Estrada
Member

Posts: 2
Location: Puerto Rico
Joined: 11.06.09
Posted on June 11 2009 05:19
hi, i had problem printin form disk to printer.
Compaq TCP/IP Services for OpenVMS Alpha Version V5.1 - ECO 3
on a AlphaServer 8200 5/440 running OpenVMS V7.2-2, ok
i create printer "init-xxx.xxx.:xxxx" thas is working fine, so we had an app to print checks, th command delete the que so he donk know were to print looking around i foud somo one with the same problem ahd he create a lta port and then spooled the port to the printer i did that but when i tri to print the cheks i get these error " LISTO PARA IMPRESION DE CHEQUES
%COB-F-WRITE_ERROR, ERROR DURING WRITE ON FILE LTA80:[].DAT;
-RMS-F-WER, FILE WRITE ERROR
-SYSTEM-F-HANGUP, DATA SET HANG-UP
%TRACE-F-TRACEBACK, SYMBOLIC STACK DUMP FOLLOWS
IMAGE MODULE ROUTINE LINE REL PC ABS PC
DEC$COBRTL 0 00000000000109C4 000000007C1AC9C4
DEC$COBRTL 0 00000000000100A0 000000007C1AC0A0
DEC$COBRTL 0 000000000002C848 000000007C1C8848
IRE032_2005 OPE032_2005 OPE032_2005 766 00000000000005B0 00000000000305B0
IRE032_2005 0 0000000000023EB0 0000000000033EB0
0 FFFFFFFF90911474 FFFFFFFF90911474
ESTE PROCESO SE CANCELO FAVOR DE COMUNICARSE CON EL ENCARGADO DEL SISTEMA
%DCL-W-IVQUAL, UNRECOGNIZED QUALIFIER - CHECK VALIDITY, SPELLING, AND PLACEMENT"

these is one of the instructions "$ IF P2 .EQS. "PRINT2" THEN DONDE :== "LG14$QUE"

$ IF P2 .EQS. "PRINT2" THEN LINEAS :== "LTA80:"
$!

my english is not good, sorry the miss spelling
thanks
Author RE: problem sendin output to printer
malmberg
Moderator

Posts: 527
Joined: 15.04.08
Posted on August 08 2010 16:35
The error message indicates that the LTA device is not properly spooled to the print queue and the Cobol program tried to write to a LTA device that did not have anything connected to it.

You should be able to use the COPY command to copy a test file to the spooled port as a test.

Note that the "$" is reserved for print queue names created by Digital/Compaq/HP or third party software.

Showing the print queue set up and spooled device set may help trouble shoot the issue.

TCPIP may or may not have anything to do with the issue, depending on what type of print queue you have.

In general for network printing, the preferences are:

1. DCPS network connection.
2. Reverse LAT
3. Telnetsym connection

And only if you have no other way of doing it should you be trying to use the old LPR/LPD.
Author RE: problem sendin output to printer
abrsvc
Member

Posts: 107
Joined: 12.03.10
Posted on August 09 2010 01:40
Realize too that an LTA device is a LAT device and has nothing to do with TCPIP. A TCPIP based printer would be aTNA device or a BG device.

If the printer is conencted via thenet and has an IP address, then you need to use TCPIP and create the queue apporopriately. If the printer is conencted to a DECserver, then you need to use LAT.

Update this note with the connection type and I'll post an example for you.

Thanks,
Dan
Author RE: problem sendin output to printer
malmberg
Moderator

Posts: 527
Joined: 15.04.08
Posted on August 09 2010 02:38
Actually it is perfectly valid to spool LAT terminal devices to non-LAT print queues. I do it all the time.

It allows you to set up generic print queues with spooled devices. It also allows you to set up spooled devices with DCPS print queues that print to raw TCPIP or DECNET connections.

A LAT port also can be used to set up a spooled device to an LPR printer.

In these cases, the LAT port is never bound to an actual terminal server port.
Jump to Forum:
Login
Username

Password



Not a member yet?
Click here to register.

Forgotten your password?
Request a new one here.
Member Poll
Are you going to OpenVMS Boot Camp 2016?

Yes

No

You must login to vote.
Shoutbox
You must login to post a message.

gtackett
October 27 2021
Make that DECdfs _2.1A_ for Vax

gtackett
October 27 2021
I'm looking for DECdfs V2.4A kit for VAX. Asking here just in case anyone is still listening.

MarkRLV
September 17 2021
At one time, didn't this web site have a job board? I would love to use my legacy skills one last time in my career.

malmberg
January 18 2021
New Hobbyist PAKs for VAX/VMS are no longer available according to reports. Only commercial licenses are reported to be for sale from HPE

dfilip
January 16 2021
Can someone please point me to hobbyist license pak? I'm looking for VAX/VMS 7.1, DECnet Phase IV, and UCX/TCPIP ... have the 7.1 media, need the license paks ... thanks!

Bart
October 16 2020
OpenVMS, and this website!

malmberg
September 05 2020
VSI community non-commercial licenses for AXP/IA64 are available now.

malmberg
September 05 2020
See the forum about licensing. Don't know if HPE hobby licenses still being issued. Commercial licenses still being sold.

silfox70
September 01 2020
I need the license for OpenVMS7.3. Where can I find them?

malmberg
August 29 2020
Eisner, which is currently being moved, got an SSH update and the keys were updated to more modern encryption standards.

jiml
July 11 2020
ssh to eisner is now giving (on linux) "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" , Has the server key in fact changed ? Of WHO can we ask that somewhere on the eisner webpage they

wyan
May 06 2020
Turns out I had an account here, it still was set to my location a decade ago, so hey, I'm back after over a decade!

Hein
April 21 2020
Hi all, haven't been here in years. Good to see it is all there still. I'm looking around at the forum to stop/start msipcap - 'could not be stopped' - for now. I'll shutdown FreeA

EstesDave
January 09 2020
does anyone have or know of DRB32 manuals

romaxmaniax
November 04 2019
V6.1

Shoutbox Archive