Re: API "QYHCHCOP"

Scott,

Got it figured out thanks (my problem not the xml stuff).  My problem was 
indeed stupidity.  I was looking at the parm list as a mapping format for a 
data space, not as parms. 

Duh!  Brain dead moment, minute, hour, day, year, decade, eon, ....

Thanks again,

-- Jim 

>>> klemscot@xxxxxxxxxxxx 10/02/03 05:04PM >>>


On Thu, 2 Oct 2003, James Lowary wrote:

> Has anyone worked with the API "QYHCHCOP"  -  Perform Hardware
> Configuration Operation?  I've looked in the archives and only found one
> message with no responses.  I'm puzzled at it's Parm Group.  Most API's
> make you tell them first the amount of data to expect, but this one has
> the "request" then the length of the request, and the "receiver" and the
> length of the receiver.

The "request" is an XML-formatted string that explains to the API what
you want to do.  "request length" is the length of that string.

The "receiver" is where the results are returned to you.  The "receiver
length" is the maximum amount of data that it can return into that
variable, and the "bytes of return data" are the amount of data that
was returned by the API.

Does that answer your question?   If not, then I'm not clear on what
you mean by "Most APIs make you tell them the first amount of data to
expect"

> http://www-1.ibm.com/servers/eserver/iseries/lpar/qyhchcop.htm
>
> Which seem to be "Bass AckWards", but it's been awhile since I've done
> much API work so maybe I've just got my head "Up and Locked".

I'm not clear on what you think is backwards...  You send the API a
request, and it sends back a response.

The hard part is that you first have to learn the "LPAR markup language"
and/or the "Disk Management Markup Language."  And then, when you try it
it complains that it can't "connect to service."  Then you read the docs,
and see that it needs access to the as-sts service -- which you quickly
find out isn't even listed in the service table.

But that doesn't appear to be the part you're having trouble with?
_______________________________________________
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.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept
for the presence of computer viruses.

www.hubbell.com - Hubbell Incorporated
**********************************************************************