There are two places you can set up the .ssh directory with the
known_host file and a user key file.
I cannot remember the general location but if you google .ssh you should
find it. Anyhow the client first looks at current directory for a .ssh
sub-directory. If it is not found it tries to create it.
What is the home directory of the user profile you are logging on /
running the QSH command under? Does the profiles home directory exist
and have the ability to create / change files? Find the .ssh that
should be under the home directory of TSU8V5S6 and copy it to the home
directory of the user you need to run the job under.
If that does not help, I will search for my instructions for setting up
a ssh user and post them.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Versfelt, Charles
Sent: Thursday, April 29, 2010 8:28 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: You don't exist.
Scott,
Thank you for the ADDENVVAR solution. It got me past the "You don't
exist" error.
This was followed by an error, and subsequently trying different things
gave me different errors.
I hope you can help. Details below.
Thanks,
Charlie
1. First, I got this:
Connecting to xxx.xxx.xx.xxx...
Could not create directory '/home/MRPVER/.ssh'.
Host key verification failed.
Connection closed
Press ENTER to end terminal session.
Regarding that error... I'm not sure why it would get an error trying to
create a directory?
The user ID I'm running this under is MRPVERSFEL.
Does it always take the first six bytes of the User ID and create a
directory?
Can I expect such an error for any User ID I run this under?
Will I have to create such a directory for any User Ids that access this
function?
2. I tried manually creating the directories, and then, got this error.
Connecting to 151.151.65.203...
Host key verification failed.
Connection closed
Press ENTER to end terminal session.
My understanding is that our Operations Manager set up the Host Keys.
I'm not sure why I would be getting the "Host key verification failed"
error.
I googled and found instructions for setting up the keys, but as I said,
my
understanding was that this was already done by our Operations manager.
As I said earlier, the command is
QSH CMD('/QOpenSys/bin/sftp +
-b/home/darlene/sftpcmd.txt +
tsu8v5s6@xxxxxxxxxxxxxxxx')
My understanding is that the keys were set up for user TSU8V5S6, which
was created specifically for this.
This command is running out of a CL program, so I tried something else,
just to see if it would work.
I tried calling the program in batch using a SBMJOB instead of calling
the program interactively.
I made the user for my SBMJOB USER(TSU8V5S6)
The batch job blew up.
QSH0002 received by FTPSNDECK2 at 3200. (C D I R)
Reply . . : D
The only information that appeared relevent in the dump was:
Error found with QSH session, reason code 4, errno 3489.
The joblog:
From module . . . . . . . . : QZSHQSHC
From procedure . . . . . . : SendMsg__FPcT1Pvi
Statement . . . . . . . . . : 2
Message . . . . : Error found with QSH session, reason code 4, errno
3489.
Cause . . . . . : The system detected an error with a QSH session,
reason
code 4, errno 3489. The reason codes and their meanings are as
follows: 1
Error found when starting a new QSH session. 2 - Error found when
running
an existing QSH session. 3 - Error found when ending an existing QSH
session. 4 - Error found when running a command. 5 - Unexpected
error
found. Errno is a value that indicates the type of the failure.
Recovery
. . : Correct the errors and then try the request again.
9 04/29/10 11:09:17.694416 QCLXERR QSYS 00DA QCLXERR
Q
Message . . . . : QSH0002 received by FTPSNDECK2 at 3200. (C D I R)
Cause . . . . . : Control language (CL) program FTPSNDECK2 in library
MYVERSFELT detected an error at statement number 3200. Message text
for
QSH0002 is: Error found with QSH session, reason code 4, errno 3489.
I hope you can help.
Thanks,
Charlie
------------------------------
message: 8
date: Wed, 28 Apr 2010 16:30:47 -0500
from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
subject: Re: You don't exist
Ahhh... I found what I was thinking of. Here's a discussion I had
previously about this:
http://forums.systeminetwork.com/isnetforums/showthread.php?t=74651
so you should be able to eliminate the 8-character limit by doing this
before you invoke any PASE programs:
ADDENVVAR ENVVAR(PASE_USRGRP_LIMITED) VALUE(N) REPLACE(*YES)
the variable name and value are case-sensitive, so please type them in
all uppercase as I show.
This eliminates the 8-character restriction on the userid field -- but
opens up a risk. The risk is that the software you're running in PASE
might only reserve 8 characters for userid (since that is the limit on
AIX) and therefore if you provide 10 characters, it'll overflow memory
and cause problems.
Fortunately, I don't think that's an issue with sftp. Since sftp is
cross-platform, and runs on other systems where more than 8 characters
are allowed for the userid, I doubt very much that it'd overflow memory.
So that might be a reasonable solution for you.
On 4/28/2010 4:22 PM, Scott Klement wrote:
hi Charlie,
There are two userids in use here. There's the userid on your system
(the one running the 'sftp' command) and there's also the userid used
to
log in to the remote system.
The part you are specifying on the command-line is
tsu8v5s6@xxxxxxxxxxxxxx -- that's the latter of the two. That's the
userid you'll use to log in to the remote system. It's not the
userid
of the CURRENT system.
Unfortunately, that's not where the problem is. The problem is on the
CURRENT system. sftp is looking up information about the local user
--
and it's failing, because of AIX's weird 8-character limit on userid.
So you really need to use a userid that's 8-characters long. (Use
profile swapping if necessary).
I seem to dimly remember someone telling me of another way to
circumvent
this limit (albeit with a lot of danger that it might cause problems)
but I can't remember what it was. You might be able to find it in the
archives.
Otherwise, create a userid with 8 or fewer characters, and use that.
On 4/28/2010 3:25 PM, Versfelt, Charles wrote:
Hi,
I hope someone can help...
I'm trying to do SFTP using QSH, getting the error "You don't exist,
go away..."
Connecting to xxx.xx.xx.xxx...
You don't exist, go away!
Connection closed
Press ENTER to end terminal session.
I'm actually doing it in a CL program, here's the command:
QSH CMD('/QOpenSys/bin/sftp +
-b/home/darlene/sftpcmd.txt +
tsu8v5s6@xxxxxxxxxxxxxx'<mailto:tsu8v5s6@xxxxxxxxxxxxxx'>)
I have heard that this problem occurs when the user ID is more than 8
bytes, but that by putting the user profile ID in the QSH command in
the QSH command (TSU8V5S6) in the CL program should solve that problem.
Just about all our user id's are more than 8 characters, including
the one I'm calling this program from,
but we were made to understand that by pointing it to another user
profile in the QSH command that would solve that problem.
Is that still the problem or might there be something else?
Please let me know if you can help, and if you need any more
information.
Thanks,
Charlie Versfelt
Sr. Programmer/analyst
Myron
------------------------------
midrange.com
