The Feedback File
Whether the message was sent through the programmable operator or not has little
significance to the user. However, so that the messages received by the user always
have the same id (the programmable operator facility id), the message should
always be sent from the logical operator through the programmable operator facili
ty.
The feedback file is anotherCMS disk file (named FEEDBACK nodeid AS) that
the programmable operator facility manages. The feedback file, unlike the log file,
is not automatically written by the programmable operator facility. Authorized
users can write time stamped notes and complaints about the operation of the sys
tem to this feedback file. To write a notice to the feedback file, you, as a user,
must explicitly use the FEEDBACK (or FB) command. An example of such a
message is
MOP FEEDBACK RESPONSE TIME WAS SLOW DURING MORNING SHIFT.
Because the feedback file is normally smaller than the log file, it is easier for the
personnel in charge of the programmable operator facility's maintenance to review
the users' comments and identify when and where particular problems occurred.
Each record in the feedback file is prefixed with the date and time the message .was
logged along with the sender's userid and nodeid. The feedback file has the follow
ing format:
col 1 col10 col 19 I I I V V V
yy/mm/dd hh:mm:ss userid
col 28I V
nodeid:
col 39I V
text
The feedback file contains variable length records. The maximum record length
that the programmable operator facility can place in the feedback file is 132 char
acters. Because the prefix uses 38 of the 132 characters, the text can be only 94
characters long. Therefore if the text of a message exceeds the maximum length of
94 characters the overflow is continued on the next record. This continued record
has the same prefix as the preceding record, with no colon preceding the text.
Any user authorized in the active routing table can obtain the feedback file as a
spool file by using the the programmable operator facility GET FB or GET
FEEDBACK command.(See the VM / SP Operator's Guide for information on the
programmable operator commands.)
An old feedback file can be purged by any user authorized by the active routing
table to use the programmable operator CMD command by issuing theCMS ERASE command.
Installing the Programmable Operator Facility
TheVM/SP product contains the file PROPLIB LOADLIB which is the basis for
the programmable operator facility. After receiving and installingVM/SP, take the
following steps before running the programmable operator facility.
1. Reserve enough mini-disk space to contain the log file(s) and feedback file for
the virtual machine that the programmable operator facility will be running in.
The amount of space needed depends on the amount of message traffic that
will be going through the programmable operator facility, and on the number
of comments you expect users to place in the log and feedback files.
The Programmable Operator Facility 443
Whether the message was sent through the programmable operator or not has little
significance to the user. However, so that the messages received by the user always
have the same id (the programmable operator facility id), the message should
always be sent from the logical operator through the programmable operator facili
ty.
The feedback file is another
the programmable operator facility manages. The feedback file, unlike the log file,
is not automatically written by the programmable operator facility. Authorized
users can write time stamped notes and complaints about the operation of the sys
tem to this feedback file. To write a notice to the feedback file, you, as a user,
must explicitly use the FEEDBACK (or FB) command. An example of such a
message is
M
Because the feedback file is normally smaller than the log file, it is easier for the
personnel in charge of the programmable operator facility's maintenance to review
the users' comments and identify when and where particular problems occurred.
Each record in the feedback file is prefixed with the date and time the message .was
logged along with the sender's userid and nodeid. The feedback file has the follow
ing format:
col 1 col
yy/mm/dd hh:mm:ss userid
col 28
nodeid:
col 39
text
The feedback file contains variable length records. The maximum record length
that the programmable operator facility can place in the feedback file is 132 char
acters. Because the prefix uses 38 of the 132 characters, the text can be only 94
characters long. Therefore if the text of a message exceeds the maximum length of
94 characters the overflow is continued on the next record. This continued record
has the same prefix as the preceding record, with no colon preceding the text.
Any user authorized in the active routing table can obtain the feedback file as a
spool file by using the the programmable operator facility GET FB or GET
FEEDBACK command.
programmable operator commands.)
An old feedback file can be purged by any user authorized by the active routing
table to use the programmable operator CMD command by issuing the
Installing the Programmable Operator Facility
The
the programmable operator facility. After receiving and installing
following steps before running the programmable operator facility.
1. Reserve enough mini-disk space to contain the log file(s) and feedback file for
the virtual machine that the programmable operator facility will be running in.
The amount of space needed depends on the amount of message traffic that
will be going through the programmable operator facility, and on the number
of comments you expect users to place in the log and feedback files.
The Programmable Operator Facility 443