LJ, I see your point, but the good news is that there's no reason that you couldn't copy the mapping files to the server, manually edit them to remove the line feeds, and run arimportcmd from there. It's the .csv files that are constantly changing, not the .arm files. They should be static enough to make this process almost one-time.
Rick On Thu, May 8, 2008 at 11:05 AM, LJ Longwing <[EMAIL PROTECTED]> wrote: > ** I just got done working with BMC regarding a mapping problem and I'm > not liking their answer. I wanted to poll the community to test the waters > for this in case I need to open an RFE to make things work the way they say > they are supposed to work > > I created an ARM file from the windows tool, just like the docs say to, > and transferred it to a Suse Linux box, and couldn't get the arimportcmd > tool to work properly, after several back and forths with support, they gave > me a 'working' arm file, after several hours of trying to figure out what > the difference was, I came down to the fact that for the Linux version of > the import tool you need to run a dos2unix conversion (remove the hex 0D > from the CRLF). When I commented that I shouldn't need to run any > conversions on the ARM I was told point blank that the difference between > how windows and Unix store text files is beyond BMC's support realm and that > I simply needed to perform the conversion myself. My problems with this are > several, but the major one of which is that the documentation states > > > Importing with mapping refers to running the BMC Remedy Import CLI by > using > > a mapping created in BMC Remedy Import. The mapping must be created on > > Windows because that is the only environment BMC Remedy Import runs on > > interactively. After it is created, the mapping can be used on any > platform. > > I take this to mean that I don't need to convert anything to use it, > because it 'can be used on any platform'....I'm curious if anyone on HPUX or > AIX has to go through this conversion, and if so, did you figure it out on > your own or did you get told this by support, and is anyone else annoyed > about the fact that the documentation is misleading at best, and completely > wrong at worst. I think that at a minimum they should either create the > file so it's readable on all platforms they support, or update the > documentation to indicate that some type of conversion needs to be performed > to be able to use it on non Windows platforms. > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
