User`s guide
Page 25
5 MidJet GSM Text functions
This section provides information about the functions in MidJet GSM Text.
For a detailed description how to configure and use the product on your
iSeries, please consult the following chapters.
5.1 Create messages
Messages to be sent out to mobile telephones can be created in different
ways:
You can use the interactive program from the Main menu. Message text
is typed in, and recipient or recipients are selected. Messages can be
sent to individuals or to persons connected to a distribution group. For the
unlimited user’s license types, a message can be addressed using only
the GSM number.
Using the SNDGSMTMSG messages can be created from a command
line or, more likely, from within your application. This is very useful in
case you want to know if an important batch job has reached a normal
end or not. In this case you will include this command in your high-level
program.
The XSBMGTM API can be called to create a message from your high-
level program. This is useful in situations when you want to report send
result or other information about the message to your application. This
API returns the message sequence number, which is the key parameter,
along with the system name, when using the XRTVGT4 to retrieve
information about the message. The version 3 XTRVGT4 API is still
available.
5.2 Monitor system operations
MidJet GSM Text is designed to be a very useful tool helping the iSeries
operator. System malfunctions and unexpected conditions generate a GSM
Text message which will be forwarded to the operator or group on call.
The system operations monitor can be configured to perform the monitoring
functions in a very flexible way. This is implemented using the concept of
checkpoints. Thirteen different types of checkpoints are available and
multiple checkpoints of each type can be created where applicable.
This section describes the characteristics of the different checkpoints.
MSGW checkpoint
The monitor can check for the occurrence of jobs that have status
MSGW. This is similar to using the WRKACTJOB command and looking
in the status column. In this case it is performed using a system API to
reduce system resource consumption. When a job with MSGW status is
found, it is checked against the Job Name filter file including the jobs and
the user ID of the jobs, with normal status MSGW, e g UPS monitor jobs.
Jobs can be filtered out using *ALL as Job name or user ID. This
alternative finds all application program errors which leave jobs in MSGW
status, but not system problems.
MSGQ checkpoint