Use this command to add messages to the time-initiated message
table. You can add a command, a message to start an application, a text
message to send to a functional support console (FSC), or any other meaningful
message.
Messages can be time-initiated or stage-initiated.
Time-initiated messages are issued at a specific time during the
day. Stage-initiated messages are issued when the TPF system
reaches a specific stage; for example, at the end of restart.
Requirements and Restrictions
You can add a time-initiated message to the table only when the TPF system
is above 1052 state because clocks must be running. You can add
stage-initiated messages at any time.
Format
- FReq
- is one of the following options that indicates the frequency with which
the message is issued.
- AT
- issues the message at the specified time.
- IN
- issues the message in the specified number of minutes.
- EVERY
- issues the message at a repeating time interval, which is specified in
minutes.
- DAILY
- issues the message each day at the specified time.
- TIme
- specifies the time or time interval to issue the message.
- time
- is the time or time interval. For the AT or DAILY option, specify
the time in the hhmm format, where hh is hours and
mm is minutes. For the IN or EVERY option, specify the time
interval in the mm format.
- 1052S
- issues the message at the beginning of restart. You can specify
this option only for the AT or EVERY option.
- 1052E
- issues the message at the end of restart. You can specify this
option only for the AT or EVERY option.
- CYCLU
- issues the message after the TPF system is cycled from a lower state to a
higher state; for example, from 1052 state to MESW state. You can
specify this option only for the AT or EVERY option.
- CYCLD
- issues the message after the TPF system is cycled from a higher state to a
lower state; for example, from NORM state to 1052 state. You can
specify this option only for the AT or EVERY option.
- NORM
- issues the message when the TPF system reaches NORM state. You can
specify this option only for the AT or EVERY option.
- MSg=text
- is the message to be issued, where text is 1-72
characters.
If you enclose the text in single quotations ('), the text can contain
all characters except single quotations. If you do not enclose the text
in single quotations, the text cannot contain commas (,) and plus signs
(+).
Attention: The message that you specify is not
verified. Therefore, the results cannot be predicted if the message
text is not correct.
- FSC
- sends the message to one of the following functional support consoles
(FSCs):
- number
- is a decimal number from 1-16 that represents the FSC.
- AUDT
- sends the message to the AUDT FSC.
- COMM
- sends the message to the COMM FSC.
- DASD
- sends the message to the DASD FSC.
- PRC
- sends the message to the PRC FSC.
- RDBS
- sends the message to the real-time database services (RDBS) FSC, which is
used by the TPF Application Requester (TPFAR) feature.
- RO
- sends the message to the RO FSC.
- TAPE
- sends the message to the TAPE FSC.
- APL=name
- sends the message to the specified application, where name is the
4-character alphanumeric name of the application. The first character
must be alphabetic.
- Note:
- You must ensure that the application name is valid and that the specified
application can process the message at the specified time.
- PAST
- specifies whether or not to process time-initiated messages that are past
due. If you specify PAST=N, the message that is past due is discarded
if it cannot be processed within 1 minute after it is issued.
A past-due time-initiated message is a message that was not
issued at the specified time. For example, if the processor was offline
when the time-initiated message was to be issued, that message is
past-due.
Additional Information
- The order of issuing the time-initiated messages may change depending on
the time it takes to enter them into the time-initiated message table, the
activation time, and the processing time. Therefore, the messages may
not be issued in the intended sequence. Stage-initiated messages are
issued in the order that they are entered in the table.
- This function does not verify the message content in any way.
Therefore, it is your responsibility to ensure that the resources required by
the message are available and that the syntax of the message is
correct.
- If you specify the AT option or the IN option for the FREQ parameter, the
message is deleted from the time-initiated message table after it is issued,
or if it is past-due and you do not process it (PAST=N). If you specify
the EVERY option or the DAILY option, the message remains in the
time-initiated message table until you delete it using the ZSTIM C
command.
- Message routing is determined by the following criteria:
- If the routing is specified by FSC, it is not necessary to do any further
destination determination.
- If the message starts with a 'Z' it is assumed to be a
command:
- If the routing is specified by APL=SMPx, the message is edited for basic
format.
- If the routing is not specified, the message is edited for basic format
and sent to SMP in this processor.
- If the routing is specified but is not SMPx, the message is forwarded to
the application. It is not edited for basic format.
- If the message does not start with a 'Z' it may be a prefixed
command:
- If the routing is specified by APL=SMPx, the message is assumed to be
prefixed and is edited for basic format.
- Otherwise
- If the routing is specified by APL, it is forwarded to the indicated
application.
- If the routing is not specified, it is forwarded to the RES0
application.
Examples
In the following example, a message is added to the time-initiated message
table to display system status every 5 minutes.
+--------------------------------------------------------------------------------+
|User: ZSTIM A FREQ=EVERY,TIME=05,MSG=ZSTAT |
| |
|System: STMA0001I 08.39.13 MSG ADDED TO TIM TBL |
+--------------------------------------------------------------------------------+
In the following example, a message is added to the time-initiated message
table to display tape status every day at 3 p.m.
+--------------------------------------------------------------------------------+
|User: ZSTIM A FREQ=DAILY,TIME=1500,MSG=ZDTAP |
| |
|System: STMA0001I 08.39.13 MSG ADDED TO TIM TBL |
+--------------------------------------------------------------------------------+
In the following example, a message is added to the time-initiated message
table to change the system error options at the end of each restart.
+--------------------------------------------------------------------------------+
|User: ZSTIM A FREQ=EVERY,TIME=1052E,MSG='ZASER HALT,DUPL,ALL BLKS' |
| |
|System: STMA0001I 08.39.13 MSG ADDED TO TIM TBL |
+--------------------------------------------------------------------------------+
In the following example, a message is added to the time-initiated message
table to display system status in 30 minutes. The ZSTAT command is
discarded if it cannot be processed within 1 minute after it is issued.
+--------------------------------------------------------------------------------+
|User: ZSTIM A FREQ=IN,TIME=30,PAST=N,MSG=ZSTAT |
| |
|System: STMA0001I 08.39.13 MSG ADDED TO TIM TBL |
+--------------------------------------------------------------------------------+
In the following example, a message is added to the time-initiated message
table to display a file record on a specific subsystem user.
+--------------------------------------------------------------------------------+
|User: ZSTIM A FREQ=IN,TIME=1,APL=SMPB, MSG='SSU/ZDFIL 07F40001 |
| |
|System: STMA0001I 08.39.13 MSG ADDED TO TIM TBL |
+--------------------------------------------------------------------------------+
Related Information
None.