[U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Rajesh Menon
Does anyone knows what is happening here: I am trying to open a text file (over 4Gb) using OPENSEQ and storing the file variable into a array as follows: COMMON /MYPROG/ FILEVARS(10) OPENSEQ /tmp/file.txt to FILEVARS(1) ELSE ... This operation results abnormal termination with fault type error

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Perry Taylor
Just for giggles... what happens if you... OPENSEQ '/tmp/file.txt' TO FV.TEMP ELSE ... FILEVARS(1) = FV.TEMP ?? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rajesh Menon Sent: Monday, May 17, 2010 2:56 PM To:

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Dan Goble
You may want to check with your Systems Administrator to be sure your file system is setup to support files larger than 2gig - Original Message - From: u2-users-boun...@listserver.u2ug.org u2-users-boun...@listserver.u2ug.org To: u2-users@listserver.u2ug.org u2-users@listserver.u2ug.org

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Rajesh Menon
I already tried that. Same Error and the fault occurring at FILEVAR(1) = FV.TEMP line. Thanks, Rajesh -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Perry Taylor Sent: Monday, May 17, 2010 11:59 AM To: U2 Users

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Rajesh Menon
Yes file system is setup to support +2Gb files. As I mentioned I can open the file using a scalar file variable. Problem happening only with the combination of +2Gb and using array variable. Thanks, Rajesh -Original Message- From: u2-users-boun...@listserver.u2ug.org

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Buffington, Wyatt
I far as I know. The OPENSEQ statement requires both a file name and a record name. (i.e.: OPENSEQ DATA.DIRECTORY, FLAT.FILE.NAME TO F.TEMP ELSE ...) HTH -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rajesh Menon

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread jpb-u2ug
Let me see, can it be because you are trying to cram over 4 GB of data into a single cell. Unlike the OPEN statement that just puts the file variable into a variable, the OPENSEQ opens the whole file to the variable. Jerry Banker -Original Message- From:

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Marc A Hilbert
What happens wif you open to regular variable then pass it over to the array: OPENSEQ TO FVAR FILEVARS(1) = FVAR ? Regards, Marc -Mensaje original- De: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] En nombre de Rajesh Menon Enviado el: lunes, 17

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread Perry Taylor
I'd call this one a bug. I just tried the following on 10.2.7 on RHEL5... OPENSEQ '/data/trax/CLM.IDX/OVER.30' TO SEQ.TEST ELSE ABORT STATUS FS FROM SEQ.TEST ELSE ABORT CLOSESEQ SEQ.TEST CRT 'FILE SIZE = ': FS6 I get... FILE SIZE = 10146506752 But if I run...

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread John Hester
I think it's something along those lines, but I don't think it's trying to stick the entire contents of the file into a variable. What I think OPENSEQ is doing is keeping track of the position where the EOF mark is so it will know when the end of the file is reached. For a file greater than 2GB

Re: [U2] OPENSEQ and Abnormal termination of UV

2010-05-17 Thread aelwood
Normally when I run into a statement that doesn't like mv or dimmed arrays I just assign before or after Like: SEARCH.FOR = ABC1,J LOCATE SEARCH.FOR IN DEF SETTING bla bla bla or in this case OPENSEQ '/data/trax/CLM.IDX/OVER.30' TO SEQ.TEST ELSE ABORT FVARS(1) = SEQ.TEST I haven't tested this