Messages

1

Report Indexing / Re: ACIF Indexer loads report multiple times (number of pages)

« on: April 28, 2021, 07:43:20 AM »

Update.....

So I removed TRIGGER2 and changed the FIELD2 for TRIGGER1 and the multiple loading issue went away. Go figure.

Thanks all!

2

Report Indexing / ACIF Indexer loads report multiple times (number of pages)

« on: April 27, 2021, 11:12:58 PM »

I am at my whits end here. We had a report in EBCDIC format and loading fine. Source migrated off the mainframe zOS and is now generating same report in ASCII. I made the necessary conversions from OS390 to ACIF indexer and now the report indexes and loads fine with one exception.... if the report is 6 pages, it loads 6 rows, each row is the same 6 page report. If it's 50 pages, it loads 50 rows of the same index data and 50 page document!

Anyone ever seen this before?

CC=YES
CCTYPE=Z
CONVERT=NO
CPGID=850
MCF2REF=CPCS
TRC=NO
FILEFORMAT=STREAM,(NEWLINE=X'0A')
TRIGGER1=*,1,X'31',(TYPE=GROUP)                                 /* 1           */
TRIGGER2=*,6,X'53445F5250',(TYPE=FLOAT)                         /* SD_RP       */
FIELD1=1,6,6,(TRIGGER=1,BASE=0)
FIELD2=0,12,10,(TRIGGER=2,BASE=0)
FIELD3=2,11,10,(TRIGGER=1,BASE=0)
FIELD4=1,59,18,(TRIGGER=1,BASE=0)
FIELD5=1,77,16,(TRIGGER=1,BASE=0)
INDEX1=X'425245414B5F5331',FIELD1,(TYPE=GROUP,BREAK=YES)        /* BREAK_S1    */
INDEX2=X'5245504F52545F4944',FIELD2,(TYPE=GROUP,BREAK=NO)       /* REPORT_ID   */
INDEX3=X'5245504F52545F44415445',FIELD3,(TYPE=GROUP,BREAK=NO)   /* REPORT_DATE */
INDEX4=X'5449544C455F31',FIELD4,(TYPE=GROUP,BREAK=NO)           /* TITLE_1     */
INDEX5=X'5449544C4532',FIELD5,(TYPE=GROUP,BREAK=NO)             /* TITLE2      */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

3

OD/WEK & JAVA API / Re: How can I verify version of ODWEK Java API ?

« on: June 20, 2014, 08:37:23 PM »

Use ODServer class and GetVersion method.

Class ODServer
java.lang.Object
  extended by com.ibm.edms.od.ODServer

All Implemented Interfaces: java.io.Serializable


getVersion
public java.lang.String getVersion()
Get the ODWEK Version string for this version of the ODApi.jar.

Returns:String indicating the Release and PTF version of ODWEK.

Code Snippet

      ODConfig ocfg = new ODConfig();
      ODServer osrv = new ODServer(ocfg);
      osrv.initialize("Testing");
      osrv.setServerName("localhost");
      osrv.setPort(1445);
      osrv.setUserId("admin");
      osrv.setPassword("password");
      osrv.logon();
      System.out.println("ODWEK Version is " + osrv.getVersion());

4

z/OS Server / Re: CMOD 9.0 ARSLOAD throws S0C4 trying to load an empty file. Used to be RC 0001

« on: June 16, 2014, 01:27:42 PM »

Here?s what I found
Primary Command: FIND

Entry Type:  SYSMOD                              Zone Name: MVST100
Entry Name:  UA67692                             Zone Type: TARGET
Description:

  Type:                          Status:
  FMID:                          SUPBY   UA71790
  Date/Time:
        -------- -------- -------- -------- -------- -------- --------
Entry Type:  SYSMOD                              Zone Name: MVST100
Entry Name:  UA67735                             Zone Type: TARGET
Description:

  Type:                          Status:
  FMID:                          SUPBY   UA71790
  Date/Time:

