BCI
Hi Scott,
Yes, Im the Ray, and the reason for delay is that I live in Australia (I was asleep when you posted). Sometime today (I am presenting a class, so time is at a premium) I will dig out the earlier posts and send them to you. Meanwhile you might like to check the BCI manual, which you can find at
http://www.informix.com/answers/english ... 28-952.pdf
BCI (BASIC SQL Client Interface) is a set of functions that mimics the ODBC 2.0 API.
Regards,
Ray
> ----------
> From: Conder, Scott (Ivy Hill)[SMTP:Scott.Conder@ivyhill-wms.com]
> Sent: Thursday, 2 November 2000 05:28
> To: ray.wurlod@informix.com
> Subject: BCI
>
> Hi Ray. Sorry to bother you but I got your e-mail address from the
> DataStage mailing list. David Barham was explaining in the discussion
> list how to create a job-control routine that would allow me to send
> e-mail messages when a job aborts. I never had any idea it would be
> this complicated!
>
> In his outline he suggested I refer to "earlier posts by Ray" to see
> how to use BCI (whatever that is) to load a list of jobs from a
> database. I am new
> to the mailing list so I did not receive the earlier posts. Im assuming
> you are the "Ray" hes referring to and if so, I was wondering if you
> could
> forward to me your explanation of this process? Any help would be much
> appreciated.
>
> Scott Conder
> Ivy Hill Corporation
> Louisville, KY
>
> 502.458.5303 ext. 4045
>
Yes, Im the Ray, and the reason for delay is that I live in Australia (I was asleep when you posted). Sometime today (I am presenting a class, so time is at a premium) I will dig out the earlier posts and send them to you. Meanwhile you might like to check the BCI manual, which you can find at
http://www.informix.com/answers/english ... 28-952.pdf
BCI (BASIC SQL Client Interface) is a set of functions that mimics the ODBC 2.0 API.
Regards,
Ray
> ----------
> From: Conder, Scott (Ivy Hill)[SMTP:Scott.Conder@ivyhill-wms.com]
> Sent: Thursday, 2 November 2000 05:28
> To: ray.wurlod@informix.com
> Subject: BCI
>
> Hi Ray. Sorry to bother you but I got your e-mail address from the
> DataStage mailing list. David Barham was explaining in the discussion
> list how to create a job-control routine that would allow me to send
> e-mail messages when a job aborts. I never had any idea it would be
> this complicated!
>
> In his outline he suggested I refer to "earlier posts by Ray" to see
> how to use BCI (whatever that is) to load a list of jobs from a
> database. I am new
> to the mailing list so I did not receive the earlier posts. Im assuming
> you are the "Ray" hes referring to and if so, I was wondering if you
> could
> forward to me your explanation of this process? Any help would be much
> appreciated.
>
> Scott Conder
> Ivy Hill Corporation
> Louisville, KY
>
> 502.458.5303 ext. 4045
>
Addendum...
Sorry, I did not mean to leave you feeling that it was so complicated to send an email when a job aborts. It isnt. Just write a function to do the work and then call it when you detect an aborted job. In this sense, it is just adding one line of code to the generated code for each job.
What I was trying to explain is that we have added substantially more functionality to job control but emailing is just one small part of it.
-----Original Message-----
> messages when a job aborts. I never had any idea it would be this
> complicated!
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential
and are intended solely for the use of the individual or entity to
whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this
e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
Sorry, I did not mean to leave you feeling that it was so complicated to send an email when a job aborts. It isnt. Just write a function to do the work and then call it when you detect an aborted job. In this sense, it is just adding one line of code to the generated code for each job.
What I was trying to explain is that we have added substantially more functionality to job control but emailing is just one small part of it.
-----Original Message-----
> messages when a job aborts. I never had any idea it would be this
> complicated!
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential
and are intended solely for the use of the individual or entity to
whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this
e-mail from your in-box. Do not copy it to anybody else
*************************************************************************