We have a client that is getting an error 99 in *plus/proj/pathinfo on PXP sessions that are running in Linux as cron tasks (ie: there is no Windx connected session). It appears that this program is related to the TortoiseSVN functionality, but we have never used ANY of the SVN functionality.
The client system is running PXP10, and the line of code getting an error is: 0146 LET api=NEW("[lcl]*obj/winapi") This line appears to require a Windx session to work correctly. It does NOT get an error when our programs are run via a Windx session. It only gets the error when a cron-based program is running.
This system is fairly old and has NOT been updated at all for quite some time, so we are really scratching our heads on why this problem would suddenly appear. Our guess is that somehow, a program was added to SVN, and is now resulting in this error. That's just a wild guess at this point, since we have no familiarity with SVN. Our staff and some of the client staff do have access to PXP consoles, so it's possible that somebody fat-fingered something and turned this on.
Anyone have any suggestions on how to determine if SVN was somehow turned on for a particular program?
Further info:
We have a utility program named "ischn", which is used for closing channels. We call that utility program with a line label (ie: call "ischn;CLOSE") to close the open channels. The error 99 is reported on that CLOSE line label. So, as soon as that line label is hit, PXP ends up in /usr/pxp10/lib/_plus/proj/pathinfo at line 146, where the actual error 99 occurs. The prior level program is line 264 of /usr/pxp10/lib/_plus/proj/pxdta