Mainframe, MVS and zOS Discussion

Hi,

I'm from a mainframe team and we are sending across the data to other team who makes use of SeeBurger. At SeeBurger end there are problems to handle the data which is being sent across because of the size of the file. According to the SeeBurger team says that because of the files mainframe has sent across the memory utilization at their end is mostly between 25-35GB and that kills their other process and we should split the files in small chunks. Does anyone have work experience with SeeBurger, I might be able to explain it furhter then.

So what's the problem with the mainframe splitting the data into multiple transmissions? If the other side can't handle what you're sending, adjustments seem to be necessary. And knowing ANYTHING about Seeburger doesn't really add to that understanding.

Before we send across the final file before that we have nearly 6 steps to execute along with the one which does the character conversion as described in this post: viewtopic.php?f=35&t=3291. This conversion program is CPU intensive program and we are sending this file every 15 minutes. And there are so many jobs (300+) which will have changes in these 6*300+ jobs. That change is not accepted by the operation's team. This is the reason we have not done that yet.

Conversion from one code page to another is a CPU-intensive process, period. The system is having to look at each character of each record for the data set and look up the replacement character -- which is a LOT of work.

And you may need to engage your management with the concept that Seeburger may need to be replaced with another vendor if they cannot handle the volume of data you're passing -- if the operations team cannot or will not split the jobs.

Thanks Robert.

We have convinced the Seeburger team to look in to this. They might reply back to us.