Can I override Pro*Fortran's limit on Fortran variable name lengths?

Question

The Fortran standards put a 31-character limit on the variable names in Fortran code. Some compilers allow you to exceed this as a compiler extension, and, unfortunately, our code has places where we actually do... The present software compiles and runs under with the Ingres 9.2 RDBMS, but we're starting the process of porting the code over to Oracle 11g.
The Pro*Fortran (we have release 1.8.79.0.0) precompiler only accepts the first 31 characters of a long var name (yes I found that limitation stated in the Pro*Fortran Precompilers guide). What I am wondering is if there is any way to override that and allow a longer name to be used. The Sun studio compiler accepts it, just not the precompiler. Searched the docs and found nothing about overriding things like this.
If necessary, yes I can shorten the variable names. I'm just trying to minimize the amount of code changes required.
Jim

Answer 1

You are correct.
5 lines below the QUERY DATA SOURCE NAME block property line
is the ‘where clause’ line
It already had FAC_ID = :FACILITIES.ID
I found that if I added my :Blk_name.Pass_cd_num
I could see it my new bind variable in a system.last_query display.
I found the QUERY DATA SOURCE NAME below the ‘from query clause’ truely
is the from clause and it will not except any :Blk_name.item_name
(Because is is just for tables)
But the ‘where clause’ property line will except bind_variables
:Blk_name.item_name is successful in the where clause.
(where Capturing_devices table being the block’s base table)
-- **FROM**
SET_BLOCK_PROPERTY('EMISSION_POINTS',QUERY_DATA_SOURCE_NAME,
'EMISSION_POINTS A,
EP_MODES B,
CAPTURING_DEVICES,
CONTROL_DEVICES CD');
-- **WHERE**
SET_BLOCK_PROPERTY('EMISSION_POINTS', DEFAULT_WHERE,
'A.ID = B.EP_ID AND
B.ID = CAPTURING_DEVICES.PARENT_MODE_ID AND F
CAPTURING_DEVICES.CD_ID = CD.ID AND
CAPTURING_DEVICES.CD_ID IS NOT NULL AND
CAPTURING_DEVICES.PARENT_MODE_ID IS NOT NULL AND
CAPTURING_DEVICES.STACK_ID IS NULL and
B.FAC_ID = :FACILITIES.ID and CD.NUM = :emission_points.cd_id_num');
--**ORDER BY**
SET_BLOCK_PROPERTY('EMISSION_POINTS',ORDER_BY,
'(A.NUM, C.PARENT_MODE_ID, C.CD_ID)');
EXECUTE_QUERY;
I still get a FRM-40505: Oracle error: ‘unable to perform query’
(I know its because of the way it is coded),
But I did learn bind variables can work in the where clause.
Also I tried using the hidden field like you suggested.
If you put char character field in a where clause it will come out in quotes
So I assigned it to a block.hidden_item (number) like you suggested
that did strip off the quotes.
That left me with passing the value of 31, I need to pass 0031
I tried to do a LPAD to the value left pad it with zeroes
But that did not work.
I went back to my effort in using a cursor loop to populate the block
Thanks