error: Couldn't get handle: Failure

ROB124 · Post by **ROB124** » Thu Jun 17, 2010 9:03 pm

When trying to do a put from PC to ZOS I get the error
error: Couldn't get handle: Failure

this works>>>>>>>>>>
//CSS18>put routes.txt
Uploaded H:\routes.txt to //CSS18/routes.txt (2.9kB 2.9kB/s 00:00:01)

These don't>>>>>>>>>>>>>>>>>
//CSS18>put routes.txt routes.text
error: Couldn't get handle: Failure
//CSS18>put routes.txt //css18.routes.text
error: Couldn't get handle: Failure
//CSS18>put routes.txt ROUTES.TEXT
error: Couldn't get handle: Failure
//CSS18>put routes.txt //CSS18.ROUTES.TEXT
error: Couldn't get handle: Failure
//CSS18>

However the file gets created just no data is transferred.

ROB124 · Post by **ROB124** » Thu Jun 17, 2010 10:52 pm

I have created a batch file with the following commands.

ls /+lrecl=133
put h:\sftpprint.txt //css18.user.sftprint

and it works
Enter password for css18@mvs1:
//CSS18>ls /+lrecl=133
/+lrecl=133
//CSS18>put h:\sftpprint.txt //css18.user.sftprint
Uploaded h:\sftpprint.txt to //css18.user.sftprint (102.4kB 102.4kB/s 00:00:01)
//CSS18>

Post by **dovetail** » Fri Jun 18, 2010 8:44 am

The Co:Z SFTP server error log will have more detailed messages for these failures.

See this for more information:

http://dovetail.com/docs/sftp/using.htm ... _error_log

ROB124 · Post by **ROB124** » Sun Jun 20, 2010 6:59 pm

DatasetHandler: Error in fopen(//DD:SYS00008, wb,type=record,noseek,recfm=*) - EDC5047I An invalid file name was specified as a function parameter. (errno2=0xC00B
ZosDataset: Dataset CSS18.ROUTES.TEXT open error: EDC5047I An invalid file name was specified as a function parameter. (errno2=0xC00B0283)
ZosDataset: last_op=601, error=0x5620062, msg=

Post by **dovetail** » Thu Jul 08, 2010 4:08 pm

Were there any messages in the joblog or syslog for this failure?

I'm not sure why you are getting this error code from the IBM C library fopen() function (0xC00B0283). If you try to look up this errno2 code with bpxmtext, you will find that it is not documented, therefore if this problem persists you will unfortunately need to open a problem with IBM to determine the cause.

If you turn on tracing logging in the Co:Z SFTP server, you will get more information in the error log including the BPXWDYN allocation command used to allocate the DD, which might be helpful.

Code: Select all

sftp> ls /+loglevel=T
sftp> ls /+lrecl=133,recfm=vb
sftp> put myfile //HLQ.NEW.DSN
sftp> get /+error.log   trace.log