Jump to content


Photo
- - - - -

core dump with external record format files


4 replies to this topic

#1 Luke

Luke

    Newbie

  • Members
  • Pip
  • 4 posts
  • Gender:Male

Posted 10 March 2006 - 03:56 PM

Hi guys

have a problem with a client site running an archaic version 4 of native (green screen) pro-iv on sco unix (I believe).

Basically they are running a process in batch which starts by clearing down an external record format file using the Clear flag (it's just a text file), then at the end of the process ends up writing to the file, however as soon as it attempts to write it core dumps.

Apparently the same problem has been experienced before, and was tracked down to "ownership of the sequential file" (this is the only info given in the call log - very helpful!), and they solved the problem by deleting and recreating the file, (which I have done using rm and touch, even did chmod 777 to make sure it's writeable), but this didn't seem to make any difference, ran through the process again and got the same core dump at the same point

the file def has Y on external record format and a file format of SEQ

Has anyone encountered a similar problem or can think of any possibilities as to what the problem may be? Currently I'm really struggling as we are unable to recreate the problem on our development box :). I'm also perplexed as to why it can clear the file down no problems, but as soon as it attempts to write to it I get a dump

cheers for any help

Edited by Luke, 10 March 2006 - 03:58 PM.


#2 Lewis Mccabe

Lewis Mccabe

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 455 posts
  • Gender:Male
  • Location:Sarasota, Florida

Posted 12 March 2006 - 07:07 PM

Years ago we ran into trouble when clearing text files. Ultimately did system call to simply recreate empty file. Then we ran into trouble as to when in the timing cycle we recreated the file. Problem solved when we recreated in a separate function (not global) and then called the batch process. Regarding permissions: If I remember correctly (it's been a while), nulling umask before creation and recreation was all we needed.

Lew

#3 Luke

Luke

    Newbie

  • Members
  • Pip
  • 4 posts
  • Gender:Male

Posted 13 March 2006 - 12:39 PM

Thanks for the reply Lew. Yeah, currently the 1st update reads all the files with clearflag = 'Y' - which incidentally still seems to be working, it's not until we try come write to the file in a later function that we get a problem. Have tried manually deleting and recreating the file with chmod 777 before starting the process, but got the same problem.

I could understand the problem if it was something that wasn't working previously, but it's worked fine like this for years. I may try simply deleting the file manually and allowing the process to recreate it, to see if this makes any difference.

just about driving me potty this one :mad:

#4 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 13 March 2006 - 03:31 PM

Luke,

I think there is an issue if you create an external file more than once in one function.

I don't know if this might be your issue...

hth,

Joseph

#5 Luke

Luke

    Newbie

  • Members
  • Pip
  • 4 posts
  • Gender:Male

Posted 14 March 2006 - 01:05 PM

Joseph

cheers for the reply, I'm going to take the clear flag out of the function to see if that helps at all.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users