Messages

61

Report Indexing / Character translation

« on: September 18, 2020, 06:20:09 AM »

Hello,

We have an application sending a mainframe file to CMOD.   One of the characters is a | (x'4f' when turning on hex in the mainframe dataset).  When it loads to CMOD, its showing as a ! (exclamation point).  Does anyone know why CMOD is doing this?

62

Report Indexing / Re: Changing indexed report to non index report

« on: September 01, 2020, 07:03:21 AM »

Thanks to all for all the input!!!....Full Report Browse option doesn't work as they use ICN and not client.

The Full text search would work. These reports are large and they would limit their searches across one days version. As indicated, the report was initially setup to index off of ORG code.  But they are more concerned with Account number.  So as its setup today, they had to go into each ORG Code index for that day to verify the Account number wasn't there. 

For this case, the change was already in place to create new application/application group with no indexing which of course only effects things after change. 

We will definitely keep the Full Test Search in mind, and be aware of how it will be used and how large the data is as to not impact performance if used. 

Again, I appreciate all the input from everyone!

Take care

Dave

63

Report Indexing / Re: Changing indexed report to non index report

« on: August 31, 2020, 05:16:23 PM »

HAHA...My bad Justin....This is a mainframe report we are loading into CMOD.  They are breaking it on ORG number.  ( I said account number previously).  They need to verify the Account number.  Apparently the Account number can fall under numerous ORG Number.  So now they need to go into each ORG code index and do a search on the account number.  So they want to have it loaded without breaking on anything.  So if the file is 100 pages, they just want the version to open with 100 pages and then be able to open the version and then do a FIND on the Account Number so it searches all 100 pages.  I realize this isn't the best way, performance wise, to do things.  Below is their explanation for wanting the report to be changed:

CDSB0SNR and CDSB0SNZ are the new account reports for the Institutional Bank and Private Wealth, respectively.  My team uses CDSB0SNR on a daily basis to validate the accuracy of data input for new CDS accounts.  When doing that, every account must be reviewed, regardless of organization. 

I hope this helps explain things.  The way we are doing it is to create new ACIF reports without any breaking (ie Org Code)

64

Report Indexing / Changing indexed report to non index report

« on: August 31, 2020, 08:51:13 AM »

Hello,

We have Applications  that are using the old OS390 indexer to index on Account number.  These reports all share an Application Group used by other Applications.   The users are requesting these reports not be indexed.  Just want then loaded to CMOD as one index.  My question is the only option to create new Application and Application groups for these reports with no indexing?  My guess is the answer is yes.  Don't believe we can just modify the Application indexes themselves since the Application Group is using Account Number field as an index.

65

Report Indexing / Using RECORD RANGE on Trigger

« on: September 12, 2019, 06:05:12 AM »

