MKS Implementer 2006 Administration Guide

Typically, these source files are:
QCBLSRC (unmodified current release)
TCBLSRC (PTFs to current release)
UCBLSRC (customer changes to current release)
AOS Message Manager Integration
In addition, the environment library list must match the library list of the ASICOMPILE job
description, with the libraries listed in the same order.
Troubleshooting Problems
The following information may be helpful with resolving typical problems related to
message files.
Problem Resolution
Source mismatch Change the Source member type to TXT.
Checked out QSRC instead of USRC The default source file must be USRCxxx.
TSRC and USRC not copied Special characteristics not entered for object type.
AOS Message Manager Integration
AOS Message Manager interfaces with Implementer to allow you to monitor the status of
promotion requests. The messages can be set up to automatically create an OS/400 message
to one or more user profiles. In addition, you can send Implementer messages directly to a
pager to notify someone not signed on to the iSeries that a situation requires attention.
To set up the AOS Message Manager integration
1 From the Implementer Menu, select option 45, System Control Maintenance. The System
Control Maintenance panel displays.
2 Press PAGE UP to display the second panel.
3 In the Secondary message queue field, type the name of the AOS Message Manager
message queue. This points AOS Message Manager to the message queue where all
messages in Implementer are sent, and to the appropriate Implementer users.
You can also page a user when specific messages are received. For more information, see
the AOS Pager Manager Users Guide.
315