![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains a cumulative list of new features introduced in the current fix pack and in the previous fix packs.
The following new features have been introduced in this fix pack.
Modify cancel button on Software Distribution panel | Feature 55522 |
Immediate start of distributions for conditioned endpoints | Feature 56050 |
Stop on failure check box | Feature 56087 |
Cancel as preferred final status for a plan | Feature 56137 |
New 32-bit MRMBIOS.EXE | Feature 180357 |
To enable this feature from the Activity Planner command line, run the wsubpln command in the following way:
wsubpln -r plan_name -Dpre_eval_conditions=true
To enable this feature from the Activity Planner GUI, the Pre-evaluate conditions at plan submission check box has been added to the Plan Submission Parameters panel.
To enable this feature from the Change Manager command line, specify the -e option when running the wsyncrmod command, or select the Pre evaluate conditions at plan submission check box which has been added to the Select activity plan name panel.
To enable this feature, perform one of the following actions:
The following new features have been introduced in previous fix packs.
Specifying the path where a single file is saved on the destination system | APAR IY68180 |
Cancelling an activity plan in Starting state | APAR IY70368 |
Concurrent login feature | Feature 54613 |
Displaying the .jar files version | Feature 55204 |
If you specify the -G option or select the Modify Destination Path check box, the file is saved on the destination system according to the following naming convention: name_endpoint_timestamp_distribution_id.extension. If you do not specify the -G option or select the Modify Destination Path check box, the default behavior applies and the retrieved file is saved with its original name to a directory on the destination system named according to the following convention: endpoint_distribution_id_timestamp.
To solve this problem, the cancel command is now performed while the activity is still being submitted. This operation is performed only when the cancel command is requested for the entire plan, and not when the operation is requested only for a subset of the activities in the plan.
[ Top of Page | Previous Page | Next Page | Contents ]