|
Dan: Try the WRKLNK command to see "objects" in the IFS. Can you FTP the file to your PC to look at it? cjg Carl J. Galgano EDI Consulting Services, Inc. 550 Kennesaw Avenue, Suite 800 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@ediconsulting.com http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight FREE AS/400 Timesharing Service - http://www.ediconsulting.com/timeshare.html "You ain't gonna learn what you don't want to know" - rw -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com] On Behalf Of Dan Bale Sent: Friday, May 17, 2002 10:27 AM To: midrange-l@midrange.com Subject: QOpenSys access at v3r2/win98 Environment: OS/400 v3r2, CA v3r2, Win98SE I have an app that uses CPYTOSTMF to put a file in QOpenSys. Once I mapped a drive to that folder, Windoze Exploder shows the file. I try to copy it to my C: drive. Get an error w/ dialog box titled: "Error Copying File" and a message: "Cannot copy file: File system error (1026)." Then I tried double-clicking on the file (an .RTF file), and Windoze Exploder locked up solid. Any ideas on how to fix this? Is there a "Work With Objects" type of command for objects in the IFS that are not in the native QSYS.LIB file system? Also, (probably unrelated to error), the app that does this is about 3 years old and I have used it successfully in the past on v3r2 systems. I have a comment in the CL that "StmFCodPag(*PCAscii) not valid for V3R2, so substitute value calculated on OS/400 version that _did_ support *PCAscii." The live code in the CPYTOSTMF uses "StmFCodPag( 1252 )". How did I come up with 1252? Is that a typical/standard code page for ASCII? TIA. - Dan Bale (I am *NOT* "Dale" http://archive.midrange.com/midrange-l/200105/msg00281.html ) SAMSA, Inc. 989-790-0507 DBale@SAMSA.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.