Thanks. I tried your suggestion and it worked. My only comment is that
parameter MFRTYPMDL(*WSCSTLETTER) is not correct I changed it to IBM6400 in
order to get it to work.

Thanks once again.

Panayiotis (Pete) Petrou
zVSE and Websphere MQ System Administration
Information Technology Division
Bank Of Cyprus
Tel 357-22-12-8473

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott, Bill
Sent: Thursday, October 08, 2009 5:15 PM
To: Midrange Systems Technical Discussion
Subject: RE: Problem with Printer Definition setup by a newbie to i5

I've glanced at your print server FAQs and I agree that it doesn't seem to
support socket.
Before trying to set up the iSeries side, please check the VSE config.
You want to find the LPR queue name and try and determine the data stream
being sent.
If VSE is not generating PCL, VSE is most likely converting EBCDIC and
sending ASCII line data to the print server.

After you find the print server queue name, verify it by doing a test from a
windows command prompt:

lpq -Saaa.bbb.ccc.ddd -PQueue_name_from_VSE

If you get any sort of status information or even a command prompt back
without an error message, the queue name is good.

While you are at the command prompt, you can also test print any .txt file
that you have by sending it to the print server:

lpr -Saaa.bbb.ccc.ddd -PQueue_name_from_VSE
complete_path_and_text_file_name

Complete path and file name should be something like "C:\mydir\readme.txt"

If your text file prints, we just need to setup the iSeries, to have the
iSeries to the same thing, try making a simple remote outq, such as this:

CRTOUTQ OUTQ(IBM6400)
RMTSYS(*INTNETADR)
RMTPRTQ(Queue_name_from_VSE)
CNNTYPE(*IP)
DESTTYPE(*OTHER)
TRANSFORM(*YES)
MFRTYPMDL(*WSCSTLETTER)
INTNETADR(aaa.bbb.ccc.ddd)

STRRMTWTR IBM6400

If this works, you may want to change the WSCSTLETTER to whatever paper size
is loaded into the printer.
Since you are printing on a simple line printer, only spool file types of
*SCS will work cleanly.




Bill Scott
Océ North America, Inc.
Tel.: (561) 997-3256
e-mail: Bill.Scott@xxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Thursday, October 08, 2009 8:16
To: Midrange Systems Technical Discussion
Subject: Re: Problem with Printer Definition setup by a newbie to i5

have you tried to setup a remote output queue for this device and then use
raw, I bet the printerserver isn't setup to support 9100.

On Thu, Oct 8, 2009 at 7:41 AM, Panayiotis Petrou <
panayiotis.petrou@xxxxxxxxxxxxxxxxxxxx> wrote:

The IBM 6400 printer we are trying to setup is connected to the LAN
thru a Micronet SP760 print server (parallel connection) on LPT1.

I tried changing the port 9100 but we get an error on the IP address/port.
I also tried the suggestions below and I got the following errors.

5722SS1 V5R4M0 060210 Job Log
S65509EB 08/10/09 14:35:15 Page 1
Job name . . . . . . . . . . : WTR_6400 User . . . . . . :
QSPLJOB Number . . . . . . . . . . . : 016465
Job description . . . . . . : QSPLPRTW Library . . . . . :
QGPL
MSGID TYPE SEV DATE TIME FROM
PGM
LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 08/10/09 14:35:15.044056
QWTPIIPP
QSYS 066E *EXT *N
Message . . . . : Job
016465/QSPLJOB/WTR_6400 started on 08/10/09 at
14:35:14 in subsystem QSPL in QSYS.
Job entered system on 08/10/09 at
14:35:14.

*NONE Request 08/10/09 14:35:15.044528
QWTSCSBJ
*N QCMD QSYS 0194
From user . . . . . . . . . : D813

Message . . . . : -CALL
QSYS/QSPWTRM1

CPD401A Diagnostic 40 08/10/09 14:35:15.331888
QWPSNMPD
QSYS *STMT QWPSNMPD QSYS *STMT
From module . . . . . . . . :
WPSNMPD

From procedure . . . . . . :
Initialize_Driver
Statement . . . . . . . . . : 131

To module . . . . . . . . . :
WPSNMPD

To procedure . . . . . . . : _C_pep

Statement . . . . . . . . . : *N

Message . . . . : Could not
establish
SNMP communications with device
WTR_6400.

