Archives of the TeradataForum
Message Posted: Thu, 10 Feb 2005 @ 12:59:52 GMT
I can't remember the exact error code (you could look in the Messages manual under the "CLI-Messages" section) but you could take almost any non-zero return code from the logon command after you ignore the obvious ones like (user not authorized, invalid/expired password etc).
Once you know what error code you're looking for, you can use that error code as the return code from a Bteq script - use the ".QUIT;" command by itself and Bteq will pass the last error code back to the operating system. This can then be trapped in the next JCL step using the COND syntax.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|