|
More than one way to skin a cat - er, trim a string, right?
Glad you got it working.
Guys,')'.
After reading through Eric's initial post stating that trim would not work
if the field was not defined as
varying, I sort of dismissed the offered solutions out of hand since the
field in question was char(20) (from
DDS).
But then I saw Jeff's success with Tom's suggestion so I went back, tried
it, and it worked like a charm. Eric's did too, once I fixed a missing
for).
Guess I got a little confused after being informed that the trim function
wouldn't work on a non-varying field but being presented with solutions
using Rtrim (or should I say wouldn't get me the results I was looking
Obviously, I mis-read what I was reading! So, like Jeff, I'm putting these
in the old toolbox!
Thanks again!
--
Buzz
You don't appear to have either. :) Instead, you've got a "home grown"
web service that appears to exchange XML. Those are fun.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, April 08, 2014 12:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: Creating a WSDL for someone else's web service
Every web service "works" the same since they all use HTTP. You've got
a URL that you use HTTP POST/GET/PUT/DELETE...methods against.
SOAP is simply standardized way to publish/consume a WS that relies on
exchanging XML messages.
REST is a term used to define certain non-SOAP defined web services
that relies mainly on arguments passed on the URL.
You don't appear to have either. :) Instead, you've got a "home grown"
web service that appears to exchange XML. Those are fun.
What you need to find out is what HTTP method needs to be used to send
the XML you've been given. Likely, it's a POST. So you'd build your
XML and use the appropriate HTTP_POST_xxxx() method of Scott's HTTP
API.
Did you get anything more from the vendor about using the service? For
example, one vendor I'm working with gave an example that used cURL (a
common HTTP API like command line utility)
Another other is to open the WS URL in a browser and see what's there.
Charles
On Tue, Apr 8, 2014 at 10:37 AM, Koester, Michael <mkoester@data-
east.com>wrote:
Thanks Charles.am
I think I may have a problem though, in that I don't know the details
that I may (or may not?) need. For starters, I don't yet know if I
dealing with a SOAP or REST service. Or can I declare that in myWSDL
and expect the service to play along with whichever I've chosen?including:
The reference you pointed me to says:
"A WSDL description contains all the details of a Web service,
The service's URL. [Got that]i
The communication mechanisms it understands. [No clue - is that
needed?]
What operations it can perform. [Got that]
The structure of its messages." [Apparently most are strings, so
can probably fake that]services.
...and it also says:
"There are four child elements of description that together
encapsulate all of the details about a Web service:
types
interface
binding
service"
Not sure what I need for those.
I'm not there yet. I do appreciate the help though.
-- Michael
~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, April 08, 2014 9:47 AM
To: Midrange Systems Technical Discussion
Subject: Re: Creating a WSDL for someone else's web service
Michael,
Personally, I'd just build the XML manually. It's pretty basic and
not SOAP based; SOAP services are where a WSDL really helps.
If you really want to look at creating a WSDL manually, this might
help:
https://www.ibm.com/developerworks/webservices/library/ws-restwsdl/
Charles
On Tue, Apr 8, 2014 at 9:33 AM, Koester, Michael <mkoester@data-
east.com>wrote:
New project: Communicate through a web service to some other
outfit to set up, modify, enable/disable, etc., email and other
toThis will be integrated with our Service Order maintenanceapplication
running on our IBM Power, in ILE-RPG. I've consumed web services
before. I can handle this.
First obstacle: I am told that this is to be done through their
"web service" (quotes intentional), but when I requested access
one." Oh.the WSDL, I was referred to the care and feeding document. Said
document is a PDF containing descriptions of how to perform
various operations through various snippets of XML. Cool. I
asked again where to find the WSDL, and was told "haven't got
with.
Perhaps I can construct one, and paste in the XML pieces? This
web service (my contact refers to the "app") is not publicly
available, which may explain why they don't have a WSDL. Perhaps
this has never been requested by other clients they've invited to
share the app
suspect
Question: How do I fudge up a WSDL that will include all the
necessary pieces to satisfy WSDL2RPG stub generators?
Second obstacle: I'm still waiting for SysOp to get the updates
installed to allow my access to "Web Administration for i". I
there is a wizard or two there that would help, but I can't getthis:
there yet. We are on
7.1 (still waiting for TR7 too).
One of the operations from the care and feeding manual looks like
[I do have the URL of where the XML gets sent to, as well as the
user and password referenced in the authenticate tag]
To suspend the user, issue the following command:
<?xml version="1.0"?>
<authenticate>
<user>[*****]</user>
<pass>[********]</pass>
<domain>gsinet.net</domain>
</authenticate>
<archive_user>
<user>
<userid>bob</userid>
<archive_code>NOPAY</archive_code>
</user>
</archive_user>
So given that I may be rolling my own WSDL by hand, can someone
point me to some useful details? My goal is to have a suitable
WSDL to be accessed by WSDL2RPG.
Many thanks,
Michael Koester
Programmer/Analyst
DataEast
on the WHERE clause IHORDT is not qualified:list
create view mklib.CUST5000A AS
select a.IHDOCD, a.IHENT#, a.IHSFX#, a.IHINV#,
a.ADINTA,
b.IHRIDC, b.IHCOM#, b.IHIDC#, b.IHENT#,
b.IHSFX#,
b.IHINV#, b.IHDOCT, b.IHORD#, b.IHREL#,
b.IHORDT,
b.IHFL50, b.IHDOCD, b.IHFL51, b.IHORDD
FROM mklib.CUST5000 a
join ASTDTA.OEINHDIH b
ON a.IHENT# = b.IHENT#
WHERE b.IHORDT IN ('COR', 'COE')
On Tue, Apr 8, 2014 at 12:16 PM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:
Am getting error, 'Column List required'. When i run this plainly forlist
viewing in SQL it is fine.
create view mklib.CUST5000A AS SELECT
ALL T01.IHDOCD, T01.IHENT#, T01.IHSFX#, T01.IHINV#,
T01.ADINTA,
T02.IHRIDC, T02.IHCOM#, T02.IHIDC#, T02.IHENT#,
T02.IHSFX#,
T02.IHINV#, T02.IHDOCT, T02.IHORD#, T02.IHREL#,
T02.IHORDT,
T02.IHFL50, T02.IHDOCD, T02.IHFL51, T02.IHORDD
FROM mklib.CUST5000 T01 INNER JOIN
ASTDTA.OEINHDIH T02
ON T01.IHENT# = T02.IHENT#
WHERE IHORDT IN ('COR', 'COE')
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
ah yes sorry bout tht.<stephenrichter@xxxxxxxxx>wrote:
On Tue, Apr 8, 2014 at 12:40 PM, Steve Richter
on the WHERE clause IHORDT is not qualified:
create view mklib.CUST5000A AS
select a.IHDOCD, a.IHENT#, a.IHSFX#, a.IHINV#,
a.ADINTA,
b.IHRIDC, b.IHCOM#, b.IHIDC#, b.IHENT#,
b.IHSFX#,
b.IHINV#, b.IHDOCT, b.IHORD#, b.IHREL#,
b.IHORDT,
b.IHFL50, b.IHDOCD, b.IHFL51, b.IHORDD
FROM mklib.CUST5000 a
join ASTDTA.OEINHDIH b
ON a.IHENT# = b.IHENT#
WHERE b.IHORDT IN ('COR', 'COE')
On Tue, Apr 8, 2014 at 12:16 PM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:
Am getting error, 'Column List required'. When i run this plainly forlist
viewing in SQL it is fine.
create view mklib.CUST5000A AS SELECT
ALL T01.IHDOCD, T01.IHENT#, T01.IHSFX#, T01.IHINV#,
T01.ADINTA,
T02.IHRIDC, T02.IHCOM#, T02.IHIDC#, T02.IHENT#,
T02.IHSFX#,
T02.IHINV#, T02.IHDOCT, T02.IHORD#, T02.IHREL#,
T02.IHORDT,
T02.IHFL50, T02.IHDOCD, T02.IHFL51, T02.IHORDD
FROM mklib.CUST5000 T01 INNER JOIN
ASTDTA.OEINHDIH T02
ON T01.IHENT# = T02.IHENT#
WHERE IHORDT IN ('COR', 'COE')
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
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.
All removed but same errorlist
On Tue, Apr 8, 2014 at 12:18 PM, Jeff Young <jyoung0950@xxxxxxxxx> wrote:
try without the ALL
Jeff Young
Sr. Programmer Analyst
On Tue, Apr 8, 2014 at 12:16 PM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:
Am getting error, 'Column List required'. When i run this plainly forlist
viewing in SQL it is fine.
create view mklib.CUST5000A AS SELECT
ALL T01.IHDOCD, T01.IHENT#, T01.IHSFX#, T01.IHINV#,
T01.ADINTA,
T02.IHRIDC, T02.IHCOM#, T02.IHIDC#, T02.IHENT#,
T02.IHSFX#,
T02.IHINV#, T02.IHDOCT, T02.IHORD#, T02.IHREL#,
T02.IHORDT,
T02.IHFL50, T02.IHDOCD, T02.IHFL51, T02.IHORDD
FROM mklib.CUST5000 T01 INNER JOIN
ASTDTA.OEINHDIH T02
ON T01.IHENT# = T02.IHENT#
WHERE IHORDT IN ('COR', 'COE')
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 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.