Cause . . . . . : Was not able to
establish SNMP communications with device
WTR_6400. The reason code is 2.
The reason codes and their meanings are as
follows: 1 - The device appears
to be an SNMP device but not a printer. 2 -
The device appears to be an SNMP
device but does not support the required
level of an industry standard
SNMP protocol. 3 - Communication with the
device timed out. This could
occur because of heavy network traffic, the
device is not an SNMP device, or
the read community name set on the device
is different than expected. Recovery
. . . : Make sure that the device is
a printer that supports the
industry standard SNMP protocol and that the
read community name is set
correctly.
Then try the operation again.
CPF3473 Escape 60 08/10/09 14:35:15.332368
QSPOPNWX
QSYS 0246 QCMD QSYS 01C7
Message . . . . : Writer
016465/QSPLJOB/WTR_6400 did not end normally.
Recovery . . . : See the previously
listed messages to determine cause of
the writer failure. Correct any
errors and start the writer again.
CPC2402 Completion 50 08/10/09 14:35:15.339064 QCMD
QSYS 0668 *EXT *N
Message . . . . : Job ended. Cancel
message received at command processor.
Cause . . . . . : A message with a
severity equal to or exceeding the end
severity was received at the command
processor. Recovery . . . : See the


Panayiotis (Pete) Petrou
zVSE and Websphere MQ System Administration Information Technology
Division Bank Of Cyprus Tel 357-22-12-8473

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
smorrison@xxxxxxxxxxxxxxxxxxx
Sent: Wednesday, October 07, 2009 9:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problem with Printer Definition setup by a newbie to i5

Jack mentioned changing the port to 9100. Our 6400 is set to
Workstation Customization Object = *NONE, and System Drive Program =
*IBMSNMPDRV. I'm not sure what you'll get trying to use HPPJLDRV.

Steve
- -
Steven Morrison
Fidelity Express





"Panayiotis
Petrou"
<panayiotis.petro To
u@xxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
s.com> cc
Sent by:
midrange-l-bounce Subject
s@xxxxxxxxxxxx Problem with Printer Definition
setup by a newbie to i5

10/07/2009 10:42
AM


Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






We have an IBM 6400 line printer attached to a print server that we
currently use to print from our VSE system via TCP/IP LPR.



I have attempted to try and define a Printer device description on an
i5 (see device description below) but I am not able to print.



Any help will be greatly appreciated.



The messages I am getting are as follows:





5722SS1 V5R4M0 060210 Job Log
S65509EB 07/10/09 12:38:21 Page 1

Job name . . . . . . . . . . : WTR_6400 User . . . . . . :
QSPLJOB Number . . . . . . . . . . . : 016337

Job description . . . . . . : QSPLPRTW Library . . . . . :
QGPL


SGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY INST

PF1124 Information 00 07/10/09 12:38:06.183544 QWTPIIPP
QSYS 066E *EXT *N

Message . . . . : Job
016337/QSPLJOB/WTR_6400 started on 07/10/09 at

12:38:06 in subsystem QSPL in QSYS.
Job entered system on 07/10/09 at

12:38:06.


NONE Request 07/10/09 12:38:06.184096 QWTSCSBJ
*N QCMD QSYS 0194

From user . . . . . . . . . : D813


Message . . . . : -CALL
QSYS/QSPWTRM1


PD338D Diagnostic 40 07/10/09 12:38:21.214888 QWPPJLDR
QSYS *STMT QWPPJLDR QSYS *STMT

From module . . . . . . . . : WPPJLDR


From procedure . . . . . . :
Socket_Recv

Statement . . . . . . . . . : 40


To module . . . . . . . . . : WPPJLDR


To procedure . . . . . . . : _C_pep


Statement . . . . . . . . . : *N


Message . . . . : An error occurred
while receiving data.


More...

Cause . . . . . : A communications
error occurred while receiving data from

remote device at RMTLOCNAME
10.1.103.186. The error code is 3426. This error

can also occur when the system
attempts to print to the remote device after

it has been powered off and on
while the printer writer remains active.

Recovery . . . : Try the request
again. If the problem continues, end

TCP/IP using the End TCP/IP
(ENDTCP)
command, start TCP/IP by using the

Start TCP/IP (STRTCP) command,
and then try the request again.

