UNIX command not working
Posted 13 January 2003 - 04:55 PM
here's a simple logic in my program.
$DLT_FILE = 'rm ' + C_XTEST + '.' + CDATE(RUN_DATE,'YYYYMMDD')
#RET = SYSTEM($DLT_FILE)
it's working before in window 98 but when we changed our client pc to XP, my PC hangs and can't able to execute this piece of logic. I have a lot of program that uses the same approach and they are all mess up.
Any Idea on how to handle a system command call in UNIX under windows XP ?
Posted 13 January 2003 - 09:04 PM
So, I assume that you have omitted a $ or some quotes.
So testing with
$C_XTEST = 'rick'
#RUN_DATE = @DATE
$DLT_FILE = 'rm ' + $C_XTEST + '.' + CDATE(#RUN_DATE,'YYYYMMDD')
works fine for me so long as $DLT_FILE does not exceed 32 chars or it is DEFINEd larger
or testing with
$DLT_FILE = 'rm ' + 'C_XTEST' + '.' + CDATE(#RUN_DATE,'YYYYMMDD')
also works for me.
Tested with 4.6 bld 276 client on Solaris platform as well as HP-UX - and XP Pro workstation.
Posted 13 January 2003 - 10:08 PM
Bill, did you try to shell out your pro-iv ? I think this is the reason why my unix command line was not executed (I cant get into the shell) because In the first place my XP suspends my telnet connection.
Posted 13 January 2003 - 11:05 PM
Which telnet are you using? If you are using the one that comes with XP - I guess that you also have the issue of local echo - duplicating your login name characters and displaying your password.
I'm running the Win2K telnet on XP.
Posted 14 January 2003 - 02:19 PM
As someone who doesn't really use GUI, I'm intrigued by your apparent problem.
It seems to me that execution of a SYSTEM command should occur entirely within the Unix server and have no effect whatsoever on the client (SYSTEM-CRT would be a different issue of course).
If the client is really affected by a SYSTEM command the question is why.. it suggests something is happening that should be unnecessary (and is probably undesirable).
Yours slightly baffled,
Posted 14 January 2003 - 04:17 PM
I'm not using an emulator. I simply went to a Win2K machine and grabbed telnet.exe off of it, threw it in a directory (errr folder) and point my .piv to use it.
I believe, though I cannot state it with absolute certainty, that ProIV gave us this workaround for the XP issue.
I suspect it wouldn't be appropriate for me to just drop telnet.exe as an attachment on this forum.
Posted 14 January 2003 - 05:03 PM
The 'SYSTEM' command is used for both client and server commands...
#RC = SYSTEM('GUI WINDOWS NOTEPAD.EXE')
#RC = SYSTEM('/usr/bin/rm -f myfile')
Check out the Developers guide to logic.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users