FLMLNK parameter conventions

Note: If you are using FLMLNK, you must pad each parameter to the maximum length. To do so, you must insert blank spaces so that each parameter takes up exactly the maximum amount of space allotted for it.

Programs in the FLMLNK subroutine interface use the following conventions:

The service_name parameter is positional and required. All other parameters must appear in the order described for each service. Parameter positions on the CALL statement must specify a value up to the last parameter coded. Some services allow for CALLs where the parameter list ends before the last one in the service description, thus taking the default specification for those parameters (see individual service descriptions for details).
SCLM uses the maximum parameter length when referencing and updating parameter values. Parameter values with fewer characters than the maximum must be padded with blanks for the remainder of the field. Parameters that are not padded with blanks cause unpredictable results. Be sure that all padding is done by inserting trailing blanks. Padding a parameter with leading blanks causes an incorrect value to be passed to the service.
To omit a parameter, insert a blank enclosed in single quotes (' ') in its place.
Note: Single quotes show service names and keywords in call invocation examples.
You must indicate the last parameter in the calling sequence with a '1' as the high-order bit in the last entry of the address list. PL/I, COBOL, Pascal, and FORTRAN call statements automatically generate this high-order bit. In assembler call statements, you must use the VL keyword.