Parm Value Changed on Dynamic Call in free

Canuhp — Tue, 04 Oct 2011 15:08:41 +0000

I have a prototype in my free program to call an external program. The parms on my prototype include two fields that are defined as 2S 0. The value of these two fields are 00 and 01 at the time of the call tothe prototype. Using debug, I step into the program being called and the value of these two variables have changed when I look at the entry list in that program. The called program is not written in free. I have tried this call with and without the CONST keyword. How can I keep this from happening?

What’s your fastest /’Unique number’ issue method?

Yorkshireman — Mon, 25 Jul 2011 08:53:20 +0000

Once again I need to incorporate a mechanism which will issue a unique number as an object discriminator.

I’m sure we’ve all been there. – Incorporate a timestamp – quick and almost always unique, though this application will be busy, so the multiple ‘threading’ is attractive, Big problem is the length though, I only have 10 bytes.

Maybe pack the numbers into printable alpha numeric? use a radix of 36?

A record on a file (yawn) slow, need to Q for a lock, but a flexible way of doing it, and understandable by ‘users’

a data area – its a file really, but maybe quicker to operate? same locking issues

A User space? – are they going to be quicker than data areas?

So – anyone any ideas? I can manage the bit about making it unique across systems by adding a boxID prefix (Darn – another byte lost!)

While I’d like to go with timestamp. I’m thinking I’m forced to use a sequential ascending number, so any helpful info / discussion about access times would be good.

Thanks All

IT Answers » IBMi RPGLE

Parm Value Changed on Dynamic Call in free

What’s your fastest /’Unique number’ issue method?