Iain,

We put the patch on about 3 weeks ago and haven't had the problem since.  
Thanks again for pointing this APAR out to us.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Iain Robertson
Sent: Monday, December 06, 2010 4:00 AM
To: [email protected]
Subject: Re: strange issues with LE abending, looking for pointers as to where 
to even look..

Rex,

You say you're on IDMS R17
Do you know if you have CA IDMS APAR RO12844 applied? This fixed an issue we 
found at R17 with batch jobs abending with apparently random S0C7s & S0C4s. As 
in your case, a rerun of the job went through OK.



Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: [email protected]


> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:[email protected]] On Behalf Of Pommier, Rex R.
> Sent: 03 December 2010 16:27
> To: [email protected]
> Subject: strange issues with LE abending, looking for
> pointers as to where to even look..
>
> Hi list,
>
> I just got a call from an applications programmer.  They're
> having some strange issues showing up in LE with programs
> abending with S0C4 and S0C7 abends, but not where they've seen before.
>
> For example, yesterday, they received a S0C7 in a job.  They
> reran the job using the same inputs and it ran clean.  But
> the abend didn't give them any indication as to what was
> happening.  Here's the JES log of the abend.
>
> +CEE0374C CONDITION=CEE3207S TOKEN=00030C87 59C3C5C5 00000000  649
>           WHILE RUNNING PROGRAM UNKNOWN
>           AT THE TIME OF INTERRUPT
>           PSW     078D1000 80093EAA
>           GPR 0-3 8708D300 0007F98C C7D14040 00BFF048
>           GPR 4-7 8007F978 00093EA8 0007F98C 000941B0
>           GPR 8-B 000942E0 00094B00 0008B068 0006FD28
>           GPR C-F 0007F828 0007F9CC 00000000 00000000
> IEA995I SYMPTOM DUMP OUTPUT  662
> SYSTEM COMPLETION CODE=0C7  REASON CODE=00000000
>  TIME=05.48.39  SEQ=02747  CPU=0000  ASID=0060
>  PSW AT TIME OF ERROR  070C0000   80D0F35E  ILC 6  INTC 07
>    NO ACTIVE MODULE FOUND
>    NAME=UNKNOWN
>    DATA AT PSW  00D0F358 - F933908C  30044740  C8389180
>    GR 0: 00000880   1: 000B0780
>       2: 01DFB680   3: 0708D4B0
>       4: 00FDD858   5: 00093EA8
>       6: 0007F98C   7: 0000001B
>       8: 01F97D80   9: 0708D448
>       A: 0008B068   B: 01DFAFE8
>       C: 80D0EE60   D: 084C7E70
>       E: 0000030B   F: 00000000
>  END OF SYMPTOM DUMP
> IEF450I USACU011 S0015GSI - ABEND=S0C7 U0000 REASON=00000000
> -S0015GSI          *S0C7    700   1340    .00    .00     .0
>
> The abend this morning was a S0C4 with the same symptoms.
> S0C4 "while running program unknown".  PSW is 'no active
> module found".  They just restarted the job at the abending
> step and it ran fine.  Environment is z/OS 1.10 and IDMS
> release 17.  Batch COBOL calling IDMS.
>
> Any ideas as to where to even start looking?
>
> Thanks.
>

The information contained in this e-mail may contain confidential and/or 
privileged information and is intended for the sole use of the intended 
recipient. If you are not the intended recipient, you are hereby notified that 
any unauthorized use, disclosure, distribution or copying of this communication 
is strictly prohibited. If you received this e-mail in error, please reply to 
sender and destroy or delete the message and any attachments. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to