RE: SRC B600-0314 -- MIDRANGE-L


SRC B600 0314   OS/400 Licensed Program Failed
Failing item - AJDG301          Probable Cause (%)      100
Perform VLIC PIP8 Problem Isolation Procedures.

1       a       Select manual IPL on the panel
        b       Select function 3 - Start IPL
If the same SRC occurs contact your next level of support for
assistance.

If it the same SRC doesn't occur - but another does, use that code &
re-run problem diagnosis.


Now you don't say what you were running when the SRC occurred.
See if any of these ring a bell.  I've omitted any that would have been
fixed by a PTF cum package within the last 6 months (you aren't that bad
are you ?  :-)   ), or ones caused by gross stupidity - like the use who
tried to do a SAVOBJ OBJ(*ALL) LIB(QSYS) STG(*FREE):

NOTE THE LAST CHANGED DATE ON THIS FIRST (SA59799) ITEM !!



Item SA59799

  APAR Identifier ...... SA59799       Last Changed..97/12/30  
  OSP CONVERGED DEBUGGER SUPPORT ON IMPI
 
 
  Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
  Severity ................... 4      Date Closed ......... 96/11/21
  Component .......... 5763SS100      Duplicate of ........
  Reported Release ......... 320      Fixed Release ............ 999
  Component Name 5763 OS/400 ROC      Special Notice           HIPER
  Current Target Date ..              Flags  RESTART/BOOT/IPL
  SCP ...................
  Platform ............                 PERVASIVE
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 320   : SF36969 available 97/08/18 (1000 ) (ie. NOT on any cum
pkg)
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  SRCB6000314
  Provide system function which enables customers to write source
  debuggers for OPM COBOL, OPM RPG, and OPM CL programs on AS/400
  Internal MicroProgrammed Interface (IMPI).
 
  MF14110 and SF36969 are corequisite PTFs - if MF14110 is
  applied without SF36969, SRCB6000314 can occure.
 
 
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
  ******************************************************
  * PROBLEM: (SA59799) Licensed Program = 5763SS1      *
  *          SRC B600 0314                             *
  *          Crash Requiring an IPL to Recover         *
  ******************************************************
  * USERS AFFECTED: All AS/400 users.                  *
  ******************************************************
  * RECOMMENDATION: Apply PTF SF36969.                 *
  ******************************************************
  Provide system function which enables customers to write source
  debuggers for OPM COBOL, OPM RPG, and OPM CL programs on AS/400
  Internal MicroProgrammed Interface (IMPI).
 
 
  PROBLEM CONCLUSION:
  Base debug support has been enhanced to allow customers to write
  source debuggers for debugging OPM RPG, OPM CL, and OPM COBOL
  programs.
 
  The ILE Debug APIs are documented in the V3R7 System Application
  Programmers Interface Reference Manual.
 
 
  TEMPORARY FIX:
                          *********
                          * HIPER *
                          *********
 




Item MA12299

  APAR Identifier ...... MA12299       Last Changed..95/12/14  
  OSP-SRCB6000314-UNPRED
 
 
  Symptom ...... IN INCORROUT         Status ........... CLOSED  UR1
  Severity ................... 2      Date Closed ......... 95/12/13
  Component .......... 9400DG300      Duplicate of ........
  Reported Release ......... 305      Fixed Release ............ 310
  Component Name 5763 5738 5716       Special Notice
  Current Target Date ..              Flags
  SCP ...................
  Platform ............
 
  Status Detail: APARCLOSURE - APAR is being closed.
 
  PE PTF List:
 
  PTF List:
  Release 305   : No PTF planned
  Release 310   : No PTF planned
  Release 360   : No PTF planned
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
   System failed during normal operations with SRCB6000314.
   The failing task appeared to be in an exception loop, and was
   trying to wrap its joblog.  VL02001723 and VL1D000200 were
   logged three times before the failure.
 
 
 
 
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
   System failed during normal operations with SRCB6000314.
   The failing task appeared to be in an exception loop, and was
   trying to wrap its joblog.  VL02001723 and VL1D000200 were
   logged three times before the failure.
 
 
 
 
 
 
 
  PROBLEM CONCLUSION:
 
 
  TEMPORARY FIX:
 
 
  COMMENTS:
  The process became masked for interrupts while running a program
  that was in an exception handling loop.  This caused the job
  message queue to hit an internal design limit which caused the
  job to enter termination phase.  When the job went into
  termination phase it became unmasked and tried to wrap the job
  message queue.  After many attempts to wrap the job message
  queue, the internal limit was hit again.  When the limit was hit
  three times in termination phase the machine was terminated
  abnormally (B6000314).
 
 
 
 
 
 
 
 
 
 
 
 
  MODULES/MACROS:
 
 
  SRLS:
 
 
  RTN CODES:
 
 
  CIRCUMVENTION:
  Use *NOWRAP for the job message queue full action and a large
  job message queue maximum size.
 
 
 
 
 
 
 




... 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          http://www.NxTrend.com


        -----Original Message-----
        From:   Dave Mahadevan [SMTP:mahadevan@fuse.net]
        Sent:   Tuesday, December 30, 1997 7:31 PM
        To:     midrange-l@midrange.com
        Subject:        SRC B600-0314

        Folks:

        I had a system attention on my CISC (no snickering please) box
on V3R2
        with this code.  My operator guide has B600-0204,B600-0615 both
refer to
        machine address/aux storage used up.  Funny thing is we IPL
everyday
        (yes Virginia there are some people out there who believe in
being a
        good boy).  I have enough aux storage (50% used).  If any of you
have a
        manual, can you look up B600-0314 ?

        --
        Thank You.

        Regards

        Dave Mahadevan.. mailto:mahadevan@fuse.net


+---
| 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
+---