Re: A dumb *S36 question - printer problem

Anybody come up with the mentioned PTF reference.

My S36 program prints one spool item for each PO (why? who knows?).  When I
print them to P4, a S36 printer on stop, they all end up in the S36 spool as
completed reports.  When I print them to P9, a "mapped" S36 printer, they
whoosh to the "mapped" outq on the AS400.  Interesting is that the first
whatever number of PO's get stuck in "OPN" status and the last and final PO
always prints fine.  The "OPN" PO's are stuck at 0 pages forever.  The
workaround is to print them to P4 and then do a CHANGE ID,P9,P4 to whoosh
them to the outq on the AS400 side where the print perfectly.

Jerry


Jerome Draper, Trilobyte Software Systems, since 1976
Network and Connectivity Specialist -- Mac's, LAN's, PC's, Windows, Linux,
Sun, and AS/400
Representing Synapse, CLI, Nlynx, Perle, Lucent, 3Com and Others .....
http://www.trilosoft.com - (415) 457-3431 - (415) 258-1658fax -
jdraper@trilosoft.com



----- Original Message -----
From: ken shields <kjs@idirect.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, September 18, 2001 2:39 PM
Subject: Re: A dumb *S36 question - printer problem


> Yes, the operator at Montreal was not in to-day , so I couldn't get the
> PTF reference.
> I will send this message to my office, and will reply with it asap.
> In the meantime, if you have a service agreement with IBM , let them
> know what your problem is, they might be able to send it Purolator
> quicker than me.
> Ken
>
> "Barry L. Kline" wrote:
> >
> > ken shields wrote:
> > >
> > > Had a similar problem on a 170, several moons ago.
> > > Problem was the rpg LR logic would not clos the mapped outq file.
> > > There was a special patch supplied by IBM, to fix the problem.
> > > The office is in Montreal, so I don't have the patch reference.
> > > Will try to get it for you.
> > > Ken
> > >
> >
> > This is interesting.  I have a different problem but one related to
> > mapped outqs. There are some jobs created in sbs QSYSWRK that service
> > the mapped output queues. When the M36 machine is brought down
> > properly, these jobs sometimes never end.  A WRKACTJOB SBS(QSYSWRK)
> > shows them in the 'end' status but they never go away.  You can wait
> > 'til hell freezes over and they won't go.  Should you get impatient
> > and issue a PWRDWNSYS *IMMED RESTART(*YES) you'll have the pleasure of
> > dealing with an OS/400 ABEND, which will cause the System Attention
> > light to come on.  The subsequent IPL needs to be done manually and
> > takes a painfully long time.  My solution so far has been to wait 10
> > minutes, then issue a ENDJOBABN command against each of the offending
> > jobs before proceeding with system backup, etc.
> >
> > Has anyone in this thread heard of this before.  Ken, is this problem
> > affected by the PTF you mentioned?
> >
> > Barry
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> --
> Best Regards
> Ken Shields
> Home phone: 905 404-2062
> Bus  phone  905 725-1144 (326)
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>