Re: API parameter lengths

Here's a case where the command line fails to pad blanks to 32 bytes.  I
call the QSYRGFN API on V4R4 like this from the command line to register a
30-character function named XYZ:

CALL QSYRGFN PARM('XYZ'
X'00000002000000100000000100000001F3404040000000100000000200000001F1404040'
X'00000000')

This creates a function named 'XYZ' + X'00' + 26 blanks.  Huh?  Why did the
command line insert a trailing null after 'Z'?  Is this a feature?  Now I
call the QSYRGFN API like this from the command line and explicitly pad the
first parameter to 32 blanks:

CALL QSYRGFN PARM('XYZ                             '
X'00000002000000100000000100000001F3404040000000100000000200000001F1404040'
X'00000000')

This creates a function named 'XYZ' + 27 blanks, as I expected.  Somehow
the QSYRGFN API can determine whether the command line caller typed a
3-character string or a 32-character string in parameter one.  Can an MI
program determine this information, too?

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---