|
The only real error I see is there is no name resolution. Check to be
sure 78CE350.BIOFORCE.SE is in the host table with the correct IP
address.
Or if you insist on no host table verify that it’s in DNS and you can get
to the DNS server.
It easier and faster to verify the host table
Jim Oberholtzer
Agile Technology Architects
On Jun 18, 2025, at 4:37 AM, konsult@xxxxxxxxxxxxxxx wrote:https://www.ibm.com/support/pages/manage-update-access-keys-ibm-electronic
message: 1
date: Tue, 17 Jun 2025 15:59:52 -0400
from: Rob Berendt <robertowenberendt@xxxxxxxxx>
subject: Re: UAK Keys...
Give this a try first:
-service-agent-esa-ibm-ifind
That looked as if it could be a brilliant solution.
Unfortunately WRKSRVAGT fails miserably with message " Download and apply
Update Access Key stopped."
And in the joblog tells me to check the audit log (not journal) where I
the following information for what it is worth:1220223
25/06/18 10:30:24 QS9WRK1: spawn() was submitted and the Process Id is:
2126.
25/06/18 10:30:25 QSJUAKCHECKER: successfully got expiration date =
expire( <
25/06/18 10:30:25 QSJUAKCHECKER : QSJUAKCHECKER : UAK is about to
2516936074
30days ) or already expired
25/06/18 10:30:27 QS9PRBPREP: Valid Problem. Id=2516936074 Status=R
25/06/18 10:30:28 QS9PRBPREP: Ready for Service Call for Problem
the
25/06/18 10:30:29 QS9PRBSND : Universal Connection.
25/06/18 10:30:29 <init>: 78CE350.BIOFORCE.SE: 78CE350.BIOFORCE.SE:
Hostname
and service name not provided or found
25/06/18 10:30:29 DownLoadUAKTask: An exception has been thrown while
Hostentitlement
Name was retrieved.
25/06/18 10:30:29 QSJUAK: download key failed.
25/06/18 10:30:30 QSJUAK: Error happened when downloading the
key,list
please see details in trace
25/06/18 10:30:30 QS9WRK1: The return code of the program is: 5.
25/06/18 10:31:28 QS9PRBSND : Service Call Successful for Problem
2516936074.
PMR is TS019616825.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.