× 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.



John,

The DDM stuff all runs with standard authority.

I do not give any special authority to my users other than some commands which IBM ships with *EXCLUDE *PUBLIC. I grant *USE rights to those commands. In most cases that would be less than 5 commands that may need authority granted to.

DArryl

Sent from my iPad

On Aug 26, 2015, at 3:50 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Wed, Aug 26, 2015 at 2:25 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx> wrote:

[In response to questions about the use of DDM to implement remote
program calls from one LPAR to another:]

If you require a password utilize the

ADDSVRAUTE Add Server Auth Entry
CHGSVRAUTE Change Server Auth Entry
DSPSVRAUTE Display Server Auth Entries
RMVSVRAUTE Remove Server Auth Entry

commands. If you use these command system value QRETSVRSEC must be set to '1'.

The DDM server name for these commands is QDDMSERVER.

I'm sure it works nicely once it's all configured, but if you don't
already have it configured, it feels like a very cumbersome solution
to me. Especially if you're in a situation like mine, where I don't
have *IOSYSCFG authority, or the expertise to properly administer
stuff like this; and the person who does have the authority and
expertise is completely backlogged, and who knows when he would be
able to set DDM up for me, even assuming my request is accepted by my
manager.

For communicating between LPARs, including both remote program
execution and real-time data transfer, my preferred method is RPC.
Conceptually, this is similar to Web services. Actually, depending on
who you ask, Web services are a specific form of RPC which happens to
utilize the HTTP protocol.

It will not surprise those who know me that the reason I like RPC is
that Python's standard library comes with facilities that make this
very, very easy. Ludicrously easy. With zero knowledge about sockets,
I just followed the examples in the Python documentation and had RPC
up and running in minutes.

(By "follow the examples" I just mean copy and paste straight out of
the docs for the "SimpleXMLRPCServer" class. The program that runs on
the "server" is 32 lines of code, including comments and blank lines
for readability; the "client" needs just 2 lines of code to start
communicating, and then the remaining lines in the short example
demonstrate the functions defined by the server.)

Of course I already had Python installed. If you have to install
Python from scratch, and you're not an administrator but have
authority to restore objects to production, I still recommend
iSeriesPython (instead of IBM's official Python). I think most people
can download and install iSeriesPython in less than half an hour
(probably much less).

Once you have the example up and running, you just have to modify it
to suit your needs. If you (not just OP, but anyone who is reading
this) is interested in this and needs further references, tips, or
help, just send me an e-mail.

John Y.
--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.