Brian,
I kinda stepped over some kjey figures:
We compile using CRTPGM and ACTGRP(*CALLER)
We use *CALLER to preserve the same activation group during the whole
job.
I thought it was like using DFTACTGRP but with your reply, I figure it
is not.
Sorry,
Pascal Bellerose
pascal_bellerose@xxxxxxxxxxxx
Cascades Canada inc.
Analyst-Programmer-Helpdesk
Telephone: 819-363-6114 (2114)
Fax: 819-363-6155 (6155)
Do you really need to print this e-mail? Change your environmentality!
Le 10 Octobre, 2007 à 15:30, Brian Parkins <PARKIB@xxxxxxxxxx> a
écrit :
Pascale, can you clarify please? (I am a little confused about your
situation.)
Here's our situation:
PGM1 is a ILE RPG Program in LIB1. Was compiled with ACTGRP(*DFT).
SRV1 is a service program in LIB1
PRC1 is a procedure of SRV1.
PGM1 is using PRC1 in an Eval operation.
There is no ACTGRP(*DFT) on the CRTPGM command - how did you create
PGM1?
Do you mean DFTACTGRP(*YES)?
DFTACTGRP(*YES) can only be specified on the CRTBNDxxx commands. If
DFTACTGRP(*YES) was specified, then you would not be able to perform a
Procedure Call to PRC1. (Procedure Calls are not possible within
programs
explicitly bound to the Default Activation Group (DAG).)
RCLRSC only affects resources in the DAG. To "clean up" resources in a
Named Activation Group you can use the RCLACTGRP command.
Brian Parkins.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with
number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
As an Amazon Associate we earn from qualifying purchases.