 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Twinax AS/400 printer failure</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 20:55:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Featured Member: Bigmac46 - ITKE Community Blog</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-93567</link>
		<dc:creator>Featured Member: Bigmac46 - ITKE Community Blog</dc:creator>
		<pubDate>Thu, 23 Jun 2011 06:21:28 +0000</pubDate>
		<guid isPermaLink="false">#comment-93567</guid>
		<description><![CDATA[[...] Twinax AS/400 printer failure  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Twinax AS/400 printer failure  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: djac</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92442</link>
		<dc:creator>djac</dc:creator>
		<pubDate>Fri, 20 May 2011 14:16:26 +0000</pubDate>
		<guid isPermaLink="false">#comment-92442</guid>
		<description><![CDATA[Is the printer connected to the terminal&#039;s parallel port? If so, could someone have been playing with the terminal set-up and &#039;turned off&#039; the printer capability?]]></description>
		<content:encoded><![CDATA[<p>Is the printer connected to the terminal&#8217;s parallel port? If so, could someone have been playing with the terminal set-up and &#8216;turned off&#8217; the printer capability?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: efie</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92328</link>
		<dc:creator>efie</dc:creator>
		<pubDate>Thu, 19 May 2011 16:37:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-92328</guid>
		<description><![CDATA[Hi Guys, 

i tried a couple other things over and above what you all have suggested. i gone as far as testing the cables a second time and even replacing the IBM console with a new one. I get the same test results as before:

PRT02 does not work, I jhave redirected the displays printouts to another displays printer such that the two displays (DSP03 and DSP04) are sharing a printer. This i did through STRDFU.

The message I get when printing is: PRT02 is either powered off, unavailable for use or in use by another job. 
The printer is still under Job name: Qsysarb and user qsys (which is not the case with other jobs)
Given what I have gone through so far Im thinking its a software related matter thus I am going full on with further playing around with your suggestion, addative to which I am researching on this &quot;QSYSARB&quot; as it does not seem to stop inspite of the commands you have provided to assist me in. i have never seen this before (well I am not he most experienced in these) but I am open and keen to learning it.

If you have further ideas, or addatives on previous discussions, they are more than welcome.

Many thanks to all of you for your time and efforts.

Efie]]></description>
		<content:encoded><![CDATA[<p>Hi Guys, </p>
<p>i tried a couple other things over and above what you all have suggested. i gone as far as testing the cables a second time and even replacing the IBM console with a new one. I get the same test results as before:</p>
<p>PRT02 does not work, I jhave redirected the displays printouts to another displays printer such that the two displays (DSP03 and DSP04) are sharing a printer. This i did through STRDFU.</p>
<p>The message I get when printing is: PRT02 is either powered off, unavailable for use or in use by another job.<br />
The printer is still under Job name: Qsysarb and user qsys (which is not the case with other jobs)<br />
Given what I have gone through so far Im thinking its a software related matter thus I am going full on with further playing around with your suggestion, addative to which I am researching on this &#8220;QSYSARB&#8221; as it does not seem to stop inspite of the commands you have provided to assist me in. i have never seen this before (well I am not he most experienced in these) but I am open and keen to learning it.</p>
<p>If you have further ideas, or addatives on previous discussions, they are more than welcome.</p>
<p>Many thanks to all of you for your time and efforts.</p>
<p>Efie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Featured Member: Nickhutcheson1 - ITKE Community Blog</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92309</link>
		<dc:creator>Featured Member: Nickhutcheson1 - ITKE Community Blog</dc:creator>
		<pubDate>Thu, 19 May 2011 06:50:55 +0000</pubDate>
		<guid isPermaLink="false">#comment-92309</guid>
		<description><![CDATA[[...] Twinax AS/400 printer failure [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Twinax AS/400 printer failure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: splat</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92111</link>
		<dc:creator>splat</dc:creator>
		<pubDate>Fri, 13 May 2011 12:58:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-92111</guid>
		<description><![CDATA[You may have done this already, but I&#039;d recommend you check the cabling.  It&#039;s been a bit since I&#039;ve dealt with twinax, but a poorly seated connector can cause issues.]]></description>
		<content:encoded><![CDATA[<p>You may have done this already, but I&#8217;d recommend you check the cabling.  It&#8217;s been a bit since I&#8217;ve dealt with twinax, but a poorly seated connector can cause issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bigmac46</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92092</link>
		<dc:creator>bigmac46</dc:creator>
		<pubDate>Thu, 12 May 2011 20:09:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-92092</guid>
		<description><![CDATA[Getting in this late but if writer restart gets &quot;IN USE&quot; - TRY this . 
CALL       PGM(QSPENDWA) PARM(&amp;PRINTER  -
IBM&#039;s way to end what I affectionally  call a &quot;RUN AWAY PRINTER&quot; .
Have used it a couple of time when no matter what I tried I coild not get a printer back on line because of &quot;IN USE&quot;   message even if varied off.      May take a few minutes to run.]]></description>
		<content:encoded><![CDATA[<p>Getting in this late but if writer restart gets &#8220;IN USE&#8221; &#8211; TRY this .<br />
CALL       PGM(QSPENDWA) PARM(&amp;PRINTER  -<br />
IBM&#8217;s way to end what I affectionally  call a &#8220;RUN AWAY PRINTER&#8221; .<br />
Have used it a couple of time when no matter what I tried I coild not get a printer back on line because of &#8220;IN USE&#8221;   message even if varied off.      May take a few minutes to run.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92087</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Thu, 12 May 2011 18:20:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-92087</guid>
		<description><![CDATA[&lt;i&gt;I tried using the command you gave me but it generates a lot of print jobs on our printrer.&lt;/i&gt;

I&#039;m not sure what that means. The PRTDEVADR command doesn&#039;t generate any jobs at all; it just prints a short report that shows the relationship between device descriptions and ports/switches for a single device controller.

&lt;i&gt;I also discovered the command WRKSPLF Opt5 for QPDCDEVA&lt;/i&gt;

Yes, QPDCDEVA is the report generated by the PRTDEVADR command.

Your output shows that the system expects device PRT02 to be on port 1 with switch address 3. You need to ensure that the printer is indeed set for switch address 3 (and that it is cabled into port 1).

By the looks of it, you have this printer connected to port 1 because it&#039;s attached with DSP03 and DSP03 is working correctly, right?

DSP03 is a 3487 HC terminal. It is used to configure the attached printer switch setting. Do you have a manual for your 3487 terminals? Do you know how to access the switch settings for these devices?

Tom]]></description>
		<content:encoded><![CDATA[<p><i>I tried using the command you gave me but it generates a lot of print jobs on our printrer.</i></p>
<p>I&#8217;m not sure what that means. The PRTDEVADR command doesn&#8217;t generate any jobs at all; it just prints a short report that shows the relationship between device descriptions and ports/switches for a single device controller.</p>
<p><i>I also discovered the command WRKSPLF Opt5 for QPDCDEVA</i></p>
<p>Yes, QPDCDEVA is the report generated by the PRTDEVADR command.</p>
<p>Your output shows that the system expects device PRT02 to be on port 1 with switch address 3. You need to ensure that the printer is indeed set for switch address 3 (and that it is cabled into port 1).</p>
<p>By the looks of it, you have this printer connected to port 1 because it&#8217;s attached with DSP03 and DSP03 is working correctly, right?</p>
<p>DSP03 is a 3487 HC terminal. It is used to configure the attached printer switch setting. Do you have a manual for your 3487 terminals? Do you know how to access the switch settings for these devices?</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: efie</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92086</link>
		<dc:creator>efie</dc:creator>
		<pubDate>Thu, 12 May 2011 17:49:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-92086</guid>
		<description><![CDATA[Koohiisan

I tried making the printer unavailable and then available (I suppose this is what you mean by “vary on” and “vary off”. I haven’t seen “vary on” or “vary off” for printer, only for displays.
The twinax cable signals the console which powers the display. 
I don’t have a conflicting printer (or workstation) all others are working properly. These are:
Display	Printer	Comment
DSP01	none	Master display
DSP02	PRT01	Working
DSP03	PRT02	Problem Printer
DSP04	PRT03	Working
DSP05	PRT04	Working
CADSP06	CAPRT05	Working, using window
CADSP07	CAPRT07	Working, using window

NickHutchesor

Nothing has ever changed on our hardware configuration
I checked the address and there are no conflictions at all, see table below:

Switch Setting&gt;          0                1                 2                    3

Port 0                  DSP01
                             *DSP
                            3486  BA

Port 1                  DSP02          PRT01     DSP03          PRT02
                             *DSP             *PRT        *DSP             *PRT
                            3487  HC       5256  2   3487  HC       4214    2

Port 2                  DSP04          PRT03      DSP05          PRT04
                             *DSP              *PRT        *DSP             *PRT
                            3487  HC       4214  2   3407  HC       4214    2

Port 3

Port 4


I ended the writer 
Powered off the writer with the 10 seconds wait
VRYCFG PRT02 *off. Display the status to make sure it is varied off.
Powered on the writer with the 10 seconds wait 
VRYCFG PRT02 *on.
Strprtwtr PRT02.

Infact I deleted the entire printer set up/description and reconnected the printer hoping for auto-config to do the “set-up” (I verified the auto-config to be set to 1), and this still didn’t work.
Any messages: same on I keep getting: writer PRT02 cannot use device PRT02 because the device is not powered on, varied on or in use by another job

TomLiotta

The twinax cable signals the console which powers the display. 
I don’t have a conflicting printer (or workstation) all others are working properly. These are:
Display	Printer	Comment
DSP01	none	Master display
DSP02	PRT01	Working
DSP03	PRT02	Problem Printer
DSP04	PRT03	Working
DSP05	PRT04	Working
CADSP06	CAPRT05	Working, using window
CADSP07	CAPRT07	Working, using window

I tried using the command you gave me but it generates a lot of print jobs on our printrer. I also discovered the command 
WRKSPLF
Opt5 for QPDCDEVA

Switch Setting&gt;          0                1                 2                    3

Port 0                  DSP01
                             *DSP
                            3486  BA

Port 1                  DSP02          PRT01     DSP03          PRT02
                             *DSP             *PRT        *DSP             *PRT
                            3487  HC       5256  2   3487  HC       4214    2

Port 2                  DSP04          PRT03      DSP05          PRT04
                             *DSP              *PRT        *DSP             *PRT
                            3487  HC       4214  2   3407  HC       4214    2

Port 3

Port 4


I hope this helps, I tried all these things.
Thanks for your time]]></description>
		<content:encoded><![CDATA[<p>Koohiisan</p>
<p>I tried making the printer unavailable and then available (I suppose this is what you mean by “vary on” and “vary off”. I haven’t seen “vary on” or “vary off” for printer, only for displays.<br />
The twinax cable signals the console which powers the display.<br />
I don’t have a conflicting printer (or workstation) all others are working properly. These are:<br />
Display	Printer	Comment<br />
DSP01	none	Master display<br />
DSP02	PRT01	Working<br />
DSP03	PRT02	Problem Printer<br />
DSP04	PRT03	Working<br />
DSP05	PRT04	Working<br />
CADSP06	CAPRT05	Working, using window<br />
CADSP07	CAPRT07	Working, using window</p>
<p>NickHutchesor</p>
<p>Nothing has ever changed on our hardware configuration<br />
I checked the address and there are no conflictions at all, see table below:</p>
<p>Switch Setting&gt;          0                1                 2                    3</p>
<p>Port 0                  DSP01<br />
                             *DSP<br />
                            3486  BA</p>
<p>Port 1                  DSP02          PRT01     DSP03          PRT02<br />
                             *DSP             *PRT        *DSP             *PRT<br />
                            3487  HC       5256  2   3487  HC       4214    2</p>
<p>Port 2                  DSP04          PRT03      DSP05          PRT04<br />
                             *DSP              *PRT        *DSP             *PRT<br />
                            3487  HC       4214  2   3407  HC       4214    2</p>
<p>Port 3</p>
<p>Port 4</p>
<p>I ended the writer<br />
Powered off the writer with the 10 seconds wait<br />
VRYCFG PRT02 *off. Display the status to make sure it is varied off.<br />
Powered on the writer with the 10 seconds wait<br />
VRYCFG PRT02 *on.<br />
Strprtwtr PRT02.</p>
<p>Infact I deleted the entire printer set up/description and reconnected the printer hoping for auto-config to do the “set-up” (I verified the auto-config to be set to 1), and this still didn’t work.<br />
Any messages: same on I keep getting: writer PRT02 cannot use device PRT02 because the device is not powered on, varied on or in use by another job</p>
<p>TomLiotta</p>
<p>The twinax cable signals the console which powers the display.<br />
I don’t have a conflicting printer (or workstation) all others are working properly. These are:<br />
Display	Printer	Comment<br />
DSP01	none	Master display<br />
DSP02	PRT01	Working<br />
DSP03	PRT02	Problem Printer<br />
DSP04	PRT03	Working<br />
DSP05	PRT04	Working<br />
CADSP06	CAPRT05	Working, using window<br />
CADSP07	CAPRT07	Working, using window</p>
<p>I tried using the command you gave me but it generates a lot of print jobs on our printrer. I also discovered the command<br />
WRKSPLF<br />
Opt5 for QPDCDEVA</p>
<p>Switch Setting&gt;          0                1                 2                    3</p>
<p>Port 0                  DSP01<br />
                             *DSP<br />
                            3486  BA</p>
<p>Port 1                  DSP02          PRT01     DSP03          PRT02<br />
                             *DSP             *PRT        *DSP             *PRT<br />
                            3487  HC       5256  2   3487  HC       4214    2</p>
<p>Port 2                  DSP04          PRT03      DSP05          PRT04<br />
                             *DSP              *PRT        *DSP             *PRT<br />
                            3487  HC       4214  2   3407  HC       4214    2</p>
<p>Port 3</p>
<p>Port 4</p>
<p>I hope this helps, I tried all these things.<br />
Thanks for your time</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92060</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Thu, 12 May 2011 00:45:41 +0000</pubDate>
		<guid isPermaLink="false">#comment-92060</guid>
		<description><![CDATA[&lt;i&gt;Job Name: QSYSARB&lt;/i&gt;

If the device is allocated to QSYSARB, there is no writer active.

&lt;i&gt;I get a message waiting with error code CPA3387...&lt;/i&gt;

And you can&#039;t start a writer because the writer fails from CPA3387.

How many twinax ports do you have available? If you run PRTDEVADR for the twinax controller, does that device show up in the right location?

Tom]]></description>
		<content:encoded><![CDATA[<p><i>Job Name: QSYSARB</i></p>
<p>If the device is allocated to QSYSARB, there is no writer active.</p>
<p><i>I get a message waiting with error code CPA3387&#8230;</i></p>
<p>And you can&#8217;t start a writer because the writer fails from CPA3387.</p>
<p>How many twinax ports do you have available? If you run PRTDEVADR for the twinax controller, does that device show up in the right location?</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nickhutcheson1</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/twinax-printer-failure/#comment-92045</link>
		<dc:creator>nickhutcheson1</dc:creator>
		<pubDate>Wed, 11 May 2011 16:17:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-92045</guid>
		<description><![CDATA[Twinaxe.  Cool.
What changed?  Device description, cableing, more devices on the same controller / line with the same address as the PRT02?
If the writer job is still active, ENDWTR.
Double check the description you created for the correct controller/line/address.
Do these steps in order.
Power off the writer.  Wait 10 seconds.
VRYCFG PRT02 *off.  Display the status to make sure it is varied off.
Power on the writer. Wait 10 seconds.
VRYCFG PRT02 *on.
Strprtwtr PRT02.
Answer any formtype messages or alignment messages.]]></description>
		<content:encoded><![CDATA[<p>Twinaxe.  Cool.<br />
What changed?  Device description, cableing, more devices on the same controller / line with the same address as the PRT02?<br />
If the writer job is still active, ENDWTR.<br />
Double check the description you created for the correct controller/line/address.<br />
Do these steps in order.<br />
Power off the writer.  Wait 10 seconds.<br />
VRYCFG PRT02 *off.  Display the status to make sure it is varied off.<br />
Power on the writer. Wait 10 seconds.<br />
VRYCFG PRT02 *on.<br />
Strprtwtr PRT02.<br />
Answer any formtype messages or alignment messages.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.011 seconds using memcached
Object Caching 394/397 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 21:19:36 -->