Topics

16

Windows Client / Adding new accesses by multiple users

« on: September 29, 2020, 06:18:10 AM »

We are using the Windows admin client 10.1.0.5 for adding new CMOD user access requests.  We've found that only one of our CMOD Admins can do any requests at one time when ADDING new users.  If more than one Admin attempts to add new user requests (different users) at the same time, we'll receive an error indicating that the UID number already exists.  I know its a timing issue but was wondering if there is anyway to avoid this?  At times we can have many requests pending and it would be nice to have multiple Admins being able to process requests at the same time.  As indicated, this only happens when trying to add new users.  Updating existing users isn't an issue.

17

Report Indexing / COLUMN DELIMITER ERROR

« on: September 27, 2020, 04:39:19 PM »

I'm trying to load a text file into CMOD.  Keeps getting the same error:

 Loading started, 3100678 bytes to process
 Row 178:  The string "/BENEFICIARY   CURRENCYFAIR" has the column delimiter in it

I've opened the file in PSPAD under HEX Editor and only find 2 instances of this exact line. Never found the proceeding / character anywhere.  I've tried editing both lines be inserting a x'20' character (space) in front of BENEFICIART and it still gets the same error.  Am I missing something? 

18

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?

19

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.

20

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?

21

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

22

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:        */

23

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

24

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?

25

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

26

MP Server / Unable to store object Failure

« on: January 28, 2019, 08:48:28 AM »

I may have posted something on this subject before but it started rearing its ugly head again....We periodically get this type of failure...In most cases we can rename the .failed file and when doing so, the file will always load successfully (at least up till now)...Our issue is, we still have reports coming from the mainframe to CMOD which use OS/390...When this type of file fails, the mainframe job itself has to be rerun manually.  We risk the possibility of losing data in the event the job runs multiple times and data from failed job gets overwritten.  Our engineering group contacted ECS storage...here was their response:

"This represents a failure rate of 0.02  for clip writes and  0.01 for blob writes
We generally advertise ECS availability of 99.9% which you are well within
There is no concern here. The application will automatically retry these failures which will succeed upon retry". 

The main issue here is, ERR doesn't support automatic retry...Our options are to manually rename .failed file or manually re-run mainframe job.

Anyone else using ECS storage having any issues?

Appreciate any feedback

Dave

27

Content Navigator / Downloading a report

« on: January 23, 2019, 09:48:24 AM »

We have a report on CMOD that is stored as application/line data...Users are viewing the report via CONTENT NAVIGATOR...One user was wanting to download multiple versions to one CSV file...After highlighting the versions that are wanted and then doing a right click. Download, the only option we see in Content Navigator is ORIGINAL and PDF (Grayed out)...Trying as an original it attempts to download each individual version into its own .txt file..But since this is line data, its unreadable...We as Admins have the thick client.  It allows you to highlight multiple versions at one time, right click and then 'Export document data for all selected as csv file)...It then opens one CSV with all highlighted versions data within.  Does anyone know of an option in Content Navigator that allows the same thing? 

Thanks,   Dave

28

Report Indexing / HELP!

« on: December 13, 2018, 12:34:35 PM »

Ok, I'm about to pull my hair out here...We have a report where we were getting all the indexes off of one page.  We were using one of the fields (ACCOUNT) as a trigger and  then going from there to get the other indexes...We had to use set it as a FLOAT with a Record Range 

 TRIGGER2=*,2,X'4143434F554E543A',(TYPE=GROUP,RECORDRANGE=(1,8))     /* ACCOUNT:     */   

What happened was on some of the files, this word ACCOUNT falls on a page in the same position that's not an index page which caused it to fail...What we TRIED to so is use the next line below ACCOUNT which is also fields....All we did was update the trigger line with the new HEX value for the new Trigger (CORR. BIC)

TRIGGER2=*,2,X'C3D6D9D94B40C2C9C3',(TYPE=GROUP,RECORDRANGE=(1,9))      /* CORR. BIC */

We then adjusted the lines on the FIELDS to go off the new trigger..Which meant decreasing each field by one   ...But since doing this, we cant get anything to load...This is all we get in the 88 MSG

APK440I ACIF AT IPTR923 HAS COMPLETED NORMALLY WITH RETURN CODE 0.
ARS4308I Indexing completed
ARS4312I Loading started, 15762 bytes to process
ARS1146I Loaded 0 rows into the database
ARS4311E Loading failed

For the life of me cant understand why it wont load anything now just by changing the trigger and field positions...Just to test again, we even tried using the field below (SPECIAL) as the new trigger, made the FIELD position changes and it still gets the generic failure...Wish it would give SOME kind of information on the actual error!!

I've attached the page we are using for indexing
                  

29

Report Indexing / INDEX FIELDS REFERENCE OUTSIDE OF THE RECORD

« on: December 12, 2018, 11:23:44 AM »

When attempting to load a large file (72MB) we received the following:
APK449S INDEX FIELDS REFERENCE OUTSIDE OF THE RECORD, FIELD# 6 INPUT RECORD# 1380465.

We are able to copy the file to NOTEPAD but with it being so large, its like finding a needle in a haystack where the bad record is.  Of course the 88 message doesn't show you what the exact line is that's causing the issue.  It gives the FIELD # which allows you to narrow down which index it is but its nearly impossible, even with specifying then index name, to find the bad record with it being so large.  Is there a way to somehow determine where the RECORD# is on the data file?  We've load over 200 files to this application and have had only 3 that have had issues.  The other 2 had the same issue but on different field names.

Appreciate any help.

30

Report Indexing / POSTING DATE ISSUE

« on: October 30, 2018, 05:37:35 AM »

we have an old mainframe report we are attempting to load to CMOD9.5 using an ACIF indexer..Appoxed 45 versions...We've respun the data to a mainframe dataset...We need to capture the date on the report.  Unfortunately its not on EVERY page of the report and the pages it is on it can move up and down lines...It is on the first page in this format (February 28, 2010) ...Is there a way to only look on the first page to get the date?  in the past I've had the scenario where the date is ONLY on the first page and I've set up a separate trigger to capture it and by removing the small 't' on the application definition...Tried doing that with this report going off of PAGE   1 as the trigger....Unfortunately, with this report other page 1's don't have the date on it so it fails..How can I force it to only look on the first page for the date?  There's no other fixed data on the page that's unique to only the first page to go off of for the date...These files are huge so we can't even manually add something ourselves to the first page..Goes to BROWSE SUBSTITUDED...Only other option is to manually update the DEFAULT value on the Application definition for POSTING date...