× 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: VLTASK?
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Mon, 16 Mar 1998 14:54:17 -0600

You didn't give your release and PTF level, so look through this APAR
and see if you have the appropriate PTF.

Item MA17687

  APAR Identifier ...... MA17687       Last Changed..98/02/12  
  LIC-COMM-APPCTCP-LOOP
 
 
  Symptom ...... LP LOOP              Status ........... CLOSED  PER
  Severity ................... 2      Date Closed ......... 98/02/04
  Component .......... 9400DG300      Duplicate of ........
  Reported Release ......... 370      Fixed Release ............ 999
  Component Name 5763 5769 5716       Special Notice
  Current Target Date ..              Flags
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 310   : PTF not available yet
  Release 320   : PTF not available yet
  Release 360   : PTF not available yet
  Release 370   : MF18270 available 98/02/11 (1000 )
  Release 410   : MF18310 available 98/02/11 (1000 )
  Release 420   : MF18311 available 98/02/12 (1000 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
   System went into a loop with VLTASK using all/most of the
   CPU resources, but no new LIC Logs we being logged.  Also,
   the DASD utilization was growing about 3% per hour.  Via
   a PEX trace we found that VLTASK was creating 8-page extents
   very quickly.  LIC Log & Streams I/O developers analyzed the
   MSD and found a loop in an SK module, but it was passed a
   bad pointer from an unknown source, causing a loop in the
   code module.
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
  The VLTASK went into a loop and was using all/most of the CPU
  resources, but no new LIC logs were being created.  Also, DASD
  utilization was growing at 3% per hour because the VLTASK was
  creating 8-page extents very quickly.  The loop was isolated in
  #skdirtn.
 
 
  PROBLEM CONCLUSION:
  The message formatting program (#skdirtn) has been changed to
  recognize and avoid an infinite loop when processing a chain of
  messages.
 
 
  TEMPORARY FIX:
 
 
  COMMENTS:
 
 
  MODULES/MACROS:   #SKDIRTN
 
 
  SRLS:      NONE
 
 
  RTN CODES:
 
 
  CIRCUMVENTION:
  None.
 
 
  MESSAGE TO SUBMITTER: UPDATED 02/09/98

MESSAGE TO SUBMITTER: UPDATED 02/09/98

=======================================================================

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: BVStone@Taylorcorp.com [SMTP:BVStone@Taylorcorp.com]
> Sent: Monday, March 16, 1998 11:11 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      VLTASK?
> 
> For the past hour we've had a job called VLTASK running on our
> developement machine and just brining it to it's knees.  Anyone know
> what this job is?
> 
> Bradley V. Stone      
> bvstone@taylorcorp.com
> http://prairie.lakes.com/~bvstone/
> "Seinfeld's van!  SEINFELD'S VAN!"
> 
> 
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.