Can't change current library from old library to new

[kraudy]

Hi, recently i changed my library on the ibm i server, so now i don't have access to that old library, lets call it LIBOLD. The new library is LIBNEW.

Here is my problem. I can't seem to find a way to remove LIBOLD form the vscode for i lib list and also can't set LIBNEW as the new current lib. Which means, everytime i try to compile something, it tries to use LIBOLD, which i have no access anymore.

I would aprecciate any advice. Thanks

This is LIBOLD

This is LIBNEW

This is the error when trying to compile

It looks like it is in limbo

[SJLennon]

This doesn't work when you right click on a library?

[kraudy]

This doesn't work when you right click on a library?

I can remove the new library but not the old one (which is set as current library)

[SJLennon]

You may have discovered something the developers didn't think of, so it may be a bug.

You did try right clicking and doing this?

Does doing CHGCURLIB on the green screen and then reconnecting make any difference?

If you are really stuck, you could:

• Create a new connection.

• Or if you are comfortable with it, you could manually edit setting.json: But be careful...

[kraudy]

Right click + change current library gives this error

Changing the curlib on the green screen does nothing

I don't wanna try editing the settings right now cuz i have other connections and i don't know if that is gonna mess something else up and give me more headache

[worksofliam]

Please share the contents of your Code for IBM i output channel after the error appears.

[sebjulliand]

Hi @kraudy,
this is indeed a bug. If your settings' current library doesn't exist anymore, then it cannot be removed.
I'll work on a fix, but in the meantime, you should follow @SJLennon advice and replace your connection's currentLibrary by something else (like QPGL). This will get you going while the fix is being worked on and you have no risk of breaking anything.

Alternatively, you can use the Copy... action to duplicate the faulty connection and make a copy of everything but the library list.

[kraudy]

Here is the output @worksofliam

[sebjulliand]

@kraudy this problem has been fixed in v2.10.1 that was released today.
After you've updated the extension, you'll be able to change you current library.

[kraudy]

Thanks @sebjulliand