We have a configuration table in our package that has a row for each
printer. It contains information specific for our workflows: headings, lines
to advance, next check number, print logo, etc, etc. All of the information
that she has been asked to put on the screen is contained in this table
except the I.P. address of the printer. That one piece of information is not
specific to our package but specific to the *devd. We could put it in the
table (and we probably will,) but that would mean that if someone changes
the device description with changing the table, the information is
incorrect.
I do have a program that calls the necessary API to obtain the address
(among other things) and I can make it available as a UDF without too much
trouble. I am just hoping that IBM has already done the work like they have
with so many other things.
I'll be with 12/13 year-old boys at scout camp all next week and hope that
when I get back someone will have said, "Oh, yeah. That is table or view
xxxxxx in QSYS2." However, what will probably happen is, I'll create the
function for her and then somebody will say, "Oh, yeah. That is table xxxxxx
in QSYS2." Just like when you can't find that tool in the garage until
you've bought a replacement.
Troy
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
midrange-l-request@xxxxxxxxxxxx
Sent: Friday, July 15, 2016 9:21 AM
To: midrange-l@xxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 15, Issue 1128
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than
"Re: Contents of MIDRANGE-L digest..."
midrange.com
