Extracting Indexes loading

[jsquizz]

What is the best way to extract indexes from a particular file after loading.. this is for reconciliation purposes.

I've read about using a post processor, and I do recall using a C exit back in the day. I don't have C dev skills, so maybe a shell script in the post processor is my best bet.

Anyone have an idea/suggestion as to what it may look like?

[Nolan]

Not sure I fully understand the requirement, index values are stored in the DB/2 tables.  If you need to extract them, I would use SQL to pull them off the database.  Wrap whatever automation you want around it.

[jsquizz]

I could have swore that back a few years ago in another installation, we had a script that ran, and extracted the indexes somehow. I don't think it connected to DB2. I'm not sure how it worked.

Basically, I just want to get something like a file that says

DOCUMENTNAME, RDATE, POLICY
DOUCMENTNAME, RDATE, POLICY
DOCUMENTNAME, RDATE, POLICY

I could be taking the wrong approach

[Nolan]

I guess you are referring to arsdoc query, that is the tool to pull out the details of documents/indexes.

https://www.ibm.com/support/knowledgecenter/en/SSQHWE_9.5.0/com.ibm.ondemand.administeringzos.doc/doddo006.htm

Again you will need to wrap your automation around running the script post loading.

[jsquizz]

I could have swore there was another way to do this.

What is the best way to pull the loadID from the DB to run the arsdoc against it to gather the indexes?

[Justin Derrick]

There's no quick/easy way to do what you're asking.  You can probably get the LoadID (or its constituent value) from the System Load Log, and go from there.  There's going to be a lot of coding to get this done.

-JD.

[jsquizz]

Alrighty thanks much. I know that in my past gigs this was done by use of ARSULOAD exit. There was another script that was thrown in the post processor that I cant remember for the life me me look liked.

[Nolan]

I have had the unfortunate pleasure of spinning reports in and out of OnDemand many times.   Getting the loadid from the arsdoc query use the -I, then using a script loop through the results and only take the unique load ids. 

This has worked for us successfully.   I wrap everything in a REXX script as that is my preferred method.