Giuseppe

look in the application group, field Information tab, and confirm that the field that you are trying to change has "updateable" selected.

The other way would be to use the windows client and update the field (but this would still require it to be 'updateable'

in response to "Is there any debugger kind of thing in CMOD"

use Update Application in the admin client, Indexer information, Modify with sample data (the spool file in question)

use the "toggle between display and add paramters" to highlight your index fields.  go to document 59, you should see that you are not picking up the date field as expected.

It might be possible to query the System Load tables  SA%..., using the the APPLGRP_NAME and LOAD_START_DT  fields.

this assumes all your loads were done after the load table was introduced.

I ran into this issue a few years ago.  There is an IBM technote on it;    https://www.ibm.com/support/pages/node/286565

there is an ibm redbook which may help with your question. 

search for  "Content Manager OnDemand Backup, Recovery, and High Availability" 

There is a chapter on backup and recovery for iSeries

actually a typing mistake on my part, the screen shot shows version 10.5.0.0  .

Does the client crash on your windows machine consistently? 
I would second JD's suggestion to open a service request.   
It shows you are running  10.1.0.0  which makes you a "test pilot"  :) 
being risk averse, I would prefer to be at 10.1.0.1 as soon as it is available.

Are you getting any errors or warning in the system log during the expiration?  we had issues in the past, that the expiration processing would stop after a problem  (  ie process one or 2 app groups one time, 20 the next).

our workaround was to resolve the problem, or manually force an expiration on the particular app group to get past the issue.  once all we got around all problem app groups, the expiration jobs would run completely.

Hi JD

We looked a this a while ago, (for individual doc loads),  which then turned itno, lets use it for bulk loads, in the end decided just not worth the bother.  Rather than have scarce java developers put things together with ODWEK, it was easier to convince them to create a file landing area, and let an OnDemand monitor job pick up the files.

in some scenarios 2 reports with the same posting date is valid.

We originally used information from the system Log, then once available started to use the System Load facility.   
There are a number of fields that we use to determine if a load is duplicated (ie  doc Begin date, row count, total pages, input size, output size, input file name)

Joe,  I can't say I've had any experience with this recently.  I vaguely remember years ago(many) that there were that there was something about Ondemand client and VB in the OnDemand Toolbox

Joe,  the command needs to provide the field definition name from the Folder instead of the app group

I had same bad result with your command,

instead use;

FNDKEYOND FOLDER('System Log') KEYFLD(('Msg Num' *EQ 30))

the knowledge base says to contact your ibm rep.  https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.2/com.ibm.installingeuc.doc/eucco080.htm

I would expect the Line2pdf transform to be under your odwek install (not familiar where this would be on z/OS)

which component is hanging?  is it the server or the client workstation.  Also what exact levels of 9.5.*  are you using at server and client?

I had to deal with some orphaned indexes recently.

the following support document from IBM may help

https://www-01.ibm.com/support/docview.wss?uid=swg21392642