Re: Pointers? Based variables? in CL?

[rob@xxxxxxxxx]

95% of what most people on the iSeries are concerned with are the 
'traditional' stuff like file i/o, etc.  And you can already do most of 
this with CL.  Granted, api's and pointers do open up a whole lot of 
possibilities, but if people can already write a CL program that will read 
the employee master file and manipulate it, then, again, the 95% has been 
reached.

You need to do other security methods to control your data.

If it's such a big concern - delete or rename the commands CRTCLPGM & 
CRTCLMOD.  That should give you a nice false sense of security.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/21/2005 11:58 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Pointers? Based variables? in CL?






hi Vern,

> Tom, I don't understand your concern about V5R4. What in the article 
bothers 
> you if it "comes true"? I mean, the stuff is here now.

I think he's referring to the ability to call APIs that return pointers, 
such as string manipulation APIs, record read/write APIs, IFS directory 
reading APIs, etc.

That stuff is currently only available through HLLs, which require the 
customer to buy a WDS license from IBM.  Tom's concern is that now systems 

where they deliberately didn't buy the HLL compilers (possibly to prevent 
people from doing development on the machine because of the potential 
security/stability risks of allowing development) will now have access to 
most or all of the HLL's capabilities through ILE CL.


> One thing NOT mentioned that is even more important, IMO, is the ability 
to 
> call something using parameters BY VALUE. IOW, we can now call things 
like 
> the access() function and have it work right.

The *BYVAL stuff that we got in V5R3 is also a big deal. When you combine 
the two (pointers and *BYVAL) this gives you access to pretty much every 
API on the system, and unlocks pretty much all of the functionality on the 

system to a CL program.

And, I think that's Tom's point :)

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