Line data without carriage control - how to load

Previous topic - Next topic

J9CMOD

I am trying to load a document that contains a lot of lines from our z/OS system log. 
- This document does not have anything that is unique on each page.
- This document does not have carriage control
- The document does not need to be split up into "pages".

We are using the OS/390 Indexer for most of our data in CMOD.

No matter what I try, I get an error :
The following message was returned from the OS/390 indexer (ARSZSTDR error_message = ARS5419E No documents found - input exhausted.).

Which (according to documentation) indicates that the trigger isn't correct.
I have tried setting my trigger at a blank space on the first line of the data, as well as on several areas with actual data.  Nothing works.
Help would be appreciated.

jeffs42885

not familiar with Z/OS but..

Read up on INPEXIT=asciinp

rick

Generic indexing could be another option since the file does not contain any metadata.

Greg Ira

J9CMOD,
I would check a couple things.  First be sure you are indexing with the correct format or if you are off by a column.  We load the z/OS system log from multiple LPARS and they all come in as VB.  Also, sometimes temporarily switching to the ACIF indexer will get you a more descriptive error message.  For TRIGGER1 we use the SYSID for each LPAR and we store the time in a Transaction Field so we get the begin and end times of the log.

CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD
TRIGGER1=*,12,X'D7F2D6C6E3',(TYPE=GROUP)                          /* P2OFT      */
FIELD1=0,12,6,(TRIGGER=1,BASE=0)
FIELD2=0,21,5,(TRIGGER=1,BASE=0)
FIELD3=*,*,8,(OFFSET=(27:34),MASK='##:##:##',ORDER=BYROW)
INDEX1=X'D985979699A36DD5819485',FIELD1,(TYPE=GROUP,BREAK=NO)     /* Report_Name */
INDEX2=X'D396876DC481A385',FIELD2,(TYPE=GROUP,BREAK=NO)           /* Log_Date    */
INDEX3=X'D396876DE3899485',FIELD3,(TYPE=GROUPRANGE,BREAK=NO)      /* Log_Time    */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
LINECNT=60
GROUPMAXPAGES=5000
IMAGEOUT=ASIS
INDEXOBJ=ALL
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

Ed_Arnold

Hello J9!  Hope all is well with you!

I have a proof of concept of archiving the SYSLOG here:

http://ODUG.net/index.php?topic=1041.0

Every day at midnight it'll suck in the SYSLOG and archive it.

Ed
#zOS #ODF

J9CMOD

Thanks, everybody for all the information.
Since the logs are our system logs (not CMOD system logs), and they are already in a dataset, I found the quick-and-easy solution was to make the file have carriage control, and set up the application that way.
It works great.
Thanks.