RE: Weird Printer Issue

Also, meant to say that I did check the job log after the incident today
(when the invoice wanted to print at BB even though it should have been
directed to P7). There were no messages in the job log, and it shows the //
PRINTER OCL statement explicitly referencing P7, but nothing later except
the normal stuff.

Jerry C. Adams
IBM i Programmer/Analyst
[I support efforts] to limit the terms of members of Congress, especially
members of the House and members of the Senate. - Dan Quayle
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: Jerry C. Adams [mailto:midrange@xxxxxxxx]
Sent: Tuesday, March 13, 2012 2:12 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Weird Printer Issue

Kirk,

You're right; we are running in 36E. And good thought. Everything does
line up properly.

Jerry C. Adams
IBM i Programmer/Analyst
Where fraternities are not allowed, Communism flourishes. - Barry Goldwater
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins
Sent: Tuesday, March 13, 2012 1:40 PM
To: Midrange Systems Technical Discussion
Subject: Re: Weird Printer Issue

Jerry I am guessing by the device names yo are running in S36 Environment.
Take a look at CHGS36 cmd and the 2 options
S/36 display IDs, S/36 printer IDs and make sure the device names in
fact line line up the way you expect it to.



On Tue, Mar 13, 2012 at 11:24 AM, Jerry C. Adams <midrange@xxxxxxxx> wrote:

I have one heck of a flaky situation. First, about two weeks ago I
connected a PC printer in our warehouse manager's office to our System
i
(V5R1) via PC5250 printer emulation. Worked great - until yesterday.



The reports, documents, etc., for the two girls in the office started
printing to this new printer (BB), even though the OCL or CL
explicitly referenced a different printer. I even changed a procedure
so that the report (a one-pager) would be put on Hold. The @#$% thing
not only went to BB even though P6 was explicitly defined, but it was
released. I ran the same procedure from my workstation and everything was

cool.

I had a few more scenarios that I wanted to run through today, but we
had a disk drive reporting as failed when I got in this morning.
Thought that might have priority over my silly little problem.



After the system came back up, miraculously, the girls reports,
checks, etc., went to the correct printer. HOWEVER, the warehouse
manager's stuff that should go to P7 (his twinax line printer) now wanted

to go to BB.

But,
when I was logged in at his terminal (twinax), the documents printed
on P7 without a hitch.



Okay, I admit to being throughly confused, but it gets better/worse.
I stopped his printer emulation of BB, completely closed the emulation
session (X-ed it out), restarted the BB emulation session from ground
zero (the
icon) - and everything for everybody is printing where it is supposed to.
Which makes everyone ecstatic.



Except me. I don't know what started this, nor when/if it will rear
its ugly head. I had planned to test out various combinations of
workstations
:
user profiles to try to narrow down the problem at least somewhat.



I did think about the out queues, and the correct out queue was
assigned to the correct device. That wouldn't have explained the

weirdness anyway.

I can't even test out any suggestions since things are (apparently)
working now. But for future reference, when it happens again, has
anyone seen anything like this before and/or got clue(s) what to look
for the next time it happens (cause I know it will - and at the worst

possible time).

Thanks.



Jerry C. Adams

IBM i Programmer/Analyst

Honest businessmen should be protected from the unscrupulous consumer.
- Lester Maddox

--

A&K Wholesale

Murfreesboro, TN

615-867-5070



--
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.

--
Kirk
--
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.