CPF3473 Escape 60 07/10/09 12:38:21.216408
QSPOPNWX
QSYS 0246 QCMD QSYS 01C7

Message . . . . : Writer
016337/QSPLJOB/WTR_6400 did not end normally.

Recovery . . . : See the
previously
listed messages to determine cause of

the writer failure. Correct any
errors and start the writer again.

CPC2402 Completion 50 07/10/09 12:38:21.235840 QCMD
QSYS 0668 *EXT *N

Message . . . . : Job ended. Cancel
message received at command processor.

Cause . . . . . : A message with a
severity equal to or exceeding the end

severity was received at the
command
processor. Recovery . . . : See the

messages previously listed to
determine the message that caused the job to

be ended. Correct the errors,
and then try the request again.

CPC2191 Completion 00 07/10/09 12:38:21.238544
QLIDLOBJ
QSYS 051B QLICLLIB QSYS 05DC

Message . . . . : Object SPLAPISPJL
in QTEMP type *USRSPC deleted.









Device description . . . . . . . . : WTR_6400

Option . . . . . . . . . . . . . . : *BASIC

Category of device . . . . . . . . : *PRT



Device class . . . . . . . . . . . : *LAN

Device type . . . . . . . . . . . : 3812

Device model . . . . . . . . . . . : 1

LAN attachment . . . . . . . . . . : *IP

Port number . . . . . . . . . . . : 515

Physical attachment . . . . . . . : *DIRECT

Online at IPL . . . . . . . . . . : *NO

Font:

Identifier . . . . . . . . . . . : 11

Point size . . . . . . . . . . . : *NONE

Form feed . . . . . . . . . . . . : *AUTOCUT

Separator drawer . . . . . . . . . : *FILE

Separator program . . . . . . . . : *NONE

Printer error message . . . . . . : *INFO

Message queue . . . . . . . . . . : *CTLD

Current message queue . . . . . . : QSYSOPR

Library . . . . . . . . . . . . : QSYS

Activation timer . . . . . . . . . : 170

Inactivity timer . . . . . . . . . : *SEC15

Line speed . . . . . . . . . . . . : 19200

Word length . . . . . . . . . . . : 8

Type of parity . . . . . . . . . . : *NONE

Stop bits . . . . . . . . . . . . : 1

Host print transform . . . . . . . : *YES

Manufacturer type and model . . . : *IBM6400

Paper source 1 . . . . . . . . . . : *CONT132

Paper source 2 . . . . . . . . . . : *NONE

Envelope source . . . . . . . . . : *NONE

ASCII code page 899 support . . . : *YES

Image configuration . . . . . . . : *NONE

Character identifier . . . . . . . : *SYSVAL

Remote location:

Name or address . . . . . . . . : 10.1.103.186

Workstation customizing object . . : QWPIBM64XX

Library . . . . . . . . . . . . : *LIBL

User-defined object . . . . . . . : *NONE

Object type . . . . . . . . . . : *NONE

Data transform program . . . . . . : *NONE

System driver program . . . . . . : *HPPJLDRV

Allocated to:

Job name . . . . . . . . . . . . . : *NONE

User . . . . . . . . . . . . . . :

Number . . . . . . . . . . . . . :

Published . . . . . . . . . . . . : *NO



Publishing information:

Support duplex . . . . . . . . . : *UNKNOWN

Support color . . . . . . . . . : *UNKNOWN

Pages per minute black . . . . . : *UNKNOWN

Pages per minute color . . . . . : *UNKNOWN

Location . . . . . . . . . . . . : *BLANK

Data streams supported . . . . . : *UNKNOWN

Text . . . . . . . . . . . . . . . : IBM6400 On 3rd floor Platy





Panayiotis (Pete) Petrou

zVSE and Websphere MQ System Administration

Information Technology Division

Bank Of Cyprus

Tel 357-22-12-8473



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.





Confidentiality Statement: This electronic mail transmission is
confidential, may be privileged and should be read or retained only by
the intended recipient. If you have received this transmission in
error, please notify the sender immediately and delete it from your
system.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.




This message and attachment(s) are intended solely for use by the addressee
and may contain information that is privileged, confidential or otherwise
exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for
delivering this message to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited.

If you have received this communication in error, please notify the sender
immediately by telephone and with a 'reply' message.

Thank you for your co-operation.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.