Programming Considerations

LANSA Version 13 SP2

Programming Considerations


There are no increases in the maximum size of any LANSA feature because the limits are considered sufficient. This ensures greater compatibility between 32-bit and 64-bit applications. For example:

·        The maximum size of an RDMLX List is still 2 billion rows, with each entry being 2 billion bytes long.

·        The Built In Functions SND_TO_DATA_QUEUE and RCV_FROM_DATA_QUEUE may be used interchangeably.

·        Job Queue Emulation can use either a 32-bit or 64-bit Job Queue Monitor and jobs may be submitted from either 32-bit or 64-bit. Note that the 64-bit Job Queue Monitor will execute the submitted job as 64-bit, no matter which platform submitted the job.

 

PC Other Files which are loaded using a 32-bit ODBC driver will need to create a 64-bit DSN with the same name as that used to load the file, or use CONNECT_SERVER when deployed to re-direct IO to a 64-bit driver.

An ActiveX included in LANSA RDML must be a registered 32-bit version. To execute the ActiveX, a version must be registered which is of the same processor architecture as the LANSA runtime. That is, if the LANSA runtime is 64-bit then the 64-bit ActiveX must be registered on the deployed PC.