Spool Files after Exit VS Code - Debugger?
After I exit VS Code on PUB400 I get two spool files:
Maybe left over debugging code? (Not a major issue, just unexpected.)
JOBSQL looks like this:
Object name...............*JOB
Object type...............
CRTSQL***
PGM( Ø / )
SRCFILE( / )
SRCMBR( )
COMMIT(*NONE)
OPTION(*SYS *EXTIND *PERIOD)
TGTRLS(*PRV)
ALWCPYDTA(*OPTIMIZE)
CLOSQLCSR(*ENDPGM)
DECRESULT(31 31 0)
STATEMENT TEXT CCSID(13488)
STATEMENT NAME: 0000000001
CALL QSYS/QCMDEXC('ADDLIBLE LIB(LENNONS1)', 0000000022.00000)
STATEMENT NAME: S16395700002000003
CALL QSYS/QCMDEXC('ADDLIBLE LIB(LENNONSB)', 0000000022.00000)
STATEMENT NAME: 0000000003
CALL QSYS/QCMDEXC('ADDLIBLE LIB(QGPL)', 0000000018.00000)
STATEMENT NAME: 0000000004
CALL QSYS/QCMDEXC('ADDLIBLE LIB(QTEMP)', 0000000019.00000)
STATEMENT NAME: 0000000005
CALL QSYS/QCMDEXC('ADDLIBLE LIB(QIWS)', 0000000018.00000)
* * * * * E N D O F L I S T I N G * * * * *
QPJOBLOG looks like this:
CPD0032 Diagnostic 30 11/13/23 01:11:56,008501 QCARULE QSYS 0832 QC2SYS QSYS *STMT
--
From user . . . . . . . . . : LENNONS
To module . . . . . . . . . : QC2SYS
To procedure . . . . . . . : system
Statement . . . . . . . . . : 13
Message . . . . : Not authorized to command ENDTRC in library *LIBL.
Cause . . . . . : An attempt was made to access a command without adequate
authority. Recovery . . . : Obtain authority from the security officer or
the command owner, and then try the command again.
CPF0001 Escape 30 11/13/23 01:11:56,008510 QCADRV2 QSYS 0544 QCMDEXC QSYS 012F
From user . . . . . . . . . : LENNONS
Message . . . . : Error found on ENDTRC command.
Cause . . . . . : The system detected errors in the command. Recovery . . .
: See the previously listed messages in the job log. Correct the errors
and then try the command again. *N instead of a command name means that the
name had not been determined before the error was found.
CPD0032 Diagnostic 30 11/13/23 01:11:56,008705 QCARULE QSYS 0832 QC2SYS QSYS *STMT
From user . . . . . . . . . : LENNONS
To module . . . . . . . . . : QC2SYS
To procedure . . . . . . . : system
Statement . . . . . . . . . : 13
Message . . . . : Not authorized to command DLTTRC in library *LIBL.
Cause . . . . . : An attempt was made to access a command without adequate
authority. Recovery . . . : Obtain authority from the security officer or
the command owner, and then try the command again.
CPF0001 Escape 30 11/13/23 01:11:56,008712 QCADRV2 QSYS 0544 QCMDEXC QSYS 012F
From user . . . . . . . . . : LENNONS
Message . . . . : Error found on DLTTRC command.
Cause . . . . . : The system detected errors in the command. Recovery . . .
: See the previously listed messages in the job log. Correct the errors
and then try the command again. *N instead of a command name means that the
name had not been determined before the error was found.
CPD0039 Diagnostic 30 11/13/23 01:11:56,008869 QCARULE QSYS 0832 QC2SYS QSYS *STMT
From user . . . . . . . . . : LENNONS
To module . . . . . . . . . : QC2SYS
To procedure . . . . . . . : system
Statement . . . . . . . . . : 13
Message . . . . : Command ENDDBG not valid in this mode.
Cause . . . . . : The command is not valid in the current mode of operation.
-=* http://pub400.com *=-
⚠️ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠️
| Context | Version |
|---|---|
| Code for IBM i version | 2.4.0 |
| Visual Studio Code version | 1.84.1 |
| Operating System | win32_x64 |
Active extensions
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.4.0
Db2 for IBM i (vscode-db2i): 0.5.2
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.15.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitLens — Git supercharged (gitlens): 14.4.1
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
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
WSL: Recommender (remote-wsl-recommender): 0.0.19
Remote system
| Setting | Value |
|---|---|
| IBM i OS | V7R5M0 |
| Tech Refresh | n/a |
| CCSID | 37 |
| SQL | Enabled |
| Source dates | Disabled |
Enabled features
| /QOpenSys/pkgs/bin | /usr/bin | /QSYS.lib/LENNONS2.lib | /QSYS.LIB | /QIBM/ProdData/IBMiDebugService/bin |
|---|---|---|---|---|
| bash | attr | GENCMDXML.PGM | QZDFMDB2.PGM | startDebugService.sh |
| chsh | iconv | GETNEWLIBL.PGM | ||
| git | setccsid | |||
| grep | ||||
| ls | ||||
| md5sum | ||||
| sort | ||||
| stat | ||||
| tar | ||||
| tn5250 |
Shell env
BUILDLIB=LENNONSB
CURLIB=LENNONSB
HOME=/home/LENNONS
HOST=pub400.com
IFS_LIB=LENNONSB
IFS_SRCPF=VSCODE
LIB1=LENNONSB
LIBLS=LENNONS1 LENNONSB QGPL QTEMP QIWS
LOGIN=lennons
LOGNAME=lennons
MAIL=/var/spool/mail/lennons
OLDPWD=/home/LENNONS
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/LENNONS
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=71.63.120.199 53460 2222
SSH_CONNECTION=71.63.120.199 53460 185.113.5.134 2222
TZ=<UTC>0
USER=lennons
USERNAME=lennons
_=/QOpenSys/pkgs/bin/env
Variants
{
"american": "#@$",
"local": "#§$"
}
Errors
[
{
"command": "system \"CRTLIB LIB(LENNONS2) TEXT('Code for i temporary objects. May be cleared.')\"",
"code": 255,
"stderr": "CPD0032: Not authorized to command CRTLIB in library *LIBL.\nCPF0006: Errors occurred in command.",
"cwd": "/home/LENNONS"
},
{
"command": "system \"DLTOBJ OBJ(LENNONS2/O_*) OBJTYPE(*FILE)\"",
"code": 255,
"stderr": "CPF2125: No objects deleted.",
"cwd": "/home/LENNONS"
}
]
JOBSQL is not debug related. QPJOBLOG contains a command "ENDDBG" that is part of system debug, which the IBM i debug service depends on. If QPJOBLOG does not exist before your vscode session, and it exists after exiting from vscode, then it could be generated by the low level system debug code.
@mkwan01 @worksofliam If I:
- Delete all my spool files.
- Start VS Code
- Connect to PUB400.COM
- Still see no spool files
- Immediately exit VS Code and the spool files turn up.
JOBSQL is the output of a PRTSQLINF command issued by someone.
Removing the debug label, as debugger is not involved in the above scenario.