Joined: 02 Oct 2008 Posts: 15 Location: Tyler, texas
The problem is this:
I use a BATCH file to send a JCL to the mainframe. The users have to put in userid and password and this is part of the FTP command file that then sends the JCL to the Z10.
Well sometimes they fail to put in the correct name or password and the FTP fails. But they don't know it failed.
Is there some error checking that will detect a failed FTP and then allow thw batch file to tell them via echo, or email from the mainframe, that it failed?
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
Suggest you talk with your desktop/network support people for some way to do this on the desktop.
If the jcl actually gets submitted and there is an issue running on the mainframe, additonal jcl might be added to the job to deal with the error (i.e. send an e-mail), but if the process never connects/submits, the mainframe batch job will never run.
Joined: 02 Oct 2008 Posts: 15 Location: Tyler, texas
Hello.
Well I used Quick basic to do the screens and do error checking. Using that I was able to verify the files on the server were there before sending them across. Also the users could cut-n-paste names and dates right on the screens.
Joined: 20 Feb 2009 Posts: 108 Location: Kansas City
Does quick basic have an ftp client library? If so you can submit jobs directly to the job queue on the mainframe via ftp. You can even check the job status in the queue:
you can use ftp tp retrieve the job output as well, and then use find or some other command to verify that some string is there as you expect. If the ftp(s) fail, you won't find the string and can put up a message
