Re: Hanging in Checking License Status

Glad that helped you out.
I hope IBM comes back with a patch for that.

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack Woehr
via WDSCI-L
Sent: Sunday, January 23, 2022 10:29 PM
To: Therrien, Paul <ptherrien@xxxxxxxxxxx>
Cc: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>; Rational Developer for IBM
i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Hanging in Checking License Status

Paul, I experienced this again tonight.
Your solution worked, thank you.
I have filed a case with IBM Support (now that I can file cases!)


On Fri, Jan 21, 2022 at 4:15 PM Therrien, Paul <ptherrien@xxxxxxxxxxx>
wrote:

I have had this happen to me on occasion and what it seems to me is
that my workspace is trying to parse my source members that were open
when I last closed RDI.
But since I have not yet connected the parser gets stuck and the
connection sign on box is locked.

The way I get around this is to go into the metadata folder (your path
WILL vary)

C:\Users\therrp\IBM\rationalsdp\workspace2\.metadata\.plugins\org.ecli
pse.rse.core\profiles\PRF.47rptherrp10_0\H.mbimint_127\node.properties


# RSE DOM Node
00-name=mysystem
01-type=Host
03-attr.description=null
03-attr.hostname=MYSYSTEM
03-attr.offline=false <=

Find attr.offline=false and change to offline=true

Now RDi will not try to parse your members until after you connect.

You will find that your connection in RDI is set to 'Work Offline'
Uncheck that, and then connect.

--

Jack Woehr, IBM Champion 2021
<https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/pub
lic_url>
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all attachments
is for the intended recipient(s) only and may contain confidential and
privileged information. If you are not the intended recipient of this
communication, any disclosure, copying further distribution or use of this
communication is prohibited. If you received this communication in error,
please contact the sender and delete/destroy all copies of this
communication immediately.