We ran into an interesting issue...We have mainframe data that has no constant value on every page to base a trigger off of....We decided to use the word Account: but it can fall anywhere between lines 1, 6....So we set up the trigger with a record range ((TYPE=GROUP,RECORDRANGE=(1,6))....That seemed to work...However, the users started reporting that on some pages were "missing"...What we found is, the missing pages have less than 6 lines and were being attached to the next index on the data file.  It appears this is due to the RECORD RANGE parameter.  If the page contains less than 6 lines it throws the indexing off.  When we manually edited the pages that had 5 lines or less and just inserted blank likes so it was more than 5, indexing worked.  We notified the application that they need to edit any page to ensure they all have 6 lines or more.  Just checking to see of anyone knows of anything else that can be done from a CMOD perspective on the Indexer?

66

Report Indexing / Re: Bad Character???

« on: July 30, 2019, 07:24:03 AM »

Thanks Ed!...We are running Version 9.5.0.8

I will pass this info onto our systems group to see what they can possibly do.

Appreciate the info!!!!!

Take care

Dave

67

Report Indexing / Bad Character???

« on: July 30, 2019, 05:29:41 AM »

Hi, we have an old report defined using OS390 indexer..Its been running for years...recently its been failing on an index (USER NAME) with the below error:

The string "SISSOKO, AØÏSSATA " has a length of 20 and the field has a maximum length of 18

I know its do to either the character that looks like an O with a line through (x'80') it OR the I with the 2 dots above it (x'57') because when we remove those 2 characters, the file loads.  We did attempt to remove each one individually and received the same results..But removing both allowed the file to load successfully...We even attempted to created a new definition using ACIF indexer with same results...Had anyone else ran into this kind of issue with special characters? Also, the INDEX is set as a STRING.

Thanks in advance for any input

Take care

Dave

68

Report Indexing / Indexing issue

« on: March 19, 2019, 05:48:15 AM »

Hi...We have a report where were are doing a record range on the trigger (TYPE=GROUP,RECORDRANGE=(1,8)).  We had to do this because on certain index pages the actual trigger can fall between lines 1-8.  The issue we found is, if the previous page before an index page has less than 6 lines it will attach itself to the following index.  As an example, if there were 2 index pages, the first had a total of 10 pages.  If Page 10 only had 5 lines on it (including carriage control) it will attach it to next index.  So when you open the first index it will have pages 1-9.  When you open the second index, it will start with page 10 and then second page will be page 1 (index page containing the trigger) of the second index on the input file.  Strange thing is if we edit the file and add just one more line (so it has 6 lines on that page) it will group the pages correctly.  First index will have the 10 pages and second index will start with the index page (Page 1)...We BELIEVE it has something to do with the Record Range but with it being set to 1,8 can't understand why when its just 5 lines it doesn't work but 6 lines it will....Any ideas? Below is a sample showing the all the Triggers.  We had to create a separate trigger to capture the Date page for use as the Posting date. It only appears once at the beginning of each file.

CC=YES
CCTYPE=Z
CONVERT=NO
CPGID=1252
MCF2REF=CPCS
TRC=NO
FILEFORMAT=STREAM,(NEWLINE=X'0A')
TRIGGER1=*,1,X'31',(TYPE=GROUP)                                            /* 1                */
TRIGGER2=*,2,X'4143434F554E543A',(TYPE=GROUP,RECORDRANGE=(1,8))     /* ACCOUNT:     */
TRIGGER3=*,15,X'666F7220446174653A',(TYPE=FLOAT)                           /* for Date:        */

69

Report Indexing / Re: View Title on TABS

« on: March 08, 2019, 06:16:46 AM »

Just a quick followup...After doing some more researching the tap order display is based on the HIT LIST order and not the QUERY order...

70

Report Indexing / Re: View Title on TABS

« on: March 08, 2019, 06:06:29 AM »

Kinda my thought too Justin...Users will need to determine what's more important to them...We can definitely change the query order of they deem the tab order is more important to them!!   

Thanks for the verification!!

Take care

Dave

71

Report Indexing / View Title on TABS

« on: March 08, 2019, 05:33:08 AM »

We have a user that want to view specific indexes on the tab when viewing a index.  It seems the order they display on the tab is based on the QUERY order...Unfortunately the index that is being display second on the tab is what they would like to show first...Does anyone know a way to modify the tab order display???  Appreciate any input

Take care

Dave

72

Content Navigator / Details View Vs Magazine view

« on: February 27, 2019, 11:28:02 AM »

Does anyone know what the differences are between Details View and Magazine View and why you would use one over the other?

73

Report Indexing / Re: APP GRP Field length

« on: February 14, 2019, 05:16:48 AM »

Thanks Justin for confirming my "Fear"...lol...Just aggravating when you "test" with users prior using their own data (running it through the report wizard) to get all the needed indexing definitions and then have them load many versions before notifying you that this one index now has a different length now  .....As always, appreciate your input!!!

Take care

Dave

74

Report Indexing / APP GRP Field length

« on: February 07, 2019, 10:20:48 AM »

I THINK I know the answer to this question but figured I'd ask it anyhow to see if someone knew of a different way..

We defined a new application group...When defining things we ran it through the report wizard to get all the index informations...Which included highlighting the fields to get their length...Now we TOLD the data was always the same...Come to find out one of the fields is not longer (went from 6 to so now its getting truncated....We know you cant just go into the app grp and modify the length as its grayed out...The only way we are aware of is to create an totally new app grp and modify the field length..This is a royal pain as we have to first rename the existing definition (app grp and app) since it has data already loaded to it and then create a the new definition under the original name so the data will load to it....Then of course map everything to the folder...Not sure if there is a easier way...Shame you aren't able to just modify the length on the existing field...Appreciate any input

Take care

Dave

75

MP Server / Re: Unable to store object Failure

« on: February 01, 2019, 03:16:57 AM »

Well we just took another "hit" on 01/31..This time it was 7 reports that received the "unable to store" error.  As always, after rerunning them they all loaded fine...Last update we had was they opened a SR with Dell....With it being so intermittent its hard to diagnose apparently..Even with giving them specific times and errors everytime...Hopefully they come back with some resolution.  Hoping you don't encounter the same issues!!!  Take care