How can I know when a copy completes unsuccessfully?

To trigger a rule when a file transfer completes unsuccessfully, you must specify the Event Type and Return Code parameter keys.

About this task

File transfers are accomplished via what IBM Control Center interprets as Process Steps. For purposes, this category even includes transfers with Sterling B2B Integrator servers that do not include a business process. For a rule to trigger when a Process Step completes in error on a managed server (whether a Sterling B2B Integrator business process activity, a Sterling Connect:Direct Process step, or, for example, a batch added by a remote user to a Sterling Connect:Enterprise mailbox), you must specify two parameter keys: an event type of Process Step Ended and a Return Code with an Operator of Not Equal To and a Value of 0. No other rule attributes must be set. However, you can further limit the times this rule would fire by setting additional values such as a particular server or a schedule.

For example, to know when the activity called WaitService in business process ISITDONE completes in error on Sterling B2B Integrator-managed server phoenix-gis 43, specify the following parameters when you create the rule:
Key Operator Value
Process Name Matches ISITDONE
Step Name Matches WaitService
Event Type Matches Process Step Ended
Server Id Matches phoenix-gis 43
Return Code Not equal to 0