OnDemand User Group
Support Forums => MP Server => Topic started by: MarkD on April 26, 2013, 12:28:42 PM
-
I have an existing app and appgrp to which I want to archive a report using a predefined .IND file. I am doing this on CMOD 9 on AIX for the first time. My IND file is called dpf45b.IND and is coded as follows:
CODEPAGE:850
GROUP_FIELD_NAME:rdate
GROUP_FIELD_VALUE:04/23/13
GROUP_FIELD_NAME:rname
GROUP_FIELD_VALUE:R-1001
GROUP_OFFSET:0
GROUP_FILENAME:/brdwnld3/dpf45b.dpf45b.dpf45b.out
I then execute:
arsload -h bcdemand -fv -u medepat -p /home/medepat/medstash -a dpf45b -g dpf45b /home/medepat/dpf45b
It seems to fail because it is unable to locate the GROUP_FILENAME where the file does indeed exist:
ARS4315I Processing file >/home/medepat/dpf45b<
ARS4334I Load Version <9.0.0.1> Operating System <AIX> <6.1> OS Userid <medepat> Install Location </opt/IBM/ondemand/V9.0/>
ARS4335I Server Version <9.0.0.1> Operating System <AIX> <6.1> Database <DB2> <10.01.0002>
ARS4312I 04/26/13 15:10:14 -- Loading started, --UNKNOWN-- bytes to process
ARS1163E No source file was specified
ARS1146I Loaded 0 rows into the database
ARS4311E 04/26/13 15:10:14 Loading failed
ARS4318E Processing failed for file >/home/medepat/dpf45b<
Processing has stopped. The remaining files will NOT be processed.
Probably something obvious, but I can't see why it should it fail to find the source file.
-
I think you need GROUP_LENGTH:0 as well, after the GROUP_OFFSET parameter.
-JD.
-
does this data file exists? /brdwnld3/dpf45b.dpf45b.dpf45b.out
-
Your application - indexer information tab - select 'generic' for indexer type
-
Thanks for the responses.
GROUP_LENGTH had no effect.
The file really is in that staging directory by that name.
I was under the mistaken impression, that if you supplied an .IND file, ARSLOAD had no reason to use the indexer parameter. I had thought this was only read if the utility determined that it had to index the report in order to load. Fact is, I did have to set the indexer to generic for it to work. I had thought I had done this in the past to load large amounts of input to an existing application without changing the indexer from ACIF or PDF. If so, this is now required in Version 9.
Fact is, a lot of things work differently, or not at all, in Version 9. We came from Version 7, and I have to consider this migration to be a downgrade, based on what we've experienced so far.
-
Yeah, if you don't have the Generic Indexer specified in the Application, you can use -X G on the arsload command line to force the load to use the generic index.
-JD.