Ed, did UA71790 address this issue in OA43472?

5

z/OS Server / Re: CMOD 9.0 ARSLOAD throws S0C4 trying to load an empty file. Used to be RC 0001

« on: June 16, 2014, 08:49:42 AM »

Thanks Ed! I am checking with my mainframe guys now to see if either PTF has been applied.

6

z/OS Server / CMOD 9.0 ARSLOAD throws S0C4 trying to load an empty file. Used to be RC 0001

« on: June 03, 2014, 11:04:31 AM »

We just have ARSLOAD installed on zOS that loads reports to CMOD 9.0 installed on multiplatform. However, the issue here is NOT with CMOD MP, it is with the zOS side.

It seems we had a zOS upgrade [zOS 1.13 Maintenance (RSU1402)] over the weekend and prior to the patch, if ARSLOAD tried to load an empty file, the return code was RC=0001 and that was fine. Now post the maintenance patch, ARSLOAD throws a S0C4 error!

Any ideas how to resolve a S0C4 error loading an empty file?

Thanks,
John

7

MP Server / Re: Copy TSM storage objects back to Cache ...

« on: October 01, 2013, 06:27:46 AM »

Good Morning,

I am trying to remember how to work backwards to identify a document given the name on the file system. Said a different way... we installed the CMOD 9.0.0.1 and upgraded the database from the previous version, but just copied over a few of the cache files for now.

I can see <retr><OAA><DOC>104FAA and 104FAA1 for example. How do I query the database to know which metadata to search to find this object from my folders?

I remember doing it many moons ago during training, but haven't done it since.

Thanks,
John

8

MP Server / Re: arsstash problem Od 9.0

« on: August 29, 2013, 10:05:18 AM »

Okay seem the order is very important for the parameters

This works:
arsload -h usgobtcmod800.company.com -u admin -p admin.stash -a ABSREPT-V01 -g PDF1010YR -X G ABS.0.PDF1010YR.ABSREPT-V01

This doesn't:
arsload -a ABSREPT-V01 -g PDF1010YR -X G ABS.0.PDF1010YR.ABSREPT-V01 -h usgobtcmod800.company.com -u admin -p admin.stash

Just in case anyone else might have had this issue.

Thanks,
John

9

MP Server / Re: OnDemand 8.5.0.5 to 9.0.0.0 Upgrade

« on: August 29, 2013, 09:48:56 AM »

Hi Glenda,

I apologize. I am only now seeing your question. I have to check my settings because I didn't get a notification (I thought I remembered somewhere such a setting.)

Anyway..... we are upgraded to 9.0.0.1 in DEV and INT, but not PROD yet. We are still working through several challenges with our large PROD database and moving to a new server since this version requires 2008 64 bit server and previous version was on 2003 Server.

My main issue now is that the ARSLOAD command seems to have changed from the previous 8.4 version we are on. It doesn't work as is and I am still trying to figure it out.

10

MP Server / Re: arsstash problem Od 9.0

« on: August 28, 2013, 02:01:29 PM »

I created a couple stash files; one for admin (admin.stash) and one for zosloader (zosloader.stash) and trying to perform the following:

Create a stash file for ARSLOAD using zosloader:
J:\Program Files\IBM\OnDemand for Windows\V9.0\bin>arsstash -a 3 -c -s zosloader.stash -u zosloader
OnDemand Password:
Verify OnDemand Password:

The zosloader.stash file is created

I also created the admin stash file:
J:\Program Files\IBM\OnDemand for Windows\V9.0\bin>arsstash -a 1 -c -s admin.stash -u admin
OnDemand Password:
Verify OnDemand Password:

The admin.stash file is created

Extract Documents using ARSDOC GET and admin.stash file:
arsdoc get -h usgobtcmod40.company.com -u admin -p admin.stash -f "AGENCY BUSINESS SUMMARY" -q "ABS_DR_TEST" -N -c -v -a -g -o ABS

