RE: Create product (solved)

Thanks Simon & all who looked at this.  I was aware that an additional
product load would be necessary as well as object changes for the
product prior to packaging.  After loading the libinfods with the
special values I worked.  Thanks again. 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Thursday, November 30, 2006 4:06 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Create product (solved)


On 30/11/2006, at 12:12 PM, Scott Klement wrote:

I don't know how much help this is.  I spent a little while (maybe 1/2
hour) earlier trying to figure out the documentation for the API, but 
ran
out of time that I could spend on it.  The documentation is terrible.

The
error message isn't very enlightening.  I suppose that it's easy

enough

for someone who is familiar with the way that software products are 
built,
but it's all new to me, and I'm a bit lost.

The information in the discussion on the iSeries forum provided the two 
things missing from the original append in this list:
        1) The message ID
        2) The command parameters used to invoke the code

The documentation is fine--especially on current releases. You just 
have to be particular when processing it. I've built a complete set of 
code around these APIs to replace the IBM SMU LPP. It packages products 
and options and handles the PTF process too. The only problem I ever 
had with these APIs was adding directory support to QPZCRTFX at VRM420 
where they were supported but not documented until 510 and the 
structures at 420 were different from the documented structures at 510. 
Bruce Vining very kindly helped me make sense of this.

In this particular case the cause of the "Object name *N not valid" is 
because the LibInfoDS is not being populated correctly. In your example 
command both the "Primary library" and the "Post-operation exit 
program" fields are blank. In the original example the "Post-operation 
exit program" field is blank.

Blanks are not acceptable values for these fields. They must contain a 
name or one of the allowable special values. Sensible default values 
can be provided on the command definition by specifying the allowable 
special values for the default parameter values.

Specifying correct values for these two fields allows the example code 
to run. The code still has the errors I mentioned in my previous append 
but they'll cause different errors that will manifest after the 
LibInfoDS structure is fixed.


Regards,
Simon Coulter.
--------------------------------------------------------------------
    FlyByNight Software         AS/400 Technical Specialists

    http://www.flybynight.com.au/
    Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
    Fax:   +61 3 9419 0175                                   \ /
                                                              X
                  ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------