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


Jerry C. Adams

IBM i Programmer/Analyst

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


A&K Wholesale

Murfreesboro, TN


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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2021 by 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.