This works beautifully and creates two files:
            ABS.0.PDF1010YR.ABSREPT-V01.ind
            ABS.0.PDF1010YR.ABSREPT-V01.out

But now I am trying to load these documents extracted to the CMODDEV v9.0 environment: and I keep getting the following message:

arsload -a ABSREPT-V01 -g PDF1010YR -X G ABS.0.PDF1010YR.ABSREPT-V01 -h usgobtcmod800.company.com -u zosloader -p zosloader.stash
ARS4315I Processing file >ABS.0.PDF1010YR.ABSREPT-V01<
ARS1105E Userid or password is invalid
ARS4318E Processing failed for file >ABS.0.PDF1010YR.ABSREPT-V01<
ARS1105E Userid or password is invalid
Unable to log load information
Processing has stopped.  The remaining files will NOT be processed.

Even when I use the actual password for ZOSLOADER or I use the admin id and password I still get that error message!!

I cannot for the life of me see what is wrong.

11

Tips and Tricks / Re: Validating Cache Storage

« on: May 28, 2013, 08:03:17 AM »

Thanks Ed.

I noticed that on our Production server, the permissions and ownership of the arscache files and folders were not full control and ownerd by the ID used to install OnDemand (like it is on the DEV and  INT servers.) The ownership got switched I think when we moved the data from the local server HDD to SAN and the Distributed Systems ID was used for that.

I have asked our Distributed Systems team to change the Ownership of that one file to the OnDemand Schema ID that the Sceduler Service runs under. I will wait to see the results tonight. If it still fails, then I will ask that they also give the ID Full COntrol of the file (right now it has Modify.)

Will keep you posted.

12

MP Server / Re: ARSMAINT -r error - Resolved

« on: May 28, 2013, 07:56:38 AM »

I found this explaination

http://www-01.ibm.com/support/docview.wss?uid=swg21383609

Problem(Abstract)
Running the arsmaint utility against my IBM? Content Manager OnDemand server to update database statistics intermittently throws the following similar error in the System Log:

ARSMAINT 434684 Error No 13 DB Error: RUNSTATS ON TABLE root.SL25 -- SQLSTATE=Not Defined, SQLCODE=1, File=arssys.c, Line=1287

Cause
The error is occurring because runstats is attempting to update statistics on a table that is currently being inserted into.

Arsmaint -r should be run at a time when little to no activity is occurring in the OnDemand System.

13

Tips and Tricks / Re: Validating Cache Storage

« on: May 23, 2013, 10:34:35 AM »

Ed,

I am on Windows and scheduled the ARSMAINT to run, but after a couple Message 164s, I get a message 198

What ID should be the owner of these files? And what permissions should be set?

   124   Filesystem Stats Name(m:\arscache1\CMODPROD) Data(84%) Inodes(-2147483648%)  Srvr->usgobtcmod40.somecompany.com <-
    32   Logoff
   198   Invalid ownership and/or permissions on cache file/directory >m:\arscache1\CMODPROD\17377\XEA\DOC\1827FAAO<  Srvr->usgobtcmod40.somecompany.com x.x.x.x<-
   164   Application Group Segment Maintenance: Name(DOC1010YR) Agid(5206) SegName(IAA1) Action(2) Time(37.109)
   164   Application Group Segment Maintenance: Name(DOC101YR) Agid(5248) SegName(JAA1) Action(2) Time(0.984)
   164   Application Group Segment Maintenance: Name(DOC102YR) Agid(5342) SegName(LAA1) Action(2) Time(10.703)
   164   Application Group Segment Maintenance: Name(DOC107YR) Agid(5403) SegName(OAA1) Action(2) Time(14.875)
   164   Application Group Segment Maintenance: Name(DOC1030D) Agid(5393) SegName(MAA1) Action(2) Time(0.078)
   164   Application Group Segment Maintenance: Name(DOC1090D) Agid(5494) SegName(PAA1) Action(2) Time(0.172)
   164   Application Group Segment Maintenance: Name(DOC10GDO) Agid(5853) SegName(ZBA1) Action(2) Time(0.734)
   164   Application Group Segment Maintenance: Name(DOC10GDA) Agid(5839) SegName(TBA1) Action(2) Time(0.016)
   164   Application Group Segment Maintenance: Name(DOC10GD) Agid(5833) SegName(RBA1) Action(2) Time(0.031)
   164   Application Group Segment Maintenance: Name(DOC10CMB) Agid(5637) SegName(CBA1) Action(2) Time(0.188)
   164   Application Group Segment Maintenance: Name(DOC10CMA) Agid(5635) SegName(BBA1) Action(2) Time(0.032)
   164   Application Group Segment Maintenance: Name(DOC10AWO) Agid(5575) SegName(TAA1) Action(2) Time(0.062)
   164   Application Group Segment Maintenance: Name(DOC10ACO) Agid(5499) SegName(QAA1) Action(2) Time(0.094)
   164   Application Group Segment Maintenance: Name(DOC10GZA) Agid(6022) SegName(DCA1) Action(2) Time(0.516)
   164   Application Group Segment Maintenance: Name(DOC10GWA1YR) Agid(6020) SegName(CCA1) Action(2) Time(0.047)
   164   Application Group Segment Maintenance: Name(DOC10GW) Agid(6011) SegName(ACA1) Action(2) Time(0.063)
   164   Application Group Segment Maintenance: Name(DOC10SPO) Agid(6278) SegName(VCA1) Action(2) Time(29.938)
   164   Application Group Segment Maintenance: Name(DOC10GZB) Agid(6024) SegName(ECA1) Action(2) Time(0.140)
   164   Application Group Segment Maintenance: Name(DOC10STO) Agid(6282) SegName(XCA1) Action(2) Time(0.609)
   164   Application Group Segment Maintenance: Name(DOC18) Agid(6678) SegName(IDA1) Action(2) Time(39.468)
   164   Application Group Segment Maintenance: Name(DOC10ZZB) Agid(6594) SegName(ZCA3) Action(2) Time(0.891)
   164   Application Group Segment Maintenance: Name(DOC35A) Agid(6805) SegName(YDA1) Action(2) Time(20.906)
   164   Application Group Segment Maintenance: Name(DOC18GDA) Agid(6791) SegName(TDA1) Action(2) Time(0.078)
   164   Application Group Segment Maintenance: Name(NODX10AA) Agid(6976) SegName(FEA1) Action(2) Time(1.157)
   164   Application Group Segment Maintenance: Name(NODX10AA2YR) Agid(7222) SegName(KEA1) Action(2) Time(0.625)
   164   Application Group Segment Maintenance: Name(NODX10AA1YR) Agid(7180) SegName(IEA1) Action(2) Time(0.157)
   164   Application Group Segment Maintenance: Name(NODX10AA7YR) Agid(7268) SegName(NEA1) Action(2) Time(1.406)
   164   Application Group Segment Maintenance: Name(NODX10AA60D) Agid(7260) SegName(MEA1) Action(2) Time(0.062)
   164   Application Group Segment Maintenance: Name(NODX10AA30D) Agid(7246) SegName(LEA1) Action(2) Time(0.125)
   164   Application Group Segment Maintenance: Name(PDF31A) Agid(7377) SegName(EFA1) Action(2) Time(27.719)
   164   Application Group Segment Maintenance: Name(NODX18AA) Agid(7341) SegName(QEA1) Action(2) Time(0.110)
   164   Application Group Segment Maintenance: Name(NODX10AA90D) Agid(7331) SegName(OEA1) Action(2) Time(0.031)
   164   Application Group Segment Maintenance: Name(PDF33) Agid(7399) SegName(HFA2) Action(2) Time(29.391)
   164   Application Group Segment Maintenance: Name(PDF37A) Agid(7411) SegName(JFA17) Action(2) Time(10.453)
   164   Application Group Segment Maintenance: Name(System Load) Agid(7562) SegName(SA2) Action(2) Time(8.625)
   164   Application Group Segment Maintenance: Name(System Log) Agid(7603) SegName(SL7) Action(2) Time(25.265)
   164   Application Group Segment Maintenance: Name(PDF14D) Agid(7652) SegName(UFA6) Action(2) Time(25.046)
    30   Login: usgobtcmod40.somecompany.com x.x.x.x

