Archives of the TeradataForum
Message Posted: Fri, 21 May 2004 @ 19:15:01 GMT
<-- Anonymously Posted: Friday, May 21, 2004 13:17 -->
I had a similar thought about having additional IN parameter. And I am currently using a proc to enter the log entries. I might not able to modify the existing proc to have an IN parameter since it is running in our production for quite some time and it is used in lot of procs. The existing procs are using a manual entry of step number. With my project, I have written nearly 60 procs where I need to enter the job logging related entries in each. I just wanted to do a smart work by avoid manual entries of step number.
The other response for my request suggested to do x+1 but that would be another set statement after or before call to job log table which will make the proc cumbersome and too big. I had once faced the limitation of 64K text in the proc which I want to avoid as well since we would not upgrade to v2r5 for some more time.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|