Speaking of upgrading to 6.5 Exp 2....

This past weekend we did the same and ran across an FTP issue. Some of our
jobs used the GET command with a buildparms and if the command syntax did
not include the remote-file name it would burp back that the file or
directory did not exist...

 Remote system type is UNIX
 ftp> get KEY9000;REC=-207,,F,ASCII
 200 PORT command successful.
 550 KEY9000;REC=-207,,F,ASCII: No such file or directory.
 Data Transfer Request Failed.  (FTPERR 13)
 ftp> exit
 221 Goodbye.

A simple change to the command and all is well......

ftp> get KEY9000 KEY9000;REC=-207,,F,ASCII


Gotta love these little gotcha's!



Rick 'downloading latest FTP patches' Clark
Systems Manager
Weltman, Weinberg & Reis
Cleveland, Ohio



**Confidentiality Notice**

This e-mail and the documents accompanying this transmission contain
confidential information belonging to the sender which is legally
privileged. The information is intended only for the use of the individuals
or entities named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying, or distribution or the taking
of any action in reliance on the contents of this e-mailed information is
strictly prohibited. If you have received this e-mail in error, please
immediately notify the sender by e-mail at the address above. The
transmission is to be deleted and any items that may have been printed are
to be destroyed. Thank you for your compliance.


> -----Original Message-----
> From: Mark Sprowls [mailto:[log in to unmask]]
> Sent: Monday, January 21, 2002 11:57 AM
> To: [log in to unmask]
> Subject: [HP3000-L] ODBC Locks on MPE 6.5 Exp 2
>
>
> Over the weekend we upgraded to MPE 6.5 Express 2. We have a
> phone system
> which takes account numbers from callers and places them into an Image
> database via HP's ODBC. Since the upgrade, our phone reps can
> no longer use
> the system. It appears that the PC application writing to the Image
> database keeps the records locked once they are written. When the user
> attempts to access/update the dataset, their session locks
> up. The session
> can not be aborted and resetting the terminal through TERMDSM does not
> work. The only solution seems to be aborting the ODBC
> listener job. The
> system has been working fine for quite some time, and no
> other changes were
> made. Does anyone have any idea why ODBC wants to keep the
> records locked
> or what I can do to prevent this?
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *