Thanks, everyone. I'm cocking up an example piece of code now. Will share
with the group later.

On Wed, Feb 1, 2017 at 4:44 PM, Kevin Wright <kevin.wright@xxxxxxxxxxxx>
wrote:

Hi,

In V7R2M0, QUSRJOBI Format JOBI0400 has a few items of interest towards
the bottom:

Offset to ASP group information
Number of entries in ASP group information
Length of one ASP group information entry
Job description library ASP device name
ASP group information entry

This is not new in V7R2M0 from what I can see.

Regards,

Kevin Wright | IBM i Developer, LPC
<snip>
I use SQLCLI APIs in my C++ stuff. My software has always connected to
*LOCAL for the database. Now we have a newfangled Power8 setup with
separate *SYSBASE and an iASP. Our sysadmin says there will be no customer
data on *SYSBASE. We want to have as minimal code change as possible for
the new hardware. He said that he can set up the user that we use for
database access to default to the iASP. He has named the database on that
iASP to have the same name. I know I can scour the JOBD that the user is
attached to for its default ASP, but how can I get it from an actively
running job? Do I even need to do this?

What we're trying to do here is avoid having to go to a 3-part naming
scheme, although that isn't onerous because we have library routines that
help us build our table access path. O

I thought QUSRJOBI() would give me this and it is possible I'm missing it.

--
Kelly Beard
--
This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L)
mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.





This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].