Why do you want the parameter to be null ?
Wondering the same thing... What difference does it make if you set it to "" ?
Ok. Good point. The person who wrote their script expect 38 params (don't ask why, I don't know)
So I am expected to pass null or a valid value to that field. If I pass "" in the 36th parameter as explained above, then it goes in as empty to the NSHScript and then the 36th parameter is equivalent to being absent or aka the 37th parameter will be read as 36th
<script name> ....... <36th param> <37th param> <38th param>
In the above if 36th param is empty the 37 becomes the 36th param.
Hence I need to pass some value like either a null or a valid value.
Also curiously asking, is null string an invalid value to set ? like is it a keyword or something
I see. If the script is not using getopts to get arguments then he's expecting a set number in a set order. The only way to paliate that is to put a placeholder value (i.e. a x character, or a keyword), and to then strip it from the value in the script when assigning the arguments to variables.
This is the only way unfortunately. I think someone else requested that you can explicitly pass empty strings that would be translated into "" when calling the script on the app server, so the argument count would be kept (which is the default behavior in bash and other shells). In the meantime my solution is the only one (placeholder value stripped in the code, or getopts with argument flags).
There’s a fix in 8.5 for this iirc (the blank parameter messing up the order). Also instead of ‘null’ (which blade seems to be interpreting as a null and not literal null) use ‘NA’ or ‘NONE’ and change the script to handle that.