Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
OD/WEK & JAVA API / Re: ODWek REST - Search with SQL - Segment start and stop date
« Last post by rjrussel on March 10, 2023, 09:09:20 AM »
CMOD will handle the rest for you.

Thats fine, I just dont get how this work.
I have a segment date field, when I use startdate = 2023-02-25 I still get hits where I have records contains date = 2021-08-04

Searching without SQL seems to be extremely slow compared to Search with SQL.
Did a few test request now.
  • Search with SQL = 59ms
  • Search without SQL = 1677ms. Even up to 3s
Total number of hits = 1

If you know how we can use segment startdate and stopdate in Search with SQL - I'd very much like to know :D

The short answer is CMOD uses the segment startdate and stopdate to limit what tables it searches across. If an AG has 100 tables in it, using a segment field can help significantly. If you only have one table for a given application group this will not of course help much.

So, searching a folder with a date field that is also defined as a segment field will cause cmod to first identify what data tables fall in the given range and then performs a search only against those tables.
2
OD/WEK & JAVA API / Re: ODWek REST - Search with SQL - Segment start and stop date
« Last post by rjrussel on March 10, 2023, 09:00:41 AM »
I'd like to request robust SQL support with access to all fields in the table, for those of us who do "interesting" things.  :)

-JD.

So not just SQL support. You want it robust? :)

I hereby certify all current SQL support as robust. There you go. Ask and you shall receive.

BTW: All kidding aside. What fields do you not believe you have access to via SQL?
3
z/OS Server / ARSDOC GET -L produces "error"
« Last post by grahaj7 on March 10, 2023, 07:01:47 AM »
hi!

I have a need to run ARSDOC GET to get the 'most recent' version of a report.   I don't see an option for this, so I have come up with a couple ways to do it:

1. First run a QUERY (sorted), use the results of the query to get a REPORT_DATE and then run an ARSDOC GET with that date as criteria.
This would totally work but, I would need to do that programmatically and I will be turning this process over to others, so the simpler the better. 

2. Running an ARSDOC GET -L 1  (limit 1) actually does the trick because the reports are sorted in descending order and the '-L 1' limits it to one report only.  I always get the most current report. So that works, BUT when I use that I get

ARS6055E A maximum of '1' hits(s) were requested for this query. The number of matching hits found was '1982'.

and ARSDOC returns 768.

 It's odd that this is an "error" because I specifically asked for '1' result, and that's what I got.  The rc768 would get flagged by the scheduling software and force an abend.   I could tell the scheduler to ignore the rc 768 but rc 768 could happen for other reasons which need addressed, and SHOULD abend.

Has anyone come up with a simple way to get "most current report" that  is not either of these two? :)  I thought about putting in an enhancement request to IBM to ask them to not produce an error/rc 768 for the second case.  (I know that would take time even if it were acceptable. )
4
CMOD will handle the rest for you.

Thats fine, I just dont get how this work.
I have a segment date field, when I use startdate = 2023-02-25 I still get hits where I have records contains date = 2021-08-04

Searching without SQL seems to be extremely slow compared to Search with SQL.
Did a few test request now.
  • Search with SQL = 59ms
  • Search without SQL = 1677ms. Even up to 3s
Total number of hits = 1

If you know how we can use segment startdate and stopdate in Search with SQL - I'd very much like to know :D
5
I'd like to request robust SQL support with access to all fields in the table, for those of us who do "interesting" things.  :)

-JD.
6
OD/WEK & JAVA API / Re: ODWek REST - Search with SQL - Segment start and stop date
« Last post by rjrussel on March 09, 2023, 11:46:08 AM »
Sounds like you don't search with SQL. Just user /cmod-rest/v1/hits/<folder> and specify a date field (that is defined as a segment field in the CMOD admin) as part of your search criteria and you should be good. CMOD will handle the rest for you.
7
Report Indexing / Re: CodePage Issue Line Data
« Last post by Ed_Arnold on March 09, 2023, 11:39:02 AM »
Better open a case with CMOD support.

Ed Arnold
8
Good question, is it more efficient to not use the Search with SQL and rather use /cmod-rest/v1/hits/<folder> ?

Cant see we specify segment startdate and stopdate in /cmod-rest/v1/hits/<folder> search.
in the background maybe the segment startdate and stopdate are used ? do you know what those values would typically be?
9
OD/WEK & JAVA API / Re: ODWek REST - Search with SQL - Segment start and stop date
« Last post by rjrussel on March 09, 2023, 08:32:49 AM »
Why do you need to search with SQL?
10
Thanks Russel,

Do you mind also explain how we can use the segment startdate and stopdate?
I dont get how I should get that value to make the search more efficient.
Pages: [1] 2 3 4 5 6 ... 10