RE: MCH3402 -- MIDRANGE-L

Title: RE: MCH3402

Ah, so it's the default activation group that's the problem. I use ILE exclusively for new applications also but just use the default activation group instead of a named one. If I created one named activation group and used this for all my applications, would I be okay then?

Dave

-----Original Message-----
From: John Taylor [mailto:john.taylor@telusplanet.net]
Sent: Thursday, October 14, 1999 1:25 PM
To: MIDRANGE-L@midrange.com
Subject: Re: MCH3402

Hi Dave,

I wouldn't consider this a bug. It is well documented that the *DFT activation group is active for the entire duration of the job. I believe it's intent was to allow the use of RPG4 syntax for those that didn't want to jump right into ILE.

I use ILE exclusively for new applications and have never run into this problem, because my applications are architected to use named activation groups. Most of my service programs also run with ACTGRP(*CALLER), but the application design ensures that this never ends up in the default AG.

John Taylor

----- Original Message -----

From: Leland, David

To: 'MIDRANGE-L@midrange.com'

Sent: Thursday, October 14, 1999 10:00

Subject: RE: MCH3402

Thanks everyone for your suggestions regarding my mysterious MCH3402 problem. I tried Barb's suggestion and removed one RCLRSC from one CL program. That fixed it. Her following statement described our situation - "Check your use of RCLRSC - it can cause problems especially for *CALLER service programs running in the default activation group (the file gets closed, but the service program storage stays active)."

Now, this seems like a "bug" to me and I can't find it documented anywhere. We're starting to use more and more *CALLER service programs and I'm concerned this problem will crop up again. Any thoughts?

Dave

-----Original Message-----
From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com]
Sent: Wednesday, October 13, 1999 9:04 AM
To: MIDRANGE-L@midrange.com
Subject: RE: MCH3402

>Date: Tue, 12 Oct 1999 14:31:32 -0500
>From: "Leland, David" <dleland@Harter.com>
>
> ... Unfortunately, I'm not sure which program to
> "add the padding" to.

Dave, you would add the padding to the program getting the MCH3402.

But (blush) I must confess that I was thinking of MCH3601 (pointer not set), not
MCH3402 when I wrote my note. MCH3402 is most commonly issued for RCLRSC
problems. Check your use of RCLRSC - it can cause problems especially for
*CALLER service programs running in the default activation group (the file gets
closed, but the service program storage stays active). There are some other
complex scenarios where RCLRSC causes files to be closed but storage to remain
active.

We have one PTF related to MCH3402 and RCLRSC:

V3R1M0 SF50631
V3R2M0 SF48117
V3R6M0 SF47832
V3R7M0 SF48116
V4R1M0 SF48503
V4R1M4 SF48504
V4R2M0 SF48541
V4R3M0 SF48555

Sorry for the misleading first answer,
Barbara

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