User`s guide

12–8 PALcode Violation Checker
Starting and Running PVC
12.4 Starting and Running PVC
After you have prepared the input files, you can begin your PVC session. For
example:
% pvc
PALcode Violation Checker V3.26
Default Cpu set to DECchip 21164 family.
PVC> set code osfpal_pc164.nh
PVC> set entry osfpal_pc164.ent
PVC> set map osfpal_pc164.map
PVC> go
Initializing Alpha dependent tables..
Initializing 21164 dependent tables..
Disassembling executable...
Searching through map file for violation exceptions...
Beginning PALcode check...
End of PALcode check...
PVC> quit
PVC messages, errors, and warnings are sent to stdout (in most cases the terminal
screen). The following example sets up a PVC log file to collect this information:
PVC> set log_file filename.log
If the run is successful, a Run Completed message is displayed. (See Section 12.6 for
other commands you can use during your PVC session.)
12.5 Creating a PVC Environment
To automatically load PVC input files when you begin your PVC session, set up the
following environment variables though your .login file (if you are using DIGITAL
UNIX with a C shell) or the Control Panel (if you are using the Windows NT
operating system):
• PVC_PAL — for the executable file
• PVC_ENTRY — for the entry points file
• PVC_MAP — for the .map file
• PVC_CPU — for the CPU type
• PVC_LOG — for the log file