RE: More ILE 101

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

Joe, like you, I haven't played there yet, but that matches my expectations
precisely.  Service programs compiled as *CALLER, when called from a *NEW
AG, will not share any resources with other instances of the service
program.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
Sent: Monday, April 12, 2004 4:58 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: More ILE 101


> From: Joel Cochran
> 
> Service programs, by contrast are always created with
> *CALLER unless there is a specific feature or performance need to use
a
> 'named' activation group.

This brings up an interesting issue.  Service programs, reinitialization
and the joys thereof.

For my tools, I LOVE to have ACTGRP(*NEW) on the command processing
program, and *CALLER On everything else.  This allows me to use *INZSR
to do initialization even in called programs, and basically not set on
*INLR anywhere.  I leave files open, expect variables to retain state
between program calls, and all kinds of goodies.

So, do I have problems when I do that with a service program?  When two
jobs call the same service program, I assume they have their own storage
for variables, right?  If I declare a bunch of variables in the global
section of a procedure, they're not shared between jobs, are they?

I'm just asking - haven't gotten around to doing a lot with them yet.

Joe

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.