Author Topic: Error loading ascii text file  (Read 2756 times)

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 573
    • View Profile
Error loading ascii text file
« on: November 17, 2017, 07:32:22 AM »
I have a log file I am trying to pull two fields off of. I can indext it with the graphic indexer no problem, but when I try to load I get the following-

                          : APK415I CC=NO
                          : APK415I CCTYPE=A
                          : APK415I CONVERT=NO
                          : APK415I CPGID=850
                          : APK415I MCF2REF=CF
                          : APK415I TRC=NO
                          : APK415I FILEFORMAT=STREAM,(NEWLINE=X'0A')
                          : APK415I TRIGGER1=*,3,X'2D',(TYPE=GROUP)
                          : APK415I FIELD1=0,1,10,(TRIGGER=1,BASE=0)
                          : APK415I FIELD2=1,1,18,(TRIGGER=1,BASE=0)
                          : APK415I INDEX1=X'7264617465',FIELD1,(TYPE=GROUP,BREAK=YES)
                          : APK415I INDEX2=X'6C6F676E616D65',FIELD2,(TYPE=GROUP,BREAK=YES)
                          : APK415I DCFPAGENAMES=NO
                          : APK415I UNIQUEBNGS=YES
                          : APK415I IMAGEOUT=ASIS
                          : APK415I INDEXOBJ=ALL
                          : APK415I INDEXSTARTBY=0
                          : APK415I INSERTIMM=NO
                          : APK415I RESTYPE=NONE
                          : APK415I FORMFEED=YES
                          : APK415I INPUTDD=/tmp/logfile.out
                          : APK415I OUTPUTDD=/dev/null
                          : APK415I INDEXDD=/tmp/logfile.out.ind
                          : APK415I RESOBJDD=/dev/null
                          : APK460S TRIGGERS SATISFIED, BUT INDEXES WERE INCOMPLETE AT END-OF-FILE.
                          : APK412I MODULE APKIXSAX HAS RETURNED WITH RETURN CODE 16.
                          : APK441I ACIF AT PI72113 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.

Just trying to capture the information off the top of the file-

11-16-2017
CMOD_PROCESS_START
-----------------------------------------------------------
-----------------------------------------------------------
11-16-2017 04:40:31 PM: Starting CMOD Processes on...
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 573
    • View Profile
Re: Error loading ascii text file
« Reply #1 on: November 21, 2017, 07:46:31 AM »
I got this working. Heres what I did. First, I removed the date from the indexing requirement and just defaulted it to t, with the new date/time values. That works good for what I'm trying to do. I actually just copied the system log application, and set it to my application group, and changed the indexer from NONE to ACIF, did the bare minimum indexing and boom, works like a charm!

I'm not sure if we use splunk or any log management tool at this shop, but this looks like a cool way to keep these random scripts in check!
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2228
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Error loading ascii text file
« Reply #2 on: November 21, 2017, 02:05:17 PM »
FYI, if you're going to keep small log files in CMOD, they won't compress very well, and they'll 'pollute' your cache with lots of very small files.

I've recommended this to many clients, but I can only think of one who actually bothered to implement it...

  • Create two AGs -- one that holds your log files for 90 days ("Active") in cache, and another that holds them for the long-term storage ("Historical")
  • Load your daily log files into your active AG.
  • On the first of the month, export the entire previous month's worth of log files with arsdoc get.
  • Load the resulting file into your long-term storage
  • Run expiration on your 'Active' App group.

What you'll get in return is:  Much better compression in the historical group, with WAY fewer individual files, which reduces overhead from your monthly volume of individual loads to 1 load into CMOD, plus less wasted space in the cache filesystems from storing 1k files in 4k blocks, etc.

Of course, maybe your volume of logs isn't high enough to spend the effort on this idea -- but when you're producing thousands of small (under 1MB) documents a day, the savings add up.

-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

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 573
    • View Profile
Re: Error loading ascii text file
« Reply #3 on: November 21, 2017, 03:05:12 PM »
Never thought of it that way. I’ll have to take that approach.

Currently, pretty much nothing writes to a log. Startup scripts, etc..and that was one of my own personal goals in my sparkly new 10.1 environment. Im going to have much more automation than what is currently in place. Thank you!
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING