RE: Excel VBA issued OVRDBF runs in QZRCSRVS not QZDASOINIT

["Neill Harper" <neill.harper@xxxxxxxx>]

Not that I would ever recommend this... but...

If you can call stored procs from VBA in excel? Then you could just fire off
a call to QCMDEXC it has two parms the command string and a string that has
the length of the command to execute.

Will work, but is probably a little bit of a security risk. It will run on
you QZDASOINIT job. 


Neill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: 13 November 2010 00:27
To: Midrange Systems Technical Discussion
Subject: Re: Excel VBA issued OVRDBF runs in QZRCSRVS not QZDASOINIT

SQL will recognize an OVRDBF. That was all we had before ALIAS but problem
is that it runs in two different client jobs and I don't see anyway to
change that.

The one solution that I would recommend if you won't use ALIAS is to create
a stored procedure, put the OVRDBF in there, pass it the member name and
return the result as a result set that you can consume.. .

On Fri, Nov 12, 2010 at 4:55 PM, Dennis Lovelady
<iseries@xxxxxxxxxxxx>wrote:

> Yes.  This is the only way, since SQL does not honor OVRDBF.
>
> Dennis Lovelady
> http://www.linkedin.com/in/dennislovelady
> --
> "Get your facts first, and then you can distort them as much as you
> please."
>        -- Mark Twain
>
>
> > When using SQL to access data in file members other than *FIRST, I
> > usually
> > do a CREATE ALIAS to that member. It's a one-time operation for each
> > member.
> >
> > HTH,
> > Loyd
> >
> > On Fri, Nov 12, 2010 at 5:17 PM, Reggie Acosta - El Monte <
> > racosta@xxxxxxxxxxxxxxx> wrote:
> >
> > > We have multi-member files and we're on v5r4 and QZRCSRVS and
> > QZDASOINIT
> > > run in QUSRWRK. My excel VBA pulls DB2 data in from the first member
> > with an
> > > SQL SELECT statement. I want to pull the data from a different member.
> > When
> > > the program runs, the OVRDBF runs in QZRCSRVS and the SQL SELECT runs
> > in
> > > QZDASOINIT.
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.