Execute Container--Executes an Software Delivery Job Container Order File
This command executes a Software Delivery job container order file.
cla140
This command executes a Software Delivery job container order file.
Syntax
ExecuteContainer ContainerFile [-o:results directory] [-p:password] [-t]
- ContainerFileFull path to the container order file.
- [-o:results directory]Full path to the results directory (optional).
- [-p:password]Password (optional).
- [-t]Time in seconds.
During execution, the container order file is copied to the file
name
.cwf in the internal directory sdjexec (“.\CA\DSM\Agent\units\00000001\usd\sdjexec”).
When the container execution is completed, the file is renamed to
name
.crf and written to the given results directory, if available, else the file is placed in the sdjexec directory).If the $rf macro is used in the procedure parameters, the output log file is given a unique name with an extension of “res” and copied to the supplied results directory.
Empty result files are not stored on the computer.
To run the container file, the data must be secured with sd_acmd SecureContainer
.
In a Windows NT/2000 environment, to execute a Software Delivery offline job using sd_acmd ExecuteContainer, sufficient security privileges are needed. By default, only users assigned domain or global administrative rights are authorized to run the Software Delivery offline jobs. Optionally, users who are members of the Windows NT/2000 local group SDOFFLIN or global group Domain SDOFFLIN are authorized to run Software Delivery offline jobs. The local group SDOFFLIN is created on all Windows NT/2000 computers when installing Software Delivery. Administrators can create the global group Domain SDOFFLIN and add users to these groups to let users run the Software Delivery offline jobs.
In UNIX, the NIS (Network Information Service) performs similarly to domain user validation in NT. The SD NIS user group for offline jobs is also called SDOFFLIN.
Examples:
The following example illustrates how to order an execution of a job container order file.
sd_acmd executecontainer "C:\myorders\test1\order1.cof" -o:"C:\myresults" -p:mypassword
The Output Directory argument can also be added to the container order file (parameter ResultDirectory in section Container). The command-line option overrides the value in the container order file.
As a password is used to secure the container order file in the example following (SecureContainer), the (same) password parameter must also be specified when running the ExecuteContainer command. The container order file executor internally decrypts any sensitive data before use.
-t parameter:
When the agent is busy executing a job or contacting the server, the offline job executor is unable to run. The -t: parameter instructs the offline job executor to wait for a specified number of seconds before giving up and returning an error code signifying that the agent is busy. A default timeout is used if none is specified.
sd_acmd executecontainer cont.cof -t:30
This instructs the offline job executor to wait up to 30 seconds for the agent to terminate before failing.