Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
Colleague wanted to enchance our FM_PAGER action routine today so that it would send an GSM SMS message instead of pager message. After those (fairly minor edits to CONSOLE$ACTIONS:FM_PAGER.COM) the action failed consistently. It took quite a few hours and bit of luck to figure out problem. The procedure CONSOLE$ACTIONS:FM_PAGER.COM was correct but somehow PCM just failed always with launching the action. The problem turned out to be the back that this user had made a precautionary copy of FM_PAGER.COM to name FM_PAGER.BCK (in console$Actions). Apparently PCM, in searching for "action".COM or "action".EXE actually found this "action".BCK and either did not know what to do with it or maybe tried launching that file as an VMS executable. Seems that one would be better off with making safety copies to "action".ORG or "action".SAV _veli P.S. PCM version was V1.6-201.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1513.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Apr 04 1997 13:07 | 7 | |
Veli, Good work. You analysis is correct. The .BCK file was found first when PCM did a wildcard search for the file because .BCK comes before .COM or .EXE in the ascii collating sequence. Regs, Dan |