|
Just as an update to this issue, I am running a 400 job by calling it from Script and it is run under the user QUSER. Dave Bednarcik Email: DaveBednarcik@WesternUnion.com Work #: (201)263-5186 Fax # : (201)263-5455 Steve Brault <sbrault@e-100gro To: "'domino400@midrange.com'" <domino400@midrange.com> up.com> cc: Sent by: Subject: Library Lists domino400-admin@m idrange.com 07/10/2002 01:23 PM Please respond to domino400 We are developing a Notes/Domino application that interacts with AS/400 data. The Domino app uses stored procedures to call RPG programs, which then do various things. These RPG programs seem to run using the user profile QNOTES. My question is: is there a way to control the library list in which these jobs run? Basically, in the plain-old AS/400 world, we have a production environment and a test environment. Even though they run under the QNOTES Profile, it does not appear that the use the libraries in the related JOBD. We had to change the Domino Servers JOBD. What we really want to happen is the following: User will select TEST or PROD All applications stuff with the Domino arena will use the correct library list based on the users Test or Prod selection. we DO NOT want to set up 2 domino servers Can anyone help me out?? ps... I saw this posting, but do not fully understand it Could you not dynamically set the schema in you ODBC Connection? Steven S. Brault Technical Consultant The e-Onehundred Group _______________________________________________ This is the Lotus Domino on the iSeries / AS400 (DOMINO400) mailing list To post a message email: DOMINO400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/domino400 or email: DOMINO400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/domino400.
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.