Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Message Management for Message Guidance #75

Merged
merged 3 commits into from
Jan 30, 2019
Merged

Conversation

hogstrom
Copy link
Contributor

Signed-off-by: Matt Hogstrom matt@hogstrom.org

Signed-off-by: Matt Hogstrom <matt@hogstrom.org>
Copy link
Member

@nannanli nannanli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please consider the following edits:

Message Management

A message is any communication that is passed from the application to a user or to another application, including error messages, return codes, and reason codes. A message typically suggests an action, indicates a condition, or informs that an event has occurred. This document describes the message ID, message format and guidelines for Zowe.

Message format

All messages must have the following information:

  • Message ID
    Specifies a unique alphanumeric identifier that provides a quick means to distinguish one message from others.
  • Message text
    Briefly describes the problem.

Message ID

A message identifier (message ID) is a unique group of alphanumeric characters that identifies a message. The message ID typically has these parts:

  • Registered project identifier
  • The product component (optional)
  • Message number
  • Message type

In Zowe, message ID uses the following format:
ZWEcnnnnt

Where,

  • ZWE
    Specifies the registered project identifier. Zowe messages use the static identifier ZWE.
  • c
    A variable that specifies one of the following registered Zowe components. Components need the ZLC to approve the use of the component to ensure consistency across all of the projects.
    • A - API Mediation Layer
    • C - Zowe CLI
    • D - Zowe Desktop
    • E - Zowe Explorer
    • S - Zowe System Services
  • nnnn
    A variable that specifies the message number which ranges from 0001 to 9999. Projects may choose to use the first digit to divide the number space.
  • t
    A variable that specifies the message type. It can be one of the following values:
    • I - Informational
    • E - Eventful action or Error
    • A - Action
    • W - Warning
    • S - Severe error

Messages should be sent to the Zowe doc team and follow the general IBM format as described in Messages and Codes.

Examples

  • ZWEA002I API Mediation Layer initialization complete
  • ZWED002E Cannot load plug-in a plugin that should have been loaded

@fbeyl
Copy link

fbeyl commented Jan 30, 2019

Maybe add job and syslog to the text.
A message is any communication that is passed from the application to a user, to another application, to the joblog or to the syslog including error messages, return codes, and reason codes.

Signed-off-by: Matt Hogstrom <matt@hogstrom.org>
@ghost ghost removed the in progress label Jan 30, 2019
@ghost ghost assigned armstro Jan 30, 2019
@ghost ghost added the in progress label Jan 30, 2019
@hogstrom hogstrom merged commit 2f1ef1d into master Jan 30, 2019
@ghost ghost removed the in progress label Jan 30, 2019
@hogstrom hogstrom deleted the messageManagement branch January 30, 2019 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants