Ability to Add New Application Level User Field to Existing AD in Workload Scheduler

Description:
Currently, when using the ADUSF option, IBM Workload Scheduler creates a new Application Description (AD) with the same name instead of adding the User Field to the existing AD. Additionally, ADUSF requires attaching the user field to an operation, not at the application definition (AD) level.

Requested Enhancements:

1. Add User Field to Existing AD:
   Allow ADUSF to add a user field to an existing Application Description without creating a duplicate AD.
2. Enforcement Parameter:
   Provide a system-level parameter (e.g., ENFORCE_ADUSF_ON_UPDATE=YES) that requires adding/validating ADUSF whenever an AD is updated (create/modify), with failure if the field is missing.
3. Application-Level User Fields:
   Support user fields at the AD level (not only operation level), so metadata can be stored once per application rather than redundantly on individual operations.

Use Case:
This capability would enable users to include additional metadata—such as Change Request numbers—when updating an AD. This improves audit traceability and supports compliance requirements.

Technical Benefit:

• Prevents unnecessary duplication of ADs
• Maintains integrity of existing AD definitions
• Enhances flexibility for adding contextual information
• Enforces consistent metadata for audit and compliance

Justification:
The current behavior forces duplication and manual cleanup, which increases operational overhead and risk of inconsistencies. Allowing updates to existing ADs and enforcing ADUSF through a system parameter would streamline workflows, reduce errors, and improve compliance by enabling accurate audit trails without impacting scheduling logic.