Wrong SD Job order execution

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

A SD procedure Group contains installation of 3 packages : PKG 1.0, PKG 2.0, PKG 3.0

It is sent to a computer. Job Linkage option is set to "No linkage" :

and Job Options "Store packages in the Scalability Server's Staging Library" is checked.

Expected behavior is that installation follows the procedure group order : PKG 1.0, PKG 2.0 and PKG 3.0

But in example below, PKG 2.0 is installed before PKG 1.0. Procedure group order is not respected.

Environment

Client Automation - All Versions

Cause

This problem could occur if the packages must be staged to the scalability server.
Once a package is staged in the Scalability Server library, the SD job is sent to the target agent.
In above example, PKG 1.0 and PKG 3.0 are bigger than PKG 2.0.
Stage of PKG 2.0 is completed first. It is why it is executed first by the Agent.

Resolution

Following parameter :
itrm/usd/manager/waitforsstransferok
could be use to change the behavior.

By default it is set to 0. Meaning that once a package is staged to the Scalability Server Library, the SD Job is sent to the target Agent.
If this parameter is set to 1, TaskMan waits that all packages are staged to the scalabiltiy Server before sending the SD Jobs to the target Agent.

1. Execute following command on the Domain Manager to check the current value
   ccnfcmda -cmd Getparametervalue -ps itrm/usd/manager -pn waitforsstransferok
   
   
   
   
2. If it is 0 and job execution order must be respected, then set it to 1 with following command :
   ccnfcmda -cmd Setparametervalue -ps itrm/usd/manager -pn waitforsstransferok -v 1