Calling All Perl Developers - Issue Vachindi...will Pay $100 If Solved

[edisav_edava]

common gusa gusa....

oka chinna issue naaku telisi....naaku perl raadhu kabatti aduguthunna....the issue may not take more than 45 mins...kani its very valuable anamata...


this thing might involve coding as well as good knowledge about modules, etc etc

[ICANWIN]

Issue ento cheppu asalu so that some one can help...

[mrudhula99]

naku koncham idea undhe...

post cheyyee .. naku thelesthee chepthaanu

[pawanism]

[quote name='edisav_edava' timestamp='1350615451' post='1302654054']
common gusa gusa....

oka chinna issue naaku telisi....naaku perl raadhu kabatti aduguthunna....the issue may not take more than 45 mins...kani its very valuable anamata...


this thing might involve coding as well as good knowledge about modules, etc etc
[/quote]


What is the issue let me know if i can i will try to do.

[edisav_edava]

For the last few months, we have been facing issues with a Perl script.
There are 2 files downloaded by a same perl script but with different versions of Perl.
We have two different versions of Perl over here. Below are the details of the Active Perl versions:

[b]Newer Version: (Downloaded file has an error)[/b]
Active Perl 5.10.0.1005
PPM Version 4.05

[b]Older Version: (Downloaded file which was correct)[/b]
Active Perl 5.10.0.1004
PPM Version 4.03

The upstream job that works on the files was working fine with the file downloaded by older version (Active Perl 5.10.0.1004), but fails when uses the file downloaded by newer version (Active Perl 5.10.0.1005)
After our troubleshooting, we found out that the file downloaded by newer version come with empty rows between data, since the .csv files came with spaces (empty rows), it is not being processed and fails.
From our end, we have to correct the file manually to process and it is a time consuming process.
There are many of scripts that fail and the issue is same.

This is a Production Issue we had been facing from past 8-9 months.

This error came out while we were migrating and testing all the scripts from old server to a new one due to Company’s Hardware Recycle Policy. We didn't have the Active Perl 5.10.0.1004 setup file, so have installed Active Perl 5.10.0.1005 in the new one. Once this issue is solved, we would migrate all the scripts left over in the old one to current production.

If you think you could help me out with that, i can create a webex session or anything

FYI: The files are downloaded from an external website, and processed by ETL tool, DataStage

[edisav_edava]

calling mrudhula & pawanism.....please respond to my request.....

[pawanism]

[quote name='edisav_edava' timestamp='1350660398' post='1302656176']
For the last few months, we have been facing issues with a Perl script.
There are 2 files downloaded by a same perl script but with different versions of Perl.
We have two different versions of Perl over here. Below are the details of the Active Perl versions:

[b]Newer Version: (Downloaded file has an error)[/b]
Active Perl 5.10.0.1005
PPM Version 4.05

[b]Older Version: (Downloaded file which was correct)[/b]
Active Perl 5.10.0.1004
PPM Version 4.03

The upstream job that works on the files was working fine with the file downloaded by older version (Active Perl 5.10.0.1004), but fails when uses the file downloaded by newer version (Active Perl 5.10.0.1005)
After our troubleshooting, we found out that the file downloaded by newer version come with empty rows between data, since the .csv files came with spaces (empty rows), it is not being processed and fails.
From our end, we have to correct the file manually to process and it is a time consuming process.
There are many of scripts that fail and the issue is same.

This is a Production Issue we had been facing from past 8-9 months.

This error came out while we were migrating and testing all the scripts from old server to a new one due to Company’s Hardware Recycle Policy. We didn't have the Active Perl 5.10.0.1004 setup file, so have installed Active Perl 5.10.0.1005 in the new one. Once this issue is solved, we would migrate all the scripts left over in the old one to current production.

If you think you could help me out with that, i can create a webex session or anything

FYI: The files are downloaded from an external website, and processed by ETL tool, DataStage
[/quote]


sent you message