SMGAV2 : Move Task when requesting is not initiating automatically.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

When moving a task from system A to system using the move (MO) command caused the value of the column SSM#DESSYS to be updated but the actual move never occurs.

The task does not exist on the system B resource table. 

Environment

OPS/MVS

Cause

The value of the column SSM#DESSYS was not correct. 

The value should be '80000000' but it was '00000000'

Resolution

To correct this problem the resource table must be deleted from SSM control in OPSVIEW 4.11.1 and readded.