Changes to Existing Features - 11.3.6

This article details the changes to existing features in CA Workload Automation AE Release 11.3.6.
wcc114sp5p
This article details the changes to existing features in CA Workload Automation AE Release 11.3.6.
Authenticating Command-Line Utilities with External Security
The addition of the -usr command-line option enables you to authenticate certain command-line utilities with external security. Using this option improves security by ensuring that the utility runs as an authenticated external security user.
The authentication of the external security user is successful only when the user password is accurately specified using the -pw or -pwx parameter. When the authentication fails, the utility does not run and exits with an error.
Following the authentication, the external security system assigns a security policy identity to the utility. The security policy determines which protected CA Workload Automation AE objects are accessible based on the assigned identity and grants the utility access to those objects.
  • This option is required when the CA Workload Automation AE instance is configured to run in external security mode and the unauthenticated user mode is set to STRICT; otherwise, it is optional.
  • The utility ignores this option when the CA Workload Automation AE instance is operating in native security mode.
  • For more information about which utilities support this option and how to use it, see AE Commands.
Cross-platform Job Requests
When the scheduler receives the cross-platform start job requests, it now requests the application server to authenticate and authorize that request. For the job to execute successfully, you must have EXECUTE access for the following resource classes:
  • as-appl
  • as-group
  • as-machine
  • as-job
FORCE_STARTJOB (108)
In the current release, you can force start a job in FAILURE or TERMINATED status that has a virtual resource dependency with free=Y or free=N and has not released the virtual resources. The FORCE_STARTJOB event verifies if the current status of the job is FAILURE or TERMINATED and schedules the job using the already held virtual resources.
Before force starting the job, the scheduler does not reevaluate other resource dependencies.
STARTJOB (107)
In the current release, you cannot issue the STARTJOB event to start a job that has a virtual resource dependency with free=Y or free=N and has already held the resource.
To start such a job, take 
one
 of the following actions:
  • Manually release the held resource by issuing the RELEASE_RESOURCE event.
  • Force start the job in FAILURE or TERMINATED status by issuing the FORCE_STARTJOB event. The virtual resource is released if the job has the virtual resource dependency with free=Y and completes successfully.
Updating the resources Attribute in an Existing Job Definition
You cannot update the resources attribute in the existing job definition if the job has a resource dependency and has held the resource.
To release the held resource, take 
one
 of the following actions:
  • Manually release the held resource by issuing the RELEASE_RESOURCE event.
  • Force start the job in FAILURE or TERMINATED status by issuing the FORCE_STARTJOB even