$! $!run_all.com - run all acceptance/regression tests for a perforce client on VMS $! $ if f$type(perforce) .eqs. "" $ then $ write sys$error "perforce symbol not found." $ exit 44 $ endif $ if f$type(newperf) .eqs. "" $ then $ @p4_setup $ endif $ if f$type(newperf) .eqs. "" $ then $ write sys$error "newperf symbol not found." $ exit 44 $ endif $! $ show logical p4* $ show symbol perforce $ show symbol newperf $! $another: $ file = f$search("*.com") $ if file .nes. "" $ then $! we upcase so as to accomodate ODS-5 case preservation (although $parse usually returns upper) $ name = f$edit(f$parse(file,,,"NAME",),"UPCASE") $ if name .eqs. "P4_SETUP" then goto another $ if name .eqs. "RUN_ALL" then goto another $ write sys$output name $ @'file' $ goto another $ endif
# | 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. |