Poorly documented APIs

[Rajeev_Asthana@xxxxxxxxxxxxxxx]

Hi All,

Recently, I tried to design a job monitoring utiltiy using various APIs which
included Job APIs and Message APIs.
Till now, I haven't acheived the full requirement. The main reason behind this
is because of very poor documentation of APIs.
For example, consider List Job Log Message (QMHLJOBL) API.
This API has an input parameter as structure which contains over 20 fields. In
the documetation, it's not very much clear  what values to use. I tried for 2
days and nothing came fruitful. Take for example, the field 'Offset to
identifiers of fields to return'. How can I know this value in advance in input
parameter? The way to get this info is no where mentioned. There are several
examples of this kind.

Then there is this key values that are used in many APIs. The processing of key
values are so confusing too. For example, consider List Job (QUSLJOB)  API.
I'm not still sure how to use keys in this API.

Can someone from API team in IBM take some initiative to document these properly
and provide some examples for each APIs?

Thanks,
Rajeev.

-------------------------------------------------------------------------------------
"This  email message and files transmitted with it are confidential, proprietary
and legally privileged. If the message that is received is an error, or if there
is  any  mistransmission,  the  originator  must  be notified immediately as the
unauthorized  use,  dissemination, publication, transfer or any other use of the
message  by  unauthorized person is strictly forbidden by law and prohibited. If
anybody  commits  violation then he would be legally liable and punishable under
the  relevant  law.  The  intended  recipient  can  be  rest  assured  that  the
confidentiality and privilege is not waived or lost by any such mistransmission.

Internet  communications  are  not secure unless it is protected by using strong
cryptography.  TCS  does not accept any responsibility whatsoever for changes in
the nature of modifications, additions, deletions made to the message once it is
sent.

TCS  reserves  the  right  to  monitor  all  e-mail  communications  through its
network."
-------------------------------------------------------------------------------------

Tata Consultancy Services
www.tcs.com



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---