|
So, my questions are:
1) Why would it be recreating the *SQLPKG when the program is executed...or
As it trying to create it because they are not authorized to it so it thinks
it is not there?
2) Would there be something specific in the SQL statements that causes it
to rebuild? The name of the files that it is cleaning up changes each time
it is run so maybe that is related.
3) What machine and what profile is it using that is causing the authority
issue? Is it the dev box profile and authority or the prod box profile and
authority...or some weird combination of dev profile and prod authority or
vice versa?
4) I know when compiling the program on the dev box, I can specify where
the *SQLPKG is created. If I specify QTEMP for that parm, will it try to
recreate it in QTEMP and maybe that will eliminate my authority issue? I
really want to do this the right way so if this is just a workaround and not
the right answer, I'd prefer to do this only as a last resort.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.