|
First of all, this looks like a support contract issue. Did they have a PTF for this? I can't think of any system values, class restrictions, temp storage restrictions, or anything else that might be causing this. Second, could you write a ftp script file for her that would get the file using FTP instead of client access? I assume that she could always store the CPYSPLF into the same disk file? If you assistance with the ftp scripting, call me. manske@pconline.com on 08/18/99 11:11:57 AM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: Fax to: Subject: Client Access file transfers locking - V4R4 I was wondering if I am alone in this situation - I am on V4R4, cum C9229440 and latest patches for the PC on both CA V4R4(express - SF57098) and V3R2(normal - SF57002). I have a "power-user" doing file transfers of her print-out to a text file on the PC for sending out to other government entities. She copies the spool file to a source physical file, this file as 7,081 lines, she then does the CA file transfer, it gets to record 3,483 and just stops; causing a dump to qezdebug outq.. MESSAGE ID- MCH0601 MESSAGE FILE- QCPFMSG LIBRARY- *LIBL SEVERITY- 40 MSGTYPE- 0F SENDING- .PROGRAM- QZDASQLL IBRARY- QIWS .INSTRUCTION- 1CEEE RECEIVING- .PROGRAM- QZDASQL LIBRARY- QIWSS .INSTRUCTION- 1CEEE MESSAGE- Space offset X'00000000' or teraspace offset X'0000000000000000' is outside current limit for object DASERVER_SPACE0001 And for a real interesting tid-bite, If I have her split the member up into three smaller ones sized as 3,400 lines, 3,600 lines and 81 lines and do the transfer as create, then append the last two members; it works (going over the previous 3,483 stop) Is there a record limit; is there a "better" way to allow the users to do this without taking too much of my time for "training" Thank you for the suggestions and help; and hope this gives everyone another heads up on V4R4 Mark A. Manske Sr. Project Lead +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.