Tidal Enterprise Scheduler: opcmsg did not finish sucessfully OpC30-902

Available Languages

Download Options

  • PDF     (5.3 KB)
    View with Adobe Reader on a variety of devices
Updated:June 6, 2012
Document ID:113410

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

The opcmsg did not finish sucessfully OpC30-902. Option completed is not valid.

Prerequisites

Requirements

Cisco recommends that you have Scheduler version 5.3.1.261 or later.

Components Used

The information in this document is based on Scheduler version 5.3.1.261 or later.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

Messages sent by Scheduler to OpenView do not appear on the console.

Reason

The opcmsg command's application name argument requires quotes around the message.

Resolution

Use the sysval 111 option in the Admiral database to indicate whether the application name in the openview msg should have quotes ("Y") or not ("N"). The default is "N".

Additionally, sysval 107 can be used to indicate if quotes are needed around the msg_txt argument.

Related Information

Revision History

Revision Publish Date Comments
1.0
06-Jun-2012
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco