Author Topic: Invalid Character issue  (Read 2314 times)

DDP021

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
Invalid Character issue
« on: November 05, 2012, 04:58:56 AM »
Hi, wondering if anyone has had this issue....We are ingesting mainframe reports into CMOD...We had an instance where a character was used in the data that caused the report to fail when ingesting into ERR...In this case it was an x'47'....Apparently this is an invalid character in CMOD...The actual failure message didn't indicate that...We found it ourselves and after editing out this character, the file ingested successfully....Wondering if there are other characters that CMOD won't recognize and if there's a way to define something to 'bypass' any invalid characters so we don't have any failures?...Any help would be appreciated..Below is the failure message we received....

OnDemand Load Id = >12794-14-0-711FAA-15645-15645<
An error occurred.  Contact your System Administrator and/or consult the System Log.  File=arsadmp.c, Line=1561
Failed while attempting to load the database
Loaded 0 rows into the database

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2230
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Invalid Character issue
« Reply #1 on: November 05, 2012, 06:28:04 AM »
Hi.

The traditional way to deal with this is to create an input exit that detects the 'rogue' character, and convert it to something similar that doesn't cause trouble.  Removing tabs from TLEs, and de-accenting characters during load are two that I've helped write in the past.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

DDP021

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
Re: Invalid Character issue
« Reply #2 on: November 05, 2012, 07:04:01 AM »
Thanks Justin....This seems like something our systems area would need to do...My group supports report definitions/ accesses...No type of coding...I'm HOPING they will know where to put this exit and how it would need to be formated...If you would have any examples of something you did that I could pass along, that would be greatly appreciated...take care...