×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
If you like Redbooks:
http://www.redbooks.ibm.com/redbooks.nsf/searchsite?SearchView&query=iasp
The title about migrating applications to IASP provides a good
overview of application considerations. I don't recall any mention of
IASP-specific object security issues. Setting the job ASP group
requires authority to the ASP device (WRKDEVD *ASP).
Although most commands and programming interfaces can't 'see' the
content of an IASP group unless the job (thread?) ASP group has been
set to that ASP group, some can. A few commands (DSPOBJD, WRKLIBPDM)
support working libraries and objects in any or all ASP groups. With
each ASP group a new database is defined. SQL applications can
connect to the ASP database without setting the job ASP group to that
ASP group. These SQL connections operate in server mode. Presumably
authority to the ASP device that defined the ASP group is required in
all these cases.
On Thu, Oct 2, 2014 at 4:14 PM, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:
When USR1 logs into a IBMi1 5250 session (and inherently placed in IASP1),
can they see or attempt to invoke LIB2/RPG2 in IASP2 if the authority is
*PUBLIC(*USE)?
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.
midrange.com
