Thanks Chris,
I'd like to see an example of that to be sure I've understood fully what you mean. Any links?
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Chris Bipes
Envoyé : vendredi 9 janvier 2009 16:56
À : Midrange Systems Technical Discussion
Objet : RE: ACTGRP
You can also go the IBM generic parms,
Parm1 unsigned long integer (length of parm2)
Parm2 Variable length character parm.
The first xx bytes of parm2 identify the format of parm 2 data.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of BMay@xxxxxxxxx
Sent: Friday, January 09, 2009 7:41 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: ACTGRP
You are most welcome David.
As for the PARM1, PARM2, etc. solution you mentioned, I have never been a big fan. Inevitably, you will run into a parameter that will not fit in your generic parm and then you have to modify all programs that use this technique again to increase the parameter sizes.
As for a preference, I have seen and/or used all three methods in the past.
If it were me, I would probably go the data area route. Just be sure you create the data areas in QTEMP so you don't have sessions stomping each other's parameters.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
