RE: MCH3402 -- MIDRANGE-L

        Look for the ones that have been created/changed lately.

        John Carr


        From:   Leland@dleland on 10/11/99 10:19 AM
        To:     MIDRANGE-L@MIDRANGE-L@midrange.com@SMTP@EXCHCONNECT
        cc:      

        Subject:        RE: MCH3402

        Unfortunately, there are many other programs being called in the
job.� It's an "async" job which waits for an entry to hit a data queue and
then calls other programs with the data received.� Looks like I could be in
for a long hunt here.

        Thanks for the reply, 
        Dave 

        -----Original Message----- 
        From: John P Carr [ mailto:jpcarr@tredegar.com] 
        Sent: Friday, October 08, 1999 7:39 PM 
        To: MIDRANGE-L 
        Subject: Re: MCH3402 



        ������� Dave 

        ������� Are ANY,� I mean ANY other programs being called within this
job 
        stream ?? 
        ������� Don't look at just these two and think you looked
everywhere. 

        ������� For example, 

        ������� PGMA� calls PGMB 
        ������� PGMB� returns to PGMA 

        ������� sometime later 

        ������� PGMA calls PGMC 
        ������� PGMC� returns to PGMA 

        ������� Sometime later 

        ������� PGMA calls PGMB 
        ������� PGMB returns to PGMA 

        ������� PGMA goes down for a MCH� error. 

        ������� Who's fault ??�� PGMC stepped on the 
        ������� PSSA or Working Variables area of 
        ������� PGMA without PGMB knowing it,�� It 
        ������� wasn't a problem till PGMA tried to 
        ������� refer to those variables(or other things 
        ������� like program names, parms, etc) 
        ������� that it discovered someone TOASTED 
        ������� PGMA's area. 

        ������� It probably isn't PGMA,� nor PGMB 
        ������� but someother program in the stack 
        ������� that may or may not logically be called every time. 

        ������� What makes it worse is that you could 
        ������� run it many times without PGMA happening 
        ������� to refer to the particular area that got stepped 
        ������� on, or the problem program being called. 

        ������� But. I'd be willing to bet that� It's a mismatched parm
somewhere. 

        ������� You have to look at EVERY program that may logically 
        ������� be called. 

        ������� John Carr 




        ������� From:Leland@dleland on 10/08/99 03:06 PM 
        ������� To:�� MIDRANGE-L@MIDRANGE-L@midrange.com@SMTP@EXCHCONNECT 
        ������� cc:��� 

        ������� Subject:����� MCH3402 

        ������� Okay, I'm stumped.� I know that Hans has said when these MCH
errors 
        occur, it's usually not the operating system but a bug in a user
program.� 
        Well, we have 2 programs that get these (only once and a while
though) and 
        I've been on a hunt to find the culprit but have been unable. 

        ������� I've checked all the parameters of the calling and receiving

        programs and they match.� I'm at a loss.� What other things should I
be 
        looking for? 

        ������� Dave 




        +--- 
        | This is the Midrange System Mailing List! 
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com. 
        | To subscribe to this list send email to
MIDRANGE-L-SUB@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 
        +--- 




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---