During CA Dispatch startup we're receiving DC980224 Invalid Class Value errors

book

Article ID: 223649

calendar_today

Updated On:

Products

CA Dispatch Output Mgmt

Issue/Introduction

When CA Dispatch comes up we are receiving the following errors: 

DC980224 V1 RPI2 Invalid Class Value, Please Update Sysgen for this RPI
DC970014 V1 Invalid LDS Token
DC980219 V1 RPI2 Foreground Task Has Ended Due To Error
DC980224 V1 RPI3 Invalid Class Value, Please Update Sysgen for this RPI
DC970014 V1 Invalid LDS Token
DC980219 V1 RPI3 Foreground Task Has Ended Due To Error

Cause

CA Dispatch RPI2 and RPI3 tasks have not been configured correctly on the VSGMU105 - Dedicated Sysout Control Information Screen 

Environment

Release : 11.7

Component : CA Dispatch

Resolution

These messages indicate to me that CA Dispatch is attempting to start the RPI2 and RPI3 subtasks (Based on the commands you have coded in the START=DSSTARnn member), but you have not yet configured the RPI2 and RPI3 subtasks of CA Dispatch on the VSGMU105 screen (option 9.0 from main menu) with the necessary CLASS/DEST processing criteria.

- If you are going to run/use the RPI2 and RPI3 subtasks of CA Dispatch you must configure them on the VSGMU105 screen with valid processing criteria before starting them.

NOTE - You CAN NOT have all three RPI tasks processing the SAME CLASS/DEST criteria. So the CLASS/DEST criteria that you define for RPI2 and RPI3 need to match what was configured for the CADZSPLn environment that will be servicing this Dispatch.

- If you are NOT going to run the RPI2 and RPI3 tasks with this Dispatch, then you will want to edit the START=DSSTARnn member this Dispatch uses and REMOVE the start commands for RPI2 and RPI3.