Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object Lock check not looking at correct build library when creating table #127

Open
beckhamrryyaann opened this issue Aug 24, 2022 · 1 comment
Assignees

Comments

@beckhamrryyaann
Copy link

beckhamrryyaann commented Aug 24, 2022

I have had several instances where I am trying to use the create table statement. The table does not exist in my "objlib" or build library. It appears bob tries to make sure the object is not locked before it creates the table. It is finding the object in my production library which is on down my library list. The production table is locked. Bob gives an error saying the "object' is in use and will not build. It seems BOB should only look for the table in my build library....
>> Temporarily set curlib to crbtest CPC2197: Library CRBTEST removed from library list. CPC2196: Library CRBTEST added to library list. CPC2198: Current library changed to CRBTEST.

MSG ID SEV RECORD TEXT SQL0913 30 1 Position 1 Row or object PRDWRK01F in MMIPROD01 type *FILE in use. SQL7961 0 Rollback completed.

Notice my current library is CRBTEST, but its finding an object lock in MMIPROD01.
This is because the table in CRBTEST does not exist yet. I am building for first time.

@edmundreinhardt
Copy link
Member

this may be related to issue 159

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants