Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mroutlander

Pages: [1] 2 3
1
MP Server / SSL Connectivity Working Inconsistently
« on: October 09, 2020, 05:35:57 AM »
Hi fellow ODUsers,
I am experiencing a strange problem. My client is running 9.5.0.11 as the CMOD server (on AIX v7 TL5). Recently, the SSL certs expired and so we got a new signed one and installed it per the IBM documentation. Checking with openssl and gsk8capicmd_64 both, the certificate and its validity appears fine.

Now comes the weird part - when connecting the Administrator client (running on Windows Server 2012) using the SSL port (1446), it goes through and the connection is established. However, the Viewer Client (running on Windows Server 2012) refuses to connect with the same settings. The ubiquitous error - "Connection cannot be established..." is seen in this case. Am I missing something trivial?

An associate of mine is trying to connect from the Administrator Client on the same machine as mine, but he is not able to connect. This has left us all quite befuddled.

Side Note - I enabled the trace at server and client ends but can't seem to find the trace file anywhere. At the server, the file is named ARCHIVE.trace.log but a search for this filename fails. Trace level is 15 and ars.cfg file has been updated too. Where could it be?

2
Thanks for responding, Justin. That was what we perceived as well. Anyway, we have raised a PMR with IBM and will wait for their assistance. Once we have a solution, I shall post the same here.

3
Hi fellow techies,

I am trying to connect to an SQL Server 2017 [the chosen database for CMOD] installation on Windows Server 2016 from CMOD 10.5 [Library server] on Red Hat Enterprise Linux 7.7 box  (both on Azure cloud). Could you please help me understand:

1. If it is possible and has anyone implemented it?
2. What are the prerequisites at both ends?
3. Any kind of separate ODBC setup required on the the library server box?
4. Any other considerations?


I admit that a remote database isn't the ideal setup but we are doing it to enable MS Support (Azure, you see  :D ). IBM documentation doesn't give any clear answers including the mandatory prerequisites and configurations (ars.cfg, ars.dbfs etc.).
 
https://www.ibm.com/support/pages/creating-remote-microsoft-sql-server-database-ibm%C2%AE-content-manager-ondemand


Apologies if this looks like a noob question. Any help shall be really appreciated. Thanks

4
Thanks Greg. That seemed like the case. I have requested for some additional test files to see how the application behaves. Will share the outcome here. Thanks again, for your pointers  :)

5
Thanks Greg! LRECL is unchanged at 133.

It is worth noting that when I tried to index an old 16-page file (with an old layout), I just changed the index positions according to the said layout and was able to get 16 different files of one page each (and with correct indexes). So, my application should be in the right shape, I assume?

6
Quote
I see you have a trigger 2 defined but nothing using it.  Is it possible one, or more, of the fields got erroneously changed back to use trigger 1?
Thanks again for the quick response.
Unfortunately, even that is not the case. TRIGGER2 was defined way back but didn't really turn out helpful and left as is. So, as of today it is a redundant trigger.

7
Thanks Greg, for your inputs. I checked and found X'F1' to be present on top of all the pages (and got disappointed  :'( as I was hoping this answer would help me resolve my problem). 

8
Hi fellow ODUsers,
I have been facing a typical problem with document breaking. I had an existing report layout (for EBCDIC reports) being indexed using ACIF. Per the new revisions mandated by the customer,
1. The positions of some of the fields changed a little
2. For some other fields, the width changed a little
3. Two fields got added.

So, I made these minor changes to the Indexer code, no biggie. Now to the weird part - earlier the same (well, almost) indexing scheme used to split a multi-page document to multiple single-page documents based on the change in field values E.g. a 3-page document would be split into 3 separate documents of 1 page each and each of the documents would have the correct index values saved against it in the database. If the OutletID field is populated as 0133, 0149, 0157 on three different pages, it appeared likewise in the indexes. But now:

1. Three rows get created but no split actually happens. All the three documents contain all the three pages
2. The index values populated for the first document are correct (picked from the first page) but these values are also duplicated for the second and third documents. i.e. OutletID 0133 is getting populated for the other documents too. Likewise for other fields. Only the ProbationDate field changes now (it is based on a floating trigger)

Code: [Select]
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD,133
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                                                                           /* 1                */
TRIGGER2=2,61,X'C3E3D940C6C9D3C540D9C5D7D6D9E3',(TYPE=GROUP)                   /* CTR FILE REPORT  */
TRIGGER3=*,37,X'E5C9D6D3C1E3C9D6D540C4C1E3C5407A',(TYPE=FLOAT)                 /* PROBATION DATE : */
FIELD1=1,3,10,(TRIGGER=1,BASE=0)
FIELD2=4,17,3,(TRIGGER=1,BASE=0)
FIELD3=6,17,10,(TRIGGER=1,BASE=0)
FIELD4=4,54,8,(TRIGGER=1,BASE=0)
FIELD5=4,90,8,(TRIGGER=1,BASE=0)
FIELD6=7,17,100,(TRIGGER=1,BASE=0)
FIELD7=0,54,8,(TRIGGER=3,BASE=0,MASK='########',DEFAULT=X'F0F1F0F1F1F9F7F0')   /* 01011970         */
FIELD8=8,23,5,(TRIGGER=1,BASE=0)
FIELD9=5,17,9,(TRIGGER=1,BASE=0)
INDEX1=X'C49683A4948595A3C481A385',FIELD1,(TYPE=GROUP,BREAK=YES)                  /* DocumentDate     */
INDEX2=X'D98583969984E3A89785',FIELD2,(TYPE=GROUP,BREAK=YES)                          /* RecordCategory      */
INDEX3=X'E28598A485958385D5A494828599',FIELD3,(TYPE=GROUP,BREAK=YES)           /* SerialNumber   */
INDEX4=X'C396A58599818785C2',FIELD4,(TYPE=GROUP,BREAK=YES)                            /* CheckStartDate        */
INDEX5=X'C396A58599818785C5',FIELD5,(TYPE=GROUP,BREAK=YES)                            /* CheckEndDate    */
INDEX6=X'E2A482918583A3D5819485',FIELD6,(TYPE=GROUP,BREAK=YES)                    /* SubjectName      */
INDEX7=X'E589969381A3899695C481A385',FIELD7,(TYPE=GROUP,BREAK=NO)              /* ProbationDate     */
INDEX8=X'E2A3969985C9C4',FIELD8,(TYPE=GROUP,BREAK=YES)                                  /* OutletID  -position changed          */
INDEX9=X'C2A4A2E49589A3',FIELD9,(TYPE=GROUP,BREAK=YES)                                 /* BusinessUnit  - new field         */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

How the indexes appeared earlier:
DocumentDate   OutletID    RecordCat  CheckStartDate  CheckEndDate     SlNo      Subject                ProbationDate
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-02-26                   
2016-03-02       0149       3A           2016-03-20      2016-03-26      00002   ILVEA GOMEZ ZALAYA        2016-03-26                   
2016-03-02       0157       4A           2016-04-20      2016-04-26      00003   ILVEA GOMEZ ZALAYA        2016-04-26


How are they appearing now:
DocumentDate   OutletID    RecordCat  CheckStartDate  CheckEndDate     SlNo      Subject                ProbationDate
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-02-26                   
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-03-26                   
2016-03-02       0133       2B           2016-02-20      2016-02-26      00001   ILVEA GOMEZ ZALAYA        2016-04-26   

What could I be missing? Any help will be really appreciated.

Regards,
AP

9
Thanks for responding, Justin! I logged out and logged back 4-5 times, the first time I saw this. Didn't make a difference. Was wondering if terminating the CMOD instance and then restarting it would help? This is the PROD instance and while we are not getting any errors processing input files, it is unclear as to which arssockd instance is running. Here is what's making me lose it:

Code: [Select]
/home/adminod> ls -l `which arssockd`
-r-xr-xr-x    1 adminod sysctrl    11964020 Apr 23 2018  /opt/IBM/ondemand/V9.5/bin/arssockd
/home/adminod>


Upgrading to 9.5.0.12 would be another set of changes DEV --> QA --> PROD and might take a while. Not sure if the customer would agree to it.

10
MP Server / Updated CMOD version Not Reflecting with arssockd -I ARCHIVE -q
« on: December 05, 2018, 04:34:51 AM »
Greetings everyone,
We recently upgraded CMOD (installed on one of our AIX 7.1 systems) from v9.0.0.3 v9.5.0.11. All the pre-requisites were met and the installation steps went fine on the day of the upgrade and when I used arssockd -I ARCHIVE -q it showed me the correct version number (v9.5.0.11). All the relevant symlinks and paths were updated too.

However, when I logged back into the system today and queried arssockd -I ARCHIVE -q again, it threw the old version number (9.0.0.3). I checked if any of the scripts/symlinks/environment variables were still pointing to 9.0.0.3. It was found that the PATH variable in $HOME/.profile was pointing to the 9.0 setup. I rectified the same but am still seeing the old version on querying.

Weirdly enough, when I miss the -q flag, the system outputs the upgraded version:

Code: [Select]
/home/adminod > arssockd -I ARCHIVE | head -20
ARS0980I Usage: arssockd [options]
        Version:  9.5.0.11
        -h <od_inst> OnDemand instance name or host name (same as -I)
        -I <od_inst> OnDemand instance name or host name (same as -h)
        . . .
        . . .

What might be wrong/missing? Any suggestions will be much appreciated.

EDIT: When I invoke arsload to ingest a standalone file, the server version comes up as 9.0.0.3. This is crazy  :-X

Code: [Select]
/arsacif/filestobeloaded > arsload -h localhost -I ARCHIVE -u adminod -p xxxxx -g AGNAME -a AppName AGNAME.AppName.20181205.063536.ARD

2018-12-05 06:44:38.808252: ARS4334I Load Version <9.5.0.11>  Operating System <AIX> <7.1>  OS Userid <ADMINOD>  Install Location </opt/IBM/ondemand/V9.5/> Data(unlimited KB) Stack(unlimited KB) Core(0 512-blocks) Cpu(unlimited seconds) File(unlimited 512-blocks) Nofiles(unlimited) Threads(262144) Processes(262144)
2018-12-05 06:44:38.808300: ARS4335I Server Version <9.0.0.3> Operating System <AIX> <7.1>  Database <DB2> <10.05.0010>
....
....

Also, the same set of installation steps were performed on another server (the QA box) and it is absolutely fine. Displays the correct version number too (with arssockd -I ARCHIVE -q)


Warm regards,
AP

11
MP Server / Re: Weird Error: The application group >< does not exist
« on: October 08, 2018, 05:16:17 AM »
Greetings Fellow ODUsers,
Apologies for such a delayed response. The good news, though, is that we were able to solve this issue by upgrading to 9.5.0.11. We had to raise a PMR because the arsload version was not upgraded in the initial 9.5.0.11 installation (that ideally should have). IBM suggested to do a re-installation of this fix pack after killing any running arsload processes/daemons. We did so and voila! all the files are getting processed successfully now by the arsload daemons. Thanks for your inputs, everybody!

Warm regards,
Abhinav

12
Apologies for the delayed reply. The activity was back-burnered for a while and just got back on track. We are going to upgrade to the latest fix pack (9.5.0.11) as suggested by JD (thanks   :) ) . I will let the group know how that pans out.

Warm regards,
AP

13
Thanks for the suggestion, JD. We were about to sign-off the UAT installation when I saw this error. If we are to install 9.5.0.11, probably another couple of weeks would go to DEV and UAT testing. Then there is this issue of ICN setup compatibility. Will look into it though. I am totally pro-upgrade but if we find a way out otherwise, I shall share the same with fellow ODUsers.

Regards,
AP

14
Thanks ssorich. While I've checked the filenames (of the failing files) for any such anomalies, I'll revisit and check again.

And thanks JD, for the fix pack download link. Once I am done reverifying the filenames, I'll probably install 9.5.0.10. Hopefully that'll fix the issue  :)

15
MP Server / Re: Weird Error: The application group >< does not exist
« on: April 27, 2018, 01:28:38 PM »
Thanks a lot, JD! I was thinking on the same lines. As suggested, will raise a PMR to start with, and if IBM insists on a fix-pack upgrade (which I am guessing they are going to), will proceed with that.

Regards,
AP

Pages: [1] 2 3