<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: printer problems PSM-E-WRITEERR in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943585#M73006</link>
    <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;CHANNELCNT is a SYSGEN parameter (and regrettably, NOT dynamic)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
    <pubDate>Wed, 30 Nov 2005 15:32:24 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2005-11-30T15:32:24Z</dc:date>
    <item>
      <title>printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943572#M72993</link>
      <description>Hi all&lt;BR /&gt;&lt;BR /&gt;The short version:&lt;BR /&gt;%PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;-SYSTEM-F-HANGUP, data set hang-up&lt;BR /&gt;&lt;BR /&gt;The long "detailed" version:&lt;BR /&gt;&lt;BR /&gt;I have a lot of problems with my printers. Some are connected via tcp, others using old LAT. Guess the problem is not the printers itself. &lt;BR /&gt;&lt;BR /&gt;Some jobs causing the printer queue to be stalled. The printfile is OK, it is printed out when reprinting it.&lt;BR /&gt;All printing is done from a C++ application using:&lt;BR /&gt;status = sys$sndjbcw(0,SJC$_ENTER_FILE,0,&amp;amp;item_list,0,0,0);&lt;BR /&gt;(I have no idea what that line is doing... just put it here so you don't have to ask:)&lt;BR /&gt;&lt;BR /&gt;The application has been working for 10 years in 30 different factories, just has to be some quotas or network or what? I have adjusted "mcr sysgen sh CHANNELCNT" since autogen asked for it.&lt;BR /&gt;&lt;BR /&gt;Guess your answers will be like "network related", (that's my answer to customers when I don't have any idea)&lt;BR /&gt;but... please give me a hint where to dig.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;/Klaes-Goran&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;EINKGCA_BTRACK&amp;gt; ucx sh ver&lt;BR /&gt;&lt;BR /&gt;HP TCP/IP Services for OpenVMS Alpha Version V5.4&lt;BR /&gt;on a AlphaServer 1200 5/533 4MB running OpenVMS V7.3-2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;EINKGCA_BTRACK&amp;gt; sh que OBSPRINT142/all/full&lt;BR /&gt;&lt;BR /&gt;Terminal queue OBSPRINT142, idle, on BTRACK::LTA629, mounted form DEFAULT&lt;BR /&gt;&lt;INTERMEC 4320=""&gt;&lt;BR /&gt;/AUTOSTART_ON=(BTRACK::LTA629) /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT)&lt;BR /&gt;Lowercase /OWNER=[SYSTEM] /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR&lt;BR /&gt;/SCHEDULE=(NOSIZE)&lt;BR /&gt;&lt;BR /&gt;Entry Jobname Username Blocks Status&lt;BR /&gt;----- ------- -------- ------ ------&lt;BR /&gt;4514 102_19002-2_SVV10799A23004H0JA&lt;BR /&gt;BAR_SFT 3 Retained on error&lt;BR /&gt;%PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;-SYSTEM-F-HANGUP, data set hang-up&lt;BR /&gt;Submitted 21-NOV-2005 07:42:18.96 /FORM=DEFAULT /PRIORITY=100&lt;BR /&gt;File: _BTRACK$DRA1:[BARTRACK.062.TMP.LABEL]102_19002-2_SVV10799A23004H0&lt;BR /&gt;/DELETE&lt;BR /&gt;Completed 21-NOV-2005 07:42:18.99 on queue OBSPRINT142&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;EINKGCA_BTRACK&amp;gt; sh que z*215*/all/full&lt;BR /&gt;Printer queue ZBSPRINT215, idle, on BTRACK::"PSB202.bs.sw.ericsson.se:9100",&lt;BR /&gt;mounted form DEFAULT&lt;BR /&gt;/BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) Lowercase /OWNER=[SYSTEM]&lt;BR /&gt;/PROCESSOR=UCX$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR&lt;BR /&gt;&lt;BR /&gt;Entry Jobname Username Blocks Status&lt;BR /&gt;----- ------- -------- ------ ------&lt;BR /&gt;1817 4_19002-4_SVV10799A23004HGLY&lt;BR /&gt;BAR_SFT 19 Retained on error&lt;BR /&gt;%PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;-SYSTEM-F-NOIOCHAN, no I/O channel available&lt;BR /&gt;Submitted 24-NOV-2005 09:35:00.77 /FORM=DEFAULT /PRIORITY=100&lt;BR /&gt;File: _BTRACK$DRA1:[BARTRACK.062.TMP.LABEL]4_19002-4_SVV10799A23004HGLY&lt;BR /&gt;/DELETE&lt;BR /&gt;Completed 24-NOV-2005 09:35:01.36 on queue ZBSPRINT215&lt;/INTERMEC&gt;</description>
      <pubDate>Wed, 30 Nov 2005 04:34:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943572#M72993</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-11-30T04:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943573#M72994</link>
      <description>Also have a lot of errors like:&lt;BR /&gt;&lt;BR /&gt;   1051  4_19002-4_SVV10799A23004J5KG&lt;BR /&gt;                         BAR_SFT          19  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-NOIOCHAN, no I/O channel available&lt;BR /&gt;         Completed 30-NOV-2005 07:56:41.46 on queue ZBSPRINT215&lt;BR /&gt;   1300  4_19002-4_SVV10799A23004J5TP&lt;BR /&gt;                         BAR_SFT          19  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-NOIOCHAN, no I/O channel available&lt;BR /&gt;         Completed 30-NOV-2005 08:58:01.79 on queue ZBSPRINT215&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Nov 2005 04:40:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943573#M72994</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-11-30T04:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943574#M72995</link>
      <description>Hm, "dataset hang up" is indeed a sign of network disruptions, but NOIOCHAN most likely not. Apart from raising CHANNELCNT (which is not a dynamic parameter, so you need a reboot, but I think you know that).&lt;BR /&gt;&lt;BR /&gt;It is possible that the C++ RTLs eats up too many I/O channels - does it help if you raise the system parameter PQL_MFILLM?</description>
      <pubDate>Wed, 30 Nov 2005 04:43:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943574#M72995</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-30T04:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943575#M72996</link>
      <description>Raising CHANNELCNT and parhaps openfile quota for the symboint process should help with NOIOCHAN. &lt;BR /&gt;&lt;BR /&gt;Dataset hangup from a lat connection indicates a network timeout. LAT has short timeouts, some of which can not be changed. Check for network issues between the DECserver and your VMS system.</description>
      <pubDate>Wed, 30 Nov 2005 04:58:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943575#M72996</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-11-30T04:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943576#M72997</link>
      <description>Check the quota of the symbiont process that deals with your printer, with Amds or Availability Manager (both available at &lt;A href="http://h71000.www7.hp.com/openvms/products/availman/index.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/products/availman/index.html&lt;/A&gt; ) or pquota (&lt;A href="http://h71000.www7.hp.com/freeware/freeware40/pquota/)" target="_blank"&gt;http://h71000.www7.hp.com/freeware/freeware40/pquota/)&lt;/A&gt;</description>
      <pubDate>Wed, 30 Nov 2005 05:29:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943576#M72997</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-11-30T05:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943577#M72998</link>
      <description>I have adjusted the PQL_MFILLM from 100 to 1000, have to let the system run for some hours before I know if this was the solution. Have been running 1 hour now without problem:) &lt;BR /&gt;&lt;BR /&gt;Uwe: Yes, I have rebooted after changing channelcnt.&lt;BR /&gt;&lt;BR /&gt;Ian: "open file quota" do you mean FILLM? &lt;BR /&gt;&lt;BR /&gt;Then I need to learn some more: How to find out which process/account to adjust? &lt;BR /&gt;&lt;BR /&gt;sh sys/proc=*symb* gives me a list of 5 processes. Show proc/id/cont tells me that some are running DCPS$SMB.EXE others running LATSYM.EXE&lt;BR /&gt;All of them with system account. Is it just to mcr authorize mod system/fillm=3000 ? It is =2000 now. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/Klaes-GÃ¶ran</description>
      <pubDate>Wed, 30 Nov 2005 05:52:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943577#M72998</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-11-30T05:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943578#M72999</link>
      <description>to find the symbiont for lta629, do &lt;BR /&gt;$ ana/sys&lt;BR /&gt;set proc/id=id_of_1st_symbiont&lt;BR /&gt;sh proc/chann&lt;BR /&gt;if you have lta629, it is this one, note the pid</description>
      <pubDate>Wed, 30 Nov 2005 06:12:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943578#M72999</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-11-30T06:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943579#M73000</link>
      <description>&amp;gt; Ian: "open file quota" do you mean FILLM?&lt;BR /&gt;&lt;BR /&gt;I am not Ian, but I'd say yes ;-)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As far as I can tell, a symbiont is not activated in a way that takes care about a username's SYSUAF quotas - thus my suggestion to look after the system parameter PQL_MFILLM which overrules any lower values from the process quota list.</description>
      <pubDate>Wed, 30 Nov 2005 08:42:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943579#M73000</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-30T08:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943580#M73001</link>
      <description>If memory serves me, a symbiont takes his quotas from jobctl process, so Uwe method is good and simple</description>
      <pubDate>Wed, 30 Nov 2005 08:54:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943580#M73001</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-11-30T08:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943581#M73002</link>
      <description>Yes FILLM. Symbiont processes are detached processes so the values in the UAF do not apply. Raising PQL_MFILLM is the way to go.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Nov 2005 09:12:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943581#M73002</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-11-30T09:12:51Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943582#M73003</link>
      <description>It didn't helped to adjust pql_mfillm from 100 to 1000, does any of you have any more suggestions?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;SYSGEN&amp;gt;  USE ACTIVE&lt;BR /&gt;SYSGEN&amp;gt;  SET PQL_MFILLM 1000&lt;BR /&gt;SYSGEN&amp;gt;  WRITE ACTIVE&lt;BR /&gt;SYSGEN&amp;gt;  EXIT&lt;BR /&gt;&lt;BR /&gt;I have got 3 more printjobs with errors as below. I have downloaded and made some tests with PQUOTA, but since I'm a novice it doesn't tells me anything. Have run it on all 5 TCPIP$TNSn processes. The FILCNT is max used 17%, all other 0.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Printer queue OBSPRINT290, idle, on BTRACK::"psbs36.bs.sw.ericsson.se:3001",&lt;BR /&gt;mounted form DEFAULT&lt;BR /&gt;  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) Lowercase /OWNER=[SYSTEM]&lt;BR /&gt;  /PROCESSOR=UCX$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR&lt;BR /&gt;&lt;BR /&gt;   1838  104_19002-4_SVV10799A23004J6ET&lt;BR /&gt;                         BAR_SFT           3  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-LINKDISCON, network partner disconnected logical link&lt;BR /&gt;         Submitted 30-NOV-2005 11:41:14.57 /FORM=DEFAULT /PRIORITY=100&lt;BR /&gt;         File: _BTRACK$DRA1:[BARTRACK.062.TMP.LABEL]104_19002-4_SVV10799A23004J6&lt;BR /&gt;             /DELETE&lt;BR /&gt;         Completed 30-NOV-2005 11:41:14.72 on queue OBSPRINT290&lt;BR /&gt;&lt;BR /&gt;   1953  104_19002-4_SVV10799A23004J6H5&lt;BR /&gt;                         BAR_SFT           3  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-NOIOCHAN, no I/O channel available&lt;BR /&gt;         Submitted 30-NOV-2005 12:23:21.63 /FORM=DEFAULT /PRIORITY=100&lt;BR /&gt;         File: _BTRACK$DRA1:[BARTRACK.062.TMP.LABEL]104_19002-4_SVV10799A23004J6&lt;BR /&gt;             /DELETE&lt;BR /&gt;         Completed 30-NOV-2005 12:23:21.85 on queue OBSPRINT290&lt;BR /&gt;&lt;BR /&gt;   2117  104_19002-4_SVV10799A23004J6TQ&lt;BR /&gt;                         BAR_SFT           3  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-LINKDISCON, network partner disconnected logical link&lt;BR /&gt;         Submitted 30-NOV-2005 13:16:43.76 /FORM=DEFAULT /PRIORITY=100&lt;BR /&gt;         File: _BTRACK$DRA1:[BARTRACK.062.TMP.LABEL]104_19002-4_SVV10799A23004J6&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;EINKGCA_BTRACK&amp;gt; sh sys/proc=*tns*&lt;BR /&gt;OpenVMS V7.3-2  on node BTRACK  30-NOV-2005 15:25:47.96  Uptime  12 23:22:56&lt;BR /&gt;  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages&lt;BR /&gt;00000422 TCPIP$TNS2      HIB      5   765514   0 00:04:34.27       493    410&lt;BR /&gt;00000423 TCPIP$TNS1      HIB      5   515322   0 00:02:53.93       466    384&lt;BR /&gt;000004C4 TCPIP$TNS3      HIB      5  1801884   0 00:10:47.49       378    295&lt;BR /&gt;000004C8 TCPIP$TNS4      HIB      5   694999   0 00:04:10.37     47529    248&lt;BR /&gt;000004CA TCPIP$TNS5      HIB      5   100546   0 00:00:30.05    115188     36&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Nov 2005 09:34:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943582#M73003</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-11-30T09:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943583#M73004</link>
      <description>Klaes-GÃ¶ran,&lt;BR /&gt;&lt;BR /&gt;Ian mentioned CHANNELCNT in passing, but HAVE you already raised it?&lt;BR /&gt;&lt;BR /&gt;What is the current value?&lt;BR /&gt;&lt;BR /&gt;Are you running any databases?&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 30 Nov 2005 13:20:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943583#M73004</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-11-30T13:20:56Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943584#M73005</link>
      <description>Isn't CHANNELCNT per individual process?</description>
      <pubDate>Wed, 30 Nov 2005 13:24:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943584#M73005</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-30T13:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943585#M73006</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;CHANNELCNT is a SYSGEN parameter (and regrettably, NOT dynamic)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 30 Nov 2005 15:32:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943585#M73006</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-11-30T15:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943586#M73007</link>
      <description>Sigh, of course that is a system parameter!&lt;BR /&gt;&lt;BR /&gt;My point was that it affects the size of the channel control blocks array _for each process_. It is not a system-wide limit.</description>
      <pubDate>Wed, 30 Nov 2005 15:43:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943586#M73007</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-30T15:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943587#M73008</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Yes, I have changed the channelcnt:&lt;BR /&gt;Parameter Name           Current    Default     Min.      Max.     Unit  Dynamic&lt;BR /&gt;--------------           -------    -------    -------   -------   ----  -------&lt;BR /&gt;CHANNELCNT                   2400        256        31      65535 Channels&lt;BR /&gt;&lt;BR /&gt;And also rebooted (one week ago), no change.&lt;BR /&gt;&lt;BR /&gt;Jan: Yes, I have &lt;BR /&gt; RDB 7.1-04 database. (Not any ODBC, no sqlserver) &lt;BR /&gt; Bea Message Queue (DMQ) with some 100 clients connected using CLS... also with some problems...network???&lt;BR /&gt; Some JRE/RMI clients &lt;BR /&gt;and 2-3 other vms-nodes running without problem&lt;BR /&gt;&lt;BR /&gt;Today I got inabout 50 new printjobs with errors like:&lt;BR /&gt; %PSM-E-WRITEERR followed by&lt;BR /&gt;&lt;BR /&gt;-SYSTEM-F-LINKDISCON&lt;BR /&gt;-SYSTEM-F-NOIOCHAN&lt;BR /&gt;-SYSTEM-F-CONNECFAIL&lt;BR /&gt;&lt;BR /&gt;most of them like this one:&lt;BR /&gt;                         BAR_SFT           3  Retained on error&lt;BR /&gt;       %PSM-E-WRITEERR, error writing !AS&lt;BR /&gt;       -SYSTEM-F-NOIOCHAN, no I/O channel available&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Also, HP people are installing new printers. Changing from Intermec to Zebra printers, i.e from LAT to TCPIP&lt;BR /&gt;They have created 72 new queues for these new tcp printers. &lt;BR /&gt;&lt;BR /&gt;There have been some "old vms-guys" looking into the problem, but... they arn't old enought:) (And I have only spent 10 years with vms commands like copy and delete, never been close to stuff like sysgen and autogen)&lt;BR /&gt;&lt;BR /&gt;Thanks a lot for all your help! &lt;BR /&gt;&lt;BR /&gt;/Klaes-Goran&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Dec 2005 03:30:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943587#M73008</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-12-01T03:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943588#M73009</link>
      <description>Found below in result from autogen. Will it help to raise lockidtbl from 6000 to 50000? What a huge difference, why? Is a value = 50000 "normal" for lockidtbl?&lt;BR /&gt;Yes, I'm going to change it and reboot since its not dynamic.&lt;BR /&gt;&lt;BR /&gt;LOCKIDTBL parameter information:&lt;BR /&gt;        Feedback information.&lt;BR /&gt;           Old value was 6000, New value is 46960&lt;BR /&gt;           Current number of locks: 67898&lt;BR /&gt;           Peak number of locks: 89088&lt;BR /&gt;&lt;BR /&gt;RESHASHTBL parameter information:&lt;BR /&gt;        Feedback information.&lt;BR /&gt;           Old value was 4096, New value is 131072&lt;BR /&gt;           Current number of resources: 47279&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/Klaes-Goran</description>
      <pubDate>Thu, 01 Dec 2005 04:10:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943588#M73009</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-12-01T04:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943589#M73010</link>
      <description>Klas-GÃ¶ran,&lt;BR /&gt;&lt;BR /&gt;you first need to troubleshoot your printing problem based on the print-symbiont, which is controlling the print-queue, on which the error is happening (LATSYM or UCX$TELNETSYM).&lt;BR /&gt;&lt;BR /&gt;TELNET print symbiont processes are called TCPIP$TNSx in recent versions of TCPIP. They should have a logfile in SYS$SPECIFIC:[SYSEXE]TCPIP$TELNETSYM_&lt;QUEUE-NAME&gt;.LOG.&lt;BR /&gt;&lt;BR /&gt;Once you find such a print-symbiont process in your system, issue a SDA&amp;gt; SHOW PROC/CHAN/ID=&lt;PID-OF-SYMBIONT-PROCESS&gt; to find out how many channels it has. If the ni. of channels is near CHANNELCNT, this would explain the NOIOCHAN error.&lt;BR /&gt;&lt;BR /&gt;See &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=941760" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=941760&lt;/A&gt; for a procedure to report the Symbiont PIDs for all the device queues...&lt;BR /&gt;&lt;BR /&gt;Volker.&lt;BR /&gt;&lt;/PID-OF-SYMBIONT-PROCESS&gt;&lt;/QUEUE-NAME&gt;</description>
      <pubDate>Thu, 01 Dec 2005 06:08:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943589#M73010</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-12-01T06:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943590#M73011</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt;It is network related! Suddenly some printer didn't reply on tcptraceroute. HP-guys will take care of it, not my problem any more.&lt;BR /&gt;&lt;BR /&gt;I have learned a lot these days, thanks a lot!&lt;BR /&gt;&lt;BR /&gt;/Klaes-GÃ¶ran&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 07 Dec 2005 04:34:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943590#M73011</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-12-07T04:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: printer problems PSM-E-WRITEERR</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943591#M73012</link>
      <description>closing</description>
      <pubDate>Wed, 07 Dec 2005 04:35:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/printer-problems-psm-e-writeerr/m-p/4943591#M73012</guid>
      <dc:creator>Klaes-Göran Carlsson</dc:creator>
      <dc:date>2005-12-07T04:35:22Z</dc:date>
    </item>
  </channel>
</rss>

