Re: Back for another VS Code setup

I moved my id_rsa from a working IBM i to this new customer and it's
working now. But I am seeing the disconnect at the end using SSH as well. I
suspect this is a PTF issue or something related. Log from VSCODE

/home/user/: LC_ALL=EN_US.UTF-8 system "call QSYS/QZDFMDB2 PARM('-d' '-i'
'-t')"
CREATE TABLE QTEMP.O_NHQDK AS (with SSH_DETAIL (id, iid) as ( select
substring(job_name, locate('/', job_name, locate('/', job_name) + 1) + 1,
10) as id, internal_job_id as iid from qsys2.netstat_job_info j where
local_address = '0.0.0.0' and local_port = 22 ) select
DEFAULT_CCSID, CCSID from table(QSYS2.ACTIVE_JOB_INFO( JOB_NAME_FILTER =>
(select id from SSH_DETAIL), DETAILED_INFO => 'ALL')) where INTERNAL_JOB_ID
= (select iid from SSH_DETAIL)) WITH DATA;
Call QSYS2.QCMDEXC('CPYTOIMPF FROMFILE(QTEMP/O_NHQDK *FIRST)
TOSTMF(''/tmp/vscodetemp-O_azr2Uw74'') MBROPT(*REPLACE) STMFCCSID(1208)
RCDDLM(*CRLF) DTAFMT(*DLM) RMVBLANK(*TRAILING) ADDCOLNAM(*SQL)
FLDDLM('','') DECPNT(*PERIOD)')
{
"code": 4,
"signal": null,
"stdout": "DB2>\n\n **** CLI ERROR *****\n SQLSTATE:
42601\nNATIVE ERROR CODE: -104\nToken INTERNAL_JOB_ID was not valid. Valid
tokens: FOR USE SKIP WAIT WITH FETCH LIMIT ORDER UNION. \nDB2>\n ?>\n\n
**** CLI ERROR *****\n SQLSTATE: 38501\nNATIVE ERROR CODE:
-443\nCopy command ended because of error.",
"stderr": "/home/ARTCCA//.bashrc: line 1:
$'\\205\\247\\227\\226\\231\\243@\\327\\301\\343\\310~\\177a\\210\\226\\224\\205a\\201\\231\\243\\203\\203\\201z[\\327\\301\\343\\310\\177\\r%':
command not found"
}



On Fri, Jun 6, 2025 at 11:09 AM Art Tostaine, Jr. <atostaine@xxxxxxxxx>
wrote:

Thanks for the suggestions so far. Still the same thing using SSH. I was
able to connect using my user profile but right when it's done with all the
connection popups vs code disconnects.

On Fri, Jun 6, 2025 at 10:51 AM Diego E. KESSELMAN <
diegokesselman@xxxxxxxxx> wrote:

Hi,

just a suggestion: don't use 755 for your /home/<User Profile>
directory, because will ask for password.

Try with 700:

chmod 700 /home/<user directory>


Also fix files with owner different to yours:

chown -R <User Profile> /home/<User Profile>


And finally, check the
*/QOpenSys/QIBM/UserData/SC1/OpenSSH/etc/sshd_config* file.

* Last line should looks like this:
ibmpaseforienv PASE_USRGRP_LIMITED=N

* To speed up logins, change the UseDNS value:
UseDNS no

*Check you have this value:
PubkeyAuthentication yes

* If your user is *SECOFR , set this value:
PermitRootLogin yes

* Now restart your service:

ENDTCPSVR *SSHD
STRTCPSVR *SSHD

* Try again to login


Hope this can help you

--
Saludos/Regards

Diego E. KESSELMAN

On 06/06/25 08:29, Sizer, Joseph via MIDRANGE-L wrote:

I recently applied some PTFs and had to redo some authorities.

You can try

chmod 755 /home/<user directory>

chmod 755 /home/<user directory>/.ssh

chmod 600 /home/<user directory>/.ssh/authorized_keys


-----Original Message-----
From: MIDRANGE-L<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

Art Tostaine, Jr.

Sent: Friday, June 6, 2025 10:25 AM
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Back for another VS Code setup

________________________________
CAUTION: This email originated from outside of the PENCOR network. Do

not click on any links or open attachments unless the sender is known, and
the content is verified as safe.

________________________________

I can connect with iACS SSH Terminal to my IBM i. VS code fails

immediately.

I've placed the key in my home/user/.ssh, added it authorized.keys,

code page 437. I have all authorizations turned on for that file now.

Are there any logs I can look at on IBM i? Copilot offered to analyze

my vs code logs and showed these errors:

-What happened?
The SSH connection was established and you were prompted for a password.
Authentication succeeded, but after the "ready" message, the connection

hung and timed out after about 17 seconds.

I don't think I should be prompted for a password. The customer box is

V7R3. I'm off to check if any PTF's required.

Any suggestions appreciated.

Thank you, Art
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,

visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives athttps://

archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.