When creating a Run Control ID, is it acceptable to include blank spaces?

• A. True
• B. False
• C. Only spaces at the end
• D. It depends on the system configuration

Answer: (B)

Run Control IDs act as the stable key for a saved set of run-time parameters, so they need to be a single, contiguous token without spaces. Spaces can cause parsing and retrieval problems—commands, scripts, URLs, and logs often treat spaces as delimiters or trim them, leading to mismatches or failed runs. For reliable operation, use alphanumeric characters (and, if allowed, underscores or similar separators) with no spaces. If you try to include spaces, validation typically rejects the ID or it behaves inconsistently, so it’s not acceptable.