× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: So Here's a Good Bug for You
  • From: Neil Palmer <NPalmer@xxxxxxxxxxx>
  • Date: Mon, 09 Jun 1997 14:52:54 -0400
  • Organization: NxTrend Technology - Canada

Al Barsa, Jr. wrote:
> 
> Hello All,
> 
> I recently had a job blow up because the wait time was (unreasonably) set
> at 1 second.  Well I'm a user (a four letter word) and shame on me.  Not so.
> 
> On my system (please check yours) I have two QBATCH classes, one in QSYS
> and one in QGPL (of course QSYS is higher in the library list).  It turns
> out that the system uses the one in QGPL, not QSYS (why there are two - who
> knows), and during V3R1 (I don't need to reiterate my feelings about this
> release.) the system changed the class in QGPL to a default wait time of 1
> second!
> 
> There was a PTF to fix this in V3R1, but it was issued after my system went
> to RISC.
> 
> So check your class QBATCH in QGPL.  If the default wait time is 1 second,
> you probably want to change it back to the proper shipped default of 120
> seconds.

I found this one when I upgraded to an early release of V3R1 about 2.5
years ago and my nightly backup job failed.  It crashed when the backup
job issued a STRSBS QINTER and I suppose it didn't respond within 1
second and issued a CPF1001.
I had to complain several times before they finally relented and issued
the PTF.
They first claimed they couldn't PTF it because they might change the
default wait time back to 120 seconds for someone who had deliberately
changed it to something else.  My argument was, who would change it to 1
second ?  Set the PTF exit program to only change back to 120 seconds if
currently set to 1 second.  Besides, doesn't everyone read the PTF cover
letters anyway ?  :-)
(Maybe that's why they wouldn't put it on a cum package, so you would
probably read the cover letter if you ordered it individually).

I also questioned why there were two QBATCH classes, but who knows !
The problem could occur with either the QBATCH class in QSYS or QGPL.
I believe if you upgraded to V3R1 the default wait time for the
QGPL/QBATCH class was changed from 120 seconds to 1.  HOWEVER if you
took delivery of a new machine from Rochester with V3R1 pre-loaded, the
QSYS/QBATCH class came with a 1 second default wait time.

The APAR is SA46363 and the V3R1 PTF is SF32088.
They still won't put it on a cumulative PTF package, so you must order
it separately (or just check the DFTWAIT time for the two QBATCH classes
on your system and if they show 1 second change back to 120 seconds).


-- 
... Neil Palmer                                      AS/400~~~~~      
... NxTrend Technology -Canada       ____________          ___  ~     
... Markham,  Ontario,  Canada       |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000 x238       |__________|_|______|_|______)   
... url:http://www.NxTrend.com        oo      oo   oo  oo   OOOo=o\   
... mailto:NPalmer@NxTrend.com     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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