codefori / codefori/vscode-db2i

CURLIB in SQL job

Open
#454 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
76
Forks
54
Avg merge
17m
Merged PRs (30d)
1

Description

db2i Version 1.15.1

The current library is not set properly in SQL job.
In Code for IBM i, I set the current library. I can use the RUNSQLSTM Action to create an unqualified object using *SYS naming, and it will be created in the current library.

Image

Image

When I start an SQL job, it uses the library list from Code for IBM i. The libraries are in the proper order, but the current library is not set.

Image

If I use Ctrl+R to interactively run the same CREATE statement using *SYS naming, the table will be created...

Image

But it's created in QGPL:

Image

I can change to use *SQL naming instead of *SYS naming, it does seem to use the first library as the default (even without the current library being set). Would very much like a way to set the current library for *SYS naming.

Thanks!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.