Re: Unknown system state during get request

["Eric Wasek" <ericw@xxxxxxxxxxxxx>]

Howdy Scott,

After the latest CUM (for 5.1) was loaded over the weekend to upgrade OS/400 
at the second remote system, the test worked.  The CUM media should be 
shipped and loaded to the first remote site within a couple of weeks.  If 
the loading of the CUM on the first remote site does not fix the situation, 
the forum will hear from me again.  Otherwise, assume that the CUM fixed it.

I am very pleased that we do not have to update HTTPAPI.  Correcting 2 sites 
with a CUM is easier than dozens of sites with HTTPAPI.

Eric

----- Original Message ----- 
From: "Eric Wasek" <ericw@xxxxxxxxxxxxx>
To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, December 09, 2010 3:16 PM
Subject: Re: Unknown system state during get request


> Hello Scott,
>
> Thanks for the information.  The OS/400 upgrade will be attempted first. 
> We
> will have to find the media and other related things to get this done.  If
> the media cannot be found or there are other problems we will be updating
> HTTPAPI.  Either way the forum will know the results when we do.
>
> Eric
>
> ----- Original Message ----- 
> From: "Scott Klement" <sk@xxxxxxxxxxxxxxxx>
> To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, December 09, 2010 1:26 PM
> Subject: Re: Unknown system state during get request
>
>
>> Hi Eric,
>>
>> I have the following in my comments for HTTPAPI (in the current version,
>> it's probably not there in 1.16):
>>
>>   * (Note: GSK_SERVER_AUTH_TYPE isn't available on V5R2 and
>>   *        earlier without a PTF.  See APAR SE07984 for more
>>   *        info.  If the current system doesn't support this
>>   *        option, GSK_ATTRIBUTE_INVALID_ID will be returned. )
>>
>> This appears to be the problem you're experiencing. (The message you
>> posted is identified by 'GSK_ATTRIBUTE_INVALID_ID' in the program, and
>> the text from your log 'setting auth type' means that you're at this
>> point in the program.) The current version of HTTPAPI compensates for
>> this error... but, as we discussed previously, you're running an old
>> version.
>>
>> So you can update OS/400, or you can update HTTPAPI.  (Or, I suppose,
>> you can change the code so it just ignores the error and continues.)
>>
>>
>> On 12/9/2010 12:37 PM, Eric Wasek wrote:
>>> Hello again,
>>> After a one week delay I am back on this situation again.  As you may
>>> recall, we were going to load LIBHTTP and test programs on a second
>>> remote
>>> system and see what the resulting messages revealed.  This has been
>>> accomplished and the results are inconsistent with the results on the
>>> first
>>> remote system.  The debug information follows, along with some of the
>>> code
>>> from the test program.
>> [SNIP]
>>> SetError() #24: Setting auth type: (GSKit) Identifier value is not 
>>> valid.
>> -----------------------------------------------------------------------
>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>> http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>>
>>
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
> 



-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------