Author Topic: ACIF and historical loads  (Read 2232 times)

DDEVENPORT

  • Guest
ACIF and historical loads
« on: July 21, 2017, 09:44:19 AM »
I am using ARSLOAD for Windows loading AFP documents using TLEs through the ACIF Indexer. We just pass the content as an ARD file.

I added a POSTING_DATE TLE formatted as %Y%m%d%H%M%S and passing 20170704010101 in the TLE.

ARS1129E Row 1:  The string "20170704010101" could not be converted to a date from the format of %Y%m%d%H%M%

What I am trying to accomplish is setting a POSTING_DATE in the past. My application would pass the date we want in the TLE and not use the system date timestamp. Bad assumption on my part that this would work?

If I can't manage POSTING_DATE this way, what would be the correct way? I cannot find documentation. The preference would be to manage this with the content data (TLE).

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: ACIF and historical loads
« Reply #1 on: July 27, 2017, 11:19:49 AM »
You're missing the seconds parameter (%S?) in the ACIF indexing parameters.

-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

DDEVENPORT

  • Guest
Re: ACIF and historical loads
« Reply #2 on: July 28, 2017, 05:54:07 AM »
Thanks for the reply.

In this case no, not missing.

Discovered that the TLE 'data' has a trailing hexadecimal '0D'. I changed that in the data to a space hexadecimal '40' and added that to the trailing character removal and it worked then.

The annoyance with this is, the error message does not 'display' the extraneous data leading you to believe that WYSIWYG(GOT) and it isn't. Another annoyance is trying to get that X'0D' removed through the CHARACTER REMOVAL GUI. Could not figure out how to do that.

Anyway, having our client application remove the offending data.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: ACIF and historical loads
« Reply #3 on: July 29, 2017, 07:06:45 AM »
Anyway, having our client application remove the offending data.

Yeah, the best way forward is to have data that is correct and compliant.  :)

Thanks for posting the solution to your issue! 

-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