🚀 go-pugleaf

Michael J. Wendling (wendling@jupiter.SLAC.Stanford.EDU) wrote:


: We recently upgraded our Alphas to VMS 6.1.  Since then we've had
: problems with batch jobs being killed due to CPU limits.  A job may be
: killed after only 20 seconds or so when the queue CPU limit is set to 
: one hour.  Has anyone seen similar problems?  Is this a known problem?
: Is there a patch?

: On a similar note, is there a difinitive list of bugs/patches for 
: VMS 6.1?

: Thanks,
: Mike 


There's a patch for this problem...

Copyright (c) Digital Equipment Corporation 1994. All rights reserved.

PRODUCT:    OpenVMS AXP

COMPONENT:  Process Management

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  AXPSYS02_061
     ECO Kits Superseded by This ECO Kit:  AXPSYS01_061
     ECO Kit Approximate Size:  810 Blocks
     Kit Applies To:  OpenVMS AXP V6.1
     System Reboot Necessary:  Yes


ECO KIT SUMMARY:

An ECO kit exists for Process Management on OpenVMS AXP V6.1.  This
kit addresses the following problems:

Problems addressed in AXPSYS02_061 kit:

      o  Applications that call the wait form of system services cause a
         hang.    The   cause   is   that   the   service  has  finished
         asynchronously but the application is still waiting in LEF.

         The problem has been found to be generally  applicable  to  all
         system services that have a wait form counterpart.


      o  On systems running OpenVMS AXP  6.1,  when  a  process  with  a
         non-zero  CPU limit SPAWNs one or more subprocesses, each SPAWN
         halves the CPU limit (as expected), but on returning  from  the
         SPAWN  the  unused  CPU  time isn't credited back to the parent
         process.  After some number of successful  SPAWNs  the  process
         will receive a %SYSTEM-F-EXCPUTIME error and will not allow the
         user to continue.  The user will have to log out and  log  back
         in to start another process.

INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system
must be rebooted.  If the system is a member of a VMScluster, the
entire cluster should be rebooted.

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

You can get the 'readme' files of VMS patches via anonymous ftp from
ftp.service.digital.com. 

Not all VMS patches are on ftp.service.digital.com, and the requirements 
to extract the patches were documented in the June 6 Customer Update:

"REQUIREMENTS

 If you have a Digital software product support contract, you can access the
 service by using your Customer Obligation ID and DSNlink access code. If you
 do not have DSNlink, you can contact Digital to request Internet FTP access.
 In this case, only the DSNlink key will be generated for the given
 Obligation ID.
 . . .
 Questions can be directed to 1-800-354-9000; ask for the DSNlink hotline and
 specify "Questions on Internet Access to Patches."  "


--Gerald (Jerry) R. Leslie
  Staff Engineer
  Dynamic Matrix Control Corporation    (my opinions are my own)
  P.O. Box 721648                       9896 Bissonnet
  Houston, Texas 77272                  Houston, Texas, 77036
  713/272-5065                          713/272-5200 (fax)
  gleslie@isvsrv.enet.dec.com
  jleslie@dmccorp.com