I installed CMOD 10.5.0.0 on a new Windows server and configured it. I was able to successfully use arsstash.exe to stash the ID and password in a stash file.

I then upgraded the server to 10.5.0.8 and now the arsstash command errors out including when trying to change the configuration using the OnDemand Configurator.

The error displayed is:
ARS1602E The stash file >ARCHIVE.stash< is invalid.

In a quick test, the spooled files were sent in a HLD status.  The monitor joblog contained OND2798 ARS1106E Connection cannot be established for the >QUSROND< server.
I suggest that the monitor be started with the parameter STRSVR(*YES).  That should fix the issue going forward.  If the server is already active, then the only overhead is a couple milliseconds verifying that is it active.

This helps immensely, I cannot thank you enough.
I have fixed my FIRST OnDemand problem.
The problem was that this, FIELD3=4,-12,35,(TRIGGER=3,BASE=TRIGGER) instructed to go 4 lines down after finding the '.' (which is an amount, not part of the address). But it only needed to go 2 lines down. This tool will help a lot in the future.

Hi Lori -

As of this date, nothing has been announced.

I get occasionally asked when is the next release is coming out.

I can truthfully say I have no idea. The Chief Architect does not confide in me.  :-)

However, I can say that in the past support continues for at least 2 years for the n-1 level of CMOD after the new "n" level is announced.

I anticipate even if a new release is announced today you'll have all of 2026 to implement it.

I also know that new function is being promulgated via fixpacks, so it pays to stay fairly current.

A good ref:

https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs

Ed

I think we are finding that on Sunday only the QUSROND Server job is not yet started before the MONOUTQ job, so the MONOUTQ job is trying to process the spool file from the outq before the server job is ready.  Would this cause the spool file to be sent to the Error outq in Error status?

They are trying to explain how to look at sample data in the Administrator Client.  Open the Administrator Client.  From the list of Applications, right click and select update on the application in question.  Go to the Indexer Information tab, click on Modify with Sample Data.  You can either download a spooled file at that point, or use sample data previously downloaded (see previous advice on manually downloading sample spooled data).  On the tool bar there is an icon with red, blue, and green horizontal lines. Click that to toggle to Display mode.  The triggers on the page are boxed in red, the fields boxed in blue.  You can then scroll page by page to see where the problem is.

Also, if you click on the icon to the right of the Display/Add mode icon, that will pop up a dialog where you can generate a listing of Field Values found in the sample data.  (Click Field Values, click All Pages, click the Create button, then the View button).  Look thru the file for missing field values.

I hope this helps,

What messages are in the monitor joblog?  You might try starting the monitor with LOG(*YES) which will write more information into the joblog.

A co-worker is telling me to do a walk through here is her text: "For Fayette, if you go into the OnDemand application and do update (right click and select update) with one of these reports on hold, you can specify the library and queue, you can 'walk' through the fields to see what the program is finding for the fields--especially field 3." I asked her how you do this with no response back. It appears she is saying you can see the data coming through on demand somehow, yet see nothing that I see enables a mode like that.

We have a spool file report created daily at about 3:00am and sent to the OnDemand iSeries monitored output queue.  The report processes successfully six days a week, but the Sunday morning report always gets sent to the Error output queue in HELD status and No message 88 (failed load) get generated in the System Log.  If later in the week the file gets released and moved back to the monitored output queue then it loads without issue.

Is there any scenario where a spool file load can fail from the monitored output queue without generating a message 88?  Given that this only happens on the weekend, could there be any system events that we should look at?

We have a ticket open with IBM support and the response so far has just been to look for message 88 records, which do not exist.

Thanks,

Good afternoon,  Management is wondering if a new CMOD Zos release is expected in 2025.  (Just for planning purposes) We are currently on V10.5