Thanks,
John

14

MP Server / Re: Unable to allocate enough memory / cannot connect

« on: October 22, 2012, 06:20:58 AM »

Ok.. this is taking a stab in the dark here.......

ARSLOAD for z/OS and naturally AIX, uses a temporary folder on the Unix System (MVS in the z/OS case.) It creates temporary files in a location that you configure it to use and those temporary files are supposed to be deleted after loading. However, in some instances they are not. Later you try to load a report with a different ID and the system tries to create a temporary file with the same name as one already existing and it can't delete/overwrite it.

I know you are thinking "what does this have to do with out of memory error?" I don't trust that message you see there are the real root cause, but a mere side effect.

You need to delete all temp files from this location.

It will be the value of the ARS_TMP variable. In our case it is set as follows:

ARS_TMP=/fs/arstemp/KAHP/arstemp/tmp

If you don't have permissions to this folder, you will have to get the Unix Admin to delete them for you.

This was the message we saw (just like you)

FILE>       KAHXGD.KAH$GDBN.JOB32664.D0000106.?,2012.291,23:27:07:60       <FILE
arsload: Using /fs/arstemp/KAHP/arstemp/tmp for temporary files                
arsload: Processing file >/fs/arstmp/KAHP/tmp/kah16777584 (DD:OBJINPT-GD.D00H001
arsload: 10/17/12 23:26:55 -- Loading started, --UNKNOWN-- bytes to process    
arsload: 10/17/12 23:26:56 Loading failed                                      
arsload: Processing failed for file >/fs/arstmp/KAHP/tmp/kah16777584 (DD:OBJINPT
Unable to allocate enough memory.  File=arsadmin.c, Line=791                    
arsload: Unable to log load information                                        
arsload: Processing has stopped.  The remaining files will NOT be processed.    



When we dug deeper, we found this..

ICH408I USER(KAHXGD  ) GROUP(KAHONDMD) NAME(PROD APPLID VIA E
  /fs/arstemp/KAHP/arstemp/tmp/16777584.arsload.env          
  CL(FSOBJ   ) FID(01D2C1C8C6E2F90001050229C7640000)        
  INSUFFICIENT AUTHORITY TO OPEN                            
  ACCESS INTENT(-W-)  ACCESS ALLOWED(GROUP      R--)        
  EFFECTIVE UID(0000025172)  EFFECTIVE GID(0000001034)

Deleted those previously created temp files and load ran succesfully.

15

MP Server / Re: ODWEK 9.0 supported on 32-bit?

« on: October 22, 2012, 05:56:27 AM »

Yes, Justin, it is. Our intention is to go 64-bit all around, but we have a predicament.....

We use IBM Content Integrator (ICI) in conjunction with a web service we wrote to connect to Content Manager (CM,) OnDemand (CMOD) and FileNet Image Services (FN.) CM and CMOD connectors have no problem working in a 64-bit environment. It's the FileNet Connector that uses J-Integra that doesn't work. Apparently, the FileNet connector is hardcoded to use J-Intergra in native mode for performance purposes. As it turns out.. J-Integra will only work in DCOM mode on 64-bit. We are currently on ODWEK 8.4.1.2. If we upgrade to ODWEK 9.0 and it requires Win2K8 and 64-bit hardware, we can't have the connectors all installed on the same server.