topic Re: Checking for errors within a VMS batch job in Operating System - OpenVMS

Checking for errors within a VMS batch job

Jorge Cocomess — Tue, 14 Nov 2006 10:00:12 GMT

Greetings,

I have this FTP batch job running on my VMS server. The batch job is written to do just that. However, I would like to insert an error check point incase the file was locked from uploading from another server. I am not sure how to do this. I am welcome for any suggestions to this subject.

Thank you in advance.

Jorge

Re: Checking for errors within a VMS batch job

Ian Miller. — Tue, 14 Nov 2006 10:12:23 GMT

If you are using the HP TCPIP Services for OpenVMS product then using the COPY/FTP command should return a error to your DCL process if the ftp transfer fails.

$ COPY/FTP ....
$ IF .NOT. $STATUS THEN ....

Re: Checking for errors within a VMS batch job

Art Wiens — Tue, 14 Nov 2006 10:14:03 GMT

$! Files arriving are via Decnet COPY. A race condition can exist when the file hasn't
$! been fully copied and this procedure "finds it". Test - if we can't OPEN it, we can't FTP it.
$ OPEN /READ /WRITE /ERROR=LOCKED_FILE FILE 'FILE_TO_SEND'
$ CLOSE FILE
$ GOTO ACCESS_OK

Works for me,
Art

Re: Checking for errors within a VMS batch job

Daniel Fernandez Illan — Wed, 15 Nov 2006 04:24:58 GMT

Hi Jorge
For a similar question I use a test for locked status of file. The command waits until target file is unlocked and after executes ftp.

$set noon
$fil="target_file"
$do:
$!Check if file is locked or opened
$att=f$file_attributes("''fil'","eof")
$if $status .eqs. "%X00000800" !File open
$then
$ wait 00:03
$ goto do
$endif
$ftp
....

Saludos.
Daniel.

Re: Checking for errors within a VMS batch job

Peter Barkas — Wed, 15 Nov 2006 04:49:33 GMT

A technique that I have used in the past is for the sender to copy the file with a file type dedicated to 'files being copied' perhaps .tmp and then to rename the file after the copy is complete.

Re: Checking for errors within a VMS batch job

John Abbott_2 — Wed, 15 Nov 2006 07:23:25 GMT

Hi Jorge

We have a mixture of ftp jobs, not all vms 2 vms, other o/s involved so..

I'd recommend that the application/job that sends the file(s) sends a "completed" 1 block file afterwards and that you check for the presence of this file.

Using this method ensures that the file transfer has completed (one or more files) and that you have all the data. You could end up with a situation where the file transfers dies part way through due to unexpected error (network, sending sever fails, diskquota exceeded etc) you could end up processing a partial copied file.

Your dcl code would just check for the completed file, continue if present or wait and loop around a number of times if not present (i.e. consider giving up waiting after so many loops).

John.

Re: Checking for errors within a VMS batch job

Wim Van den Wyngaert — Wed, 15 Nov 2006 07:29:31 GMT

I would keep a log of what FTP said. After the FTP read it, parse it and compare it with a good ftp. Error as soon as something is missing or given extra.

Wim

Re: Checking for errors within a VMS batch job

Jorge Cocomess — Wed, 15 Nov 2006 10:30:09 GMT

Hi,

The file being generated on the Wintel server and FTPed down to the VMS server at a scheduled time. From the VMS server I will check for this file and FTP up to our client FTP site. The reason I like to do the error checking due to the repeat of this FTP process every 15 minutes interval.

I will update my FTP batch job and post it online for your review. Please review it and give me your suggestion.

Thank you in advance.

Jorge

Re: Checking for errors within a VMS batch job

Ian Miller. — Wed, 15 Nov 2006 12:25:05 GMT

You may find FTSO of interest - its' free
http://h71000.www7.hp.com/freeware/freeware70/ftso/

Re: Checking for errors within a VMS batch job

Jorge Cocomess — Wed, 15 Nov 2006 12:48:24 GMT

Ian,

Thanks for the link. By the way, how do you use these programs? There was a readme file but nothing for installation intructions.

J

Re: Checking for errors within a VMS batch job

Shlomo Berlinger — Mon, 27 Nov 2006 06:20:23 GMT

Automate your ftp session as follows:

1. Before calling ftp, set sys$output to a file (to trap ftp output).
2. Call ftp using /input to give ftp your copy (put) command.
3. After the ftp command, check the output file for a sucess string. (The success string might vary; check your output file to be certain).

$ def/user sys$output ftp.output
$ ftp 192.168.1.1 /user="username" /pass="password" /input=ftp.input
$ sea/noout ftp.output "226 Transfer complete"
$ if $STATUS .ne. 1 then write sys$output "FTP failed."

Re: Checking for errors within a VMS batch job

Jorge Cocomess — Mon, 27 Nov 2006 19:07:24 GMT

Great!! I will give it try and let you know how it went.

Sometime, I wish I can assign more points than the usual 10 pts deal.

Have a great day!!

Jorge