$! $!Basically we silently assign a symbol "newperf" to be $!used by the other tests. $! $!On VMS V7.3-1 see within the $!HELP utilty the 2 example in the ":=" symbol assignment $!topic. Note that the leading dollar sign is needed to $!treat the program as a foreign command. $! $!Here are some commented out examples of how to modify the last line: $! $! newperf :== $user:[pprymmer.bin]vms71p4.exe $! newperf :== $disk$dka100:[pprymmer.bin]vms39491p4.exe $! newperf :== $dla4003:[pprymmer.bin]p4.exe $! $!Please edit the next line to suit your perforce client installation: $! $ newperf :== $S1:[PPRYMMER.PERFORCE]PERFORCE_AV.EXE
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 5686 | peter_prymmer |
VMS DCL procedures to reveal several bugs in (at least) the 2002.2 release of the p4.exe client program for VMS including: 1) use of "p4" as a foreign command global symbol is not recommended (these tests use "perforce" and "newperf") 2) the inability to deal with RMS versioning (demonstrated by the revert_deletion.com test) 3) the inability to recognize uppercase parameters and switches (demonstrated by the dash_v.com test) 4) a regression in dealing with a return() of a bad $STATUS to the command level when P4PORT is incorrectly set and you issue "perf info" (info_status.com test) I recommend reading the readme and modifying p4_setup.com and revert_deletion.com before trying to use these procedures. |