You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SQL procedure was defined by a contract programmer from Profound Logic. I don't have authority to review permissions but the service jobs don't report any errors running this procedure since the service jobs are connected using QSECOFR.
Realistically, I or other user don't need to continue to create this procedure once created. I would recommend checking for the existence first. If it ever comes to pass that this toll needs to no longer use QSECOFR as the initial service job profile, you will need to use the GRANT SQL statement to allow others to use the procedure.
I tried to run the procedure using ACS RSS under my authorities and I get SQL0440 error.
Context
Version
Code for IBM i version
2.8.0
Visual Studio Code version
1.86.2
Operating System
win32_x64
Active extensions
Auto Hide (fork) (vscode-autohide-fork): 1.0.9
Calculator (calculator): 0.1.1
Code Spell Checker (code-spell-checker): 3.0.1
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.4.0
Db2 for IBM i (vscode-db2i): 0.8.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.16.0
Excel Viewer (gc-excelviewer): 4.2.59
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.6
JSON Language Features (json-language-features): 1.0.0
Merge Conflict (merge-conflict): 1.0.0
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Overtype (overtype): 0.5.0
Partial Diff (partial-diff): 1.4.3
RPGLE (vscode-rpgle): 0.26.2
Rainbow CSV (rainbow-csv): 3.11.0
TODO Highlight (vscode-todo-highlight): 1.0.5
Text Marker (Highlighter) (text-marker): 1.11.0
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
undefined (indent-rainbow): 8.3.1
[
{
"command": "/QOpenSys/usr/bin/qsh",
"code": 1,
"stderr": "CPC7301: File QSQLSRC created in library QTEMP.\nCPC7303: File QSQLSRC in library QTEMP changed.\nCPC7305: Member GETNEWLIBL added to file QSQLSRC in QTEMP.\nSQL0551: Not authorized to object GETNEWLIBL in ILEDITOR type *PGM.\nSQL0551: Not authorized to object GETNEWLIBL in ILEDITOR type *PGM.\nSQL9010: RUNSQLSTM or RUNSQL command failed.",
"cwd": "/"
}
]
The text was updated successfully, but these errors were encountered:
I am receiving this error now...
![image](https://private-user-images.githubusercontent.com/1353665/312900502-3d5cded1-48e0-4cd4-bcda-d13e3ad53860.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyMDU2ODksIm5iZiI6MTcyMDIwNTM4OSwicGF0aCI6Ii8xMzUzNjY1LzMxMjkwMDUwMi0zZDVjZGVkMS00OGUwLTRjZDQtYmNkYS1kMTNlM2FkNTM4NjAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDVUMTg0OTQ5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzMzNDQyMWU0MGQxYmIxNmQyZDYxNjI2NDFmNDUxMjQ1NWNjNThhMWM5YTI1YTRkNThlMzFmMWRlYTJiYWNiYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.zoJ8meKa31WBJ2osbllxIpBsRrFNPCkZqX7p8RMGxfg)
The SQL procedure was defined by a contract programmer from Profound Logic. I don't have authority to review permissions but the service jobs don't report any errors running this procedure since the service jobs are connected using QSECOFR.
Realistically, I or other user don't need to continue to create this procedure once created. I would recommend checking for the existence first. If it ever comes to pass that this toll needs to no longer use QSECOFR as the initial service job profile, you will need to use the GRANT SQL statement to allow others to use the procedure.
I tried to run the procedure using ACS RSS under my authorities and I get SQL0440 error.
Active extensions
Remote system
Enabled features
Shell env
Variants
Errors
The text was updated successfully, but these errors were encountered: