Extract from z/OS, load to MP results in double load

Previous topic - Next topic

LWagner

I have extracted PDFs loaded on z/OS under CMOD 8.4 as generic files, to a CMOD 8.5 indexing server, which then runs arsload to an AIX CMOD 9.0.0.5 server.

The syslog shows one load id, but the folder shows double the rows. Looking at properties of identical rows, the partial load-ids are different.  I can do an unload on the loadid shown in the system log, and one set of indices is gone, but the 2nd remains, with no system log trace.

Anyone care to take a stab at what happened, and how to limit it to a single load ?

Alessandro Perucchi

Hello,

I've done that a lot, and never encounter that kind of problem...
Really strange.

Are you sure that your 8.5 indexing server didn't run twice? And that no System Logs are there for the second load... very strange indeed.

Did you convert the "System Log" with the new Data format on the AIX CMOD 9.0.0.5 server? Maybe this will cause some issues with an "arsload" which is run in a CMOD 8.5. Maybe... I am not sure ...

Is there a reason why you keep the indexer as CMOD 8.5 and the server with V9? Have you tried to load the extracted document directly from the V9 server instead of the indexer server? Does it show the same behaviour?

Alessandro Perucchi

#Install #Migrations #Conversion #Educate #Repair #Upgrade #Migrate #Enhance #Optimize #AIX #Linux #Multiplatforms #DB2 #Windows #Oracle #TSM #Tivoli #Performance #Audits #Customizing #Availability #HA #DR #JavaApi #ContentNavigator #ICN #WEBi #ODWEK #Services #PDF #AFP #XML

LWagner

I generate scripts with paired "arsdoc get" and arsload.  I have run hundreds of these, with up to thousands of iterations.  No dup loads.  We upgraded the AIX CMOD servers , the new system to 9.0.0.5 in May.  This is the first new data moves since then. Our z/OS system is staying at 8.4.0.3.

I tried a move from a 9.0 CMOD index server.  It failed on the arsdoc get, telling me the down version server needed to be upgraded. So, back to the 8.5 intermediate server.

It is possible the other load log entry is on another server. On first setup, our message 66's on CMOD 9.0 went to another server.  Very odd default.  I will look into that possibility.