Well someone should of cleared that up 20 years ago! LOL.

Thanks Ed, I will suggest it as a cost saving suggestion to the team to setup.

I don't know if that is possible.   You asking about loading data or dragging and dropping AG/APP defs?

If you are talking about loading data, I would think there would be many challenges to set it up.   Running ARSLOAD on Z/OS pointing to MP doesn't seam like something it can handle?  You would update the ars.ini for the MP server name but security could be a challenge.

I think you need to move the data to the MP server and perform the load there, IMHO.

Update the post if you get it working, I am curious if it is possible since we always move the data from Z/OS to MP and then load.

I see from the tech note: https://www.ibm.com/support/pages/node/6525888
how to update the cmod-rest.war file.  This ones is a little more fun.

For Windows, Z/OS and AIX deployments we only use the base product so the log4j files are not really required/used.  I will replace them with 2.15.0 but I have no classpath in play to update for them.

Let me know if you think I am missing anything.

Thanks

"You will then need to update the classpath within your application server to reference the new version of these files"

Is this applicable to the base product?  If yes, where do I update?   

Correct, an internet search is always the 1st step of troubleshooting.  Most often already answered, or in the online documentation.

As you noted :)

-C 123456789

Why are field1 and field2 hardcoded?  Field3 looks correct but 1 and 2 should be using the same  style

FIELD1=Line,Column,Length,(TRIGGER=1,BASE=0)  <---put real location values for line/column/length
FIELD2=Line,Column,Length,(TRIGGER=1,BASE=0)  <---put real location values for line/column/length

For the 64 bit client, it looks like arsole.ocx is not supported.  Did anyone ever find a way to use ole with the 64bit client?

https://www.ibm.com/support/knowledgecenter/SSEPCD_10.5.0/com.ibm.ondemand.winclient.doc/dodwc257.htm

Note: OLE Controls are supported by the 32-bit OnDemand client. OLE Controls are not supported by the 64-bit OnDemand client.

Ideally, you should have a PROC setup to run the ARSLOAD module.  You can create a few JCLs with a max of 255 steps per JCL, (I would do 8 JCLs).
If you are not using an EXIT to get the A and AG names, then you would pass those required values on each step.   Note that this assumes all the datasets are ready to go at the same time.

(More advanced method)
If you are more comfortable in OMVS, you can write a script or REXX to read an input file, then loop through running arsload commands directly from OMVS.  Then put the script in one JCL.

Many ways to solve the problem, you need to find the one that is best for your shop.

Adding to the stricter rules. 

Comments must be /* comment */   - No space between forward slash and the asterisk.

The error message was
ARS5481I INDEX1='SEC_ID',FIELD1,(TYPE=GROUP,BREAK=YES)                / *SEC ID */
ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR BREAK

The issue was the comment!!!   

Then it is not possible to capture the OnDemand success or failure error code in JCL.  I recommend for any critical loading you use arsload via the batch JCL method, any failures will provide a non zero return code.

It sounds like you are dumping the file to the spool versus using the arsload in the JCL.  If you have arsload in the JCL and it still is not giving you are return code, let us know the parms on the arsload statement in the JCL and what version of OnDemand you are running.

Adding to Indexer parm tightened up for NODX

If you see this:

ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR NAME

Then the solution is to change

INDEX03=PAGE_NO,FIELD1,(TYPE=GROUPRANGE)

to

INDEX03='PAGE_NO',FIELD1,(TYPE=GROUPRANGE)

Quotes are now enforced on the index name.

We found all of ours to clean up using this query.

select name  from $DBOWNER$.arsapp
where indexer like '%INDEXSTYLE=NODX%' and indexer like '%INDEX%=P%'

Your response is still very unclear on what you are trying to accomplish.  The server and the client are to different parts and can run at different levels. (see compatibility matrix)

What you need to do is upgrade your servers to 10.1.x in all locations to be running a fully supported product.

For the thick client, you can roll out the updated version 10.1.x to your user base before or after the server is upgraded.
If you have users using ICN, then that server should also get the updated OnDemand server binaries installed for ODWEK.

Hello folks, we have upgraded our test system to 10.1.0.4 and in testing the Anystore exit via ARSLOAD it fails on a 2nd file being processed.  The ODSSGET module is stuck pointing to the EOF of the inital DDNAME loaded.

@rjchavez said years ago

"The ODSSGET routine is called to OPEN, READ, and CLOSE files including the actual report files.  These traditional MVS services were causing the issue (still not sure why).  I changed the exit to use FOPEN, FREAD, and FCLOSE instead.  This corrected the problem."  - http://odug.net/index.php?topic=1777.0

I don't have any documentation on ODSSGET as like others, Lab Services provided it without source code. :(

Q1. FOPEN/FREAD/FCLOSE?  Is that part of ODSSGET or something written in C?
Q2. Does anyone know how to reset the ODSSGET (initialize it).  I have tried ODSSGET-CLOSE and ODSSGET-OPEN but the results are the same.  Remains pointing to the EOF on initial DDNAME.

Initial Load
Init Call ODSSGET           
Set ODSSGET-OPEN to True
ODSSGET-DDNAME     :SYS00001
ODSSGET-RETURN-CODE:00000   
ODSSGET-REASON-CODE:00000   
ODSSGET-DDNAME     :SYS00001
ODSSGET-ACTION     :OPEN   
...
Terminate Anyssotre Exit with ODSSGET-CLOSE
Set ODSSGET-CLOSE to True
Perform CALL-ODSSGET.   
ODSSGET-DDNAME     :SYS00001
ODSSGET-RETURN-CODE:00001   
ODSSGET-REASON-CODE:01001   
...
2nd file
Init Call ODSSGET             
Set ODSSGET-OPEN to True
CEE3201S The system detected an operation exception (System Completion Code=0C1)


Any suggestions are welcome.

Thanks

Check the Z/OS logs at load time for an SMS message explaining why it doesn't like the collection name.   Was there any change to SMS routines over the weekend?  You sure your report specification exit is putting the correct APP/AG and collection node to use?

You should also move to a new version of OnDemand to get IBM support. :)