RE: RMTW* jobs now appear along with remote writers

Unfortunately it appears this will only be PTF'd to V4R1, V4R2 & V4R3
(as per APAR SA73727).
The PTF's are in test status at the moment and not generally available
yet.

Depending on how many remote writers you have, you may want to change
your startup program to start them explicitly instead of with *ALL -
which of course is a pain when you add more writers.
However, maybe if you tried STRRMTWTR name   for the ones you already
know the names of, followed by a short DLYJOB for maybe 15 seconds, then
a STRSRTWTR *ALL  you would take care of any newly created writers in
the future, and it may reduce/eliminate the chance of the problem
occuring.

As you mentioned for SA73373, SA73727 also says:
 COMMENTS:
  This PTF will limit the number of undesired writers started when
  simultaneous STRRMTWTR *ALL commands are run.  However, totally
  eliminating this occurrence is not possible.


Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Sclind2 [SMTP:Sclind2@aol.com]
> Sent: Tuesday, May 19, 1998 5:20 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RMTW* jobs now appear along with remote writers
> 
> We do most of our printing using remote OUTQ'S (IP addresses, Host
> Print
> Transform, etc).
> 
> Now whenever I issue a STRRMTWTR *ALL, I get two jobs in QSPL; one
> with the
> actual writer name and one that starts with RMTW*.
> 
> This seems to have started after applying cum 97343.  I see APAR
> SA73373
> states that no PTF is planned for V3R6 or V3R7, and even in later
> releases
> "totally eliminating this occurrence is not possible".   
> 
> Also, in QSYSOPR the forms change message reads "Load form type 'xxx'
> device
> writer RMTW00001" (rather than the actual OUTQ/writer name).  This is,
> of
> course, confusing to the users who respond to the message.  I had to
> change
> the CPA3394 message in QSYS to reference &2 (the OUTQ name) rather
> than &1
> (the writer name) in the first level text.
> 
> Does anyone know why this started, and if anything can be done to
> eliminate
> these jobs in V3R7?
> 
> Scott Lindstrom
> Zenith Electronics
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---