Of course, the first line should be :

"(1) You have an ISV product that is detecting a new address space or jobstep - 
(maybe via the IEFUJI or IEFUSI)." 

Rob Scott
Lead Developer
Rocket Software
77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA
Tel: +1.781.684.2305
Email: [email protected]
Web: www.rocketsoftware.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Rob Scott
Sent: 15 April 2014 10:20
To: [email protected]
Subject: Re: Dumps when starting Started Tasks

Only a guess, however this is what my first suspicion would be :

(1) You have an ISV product that is detecting a new address or jobstep - (maybe 
via the IEFUJI or IEFUSI).
(2) The ISV product exit is attempting to notify its associated server via a 
cross-memory post using an ASCB address stored somewhere in common storage.
(3) It is possible your ISV product has terminated without cleaning up, leaving 
behind the exit and the common storage control block.
(3a) It is also possible that the common storage block has been overlaid 
somehow without the ISV server terminating.
(4) The exit is attempting to cross-memory post using bad (or out of date) 
information from the common storage control block.

This would explain the S602 abends that you are seeing.

Capture a dump and you should be able to find the address of the POST-issuing 
program.   

Rob Scott
Lead Developer
Rocket Software
77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA
Tel: +1.781.684.2305
Email: [email protected]
Web: www.rocketsoftware.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Ferran Perxas
Sent: 15 April 2014 08:29
To: [email protected]
Subject: Dumps when starting Started Tasks

Good morning,

Yesterday we had an issue I'd like to share just in case someone has 
experienced it before.

Sometime in the morning this piece of log appeared on syslog

IEE501I CONSOLE UC4CN000 FAILED, REASON=ABTERM.  ALL ALTERNATES UNAVAILABLE , 
CONSOLE IS NOT SWITCHED
IEA631I  OPERATOR UC4CN000 NOW INACTIVE, SYSTEM=CPUA    , LU=UC4TR000

IEE828E SOME MESSAGES NOW SENT TO HARDCOPY ONLY

Please notice this is not a "standard" console, it is somehow related to the 
product UC4 which is a Batch scheduler. We are still talking to support in 
order to know how this exactly works.

The real problem was that from this moment no started tasks could be started, 
all of them crashed on start:

START MVTASA.ST8005
$HASP100 MVTASA   ON STCINRDR
OMS9612I PROCESSING INIT (STC09784)
IEF695I START MVTASA   WITH JOBNAME MVTASA   IS ASSIGNED TO USER STCSYS
 , GROUP STCGRP
$HASP373 MVTASA   STARTED
IEA995I SYMPTOM DUMP OUTPUT 893
SYSTEM COMPLETION CODE=602  REASON CODE=00000000
 TIME=08.32.24  SEQ=09184  CPU=0041  ASID=008F
 PSW AT TIME OF ERROR  070C1000   80FEB316  ILC 2  INTC 0D
   NO ACTIVE MODULE FOUND
   NAME=UNKNOWN
   DATA AT PSW  00FEB310 - 00181610  0A0D0000  00FF6258
   AR/GR 0: 00000000/84000000   1: 00000000/84602000
         2: 0181001D/00000000   3: 00000000/00F61100
         4: 00000000/008FFBF8   5: 00000000/000AB76C
         6: 00000000/89494736   7: 00000000/00FB8D00
         8: 00000000/00FEA621   9: 00000000/00000000
         A: 00000000/00000000   B: 00000000/008FECA8
         C: 00000000/00000041   D: 00000000/0BF00E78
         E: 00000000/00FF0280   F: 00000000/00000000
 END OF SYMPTOM DUMP
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=008F.
$HASP310 MVTASA   TERMINATED AT END OF MEMORY

We arrived a few minutes later. At this point some critical tasks in this shop 
required to be started as a started task so we had to stop and IPL the whole 
LPAR before major incidents appeared. With the fresh IPL the whole system 
worked fine.

The last few lines of log (stopping JES2) during the stop showed us these lines.

IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0024.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=002D.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME/ASID NOT AVAILABLE.
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY
$HASP310 INIT     TERMINATED AT END OF MEMORY

Has anyone experienced something similar?

Regards,
Ferran

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to