Sys_shell Error Handling

[[email protected]]

I use Sys_Shell to execute a "dos batch file"

Such batch file namely "auto.bat"
would contain data like

*******************************

net use \\print_server\printer1
copy xyz.dat \\print_server\printer1

*******************************
(xyz.dat contain typical txt data to be printer by "printer1"

in most cases, such operation resulted successfully and I am
very please with the result. where printer1 just printing out the
xyz.dat's data, typically 10 to 20 line of texts

However, from time to time, when "\\print_server" a physical pc
itself is experiencing problem or off line. resulting in a dos prompt window
loking like in a lockup stage and no doubt the entire Alpha5 just wait to see
and all other print job in queue andnot going anywhere/

Since the quality of such operation/execution is now under a dos prompt
and looking like it is beyond Alpha's control?

How can I get a proper ackowledgement back from "system? or pc?"
to tell me if such operations is successfull.

Furthermore, while "dos prompt" is hang with the auto.bat being executed
and waiting, such xyz.dat file being "locked" and therefore I am not able
to brutally force delete and forget about the job.

And lastly how to "force close" the dos prompt operation, which is partilally
hang or looking like in a lock up stage awaitng \\print_server\printer... response.

I hope I am able to explain my problem,

Appreciate anyone's assistance,

Ken Tjia
AM/PM
Canada

[Finian Lennon]

You need to use Sys_shell_wait and an error trap in your batch file to ensure that it completes. You can find the necessary syntax for writing the batch file in many sites on the web.

You would use A5 to
(1) check for a file name on the hard drive
(2) If it finds that file, delete it
(3) Create a file of that same name
(4) Run the batch file using sys_shell_wait.
(5) If it (the batch file) succeeds/completes, delete the file
(6) If it fails, end the batch file but don't delete that file
(7) The next line after sys_shell_wait checks for the existence of the file. If it's not there it knows the batch file completed successfully, if it is there the batch file failed.

[[email protected]]

Thanks, but i do not think such function is available on version 5
will check for it later on the day//

[Stan Mathews]

Thanks, but i do not think such function is available on version 5
will check for it later on the day//

sys_shell_wait() for v5

[[email protected]]

Yes Stan, good morning
just did a quick search myself and discover such link
i trust this would help me a lot and will give it a serious test this afternoon/

Once again appreciate the prompt assistant

Ken Tjia

[Finian Lennon]

Mmm.. I just noticed that the built-in Sys_Shell_Wait was released for Vv6 and not for V5. Do a board search on sys_shell_wait and I think you'll find a version I posted that does work. If not, let me know and I'll post it again here.

You can still get by, though not as elegantly, without sys_shell_wait. Once again, the technique involves writing a file to the hard drive and then running sys_shell("Batch_file"). The last line of the batch file removes the file you wrote before starting the batch file, and the xbasic would look something like (and you MUST supply your own path information for the app_path variable below)

if file.exists(app_path+"deletefilename.txt") then
file.remove(app_path+"deletefilename.txt")
end if
fp = file.create(app_path + "deletefilename.txt", file_rw_exclusive)
fp.write_line("Anything")
fp.flush()
fp.close()
sys_shell("BatchFile")
tryagain:
if file.exists(app_path+app_path + "deletefilename.txt") then
goto tryagain
end if

and the script will proceed when the deletefilename.txt file is removed.

[[email protected]]

Yes, I have done such features for the last 10 days.
Seems ok, by actually having a shadow file.

It is working but not too clean? I discover when the
actual device (printer) is down, the command promt
stayed on forever, despite force close, such file occupied
forever by the system. Meaning such file will exist forever
until the pc get reboot oneday.

Again it is acceptable, but we ran 40 plus print job and
on purposely turn off the printer, boy it sure look ugly hi.
with many command prompt opened and drained a great deal
of resources.

Thanks for now,

Ken Tjia