The two ‘excel’-files of this check
(check_vmtel_contacts _[n]ok.TXT) have got the
structure:
|
column
|
remark
|
|
VMTEL
ID
|
reference id for the
contact name
|
|
VMTEL
Name
|
contact name in
vmtel.txt (last name + space + first name)
|
|
Service Desk
Name
|
contact name the new database (last name + space +
first name)
|
|
state
|
result of the
check
|
Depending on the value of ‘state’ the
contact name is listed in either the ‘_ok’ or the
‘_nok’ file.
-
state of the ‘_ok’ file and
actions to be done
In this file the
state-column has got two values:
duplicate entries in vmtel.txt
In the output file ‘check_names.txt’
all duplicate entries in vmtel.txt are listed. For these entries a
correct check can not be taken. Every ‘not ok’ entry
must be checked if there is a duplicate entry in vmtel until the
file vmtel.txt is correct.
state ‘ok’
The name in the new database is correct, no action
to be taken.
state
‘inactive,ignored’
The name in the new database is marked as
inactive. There is no action to be taken here, since these entries
are listed in the not ok file of ‘Explanation of check
‘check_service_desk_contacts
(3)’.
-
state of the ‘_nok’ file and
actions to be done
In this file the
state-column has got three values:
-
names are
different
-
new name
missing
-
phone
values are different
-
some
values are different ([C|D|E])
state ‘names are
different’
The names are different, due to duplicate entries
in the vmtel.txt file, or entries in the Service Desk with
accents (like PLAHÉ) or changed entries in vmtel (after
the 10. Aug. 2003). After vmtel and the accent-entry are corrected
only the changes in vmtel will be listed and the changed entries
can be altered manually. The file
“check_vmtel_contacts_upd.ca” contains the list of
names which can be updated. This list is not useful unless all
duplicate entries are deleted.
state ‘new name
missing’
The names are missing in the database. The process
of updating vmtel on the server lofty must be checked and run
manually. All new entries are only generated on the server lofty.
(The file ‘check_vmtel_contacts_new.ca’ contains a
Unicenter input for this, but the process on the server lofty
should be used.)
state ‘phone values are
different’
The name is correct, but the phone number has
changed. The entry has to be checked and altered
manually.
state ‘some values are different
([C|D|E])’
The name and the phone number are correct but
another value (E=c_contact_num, D=c_dept, E=c_expense {names of the
ctct field in Service Desk}) differs. The entry has to be checked
and altered manually. These differences are due to changes in
vmtel.
1. Hardware Requirements
