I've had reports from people hitting the maximum command line length
when running smurf commands. The maximum length is currently 444
characters, which is not enough if you need to reference, say, 8 files
on the command line all with very long paths. One solution is to
change the application parameters to get all file names using one
parameter (e.g. through indirection), but it would probably be better
to lift the 444 limit if possible.
The 444 value is defined in pcs/messys/MESSYS_PAR:
*
* The maximum length of a message value (see also DDMSG) should be
* used in preference to MSG_VAL_LEN now.
*
INTEGER MESSYS__VAL_LEN ! maximum size of a message 'value'
PARAMETER ( MESSYS__VAL_LEN = 444 )
and used to define the maximum command line length in pcs/dtask/dts_dcltask.f:
* Local Variables:
CHARACTER VALUE*(MESSYS__VAL_LEN) ! command-line parameter string
The same constant (MESSYS__VAL_LEN) is used all over the place in PCS.
Does anyone have thoughts on the safety or otherwise of simply raising
the value of MESSYS__VAL_LEN to - say - 2000 ? Or is it just a case
of trawling through all its usages and considering each one?
David
|