You could also set up the job that creates the CSV to perform the conversion
before shipping the file:

https://ccrma.stanford.edu/~craig/utility/flip/

Axton Grams

On Fri, Aug 19, 2011 at 7:47 AM, Brian Gillock <arslist2...@gmail.com>wrote:

> ** I'm sure you've thought of and discarded this, but just in case...A
> crude method would be a script kicked off by a cron job prior to import.
>
> On Thu, Aug 18, 2011 at 10:50 AM, William Rentfrow <
> wrentf...@stratacominc.com> wrote:
>
>> ** **
>>
>> We have a Windows system that stores some data - we are going to bring
>> that data into the CMDB.
>>
>> The process goes something like this:
>>
>> 1.) Windows job creates CSV
>> 2.) Automated process pushes file to Linux box
>> 3.) AIE Imports file
>> 4.) Reconciliation, etc….
>>
>> What I am not sure of is how to deal with the DOS > Unix ascii conversion
>> when this is automated.  I normally run the unix command "dos2unix" on CSV
>> files prior to AIE imports.  BMC has advised us this is necessary for AIE
>> imports to work, and it is in line with everything else on *nix that needs
>> DOS ascii files converted.
>>
>> But this can't be an unusual problem - so has anyone else dealt with this?
>>
>> William Rentfrow
>> Principal Consultant, StrataCom Inc.
>> wrentf...@stratacominc.com
>> Blog: *www.williamrentfrow.com*
>> O 715-592-5185
>> C 715-410-8056
>> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>
>
> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to