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.

Sign up for GitHub

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

Added Message Management for Message Guidance #75

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e36adf0
Added Message Management for Message Guidance
hogstrom Jan 16, 2019
634c527
Corrected ZPI -> API type
hogstrom Jan 30, 2019
157db18
Merge branch 'master' into messageManagement
armstro Jan 30, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions process/messageManagement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Message Management

### Message ID Components (message prefixes)
OMP
ZWE

### Zowe Components
A - API Mediation Layer
C - Zowe CLI
D - Zowe Desktop
E - Zowe Explorer
S - Zowe System Services

### Message Formats
ZWEcnnnnt where:

**ZWE** - static for Zowe messages.

**c** - one of the registered Components ... (see above). Components need the ZLC to approve the use of the component to ensure consistency across all of the projects.

**nnnn** - is a linear sequence starting from 0001 to 9999. Projects may choose to use the first digit to divide the number space. **

**t** - is a Type. One of (I, E, A, W) General conventions by IBM are **I**nform, **E**ventual Action (often construed as error), **A**ction, **W**arning or **S**evere error

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