[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

278.0. "Local Printer on PC, VMS Queue and LAT" by STU01::53514::stu01::kroiss () Tue Mar 04 1997 12:21

Hi,

I have a Problem with an Printer, locally attached to an OS/2 PC with a Queue
on an VMS Node.

Problem Description:
Customer has several PATHWORKS 4.1 DOS Clients.
On the Client side are localy attached printers via parallel port.
Customer configures a LAT Service for this local printer and prints out
from the VMS Server side. (VMS 5.5-2)

Problem:
Customer has to migrate to IBM OS/2 LAN Server environment
with PATHWORKS Version 5.1 on top.
When trying to copy a VMS-File to the LAT port 
pointing to the localy attached client printer via LAT,
the VMS side gets an error:

file write error
data set hang-up
file not completely copied

Tested with the configuration on the client side i got following
results:
connection via LAT-terminal to the client LAT Service i can print out to
the printer !!
iris trace show traffic between VMS and OS/2 Client 
connecting the NODE and SERVICE correctly.

Environment:
Client
localy queue NEC attached to lpt1:
c:\spool\nec exists
latcp add NECPR NEC

$ mc latcp create port lta510: /app
$ mc latcp set port lta510: /NODE=OS2PC /SERVICE=NECPR
$ copy test.txt lta510:
results in
file write error
data set hang-up
file not completely copied

Regards 
Kurt

T.R Title User Personal
Name Date Lines

278.1 Contact LAT Client Maintainers XDELTA::HOFFMAN Steve, OpenVMS Engineering Tue Mar 04 1997 12:38 16

T.R	Title	User	Personal Name	Date	Lines
278.1	Contact LAT Client Maintainers	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Mar 04 1997 12:38`	16
	This appears to have nothing to do with OpenVMS -- it would appear that there is a problem in the LAT package you have acquired for the OS/2 PC system. (You're asking the wrong folks for help...) Check with the folks that support (supplied) the OS/2 LAT client. Consider a switch to a package such as LPR/LPD (part of UCX and of various other IP packages), or consider inserting a LATprint or DECserver device and serving access to the printer, or consider placing a communications line near the PC and relocating the printer onto that line. There is a recently announced LAT package for varios systems, and there are DCPS packages for a number of PCs.

   This appears to have nothing to do with OpenVMS -- it would appear
   that there is a problem in the LAT package you have acquired for the
   OS/2 PC system.  (You're asking the wrong folks for help...)

   Check with the folks that support (supplied) the OS/2 LAT client.

   Consider a switch to a package such as LPR/LPD (part of UCX and of
   various other IP packages), or consider inserting a LATprint or
   DECserver device and serving access to the printer, or consider
   placing a communications line near the PC and relocating the printer
   onto that line.

   There is a recently announced LAT package for varios systems, and
   there are DCPS packages for a number of PCs.