Large file-disc read error

[ss123mercator]

We are using 6.5.2 in a W2k environment. Running into files size issues. Both EDI/X12 and flat.

I have a 100mb x12 file that gets mapped to another file, aprox 65mb and then ftp output to Mainframe.
while trying ftp to mainframe, errors are coming, like disc read error, not enough memory.

server had enough resources 2.4ghz, 2.5gb ram, 130gb free.

Could anybody help please.....urgent.

ss123.

 

[BocaBurger]

Would need to see FTP trace. Is this Event Server? How many maps were running? Would need to see actual error logs.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[ss123mercator]

Thaks for your response, it wont create full trace bec' it is first card it self, in trace it shows only card reader,even in launcher file also, I saw all properties in mercator.ini.

The challenge is thru ftp to Mainframe.

 

[mjnaaktgeboren]

I am not sure I totally understand the error, but if you are saying it's running out of space on the mainframe, I have gotten around something like this in the past by pre-allocating and appending to the file on the mainframe.

 

[BocaBurger]

You state "errors are coming, like disc read error, not enough memory." Where do you see these errors? In what logs?
This looks like it should be reported to Ascential Support, there were issues with the 6.5.2 FTP adapter and there are patches available.


BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[ss123mercator]

Thanks guys, I forwarded to Ascential technical support, but no word yet from them, they r also facing same challenge..so they sent it to engineers there.

any way I appreciate your cooperation.

ss123mercator.

 

[eyetry]

The problem I've noted here is that the product tends to used resources in an exponential fashion. So, map design issues can cause problems with available resources. Things I look for that may help you...

Minimize the amount of data passed to Functional maps.

Use Burst mode for flat files (doesn't seem to be as help full with EDI/X12)

People play Page Size and Count too.

When dealing with files that can range in sizes above 25mb, do not pass data from map 'A' to 'B'. Pass data addresses when possible.

Using a control map you can minimize the number of concurrent maps consuming resources. Map 'A' can tell Map 'B' where to get and put data as well as what to call the output. When map 'B' is complete and return code indicates success Map 'A' can execute Map 'C' the same way. (May not always be the most effective method either. But you need to play with diff options till you find one that works for you)

Hope these thoughts help.

eyetry

 

[BocaBurger]

EDI can be bursted, if you pre-process, and depending on what is in the transmission. If you have header, details trailer, you can break this into three files, map 2 gets all three and bursts on detail input.
There are many map and event server tuning options, the problem is that there are so many variables that support can only point out where to look and make some suggestions based on experience and some internal tests. Many issues are so system specific that the particular problem only occurs on one server, and the customer can't even reproduce on their test box.


BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[eyetry]

Don't see any conflict between what we've stated. Although, EDI/X12 as I used it referred to HIPAA X12 structures as oppossed to EDI in general. Regardless, you should be able to burst with all file formats X12 or not.

As you stated there are other factors. Like what's happening on the machine while it's running the map. Were resources being shared?

eyetry