FAQs
This page contains answers to common questions handled by our support staff,
along with some tips and tricks that we have found useful and presented here as questions.
Note: In these answers we will follow a few shorthand conventions for describing user-interface procedures. Key combinations will be presented like this: Ctrl+Alt+Delete, which means that you should press and hold down the Control key, the Alt key, and the Delete key at the same time. Menu selections will be presented like this: File->Open, which means that you should open the File menu, and then make the Open selection.
My software is
in a countdown. What do I do?
There is a
agent who is unable to log into TELEMATION.
Message at the bottom of screen reads "TMR ID IN USE"
How
do I associate a DSC product user with the UNIX tty id?
How can
I set up a default dbase that is used when invoking DSC products?
What are the DSC master file record
prefixes?
Verifying a file using FPADMIN reports that there
are count mismatches. Should I be
concerned?
The first time Database Systems software is
installed on a system, a security countdown of 5 days will begin.
System recovery processes and system upgrades may cause the
countdown to begin once again.
If this happens, the following Security Procedure will take care of the problem.
The most common reason for
this error message is the TMR has logged out of the system incorrectly. This can happen
several ways. The most common methods are: TMR has "X-ed" or closes down
the current window from a terminal emulation session such as Reflections or Host On
Demand, or the System "Freezes" or goes down.
To correct this, contact a Systems Administrator and have them
execute a tm_init -admin and initialize memory for TMR buckets. You can also set a
Flag in the TMR Profile setup to allow for a TMR to be able to login multiple times.
The utility "ds_ttyname" can be used to display
the DSC user id along with the UNIX tty device id. The utility
"ds_ttyname -a" can be used on most UNIX systems to also display the current
process id with the DSC user number and UNIX tty device id.
At Revision 10 of DSC products there is a file called
"dbase_deflt" in /dbase. This file contains the pathname of the default
dbase to use when the "-db" product directive is not used when executing a user
application or DSC product.
At Revision 11 of DSC products the directory where "dbase_deflt" is
located is "/dbase11".
The other method of establishing a default dbase is to
define an environment variable called DBASE_DEFLT that specifies the default pathname
desired.
sh:
DBASE_DEFLT=/thepath/to/dbase
export DBASE_DEFLT
csh: setenv
DBASE_DEFLT /thepath/to/dbase
Back to Top
pde.master file prefixes
| $$ |
Screen Header Record |
| $$$$ |
Installation Control Record |
| PGM. |
Eztran header record |
| scn-name |
Screen Detail Record |
trn.master file
prefixes
| F$ |
File Definition - Header |
| F. |
File Definition - Field |
| L$ |
Link Definition |
| M$ |
Menu Definition |
| M. |
Menu Definition - Response |
| M1 |
Menu Definition - Multiple Records |
| O$ |
Run Module User |
| T$ |
User Record |
| A. |
Audit Control Record |
| J$ |
Legend Control - Header |
| J. |
Legend Control - Response |
pde.format file
prefixes
| ## |
Output Format - Header |
| #. |
Output Format - Field Definition |
rpt.master file
prefixes
| B$ |
Labels - Field Labels |
| T$ |
Labels - File Description |
| R$ |
Report Definition - Header |
| S$ |
Report Definition - Section Header |
| F$ |
Report Definition - Section Fields |
| L$ |
Report Definition - Sorts / Searches |
| O$ |
Report Definition - Output Media |
| P$ |
Transport Definition - Header |
| P. |
Transport Definition - Detail |
| U$ |
Transwriter User Record |
| VU |
Tranview User Record |
run.master file
prefixes
| $$$$ |
Installation Control Record |
| D$ |
File Definition |
| J$ |
Legend Definition |
| M$ |
Menu Definition |
| O$ |
Run Module User Record |
| PGM |
EasyTran Program |
| SCN. |
Screen Definition |
tlm.master file
prefixes
A$ |
A0KEY |
Telephone
Site Maintenance |
STCTRL |
B$ |
B0KEY |
Label
Maintenance |
LABELS |
C$ |
C0KEY |
Campaign
Maintenance |
CAMPGN |
D$ |
D0KEY |
Display
Utility |
DISPLY |
E$ |
E0KEY |
Report
Search Criteria |
STARCH |
G$ |
G0KEY |
Literature
Pieces |
PIECES |
H$ |
H0KEY |
History
Maintenance |
HISTRY |
K$ |
K0KEY |
Internal
Counter Records |
DOCNUM |
L$ |
L0KEY |
Cover
Letters |
COVER |
M$ |
M0KEY |
Message
Records |
MESSAG |
N$ |
N0KEY |
Follow
up Cycle Codes |
FOLLOW |
O$ |
O0KEY |
Order
Entry Control |
ORDER |
P$ |
P0KEY |
Scripting
Maintenance Header |
SCHEAD |
P. |
P1KEY |
Scripting
Maintenance Questions |
SCQUST |
P# |
P2KEY |
Scripting
maintenance Response |
SCRESP |
P+ |
n/a |
Compiled
Script Record |
n/a |
Q$ |
Q0KEY |
Call
List Manager |
CQLIST |
R$ |
R0KEY |
Defined
Reports |
REPFIL |
S$ |
S0KEY |
Statistics
Maintenance |
STATS |
T$ |
T0KEY |
Telemation
User Maintenance |
TMRMST |
U$ |
U0KEY |
Graph
Maintenance |
GRAPHX |
V$ |
V0KEY |
Literature
Packets |
PACKET |
W$ |
W0KEY |
Call
Model Maintenance |
CALMDL |
X$ |
X0KEY |
Customer
Extensions |
CUSEXT |
Y$ |
Y0KEY |
Holiday
Maintenance |
HOLIDY |
Z$ |
Z0KEY |
Installation
Control Record |
INSTAL |
Back to Top
Verifying a file using FPADMIN reports that there are count mismatches. Should I be
concerned?
NO, data and index count mismatches are normal for FAST files that
use the Count Update Modulus.
This option buffers all index count
updates and data node counts in shared memory. This will dramatically increase
the performance of record or index adds, changes and deletes. The modulus value
(non-zero) determines how often buffered counts are written to disk. For each
data or index node, the actual update takes place but the file counts will be
applied when the sum of the adds and deletes applied reaches a multiple of the
given modulus value or when all processes using the file are gone.
The default for the option is 100. A higher modulus
value will increase the performance, but also increases the risk of the file
record counts not being accurate, if a system problem arises or the system goes
down. The file counts can be corrected by performing a Verify File (repair)
option.
Back to Top
|
