|
Depending on your company it can be hard to get projects approved tochange code that works when there are other more pressing projects that need
Paul Nelson
Scott
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Thursday, January 05, 2017 2:38 PMIBM i 7.3?
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Really? There's still people using the QDLS file system on
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_support_docv
Yes, they are. The one client still using it (V7R1) sends thousands of
invoices a day over a secure connection to RR Donnelly for printing and
mailing.
I quit suggesting that they migrate into the 21st century.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, January 05, 2017 1:48 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Really? There's still people using the QDLS file system on IBM i
7.3?
1. IBM i 7.3
- TITLE: Cannot Save Files From Office In QDLS With SMB2 Enabled
- URL:
S2D&mynp=OCSWG60&mync=E&cm_sp=ibmi-_-OCSSTS2D-OCSWG60-_-E
- ABSTRACT: Users trying to save a file from Microsoft Office to a share
in the QDLS file system will get an error, "Document not saved".
I could maybe see this if they were using some crappy vendor package which
insisted on using QDLS because the vendor won't spend time upgrading (like
changing from CPYTOPCD to CPYTOIMPF).
But for general "let's use IBM i to do file serving" and still use QDLS?
To me that's like dropping a turd sandwich in the user's mouth because of
the 8.3 file naming alone. All the users will be thinking "that crappy
AS400 only supports the old 8.3 file naming". Just remap it and it over
with!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.